linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Krekna Mektek <krekna@gmail.com>
To: linux-raid@vger.kernel.org
Subject: Re: RAID 5 inaccessible - continued
Date: Tue, 14 Feb 2006 11:35:28 +0100	[thread overview]
Message-ID: <8b24c8b10602140235s7a4ef1fam@mail.gmail.com> (raw)
In-Reply-To: <17393.42370.394254.464935@cse.unsw.edu.au>

2006/2/14, Neil Brown <neilb@suse.de>:
> On Tuesday February 14, krekna@gmail.com wrote:
> > Krekna is crying out loud in the empty wilderness....
> > No one there to help me?
>
> Nope :-)
>
> > > I did the folowing:
> > >
> > > dd conv=noerror if=dev/hdd1 of=/mnt/hdb1/Faulty-RAIDDisk.img
> > > losetup /dev/loop0 /mnt/hdb1/Faulty-RAIDDisk.img
> ..
> > >
> > > But it did not work out (yet).
> > >
> > > madm -E /dev/loop0
> > > mdadm: No super block found on /dev/loop0 (Expected magic a92b4efc,
> > > got 00000000)
> ...
> > >
> > > - can I restore the superblock from the hdd1 disk (which is still alive)
> > >
>
> If mdadm -E /dev/hdd1 shows a valid superblock, and mdadm -E
> /dev/loop0 doesn't, then your 'dd' wasn't very successful.

Hi,

Actually, /dev/hdd1 partition is 390708801 blocks, the disk itself is
a Hitachi 400GB disk.
So this is 390708801 blocks of 1024 bytes. This is according to my
calculation 400085812224 bytes.
The Faulty-RAIDDisk.img is according to my ls -l 400085771264 bytes.

So it looks like they are quite the same, and the difference between
the two is 40960 bytes. These are 40 blocks, so 36 are missing?

The dd actually succeeded, and did finish the job in about one day.
The badblocks were found after about the first 7 Gigs.

Is there no way like the conv=noerror for mdadm, to just continue?
Can I restore the superblock on the .img file somehow?
Is it probably save to --zero-superblock all the three disks and that
the RAID array will create two new superblocks (Leaving the spare out,
because its probably out of date).

I can do the dd again, but I think it will do the same thing, because
it finished 'succesfully'.
The superblock is at the end of the disk I read, about the last
64-128K or something.

Krekna


>
> What is the size of /mnt/hdb1/Faulty-RAIDDisk.img ?? What is the size
> of /dev/hdd1?
>
> BTW, you don't need to edit mdadm.conf to try things out.  Just
>
>   mdadm -A /dev/md0 /dev/hdb1 /dev/hdc1 /dev/loop0
>
> NeilBrown
>

  reply	other threads:[~2006-02-14 10:35 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-13 15:08 RAID 5 inaccessible - continued Krekna Mektek
2006-02-14  8:35 ` Krekna Mektek
2006-02-14  9:40   ` Neil Brown
2006-02-14 10:35     ` Krekna Mektek [this message]
     [not found]       ` <43F1FFE1.2010107@h3c.com>
2006-02-14 17:18         ` Krekna Mektek
2006-02-14 17:41           ` David Greaves
2006-02-15  9:36             ` Krekna Mektek
     [not found]             ` <8b24c8b10602151218i43886b75h@mail.gmail.com>
     [not found]               ` <43F3B119.1000800@dgreaves.com>
2006-02-16 14:32                 ` Krekna Mektek
2006-02-16 15:08                   ` Krekna Mektek
2006-02-16 16:42                     ` Krekna Mektek
2006-02-15  9:35         ` Krekna Mektek
2006-02-15  9:59       ` Burkhard Carstens
2006-02-15 15:09         ` Krekna Mektek

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=8b24c8b10602140235s7a4ef1fam@mail.gmail.com \
    --to=krekna@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).