[Bug 533800] New: mkinitrd: fails to understand fstab's LABEL= names
http://bugzilla.novell.com/show_bug.cgi?id=533800 Summary: mkinitrd: fails to understand fstab's LABEL= names Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: x86 OS/Version: Linux Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: jengelh@medozas.de QAContact: qa@suse.de Found By: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.0.13) Gecko/2009080200 SUSE/3.0.13-0.1.2 When /etc/fstab contains a LABEL= specification for the root filesystem, mkinitrd fails. Reproducible: Always Steps to Reproduce: 1. Start 11.1 installer 2. Choose "mount by filesystem label" (and give the filesystems some label) 3. When initial installation is done and the new system itself runs, run mkinitrd. Actual Results: # mkinitrd -k vmlinuz -i itest Kernel image: /boot/vmlinuz Initrd image: /boot/itest Root device: /dev/root (mounted on / as xfs) Device root not found in sysfs Script /lib/mkinitrd/setup/72-block.sh failed! Expected Results: Cope with the situation, or never use LABEL= in the first place (but instead: /dev/disk/by-label/ when the installer creates the fstab entries) Oddly enough, the initial system is installed fine, despite the use of LABEL=. It is only in the final system. Also, there is a workaround possible: using "/dev/disk/by-label/root" instead of "LABEL=root" in fstab, after which things work: # mkinitrd -k vmlinuz -i itest Kernel image: /boot/vmlinuz Initrd image: /boot/itest Root device: /dev/disk/by-label/root (/dev/md1) (mounted on / as xfs) Kernel Modules: scsi_mod libata ahci exportfs xfs md-mod raid1 crc-t10dif sd_mod usbcore ohci-hcd uhci-hcd ehci-hcd hid usbhid raid0 xor async_tx async_memcpy async_xor raid456 Features: block usb md 16091 blocks -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=533800 shuang qiu <sqiu@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sqiu@novell.com AssignedTo|bnc-team-screening@forge.pr |mvancura@novell.com |ovo.novell.com | -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=533800 http://bugzilla.novell.com/show_bug.cgi?id=533800#c1 Felix Miata <mrmazda@earthlink.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mrmazda@earthlink.net --- Comment #1 from Felix Miata <mrmazda@earthlink.net> 2009-11-24 02:42:28 UTC --- I have the same problem, except my / is /dev/md2. I must change fstab from LABEL=09suse111 to /dev/md2 to get mkinitrd to work as it does with oS 11.0. Is the root cause of this problem the same as for bug 483136 ? -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=533800 http://bugzilla.novell.com/show_bug.cgi?id=533800#c2 Joe Morris <joe_morris@ntm.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |joe_morris@ntm.org --- Comment #2 from Joe Morris <joe_morris@ntm.org> 2009-12-01 13:48:51 UTC --- This bit me last night on a remotely administered server. I had changed fstab to mount by label via Yast due to upgrading a couple hard drives running md raid1. I am glad I noticed the problem before trying to reboot. Changing fstab to mount by /dev/disk/by-label/ instead of LABEL= allowed mkinitrd to work. Last night, in the crunch, I worked around it by mkinitrd -d /dev/md2. Thanks for the /dev/disk/by-label idea. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=533800 http://bugzilla.novell.com/show_bug.cgi?id=533800#c3 --- Comment #3 from Joe Morris <joe_morris@ntm.org> 2009-12-01 13:53:28 UTC --- Just thought, the failure I saw last night mentioned /lib/mkinitrd/setup/72-block.sh. Not sure if setup-block.sh is the source of the problem or not, but thought I would mention the failure. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=533800 http://bugzilla.novell.com/show_bug.cgi?id=533800#c5 Michal Marek <mmarek@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |jengelh@medozas.de --- Comment #5 from Michal Marek <mmarek@novell.com> 2010-01-22 15:16:30 UTC --- Does it fail also with the current Factory mkinitrd package (which fixes bug 483136)? -- Configure bugmail: http://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=533800 https://bugzilla.novell.com/show_bug.cgi?id=533800#c6 Michal Marek <mmarek@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |RESOLVED InfoProvider|jengelh@medozas.de | Resolution| |NORESPONSE --- Comment #6 from Michal Marek <mmarek@novell.com> 2011-08-01 12:13:57 UTC --- Please reopen if the problem persists in 12.1. -- 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.
participants (1)
-
bugzilla_noreply@novell.com