On Mon Jul 25, 2011 at 03:04:34PM -0600, Matthew Tice wrote:
> Well things are a lot different now - I'm unable to start the array
> successfully. I removed an older non-relevant drive that was giving
> me smart errors - when I rebooted the drive assignments shifted (not
> sure this really matters, though).
>
> Now when I try to start the array I get:
>
> # mdadm -A -f /dev/md0
> mdadm: no devices found for /dev/md0
>
> I can nudge it slightly with auto-detect:
>
> # mdadm --auto-detect
>
> Then I try to assemble the array with:
>
> # mdadm -A -f /dev/md0 /dev/sd[bcde]
> mdadm: cannot open device /dev/sde: Device or resource busy
> mdadm: /dev/sde has no superblock - assembly aborted
>
<- SNIP ->
> │ └─sde: [8:64] MD raid5 (none/4) 931.51g md_d0 inactive spare
<- SNIP ->
>
> I've looked but I'm unable to find where the drive is in use.
lsdrv shows that it's in use in array md_d0 - presumably this is a
part-assembled array (possibly auto-assembled by the kernel). Try
stopping that first, then doing the "mdadm -A -f /dev/md0 /dev/sd[bcde]"
Cheers,
Robin
--
___
( ' } | Robin Hill <robin@xxxxxxxxxxxxxxx> |
/ / ) | Little Jim says .... |
// !! | "He fallen in de water !!" |
Attachment:
pgpSh_1R0Guo3.pgp
Description: PGP signature
