Bugzilla – Bug 440986
update from beta2 to beta4 changes from libata to old PATA drivers (sda -> hda), resulting in unbootable system.
Last modified: 2008-11-26 00:12:21 UTC
Created attachment 249345 [details] yast2 logs from "save_y2logs" after update system was updated from beta2 (FACTORY from 18.10.2008) to beta4 by booting from dVD and updating from DVD. This changed the harddisk drivers from libata to old PATA drivers (sda -> hda), resulting in unbootable system (lots of other fallout, of course). Will file separate bugs for bootloader configuration etc.
Hmmm... b2 and b3/4 have different driver priorities. It would make sense if b2->4 upgrade renamed hda -> sda but the other way around is a bit strange. Oh... I see. We don't have modules.order in the installation initrd. cc'ing Alex. Alex, the installation initrd doesn't have modules.order and so modprobe loads IDE driver before libata ones. IIRC, you tracked this down for the initrd of installed systems, right? Do you know who should be bugged for the installation initrd? Thanks.
The installed system also uses hda.
The installed system uses whatever the instsys uses - unless yast decides to kick in. So if the instsys uses old IDE drivers, you will most probably end up with IDE drivers in the installed system too. Instsys is snwint. I'll reassign this to him.
I see no modules.order in our kernel rpms. Where should it come from?
Anyway, looks like a kernel packaging bug.
It should be in the kernel rpm. I remember it was in the kernel rpm. Maybe it got lost while splitting the kernel packages? cc'ing Andreas. Andreas, modules.order should be in the kernel package, most likely the base one. Any ideas how this can be done? Thanks.
Created attachment 249743 [details] YaST2 logs from a fresh installation (disk devices vere not available during reboot) I have got the same problems even during fresh installation. The disk devices were not available after the reboot => the installation were not finished, system was not usable, ...
*** Bug 439314 has been marked as a duplicate of this bug. ***
*** Bug 441463 has been marked as a duplicate of this bug. ***
Btw. 441384 might be a duplicate of this. Increasing priority to P1, this needs to be fixed for next build (AJ speaking for openSUSE core team).
Yes, these are duplicates. #441384 is newer, but it has the gmane links, so let's continue there. *** This bug has been marked as a duplicate of bug 441384 ***
The following bugs may also end up being duplicates: bug 439183 and bug 448081