Bug 206609 - mkinitrd 1.2-106.18 generates incorrect initrd on system where / is on lvm
Summary: mkinitrd 1.2-106.18 generates incorrect initrd on system where / is on lvm
Status: RESOLVED DUPLICATE of bug 208417
Alias: None
Product: SUSE Linux 10.1
Classification: openSUSE
Component: Kernel (show other bugs)
Version: Final
Hardware: x86 SuSE Linux 10.1
: P3 - Medium : Critical (vote)
Target Milestone: ---
Assignee: Hannes Reinecke
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-09-18 22:31 UTC by Mobeen Azhar
Modified: 2006-09-28 13:27 UTC (History)
3 users (show)

See Also:
Found By: Customer
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mobeen Azhar 2006-09-18 22:31:20 UTC
For systems where / is on lvm, mkinitrd 1.2-106.18 generates an initrd with evms support instead of lvm, thereby rendering the system unbootable.  This version of mkinitrd and an associated kernel update were released recently and made available via automatic updates.  This can be a big problem since systems setup to automatically install critical patches will be rendered unbootable if they use / on lvm.
Comment 1 Johannes Engel 2006-09-25 10:29:49 UTC
This is not necessarily true, since I haven't got evms installed, the initrd is usable, but I get errors during creation "File descriptor 5 left open", "/dev/hda8 is no md device". So it seems to be detected as an MD device (not evms in my case), although it is lvm2.
Comment 2 Mobeen Azhar 2006-09-25 15:55:58 UTC
I did not have evms either - just lvm2.  Looking into the initrd generated on my system, I saw evms files in there instead of lvm files - hence my conclusion that mkinitrd was creating an initrd for evms systems instead of lvm even when the system only had lvm. 
In Johannes case, it seems that despite the errors, approprite lvm support was included in the initrd, since otherwise the kernel would not have booted and mounted root.
Comment 3 Johannes Engel 2006-09-26 22:39:42 UTC
Seems to be...
Here my errors on generating an initrd:

/boot # mkinitrd -k vmlinuz-2.6.16.21-0.25-engel -i initrd-2.6.16.21-0.25-engel -s 1400x1050 -M /boot/System.map-2.6.16.21-0.25-engel
/sbin/mkinitrd: line 3031: evms: command not found
File descriptor 5 left open
File descriptor 5 left open
mdadm: /dev/hda8 does not appear to be an md device
mdadm: /dev/hda8 does not appear to be an md device
mdadm: /dev/hda8 does not appear to be an md device
Root device:    /dev/system/root (mounted on / as reiserfs)
Module list:    piix 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-engel
Initrd image:   /boot/initrd-2.6.16.21-0.25-engel
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

Cannot determine dependencies of module raid0. Is modules.dep up to date?
Cannot determine dependencies of module raid1. Is modules.dep up to date?
Cannot determine dependencies of module raid5. Is modules.dep up to date?
Cannot determine dependencies of module linear. Is modules.dep up to date?
Cannot determine dependencies of module raid0. Is modules.dep up to date?
Cannot determine dependencies of module raid1. Is modules.dep up to date?
Cannot determine dependencies of module raid5. Is modules.dep up to date?
Cannot determine dependencies of module linear. Is modules.dep up to date?
Driver modules: ide-core ide-disk piix processor thermal fan dm-mod dm-snapshot
Filesystem modules:     reiserfs
Including:      initramfs dm/lvm2 fsck.reiserfs
Bootsplash:     SuSE (1400x1050)
11426 blocks

The "File descriptor 5 left open" errors result from the call of lvs in line 3039 of /sbin/mkinitrd, the following three errors from line 3049.
Comment 4 Johannes Engel 2006-09-27 11:53:32 UTC
The problem persists in mkinitrd-1.2-106.19
Comment 5 Hannes Reinecke 2006-09-28 13:27:33 UTC

*** This bug has been marked as a duplicate of bug 208417 ***