From: David T-G <davidtg-robot@justpickone.org>
To: Linux RAID list <linux-raid@vger.kernel.org>
Subject: Re: assemble didn't quite
Date: Thu, 14 Sep 2023 15:59:59 +0000 [thread overview]
Message-ID: <20230914155959.GI1085@jpo> (raw)
In-Reply-To: <20230910031155.GE1085@jpo>
Hi again, all --
...and then David T-G home said...
% ...and then David T-G home said...
% %
% % ...and then Wol said...
% %
% ...
% % % I wonder if a controlled reboot would fix it. Or just do a --stop followed
% %
% % I've tried a couple of reboots; they're stuck that way. I'll try the
% % stop and assemble.
% [snip]
%
% Stopping was easy:
...
%
% Restarting wasn't as impressive:
%
% diskfarm:~ # for A in 51 52 53 54 55 56 ; do mdadm --assemble /dev/md$A /dev/sd[dcblfk]$A ; done
% mdadm: /dev/md51 assembled from 3 drives - not enough to start the array.
...
% diskfarm:~ # grep md51 /proc/mdstat
% md51 : inactive sdk51[6](S) sdl51[4](S) sdf51[5](S) sdc51[1](S) sdd51[3](S) sdb51[0](S)
%
% Still all spares. And here I was hoping this would be easy ...
In the end, after a few more tries,
--stop /dev/mdNN
--assemble --force /dev/mdNN /dev/sd{d,c,b,l,f,k}NN
worked, at which point md50 the linear array happily lit itself up. So
far, all seems good. Yay!
Now about the size ...
Thanks again & HAND
:-D
--
David T-G
See http://justpickone.org/davidtg/email/
See http://justpickone.org/davidtg/tofu.txt
next prev parent reply other threads:[~2023-09-14 16:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-08 2:50 all of my drives are spares David T-G
2023-09-09 11:26 ` David T-G
2023-09-09 18:28 ` Wol
2023-09-10 2:55 ` David T-G
2023-09-10 3:11 ` assemble didn't quite (was "Re: all of my drives are spares") David T-G
2023-09-14 15:59 ` David T-G [this message]
2023-09-10 3:44 ` timing " David T-G
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230914155959.GI1085@jpo \
--to=davidtg-robot@justpickone.org \
--cc=linux-raid@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).