Hi Kaizaad,
Your instruction below is the solution to my software RAID problem I made the
changes to mdadm.conf in initrd and it works like a charm.
Thank you for helping me save my sanity.
Tom
----- Original Message ----
From: Kaizaad Bilimorya <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Cc: sisuite-users@lists.sourceforge.net
Sent: Thursday, July 17, 2008 7:14:12 PM
Subject: Re: [sisuite-users] SI software RAID Fedora 9 help
On Thu, 17 Jul 2008, Tom Luong wrote:
> Hi,
>
> I decided to upgrade both server and client to be on the same version SI
> 4.0.2. I have 2 golden clients which I took images of. One image on
> software RAID1 and the other using a 3ware RAID controller. Both are
> Fedora 9 clients. I also created a new initrd which has included RAID1,
> RAID10, RAID456, and 3w-9xxx modules. I was successful at imaging a
> client with the 3ware RAID controller. However, I still get the same
> error message "mdadm: no devices found for /dev/md1" and "mount: error
> mounting /dev/root as /sysroot as ext3: Invalid argument."
>
> I am suspecting missing modules during in the initrd. I'm baffled as to
> why the same initrd from the golden client didn't work. Also, I am
> clueless as to why the new initrd(mentioned above) didn't work either.
>
> Anyone have any thoughts on this?
>
> Many thanks,
> Tom
Hi Tom,
I don't know if this will help but I think I was getting the same error
after I updated my GC (using software RAID 1) from Fedora 6 to Fedora 8
and then tried to image identical machines:
mdadm: no devices found for /dev/md2
mdadm: no devices found for /dev/md1
I noticed in my old image (FC6) that the mdadm.conf file was assembling
the RAID devices using UUID numbers. For some reason this worked
eventhough they didn't match the device UUIDs on the newly imaged machine.
I think that something got fixed in the newer version of mdadm that comes
with FC8.
So, what I ended up doing was making sure my GC had a mdadm.conf that
referred to the partitions by device instead of UUID:
- old /etc/mdadm.conf file on GC
DEVICE partitions
MAILADDR root
ARRAY /dev/md2 level=raid1 num-devices=2
uuid=bf4cf5e0:af594541:ba1437df:19ee030e
ARRAY /dev/md0 level=raid1 num-devices=2
uuid=6dd8e520:d1372e02:f4fd3fc6:3e00075b
ARRAY /dev/md1 level=raid1 num-devices=2
uuid=f2d823af:23552e7d:5132bc1a:388d7c54
- new FC8 /etc/mdadm.conf file on GC
DEVICE /dev/sda1 /dev/sdb1 /dev/sda2 /dev/sdb2 /dev/sda3 /dev/sdb3
MAILADDR root
ARRAY /dev/md0 level=raid1 num-devices=2 devices=/dev/sda1,/dev/sdb1
ARRAY /dev/md1 level=raid1 num-devices=2 devices=/dev/sda2,/dev/sdb2
ARRAY /dev/md2 level=raid1 num-devices=2 devices=/dev/sda3,/dev/sdb3
After updating the kernel (yum update) I also made sure that the
/boot/initrd-currently_running.img file that is created when a new kernel
is installed has a copy of the new /etc/mdadm.conf file in it:
mkdir /tmp/initrd
cd /tmp/initrd
cp -ip /boot/initrd-currently_running.img .
gunzip -c initrd-currently_running.img |cpio -idmv
cat etc/mdadm.conf
DEVICE /dev/sda1 /dev/sdb1 /dev/sda2 /dev/sdb2 /dev/sda3 /dev/sdb3
MAILADDR root
ARRAY /dev/md0 level=raid1 num-devices=2 devices=/dev/sda1,/dev/sdb1
ARRAY /dev/md1 level=raid1 num-devices=2 devices=/dev/sda2,/dev/sdb2
ARRAY /dev/md2 level=raid1 num-devices=2 devices=/dev/sda3,/dev/sdb3
I then used the standard systemimager si_* procedure and imaged the boxes.
When they booted the raid devices were assembled np.
Hope this helps
-k-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
sisuite-users mailing list
sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users
