Hi, > It simply looks like the drive designation changed /dev/sda -> /dev/sdc and > mdadm kicked sda out of the array because it wasn't there. Are you not using > UUID designation to assemble the arrays? What does your /etc/mdadm.conf look like? > > It looks like you could add /dev/sdc3 back into the array, let it rebuild if > necessary, then use: > > mdadm --detail --scan >> /etc/mdadm.conf > > To create a new UUID based mdadm.conf that would prevent this from happening again. # cat /etc/mdadm.conf # mdadm.conf written out by anaconda MAILADDR root AUTO +imsm +1.x -all ARRAY /dev/md0 level=raid1 num-devices=2 UUID=99acf2a0:afa1266c:b870423d:f06e4009 So I would then use "mdadm --add /dev/md0 /dev/sdc3" to add it, correct? It's not necessary to first fail the device? Thanks again, Alex -- To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
