geninitrd fails if softraid partition (mdXpY) used as rootfs

Bug #706553 reported by qwiat
4
This bug affects 1 person
Affects Status Importance Assigned to Milestone
PLD Linux
New
Undecided
Unassigned

Bug Description

I get "ERROR: RAID devices not found for "/dev/md0p1", check your configuration!" if softraid partition (mdXpY) is used as rootfs:
------------------------------------
# geninitrd -v -f foo 2.36.2-1
geninitrd: # $Revision: 12044 $ $Date: 2011-01-13 21:20:40 +0100 (czw) $
geninitrd: Using _lib: lib64
geninitrd: Using initrd_dir: /usr/lib64/initrd
geninitrd: find_tool: found /usr/lib64/initrd/busybox
geninitrd: find_tool: did not found any of: /usr/lib64/initrd/cryptsetup /sbin/cryptsetup-initrd
geninitrd: find_tool: did not found any of: /usr/lib64/initrd/dmraid /sbin/dmraid-initrd
geninitrd: find_tool: did not found any of: /usr/lib64/initrd/lvm /sbin/initrd-lvm
geninitrd: find_tool: found /usr/lib64/initrd/mdassemble
geninitrd: find_tool: found /sbin/mdadm
geninitrd: find_tool: did not found any of: /usr/lib64/initrd/blkid /sbin/initrd-blkid
geninitrd: find_tool: did not found any of: /usr/lib64/initrd/udevd /sbin/initrd-udevd
geninitrd: find_tool: did not found any of: /usr/lib64/initrd/udevadm /sbin/initrd-udevadm
geninitrd: find_tool: did not found any of: /usr/lib64/initrd/resume /usr/lib64/suspend/resume /usr/sbin/resume
geninitrd: find_tool: did not found any of: /usr/sbin/splash_geninitramfs /usr/bin/splash_geninitramfs
geninitrd: find_tool: did not found any of: /usr/sbin/splash_geninitramfs /usr/bin/splash_geninitramfs
geninitrd: find_tool: did not found any of: /bin/splash.bin
geninitrd: find_tool: did not found any of: /usr/lib64/initrd/v86d /sbin/v86d
geninitrd: Using modprobe -c to get modules config
geninitrd: Finding SATA modules
geninitrd: Using /dev/md0p1 as device for rootfs
geninitrd: Finding modules for device path /dev/md0p1
geninitrd: Finding RAID details using mdadm for rootdev=/dev/md0p1
geninitrd: ERROR: RAID devices not found for "/dev/md0p1", check your configuration!
------------------------------------

my fstab:
------------------------------------
/dev/md0p1 / ext2 defaults 0 1
/dev/md0p2 swap swap defaults 0 0

none /proc proc defaults,noauto,gid=17 0 0
none /sys sysfs defaults,noauto,gid=17 0 0
none /proc/bus/usb usbfs defaults,noauto,devgid=78,devmode=0664 0 0
none /dev/pts devpts gid=5,mode=620 0 0
none /dev/cpuset cpuset defaults,noauto 0 0
------------------------------------

mdadm.conf
------------------------------------
#MAILADDR <email address hidden>
#PROGRAM /usr/sbin/handle-mdadm-events
ARRAY /dev/md0 metadata=0.90 UUID=9fec8181:43018b3d:776c2c25:004bd7b2
------------------------------------

mdadm output:
------------------------------------
# mdadm -v --detail --scan
ARRAY /dev/md0 level=raid5 num-devices=3 metadata=0.90 UUID=9fec8181:43018b3d:776c2c25:004bd7b2
   devices=/dev/sda1,/dev/sdb1,/dev/sdc1
------------------------------------

versions:
- geninitrd: 10000.32-1 and 10000.20-5
- arch: x86_64
- mdadm: 3.1.2
- kernel: 2.36.2-1

Tags: geninitrd
qwiat (qwiat)
description: updated
description: updated
description: updated
Revision history for this message
Arkadiusz Miśkiewicz (arekm) wrote :
Revision history for this message
qwiat (qwiat) wrote :

New mod-md.sh works fine, but there is problem with generated initrd in boot: time:

mdadm: /dev/md0p1 is not valid name for md device - ignored.
Segmentation fault

Revision history for this message
Arkadiusz Miśkiewicz (arekm) wrote :

Publish initrd somewhere or linuxrc and /etc/mdadm.conf contents from that initrd.

Revision history for this message
Arkadiusz Miśkiewicz (arekm) wrote :
Revision history for this message
qwiat (qwiat) wrote :

Initrd image is not generated

Revision history for this message
qwiat (qwiat) wrote :

the same problem with recent revision:

geninitrd: # $Revision: 12044 $ $Date: 2011-01-13 21:20:40 +0100 (czw) $
geninitrd: Using _lib: lib64
geninitrd: Using initrd_dir: /usr/lib64/initrd
geninitrd: find_tool: found /usr/lib64/initrd/busybox
geninitrd: find_tool: did not found any of: /usr/lib64/initrd/cryptsetup /sbin/cryptsetup-initrd
geninitrd: find_tool: did not found any of: /usr/lib64/initrd/dmraid /sbin/dmraid-initrd
geninitrd: find_tool: did not found any of: /usr/lib64/initrd/lvm /sbin/initrd-lvm
geninitrd: find_tool: found /usr/lib64/initrd/mdassemble
geninitrd: find_tool: found /sbin/mdadm
geninitrd: find_tool: did not found any of: /usr/lib64/initrd/blkid /sbin/initrd-blkid
geninitrd: find_tool: did not found any of: /usr/lib64/initrd/udevd /sbin/initrd-udevd
geninitrd: find_tool: did not found any of: /usr/lib64/initrd/udevadm /sbin/initrd-udevadm
geninitrd: find_tool: did not found any of: /usr/lib64/initrd/resume /usr/lib64/suspend/resume /usr/sbin/resume
geninitrd: find_tool: did not found any of: /usr/sbin/splash_geninitramfs /usr/bin/splash_geninitramfs
geninitrd: find_tool: did not found any of: /usr/sbin/splash_geninitramfs /usr/bin/splash_geninitramfs
geninitrd: find_tool: did not found any of: /bin/splash.bin
geninitrd: find_tool: did not found any of: /usr/lib64/initrd/v86d /sbin/v86d
geninitrd: Using modprobe -c to get modules config
geninitrd: Finding SATA modules
geninitrd: Using /dev/md0p1 as device for rootfs
geninitrd: Finding modules for device path /dev/md0p1
geninitrd: Finding RAID details using mdadm for rootdev=/dev/md0p1
geninitrd: ERROR: RAID devices not found for "/dev/md0p1", check your configuration!

Revision history for this message
Arkadiusz Miśkiewicz (arekm) wrote :

Are you sure that you use geninitrd and mod-md.sh from svn trunk? Here with your mdadm --scan... output works fine:

geninitrd: Finding RAID details using mdadm for rootdev=/dev/md0p1
geninitrd: md: found rootdev=/dev/md0p1 on device /dev/md0 with devices list /dev/sda1 /dev/sdb1 /dev/sdc1

Revision history for this message
Arkadiusz Miśkiewicz (arekm) wrote :

Use geninitrd-10000.32-0.2, should be in th-test soon.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.