From mboxrd@z Thu Jan 1 00:00:00 1970 From: David T-G Subject: Re: failed disks, mapper, and "Invalid argument" Date: Thu, 21 May 2020 07:04:38 -0400 Message-ID: <20200521110438.GH1415@justpickone.org> References: <20200520200514.GE1415@justpickone.org> <5EC5BBEF.7070002@youngman.org.uk> <20200520235347.GF1415@justpickone.org> <5EC63819.5010508@youngman.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <5EC63819.5010508@youngman.org.uk> Sender: linux-raid-owner@vger.kernel.org To: Linux RAID list List-Id: linux-raid.ids 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