On Tue, 21 Aug 2012 11:17:57 +0000 "Vanhorn, Mike" <michael.vanhorn@xxxxxxxxxx> wrote: > Thank you for your response. Here is the output you requested. > > >What is the result of: > > > > mdadm -S /dev/md0 > > # mdadm -S /dev/md0 > mdadm: stopped /dev/md0 > # > > > mdadm -Avvv /dev/md0 > > # mdadm -Avvv /dev/md0 > mdadm: looking for devices for /dev/md0 > mdadm: cannot open device /dev/sdi1: Device or resource busy > mdadm: /dev/sdi1 has no superblock - assembly aborted > # So /dev/sdi1 is busy. You need to find out why. (the "no superblock" message is a bit misleading... I might have fixed that in newer mdadm, I'm not sure). The "/proc/mdstat" that you showed in the original email had sdi1 as a member of md0, so it clearly wasn't being used by anything else then. "mdadm -S /dev/md0" would have removed it from md0 so it shouldn't have been busy. The fact that it is busy is very odd. A device can be busy if: - it is mounted as a filesystem - it is active as swap - it is part of an md array - it is part of a dm device - probably something else, but those are the main ones. NeilBrown
Attachment:
signature.asc
Description: PGP signature
