From: Stan Hoeppner <stan@hardwarefreak.com>
To: linux-raid@vger.kernel.org
Subject: Re: dm-crypt over raid6 unreadable after crash
Date: Mon, 11 Jul 2011 06:49:47 -0500 [thread overview]
Message-ID: <4E1AE35B.1020307@hardwarefreak.com> (raw)
In-Reply-To: <20110711075729.GB32187@apartia.fr>
On 7/11/2011 2:57 AM, Louis-David Mitterrand wrote:
> On Sun, Jul 10, 2011 at 06:44:21PM -0500, Stan Hoeppner wrote:
>>
>> Moral of this story: Using live CDs to troubleshoot Linux RAID arrays,
>> LVM volumes, dmcrypt, etc, is tricky at best, fraught with disaster at
>> worst. Always have a "system rescue" CD/DVD built from the particular
>> machine in question at the ready. Most distros have a facility for
>> building such a per machine boot/rescue CD. Such media will have the
>> same kernel and module versions, the system's mdadm configuration, and
>> all other system specific stuff needed to properly troubleshoot and repair.
>>
>> If such rescue media had been used the OP would have likely experienced
>> far less grief, and might already had this problem fixed.
>
> A live CD like grml can properly auto-start a md array. My problem
> came from doing a --create instead of an --assemble at some point.
What did it not auto-start your md array in this case again?
--
Stan
next prev parent reply other threads:[~2011-07-11 11:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-06 16:12 dm-crypt over raid6 unreadable after crash Louis-David Mitterrand
2011-07-06 17:00 ` Phil Turmel
2011-07-07 9:05 ` Louis-David Mitterrand
2011-07-07 12:41 ` Phil Turmel
2011-07-07 13:09 ` Louis-David Mitterrand
2011-07-07 13:32 ` Phil Turmel
2011-07-08 5:40 ` Luca Berra
2011-07-10 12:03 ` Louis-David Mitterrand
2011-07-10 12:28 ` Phil Turmel
2011-07-10 23:44 ` Stan Hoeppner
2011-07-11 7:57 ` Louis-David Mitterrand
2011-07-11 11:49 ` Stan Hoeppner [this message]
2011-07-11 7:54 ` Louis-David Mitterrand
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=4E1AE35B.1020307@hardwarefreak.com \
--to=stan@hardwarefreak.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