[Bug 208417] New: Root LV fails to mount after update
https://bugzilla.novell.com/show_bug.cgi?id=208417 Summary: Root LV fails to mount after update Product: SUSE Linux 10.1 Version: Final Platform: i686 OS/Version: SuSE Linux 10.1 Status: NEW Severity: Critical Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: spam.lounge@gmail.com QAContact: qa@suse.de Hi, I'm having trouble mounting the root filesystem after an update yesterday (kernel and udev). The only reference to this problem I've been able to find is listed on this openSUSE 10.2 Alpha 4 bug report, wich appears to be the exact same problem: https://bugzilla.novell.com/show_bug.cgi?id=204745 I have the root filesystem on top of a logical volume, and the initrd can't mount it. Here's the relevant output: Waiting for /dev/mapper/control to appear: . ok Loading reiserfs Resume device /dev/vg01/swap not found (ignoring) libgcc_s.so.1 must be installed for pthread_cancel to work /init: line 515: 726 aborted /sbin/evms_activate mount: special device /dev/vg01/root does not exist /init: line 490: /mnt/etc/fstab No such file or directory umount: /mnt: not mounted /init: line 511: /table_file: no such file or directory libgcc_s.so.1 must be installed for pthread_cancel to work /init: line 522: 846 aborted /sbin/evms_activate device-mapper: device doesn't appear to be in the dev hash table device-mapper: remove ioctl failed: no such device or address command failed Waiting for device /dev/vg01/root to appear........................... not found -- exiting to /bin/sh Evms_activate requires libgcc_s.so.1, which isn't on the initrd, but after building a custom initrd which includes it, the problem still persists. So apparently that's not the root of it. mount: special device /dev/vg01/root does not exist /init: line 490: /mnt/etc/fstab: no such file or directory umount: /mnt: not mounted /init: line 511: /table_file: no such file or directory device-mapper: device doesn't appear to be in the dev hash table device-mapper: remove ioctl failed: no such device or address command failed Waiting for device /dev/vg01/root to appear........................... not found -- exiting to /bin/sh Today there were also updated packages to initrd and multipath-tools, but these don't solve the problem after generating a new initrd. Reverting to old versions of the packages doesn't help either. Here are the versions of the packages I mentioned: kernel-default-2.6.16.21-0.25 mkinitrd-1.2-106.19 multipath-tools-0.4.6-25.11 udev-085-30.15 The system is, needless to say, unusable. The only way I've been able to generate new initrd's and update packages is to boot from another partition, mount the root filesystem and chroot into it. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=208417 fehr@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fehr@novell.com ------- Comment #1 from fehr@novell.com 2006-09-27 09:05 MST ------- It seems that for some reason mkinitrd is adding EVMS support to initrd instead of LVM support. evms_activate is completely unnecessary for your secnario, you need vgscan and vgchange instead. What does mkinitrd print when you call it? -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=208417 ------- Comment #2 from spam.lounge@gmail.com 2006-09-27 10:19 MST ------- That is indeed the problem. Here's the output of mkinitrd. Vg01/bulk is a non-system LV, I have no idea how or why it's showing up there.. ========================================================== Root device: /dev/vg01/root (/dev/evms/lvm2/vg01/bulk) (mounted on / as reiserfs) Module list: sis5513 processor thermal fan reiserfs dm_mod dm-mod dm-snapshot (xennet xenblk dm-mod dm-snapshot) Kernel image: /boot/vmlinuz-2.6.16.21-0.25-default Initrd image: /boot/initrd-2.6.16.21-0.25-default Shared libs: lib/ld-2.4.so lib/libacl.so.1.1.0 lib/libattr.so.1.1.0 lib/libc-2.4.so lib/libdevmapper.so.1.02 lib/libdl-2.4.so lib/libevms-2.5.so.0.5 lib/libhistory.so.5.1 lib/libncurses.so.5.5 lib/libpthread-2.4.so lib/libreadline.so.5.1 lib/librt-2.4.so lib/libuuid.so.1.2 Driver modules: ide-core ide-disk sis5513 processor thermal fan dm-mod dm-snapshot Filesystem modules: reiserfs Including: initramfs dm/evms2 fsck.reiserfs Bootsplash: SuSE (1024x768), SuSE (1400x1050) 15051 blocks Kernel image: /boot/vmlinuz-2.6.16.21-0.25-xen Initrd image: /boot/initrd-2.6.16.21-0.25-xen Shared libs: lib/ld-2.4.so lib/libacl.so.1.1.0 lib/libattr.so.1.1.0 lib/libc-2.4.so lib/libdevmapper.so.1.02 lib/libdl-2.4.so lib/libevms-2.5.so.0.5 lib/libhistory.so.5.1 lib/libncurses.so.5.5 lib/libpthread-2.4.so lib/libreadline.so.5.1 lib/librt-2.4.so lib/libuuid.so.1.2 Driver modules: ide-core ide-disk sis5513 processor thermal fan dm-mod dm-snapshot Xen domU modules: xennet xenblk dm-mod dm-snapshot Filesystem modules: reiserfs Including: initramfs dm/evms2 fsck.reiserfs No bootsplash for kernel flavor xen ========================================================== If I remove the evms package (I don't know how to remove evms from the initrd at build time), then it correctly builds in lvm2 support only and the resulting initrd can be used to boot the machine. /dev/hda3 is the single PV that holds the vg01 VG. ========================================================== /sbin/mkinitrd: line 3031: evms: command not found mdadm: /dev/hda3 does not appear to be an md device mdadm: /dev/hda3 does not appear to be an md device mdadm: /dev/hda3 does not appear to be an md device mdadm: /dev/hda3 does not appear to be an md device mdadm: /dev/hda3 does not appear to be an md device mdadm: /dev/hda3 does not appear to be an md device mdadm: /dev/hda3 does not appear to be an md device mdadm: /dev/hda3 does not appear to be an md device mdadm: /dev/hda3 does not appear to be an md device mdadm: /dev/hda3 does not appear to be an md device Root device: /dev/vg01/root (mounted on / as reiserfs) Module list: sis5513 processor thermal fan reiserfs dm_mod dm-mod dm-snapshot raid0 raid1 raid5 linear (xennet xenblk dm-mod dm-snapshot) Kernel image: /boot/vmlinuz-2.6.16.21-0.25-default Initrd image: /boot/initrd-2.6.16.21-0.25-default Shared libs: lib/ld-2.4.so lib/libacl.so.1.1.0 lib/libattr.so.1.1.0 lib/libc-2.4.so lib/libdevmapper.so.1.02 lib/libdl-2.4.so lib/libhistory.so.5.1 lib/libncurses.so.5.5 lib/libpthread-2.4.so lib/libreadline.so.5.1 lib/librt-2.4.so lib/libuuid.so.1.2 Driver modules: ide-core ide-disk sis5513 processor thermal fan dm-mod dm-snapshot raid0 raid1 xor raid5 linear Filesystem modules: reiserfs Including: initramfs dm/lvm2 fsck.reiserfs Bootsplash: SuSE (1024x768), SuSE (1400x1050) 12206 blocks Kernel image: /boot/vmlinuz-2.6.16.21-0.25-xen Initrd image: /boot/initrd-2.6.16.21-0.25-xen Shared libs: lib/ld-2.4.so lib/libacl.so.1.1.0 lib/libattr.so.1.1.0 lib/libc-2.4.so lib/libdevmapper.so.1.02 lib/libdl-2.4.so lib/libhistory.so.5.1 lib/libncurses.so.5.5 lib/libpthread-2.4.so lib/libreadline.so.5.1 lib/librt-2.4.so lib/libuuid.so.1.2 Driver modules: ide-core ide-disk sis5513 processor thermal fan dm-mod dm-snapshot raid0 raid1 xor raid5 linear Xen domU modules: xennet xenblk dm-mod dm-snapshot Filesystem modules: reiserfs Including: initramfs dm/lvm2 fsck.reiserfs No bootsplash for kernel flavor xen 12404 blocks ========================================================== -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=208417 fehr@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team- |hare@novell.com |screening@forge.provo.novell| |.com | ------- Comment #3 from fehr@novell.com 2006-09-27 10:31 MST ------- mkinitrd is definitely mis-detctig the root device to somehow confuses /dev/vg01/root and /dev/evms/lvm2/vg01/bulk and wrongly concludes you have a EVMS based root fs. Hannes I assume this detection of device for root fs is in mkinitrd. No idea why it looks into /dev/evms if the root device is given as /dev/vg01/root. Do you really have EVMS activated? If yes, this is no good idea. Using EVMS and LVM at the same time is dangerous since both will manage the same on-disk data structures unless you configure them carefully to work on distinct set of block devices. Could be helpfuls to have the output of the following commands: find /dev/evms -ls find /dev/mapper -ls find /dev/vg01 -ls dmsetup ls dmsetup table -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=208417 ------- Comment #4 from spam.lounge@gmail.com 2006-09-28 02:49 MST ------- No, I do not have EVMS activated, I only use LVM. In fact, before yesterday, I had no idea what EVMS was all about, so I most definitely never configured it on this system. I went back and re-installed the EVMS package after making sure there were no traces of it in the system (apart from the EVMS YaST modules), and rebuilt the initrd. Aparently having the package installed is enough for mkinitrd to assume I'm actually using EVMS and build the initrd on that assumption, plus the misdetection of the root filesystem you mentioned. The only way I can build a working LVM2 initrd is to remove the EVMS package altogether. Here's the output of those commands you mentioned, with the EVMS package installed, and again with no EVMS configuration done on my part: # find /dev/evms -ls 55305 0 drwxr-xr-x 4 root root 80 Sep 28 09:13 /dev/evms 55326 0 drwxr-xr-x 2 root root 60 Sep 28 09:13 /dev/evms/.nodes 55360 0 brw-r----- 1 root root Sep 28 09:13 /dev/evms/.nodes/hda 55306 0 drwxr-xr-x 2 root root 60 Sep 28 09:13 /dev/evms/dm 55463 0 crw-r----- 1 root root Sep 28 09:13 /dev/evms/dm/control # find /dev/mapper -ls 1802 0 drwxr-xr-x 2 root root 260 Sep 28 09:01 /dev/mapper 6464 0 brw------- 1 root root Sep 28 09:01 /dev/mapper/home 3933 0 lrwxrwxrwx 1 root root 16 Sep 28 09:00 /dev/mapper/control -> ../device-mapper 2022 0 brw------- 1 root root Sep 28 09:00 /dev/mapper/vg01-sled10--swap 2001 0 brw------- 1 root root Sep 28 09:00 /dev/mapper/vg01-sled10--root 1980 0 brw------- 1 root root Sep 28 09:00 /dev/mapper/vg01-swap 1968 0 brw------- 1 root root Sep 28 09:01 /dev/mapper/vg01-bulk 1937 0 brw------- 1 root root Sep 28 09:00 /dev/mapper/vg01-homesecure 1915 0 brw------- 1 root root Sep 28 09:00 /dev/mapper/vg01-tmp 1893 0 brw------- 1 root root Sep 28 09:01 /dev/mapper/vg01-var 1872 0 brw------- 1 root root Sep 28 09:01 /dev/mapper/vg01-usr 1860 0 brw------- 1 root root Sep 28 09:00 /dev/mapper/vg01-root # find /dev/vg01 -ls 1861 0 drwx------ 2 root root 220 Sep 28 09:01 /dev/vg01/ 5864 0 lrwxrwxrwx 1 root root 37 Sep 28 09:01 /dev/vg01/sled10-swap -> /dev/mapper/vg01-sled10--swap 5863 0 lrwxrwxrwx 1 root root 37 Sep 28 09:01 /dev/vg01/sled10-root -> /dev/mapper/vg01-sled10--root 5862 0 lrwxrwxrwx 1 root root 29 Sep 28 09:01 /dev/vg01/swap -> /dev/mapper/vg01-swap 5861 0 lrwxrwxrwx 1 root root 29 Sep 28 09:01 /dev/vg01/bulk -> /dev/mapper/vg01-bulk 5860 0 lrwxrwxrwx 1 root root 35 Sep 28 09:01 /dev/vg01/homesecure -> /dev/mapper/vg01-homesecure 5859 0 lrwxrwxrwx 1 root root 28 Sep 28 09:01 /dev/vg01/tmp -> /dev/mapper/vg01-tmp 5858 0 lrwxrwxrwx 1 root root 28 Sep 28 09:01 /dev/vg01/var -> /dev/mapper/vg01-var 5857 0 lrwxrwxrwx 1 root root 28 Sep 28 09:01 /dev/vg01/usr -> /dev/mapper/vg01-usr 5856 0 lrwxrwxrwx 1 root root 29 Sep 28 09:01 /dev/vg01/root -> /dev/mapper/vg01-root # dmsetup ls vg01-sled10--swap (253, 8) vg01-sled10--root (253, 7) vg01-bulk (253, 5) vg01-tmp (253, 3) home (253, 9) vg01-homesecure (253, 4) vg01-usr (253, 1) vg01-var (253, 2) vg01-swap (253, 6) vg01-root (253, 0) # dmsetup table vg01-sled10--swap: 0 2097152 linear 3:3 41943424 vg01-sled10--root: 0 8388608 linear 3:3 33554816 vg01-bulk: 0 14680064 linear 3:3 52429184 vg01-bulk: 14680064 4620288 linear 3:3 71303552 vg01-tmp: 0 4194304 linear 3:3 27263360 home: 0 4192248 crypt aes-cbc-plain d1df26e0b18a70eaaef55aeef9d16d80aa9ac6787de61124a175c5c26e7aa3ef 0 253:4 2056 vg01-homesecure: 0 4194304 linear 3:3 67109248 vg01-usr: 0 10485760 linear 3:3 12583296 vg01-var: 0 4194304 linear 3:3 23069056 vg01-swap: 0 2097152 linear 3:3 31457664 vg01-root: 0 12582912 linear 3:3 384 I also noticed there are EVMS log files in /var/log (evms-engine.log), but this was not the result of any configuration I did. Apparently this was the result of the EVMS RPM install script(s). Sorry if I'm being a bit unhelpful on the EVMS front, but I still haven't done enough reading on it to know what its behavior is supposed to be. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=208417 ------- Comment #5 from fehr@novell.com 2006-09-28 03:01 MST ------- Hannes needs to look into that.
From the data you sent it seems that the node /dev/evms/lvm2/vg01/bulk which mkinitrd mis-detects as root fs does not even exist. The content of /dev/evms and dmsetup output clearly shows that EVMS is not actiavted.
As a workaround, you can simply remove packages evms and yast2-storage-evms. Nevertheless there is something pretty strange going on in mkinitrd. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=208417 hare@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED ------- Comment #6 from hare@novell.com 2006-09-28 05:32 MST ------- Cool. evms detects regions & volumes even if it's not activated. Oh well. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=208417 ------- Comment #7 from hare@novell.com 2006-09-28 06:33 MST ------- Created an attachment (id=99828) --> (https://bugzilla.novell.com/attachment.cgi?id=99828&action=view) Updated /sbin/mkinitrd Updated mkinitrd with fixed LVM2 detection. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=208417 hare@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED ------- Comment #8 from hare@novell.com 2006-09-28 06:35 MST ------- Updated mkinitrd rpm submitted to autobuild, will be included in the next 10.2 snapshot. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=208417 hare@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |NEEDINFO Info Provider| |aj@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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=208417 hare@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |moby@pcsn.net ------- Comment #10 from hare@novell.com 2006-09-28 07:27 MST ------- *** Bug 206609 has been marked as a duplicate of this bug. *** -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=208417 spam.lounge@gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|aj@novell.com | ------- Comment #11 from spam.lounge@gmail.com 2006-09-28 07:46 MST ------- Problem solved with the new mkinitrd. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=208417 hare@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO Info Provider| |aj@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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=208417 hare@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |arjen@zeilers.net ------- Comment #12 from hare@novell.com 2006-09-29 03:09 MST ------- *** Bug 208858 has been marked as a duplicate of this bug. *** -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=208417 aj@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |aj@novell.com Info Provider|aj@novell.com |kukuk@novell.com ------- Comment #13 from aj@novell.com 2006-09-29 06:29 MST ------- This should go out for SLE as well IMO. Thorsten, do you approve? If yes: Hannes , please release for both 10.1 and SLES10 (same SWAMPID, two patchfiles). -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=208417 kukuk@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|kukuk@novell.com | ------- Comment #14 from kukuk@novell.com 2006-10-02 06:03 MST ------- Yes. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=208417 ------- Comment #15 from aj@novell.com 2006-10-02 06:14 MST ------- MaintenanceTracker-6356 -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=208417 hare@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED ------- Comment #16 from hare@novell.com 2006-10-06 03:03 MST ------- rpm & patchinfo submitted for SLES10. Patchinfo submitted for 10.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, or are watching someone who is.
participants (1)
-
bugzilla_noreply＠novell.com