Re: hung grow

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

 



On 04/10/17 19:44, Joe Landman wrote:
Generally speaking 3 failed drives on a RAID6 is a dead RAID6.  You may get lucky, in that this may have been simply a timeout error (I've seen these on consumer grade drives), or an internal operation on the drive taking longer than normal, and been booted.  In which case, you'll get scary warning messages, but might get your data back.

Under no circumstances do anything to change RAID metadata right now (grow, shrink, etc.).  Start with basic assembly.  If you can do that, you are in good shape.  If you can't, recovery is unlikely, even with heroic intervention.

No - Curt needs to stop the grow before anything else will work, I think. Fortunately, seeing as it's hung at 0% this shouldn't mess about with the data at all.

And you NEED to ddrescue that fifth drive. At which point basic assembly should hopefully work fine.

(Note that the grow quite likely failed because the fifth drive errored ... Oh - and are they raid drives? What are they? You don't have a timeout mismatch?)

Cheers,
Wol
--
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