All of lore.kernel.org
 help / color / mirror / Atom feed
From: Billy Transue <bill@black9.net>
To: "Dieter Nützel" <Dieter.Nuetzel@hamburg.de>
Cc: ReiserFS List <reiserfs-list@namesys.com>
Subject: Re: Problem with my HDD
Date: 31 May 2002 13:49:42 -0500	[thread overview]
Message-ID: <1022870982.641.6.camel@threshold> (raw)
In-Reply-To: <200205311828.27837.Dieter.Nuetzel@hamburg.de>

Thanks, I had no idea it allocated all the space right away, but it
still didn't work, the file got a bit bigger, not much.  It was 
73728 bytes big, I let the process run til my computer suddenly crashed,
here is an excert from syslog, there was ton of lines just like the
first 3 shown, from 12:01 til this last one then the kernel panic.  It
should be noted I've been getting kernel panics before too.  I think my
2nd chip of memory is bad.  I'm taking it out after I type this,
hopefully no kernel panics til then.  Any advice?

May 31 12:19:09 threshold kernel: hdd: read_intr: status=0x59 {
DriveReady SeekComplete DataRequest Error }
May 31 12:19:09 threshold kernel: hdd: read_intr: error=0x40 {
UncorrectableError }, LBAsect=11310269, sector=446
May 31 12:19:09 threshold kernel: end_request: I/O error, dev 16:45
(hdd), sector 446
May 31 12:19:14 threshold kernel: CPU 0: Machine Check Exception:
0000000000000004

Love,
Billy

On Fri, 2002-05-31 at 11:28, Dieter Nützel wrote:
> On Friday 31 May 2002 04:20,  Billy Transue wrote:
> 
> [-]
> > I've suffered a very similar problem and posted to the list earlier, I
> > did, dd_resuce -l dd.log /dev/hdd5 ./hdd5 and winded up w/ this:
> > dd_rescue: (info): ipos:         0.0k, opos:         0.0k,
> > xferd:         0.0k
> >                    errs:      0, errxfer:         0.0k,
> > succxfer:         0.0k
> >              +curr.rate:        0kB/s, avg.rate:        0kB/s,
> > avg.load:  0.0%
> >
> > it never changed, the file created hdd5 was 65536 bytes large.  The log
> > file was empty.  Am I doing something wrong?  Any info would be
> > appreciated.  Thanks in advance.
> 
> Bill, have you ever tried the (r)evers mode?
> A valid run on a 859.412k partition should look like this:
> 
> SunWave1 /tmp# time dd_rescue -r -l dd_rescue-sdb8.log /dev/sdb8 sdb8
> dd_rescue: (info): ipos:    859446.0k, opos:    859446.0k, xferd:         0.0k
>              -  *  errs:      0, errxfer:         0.0k, succxfer:         0.0k
>              +curr.rate:        0kB/s, avg.rate:        0kB/s, avg.load: 96.1%
> dd_rescue: (warning): /dev/sdb8 (859446.0k): Input/output error!
> dd_rescue: (info): ipos:    859445.5k, opos:    859445.5k, xferd:         0.5k
>              -  *  errs:      1, errxfer:         0.5k, succxfer:         0.0k
>              +curr.rate:      197kB/s, avg.rate:        0kB/s, avg.load: 96.0%
> dd_rescue: (warning): /dev/sdb8 (859445.5k): Input/output error!
> dd_rescue: (info): ipos:    859445.0k, opos:    859445.0k, xferd:         1.0k
>              -  *  errs:      2, errxfer:         1.0k, succxfer:         0.0k
>              +curr.rate:      252kB/s, avg.rate:        0kB/s, avg.load: 95.9%
> dd_rescue: (warning): /dev/sdb8 (859445.0k): Input/output error!
> dd_rescue: (info): ipos:    859444.5k, opos:    859444.5k, xferd:         1.5k
>              -  *  errs:      3, errxfer:         1.5k, succxfer:         0.0k
>              +curr.rate:      261kB/s, avg.rate:        1kB/s, avg.load: 95.8%
> dd_rescue: (warning): /dev/sdb8 (859444.5k): Input/output error!
> dd_rescue: (info): ipos:        54.0k, opos:        54.0k, xferd:    859392.0k
>              -     errs:      4, errxfer:         2.0k, succxfer:    859390.0k
>              +curr.rate:     2413kB/s, avg.rate:     2219kB/s, avg.load:  4.5%
> Summary for /dev/sdb8 -> sdb8:
> dd_rescue: (info): ipos:         0.0k, opos:         0.0k, xferd:    859446.0k
>              -     errs:      4, errxfer:         2.0k, succxfer:    859444.0k
>              +curr.rate:     2201kB/s, avg.rate:     2217kB/s, avg.load:  4.5%
> 0.530u 16.960s 6:27.67 4.5%     0+0k 0+0io 122pf+0w
> 
> SunWave1 /tmp# l dd_rescue-sdb8.log sdb8
> -rw-r-----    1 root     root         1713 Mai 31 18:15 dd_rescue-sdb8.log
> -rw-r-----    1 root     root     880072704 Mai 31 18:15 sdb8
> 
> Are you sure that you had write permission and enough space (!!!) on your 
> destination (in your case the current working directory)?
> 
> dd_rescue seems to allocate the whole needed disk space at the beginning!
> 
> Good luck!
> 
> -Dieter
> 
> BTW I've had "recovered" several (Winbloze) disks of our customers with 
> dd_rescue. But *nix FSes are much better to recover because of the better FS 
> redundancy and fsck tools after the dd_rescue run.
> 
> -- 
> Dieter Nützel
> Graduate Student, Computer Science
> 
> University of Hamburg
> Department of Computer Science
> @home: Dieter.Nuetzel@hamburg.de



  reply	other threads:[~2002-05-31 18:49 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-31 16:28 Problem with my HDD Dieter Nützel
2002-05-31 18:49 ` Billy Transue [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-05-29 17:49 Cookie-Monster
2002-05-29 17:53 ` Anders Widman
2002-05-29 21:19 ` Kuba Ober
2002-05-29 23:45 ` Robert Brockway
2002-05-30  0:09   ` Re[2]: " Anders Widman
2002-05-30  5:17     ` Oleg Drokin
2002-05-31  5:15       ` Billy Transue
2002-05-31  8:29         ` Oleg Drokin
2002-05-30  5:14   ` Oleg Drokin
2002-05-30  5:49     ` Robert Brockway
2002-05-30  5:21 ` Oleg Drokin

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=1022870982.641.6.camel@threshold \
    --to=bill@black9.net \
    --cc=Dieter.Nuetzel@hamburg.de \
    --cc=reiserfs-list@namesys.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.