Re: array went wonky

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 05/03/2013 02:47 AM, Gimpbully wrote:
> Anyone?  I'm so close I can taste it.  It looks like the superblocks
> on the other disks think that sdf1 is still defined as a spare, but
> it's a ddrescue of what used to be /dev/sdc.  Is there a way to
> update the superblocks?

Sorry, been busy.

Unfortunately, once a member is marked "spare", it simply doesn't know
any more what role it used to have.  So "--assemble" won't get you there.

You will need to use "--create --assume-clean" or directly edit the
offending superblock.

> *Complete* output of "mdadm -E" for the array members is needed before
> any "--create" operation is attempted.  Plus the distro info, kernel
> version, and mdadm version .

I would also like to see "smartctl -x" output for each underlying disk.
 It would be good if we understood *why* your array "went wonky" so that
it doesn't happen again after reassembling your array.  Your situation
"smells" like a timeout mismatch and/or lack of scrubbing.

Finally, in the interest of helping others help you, please don't
top-post, and *do* trim your quotes.  It greatly helps when coming back
to a thread after a few days.

Phil
--
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




[Index of Archives]     [Linux RAID Wiki]     [ATA RAID]     [Linux SCSI Target Infrastructure]     [Linux Block]     [Linux IDE]     [Linux SCSI]     [Linux Hams]     [Device Mapper]     [Device Mapper Cryptographics]     [Kernel]     [Linux Admin]     [Linux Net]     [GFS]     [RPM]     [git]     [Yosemite Forum]


  Powered by Linux