linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Greaves <david@dgreaves.com>
To: Janos Haar <djani22@netcenter.hu>
Cc: linux-raid@vger.kernel.org
Subject: Re: questions about softraid limitations
Date: Fri, 16 May 2008 09:36:47 +0100	[thread overview]
Message-ID: <482D479F.3040809@dgreaves.com> (raw)
In-Reply-To: <01be01c8b61a$6e616260$9300a8c0@dcccs>

Janos Haar wrote:
>> Firstly, are you aware that Linux SW raid will not understand disks
>> written by hardware raid.
> Yes, i know, but the linux raid is a great tool to try it, and if the
> user know what he is doing, it is safe too. :-)
OK - just checking :)

>> This will not allow md to write superblocks to the disks.
> 
> I think exactly for this steps:
> 
> dd if=/dev/zero of=suberblock.bin bs=64k count=1
> losetup /dev/loop0 superblock.bin
> blockdev --setro /dev/sda
> mdadm --build -l linear /dev/md0 /dev/sda /dev/loop0
> 
> The superblock area is writable.
> And this is enough to try to assemble the array to do the recovery, but
> this step is refused.
Ah, I understand now.
I think you need -n2 to tell mdadm to use 2 devices.

>>> Its OK, but what about building a readonly raid 5 array for recovery
>>> usage only? :-)
>> That's fine. If they are md raid disks. Yours aren't yet since you
>> haven't
>> written the superblocks.
> 
> I only want to help for some people to get back the data.
> I only need to build, not to create.

I think this would be really hard if they are not md arrays since the on-disk
layout is likely to be different. Not something I know how to do.

Typically the first step in recovery is to duplicate the disks using ddrescue
and work on copies of the duplicates where you can overwrite things.
If you have had a hardware failure on the drive then even mounting readonly can
make things worse. (If the mb/controller failed then fair enough - but in that
case it's not a 'recovery', just a simple, 'no-risk(tm)' migration... ?)

Tell us more about the failed system:
* hardware or md raid5  (if hw then you'll need a *lot* of info about on-disk
layout and I personally have no clue how to help - sorry)

If md:
* kernel of original system and new system
* new mdadm version
* what kind of failure occured
* any dmesg data you have
* can you ddrescue the drives and do mdadm --examine /dev/sd<partition> for each
component.

Cheers
David
PS Aplogies if I'm stating things that are obvious to you :)

  parent reply	other threads:[~2008-05-16  8:36 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-14  0:34 questions about softraid limitations Janos Haar
2008-05-14 10:45 ` David Greaves
2008-05-14 23:29   ` Janos Haar
2008-05-16  1:39     ` Neil Brown
2008-05-16  6:05       ` [OT] " Peter Rabbitson
2008-05-18 23:52         ` Neil Brown
2008-05-16 10:00       ` Janos Haar
2008-05-16  8:36     ` David Greaves [this message]
2008-05-16  9:18       ` David Greaves
2008-05-16  9:28       ` Janos Haar
2008-05-18  9:11         ` David Greaves
2008-05-18 11:11           ` Janos Haar
2008-05-18 13:00             ` David Greaves
2008-05-18 21:51               ` Janos Haar
2008-05-18 19:36           ` David Lethe
2008-05-18 22:23             ` David Greaves
2008-05-18 22:38               ` Janos Haar
  -- strict thread matches above, loose matches on Subject: below --
2008-05-18 23:18 David Lethe

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=482D479F.3040809@dgreaves.com \
    --to=david@dgreaves.com \
    --cc=djani22@netcenter.hu \
    --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).