disk problems or false alarm??

From: Guolin Cheng (guolin_at_alexa.com)
Date: 04/30/04

  • Next message: Mike Rambour: "Re: what am I missing, getting SMTP to work" 
    Date: Fri, 30 Apr 2004 10:54:59 -0700
To: <fedora-list@redhat.com>, <ext3-users@redhat.com>

    Hi,

     

     I run hundreds of Redhat 8.0 boxes and Fedora Core 1 boxes, both
    Operation systems boxes give me some trouble reporting disk errors like
    the following (collected from /var/log/messages of each linux boxes by
    my own script). And a "badblocks" command on some of the related hard
    drive reports that failed sectors found, while others reports no,
    false-positive. Any one can give me suggestions or hints?

     

    Thanks a lot.

     

    ......

    Host: arc242

    arc242: Apr 29 13:51:32 arc242 kernel: hdb: dma_intr: status=0x51 {
    DriveReady SeekComplete Error }

    arc242: Apr 29 13:51:32 arc242 kernel: hdb: dma_intr: error=0x01 {
    AddrMarkNotFound }, LBAsect=38613129, sector=38613064

    arc242: Apr 29 13:51:36 arc242 kernel: hdb: dma_intr: status=0x51 {
    DriveReady SeekComplete Error }

    arc242: Apr 29 13:51:36 arc242 kernel: hdb: dma_intr: error=0x01 {
    AddrMarkNotFound }, LBAsect=38613129, sector=38613064

    arc242: Apr 29 13:51:43 arc242 kernel: hdb: dma_intr: status=0x51 {
    DriveReady SeekComplete Error }

    arc242: Apr 29 13:51:43 arc242 kernel: hdb: dma_intr: error=0x40 {
    UncorrectableError }, LBAsect=38613129, sector=38613064

    arc242: Apr 29 13:51:43 arc242 kernel: end_request: I/O error, dev
    03:41 (hdb), sector 38613064

    arc242: Apr 29 13:51:49 arc242 kernel: hdb: dma_intr: status=0x51 {
    DriveReady SeekComplete Error }

    arc242: Apr 29 13:51:49 arc242 kernel: hdb: dma_intr: error=0x40 {
    UncorrectableError }, LBAsect=38613129, sector=38613064

    arc242: Apr 29 13:51:49 arc242 kernel: end_request: I/O error, dev
    03:41 (hdb), sector 38613064

     

    Host: arc292

    arc292: Apr 29 04:02:27 arc292 kernel: hda: dma_intr: status=0x51 {
    DriveReady SeekComplete Error }

    arc292: Apr 29 04:02:27 arc292 kernel: hda: dma_intr: error=0x40 {
    UncorrectableError }, LBAsect=239379157, high=14, low=4498133,
    sector=331888

    arc292: Apr 29 04:02:27 arc292 kernel: end_request: I/O error, dev
    03:0b (hda), sector 331888

    arc292: Apr 29 04:02:29 arc292 kernel: hda: dma_intr: status=0x51 {
    DriveReady SeekComplete Error }

    arc292: Apr 29 04:02:29 arc292 kernel: hda: dma_intr: error=0x40 {
    UncorrectableError }, LBAsect=239379157, high=14, low=4498133,
    sector=331888

    arc292: Apr 29 04:02:29 arc292 kernel: end_request: I/O error, dev
    03:0b (hda), sector 331888

     

    ...... blahblah...

     

    I tried to run "badblocks" on the boxes to test whether there are real
    hardware problems, then I got some of them really reports problems, and
    some of them NOT. Anyone know why?

     

     

    [root@arc242 root]# badblocks -s -v -n -b 512 -c 4096 /dev/hdb 38620000
    38600000

    Checking for bad blocks in non-destructive read-write mode

    >From block 38600000 to 38620000

    Checking for bad blocks (non-destructive read-write test)

    Testing with random pattern: done

    Pass completed, 0 bad blocks found.

    [root@arc242 root]#

     

    [root@arc292 root]# badblocks -s -v -n -b 512 -c 4096 /dev/hda
    239400000 239300000

    Checking for bad blocks in non-destructive read-write mode

    >From block 239300000 to 239400000

    Checking for bad blocks (non-destructive read-write test)

    Testing with random pattern: 239379104/239400000

    239379105

    done

    Pass completed, 2 bad blocks found.

    [root@arc292 root]#

    [root@arc292 root]# 

    


    -- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list
  • Next message: Mike Rambour: "Re: what am I missing, getting SMTP to work"

    Relevant Pages

    • Why are bad disk sectors numbered strangely, and what happens to them?
      ... second is what does Linux do with them after detecting them? ... sector, and to see that the two numbers are sometimes related but sometimes ... {DriveReady SeekComplete Error} ... dev hda, sector 19021842 ...
      (Linux-Kernel)
    • Re: Sync option destroys flash!
      ... > so mixed up the whole card is dead (it identifies but all sectors fail ... hda: read_intr: status=0x51 {DriveReady SeekComplete Error} ... end_request: I/O error, dev 03:00, sector 6 ... "finished programming" one is not, read it and verify the checksums. ...
      (Linux-Kernel)
    • Harddisk errors
      ... sector 9393983 ... DriveReady SeekComplete Error} ... Feb 2 10:26:04 localhost kernel: ide: failed opcode was: unknown ... Does it mean that it's time to replace the disk? ...
      (Fedora)
    • cdrom problem
      ... I have a problem with my cdrom, the next error happend when i try to ... mount a cdrom: ... status=0x51 {DriveReady SeekComplete Error} ...
      (Fedora)