public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Jaap Struyk <japie@deserver.nl>
To: xfs@oss.sgi.com
Subject: Re: ways to restore data from crashed disk
Date: Sat, 09 Jun 2007 09:50:49 +0200	[thread overview]
Message-ID: <466A5BD9.7010604@deserver.nl> (raw)
In-Reply-To: <46697C94.40401@sandeen.net>

Eric Sandeen schreef:

> it looks like the original filesystem was bigger than your image:
> 
> 4096*36710528
> 150366322688 <-- 140 MB
> 
> so it looks like your image file is not correct... I'm not familiar with
> the tool you're using, is it somehow compressing a sparse file or
> something like that?

You are completely right!

I used dd_rhelp instead of dd_rescue since everytime a bad block is hit
my disk isn't acceseble anymore and I have to reboot.
So I tryed another aproach and used a knoppix cd to boot and used
dd_rescue right away and with knoppix the disk keeps readable. (so it
seems the kernel knoppix is using isn't killed by bad blocks, mine is)
In concreto: I dumped my disk on another, used xfs_repair without
problems and got almost all my data back (except for the last 2G that
was written)
Thanks for pointing me the right track, or else I was still wrestling to
recover an incomplete image file!
-- 
Groetjes Japie

      reply	other threads:[~2007-06-09  7:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-31 10:50 ways to restore data from crashed disk Jaap Struyk
2007-05-31 13:37 ` Eric Sandeen
2007-06-07 18:12   ` Jaap Struyk
2007-06-07 18:56     ` Jaap Struyk
2011-05-26 12:39       ` Robert
2007-06-07 19:28     ` Eric Sandeen
2007-06-08  4:03       ` Jaap Struyk
2007-06-08 15:58         ` Eric Sandeen
2007-06-09  7:50           ` Jaap Struyk [this message]

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=466A5BD9.7010604@deserver.nl \
    --to=japie@deserver.nl \
    --cc=xfs@oss.sgi.com \
    /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