On Friday, 02 March 2012 18:21:17 +0100, tv.debian@googlemail.com wrote: > >> Can you tell us what kind of raid and metadata we are talking about. > > This is the detail of the root device: > > > > # mdadm --detail /dev/md2 > > /dev/md2: > > Version : 00.90 > > Creation Time : Wed Sep 6 11:27:09 2006 > > Raid Level : raid1 > > Array Size : 19534976 (18.63 GiB 20.00 GB) > > Used Dev Size : 19534976 (18.63 GiB 20.00 GB) > > Raid Devices : 2 > > Total Devices : 1 > > Preferred Minor : 2 > > Persistence : Superblock is persistent > > > > Update Time : Fri Mar 2 11:41:16 2012 > > State : clean, degraded > > Active Devices : 1 > > Working Devices : 1 > > Failed Devices : 0 > > Spare Devices : 0 > > > > UUID : da5a0c19:c38ccc6d:325196eb:eb163021 > > Events : 0.5276104 > > > > Number Major Minor RaidDevice State > > 0 0 0 0 removed > > 1 8 3 1 active sync /dev/sda3 > > > > The /etc/mdadm/mdadm.conf used metadata=00.90. I changed it to 0.90, if > > this may cause some inconvenience (metadata format 00.90 unknown, > > ignored). But I don't think the problem is this because > > 2.6.32-bpo.5-amd64 boots without problems and my compiled kernel is > > based on config-2.6.32-bpo.5-amd64; I only patch the kernel with support > > of IMQ and Layer7. > > > > This is the output with default kernel options: > > > > Gave up waiting for root device. Common problems: > > - Boot args (cat /proc/cmdline) > > - Check rootdelay= (did the system wait long enought?) > > - Check root= (did the system wait for the right revice?) > > - Missing modules (cat /proc/mdoules: Is /dev) > > ALERT! /dev/md2 does not exist. Dropping to a shell! > > > > And using rootdelay=120: > > > > Success: loaded module raid1. > > done > > Begin: Assembling all MD arrays... mdadm: metadata format 00.90 unknown ignored. > > mdadm: metada format 00.90 unknown, ignored > > mdadm: metada format 00.90 unknown, ignored > > mdadm: metada format 00.90 unknown, ignored > > mdadm: metada format 00.90 unknown, ignored > > mdadm: No devices listed in conf file were found > > Failure: failed to assamble all arrays. > > done. > > Begin: Waiting for udev to process events ... done > > done > > Begin: waiting for root filesystem ... done > > Gave up waiting for root device. Common problems: > > - Boot args (cat /proc/cmdline) > > - Check rootdelay= (did the system wait long enought?) > > - Check root= (did the system wait for the right revice?) > > - Missing modules (cat /proc/mdoules: Is /dev) > > ALERT! /dev/md2 does not exist. Dropping to a shell! > metadata=0.90 in mdadm.conf is fine. The "00.90" problem looks like this > old problem described in bug #606389, it's supposed to be fixed in > Squeeze mdadm... Anyway, correcting to 0.90 in mdadm.conf should do the > trick. > > This "mdadm: No devices listed in conf file were found" might suggest > that the mdadm.conf file isn't up to date ? Try populating it and > rebuilding the initrd. If it is up to date, then it's likely not picked > up by the initramfs. > Look for "mdadm" scripts under /etc/initramfs-tools/$(hooks|scripts). Doing a test on 2.6.32-bpo.5-amd64, the /etc/mdadm/mdadm.conf seems to be consistent: # cat /etc/mdadm/mdadm.conf ARRAY /dev/md0 level=raid1 num-devices=2 metadata=0.90 UUID=e94e767e:1183e8a6:67791052:2affdb87 ARRAY /dev/md1 level=raid1 num-devices=2 metadata=0.90 UUID=0492f0eb:9f649719:24a66d4c:4b61d9a6 ARRAY /dev/md2 level=raid1 num-devices=2 metadata=0.90 UUID=da5a0c19:c38ccc6d:325196eb:eb163021 ARRAY /dev/md3 level=raid1 num-devices=2 metadata=0.90 UUID=552e20c1:b4272c8d:b7f9e5fe:737c9276 ARRAY /dev/md5 level=raid1 num-devices=2 metadata=0.90 UUID=80619797:1712d4dd:64a19d1d:8273eab2 # mdadm --detail --scan ARRAY /dev/md0 level=raid1 num-devices=2 metadata=00.90 UUID=e94e767e:1183e8a6:67791052:2affdb87 ARRAY /dev/md1 level=raid1 num-devices=2 metadata=00.90 UUID=0492f0eb:9f649719:24a66d4c:4b61d9a6 ARRAY /dev/md2 level=raid1 num-devices=2 metadata=00.90 UUID=da5a0c19:c38ccc6d:325196eb:eb163021 ARRAY /dev/md3 level=raid1 num-devices=2 metadata=00.90 UUID=552e20c1:b4272c8d:b7f9e5fe:737c9276 ARRAY /dev/md5 level=raid1 num-devices=2 metadata=00.90 UUID=80619797:1712d4dd:64a19d1d:8273eab2 In any case, given that 2.6.32-bpo.5-amd64 boots without problems with same configuration and mdadm metadata, I am inclined to think that the problem is some of the kernel. Maybe inirtd... > Are you using kernel-package "make-kpkg" or the "make deb-pkg" target to > build your kernel packages ? The former requires a bit of manual > configuration to work properly. I'm using make-kpkg: # cp /boot/config-`uname -r` .config # make menuconfig # make-kpkg --initrd --append_to_version=-layer7-imq-amd64 linux-image Thanks for your reply. Regards, Daniel -- Fingerprint: BFB3 08D6 B4D1 31B2 72B9 29CE 6696 BF1B 14E6 1D37 Powered by Debian GNU/Linux Lenny - Linux user #188.598
Attachment:
signature.asc
Description: Digital signature