linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Krekna Mektek <krekna@gmail.com>
To: David Greaves <david@dgreaves.com>, linux-raid@vger.kernel.org
Subject: Re: RAID 5 inaccessible - continued
Date: Thu, 16 Feb 2006 16:08:18 +0100	[thread overview]
Message-ID: <8b24c8b10602160708j248c1752u@mail.gmail.com> (raw)
In-Reply-To: <8b24c8b10602160632h59111c54u@mail.gmail.com>

Whoops, sorry, I remember something about LVM... I've setup the system
with LVM, I'm sure of that. In that case I can't mount /dev/md0 of
course..

I need to find out how this stuff works again..

Krekna

2006/2/16, Krekna Mektek <krekna@gmail.com>:
> Hi,
>
> Well, the dd_rescue did it's work, the array is now rebuilding, but
> it's doing its thing very slowly.
>
> But now the following, while the array is rebuilding and with the good
> image on my new disk (The FaultyRAIDDisk.img), I am trying to mount
> /dev/md0 already, but it now says :
>
> root@1[~]# fdisk -l /dev/md0
>
> Disk /dev/md0: 800.1 GB, 800171491328 bytes
> 2 heads, 4 sectors/track, 195354368 cylinders
> Units = cylinders of 8 * 512 = 4096 bytes
>
> Disk /dev/md0 doesn't contain a valid partition table
>
> How can some individual disks which crash destroy my partition table!? Help!
> Is there some way to get my data back from here??
>
>
>
> 2006/2/15, David Greaves <david@dgreaves.com>:
> > man ddrescue:
> >       -r, --max-retries=<n>
> >               exit after given retries (-1=infinity) [0]
> >
> >
> > So the -r10 basically tries to re-read each dodgy sector 10 times.
> >
> > Is it working?
> >
> > David
> >
> > Krekna Mektek wrote:
> >
> > >Hi,
> > >
> > >I am busy with it now, but what does the 10 mean in -r10 ? I
> > >understand from the --help that one can use the -r option, but without
> > >something behind it?
> > >
> > >Krekna
> > >
> > >2006/2/14, David Greaves <david@dgreaves.com>:
> > >
> > >
> > >>Krekna Mektek wrote:
> > >>
> > >>
> > >>
> > >>>I want to rebuilt from the good one and the faulty one. That's why I
> > >>>wanted to dd the disk to an image file, but it complains it has no
> > >>>boot sector.
> > >>>
> > >>>
> > >>>
> > >>>
> > >>>
> > >>>>>>I did the folowing:
> > >>>>>>
> > >>>>>>dd conv=noerror if=dev/hdd1 of=/mnt/hdb1/Faulty-RAIDDisk.img
> > >>>>>>losetup /dev/loop0 /mnt/hdb1/Faulty-RAIDDisk.img
> > >>>>>>
> > >>>>>>
> > >>>>>>
> > >>>>>>
> > >>You could try doing this again using ddrescue (google if you need to
> > >>install it):
> > >>
> > >>   ddrescue dev/hdd1 /mnt/hdb1/Faulty-RAIDDisk.img
> > >>/mnt/hdb1/Faulty-RAIDDisk.log
> > >>
> > >>Then do it again using -r10 (to increase the retries on the faulty sectors)
> > >>
> > >>   ddrescue -r10 dev/hdd1 /mnt/hdb1/Faulty-RAIDDisk.img
> > >>/mnt/hdb1/Faulty-RAIDDisk.log
> > >>
> > >>This will be much quicker because the log file contains details of the
> > >>faulty sectors.
> > >>With luck (mucho luck) you may not even lose data.
> > >>
> > >>David
> > >>
> > >>--
> > >>
> > >>
> > >>
> > >>
> > >
> > >
> > >
> >
> >
> > --
> >
> >
>

  reply	other threads:[~2006-02-16 15:08 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
     [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 [this message]
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=8b24c8b10602160708j248c1752u@mail.gmail.com \
    --to=krekna@gmail.com \
    --cc=david@dgreaves.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).