From: Larry McVoy <lm@bitmover.com>
To: "Richard B. Johnson" <root@chaos.analogic.com>
Cc: "Theodore Ts'o" <tytso@mit.edu>, Larry McVoy <lm@bitmover.com>,
Ricky Beam <jfbeam@bluetronic.net>,
Linux Kernel Mail List <linux-kernel@vger.kernel.org>
Subject: Re: data from kernel.bkbits.net
Date: Mon, 24 Nov 2003 14:24:13 -0800 [thread overview]
Message-ID: <20031124222413.GA27604@work.bitmover.com> (raw)
In-Reply-To: <Pine.LNX.4.53.0311241628230.3173@chaos>
On Mon, Nov 24, 2003 at 04:34:43PM -0500, Richard B. Johnson wrote:
> On Mon, 24 Nov 2003, Theodore Ts'o wrote:
>
> > On Mon, Nov 24, 2003 at 03:05:24PM -0500, Richard B. Johnson wrote:
> > > Attempt to copy the raw drive to /dev/null. If that works, the
> > > drive is likely okay, but the fs got fsucked up by software. You
> > > might be able to mount the drive on a 2.4.22 machine if you have a
> > > spare. Then you might be able to selectively copy important stuff
> > > to another drive, after which you can make a new file-system as
> > > a "repair".
> >
> > The error messages Larry reported were obviously reported by the
> > hardware, and were **not** filesystem errors.
> >
> > - Ted
>
> Yes but an attempt to read beyond the limits of the physical
> drive will provide you with a lot of **interesting** hardware
> errors. This happens if the file-system gets corrupt.
Yeah, I think Richard may be right. Anyway, the drive sort of reads
from the raw partition. It gets a IDE reset and then it reads. I can
read it a second time with no reset. Haven't tried a reboot between
reads, hang on, yeah, a reboot brings the errors back.
But, fscking the dd-ed image gets me less errors so I'm trying that
route to get the data back.
--
---
Larry McVoy lm at bitmover.com http://www.bitmover.com/lm
next prev parent reply other threads:[~2003-11-24 22:24 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-24 5:19 data from kernel.bkbits.net Larry McVoy
2003-11-24 7:34 ` H. Peter Anvin
2003-11-24 14:57 ` Larry McVoy
2003-11-24 15:43 ` Ricky Beam
2003-11-24 15:50 ` Larry McVoy
2003-11-24 19:17 ` Ricky Beam
2003-11-24 19:24 ` Larry McVoy
2003-11-24 19:35 ` Jamie Lokier
2003-11-24 20:05 ` Richard B. Johnson
2003-11-24 20:33 ` Theodore Ts'o
2003-11-24 21:34 ` Richard B. Johnson
2003-11-24 22:24 ` Larry McVoy [this message]
2003-11-24 22:38 ` Jamie Lokier
2003-11-25 0:30 ` Theodore Ts'o
2003-11-24 20:09 ` Ricky Beam
2003-11-24 9:48 ` Willy Tarreau
2003-11-25 15:00 ` Ben Collins
-- strict thread matches above, loose matches on Subject: below --
2003-11-24 19:14 Adam Radford
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=20031124222413.GA27604@work.bitmover.com \
--to=lm@bitmover.com \
--cc=jfbeam@bluetronic.net \
--cc=linux-kernel@vger.kernel.org \
--cc=root@chaos.analogic.com \
--cc=tytso@mit.edu \
/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