Bug 540522

Summary:	Unable to install initrd creation consistently fails.
Product:	[openSUSE] openSUSE 11.2	Reporter:	Ray Sutton <blackhole999>
Component:	Bootloader	Assignee:	Milan Vančura <mvancura>
Status:	RESOLVED DUPLICATE	QA Contact:	Jiri Srain <jsrain>
Severity:	Critical
Priority:	P5 - None	CC:	forgotten_aFJloKvMbR, forgotten_gRveQ1K55E
Version:	Milestone 7
Target Milestone:	---
Hardware:	x86-64
OS:	SUSE Other
Whiteboard:
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Ray Sutton 2009-09-19 20:02:55 UTC

User-Agent:       Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.1.3) Gecko/20090824 Firefox/3.5.3

System is core I7 12G mem 500GB disk in software raid 1 + LVM configuration
partition /dev/md0 = /boot /dev/sys/dom0 = /  (LVM on top of raid 1 on /dev/md1)
/dev/sys/dom0swap = swap. disks formatted ext3 grub installed to MBR

fails in creating initrd with 2 errors, firstly missing scsi_id.config fixed by creating file from shell. Second error

Device md1 not handled
Script /lib/mkinitrd/setup/72-block.sh failed.

had initially tried ext4 for both, in this case md0 was not handled, assumed grub was having issues with ext4 switched boot to ext3 retried same result but with md1 not handled, tried both as ext3 same error.

attempting to create initrd from shell fails in same way. 

Although this was a clean install with all partitions formatted system previously held 11.1 with hd0/hd1 MBR both configured with grub booting the same boot partition so its not clear if the boot loader was overwritten.  

Disk are bios configured in AHCI mode.

Reproducible: Always

Steps to Reproduce:
1.
2.
3.
Actual Results:  
Install fails resulting system not bootable.

Expected Results:  
A functioning OS

Comment 1 Forgotten User gRveQ1K55E 2009-09-29 13:08:44 UTC

Have a look here: Bug 505670

Comment 2 Ray Sutton 2009-09-29 19:08:30 UTC

At work so I'll try the LVM resolution there tonight or at the weekend, however on first glance I'm not sure it the same problem, as far as I can tell tracing the startup the LVM2 configuration & udev occur before the md setup. In my case I have LVM2 on top of raid1 the problem would appear to be that the device /dev/md1 is not available during LVM2 setup and the PV/VG/LV for root is therefore not visible. I'll update once I've had a chance to try the 505670 resolution

Comment 3 Forgotten User aFJloKvMbR 2009-10-05 15:18:46 UTC

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"

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.

Comment 4 Forgotten User aFJloKvMbR 2009-10-05 15:30:50 UTC

Correction ...After I added 
"mkdir $tmp_mnt/etc/sysconfig" 
before line 40: "cp -a /etc/sysconfig/lvm
$tmp_mnt/etc/sysconfig" I could create initrd and boot.

Comment 5 Stephan Kulow 2009-10-12 08:11:19 UTC

let's put it all in one

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