[Bug 444378] New: Kernel upgrade problems with devices
https://bugzilla.novell.com/show_bug.cgi?id=444378 Summary: Kernel upgrade problems with devices Product: openSUSE 11.1 Version: Factory Platform: x86-64 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: lmedinas@gmail.com QAContact: qa@suse.de Found By: --- Since i upgraded to 11.1 (around beta2) i have some problems with initrd, grub and fstab. On my fstab i list my disks partitions as /dev/dm-x grub and initrd uses /dev/mapper/sil_agaecedfccfb_part1 but when i boot kernel it falls back to /dev/disk/by-id/ata-Maxtor_6V250F0_V596HXEG-part1 and the funny part is df -h shows Filesystem Size Used Avail Use% Mounted on /dev/dm-1 97G 74G 18G 81% / This make my latest factory kernel unbootable. Shouldn't kernel upgrades test or attribute the real devices ? I suspect something goes wrong with udev. -- 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=444378
User aorlovskyy@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=444378#c1
Alexander Orlovskyy
https://bugzilla.novell.com/show_bug.cgi?id=444378
Greg Kroah-Hartman
https://bugzilla.novell.com/show_bug.cgi?id=444378
User kasievers@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=444378#c2
Kay Sievers
Since i upgraded to 11.1 (around beta2) i have some problems with initrd, grub and fstab.
On my fstab i list my disks partitions as /dev/dm-x grub and initrd uses /dev/mapper/sil_agaecedfccfb_part1
but when i boot kernel it falls back to /dev/disk/by-id/ata-Maxtor_6V250F0_V596HXEG-part1
What means "falls back"? It waits for that at bootup?
and the funny part is df -h shows Filesystem Size Used Avail Use% Mounted on /dev/dm-1 97G 74G 18G 81% /
What do you mean?
This make my latest factory kernel unbootable.
Shouldn't kernel upgrades test or attribute the real devices ? I suspect something goes wrong with udev.
Please attach: /etc/fstab and /boot/grub/menu.lst and the output of: cat /proc/cmdline of the working kernel. -- 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=444378
User lmedinas@gmail.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=444378#c3
--- Comment #3 from Luis Medinas
https://bugzilla.novell.com/show_bug.cgi?id=444378
User lmedinas@gmail.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=444378#c4
--- Comment #4 from Luis Medinas
https://bugzilla.novell.com/show_bug.cgi?id=444378
User lmedinas@gmail.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=444378#c5
Luis Medinas
https://bugzilla.novell.com/show_bug.cgi?id=444378
User kasievers@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=444378#c6
Kay Sievers
https://bugzilla.novell.com/show_bug.cgi?id=444378
User lmedinas@gmail.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=444378#c7
Luis Medinas
https://bugzilla.novell.com/show_bug.cgi?id=444378
User kasievers@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=444378#c8
Kay Sievers
Yes i run everytime i upgrade the kernel.
Root device: /dev/disk/by-id/ata-Maxtor_6V250F0_V596HXEG-part1 (/dev/sda1)
Hmm, mkinitrd uses this as your root for some reason. What does: cat /proc/mounts on the running system print? What does: mountpoint -d / on the running system print? You can also try to override the root device for mkinitrd with: mkinitrd -d <root device> -- 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=444378
User lmedinas@gmail.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=444378#c9
Luis Medinas
https://bugzilla.novell.com/show_bug.cgi?id=444378
User kasievers@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=444378#c10
--- Comment #10 from Kay Sievers
cat /proc/mounts
/dev/sda1 / ext3 rw,errors=continue,user_xattr,acl,barrier=1,data=ordered 0 0
mkinitrd seems right, you do not use the dm device as the root filesystem, but boot from the "plain" partition.
mountpoint -d / 8:1
Same here, this is the device number of sda1, not a dm device.
Now the question is: what root device should i use to generate the new initrd ?
The root= string in the grub conf, the line for "/" in /etc/fstab and the root for mkinitrd should all be the same to work as expected. If you want to boot from the dm device, you should try passing the same string as you currently have in grub.conf and fstab to mkinitrd. I can not tell if that will work though. The other option, if you do not want to use device mapper as your root filesystem, is to use /dev/disk/by-id/ata-Maxtor_6V250F0_V596HXEG-part1 in the grub.conf, fstab. -- 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=444378
User lmedinas@gmail.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=444378#c11
--- Comment #11 from Luis Medinas
https://bugzilla.novell.com/show_bug.cgi?id=444378
User kasievers@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=444378#c12
--- Comment #12 from Kay Sievers
https://bugzilla.novell.com/show_bug.cgi?id=444378
User kasievers@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=444378#c13
Kay Sievers
participants (1)
-
bugzilla_noreply@novell.com