<snip>
Using CentOS 5.2 and in the fstab, the drives are referenced via
/dev/md2, /dev/md0, etc and not via UUID. In mdadm.conf they are
referenced via UUID
The UUID should be the same, but it is worth checking the UUIDs in the
mdadm.conf against what the (live) OS is actually seeing. These are
symlinks in /dev/disk/by-uuid btw.
Now I'm confused about the UUID - when I recreate the arrays on the live
cd, I get different UUID's than what is in the mdadm.conf file when
compared to the /dev/disk/by-uuid
(I also found that blkid gives the UUID information)
If I do a mdadm --examine --scan
I get the same UUID's that are in the mdadm.conf file.
So which is correct?
If the ones under the live CD, should I change the mdadm.conf file to match?
Any suggestions on how to get this operational again (on the
new machine, I don't have access to the old any longer)? Do I
have to recreate the raid array? How?
If you can mount the arrays and read data then there is nothing wrong
with the arrays themselves. Chances are this is a grub problem. What
is the default entry in /boot/grub/menu.lst?
Not sure that it is a grub problem though -
This is the default entry
title CentOS (2.6.18-92.1.22.el5)
root (hd0,0)
kernel /vmlinuz-2.6.18-92.1.22.el5 ro root=/dev/md2 rhgb quiet
initrd /initrd-2.6.18-92.1.22.el5.img
I also recreated initrd in a chroot in case I needed different modules
on boot as per Cody's message earlier.
<snip>
I would verify the partitions with fsck. Of course they should not be
mounted when you do this.
They all check out okay
Martin
_______________________________________________
clug-talk mailing list
[email protected]
http://clug.ca/mailman/listinfo/clug-talk_clug.ca
Mailing List Guidelines (http://clug.ca/ml_guidelines.php)
**Please remove these lines when replying
