https://bugzilla.novell.com/show_bug.cgi?id=463450 User koenig@linux.de added comment https://bugzilla.novell.com/show_bug.cgi?id=463450#c9 Harald Koenig <koenig@linux.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|koenig@linux.de | --- Comment #9 from Harald Koenig <koenig@linux.de> 2009-01-05 10:38:33 MST --- (In reply to comment #8 from Josef Reidinger)
Interesting think is that as hd0 is /dev/disk/by-id/usb-Maxtor_OneTouch_II_B41M9YBH-0:0,
Maxtor_OneTouch_II is only hd0 when booting form DVD9 for update. I guess that's because the 3ware driver (3w_xxxx) gets loaded _after_ the usb storage modules. so the usb disks are detected first and the internal raid later (too late). during update the internal raid is sdc (boot partition was sdc5, now back as sda5)
but I expect, that you have your /boot on /dev/sda5, which is on raid...so you have your boot partition on your raid, correct? (I am little confused by many devices you have :)
correct! it's not only you being confused;) but it's quite easy (TM) to fix fstab and menu.lst after update -- not sure if this is really worth a bug report (though it's really annoying and IMHO a nasty bug) because my setup s a bit exotic and it's hard to describe and test (well, now this happend, so you can fix that bug too;)) unfortuneately(?) the 3ware raid partitions do not show up in /dev/disk/by-id/ (only LVM PV sda7 shows up as /dev/disk/by-id/lvm2-pvuuid-*) the boot partition sda5 only shows up in /dev/disk/by-path/ and /dev/disk/by-uuid/ (but I don't like those long paths in fstab and menu.st anyway for "optical" reasons -- so I myself can live with those renaming problems;) -- 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.