Thread (24 messages) 24 messages, 4 authors, 2020-05-21

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

From: David T-G <hidden>
Date: 2020-05-21 11:04:38

Wol, et al --

...and then Wols Lists said...
% 
% On 21/05/20 00:53, David T-G wrote:
% >   diskfarm:root:13:/mnt/scratch/disks> mdadm --assemble --force /dev/md0 --verbose /dev/sda1 /dev/sdb1 /dev/sdc1
% >   mdadm: looking for devices for /dev/md0
% >   mdadm: /dev/sda1 is busy - skipping
% >   mdadm: /dev/sdb1 is busy - skipping
% >   mdadm: /dev/sdc1 is busy - skipping
% > 
% > like the overlay is keeping me from the raw devices, so I'd have to tear
% > down all of that to try the real thing.  I'll h old off on that...
% 
% Did you do an mdadm --stop before trying the force assemble? That
% implies to me you've got the remnants of a previous attempt lying around...

Yes, I did.  md0 doesn't exist at all on the system at the moment.


% 
% Not sure which command it is - "cat /proc/mdstat" maybe, but make sure
% ALL your arrays are stopped (unless you know they are running okay)
% before you try stuff.

The mish-mash array (md127, and no I don't understand how these things
are named!) is fine.  The problem array (md0) is on exactly those four
disks (now sda, sdb, sdc, sdd).


% 
% Cheers,
% Wol


Thanks again & HAND

:-D
-- 
David T-G
See http://justpickone.org/davidtg/email/
See http://justpickone.org/davidtg/tofu.txt
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help