From: Phil Turmel <philip@turmel.org>
To: Dylan Distasio <interzone@gmail.com>, linux-raid@vger.kernel.org
Subject: Re: Looking for some advice on best way to identify drives / recover from issues
Date: Sun, 05 Jan 2014 13:34:35 -0500 [thread overview]
Message-ID: <52C9A5BB.4090803@turmel.org> (raw)
In-Reply-To: <CAJrqPH9FNtomPygu1XPm2VQpJg3MKX1zUPCt0AOnzQ4GO7YEEQ@mail.gmail.com>
Good afternoon Dylan,
On 01/05/2014 10:04 AM, Dylan Distasio wrote:
> Hi all-
[trim /]
> Unfortunately, I did not take the time to physically label the drives
> in the box (there are close to 20) as I built these, and had been
> meaning to, but life got in the way. Since I have had no issues with
> these arrays in a very long time, I don't even remember if I split
> them across controllers or what.
[trim /]
> Will that give me enough info to figure out which drive belongs to
> which array? Does anyone have any other suggestions? I am not sure
> of the current state of ANY of the arrays that were on this box, but I
> don't want to make things worse by booting this system up with some
> drives missing because I've unplugged them, and having the a bad
> situation get worse.
I created a script for precisely this type of documentation task, keyed
to drive serial numbers and UUIDs wherever identifiable.
https://github.com/pturmel/lsdrv
(If any of your drive serial numbers are entirely numeric, you'll want
the patch shown in the open issues)
HTH,
Phil
next prev parent reply other threads:[~2014-01-05 18:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-05 15:04 Looking for some advice on best way to identify drives / recover from issues Dylan Distasio
2014-01-05 15:44 ` Mark Knecht
2014-01-05 17:01 ` Dylan Distasio
2014-01-05 18:05 ` Mark Knecht
2014-01-05 16:33 ` Roger Heflin
2014-01-05 17:06 ` Dylan Distasio
2014-01-05 19:37 ` Krzysztof Adamski
2014-01-22 17:16 ` Dylan Distasio
2014-01-05 18:34 ` Phil Turmel [this message]
2014-01-06 15:57 ` John Stoffel
2014-01-06 16:54 ` Phil Turmel
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=52C9A5BB.4090803@turmel.org \
--to=philip@turmel.org \
--cc=interzone@gmail.com \
--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).