https://bugzilla.novell.com/show_bug.cgi?id=290959#c1 Marcus Meissner changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |meissner@novell.com --- Comment #1 from Marcus Meissner 2007-07-10 23:30:41 MST --- left overs from bootloader problems. entry 3 has a wrong initrd line at least. and default should be 0 perhaps. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=290959 Matej Horvath changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team- |kernel-maintainers@forge.provo.novell.com |screening@forge.provo.novell| |.com | -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=290959#c4 --- Comment #4 from Richard Creighton 2007-09-02 13:05:16 MST --- I suggest the reason it 'works for you' has more to do with your equipment than the script. I believe the change from calling IDE drives HDn to SDn has caused many unanticipated side effects including this one. This bug will bite anyone that has a mixed hardware architecture, ie, 1 or more IDE drives and 1 or more SATA drives upon which the 10.3 upgrade is being installed. Because of the rename between versions, the script will write the changed files to the new SDAn drive which is the old physical HDAn device whih causes the failure. Unless you have a mixed hardware architecture when you test and unless you have the 10.3 on a SATA drive and the SATA is renamed by the kernel version upgrade, you will not experience the privilege of seeing the bug in action so of course, it will 'work for you'. I don't know who thought of renaming HDn to SDn in mixed architecture hardware systems, but it was ill conceived and has caused me and undoubtedly many thousands of others many headaches. When Novell upgrades from 10.2 and earlier to it's customers that have both IDE and SATA hardware, expect big problems unless you take the time to evalulate this renaming scheme a little more fully. Now is the time to take this bug and see it for what it really is and not dismiss it so casually as 'works for me'. Give it to someone that has the proper hardware to be affected by it and let them troubeshoot it. I assure you it is real. This bug has been reported in several dozen different forms in bugzilla and the root cause is the same in each case. I want SuSE and Novell to suceed which is why I am a beta tester and volunteer my equipment and time for free. I risk damage to my equipment knowing that beta software can damage it. I accept that. What I can't accept is 'works for me' without examining the root cause of reported failures. Now that I hope you understand that there is a root cause beyond the symptom of 'won't boot after upgrade', dig into it more deeply, but don't write it off. That makes your free beta testers feel worthless and ultimately dooms Novell to failure and with that failure, your job is moot as well. I hope you can see that. I know you are busy and probably under a lot of pressure with a large workload, but this one is very important, don't let it go so casually. -- 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.