All of lore.kernel.org
 help / color / mirror / Atom feed
From: David T-G <davidtg-robot@justpickone.org>
To: Linux RAID list <linux-raid@vger.kernel.org>
Subject: assemble didn't quite (was "Re: all of my drives are spares")
Date: Sun, 10 Sep 2023 03:11:55 +0000	[thread overview]
Message-ID: <20230910031155.GE1085@jpo> (raw)
In-Reply-To: <20230910025554.GD1085@jpo>

...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:

  diskfarm:~ # for A in 51 52 53 54 55 56 ; do mdadm --stop /dev/md$A ;
  done
  mdadm: stopped /dev/md51
  mdadm: stopped /dev/md52
  mdadm: stopped /dev/md53
  mdadm: stopped /dev/md54
  mdadm: stopped /dev/md55
  mdadm: stopped /dev/md56

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.
  mdadm: /dev/md52 assembled from 3 drives - not enough to start the array.
  mdadm: /dev/md53 assembled from 3 drives - not enough to start the array.
  mdadm: /dev/md54 assembled from 3 drives - not enough to start the array.
  mdadm: /dev/md55 assembled from 3 drives - not enough to start the array.
  mdadm: /dev/md56 assembled from 3 drives - not enough to start the array.

  diskfarm:~ # mdadm --detail /dev/md51
  /dev/md51:
	     Version : 1.2
	  Raid Level : raid5
       Total Devices : 6
	 Persistence : Superblock is persistent
  
	       State : inactive
     Working Devices : 6
  
		Name : diskfarm:51  (local to host diskfarm)
		UUID : 9330e44f:35baf039:7e971a8e:da983e31
	      Events : 46655
  
      Number   Major   Minor   RaidDevice
  
	 -     259       39        -        /dev/sdl51
	 -     259        9        -        /dev/sdb51
	 -     259       31        -        /dev/sdk51
	 -     259       16        -        /dev/sdd51
	 -     259        2        -        /dev/sdc51
	 -     259       23        -        /dev/sdf51
  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 ...


Thanks again

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


  reply	other threads:[~2023-09-10  3:12 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       ` David T-G [this message]
2023-09-14 15:59         ` assemble didn't quite David T-G
2023-09-10  3:44       ` timing (was "Re: all of my drives are spares") 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=20230910031155.GE1085@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.