Re: failed disks, mapper, and "Invalid argument"

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

 



Wols, et al --

...and then Wols Lists said...
% 
% On 21/05/20 00:53, David T-G wrote:
% >   ## parted
% >   Model: ATA ST4000DM000-1F21 (scsi)
...
% >   SCT capabilities:              (0x1085) SCT Status supported.
% >   SMART Error Log Version: 1
% >   ## scterc
% >   SCT Error Recovery Control command not supported
% > 
% > Curiously, note that querying just scterc as the wiki instructs says "not
% > supported", but a general smartctl query says yes.  I'm not sure how to
% > interpret this...
% 
% Seagate Barracudas :-(

Yep.  They were good "back in the day" ...


% 
% As for smartctl, you're asking two different things. Firstly is SCT
% supported (yes). Secondly, is the ERC feature supported (no).
% 
% And that second question is the killer. Your drives do not support error
% recovery. Plan to replace them with ones that do ASAP!

That would be nice.  I actually have wanted for quite some time
to grow these from 4T to 8T, but budget hasn't permitted.  Got any
particularly-affordable recommendations?

This whole problem sounds familiar to me.  I thought that it was possible
to adjust the timeouts on the software side to match the longer disk time
or similar.  Of course, I didn't know that I had a real problem in the
first place ...  But does that sound familiar to anyone?


% 
...
% 
% In the meantime, make sure you're running Brad's script, and watch out
% for any hint of lengthening read/write times. That's unlikely to be why
% your overlay drives won't mount - I suspect a problem with loopback, but
% I don't know.

I most definitely also want to be able to spot trends to get ahead of
failures.  I just don't know for what to look or how to parse it to write
a script that will say "hey, this thingie here is growing, and you said
you cared ...".


% 
% What I don't want to advise, but I strongly suspect will work, is to
% force-assemble the two good drives and the nearly-good drive. Because it
% has no redundancy it won't scramble your data because it can't do a

Should I, then, get rid of the mapper overlay stuff?  I tried pointing to
even just three devs and got that they're busy.


% rebuild, but I would VERY STRONGLY suggest you download lsdrv and get
% the output. The whole point of this script is to get the information you

You mean the output that is some error and a few lines of traceback?
Yeah, I saw that, but I don't know how to fix it.  Another problem in the
queue.


% need so that if everything does go pear shaped, you can rebuild the
% metadata from first principles. It's easy - git clone, run.

... and then debug ;-)


% 
% Cheers,
% Wol


Thanks again & HAND

:-D
-- 
David T-G
See http://justpickone.org/davidtg/email/
See http://justpickone.org/davidtg/tofu.txt




[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