From: Adam Goryachev <mailinglists@websitemanagers.com.au>
To: Arun Khan <knura9@gmail.com>
Cc: Linux MDADM Raid <linux-raid@vger.kernel.org>
Subject: Re: Unable to reactivate a RAID10 mdadm device
Date: Tue, 12 Feb 2013 23:05:53 +1100 [thread overview]
Message-ID: <511A3021.4020300@websitemanagers.com.au> (raw)
In-Reply-To: <CAHhM8gBiQNHU+WJ_FRTG9HdZx3CVsVyUse_UBQ4VQLJLie8PjQ@mail.gmail.com>
On 12/02/13 22:34, Arun Khan wrote:
> On Tue, Feb 12, 2013 at 5:00 PM, Arun Khan <knura9@gmail.com> wrote:
>> On Tue, Feb 12, 2013 at 2:02 PM, Adam Goryachev wrote:
>>> You didn't mention the kernel version (or I've missed it) but that is my
>>> suggestion, certainly before you try anything destructive....
>> It was mentioned right at the beginning of my OP - Stock Debian Squeeze 2.6.32-5
>>
> and I missed this one -
> The System Rescue CD has kernel 3.2.19 and mdadm - v3.1.4 - 31st August 2010.
>
> I am using System Rescue CD to recover /dev/md0.
Sorry, I missed those then....
Why don't you try using a debian stable rescue cd? It should have a
similar version of mdadm and kernel to what you are using on the machine.
I think the issue I mentioned was only in the kernel for a limited
period of time, and I'm sure 2.6.x was not affected... I'd suggest you
check the list archives if you need to know exactly which versions are
affected.
Hope this helps...
Regards,
Adam
--
Adam Goryachev
Website Managers
www.websitemanagers.com.au
next prev parent reply other threads:[~2013-02-12 12:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-12 7:16 Unable to reactivate a RAID10 mdadm device Arun Khan
2013-02-12 8:32 ` Adam Goryachev
2013-02-12 11:30 ` Arun Khan
2013-02-12 11:34 ` Arun Khan
2013-02-12 12:05 ` Adam Goryachev [this message]
2013-02-12 8:42 ` Dave Cundiff
2013-02-12 11:25 ` Arun Khan
2013-02-12 21:28 ` Dave Cundiff
2013-02-23 14:59 ` Arun Khan
2013-02-24 14:27 ` Roy Sigurd Karlsbakk
2013-02-25 6:22 ` Arun Khan
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=511A3021.4020300@websitemanagers.com.au \
--to=mailinglists@websitemanagers.com.au \
--cc=knura9@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 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.