|
mdadm says "mdadm: /dev/md1 not identified in config file" when booting FC7
Hi all!
I have problems booting up my box after an upgrade attempt FC6 -> FC7 x86_64.
When booting up the system I get past Grub.
<snippet>
root (hd0,0)
Filesystem type is ext2fs, partition type 0xfd
kernel /vmlinuz-2.6.21-1.3194.fc7 ro root=/dev/VolGroup00/LogVol01 rhgb quiet
{Linux-bzImage, setup=0x1e00, size=0x1ce763]
initrd /initrd-2.6.21-1.3194.fc7.img
[Linux-initrd @ 0x37c1d000, 0x3d2111 bytes]
.
Decompressing Linux...done
Booting the kernel.
Red Hat nash version 6.0.9 starting
mdadm: /dev/md1 not identified in config file.
Reading all physical volumes. This may take a while...
No volume groups found.
Volume group "VolGroup00" not found
Unable to access resume device (dev/VolGroup00/LogVol00)
mount: could not find filesystem '/dev/root'
setuproot: moving /dev failed: No such file or directory
setuproot: error mounting /proc: No such file or directory
setuproot: error mounting /sys: No such file or directory
switchroot: mount failed: No such file or directory
Kernel panic - not syncing: Attempted to kill init!
</snippet>
When booting up the system with FC7 rescue disc, I manage to mount /dev/VolGroup00/Logvol01 as /mnt/sysimage without any problems.
mdadm --detail for my arrays gives me:
<snippet>
mdadm --detail /dev/md0
/dev/md0:
Version : 00.90.03
Creation Time : Sun Aug 20 19:35:59 2006
Raid Level : raid1
Array Size : 513984 (502.02 MiB 526.32 MB)
Used Dev Size : 513984 (502.02 MiB 526.32 MB)
Raid Devices : 2
Total Devices : 2
Preferred Minor : 0
Persistence : Superblock is persistent
Update Time : Sun Sep 9 17:34:54 2007
State : clean
Active Devices : 2
Working Devices : 2
Failed Devices : 0
Spare Devices : 0
UUID : 59e51400:e3912e0b:30aaf9db:450a3e09
Events : 0.170
Number Major Minor RaidDevice State
0 8 33 0 active sync /dev/sdc1
1 8 49 1 active sync /dev/sdd1
mdadm --detail /dev/md0
/dev/md1:
Version : 00.90.03
Creation Time : Sun Aug 20 19:32:21 2006
Raid Level : raid1
Array Size : 312054528 (297.60 GiB 319.54 GB)
Used Dev Size : 312054528 (297.60 GiB 319.54 GB)
Raid Devices : 2
Total Devices : 2
Preferred Minor : 1
Persistence : Superblock is persistent
Update Time : Sun Sep 9 17:37:45 2007
State : clean
Active Devices : 2
Working Devices : 2
Failed Devices : 0
Spare Devices : 0
UUID : 08f4a2c8:43a6b7e0:ac116da5:e96d74cb
Events : 0.3130016
Number Major Minor RaidDevice State
0 8 34 0 active sync /dev/sdc2
1 8 50 1 active sync /dev/sdd2
mdadm --detail /dev/md2
/dev/md2:
Version : 00.90.03
Creation Time : Tue Jul 31 22:50:21 2007
Raid Level : raid1
Array Size : 120623936 (115.04 GiB 123.52 GB)
Used Dev Size : 120623936 (115.04 GiB 123.52 GB)
Raid Devices : 2
Total Devices : 2
Preferred Minor : 2
Persistence : Superblock is persistent
Update Time : Sun Sep 9 16:29:17 2007
State : clean
Active Devices : 2
Working Devices : 2
Failed Devices : 0
Spare Devices : 0
UUID : 410178e0:7005206d:72b79694:848d86f6
Events : 0.4
Number Major Minor RaidDevice State
0 8 1 0 active sync /dev/sda1
1 8 17 1 active sync /dev/sdb1
</snippet>
My /etc/mdadm.conf looks like
<snippet>
DEVICE /dev/sd[a-z]*
ARRAY /dev/md0 level=raid1 num-devices=2 UUID=59e51400:e3912e0b:30aaf9db:450a3e09
ARRAY /dev/md2 level=raid1 num-devices=2 UUID=410178e0:7005206d:72b79694:848d86f6
ARRAY /dev/md1 level=raid1 num-devices=2 UUID=08f4a2c8:43a6b7e0:ac116da5:e96d74cb
</snippet>
As far as I see it the md arrays are doing fine and I have them specified in /etc/mdadm.conf?
Anyone out there that have an idea about the cause and resolution for my problem? I don't really know where to start... grub, mdadm, lvm?
Thnks in advance
Raffe
|
