Re: help requested for mdadm grow error

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

 



On 25/05/20 20:05, Thomas Grawert wrote:
> The EFAX had me worried a moment, but these are 12TB Reds? That's fine.
>> A lot of the smaller drives are now shingled, ie not fit for purpose!
>>
>> Debian 10 - I don't know my Debians - how up to date is that? Is it a
>> new kernel with not much backports, or an old kernel full of backports?
>>
>> What version of mdadm?
>>
>>
>> That said, everything looks good. There are known problems - WITH FIXES
>> - growing a raid 5 so I suspect you've fallen foul of one. I'd sort out
>> a rescue disk that you can boot off as you might need it. Once we know a
>> bit more the fix is almost certainly a rescue disk and resume the
>> reshape, or a revert-reshape and then reshaping from a rescue disk. At
>> which point, you'll get your array back with everything intact.
> 
> yes, that´s the 12TB WD-Red - I´m using five pieces of it.
> 
> The Debian 10 is the most recent one. Kernel version is 4.9.0-12-amd64.
> mdadm-version is v3.4 from 28th Jan 2016 - seems to be the latest,
> because I can´t upgrade to any newer one using apt upgrade.

OW! OW! OW!

The newest mdadm is 4.1 or 4.2. UPGRADE NOW. Just download and build it
from the master repository - the instructions are in the wiki.

And if Debian 10 is the latest, kernel 4.9 will be a
franken-patched-to-hell-kernel ... I believe the latest kernel is 5.6?
> 
> I don´t think I need a rescue disk, because the raid isn´t bootable.
> It´s simply a big storage.
> 
Okay, the latest mdadm *might* fix your problem. However, you probably
need a proper up-to-date kernel as well, so you DO need a rescue disk.
Unless Debian has the option of upgrading the kernel to a 5.x series
kernel which hopefully isn't patched to hell and back?

This looks like the classic "I'm running ubuntu with a franken-kernel
and raid administration no longer works" problem.

I'm guessing (an educated "probably right" guess) that your reshape has
hung at 0% complete. So the fix is to get your rescue disk, use the
latest mdadm to do a revert-reshape, then use the latest kernel and
mdadm to do the reshape, before booting back in to your old Debian and
carrying as if nothing had happened.

Cheers,
Wol




[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