On 3/17/2010 10:52 AM, Patrick Ale wrote: > Hi, > > I have an interesting challenge, maybe one of you can help me :-) > > I am creating an MD RAID 1 array consisting out of two SATA disks > (currently /dev/sdb1 and /dev/sdc1). > Both partitions use the Sun disk label and the partitions used start > on cylinder 1. > > Device Flag Start End Blocks Id System > /dev/sdb1 1 60788 488271577+ fd Linux raid autodetect > > Device Flag Start End Blocks Id System > /dev/sdc1 1 60788 488271577+ fd Linux raid autodetect > > > When I run the mdadm command to construct the array (mdadm --create > /dev/md0 --level=1 --raid-devices=2 --run /dev/sdb1 /dev/sdc1) all > goes fine, the array syncs up and all. > > However, when you do a blkid -c /dev/null you'll see that both > /dev/sdb1 and /dev/sdc1 both share the same UUID. > > /dev/sdb1: UUID="978635d6-52ab-c92b-76ea-5a12e49bd4b5" TYPE="linux_raid_member" > /dev/sdc1: UUID="978635d6-52ab-c92b-76ea-5a12e49bd4b5" TYPE="linux_raid_member" I had an interesting problem at some point in time with this setup where silo and raid were not playing nicely together. As workaround I used to add an empty partition at the beginning of the disk (the smallest size as possible - basically just a padding partition) on both RAID-1 disks and start using the disk for real from sdX2. I have no clue if that problem has been addressed or not, but my suggestion would be to check if you experience any kind of FS corruption for files stored at the beginning of the raid disk before and after asking silo to install/update the MBR. Cheers Fabio _______________________________________________ sparc mailing list sparc@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/sparc
