Re: (R) in mdstat output, clean && degraded

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

 



On 06/23/2015 05:21 PM, Jared Mauch wrote:
> Let me know what debugging/details might be interesting to collect.  

A good sequence of events (from bash history perhaps) with corresponding
log messages is always helpful.  Your initial report was pretty good.

> Based on the Events# being in-sync, I am going to assume that the drives
> may be operating in a protected-type mode even if the output doesn’t
> concur.

I think that's unlikely.  In replace, one drive responds for sectors
below the progress mark, and the other drive responds for sectors above it.

> I can say this state seems to survive reboots.

That suggests you give a vanilla (or near-vanilla) kernel a try with one
of the various liveCDs that have them.  I personally find the one from
sysrescuecd.org to be most convenient, but I'm a gentoo guy :-)

Otherwise, consider adding a third drive to see if it will rebuild and
break the deadlock.

I should have to say, but I hope you have a backup :-)

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