On Sun Aug 31, 2014 at 11:12:44am +0200, Fabio Bacigalupo wrote:
> 2014-08-29 11:10 GMT+02:00 Robin Hill <robin@xxxxxxxxxxxxxxx>:
> > You'll need to use --assemble --force in order to get the array going
> > again afterwards (as the event counts are different on the two disks).
>
> I finally got my RAID array back up and running. Thank you for your
> guidance, Robin. There is one last question. The third drive just to
> be /dev/sda3 which is now occupied by the system disk. If I add
> another disk (a new one) into system it will be /dev/sdd. What do I
> need to do to add this to the RAID array? Can it fill the unsed slot
> [_UU] or do I have to add it as a new drive to get something like this
> [_UUU] ?
>
You'll need to copy the partition info over from one of the existing
array members, then just use --add to add it into the array - it will
fill in the unused slot. md doesn't care what the kernel disk
order/naming is at all, it uses the RAID metadata to figure out which
disk goes where in the array.
Glad to hear you've got it all back up and running anyway.
Cheers,
Robin
--
___
( ' } | Robin Hill <robin@xxxxxxxxxxxxxxx> |
/ / ) | Little Jim says .... |
// !! | "He fallen in de water !!" |
Attachment:
signature.asc
Description: Digital signature
