Bug 544361 - lvm2-2.02.45-9.1.x86_64 breaks creation of initrd by mkinitrd leaving system unbootable
Summary: lvm2-2.02.45-9.1.x86_64 breaks creation of initrd by mkinitrd leaving system ...
Status: RESOLVED DUPLICATE of bug 525237
Alias: None
Product: openSUSE 11.2
Classification: openSUSE
Component: Basesystem (show other bugs)
Version: Factory
Hardware: 64bit SUSE Other
: P2 - High : Critical (vote)
Target Milestone: RC 1
Assignee: Xin Wei Hu
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-10-05 15:25 UTC by Forgotten User aFJloKvMbR
Modified: 2009-10-13 15:02 UTC (History)
3 users (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---
jplack: SHIP_STOPPER+


Attachments
create sysconfig directory prior to usage in initrd (678 bytes, patch)
2009-10-06 11:46 UTC, Joachim Plack
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Forgotten User aFJloKvMbR 2009-10-05 15:25:17 UTC
User-Agent:       Mozilla/5.0 (X11; U; Linux x86_64; fi-FI; rv:1.9.1.3) Gecko/20090909 SUSE/3.5.3-1.4 Firefox/3.5.3

I find that lvm2-2.02.45-9.1.x86_64 contains buggy script (lib/mkinitrd/scripts/setup-lvm2.sh) 
that copies /etc/sysconfig/vlm to file named $tmp_mnt/etc/sysconfig. 
It does not create directory first. 
After I added "mkdir $tmp_mnt/etc/sysconfig" before line 40: "cp -a /etc/sysconfig/lvm $tmp_mnt/etc/sysconfig" I was able to create initrd and boot.

Theres lot of mkinitrd related bugs  in tracker . Hope this is root cause for at least some of them. As following (setup-clock.sh setup-dm.sh )  mkinitrd/scripts are refering to $tmp_mnt/etc/sysconfig  those problems could be could be related to this.


Reproducible: Always

Steps to Reproduce:
1.Updated from milestone 7 to milestone8 with (zypper dup)
2. see errors on console, find that initrd is not creted.tried to run mkinitrd by hand
3. edited ib/mkinitrd/scripts/setup-lvm2.sh
4. run mkinitrd
Comment 1 Joachim Plack 2009-10-06 11:46:08 UTC
Created attachment 321240 [details]
create sysconfig directory prior to usage in initrd
Comment 2 Joachim Plack 2009-10-06 11:47:57 UTC
This is most likely a duplicate of #525237
which happened in milestone 4!
Find patch that fixes the problem attached (as shown above)
This need to be fixed before RC1
Comment 3 Rodolfo Boer 2009-10-11 12:49:46 UTC
(In reply to comment #2)
> This is most likely a duplicate of #525237
> which happened in milestone 4!

I dont't think it's related to that bug.

I've got this problem as well with root on a luks encrypted partition, no raid. I solved it just as the reporter did.

setup-clock.sh and setup-dm.sh do a mkdir -p before writing the config. The lvm script does not and when it cats its config to $tmp_mnt/etc/sysconfig, if it hasn't already been created as a directory by an early script, sysconfig gets created as a file.

This makes later script fail and the ramdisk is not created, making the system unbootable.
Comment 4 Stephan Kulow 2009-10-13 15:02:43 UTC
It's still the same bug I think

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