https://bugzilla.novell.com/show_bug.cgi?id=333753#c4 Occo Eric Nolf <oen@dsl.pipex.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |REOPENED Info Provider|oen@dsl.pipex.com | --- Comment #4 from Occo Eric Nolf <oen@dsl.pipex.com> 2007-10-19 08:08:29 MST --- Hi Hannes, No, that's not what I'm saying. Any attempt to install 10.3 on my RAID0+1 system, and any attempt to upgrade to 10.3, results in a system that appears not to be accessible at all. The installation or upgrade stops at the point where the initrd should be written. There is no other option available than to break off the process; the result is a system without initrd and with the 'old' boodloader which doesn't know about the partially installed 10.3 system. To apply any patch it would be necessary to access the partially installed 10.3 system via the rescue system. This may be possible, but I'm not an expert in that particular area. However, even if that would work it would still mean that the mkinitrd script in the 10.3 installation program remains 'buggy'. If you think the patch for #334461 would solve the problem I described in my first post here, I'm willing to give it a try - provided you can tell me how to apply the patch via the rescue system. Any 10.3 installation or upgrade overwrites my existing 10.2 system which has to be re-installed if 10.3 won't run. I'm not looking forward to that, so please don't ask me to try unless you're fairly sure the patch will do the job :-)) Eric -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.