LinuxQuestions.org
LinuxAnswers - the LQ Linux tutorial section.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Server
User Name
Password
Linux - Server This forum is for the discussion of Linux Software used in a server related context.

Notices

Reply
 
Search this Thread
Old 09-09-2007, 12:54 PM   #1
raffeD
LQ Newbie
 
Registered: Sep 2007
Posts: 1

Rep: Reputation: 0
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
 
Old 08-11-2008, 11:47 AM   #2
credulou
LQ Newbie
 
Registered: Aug 2008
Posts: 1

Rep: Reputation: 0
Every get a response

RaffD Did you ever get anywhere with this problem, I have just upgraded FC5-.FC7->FC8 and have exactly the same problem.

Any ideas?
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
RAID5 using mdadm, how to mount /dev/md0? ggduff Linux - Software 4 11-14-2007 01:59 AM
mdadm: no device found for /dev/md0 doorito Linux - Server 1 04-09-2007 09:21 PM
using raid1 with mdadm to "restore" system to previous state predder Linux - Enterprise 0 08-08-2006 07:57 PM
mdadm and booting Boss Hoss Linux - Software 2 07-11-2006 09:17 PM
mdadm: no devices found for /dev/md0 humbletech99 Linux - General 2 06-19-2006 04:28 AM


All times are GMT -5. The time now is 01:48 AM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration