Check your /etc/default/grub, if you use raid 1.

Sam Varshavchik mrsam at courier-mta.com
Sun Jul 29 15:25:06 UTC 2012


Reindl Harald writes:

>
>
> Am 29.07.2012 16:42, schrieb Sam Varshavchik:
> > And, fail/remove/add did not resync the drive. Because the volume uses an  
> internal bitmap: oh, the newly-added
> > drive has a valid bitmap, apparently from the same volume, so let's add  
> this drive without resyncing it!
> >
> > That, I think is a bug. Failing a drive should zero its superblock, to  
> force a real resync if it gets added back to
> > the array.
>
> no, no and no!
> if you have some mechanic problems that could end in zero the superblocks of  
> all disks
>
> in my last tests with a RAID1 i pulled the power from one SATA disk
> and after reboot i was not able to re-add the drive before manually
> zero the superblock which is the right behavior

I'm talking about a manual --fail with mdadm.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: not available
URL: <http://lists.fedoraproject.org/pipermail/users/attachments/20120729/0315615f/attachment.sig>


More information about the users mailing list