From: sylvain.depuille@laposte.net
To: Can Jeuleers <can.jeuleers@gmail.com>
Cc: John Stoffel <john@stoffel.org>, linux-raid@vger.kernel.org
Subject: Re: Re : Re: Big trouble during reassemble a Raid5
Date: Sun, 4 Jan 2015 19:19:47 +0100 (CET) [thread overview]
Message-ID: <88720318.23672175.1420395587173.JavaMail.zimbra@laposte.net> (raw)
In-Reply-To: <54A64FEB.8090109@gmail.com>
Hello,
thank's for the tricks.
I have modify the #! as #!/usr/bin/python2 because i have python 2.7 and 3.3 as default on my PCs.
I keep this script on my PCs, and the output ;-)
Thank's a lot.
Best Regards
----- Mail original -----
De: "Can Jeuleers" <can.jeuleers@gmail.com>
À: "John Stoffel" <john@stoffel.org>, "sylvain depuille" <sylvain.depuille@laposte.net>
Cc: linux-raid@vger.kernel.org
Envoyé: Vendredi 2 Janvier 2015 08:59:39
Objet: Re: Re : Re: Big trouble during reassemble a Raid5
On 02/01/15 05:07, John Stoffel wrote:
> My real suggestion to you is to now collect all the information you
> can on the system, including drive serial numbers, and how they map to
> each device and member of the RAID array. Sometimes when a system
> reboots, or you add new disks, things get re-arranged and you don't
> notice at first. And that leads you down the wrong path quite
> quickly.
Sylvain, a nice script for documenting device serial numbers,
partitions, RAID memberships etc can be found here:
https://github.com/pturmel/lsdrv/raw/master/lsdrv
Written by Phil Turmel; a frequent contributor to this list.
Jan
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2015-01-04 18:19 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2105542796.11263344.1419768937013.JavaMail.zimbra@laposte.net>
2014-12-28 12:16 ` Big trouble during reassemble a Raid5 sylvain.depuille
2014-12-29 18:32 ` John Stoffel
[not found] ` <164935924.13594562.1419881845418.JavaMail.zimbra@laposte.net>
2014-12-29 20:36 ` Re : " John Stoffel
2014-12-30 9:37 ` sylvain.depuille
2014-12-30 21:06 ` John Stoffel
2014-12-30 12:44 ` sylvain.depuille
[not found] ` <84D72604-6572-40D9-8861-19B28BBF91B6@laposte.net>
[not found] ` <21667.5112.568800.563410@quad.stoffel.home>
[not found] ` <367813595.16604641.1420034830100.JavaMail.zimbra@laposte.net>
[not found] ` <21668.1236.130012.995660@quad.stoffel.home>
2014-12-31 14:51 ` sylvain.depuille
2014-12-31 16:08 ` John Stoffel
[not found] ` <A6F7476D-8314-480D-B6B5-F84FF1F0960B@laposte.net>
[not found] ` <21668.12775.212408.482021@quad.stoffel.home>
2014-12-31 17:59 ` sylvain.depuille
2014-12-31 19:11 ` John Stoffel
2015-01-01 18:21 ` sylvain.depuille
2015-01-02 4:07 ` John Stoffel
2015-01-02 7:59 ` Can Jeuleers
2015-01-04 18:19 ` sylvain.depuille [this message]
2015-01-04 18:16 ` sylvain.depuille
2015-01-01 21:06 ` sylvain.depuille
2015-01-02 4:01 ` John Stoffel
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=88720318.23672175.1420395587173.JavaMail.zimbra@laposte.net \
--to=sylvain.depuille@laposte.net \
--cc=can.jeuleers@gmail.com \
--cc=john@stoffel.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).