Bad disk controller? Dying HDD? - Hardware

This is a discussion on Bad disk controller? Dying HDD? - Hardware ; Hi. My old mini-tower PC's HDDs are acting crazy today. I came home and noticed my second drive wasn't there so I checked dmesg (deleted normal logs before hdb): hdb: dma_timer_expiry: dma status == 0x61 hdb: DMA timeout error hdb: ...

+ Reply to Thread
Page 1 of 3 1 2 3 LastLast
Results 1 to 20 of 55

Thread: Bad disk controller? Dying HDD?

  1. Bad disk controller? Dying HDD?

    Hi. My old mini-tower PC's HDDs are acting crazy today. I came home and
    noticed my second drive wasn't there so I checked dmesg (deleted normal
    logs before hdb):

    hdb: dma_timer_expiry: dma status == 0x61
    hdb: DMA timeout error
    hdb: dma timeout error: status=0x58 { DriveReady SeekComplete
    DataRequest }
    ide: failed opcode was: unknown
    hda: DMA disabled
    hdb: DMA disabled
    ide0: reset: success
    hdb: dma_intr: status=0x7d { DriveReady DeviceFault SeekComplete
    DataRequest CorrectedError Error }
    hdb: dma_intr: error=0x7d { DriveStatusError UncorrectableError
    SectorIdNotFound AddrMarkNotFound }, LBAsect=226327933, sector=3522545
    ide: failed opcode was: unknown
    hdb: DMA disabled
    ide0: reset: success
    hdb: task_in_intr: status=0x7d { DriveReady DeviceFault SeekComplete
    DataRequest CorrectedError Error }
    hdb: task_in_intr: error=0x7d { DriveStatusError UncorrectableError
    SectorIdNotFound AddrMarkNotFound }, LBAsect=226327933, sector=2362513
    ide: failed opcode was: unknown
    ide0: reset: success
    hdb: task_in_intr: status=0x7d { DriveReady DeviceFault SeekComplete
    DataRequest CorrectedError Error }
    hdb: task_in_intr: error=0x7d { DriveStatusError UncorrectableError
    SectorIdNotFound AddrMarkNotFound }, LBAsect=226327933, sector=2362513
    ide: failed opcode was: unknown
    ide0: reset: success
    ABORTED IN=eth0 OUT= MAC=00:d0:b7:85:0a:3f:00:a0:c5:e3:18:a8:08:00
    SRC=216.86.199.5 DST=192.168.0.32 LEN=40 TOS=0x00 PREC=0x00 TTL=46
    ID=15957 DF PROTO=TCP SPT=6667 DPT=1788 SEQ=2622437680 ACK=0 WINDOW=0
    RES=0x00 RST URGP=0
    hdb: task_in_intr: status=0x7d { DriveReady DeviceFault SeekComplete
    DataRequest CorrectedError Error }
    hdb: task_in_intr: error=0x7d { DriveStatusError UncorrectableError
    SectorIdNotFound AddrMarkNotFound }, LBAsect=226327933, sector=3537401
    ide: failed opcode was: unknown
    ide0: reset: success
    hdb: task_in_intr: status=0x7d { DriveReady DeviceFault SeekComplete
    DataRequest CorrectedError Error }
    hdb: task_in_intr: error=0x7d { DriveStatusError UncorrectableError
    SectorIdNotFound AddrMarkNotFound }, LBAsect=226327933, sector=3537401
    ide: failed opcode was: unknown
    ide0: reset timed-out, status=0x90
    hdb: status error: status=0x7d { DriveReady DeviceFault SeekComplete
    DataRequest CorrectedError Error }
    hdb: status error: error=0x7d { DriveStatusError UncorrectableError
    SectorIdNotFound AddrMarkNotFound }, LBAsect=226327933, sector=3537401
    ide: failed opcode was: unknown
    end_request: I/O error, dev hdb, sector 3537401
    hdb: drive not ready for command
    hdb: status error: status=0x7d { DriveReady DeviceFault SeekComplete
    DataRequest CorrectedError Error }
    hdb: status error: error=0x7d { DriveStatusError UncorrectableError
    SectorIdNotFound AddrMarkNotFound }, LBAsect=226327933, sector=3537409
    ide: failed opcode was: unknown
    hdb: drive not ready for command
    ide0: reset timed-out, status=0x90
    end_request: I/O error, dev hdb, sector 3537409
    end_request: I/O error, dev hdb, sector 3537417
    end_request: I/O error, dev hdb, sector 3537425
    end_request: I/O error, dev hdb, sector 3537401
    end_request: I/O error, dev hdb, sector 3538825
    end_request: I/O error, dev hdb, sector 3538833
    end_request: I/O error, dev hdb, sector 3538841
    end_request: I/O error, dev hdb, sector 3538849
    end_request: I/O error, dev hdb, sector 3538825
    end_request: I/O error, dev hdb, sector 3537977
    end_request: I/O error, dev hdb, sector 3537985
    end_request: I/O error, dev hdb, sector 3537993
    end_request: I/O error, dev hdb, sector 3538001
    end_request: I/O error, dev hdb, sector 3537977
    end_request: I/O error, dev hdb, sector 3536889
    end_request: I/O error, dev hdb, sector 3536897
    end_request: I/O error, dev hdb, sector 3536905
    end_request: I/O error, dev hdb, sector 3536913
    end_request: I/O error, dev hdb, sector 3536889
    end_request: I/O error, dev hdb, sector 3539689
    end_request: I/O error, dev hdb, sector 3539697
    end_request: I/O error, dev hdb, sector 3539705
    end_request: I/O error, dev hdb, sector 3539713
    end_request: I/O error, dev hdb, sector 3539689
    end_request: I/O error, dev hdb, sector 3544185
    end_request: I/O error, dev hdb, sector 3544193
    end_request: I/O error, dev hdb, sector 3544201
    end_request: I/O error, dev hdb, sector 3544209
    end_request: I/O error, dev hdb, sector 3544185
    end_request: I/O error, dev hdb, sector 3540457
    end_request: I/O error, dev hdb, sector 3540465
    end_request: I/O error, dev hdb, sector 3540473
    end_request: I/O error, dev hdb, sector 3540481
    end_request: I/O error, dev hdb, sector 3540457
    end_request: I/O error, dev hdb, sector 3542089
    end_request: I/O error, dev hdb, sector 3542097
    end_request: I/O error, dev hdb, sector 3542105
    end_request: I/O error, dev hdb, sector 3542113
    end_request: I/O error, dev hdb, sector 3542089
    end_request: I/O error, dev hdb, sector 3542897
    end_request: I/O error, dev hdb, sector 3542905
    end_request: I/O error, dev hdb, sector 3542913
    end_request: I/O error, dev hdb, sector 3542921
    end_request: I/O error, dev hdb, sector 3542897
    end_request: I/O error, dev hdb, sector 7257
    end_request: I/O error, dev hdb, sector 7265
    end_request: I/O error, dev hdb, sector 7273
    journal_bmap: journal block not found at offset 12 on hdb1
    Aborting journal on device hdb1.
    end_request: I/O error, dev hdb, sector 7177
    Buffer I/O error on device hdb1, logical block 897
    lost page write due to I/O error on hdb1
    end_request: I/O error, dev hdb, sector 2362529
    Buffer I/O error on device hdb1, logical block 295316
    lost page write due to I/O error on hdb1
    ABORTED IN=eth0 OUT= MAC=00:d0:b7:85:0a:3f:00:a0:c5:e3:18:a8:08:00
    SRC=64.22.96.69 DST=192.168.0.32 LEN=40 TOS=0x00 PREC=0x00 TTL=50 ID=0
    DF PROTO=TCP SPT=35249 DPT=22 SEQ=481307265 ACK=0 WINDOW=0 RES=0x00 RST
    URGP=0
    ABORTED IN=eth0 OUT= MAC=00:d0:b7:85:0a:3f:00:a0:c5:e3:18:a8:08:00
    SRC=64.22.96.69 DST=192.168.0.32 LEN=40 TOS=0x00 PREC=0x00 TTL=50 ID=0
    DF PROTO=TCP SPT=35249 DPT=22 SEQ=481307265 ACK=0 WINDOW=0 RES=0x00 RST
    URGP=0
    end_request: I/O error, dev hdb, sector 3543081
    end_request: I/O error, dev hdb, sector 3543089
    end_request: I/O error, dev hdb, sector 3543097
    end_request: I/O error, dev hdb, sector 3543105
    end_request: I/O error, dev hdb, sector 3543081
    ext3_abort called.
    EXT3-fs error (device hdb1): ext3_journal_start_sb: Detected aborted
    journal
    Remounting filesystem read-only
    end_request: I/O error, dev hdb, sector 3533193
    end_request: I/O error, dev hdb, sector 3533201
    end_request: I/O error, dev hdb, sector 3533209
    end_request: I/O error, dev hdb, sector 3533217
    end_request: I/O error, dev hdb, sector 3533193
    end_request: I/O error, dev hdb, sector 3533193
    end_request: I/O error, dev hdb, sector 3533193
    end_request: I/O error, dev hdb, sector 3533193
    end_request: I/O error, dev hdb, sector 3533193
    end_request: I/O error, dev hdb, sector 3533193
    end_request: I/O error, dev hdb, sector 2362529
    EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    block - inode=72691, block=295316
    end_request: I/O error, dev hdb, sector 3533193
    end_request: I/O error, dev hdb, sector 3533193
    end_request: I/O error, dev hdb, sector 3533193
    end_request: I/O error, dev hdb, sector 3533193
    end_request: I/O error, dev hdb, sector 3533193
    end_request: I/O error, dev hdb, sector 3533193
    ABORTED IN=eth0 OUT= MAC=00:d0:b7:85:0a:3f:00:16:17:94:32:d6:08:00
    SRC=192.168.0.46 DST=192.168.0.32 LEN=40 TOS=0x00 PREC=0x00 TTL=64
    ID=230 PROTO=TCP SPT=1056 DPT=139 SEQ=1299343103 ACK=1299343103 WINDOW=0
    RES=0x00 RST URGP=0
    ABORTED IN=eth0 OUT= MAC=00:d0:b7:85:0a:3f:00:16:17:94:32:d6:08:00
    SRC=192.168.0.46 DST=192.168.0.32 LEN=40 TOS=0x00 PREC=0x00 TTL=64
    ID=1980 PROTO=TCP SPT=1261 DPT=139 SEQ=969640467 ACK=969640467 WINDOW=0
    RES=0x00 RST URGP=0
    end_request: I/O error, dev hdb, sector 2362721
    EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    block - inode=73086, block=295340
    end_request: I/O error, dev hdb, sector 2362801
    EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    block - inode=73240, block=295350
    end_request: I/O error, dev hdb, sector 2362753
    EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    block - inode=73146, block=295344
    end_request: I/O error, dev hdb, sector 2362729
    EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    block - inode=73092, block=295341
    end_request: I/O error, dev hdb, sector 2362729
    EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    block - inode=73093, block=295341
    end_request: I/O error, dev hdb, sector 2362745
    EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    block - inode=73121, block=295343
    end_request: I/O error, dev hdb, sector 2362729
    EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    block - inode=73089, block=295341
    end_request: I/O error, dev hdb, sector 4568761
    end_request: I/O error, dev hdb, sector 2362753
    EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    block - inode=73140, block=295344
    end_request: I/O error, dev hdb, sector 2362729
    EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    block - inode=73100, block=295341
    end_request: I/O error, dev hdb, sector 2362737
    EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    block - inode=73113, block=295342
    end_request: I/O error, dev hdb, sector 2362745
    EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    block - inode=73129, block=295343
    end_request: I/O error, dev hdb, sector 2362745
    EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    block - inode=73135, block=295343
    end_request: I/O error, dev hdb, sector 2362761
    EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    block - inode=73164, block=295345
    end_request: I/O error, dev hdb, sector 2362753
    EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    block - inode=73142, block=295344
    end_request: I/O error, dev hdb, sector 2362761
    EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    block - inode=73162, block=295345
    end_request: I/O error, dev hdb, sector 2362729
    EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    block - inode=73104, block=295341
    end_request: I/O error, dev hdb, sector 2362745
    EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    block - inode=73128, block=295343
    end_request: I/O error, dev hdb, sector 2362745
    EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    block - inode=73122, block=295343
    end_request: I/O error, dev hdb, sector 2362761
    EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    block - inode=73153, block=295345
    end_request: I/O error, dev hdb, sector 2362753
    EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    block - inode=73141, block=295344
    end_request: I/O error, dev hdb, sector 2362753
    EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    block - inode=73144, block=295344
    end_request: I/O error, dev hdb, sector 2362753
    EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    block - inode=73148, block=295344
    end_request: I/O error, dev hdb, sector 2362753
    EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    block - inode=73139, block=295344
    end_request: I/O error, dev hdb, sector 2362729
    EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    block - inode=73095, block=295341
    end_request: I/O error, dev hdb, sector 2362745
    EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    block - inode=73127, block=295343
    end_request: I/O error, dev hdb, sector 2362745
    EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    block - inode=73134, block=295343
    end_request: I/O error, dev hdb, sector 2362753
    EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    block - inode=73152, block=295344
    end_request: I/O error, dev hdb, sector 2362753
    EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    block - inode=73149, block=295344
    end_request: I/O error, dev hdb, sector 2362761
    EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    block - inode=73155, block=295345
    end_request: I/O error, dev hdb, sector 2362745
    EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    block - inode=73131, block=295343
    end_request: I/O error, dev hdb, sector 2362761
    EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    block - inode=73168, block=295345
    end_request: I/O error, dev hdb, sector 2362745
    EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    block - inode=73132, block=295343
    end_request: I/O error, dev hdb, sector 2362737
    EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    block - inode=73118, block=295342
    end_request: I/O error, dev hdb, sector 2362761
    EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    block - inode=73158, block=295345
    end_request: I/O error, dev hdb, sector 2362729
    EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    block - inode=73103, block=295341
    end_request: I/O error, dev hdb, sector 2588673
    end_request: I/O error, dev hdb, sector 2362729
    EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    block - inode=73101, block=295341
    end_request: I/O error, dev hdb, sector 2362753
    EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    block - inode=73138, block=295344
    end_request: I/O error, dev hdb, sector 2362761
    EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    block - inode=73167, block=295345
    end_request: I/O error, dev hdb, sector 2362729
    EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    block - inode=73102, block=295341
    end_request: I/O error, dev hdb, sector 2362761
    EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    block - inode=73165, block=295345
    end_request: I/O error, dev hdb, sector 2362745
    EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    block - inode=73125, block=295343
    end_request: I/O error, dev hdb, sector 2362737
    EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    block - inode=73110, block=295342
    end_request: I/O error, dev hdb, sector 2362737
    EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    block - inode=73109, block=295342
    end_request: I/O error, dev hdb, sector 2362769
    EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    block - inode=73169, block=295346
    end_request: I/O error, dev hdb, sector 3651025
    end_request: I/O error, dev hdb, sector 2362761
    EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    block - inode=73157, block=295345
    end_request: I/O error, dev hdb, sector 2362729
    EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    block - inode=73097, block=295341
    end_request: I/O error, dev hdb, sector 2362737
    EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    block - inode=73106, block=295342
    end_request: I/O error, dev hdb, sector 2362737
    EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    block - inode=73114, block=295342
    end_request: I/O error, dev hdb, sector 2362761
    EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    block - inode=73166, block=295345
    end_request: I/O error, dev hdb, sector 2362737
    EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    block - inode=73117, block=295342
    end_request: I/O error, dev hdb, sector 2362737
    EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    block - inode=73120, block=295342
    end_request: I/O error, dev hdb, sector 2362753
    EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    block - inode=73150, block=295344
    end_request: I/O error, dev hdb, sector 2362729
    EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    block - inode=73091, block=295341
    end_request: I/O error, dev hdb, sector 2362753
    EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    block - inode=73147, block=295344
    end_request: I/O error, dev hdb, sector 2362729
    EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    block - inode=73099, block=295341
    end_request: I/O error, dev hdb, sector 2362761
    EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    block - inode=73154, block=295345
    end_request: I/O error, dev hdb, sector 2362745
    EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    block - inode=73124, block=295343
    end_request: I/O error, dev hdb, sector 2362737
    EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    block - inode=73108, block=295342
    end_request: I/O error, dev hdb, sector 2362737
    EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    block - inode=73116, block=295342
    end_request: I/O error, dev hdb, sector 2362753
    EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    block - inode=73137, block=295344
    end_request: I/O error, dev hdb, sector 2362737
    EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    block - inode=73111, block=295342
    end_request: I/O error, dev hdb, sector 4568729
    end_request: I/O error, dev hdb, sector 2362737
    EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    block - inode=73119, block=295342
    end_request: I/O error, dev hdb, sector 2362729
    EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    block - inode=73098, block=295341
    end_request: I/O error, dev hdb, sector 4567841
    end_request: I/O error, dev hdb, sector 2362721
    EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    block - inode=73088, block=295340
    end_request: I/O error, dev hdb, sector 2362737
    EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    block - inode=73105, block=295342
    end_request: I/O error, dev hdb, sector 2362729
    EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    block - inode=73090, block=295341
    end_request: I/O error, dev hdb, sector 2362745
    EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    block - inode=73133, block=295343
    end_request: I/O error, dev hdb, sector 2362761
    EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    block - inode=73161, block=295345
    end_request: I/O error, dev hdb, sector 2362737
    EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    block - inode=73115, block=295342
    end_request: I/O error, dev hdb, sector 2362745
    EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    block - inode=73136, block=295343
    end_request: I/O error, dev hdb, sector 2362745
    EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    block - inode=73123, block=295343
    end_request: I/O error, dev hdb, sector 2362761
    EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    block - inode=73160, block=295345
    end_request: I/O error, dev hdb, sector 2362737
    EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    block - inode=73112, block=295342
    end_request: I/O error, dev hdb, sector 2362761
    EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    block - inode=73156, block=295345
    end_request: I/O error, dev hdb, sector 2362761
    EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    block - inode=73159, block=295345
    end_request: I/O error, dev hdb, sector 2362753
    EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    block - inode=73151, block=295344
    end_request: I/O error, dev hdb, sector 2362729
    EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    block - inode=73094, block=295341
    end_request: I/O error, dev hdb, sector 2362729
    EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    block - inode=73096, block=295341
    end_request: I/O error, dev hdb, sector 2362745
    EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    block - inode=73130, block=295343
    end_request: I/O error, dev hdb, sector 2362737
    EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    block - inode=73107, block=295342
    end_request: I/O error, dev hdb, sector 2362761
    EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    block - inode=73163, block=295345
    end_request: I/O error, dev hdb, sector 2362745
    EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    block - inode=73126, block=295343
    end_request: I/O error, dev hdb, sector 3648201
    end_request: I/O error, dev hdb, sector 2362753
    EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    block - inode=73143, block=295344
    end_request: I/O error, dev hdb, sector 2362753
    EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    block - inode=73145, block=295344
    end_request: I/O error, dev hdb, sector 2710017
    end_request: I/O error, dev hdb, sector 2605065
    end_request: I/O error, dev hdb, sector 3544825
    end_request: I/O error, dev hdb, sector 2362505
    EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    block - inode=72647, block=295313
    end_request: I/O error, dev hdb, sector 2362529
    EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    block - inode=72689, block=295316
    end_request: I/O error, dev hdb, sector 2362505
    EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    block - inode=72643, block=295313
    end_request: I/O error, dev hdb, sector 2362521
    EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    block - inode=72678, block=295315
    end_request: I/O error, dev hdb, sector 3522817
    end_request: I/O error, dev hdb, sector 2362521
    EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    block - inode=72682, block=295315
    end_request: I/O error, dev hdb, sector 2362521
    EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    block - inode=72687, block=295315
    end_request: I/O error, dev hdb, sector 2362505
    EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    block - inode=72648, block=295313
    end_request: I/O error, dev hdb, sector 2362521
    EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    block - inode=72683, block=295315
    end_request: I/O error, dev hdb, sector 2362505
    EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    block - inode=72650, block=295313
    end_request: I/O error, dev hdb, sector 2362505
    EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    block - inode=72649, block=295313
    end_request: I/O error, dev hdb, sector 2362521
    EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    block - inode=72673, block=295315
    end_request: I/O error, dev hdb, sector 2362505
    EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    block - inode=72653, block=295313
    end_request: I/O error, dev hdb, sector 2362505
    EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    block - inode=72641, block=295313
    end_request: I/O error, dev hdb, sector 2362521
    EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    block - inode=72674, block=295315
    end_request: I/O error, dev hdb, sector 2362521
    EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    block - inode=72685, block=295315
    end_request: I/O error, dev hdb, sector 2362521
    EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    block - inode=72676, block=295315
    end_request: I/O error, dev hdb, sector 2362521
    EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    block - inode=72686, block=295315
    end_request: I/O error, dev hdb, sector 3522553
    end_request: I/O error, dev hdb, sector 3524505
    end_request: I/O error, dev hdb, sector 2362521
    EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    block - inode=72681, block=295315
    end_request: I/O error, dev hdb, sector 2362505
    EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    block - inode=72645, block=295313
    end_request: I/O error, dev hdb, sector 2362505
    EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    block - inode=72646, block=295313
    end_request: I/O error, dev hdb, sector 2362521
    EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    block - inode=72675, block=295315
    end_request: I/O error, dev hdb, sector 2362505
    EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    block - inode=72651, block=295313
    end_request: I/O error, dev hdb, sector 2362521
    EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    block - inode=72680, block=295315
    end_request: I/O error, dev hdb, sector 2362521
    EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    block - inode=72679, block=295315
    end_request: I/O error, dev hdb, sector 2362505
    EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    block - inode=72654, block=295313
    end_request: I/O error, dev hdb, sector 2362505
    EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    block - inode=72655, block=295313
    end_request: I/O error, dev hdb, sector 2362521
    EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    block - inode=72677, block=295315
    end_request: I/O error, dev hdb, sector 2362505
    EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    block - inode=72656, block=295313
    end_request: I/O error, dev hdb, sector 2362521
    EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    block - inode=72684, block=295315
    end_request: I/O error, dev hdb, sector 2362497
    EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    block - inode=72640, block=295312
    end_request: I/O error, dev hdb, sector 2362505
    EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    block - inode=72642, block=295313
    end_request: I/O error, dev hdb, sector 2362505
    EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    block - inode=72644, block=295313
    end_request: I/O error, dev hdb, sector 2362529
    EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    block - inode=72690, block=295316
    end_request: I/O error, dev hdb, sector 2362505
    EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    block - inode=72652, block=295313
    end_request: I/O error, dev hdb, sector 2362521
    EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    block - inode=72688, block=295315
    end_request: I/O error, dev hdb, sector 5119177

    I did an unmount of hdb, fdisk /dev/hdb, and it couldn't read it. I did
    a reboot, HDD showed up in CMOS/BIOS and Debian went to its safe mode
    and let me fsck it. fsck /dev/hdb said all ext3 journals got lost and
    reverted back to ext2. I fsck'ed. After reboot and remounting, it seems
    the files were OK? So I put journal back and things were OK.


    A few minutes later, things go crazy again:
    $ dmesg
    e PFN ranges
    0: 0 -> 130864
    On node 0 totalpages: 130864
    DMA zone: 32 pages used for memmap
    DMA zone: 0 pages reserved
    DMA zone: 4064 pages, LIFO batch:0
    Normal zone: 990 pages used for memmap
    Normal zone: 125778 pages, LIFO batch:31
    HighMem zone: 0 pages used for memmap
    DMI 2.3 present.
    ACPI: RSDP 000FA850, 0014 (r0 ACPIAM)
    ACPI: RSDT 1FF30000, 0030 (r1 A M I OEMRSDT 6000517 MSFT 97)
    ACPI: FACP 1FF30200, 0081 (r1 A M I OEMFACP 6000517 MSFT 97)
    ACPI: DSDT 1FF303E0, 3755 (r1 A0058 A0058002 2 MSFT 100000D)
    ACPI: FACS 1FF40000, 0040
    ACPI: APIC 1FF30390, 004A (r1 A M I OEMAPIC 6000517 MSFT 97)
    ACPI: OEMB 1FF40040, 003F (r1 A M I OEMBIOS 6000517 MSFT 97)
    ACPI: PM-Timer IO Port: 0x808
    ACPI: Local APIC address 0xfee00000
    ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
    Processor #0 15:12 APIC version 16
    ACPI: IOAPIC (id[0x01] address[0xfec00000] gsi_base[0])
    IOAPIC[0]: apic_id 1, version 3, address 0xfec00000, GSI 0-23
    ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
    ACPI: IRQ0 used by override.
    ACPI: IRQ2 used by override.
    ACPI: IRQ9 used by override.
    Enabling APIC mode: Flat. Using 1 I/O APICs
    Using ACPI (MADT) for SMP configuration information
    Allocating PCI resources starting at 30000000 (gap: 20000000:dff80000)
    Built 1 zonelists. Total pages: 129842
    Kernel command line: root=/dev/hda1 ro
    mapped APIC to ffffd000 (fee00000)
    mapped IOAPIC to ffffc000 (fec00000)
    Enabling fast FPU save and restore... done.
    Enabling unmasked SIMD FPU exception support... done.
    Initializing CPU#0
    PID hash table entries: 2048 (order: 11, 8192 bytes)
    Detected 2202.937 MHz processor.
    spurious 8259A interrupt: IRQ7.
    Console: colour VGA+ 80x25
    Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
    Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
    Memory: 514020k/523456k available (1702k kernel code, 8820k reserved,
    663k data, 244k init, 0k highmem)
    virtual kernel memory layout:
    fixmap : 0xfff4e000 - 0xfffff000 ( 708 kB)
    pkmap : 0xff800000 - 0xffc00000 (4096 kB)
    vmalloc : 0xe0800000 - 0xff7fe000 ( 495 MB)
    lowmem : 0xc0000000 - 0xdff30000 ( 511 MB)
    .init : 0xc0355000 - 0xc0392000 ( 244 kB)
    .data : 0xc02a9827 - 0xc034f784 ( 663 kB)
    .text : 0xc0100000 - 0xc02a9827 (1702 kB)
    Checking if this processor honours the WP bit even in supervisor mode... Ok.
    Calibrating delay using timer specific routine.. 4410.78 BogoMIPS
    (lpj=8821571)
    Security Framework v1.0.0 initialized
    SELinux: Disabled at boot.
    Capability LSM initialized
    Mount-cache hash table entries: 512
    CPU: After generic identify, caps: 078bfbff e1d3fbff 00000000 00000000
    00000000 00000000 00000000
    CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
    CPU: L2 Cache: 512K (64 bytes/line)
    CPU: After all inits, caps: 078bfbff e1d3fbff 00000000 00000410 00000000
    00000000 00000000
    Intel machine check architecture supported.
    Intel machine check reporting enabled on CPU#0.
    Compat vDSO mapped to ffffe000.
    Checking 'hlt' instruction... OK.
    SMP alternatives: switching to UP code
    Freeing SMP alternatives: 11k freed
    ACPI: Core revision 20070126
    CPU0: AMD Athlon(tm) 64 Processor 3200+ stepping 00
    Total of 1 processors activated (4410.78 BogoMIPS).
    ENABLING IO-APIC IRQs
    ...TIMER: vector=0x31 apic1=0 pin1=2 apic2=0 pin2=0
    Brought up 1 CPUs
    Booting paravirtualized kernel on bare hardware
    NET: Registered protocol family 16
    ACPI: bus type pci registered
    PCI: PCI BIOS revision 2.10 entry at 0xf0031, last bus=1
    PCI: Using configuration type 1
    Setting up standard PCI resources
    ACPI: Interpreter enabled
    ACPI: (supports S0 S1 S3 S4 S5)
    ACPI: Using IOAPIC for interrupt routing
    ACPI: PCI Root Bridge [PCI0] (0000:00)
    PCI: Probing PCI hardware (bus 00)
    PCI: Firmware left 0000:00:09.0 e100 interrupts enabled, disabling
    PCI: enabled onboard AC97/MC97 devices
    ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
    ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 7 10 *11 14 15)
    ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 7 *10 11 14 15)
    ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 7 10 11 14 15)
    ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 7 10 11 14 15) *0, disabled.
    ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 7 10 11 14 15) *0, disabled.
    ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 7 10 11 14 15) *0, disabled.
    ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 7 10 11 14 15) *0, disabled.
    ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 7 10 11 14 15) *0, disabled.
    Linux Plug and Play Support v0.97 (c) Adam Belay
    pnp: PnP ACPI init
    ACPI: bus type pnp registered
    pnp: PnP ACPI: found 13 devices
    ACPI: ACPI bus type pnp unregistered
    PnPBIOS: Disabled by ACPI PNP
    PCI: Using ACPI for IRQ routing
    PCI: If a device doesn't work, try "pci=routeirq". If it helps, post a
    report
    NET: Registered protocol family 8
    NET: Registered protocol family 20
    ACPI: RTC can wake from S4
    pnp: 00:09: iomem range 0xfec00000-0xfec00fff has been reserved
    pnp: 00:09: iomem range 0xfee00000-0xfee00fff has been reserved
    pnp: 00:09: iomem range 0xfff80000-0xffffffff could not be reserved
    pnp: 00:0c: iomem range 0x0-0x9ffff could not be reserved
    pnp: 00:0c: iomem range 0xc0000-0xdffff could not be reserved
    pnp: 00:0c: iomem range 0xe0000-0xfffff could not be reserved
    pnp: 00:0c: iomem range 0x100000-0x1ffeffff could not be reserved
    Time: tsc clocksource has been installed.
    PCI: Bridge: 0000:00:01.0
    IO window: disabled.
    MEM window: f9500000-fd6fffff
    PREFETCH window: e1400000-f13fffff
    PCI: Setting latency timer of device 0000:00:01.0 to 64
    NET: Registered protocol family 2
    IP route cache hash table entries: 4096 (order: 2, 16384 bytes)
    TCP established hash table entries: 16384 (order: 5, 196608 bytes)
    TCP bind hash table entries: 16384 (order: 5, 131072 bytes)
    TCP: Hash tables configured (established 16384 bind 16384)
    TCP reno registered
    checking if image is initramfs... it is
    Freeing initrd memory: 1305k freed
    audit: initializing netlink socket (disabled)
    audit(1218577017.172:1): initialized
    VFS: Disk quotas dquot_6.5.1
    Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
    io scheduler noop registered
    io scheduler anticipatory registered
    io scheduler deadline registered
    io scheduler cfq registered (default)
    PCI: VIA PCI bridge detected. Disabling DAC.
    Boot video device is 0000:01:00.0
    isapnp: Scanning for PnP cards...
    Switched to high resolution mode on CPU 0
    isapnp: No Plug & Play device found
    Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing enabled
    00:0a: ttyS0 at I/O 0x2f8 (irq = 3) is a 16550A
    00:0b: ttyS1 at I/O 0x3f8 (irq = 4) is a 16550A
    RAMDISK driver initialized: 16 RAM disks of 8192K size 1024 blocksize
    PNP: PS/2 Controller [PNP0303:PS2K,PNP0f03:PS2M] at 0x60,0x64 irq 1,12
    serio: i8042 KBD port at 0x60,0x64 irq 1
    serio: i8042 AUX port at 0x60,0x64 irq 12
    mice: PS/2 mouse device common for all mice
    TCP bic registered
    NET: Registered protocol family 1
    NET: Registered protocol family 17
    Using IPI No-Shortcut mode
    Freeing unused kernel memory: 244k freed
    Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
    ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
    VP_IDE: IDE controller at PCI slot 0000:00:0f.1
    ACPI: PCI Interrupt 0000:00:0f.1[A] -> GSI 20 (level, low) -> IRQ 16
    VP_IDE: chipset revision 6
    VP_IDE: not 100% native mode: will probe irqs later
    VP_IDE: VIA vt8237 (rev 00) IDE UDMA133 controller on pci0000:00:0f.1
    ide0: BM-DMA at 0xfc00-0xfc07, BIOS settings: hdaMA, hdbMA
    ide1: BM-DMA at 0xfc08-0xfc0f, BIOS settings: hdcMA, hddio
    Probing IDE interface ide0...
    input: AT Translated Set 2 keyboard as /class/input/input0
    hda: ST380011A, ATA DISK drive
    hdb: QUANTUM FIREBALL EX6.4A, ATA DISK drive
    ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
    Probing IDE interface ide1...
    hdc: TOSHIBA DVD-ROM SD-M1912, ATAPI CD/DVD-ROM drive
    ide1 at 0x170-0x177,0x376 on irq 15
    SCSI subsystem initialized
    libata version 2.21 loaded.
    hda: max request size: 512KiB
    hda: 156301488 sectors (80026 MB) w/2048KiB Cache, CHS=16383/255/63,
    UDMA(100)
    hda: cache flushes supported
    hda: hda1 hda2 < hda5 hda6 hda7 hda8 hda9 hda10 hda11 hda12 >
    hdb: max request size: 128KiB
    hdb: 12594960 sectors (6448 MB) w/418KiB Cache, CHS=13328/15/63, UDMA(33)
    hdb: cache flushes not supported
    hdb: hdb1
    kjournald starting. Commit interval 5 seconds
    EXT3-fs: mounted filesystem with ordered data mode.
    input: PC Speaker as /class/input/input1
    pci_hotplug: PCI Hot Plug PCI Core version: 0.5
    shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
    Real Time Clock Driver v1.12ac
    Floppy drive(s): fd0 is 1.44M
    FDC 0 is a post-1991 82077
    usbcore: registered new interface driver usbfs
    usbcore: registered new interface driver hub
    usbcore: registered new device driver usb
    Linux agpgart interface v0.102 (c) Dave Jones
    hdc: ATAPI 48X DVD-ROM drive, 512kB Cache, UDMA(33)
    Uniform CD-ROM driver Revision: 3.20
    USB Universal Host Controller Interface driver v3.0
    ACPI: PCI Interrupt 0000:00:10.0[A] -> GSI 21 (level, low) -> IRQ 17
    uhci_hcd 0000:00:10.0: UHCI Host Controller
    uhci_hcd 0000:00:10.0: new USB bus registered, assigned bus number 1
    uhci_hcd 0000:00:10.0: irq 17, io base 0x0000dc00
    usb usb1: configuration #1 chosen from 1 choice
    hub 1-0:1.0: USB hub found
    hub 1-0:1.0: 2 ports detected
    e100: Intel(R) PRO/100 Network Driver, 3.5.17-k4-NAPI
    e100: Copyright(c) 1999-2006 Intel Corporation
    ACPI: PCI Interrupt 0000:00:10.1[A] -> GSI 21 (level, low) -> IRQ 17
    uhci_hcd 0000:00:10.1: UHCI Host Controller
    uhci_hcd 0000:00:10.1: new USB bus registered, assigned bus number 2
    uhci_hcd 0000:00:10.1: irq 17, io base 0x0000ec00
    usb usb2: configuration #1 chosen from 1 choice
    hub 2-0:1.0: USB hub found
    hub 2-0:1.0: 2 ports detected
    ACPI: PCI Interrupt 0000:00:10.2[B] -> GSI 21 (level, low) -> IRQ 17
    uhci_hcd 0000:00:10.2: UHCI Host Controller
    uhci_hcd 0000:00:10.2: new USB bus registered, assigned bus number 3
    uhci_hcd 0000:00:10.2: irq 17, io base 0x0000c000
    usb usb3: configuration #1 chosen from 1 choice
    hub 3-0:1.0: USB hub found
    hub 3-0:1.0: 2 ports detected
    ACPI: PCI Interrupt 0000:00:10.3[B] -> GSI 21 (level, low) -> IRQ 17
    uhci_hcd 0000:00:10.3: UHCI Host Controller
    uhci_hcd 0000:00:10.3: new USB bus registered, assigned bus number 4
    uhci_hcd 0000:00:10.3: irq 17, io base 0x0000c400
    usb usb4: configuration #1 chosen from 1 choice
    hub 4-0:1.0: USB hub found
    hub 4-0:1.0: 2 ports detected
    ACPI: PCI Interrupt 0000:00:10.4[C] -> GSI 21 (level, low) -> IRQ 17
    ehci_hcd 0000:00:10.4: EHCI Host Controller
    ehci_hcd 0000:00:10.4: new USB bus registered, assigned bus number 5
    ehci_hcd 0000:00:10.4: irq 17, io mem 0xfd700000
    ehci_hcd 0000:00:10.4: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
    usb usb5: configuration #1 chosen from 1 choice
    hub 5-0:1.0: USB hub found
    hub 5-0:1.0: 8 ports detected
    input: ImPS/2 Generic Wheel Mouse as /class/input/input2
    agpgart: Detected AGP bridge 0
    agpgart: AGP aperture is 64M @ 0xf4000000
    sata_via 0000:00:0f.0: version 2.2
    ACPI: PCI Interrupt 0000:00:0f.0[B] -> GSI 20 (level, low) -> IRQ 16
    sata_via 0000:00:0f.0: routed to hard irq line 10
    scsi0 : sata_via
    scsi1 : sata_via
    ata1: SATA max UDMA/133 cmd 0x0001e800 ctl 0x0001e402 bmdma 0x0001d400
    irq 16
    ata2: SATA max UDMA/133 cmd 0x0001e000 ctl 0x0001d802 bmdma 0x0001d408
    irq 16
    ata1: SATA link down 1.5 Gbps (SStatus 0 SControl 300)
    ata2: SATA link down 1.5 Gbps (SStatus 0 SControl 300)
    ACPI: PCI Interrupt 0000:00:09.0[A] -> GSI 16 (level, low) -> IRQ 18
    e100: eth0: e100_probe: addr 0xfdc00000, irq 18, MAC addr 000:B7:85:0A:3F
    PCI: Enabling device 0000:00:11.6 (0000 -> 0001)
    ACPI: PCI Interrupt 0000:00:11.6[C] -> GSI 22 (level, low) -> IRQ 19
    usb 2-2: new low speed USB device using uhci_hcd and address 2
    PCI: Setting latency timer of device 0000:00:11.6 to 64
    usb 2-2: configuration #1 chosen from 1 choice
    usbcore: registered new interface driver hiddev
    ACPI: PCI interrupt for device 0000:00:11.6 disabled
    VIA 82xx Modem: probe of 0000:00:11.6 failed with error -13
    ACPI: PCI Interrupt 0000:00:11.5[C] -> GSI 22 (level, low) -> IRQ 19
    PCI: Setting latency timer of device 0000:00:11.5 to 64
    codec_read: codec 0 is not valid [0xfe0000]
    codec_read: codec 0 is not valid [0xfe0000]
    codec_read: codec 0 is not valid [0xfe0000]
    codec_read: codec 0 is not valid [0xfe0000]
    hiddev96: USB HID v1.10 Device [American Power Conversion Back-UPS RS
    1500 FW:8.g8 .D USB FW:g8 ] on usb-0000:00:10.1-2
    usbcore: registered new interface driver usbhid
    drivers/hid/usbhid/hid-core.c: v2.6:USB HID core driver
    Adding 2361512k swap on /dev/hda10. Priority:-1 extents:1 across:2361512k
    EXT3 FS on hda1, internal journal
    loop: module loaded
    w83627hf: Found W83697HF chip at 0x290
    fuse init (API version 7.8)
    device-mapper: ioctl: 4.11.0-ioctl (2006-10-12) initialised:
    dm-devel@redhat.com
    kjournald starting. Commit interval 5 seconds
    EXT3 FS on hda5, internal journal
    EXT3-fs: mounted filesystem with ordered data mode.
    kjournald starting. Commit interval 5 seconds
    EXT3 FS on hda6, internal journal
    EXT3-fs: mounted filesystem with ordered data mode.
    kjournald starting. Commit interval 5 seconds
    EXT3 FS on hda7, internal journal
    EXT3-fs: mounted filesystem with ordered data mode.
    kjournald starting. Commit interval 5 seconds
    EXT3 FS on hda8, internal journal
    EXT3-fs: mounted filesystem with ordered data mode.
    kjournald starting. Commit interval 5 seconds
    EXT3 FS on hda9, internal journal
    EXT3-fs: mounted filesystem with ordered data mode.
    kjournald starting. Commit interval 5 seconds
    EXT3 FS on hda11, internal journal
    EXT3-fs: mounted filesystem with ordered data mode.
    kjournald starting. Commit interval 5 seconds
    EXT3 FS on hda12, internal journal
    EXT3-fs: mounted filesystem with ordered data mode.
    ext3: No journal on filesystem on hdb1
    ip_tables: (C) 2000-2006 Netfilter Core Team
    Netfilter messages via NETLINK v0.30.
    nf_conntrack version 0.5.0 (4089 buckets, 32712 max)
    e100: eth0: e100_watchdog: link up, 100Mbps, full-duplex
    NET: Registered protocol family 10
    lo: Disabled Privacy Extensions
    input: Power Button (FF) as /class/input/input3
    ACPI: Power Button (FF) [PWRF]
    input: Power Button (CM) as /class/input/input4
    ACPI: Power Button (CM) [PWRB]
    input: Sleep Button (CM) as /class/input/input5
    ACPI: Sleep Button (CM) [SLPB]
    eth0: no IPv6 routers present
    vboxdrv: Trying to deactivate the NMI watchdog permanently...
    vboxdrv: Successfully done.
    vboxdrv: Found 1 processor cores.
    vboxdrv: fAsync=0 u64DiffCores=1.
    vboxdrv: TSC mode is 'synchronous', kernel timer mode is 'normal'.
    vboxdrv: Successfully loaded version 1.6.4 (interface 0x00080000).
    vmmon: module license 'unspecified' taints kernel.
    [2923]: VMCI: Driver initialized.
    [2923]: Module vmmon: registered with major=10 minor=165
    [2923]: Module vmmon: initialized
    /dev/vmnet: open called by PID 2952 (vmnet-bridge)
    /dev/vmnet: hub 0 does not exist, allocating memory.
    /dev/vmnet: port on hub 0 successfully opened
    bridge-eth0: enabling the bridge
    bridge-eth0: up
    bridge-eth0: already up
    bridge-eth0: attached
    /dev/vmnet: open called by PID 2966 (vmnet-natd)
    /dev/vmnet: hub 8 does not exist, allocating memory.
    /dev/vmnet: port on hub 8 successfully opened
    powernow-k8: Found 1 AMD Athlon(tm) 64 Processor 3200+ processors
    (version 2.00.00)
    powernow-k8: 0 : fid 0xe (2200 MHz), vid 0x2
    powernow-k8: 1 : fid 0xc (2000 MHz), vid 0x6
    powernow-k8: 2 : fid 0xa (1800 MHz), vid 0xa
    powernow-k8: 3 : fid 0x2 (1000 MHz), vid 0x12
    Marking TSC unstable due to: cpufreq changes.
    Time: acpi_pm clocksource has been installed.
    Clocksource tsc unstable (delta = -176950529 ns)
    /dev/vmnet: open called by PID 3029 (vmnet-netifup)
    /dev/vmnet: hub 1 does not exist, allocating memory.
    /dev/vmnet: port on hub 1 successfully opened
    /dev/vmnet: open called by PID 3030 (vmnet-netifup)
    /dev/vmnet: port on hub 8 successfully opened
    /dev/vmnet: open called by PID 3066 (vmnet-dhcpd)
    /dev/vmnet: port on hub 1 successfully opened
    /dev/vmnet: open called by PID 3047 (vmnet-dhcpd)
    /dev/vmnet: port on hub 8 successfully opened
    vmnet8: no IPv6 routers present
    vmnet1: no IPv6 routers present
    ext3: No journal on filesystem on hdb1
    kjournald starting. Commit interval 5 seconds
    EXT3 FS on hdb1, internal journal
    EXT3-fs: mounted filesystem with ordered data mode.
    hda: status error: status=0xd0 { Busy }
    ide: failed opcode was: unknown
    hda: DMA disabled
    hdb: DMA disabled
    hda: drive not ready for command
    ide0: reset timed-out, status=0xd0
    hda: lost interrupt
    attempt to access beyond end of device
    hda5: rw=0, want=8877388712, limit=29302497
    attempt to access beyond end of device
    hda5: rw=0, want=8877388712, limit=29302497
    attempt to access beyond end of device
    hda5: rw=0, want=8877388584, limit=29302497
    attempt to access beyond end of device
    hda5: rw=0, want=8885842944, limit=29302497
    attempt to access beyond end of device
    hda5: rw=0, want=8877388712, limit=29302497
    hda: task_out_intr: status=0xd8 { Busy }
    ide: failed opcode was: unknown
    ide0: reset timed-out, status=0xd0
    end_request: I/O error, dev hda, sector 2806748
    Buffer I/O error on device hda5, logical block 278543
    lost page write due to I/O error on hda5
    end_request: I/O error, dev hda, sector 2806811
    Buffer I/O error on device hda5, logical block 278551
    lost page write due to I/O error on hda5
    end_request: I/O error, dev hda, sector 2806835
    Buffer I/O error on device hda5, logical block 278554
    lost page write due to I/O error on hda5
    end_request: I/O error, dev hda, sector 2806843
    Buffer I/O error on device hda5, logical block 278555
    lost page write due to I/O error on hda5
    end_request: I/O error, dev hda, sector 2806851
    Buffer I/O error on device hda5, logical block 278556
    lost page write due to I/O error on hda5
    end_request: I/O error, dev hda, sector 2806859
    Buffer I/O error on device hda5, logical block 278557
    lost page write due to I/O error on hda5
    end_request: I/O error, dev hda, sector 2806867
    Buffer I/O error on device hda5, logical block 278558
    lost page write due to I/O error on hda5
    end_request: I/O error, dev hda, sector 2806875
    Buffer I/O error on device hda5, logical block 278559
    lost page write due to I/O error on hda5
    end_request: I/O error, dev hda, sector 2806883
    Buffer I/O error on device hda5, logical block 278560
    lost page write due to I/O error on hda5
    end_request: I/O error, dev hda, sector 2806891
    Buffer I/O error on device hda5, logical block 278561
    lost page write due to I/O error on hda5
    end_request: I/O error, dev hda, sector 2806899
    end_request: I/O error, dev hda, sector 2806907
    end_request: I/O error, dev hda, sector 2806915
    end_request: I/O error, dev hda, sector 2806923
    end_request: I/O error, dev hda, sector 2806931
    end_request: I/O error, dev hda, sector 2806939
    end_request: I/O error, dev hda, sector 2806947
    end_request: I/O error, dev hda, sector 2806955
    end_request: I/O error, dev hda, sector 2807011
    end_request: I/O error, dev hda, sector 2807019
    end_request: I/O error, dev hda, sector 2807027
    end_request: I/O error, dev hda, sector 2807035
    end_request: I/O error, dev hda, sector 2807043
    end_request: I/O error, dev hda, sector 2807051
    end_request: I/O error, dev hda, sector 2807059
    end_request: I/O error, dev hda, sector 2807067
    end_request: I/O error, dev hda, sector 2807075
    end_request: I/O error, dev hda, sector 2807083
    end_request: I/O error, dev hda, sector 2807091
    end_request: I/O error, dev hda, sector 2807099
    end_request: I/O error, dev hda, sector 2807107
    end_request: I/O error, dev hda, sector 2807115
    end_request: I/O error, dev hda, sector 2807123
    end_request: I/O error, dev hda, sector 2807131
    end_request: I/O error, dev hda, sector 2807139
    end_request: I/O error, dev hda, sector 2807147
    end_request: I/O error, dev hda, sector 2807155
    end_request: I/O error, dev hda, sector 2807163
    end_request: I/O error, dev hda, sector 2807171
    end_request: I/O error, dev hda, sector 2807179
    end_request: I/O error, dev hda, sector 2807187
    end_request: I/O error, dev hda, sector 2807195
    end_request: I/O error, dev hda, sector 2807203
    end_request: I/O error, dev hda, sector 2807211
    end_request: I/O error, dev hda, sector 2807219
    end_request: I/O error, dev hda, sector 2807227
    end_request: I/O error, dev hda, sector 2807235
    end_request: I/O error, dev hda, sector 2807243
    end_request: I/O error, dev hda, sector 2807251
    end_request: I/O error, dev hda, sector 2807259
    end_request: I/O error, dev hda, sector 2807267
    end_request: I/O error, dev hda, sector 2807275
    end_request: I/O error, dev hda, sector 2807283
    end_request: I/O error, dev hda, sector 2807291
    end_request: I/O error, dev hda, sector 2807299
    end_request: I/O error, dev hda, sector 2807307
    end_request: I/O error, dev hda, sector 2807315
    end_request: I/O error, dev hda, sector 2807323
    end_request: I/O error, dev hda, sector 2807331
    end_request: I/O error, dev hda, sector 2807339
    end_request: I/O error, dev hda, sector 2807795
    end_request: I/O error, dev hda, sector 2825411
    end_request: I/O error, dev hda, sector 2885699
    end_request: I/O error, dev hda, sector 11893315
    end_request: I/O error, dev hda, sector 19903083
    end_request: I/O error, dev hda, sector 30929763
    end_request: I/O error, dev hda, sector 31717203
    end_request: I/O error, dev hda, sector 34075299
    end_request: I/O error, dev hda, sector 34075443
    end_request: I/O error, dev hda, sector 35911243
    end_request: I/O error, dev hda, sector 35911851
    end_request: I/O error, dev hda, sector 37483315
    end_request: I/O error, dev hda, sector 39648483
    end_request: I/O error, dev hda, sector 39648491
    end_request: I/O error, dev hda, sector 40871067
    end_request: I/O error, dev hda, sector 40873747
    end_request: I/O error, dev hda, sector 40873867
    end_request: I/O error, dev hda, sector 115275
    end_request: I/O error, dev hda, sector 115279
    end_request: I/O error, dev hda, sector 115281
    end_request: I/O error, dev hda, sector 115283
    end_request: I/O error, dev hda, sector 278745
    end_request: I/O error, dev hda, sector 578403
    end_request: I/O error, dev hda, sector 578411
    end_request: I/O error, dev hda, sector 1102723
    end_request: I/O error, dev hda, sector 1102747
    end_request: I/O error, dev hda, sector 2675555
    end_request: I/O error, dev hda, sector 2675563
    end_request: I/O error, dev hda, sector 2675619
    end_request: I/O error, dev hda, sector 2741115
    end_request: I/O error, dev hda, sector 2741163
    end_request: I/O error, dev hda, sector 2741171
    end_request: I/O error, dev hda, sector 2741347
    end_request: I/O error, dev hda, sector 2741459
    end_request: I/O error, dev hda, sector 2741467
    end_request: I/O error, dev hda, sector 2741475
    end_request: I/O error, dev hda, sector 2741483
    end_request: I/O error, dev hda, sector 2741491
    end_request: I/O error, dev hda, sector 2741523
    end_request: I/O error, dev hda, sector 2741603
    end_request: I/O error, dev hda, sector 2741611
    end_request: I/O error, dev hda, sector 2741771
    end_request: I/O error, dev hda, sector 2741779
    end_request: I/O error, dev hda, sector 2741915
    end_request: I/O error, dev hda, sector 2741923
    end_request: I/O error, dev hda, sector 2742067
    end_request: I/O error, dev hda, sector 39976827
    end_request: I/O error, dev hda, sector 39976875
    end_request: I/O error, dev hda, sector 115287
    end_request: I/O error, dev hda, sector 115297
    end_request: I/O error, dev hda, sector 115299
    end_request: I/O error, dev hda, sector 115303
    end_request: I/O error, dev hda, sector 115305
    end_request: I/O error, dev hda, sector 115307
    end_request: I/O error, dev hda, sector 115309
    end_request: I/O error, dev hda, sector 115311
    end_request: I/O error, dev hda, sector 115317
    end_request: I/O error, dev hda, sector 115319
    end_request: I/O error, dev hda, sector 115321
    end_request: I/O error, dev hda, sector 115323
    end_request: I/O error, dev hda, sector 115325
    end_request: I/O error, dev hda, sector 115327
    end_request: I/O error, dev hda, sector 115349
    end_request: I/O error, dev hda, sector 131191
    end_request: I/O error, dev hda, sector 262213
    end_request: I/O error, dev hda, sector 262215
    end_request: I/O error, dev hda, sector 262221
    end_request: I/O error, dev hda, sector 262223
    end_request: I/O error, dev hda, sector 262449
    end_request: I/O error, dev hda, sector 262565
    end_request: I/O error, dev hda, sector 262585
    end_request: I/O error, dev hda, sector 262609
    end_request: I/O error, dev hda, sector 262679
    Aborting journal on device hda7.
    end_request: I/O error, dev hda, sector 39976875
    end_request: I/O error, dev hda, sector 40871067
    end_request: I/O error, dev hda, sector 40873747
    end_request: I/O error, dev hda, sector 40873867
    __journal_remove_journal_head: freeing b_frozen_data
    __journal_remove_journal_head: freeing b_frozen_data
    __journal_remove_journal_head: freeing b_frozen_data
    Aborting journal on device hda5.
    end_request: I/O error, dev hda, sector 2741115
    end_request: I/O error, dev hda, sector 2741467
    end_request: I/O error, dev hda, sector 2741915
    end_request: I/O error, dev hda, sector 2806707
    end_request: I/O error, dev hda, sector 2806843
    end_request: I/O error, dev hda, sector 2806851
    end_request: I/O error, dev hda, sector 2806859
    end_request: I/O error, dev hda, sector 2806867
    end_request: I/O error, dev hda, sector 2806947
    end_request: I/O error, dev hda, sector 2807035
    end_request: I/O error, dev hda, sector 2807043
    end_request: I/O error, dev hda, sector 2807059
    end_request: I/O error, dev hda, sector 2807067
    end_request: I/O error, dev hda, sector 2807131
    end_request: I/O error, dev hda, sector 2807147
    end_request: I/O error, dev hda, sector 2741171
    end_request: I/O error, dev hda, sector 2741347
    end_request: I/O error, dev hda, sector 2741611
    ext3_abort called.
    EXT3-fs error (device hda7): ext3_journal_start_sb: Detected aborted journal
    Remounting filesystem read-only
    ext3_abort called.
    EXT3-fs error (device hda5): ext3_journal_start_sb: Detected aborted journal
    Remounting filesystem read-only
    end_request: I/O error, dev hda, sector 1102763
    EXT3-fs error (device hda5): ext3_get_inode_loc: unable to read inode
    block - inode=32883, block=65545
    end_request: I/O error, dev hda, sector 30929763
    EXT3-fs error (device hda6): ext3_get_inode_loc: unable to read inode
    block - inode=65052, block=131100
    end_request: I/O error, dev hda, sector 29880963
    printk: 145 messages suppressed.
    Buffer I/O error on device hda6, logical block 0
    lost page write due to I/O error on hda6
    EXT3-fs error (device hda6) in ext3_reserve_inode_write: IO failure
    end_request: I/O error, dev hda, sector 29880963
    Buffer I/O error on device hda6, logical block 0
    lost page write due to I/O error on hda6
    end_request: I/O error, dev hda, sector 5379
    end_request: I/O error, dev hda, sector 5381
    end_request: I/O error, dev hda, sector 5383
    Aborting journal on device hda1.
    end_request: I/O error, dev hda, sector 2151299
    EXT3-fs error (device hda5): ext3_get_inode_loc: unable to read inode
    block - inode=98115, block=196612
    ext3_abort called.
    EXT3-fs error (device hda1): ext3_journal_start_sb: Detected aborted journal
    Remounting filesystem read-only
    end_request: I/O error, dev hda, sector 37483315
    EXT3-fs error (device hda6): ext3_get_inode_loc: unable to read inode
    block - inode=466454, block=950294
    end_request: I/O error, dev hda, sector 29880963
    printk: 1 messages suppressed.
    Buffer I/O error on device hda6, logical block 0
    lost page write due to I/O error on hda6
    EXT3-fs error (device hda6) in ext3_reserve_inode_write: IO failure
    end_request: I/O error, dev hda, sector 29880963
    end_request: I/O error, dev hda, sector 1889155
    EXT3-fs error (device hda5): ext3_get_inode_loc: unable to read inode
    block - inode=81764, block=163844
    end_request: I/O error, dev hda, sector 30929763
    EXT3-fs error (device hda6): ext3_get_inode_loc: unable to read inode
    block - inode=65052, block=131100
    end_request: I/O error, dev hda, sector 29880963
    EXT3-fs error (device hda6) in ext3_reserve_inode_write: IO failure
    end_request: I/O error, dev hda, sector 29880963
    end_request: I/O error, dev hda, sector 1102723
    EXT3-fs error (device hda5): ext3_get_inode_loc: unable to read inode
    block - inode=32712, block=65540
    end_request: I/O error, dev hda, sector 6083459
    EXT3-fs error (device hda5): ext3_get_inode_loc: unable to read inode
    block - inode=343393, block=688132
    end_request: I/O error, dev hda, sector 1102811
    EXT3-fs error (device hda5): ext3_get_inode_loc: unable to read inode
    block - inode=33086, block=65551
    end_request: I/O error, dev hda, sector 1102811
    EXT3-fs error (device hda5): ext3_get_inode_loc: unable to read inode
    block - inode=33087, block=65551
    end_request: I/O error, dev hda, sector 1102819
    EXT3-fs error (device hda5): ext3_get_inode_loc: unable to read inode
    block - inode=33112, block=65552
    end_request: I/O error, dev hda, sector 7394579
    EXT3-fs error (device hda5): ext3_get_inode_loc: unable to read inode
    block - inode=426780, block=852022
    end_request: I/O error, dev hda, sector 1103747
    EXT3-fs error (device hda5): ext3_get_inode_loc: unable to read inode
    block - inode=36808, block=65668
    end_request: I/O error, dev hda, sector 6083523
    EXT3-fs error (device hda5): ext3_get_inode_loc: unable to read inode
    block - inode=343650, block=688140
    end_request: I/O error, dev hda, sector 1102763
    EXT3-fs error (device hda5): ext3_get_inode_loc: unable to read inode
    block - inode=32894, block=65545
    end_request: I/O error, dev hda, sector 1102723
    EXT3-fs error (device hda5): ext3_get_inode_loc: unable to read inode
    block - inode=32713, block=65540
    end_request: I/O error, dev hda, sector 1102827
    EXT3-fs error (device hda5): ext3_get_inode_loc: unable to read inode
    block - inode=33125, block=65553
    end_request: I/O error, dev hda, sector 3199875
    EXT3-fs error (device hda5): ext3_get_inode_loc: unable to read inode
    block - inode=163524, block=327684
    end_request: I/O error, dev hda, sector 3462723
    EXT3-fs error (device hda5): ext3_get_inode_loc: unable to read inode
    block - inode=182707, block=360540
    end_request: I/O error, dev hda, sector 29890819
    Aborting journal on device hda6.
    ext3_abort called.
    EXT3-fs error (device hda6): ext3_journal_start_sb: Detected aborted journal
    Remounting filesystem read-only
    end_request: I/O error, dev hda, sector 40697075
    printk: 4 messages suppressed.
    Buffer I/O error on device hda7, logical block 131074
    lost page write due to I/O error on hda7
    end_request: I/O error, dev hda, sector 40697083
    Buffer I/O error on device hda7, logical block 131075
    lost page write due to I/O error on hda7
    end_request: I/O error, dev hda, sector 40697091
    Buffer I/O error on device hda7, logical block 131076
    lost page write due to I/O error on hda7
    end_request: I/O error, dev hda, sector 2675587
    end_request: I/O error, dev hda, sector 2675595
    end_request: I/O error, dev hda, sector 2675643
    end_request: I/O error, dev hda, sector 2675651
    end_request: I/O error, dev hda, sector 262603
    printk: 4 messages suppressed.
    Buffer I/O error on device hda1, logical block 131270
    lost page write due to I/O error on hda1

    I had to power off and on my PC (couldn't do a normal shutdown and the
    reset button didn't work).


    Things were calm for maybe 10 minutes, then again:
    hdb: dma_timer_expiry: dma status == 0x61
    hdb: DMA timeout error
    hdb: dma timeout error: status=0x58 { DriveReady SeekComplete DataRequest }
    ide: failed opcode was: unknown
    hda: DMA disabled
    hdb: DMA disabled
    ide0: reset: success

    I ran smartctl -a on both drives:
    # smartctl -a /dev/hda
    smartctl version 5.38 [i686-pc-linux-gnu] Copyright (C) 2002-8 Bruce Allen
    Home page is http://smartmontools.sourceforge.net/

    === START OF INFORMATION SECTION ===
    Model Family: Seagate Barracuda 7200.7 and 7200.7 Plus family
    Device Model: ST380011A
    Serial Number: 4JV5P7LN
    Firmware Version: 8.01
    User Capacity: 80,026,361,856 bytes
    Device is: In smartctl database [for details use: -P show]
    ATA Version is: 6
    ATA Standard is: ATA/ATAPI-6 T13 1410D revision 2
    Local Time is: Tue Aug 12 22:15:59 2008 PDT
    SMART support is: Available - device has SMART capability.
    SMART support is: Enabled

    === START OF READ SMART DATA SECTION ===
    SMART overall-health self-assessment test result: PASSED

    General SMART Values:
    Offline data collection status: (0x82) Offline data collection activity
    was completed without error.
    Auto Offline Data Collection:
    Enabled.
    Self-test execution status: ( 0) The previous self-test routine
    completed
    without error or no self-test
    has ever
    been run.
    Total time to complete Offline
    data collection: ( 430) seconds.
    Offline data collection
    capabilities: (0x5b) SMART execute Offline immediate.
    Auto Offline data collection
    on/off support.
    Suspend Offline collection upon new
    command.
    Offline surface scan supported.
    Self-test supported.
    No Conveyance Self-test supported.
    Selective Self-test supported.
    SMART capabilities: (0x0003) Saves SMART data before entering
    power-saving mode.
    Supports SMART auto save timer.
    Error logging capability: (0x01) Error logging supported.
    General Purpose Logging supported.
    Short self-test routine
    recommended polling time: ( 1) minutes.
    Extended self-test routine
    recommended polling time: ( 58) minutes.

    SMART Attributes Data Structure revision number: 10
    Vendor Specific SMART Attributes with Thresholds:
    ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE
    UPDATED WHEN_FAILED RAW_VALUE
    1 Raw_Read_Error_Rate 0x000f 060 057 006 Pre-fail
    Always - 81109586
    3 Spin_Up_Time 0x0003 098 098 000 Pre-fail
    Always - 0
    4 Start_Stop_Count 0x0032 100 100 020 Old_age
    Always - 0
    5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail
    Always - 0
    7 Seek_Error_Rate 0x000f 082 060 030 Pre-fail
    Always - 195706519
    9 Power_On_Hours 0x0032 075 075 000 Old_age
    Always - 22212
    10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail
    Always - 0
    12 Power_Cycle_Count 0x0032 100 100 020 Old_age
    Always - 120
    194 Temperature_Celsius 0x0022 032 048 000 Old_age Always
    - 32
    195 Hardware_ECC_Recovered 0x001a 060 057 000 Old_age Always
    - 81109586
    197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always
    - 0
    198 Offline_Uncorrectable 0x0010 100 100 000 Old_age
    Offline - 0
    199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always
    - 0
    200 Multi_Zone_Error_Rate 0x0000 100 253 000 Old_age
    Offline - 0
    202 TA_Increase_Count 0x0032 100 253 000 Old_age Always
    - 0

    SMART Error Log Version: 1
    No Errors Logged

    SMART Self-test log structure revision number 1
    Num Test_Description Status Remaining
    LifeTime(hours) LBA_of_first_error
    # 1 Extended offline Completed without error 00% 18951
    -
    # 2 Extended offline Completed without error 00% 18674
    -
    # 3 Extended offline Completed without error 00% 15957
    -
    # 4 Extended offline Completed without error 00% 14448
    -

    SMART Selective self-test log data structure revision number 1
    SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
    1 0 0 Not_testing
    2 0 0 Not_testing
    3 0 0 Not_testing
    4 0 0 Not_testing
    5 0 0 Not_testing
    Selective self-test flags (0x0):
    After scanning selected spans, do NOT read-scan remainder of disk.
    If Selective self-test is pending on power-up, resume after 0 minute delay.

    # smartctl -a /dev/hdb
    smartctl version 5.38 [i686-pc-linux-gnu] Copyright (C) 2002-8 Bruce Allen
    Home page is http://smartmontools.sourceforge.net/

    === START OF INFORMATION SECTION ===
    Device Model: QUANTUM FIREBALL EX6.4A
    Serial Number: 376833611720
    Firmware Version: A0A.0D00
    User Capacity: 6,448,619,520 bytes
    Device is: In smartctl database [for details use: -P show]
    ATA Version is: 4
    ATA Standard is: ATA/ATAPI-4 T13 1153D revision 15
    Local Time is: Tue Aug 12 22:16:25 2008 PDT
    SMART support is: Available - device has SMART capability.
    SMART support is: Enabled

    Error SMART Status command failed: Input/output error
    A mandatory SMART command failed: exiting. To continue, add one or more
    '-T permissive' options.

    Then, my Linux pauses becuse hdb went funky. I rechecked my dmesg (might
    old dupes from earlier):
    hdb: dma_timer_expiry: dma status == 0x61
    hdb: DMA timeout error
    hdb: dma timeout error: status=0x58 { DriveReady SeekComplete DataRequest }
    ide: failed opcode was: unknown
    hda: DMA disabled
    hdb: DMA disabled
    ide0: reset: success
    hdb: drive_cmd: status=0x7d { DriveReady DeviceFault SeekComplete
    DataRequest CorrectedError Error }
    hdb: drive_cmd: error=0x7d { DriveStatusError UncorrectableError
    SectorIdNotFound AddrMarkNotFound }, LBAsect=226327933, sector=0
    ide: failed opcode was: 0xb0
    hdb: dma_timer_expiry: dma status == 0x61
    hdb: DMA timeout error
    hdb: dma timeout error: status=0x58 { DriveReady SeekComplete DataRequest }
    ide: failed opcode was: unknown
    hda: DMA disabled
    hdb: DMA disabled
    ide0: reset: success
    hdb: dma_timer_expiry: dma status == 0x61
    hdb: DMA timeout error
    hdb: dma timeout error: status=0x58 { DriveReady SeekComplete DataRequest }
    ide: failed opcode was: unknown
    hda: DMA disabled
    hdb: DMA disabled
    ide0: reset: success
    hdb: dma_timer_expiry: dma status == 0x41
    hdb: DMA timeout error
    hdb: dma timeout error: status=0x58 { DriveReady SeekComplete DataRequest }
    ide: failed opcode was: unknown
    hdb: DMA disabled
    ide0: reset: success


    # smartctl -a /dev/hdb
    smartctl version 5.38 [i686-pc-linux-gnu] Copyright (C) 2002-8 Bruce Allen
    Home page is http://smartmontools.sourceforge.net/

    === START OF INFORMATION SECTION ===
    Device Model: QUANTUM FIREBALL EX6.4A
    Serial Number: 376833611720
    Firmware Version: A0A.0D00
    User Capacity: 6,448,619,520 bytes
    Device is: In smartctl database [for details use: -P show]
    ATA Version is: 4
    ATA Standard is: ATA/ATAPI-4 T13 1153D revision 15
    Local Time is: Tue Aug 12 22:19:21 2008 PDT
    SMART support is: Available - device has SMART capability.
    SMART support is: Enabled

    === START OF READ SMART DATA SECTION ===
    SMART overall-health self-assessment test result: PASSED

    General SMART Values:
    Offline data collection status: (0x82) Offline data collection activity
    was completed without error.
    Auto Offline Data Collection:
    Enabled.
    Total time to complete Offline
    data collection: ( 1) seconds.
    Offline data collection
    capabilities: (0x03) SMART execute Offline immediate.
    Auto Offline data collection
    on/off support.
    Suspend Offline collection upon new
    command.
    No Offline surface scan supported.
    No Self-test supported.
    No Conveyance Self-test supported.
    No Selective Self-test supported.
    SMART capabilities: (0x0003) Saves SMART data before entering
    power-saving mode.
    Supports SMART auto save timer.
    Error logging capability: (0x00) Error logging NOT supported.
    No General Purpose Logging support.

    SMART Attributes Data Structure revision number: 7
    Vendor Specific SMART Attributes with Thresholds:
    ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE
    UPDATED WHEN_FAILED RAW_VALUE
    1 Raw_Read_Error_Rate 0x0029 100 100 020 Pre-fail
    Offline - 0
    3 Spin_Up_Time 0x0027 089 076 020 Pre-fail
    Always - 1489
    4 Start_Stop_Count 0x0032 099 099 008 Old_age
    Always - 1198
    5 Reallocated_Sector_Ct 0x0033 100 100 020 Pre-fail
    Always - 0
    7 Seek_Error_Rate 0x000b 100 100 023 Pre-fail
    Always - 0
    9 Power_On_Hours 0x0012 007 007 001 Old_age
    Always - 61139
    11 Calibration_Retry_Count 0x0013 100 100 020 Pre-fail
    Always - 0
    12 Power_Cycle_Count 0x0032 099 099 008 Old_age
    Always - 1191
    13 Read_Soft_Error_Rate 0x000b 100 100 023 Pre-fail
    Always - 0
    199 UDMA_CRC_Error_Count 0x001a 200 200 000 Old_age Always
    - 0

    Warning: device does not support Error Logging
    SMART Error Log Version: 0
    No Errors Logged

    Warning: device does not support Self Test Logging
    SMART Self-test log structure revision number 0
    Warning: ATA Specification requires self-test log structure revision
    number = 1
    No self-tests have been logged. [To run self-tests, use: smartctl -t]


    Device does not support Selective Self Tests/Logging


    What's going on with my HDDs? I am not a hardware and Linux/Debian
    expert. My hardware specifications can be found here:
    http://alpha.zimage.com/~ant/antfarm.../computers.txt
    (secondary/backup computer). For now, I am going to unmount /dev/hdb to
    see if hdb is causing all this madness.

    Thank you in advance.
    --
    /\___/\
    / /\ /\ \ Phil/Ant @ http://antfarm.home.dhs.org (Personal Web Site)
    | |o o| | Ant's Quality Foraged Links (AQFL): http://aqfl.net
    \ _ / Remove ANT from e-mail address: philpi@earthlink.netANT
    ( ) or ANTant@zimage.com
    Ant is currently not listening to any songs on his home computer.

  2. Re: Bad disk controller? Dying HDD?

    On Wednesday 13 August 2008 07:21, someone identifying as *Ant* wrote
    in /comp.os.linux.hardware:/

    > Hi. My old mini-tower PC's HDDs are acting crazy today. I came home and
    > noticed my second drive wasn't there so I checked dmesg (deleted normal
    > logs before hdb):
    >
    > hdb: dma_timer_expiry: dma status == 0x61
    > hdb: DMA timeout error
    > hdb: dma timeout error: status=0x58 { DriveReady SeekComplete
    > DataRequest }
    > ide: failed opcode was: unknown
    > hda: DMA disabled
    > hdb: DMA disabled
    > ide0: reset: success
    > hdb: dma_intr: status=0x7d { DriveReady DeviceFault SeekComplete
    > DataRequest CorrectedError Error }
    > [...]
    >
    > What's going on with my HDDs? I am not a hardware and Linux/Debian
    > expert.


    It looks like you have a hardware problem, and it could be either the IDE
    controller itself, the IDE ribbon from the controller to your hard disk, or
    the hard disks themselves.

    It is hard to tell at this stage which is the culprit, but common sense
    tells me that hard disks tend to fail faster than the other two components
    in the list of suspects.

    The best advice I can give you - I do hope you've made backups - is to
    replace the disk as soon as possible. Don't try anything foolish like
    repairing disk sectors or anything, because you'd only be trying to
    resuscitate a corpse that's been dead for weeks.

    Just my two cents worth... ;-)

    --
    *Aragorn*
    (registered GNU/Linux user #223157)

  3. Re: Bad disk controller? Dying HDD?

    On 8/12/2008 10:46 PM PT, Aragorn typed:

    > On Wednesday 13 August 2008 07:21, someone identifying as *Ant* wrote
    > in /comp.os.linux.hardware:/
    >
    >> Hi. My old mini-tower PC's HDDs are acting crazy today. I came home and
    >> noticed my second drive wasn't there so I checked dmesg (deleted normal
    >> logs before hdb):
    >>
    >> hdb: dma_timer_expiry: dma status == 0x61
    >> hdb: DMA timeout error
    >> hdb: dma timeout error: status=0x58 { DriveReady SeekComplete
    >> DataRequest }
    >> ide: failed opcode was: unknown
    >> hda: DMA disabled
    >> hdb: DMA disabled
    >> ide0: reset: success
    >> hdb: dma_intr: status=0x7d { DriveReady DeviceFault SeekComplete
    >> DataRequest CorrectedError Error }
    >> [...]
    >>
    >> What's going on with my HDDs? I am not a hardware and Linux/Debian
    >> expert.

    >
    > It looks like you have a hardware problem, and it could be either the IDE
    > controller itself, the IDE ribbon from the controller to your hard disk, or
    > the hard disks themselves.
    >
    > It is hard to tell at this stage which is the culprit, but common sense
    > tells me that hard disks tend to fail faster than the other two components
    > in the list of suspects.
    >
    > The best advice I can give you - I do hope you've made backups - is to
    > replace the disk as soon as possible. Don't try anything foolish like
    > repairing disk sectors or anything, because you'd only be trying to
    > resuscitate a corpse that's been dead for weeks.
    >
    > Just my two cents worth... ;-)


    Yeah, I have a backup of my important datas (not the whole drives -- I
    need to reinstall Debian from scratch eventually). So far, no
    reoccurrences after unmounting hdb, but then I have been AFK. Again, I
    was gone all day earlier. :P
    --
    "I once heard the survivors of a colony of ants that had been partially
    obliterated by a cow's foot seriously debating the intention of the gods
    towards their civilization" --Archy the ****roach from Don Marquis'
    "Archy and Mehitabel" book ("Certain Maxims of Archy" poem)
    /\___/\
    / /\ /\ \ Phil/Ant @ http://antfarm.home.dhs.org (Personal Web Site)
    | |o o| | Ant's Quality Foraged Links (AQFL): http://aqfl.net
    \ _ / Remove ANT from e-mail address: philpi@earthlink.netANT
    ( ) or ANTant@zimage.com
    Ant is currently not listening to any songs on his home computer.

  4. Re: Bad disk controller? Dying HDD?

    Ant wrote:
    > Hi. My old mini-tower PC's HDDs are acting crazy today. I came home
    > and noticed my second drive wasn't there so I checked dmesg (deleted
    > normal logs before hdb):
    >
    > hdb: dma_timer_expiry: dma status == 0x61
    > hdb: DMA timeout error
    > hdb: dma timeout error: status=0x58 { DriveReady SeekComplete
    > DataRequest }
    > ide: failed opcode was: unknown
    > hda: DMA disabled
    > hdb: DMA disabled
    > ide0: reset: success
    > hdb: dma_intr: status=0x7d { DriveReady DeviceFault SeekComplete
    > DataRequest CorrectedError Error }
    > hdb: dma_intr: error=0x7d { DriveStatusError UncorrectableError
    > SectorIdNotFound AddrMarkNotFound }, LBAsect=226327933, sector=3522545
    > ide: failed opcode was: unknown
    > hdb: DMA disabled
    > ide0: reset: success
    > hdb: task_in_intr: status=0x7d { DriveReady DeviceFault SeekComplete
    > DataRequest CorrectedError Error }
    > hdb: task_in_intr: error=0x7d { DriveStatusError UncorrectableError
    > SectorIdNotFound AddrMarkNotFound }, LBAsect=226327933, sector=2362513
    > ide: failed opcode was: unknown
    > ide0: reset: success
    > hdb: task_in_intr: status=0x7d { DriveReady DeviceFault SeekComplete
    > DataRequest CorrectedError Error }
    > hdb: task_in_intr: error=0x7d { DriveStatusError UncorrectableError
    > SectorIdNotFound AddrMarkNotFound }, LBAsect=226327933, sector=2362513
    > ide: failed opcode was: unknown
    > ide0: reset: success
    > ABORTED IN=eth0 OUT= MAC=00:d0:b7:85:0a:3f:00:a0:c5:e3:18:a8:08:00
    > SRC=216.86.199.5 DST=192.168.0.32 LEN=40 TOS=0x00 PREC=0x00 TTL=46
    > ID=15957 DF PROTO=TCP SPT=6667 DPT=1788 SEQ=2622437680 ACK=0 WINDOW=0
    > RES=0x00 RST URGP=0
    > hdb: task_in_intr: status=0x7d { DriveReady DeviceFault SeekComplete
    > DataRequest CorrectedError Error }
    > hdb: task_in_intr: error=0x7d { DriveStatusError UncorrectableError
    > SectorIdNotFound AddrMarkNotFound }, LBAsect=226327933, sector=3537401
    > ide: failed opcode was: unknown
    > ide0: reset: success
    > hdb: task_in_intr: status=0x7d { DriveReady DeviceFault SeekComplete
    > DataRequest CorrectedError Error }
    > hdb: task_in_intr: error=0x7d { DriveStatusError UncorrectableError
    > SectorIdNotFound AddrMarkNotFound }, LBAsect=226327933, sector=3537401
    > ide: failed opcode was: unknown
    > ide0: reset timed-out, status=0x90
    > hdb: status error: status=0x7d { DriveReady DeviceFault SeekComplete
    > DataRequest CorrectedError Error }
    > hdb: status error: error=0x7d { DriveStatusError UncorrectableError
    > SectorIdNotFound AddrMarkNotFound }, LBAsect=226327933, sector=3537401
    > ide: failed opcode was: unknown
    > end_request: I/O error, dev hdb, sector 3537401
    > hdb: drive not ready for command
    > hdb: status error: status=0x7d { DriveReady DeviceFault SeekComplete
    > DataRequest CorrectedError Error }
    > hdb: status error: error=0x7d { DriveStatusError UncorrectableError
    > SectorIdNotFound AddrMarkNotFound }, LBAsect=226327933, sector=3537409
    > ide: failed opcode was: unknown
    > hdb: drive not ready for command
    > ide0: reset timed-out, status=0x90
    > end_request: I/O error, dev hdb, sector 3537409
    > end_request: I/O error, dev hdb, sector 3537417
    > end_request: I/O error, dev hdb, sector 3537425
    > end_request: I/O error, dev hdb, sector 3537401
    > end_request: I/O error, dev hdb, sector 3538825
    > end_request: I/O error, dev hdb, sector 3538833
    > end_request: I/O error, dev hdb, sector 3538841
    > end_request: I/O error, dev hdb, sector 3538849
    > end_request: I/O error, dev hdb, sector 3538825
    > end_request: I/O error, dev hdb, sector 3537977
    > end_request: I/O error, dev hdb, sector 3537985
    > end_request: I/O error, dev hdb, sector 3537993
    > end_request: I/O error, dev hdb, sector 3538001
    > end_request: I/O error, dev hdb, sector 3537977
    > end_request: I/O error, dev hdb, sector 3536889
    > end_request: I/O error, dev hdb, sector 3536897
    > end_request: I/O error, dev hdb, sector 3536905
    > end_request: I/O error, dev hdb, sector 3536913
    > end_request: I/O error, dev hdb, sector 3536889
    > end_request: I/O error, dev hdb, sector 3539689
    > end_request: I/O error, dev hdb, sector 3539697
    > end_request: I/O error, dev hdb, sector 3539705
    > end_request: I/O error, dev hdb, sector 3539713
    > end_request: I/O error, dev hdb, sector 3539689
    > end_request: I/O error, dev hdb, sector 3544185
    > end_request: I/O error, dev hdb, sector 3544193
    > end_request: I/O error, dev hdb, sector 3544201
    > end_request: I/O error, dev hdb, sector 3544209
    > end_request: I/O error, dev hdb, sector 3544185
    > end_request: I/O error, dev hdb, sector 3540457
    > end_request: I/O error, dev hdb, sector 3540465
    > end_request: I/O error, dev hdb, sector 3540473
    > end_request: I/O error, dev hdb, sector 3540481
    > end_request: I/O error, dev hdb, sector 3540457
    > end_request: I/O error, dev hdb, sector 3542089
    > end_request: I/O error, dev hdb, sector 3542097
    > end_request: I/O error, dev hdb, sector 3542105
    > end_request: I/O error, dev hdb, sector 3542113
    > end_request: I/O error, dev hdb, sector 3542089
    > end_request: I/O error, dev hdb, sector 3542897
    > end_request: I/O error, dev hdb, sector 3542905
    > end_request: I/O error, dev hdb, sector 3542913
    > end_request: I/O error, dev hdb, sector 3542921
    > end_request: I/O error, dev hdb, sector 3542897
    > end_request: I/O error, dev hdb, sector 7257
    > end_request: I/O error, dev hdb, sector 7265
    > end_request: I/O error, dev hdb, sector 7273
    > journal_bmap: journal block not found at offset 12 on hdb1
    > Aborting journal on device hdb1.
    > end_request: I/O error, dev hdb, sector 7177
    > Buffer I/O error on device hdb1, logical block 897
    > lost page write due to I/O error on hdb1
    > end_request: I/O error, dev hdb, sector 2362529
    > Buffer I/O error on device hdb1, logical block 295316
    > lost page write due to I/O error on hdb1
    > ABORTED IN=eth0 OUT= MAC=00:d0:b7:85:0a:3f:00:a0:c5:e3:18:a8:08:00
    > SRC=64.22.96.69 DST=192.168.0.32 LEN=40 TOS=0x00 PREC=0x00 TTL=50 ID=0
    > DF PROTO=TCP SPT=35249 DPT=22 SEQ=481307265 ACK=0 WINDOW=0 RES=0x00
    > RST URGP=0
    > ABORTED IN=eth0 OUT= MAC=00:d0:b7:85:0a:3f:00:a0:c5:e3:18:a8:08:00
    > SRC=64.22.96.69 DST=192.168.0.32 LEN=40 TOS=0x00 PREC=0x00 TTL=50 ID=0
    > DF PROTO=TCP SPT=35249 DPT=22 SEQ=481307265 ACK=0 WINDOW=0 RES=0x00
    > RST URGP=0
    > end_request: I/O error, dev hdb, sector 3543081
    > end_request: I/O error, dev hdb, sector 3543089
    > end_request: I/O error, dev hdb, sector 3543097
    > end_request: I/O error, dev hdb, sector 3543105
    > end_request: I/O error, dev hdb, sector 3543081
    > ext3_abort called.
    > EXT3-fs error (device hdb1): ext3_journal_start_sb: Detected aborted
    > journal
    > Remounting filesystem read-only
    > end_request: I/O error, dev hdb, sector 3533193
    > end_request: I/O error, dev hdb, sector 3533201
    > end_request: I/O error, dev hdb, sector 3533209
    > end_request: I/O error, dev hdb, sector 3533217
    > end_request: I/O error, dev hdb, sector 3533193
    > end_request: I/O error, dev hdb, sector 3533193
    > end_request: I/O error, dev hdb, sector 3533193
    > end_request: I/O error, dev hdb, sector 3533193
    > end_request: I/O error, dev hdb, sector 3533193
    > end_request: I/O error, dev hdb, sector 3533193
    > end_request: I/O error, dev hdb, sector 2362529
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=72691, block=295316
    > end_request: I/O error, dev hdb, sector 3533193
    > end_request: I/O error, dev hdb, sector 3533193
    > end_request: I/O error, dev hdb, sector 3533193
    > end_request: I/O error, dev hdb, sector 3533193
    > end_request: I/O error, dev hdb, sector 3533193
    > end_request: I/O error, dev hdb, sector 3533193
    > ABORTED IN=eth0 OUT= MAC=00:d0:b7:85:0a:3f:00:16:17:94:32:d6:08:00
    > SRC=192.168.0.46 DST=192.168.0.32 LEN=40 TOS=0x00 PREC=0x00 TTL=64
    > ID=230 PROTO=TCP SPT=1056 DPT=139 SEQ=1299343103 ACK=1299343103
    > WINDOW=0 RES=0x00 RST URGP=0
    > ABORTED IN=eth0 OUT= MAC=00:d0:b7:85:0a:3f:00:16:17:94:32:d6:08:00
    > SRC=192.168.0.46 DST=192.168.0.32 LEN=40 TOS=0x00 PREC=0x00 TTL=64
    > ID=1980 PROTO=TCP SPT=1261 DPT=139 SEQ=969640467 ACK=969640467
    > WINDOW=0 RES=0x00 RST URGP=0
    > end_request: I/O error, dev hdb, sector 2362721
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73086, block=295340
    > end_request: I/O error, dev hdb, sector 2362801
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73240, block=295350
    > end_request: I/O error, dev hdb, sector 2362753
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73146, block=295344
    > end_request: I/O error, dev hdb, sector 2362729
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73092, block=295341
    > end_request: I/O error, dev hdb, sector 2362729
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73093, block=295341
    > end_request: I/O error, dev hdb, sector 2362745
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73121, block=295343
    > end_request: I/O error, dev hdb, sector 2362729
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73089, block=295341
    > end_request: I/O error, dev hdb, sector 4568761
    > end_request: I/O error, dev hdb, sector 2362753
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73140, block=295344
    > end_request: I/O error, dev hdb, sector 2362729
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73100, block=295341
    > end_request: I/O error, dev hdb, sector 2362737
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73113, block=295342
    > end_request: I/O error, dev hdb, sector 2362745
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73129, block=295343
    > end_request: I/O error, dev hdb, sector 2362745
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73135, block=295343
    > end_request: I/O error, dev hdb, sector 2362761
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73164, block=295345
    > end_request: I/O error, dev hdb, sector 2362753
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73142, block=295344
    > end_request: I/O error, dev hdb, sector 2362761
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73162, block=295345
    > end_request: I/O error, dev hdb, sector 2362729
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73104, block=295341
    > end_request: I/O error, dev hdb, sector 2362745
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73128, block=295343
    > end_request: I/O error, dev hdb, sector 2362745
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73122, block=295343
    > end_request: I/O error, dev hdb, sector 2362761
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73153, block=295345
    > end_request: I/O error, dev hdb, sector 2362753
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73141, block=295344
    > end_request: I/O error, dev hdb, sector 2362753
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73144, block=295344
    > end_request: I/O error, dev hdb, sector 2362753
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73148, block=295344
    > end_request: I/O error, dev hdb, sector 2362753
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73139, block=295344
    > end_request: I/O error, dev hdb, sector 2362729
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73095, block=295341
    > end_request: I/O error, dev hdb, sector 2362745
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73127, block=295343
    > end_request: I/O error, dev hdb, sector 2362745
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73134, block=295343
    > end_request: I/O error, dev hdb, sector 2362753
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73152, block=295344
    > end_request: I/O error, dev hdb, sector 2362753
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73149, block=295344
    > end_request: I/O error, dev hdb, sector 2362761
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73155, block=295345
    > end_request: I/O error, dev hdb, sector 2362745
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73131, block=295343
    > end_request: I/O error, dev hdb, sector 2362761
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73168, block=295345
    > end_request: I/O error, dev hdb, sector 2362745
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73132, block=295343
    > end_request: I/O error, dev hdb, sector 2362737
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73118, block=295342
    > end_request: I/O error, dev hdb, sector 2362761
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73158, block=295345
    > end_request: I/O error, dev hdb, sector 2362729
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73103, block=295341
    > end_request: I/O error, dev hdb, sector 2588673
    > end_request: I/O error, dev hdb, sector 2362729
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73101, block=295341
    > end_request: I/O error, dev hdb, sector 2362753
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73138, block=295344
    > end_request: I/O error, dev hdb, sector 2362761
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73167, block=295345
    > end_request: I/O error, dev hdb, sector 2362729
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73102, block=295341
    > end_request: I/O error, dev hdb, sector 2362761
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73165, block=295345
    > end_request: I/O error, dev hdb, sector 2362745
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73125, block=295343
    > end_request: I/O error, dev hdb, sector 2362737
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73110, block=295342
    > end_request: I/O error, dev hdb, sector 2362737
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73109, block=295342
    > end_request: I/O error, dev hdb, sector 2362769
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73169, block=295346
    > end_request: I/O error, dev hdb, sector 3651025
    > end_request: I/O error, dev hdb, sector 2362761
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73157, block=295345
    > end_request: I/O error, dev hdb, sector 2362729
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73097, block=295341
    > end_request: I/O error, dev hdb, sector 2362737
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73106, block=295342
    > end_request: I/O error, dev hdb, sector 2362737
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73114, block=295342
    > end_request: I/O error, dev hdb, sector 2362761
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73166, block=295345
    > end_request: I/O error, dev hdb, sector 2362737
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73117, block=295342
    > end_request: I/O error, dev hdb, sector 2362737
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73120, block=295342
    > end_request: I/O error, dev hdb, sector 2362753
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73150, block=295344
    > end_request: I/O error, dev hdb, sector 2362729
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73091, block=295341
    > end_request: I/O error, dev hdb, sector 2362753
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73147, block=295344
    > end_request: I/O error, dev hdb, sector 2362729
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73099, block=295341
    > end_request: I/O error, dev hdb, sector 2362761
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73154, block=295345
    > end_request: I/O error, dev hdb, sector 2362745
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73124, block=295343
    > end_request: I/O error, dev hdb, sector 2362737
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73108, block=295342
    > end_request: I/O error, dev hdb, sector 2362737
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73116, block=295342
    > end_request: I/O error, dev hdb, sector 2362753
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73137, block=295344
    > end_request: I/O error, dev hdb, sector 2362737
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73111, block=295342
    > end_request: I/O error, dev hdb, sector 4568729
    > end_request: I/O error, dev hdb, sector 2362737
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73119, block=295342
    > end_request: I/O error, dev hdb, sector 2362729
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73098, block=295341
    > end_request: I/O error, dev hdb, sector 4567841
    > end_request: I/O error, dev hdb, sector 2362721
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73088, block=295340
    > end_request: I/O error, dev hdb, sector 2362737
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73105, block=295342
    > end_request: I/O error, dev hdb, sector 2362729
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73090, block=295341
    > end_request: I/O error, dev hdb, sector 2362745
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73133, block=295343
    > end_request: I/O error, dev hdb, sector 2362761
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73161, block=295345
    > end_request: I/O error, dev hdb, sector 2362737
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73115, block=295342
    > end_request: I/O error, dev hdb, sector 2362745
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73136, block=295343
    > end_request: I/O error, dev hdb, sector 2362745
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73123, block=295343
    > end_request: I/O error, dev hdb, sector 2362761
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73160, block=295345
    > end_request: I/O error, dev hdb, sector 2362737
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73112, block=295342
    > end_request: I/O error, dev hdb, sector 2362761
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73156, block=295345
    > end_request: I/O error, dev hdb, sector 2362761
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73159, block=295345
    > end_request: I/O error, dev hdb, sector 2362753
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73151, block=295344
    > end_request: I/O error, dev hdb, sector 2362729
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73094, block=295341
    > end_request: I/O error, dev hdb, sector 2362729
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73096, block=295341
    > end_request: I/O error, dev hdb, sector 2362745
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73130, block=295343
    > end_request: I/O error, dev hdb, sector 2362737
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73107, block=295342
    > end_request: I/O error, dev hdb, sector 2362761
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73163, block=295345
    > end_request: I/O error, dev hdb, sector 2362745
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73126, block=295343
    > end_request: I/O error, dev hdb, sector 3648201
    > end_request: I/O error, dev hdb, sector 2362753
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73143, block=295344
    > end_request: I/O error, dev hdb, sector 2362753
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73145, block=295344
    > end_request: I/O error, dev hdb, sector 2710017
    > end_request: I/O error, dev hdb, sector 2605065
    > end_request: I/O error, dev hdb, sector 3544825
    > end_request: I/O error, dev hdb, sector 2362505
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=72647, block=295313
    > end_request: I/O error, dev hdb, sector 2362529
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=72689, block=295316
    > end_request: I/O error, dev hdb, sector 2362505
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=72643, block=295313
    > end_request: I/O error, dev hdb, sector 2362521
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=72678, block=295315
    > end_request: I/O error, dev hdb, sector 3522817
    > end_request: I/O error, dev hdb, sector 2362521
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=72682, block=295315
    > end_request: I/O error, dev hdb, sector 2362521
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=72687, block=295315
    > end_request: I/O error, dev hdb, sector 2362505
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=72648, block=295313
    > end_request: I/O error, dev hdb, sector 2362521
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=72683, block=295315
    > end_request: I/O error, dev hdb, sector 2362505
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=72650, block=295313
    > end_request: I/O error, dev hdb, sector 2362505
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=72649, block=295313
    > end_request: I/O error, dev hdb, sector 2362521
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=72673, block=295315
    > end_request: I/O error, dev hdb, sector 2362505
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=72653, block=295313
    > end_request: I/O error, dev hdb, sector 2362505
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=72641, block=295313
    > end_request: I/O error, dev hdb, sector 2362521
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=72674, block=295315
    > end_request: I/O error, dev hdb, sector 2362521
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=72685, block=295315
    > end_request: I/O error, dev hdb, sector 2362521
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=72676, block=295315
    > end_request: I/O error, dev hdb, sector 2362521
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=72686, block=295315
    > end_request: I/O error, dev hdb, sector 3522553
    > end_request: I/O error, dev hdb, sector 3524505
    > end_request: I/O error, dev hdb, sector 2362521
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=72681, block=295315
    > end_request: I/O error, dev hdb, sector 2362505
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=72645, block=295313
    > end_request: I/O error, dev hdb, sector 2362505
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=72646, block=295313
    > end_request: I/O error, dev hdb, sector 2362521
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=72675, block=295315
    > end_request: I/O error, dev hdb, sector 2362505
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=72651, block=295313
    > end_request: I/O error, dev hdb, sector 2362521
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=72680, block=295315
    > end_request: I/O error, dev hdb, sector 2362521
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=72679, block=295315
    > end_request: I/O error, dev hdb, sector 2362505
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=72654, block=295313
    > end_request: I/O error, dev hdb, sector 2362505
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=72655, block=295313
    > end_request: I/O error, dev hdb, sector 2362521
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=72677, block=295315
    > end_request: I/O error, dev hdb, sector 2362505
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=72656, block=295313
    > end_request: I/O error, dev hdb, sector 2362521
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=72684, block=295315
    > end_request: I/O error, dev hdb, sector 2362497
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=72640, block=295312
    > end_request: I/O error, dev hdb, sector 2362505
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=72642, block=295313
    > end_request: I/O error, dev hdb, sector 2362505
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=72644, block=295313
    > end_request: I/O error, dev hdb, sector 2362529
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=72690, block=295316
    > end_request: I/O error, dev hdb, sector 2362505
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=72652, block=295313
    > end_request: I/O error, dev hdb, sector 2362521
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=72688, block=295315
    > end_request: I/O error, dev hdb, sector 5119177


    > I did an unmount of hdb, fdisk /dev/hdb, and it couldn't read it. I did a reboot, HDD showed up in CMOS/BIOS and
    > Debian went to its safe mode and let me fsck it. fsck /dev/hdb said all ext3 journals got lost and
    > reverted back to ext2. I fsck'ed. After reboot and remounting, it
    > seems the files were OK? So I put journal back and things were OK.


    > A few minutes later, things go crazy again:
    > $ dmesg
    > e PFN ranges
    > 0: 0 -> 130864
    > On node 0 totalpages: 130864
    > DMA zone: 32 pages used for memmap
    > DMA zone: 0 pages reserved
    > DMA zone: 4064 pages, LIFO batch:0
    > Normal zone: 990 pages used for memmap
    > Normal zone: 125778 pages, LIFO batch:31
    > HighMem zone: 0 pages used for memmap
    > DMI 2.3 present.
    > ACPI: RSDP 000FA850, 0014 (r0 ACPIAM)
    > ACPI: RSDT 1FF30000, 0030 (r1 A M I OEMRSDT 6000517 MSFT 97)
    > ACPI: FACP 1FF30200, 0081 (r1 A M I OEMFACP 6000517 MSFT 97)
    > ACPI: DSDT 1FF303E0, 3755 (r1 A0058 A0058002 2 MSFT 100000D)
    > ACPI: FACS 1FF40000, 0040
    > ACPI: APIC 1FF30390, 004A (r1 A M I OEMAPIC 6000517 MSFT 97)
    > ACPI: OEMB 1FF40040, 003F (r1 A M I OEMBIOS 6000517 MSFT 97)
    > ACPI: PM-Timer IO Port: 0x808
    > ACPI: Local APIC address 0xfee00000
    > ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
    > Processor #0 15:12 APIC version 16
    > ACPI: IOAPIC (id[0x01] address[0xfec00000] gsi_base[0])
    > IOAPIC[0]: apic_id 1, version 3, address 0xfec00000, GSI 0-23
    > ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
    > ACPI: IRQ0 used by override.
    > ACPI: IRQ2 used by override.
    > ACPI: IRQ9 used by override.
    > Enabling APIC mode: Flat. Using 1 I/O APICs
    > Using ACPI (MADT) for SMP configuration information
    > Allocating PCI resources starting at 30000000 (gap: 20000000:dff80000)
    > Built 1 zonelists. Total pages: 129842
    > Kernel command line: root=/dev/hda1 ro
    > mapped APIC to ffffd000 (fee00000)
    > mapped IOAPIC to ffffc000 (fec00000)
    > Enabling fast FPU save and restore... done.
    > Enabling unmasked SIMD FPU exception support... done.
    > Initializing CPU#0
    > PID hash table entries: 2048 (order: 11, 8192 bytes)
    > Detected 2202.937 MHz processor.
    > spurious 8259A interrupt: IRQ7.
    > Console: colour VGA+ 80x25
    > Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
    > Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
    > Memory: 514020k/523456k available (1702k kernel code, 8820k reserved,
    > 663k data, 244k init, 0k highmem)
    > virtual kernel memory layout:
    > fixmap : 0xfff4e000 - 0xfffff000 ( 708 kB)
    > pkmap : 0xff800000 - 0xffc00000 (4096 kB)
    > vmalloc : 0xe0800000 - 0xff7fe000 ( 495 MB)
    > lowmem : 0xc0000000 - 0xdff30000 ( 511 MB)
    > .init : 0xc0355000 - 0xc0392000 ( 244 kB)
    > .data : 0xc02a9827 - 0xc034f784 ( 663 kB)
    > .text : 0xc0100000 - 0xc02a9827 (1702 kB)
    > Checking if this processor honours the WP bit even in supervisor
    > mode... Ok. Calibrating delay using timer specific routine.. 4410.78
    > BogoMIPS (lpj=8821571)
    > Security Framework v1.0.0 initialized
    > SELinux: Disabled at boot.
    > Capability LSM initialized
    > Mount-cache hash table entries: 512
    > CPU: After generic identify, caps: 078bfbff e1d3fbff 00000000 00000000
    > 00000000 00000000 00000000
    > CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
    > CPU: L2 Cache: 512K (64 bytes/line)
    > CPU: After all inits, caps: 078bfbff e1d3fbff 00000000 00000410
    > 00000000 00000000 00000000
    > Intel machine check architecture supported.
    > Intel machine check reporting enabled on CPU#0.
    > Compat vDSO mapped to ffffe000.
    > Checking 'hlt' instruction... OK.
    > SMP alternatives: switching to UP code
    > Freeing SMP alternatives: 11k freed
    > ACPI: Core revision 20070126
    > CPU0: AMD Athlon(tm) 64 Processor 3200+ stepping 00
    > Total of 1 processors activated (4410.78 BogoMIPS).
    > ENABLING IO-APIC IRQs
    > ..TIMER: vector=0x31 apic1=0 pin1=2 apic2=0 pin2=0
    > Brought up 1 CPUs
    > Booting paravirtualized kernel on bare hardware
    > NET: Registered protocol family 16
    > ACPI: bus type pci registered
    > PCI: PCI BIOS revision 2.10 entry at 0xf0031, last bus=1
    > PCI: Using configuration type 1
    > Setting up standard PCI resources
    > ACPI: Interpreter enabled
    > ACPI: (supports S0 S1 S3 S4 S5)
    > ACPI: Using IOAPIC for interrupt routing
    > ACPI: PCI Root Bridge [PCI0] (0000:00)
    > PCI: Probing PCI hardware (bus 00)
    > PCI: Firmware left 0000:00:09.0 e100 interrupts enabled, disabling
    > PCI: enabled onboard AC97/MC97 devices
    > ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
    > ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 7 10 *11 14 15)
    > ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 7 *10 11 14 15)
    > ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 7 10 11 14 15)
    > ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 7 10 11 14 15) *0,
    > disabled. ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 7 10 11 14 15)
    > *0, disabled. ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 7 10 11 14
    > 15) *0, disabled. ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 7 10 11
    > 14 15) *0, disabled. ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 7 10
    > 11 14 15) *0, disabled. Linux Plug and Play Support v0.97 (c) Adam
    > Belay pnp: PnP ACPI init
    > ACPI: bus type pnp registered
    > pnp: PnP ACPI: found 13 devices
    > ACPI: ACPI bus type pnp unregistered
    > PnPBIOS: Disabled by ACPI PNP
    > PCI: Using ACPI for IRQ routing
    > PCI: If a device doesn't work, try "pci=routeirq". If it helps, post
    > a report
    > NET: Registered protocol family 8
    > NET: Registered protocol family 20
    > ACPI: RTC can wake from S4
    > pnp: 00:09: iomem range 0xfec00000-0xfec00fff has been reserved
    > pnp: 00:09: iomem range 0xfee00000-0xfee00fff has been reserved
    > pnp: 00:09: iomem range 0xfff80000-0xffffffff could not be reserved
    > pnp: 00:0c: iomem range 0x0-0x9ffff could not be reserved
    > pnp: 00:0c: iomem range 0xc0000-0xdffff could not be reserved
    > pnp: 00:0c: iomem range 0xe0000-0xfffff could not be reserved
    > pnp: 00:0c: iomem range 0x100000-0x1ffeffff could not be reserved
    > Time: tsc clocksource has been installed.
    > PCI: Bridge: 0000:00:01.0
    > IO window: disabled.
    > MEM window: f9500000-fd6fffff
    > PREFETCH window: e1400000-f13fffff
    > PCI: Setting latency timer of device 0000:00:01.0 to 64
    > NET: Registered protocol family 2
    > IP route cache hash table entries: 4096 (order: 2, 16384 bytes)
    > TCP established hash table entries: 16384 (order: 5, 196608 bytes)
    > TCP bind hash table entries: 16384 (order: 5, 131072 bytes)
    > TCP: Hash tables configured (established 16384 bind 16384)
    > TCP reno registered
    > checking if image is initramfs... it is
    > Freeing initrd memory: 1305k freed
    > audit: initializing netlink socket (disabled)
    > audit(1218577017.172:1): initialized
    > VFS: Disk quotas dquot_6.5.1
    > Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
    > io scheduler noop registered
    > io scheduler anticipatory registered
    > io scheduler deadline registered
    > io scheduler cfq registered (default)
    > PCI: VIA PCI bridge detected. Disabling DAC.
    > Boot video device is 0000:01:00.0
    > isapnp: Scanning for PnP cards...
    > Switched to high resolution mode on CPU 0
    > isapnp: No Plug & Play device found
    > Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing
    > enabled 00:0a: ttyS0 at I/O 0x2f8 (irq = 3) is a 16550A
    > 00:0b: ttyS1 at I/O 0x3f8 (irq = 4) is a 16550A
    > RAMDISK driver initialized: 16 RAM disks of 8192K size 1024 blocksize
    > PNP: PS/2 Controller [PNP0303:PS2K,PNP0f03:PS2M] at 0x60,0x64 irq 1,12
    > serio: i8042 KBD port at 0x60,0x64 irq 1
    > serio: i8042 AUX port at 0x60,0x64 irq 12
    > mice: PS/2 mouse device common for all mice
    > TCP bic registered
    > NET: Registered protocol family 1
    > NET: Registered protocol family 17
    > Using IPI No-Shortcut mode
    > Freeing unused kernel memory: 244k freed
    > Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
    > ide: Assuming 33MHz system bus speed for PIO modes; override with
    > idebus=xx VP_IDE: IDE controller at PCI slot 0000:00:0f.1
    > ACPI: PCI Interrupt 0000:00:0f.1[A] -> GSI 20 (level, low) -> IRQ 16
    > VP_IDE: chipset revision 6
    > VP_IDE: not 100% native mode: will probe irqs later
    > VP_IDE: VIA vt8237 (rev 00) IDE UDMA133 controller on pci0000:00:0f.1
    > ide0: BM-DMA at 0xfc00-0xfc07, BIOS settings: hdaMA, hdbMA
    > ide1: BM-DMA at 0xfc08-0xfc0f, BIOS settings: hdcMA, hddio
    > Probing IDE interface ide0...
    > input: AT Translated Set 2 keyboard as /class/input/input0
    > hda: ST380011A, ATA DISK drive
    > hdb: QUANTUM FIREBALL EX6.4A, ATA DISK drive
    > ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
    > Probing IDE interface ide1...
    > hdc: TOSHIBA DVD-ROM SD-M1912, ATAPI CD/DVD-ROM drive
    > ide1 at 0x170-0x177,0x376 on irq 15
    > SCSI subsystem initialized
    > libata version 2.21 loaded.
    > hda: max request size: 512KiB
    > hda: 156301488 sectors (80026 MB) w/2048KiB Cache, CHS=16383/255/63,
    > UDMA(100)
    > hda: cache flushes supported
    > hda: hda1 hda2 < hda5 hda6 hda7 hda8 hda9 hda10 hda11 hda12 >
    > hdb: max request size: 128KiB
    > hdb: 12594960 sectors (6448 MB) w/418KiB Cache, CHS=13328/15/63,
    > UDMA(33) hdb: cache flushes not supported
    > hdb: hdb1
    > kjournald starting. Commit interval 5 seconds
    > EXT3-fs: mounted filesystem with ordered data mode.
    > input: PC Speaker as /class/input/input1
    > pci_hotplug: PCI Hot Plug PCI Core version: 0.5
    > shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
    > Real Time Clock Driver v1.12ac
    > Floppy drive(s): fd0 is 1.44M
    > FDC 0 is a post-1991 82077
    > usbcore: registered new interface driver usbfs
    > usbcore: registered new interface driver hub
    > usbcore: registered new device driver usb
    > Linux agpgart interface v0.102 (c) Dave Jones
    > hdc: ATAPI 48X DVD-ROM drive, 512kB Cache, UDMA(33)
    > Uniform CD-ROM driver Revision: 3.20
    > USB Universal Host Controller Interface driver v3.0
    > ACPI: PCI Interrupt 0000:00:10.0[A] -> GSI 21 (level, low) -> IRQ 17
    > uhci_hcd 0000:00:10.0: UHCI Host Controller
    > uhci_hcd 0000:00:10.0: new USB bus registered, assigned bus number 1
    > uhci_hcd 0000:00:10.0: irq 17, io base 0x0000dc00
    > usb usb1: configuration #1 chosen from 1 choice
    > hub 1-0:1.0: USB hub found
    > hub 1-0:1.0: 2 ports detected
    > e100: Intel(R) PRO/100 Network Driver, 3.5.17-k4-NAPI
    > e100: Copyright(c) 1999-2006 Intel Corporation
    > ACPI: PCI Interrupt 0000:00:10.1[A] -> GSI 21 (level, low) -> IRQ 17
    > uhci_hcd 0000:00:10.1: UHCI Host Controller
    > uhci_hcd 0000:00:10.1: new USB bus registered, assigned bus number 2
    > uhci_hcd 0000:00:10.1: irq 17, io base 0x0000ec00
    > usb usb2: configuration #1 chosen from 1 choice
    > hub 2-0:1.0: USB hub found
    > hub 2-0:1.0: 2 ports detected
    > ACPI: PCI Interrupt 0000:00:10.2[B] -> GSI 21 (level, low) -> IRQ 17
    > uhci_hcd 0000:00:10.2: UHCI Host Controller
    > uhci_hcd 0000:00:10.2: new USB bus registered, assigned bus number 3
    > uhci_hcd 0000:00:10.2: irq 17, io base 0x0000c000
    > usb usb3: configuration #1 chosen from 1 choice
    > hub 3-0:1.0: USB hub found
    > hub 3-0:1.0: 2 ports detected
    > ACPI: PCI Interrupt 0000:00:10.3[B] -> GSI 21 (level, low) -> IRQ 17
    > uhci_hcd 0000:00:10.3: UHCI Host Controller
    > uhci_hcd 0000:00:10.3: new USB bus registered, assigned bus number 4
    > uhci_hcd 0000:00:10.3: irq 17, io base 0x0000c400
    > usb usb4: configuration #1 chosen from 1 choice
    > hub 4-0:1.0: USB hub found
    > hub 4-0:1.0: 2 ports detected
    > ACPI: PCI Interrupt 0000:00:10.4[C] -> GSI 21 (level, low) -> IRQ 17
    > ehci_hcd 0000:00:10.4: EHCI Host Controller
    > ehci_hcd 0000:00:10.4: new USB bus registered, assigned bus number 5
    > ehci_hcd 0000:00:10.4: irq 17, io mem 0xfd700000
    > ehci_hcd 0000:00:10.4: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
    > usb usb5: configuration #1 chosen from 1 choice
    > hub 5-0:1.0: USB hub found
    > hub 5-0:1.0: 8 ports detected
    > input: ImPS/2 Generic Wheel Mouse as /class/input/input2
    > agpgart: Detected AGP bridge 0
    > agpgart: AGP aperture is 64M @ 0xf4000000
    > sata_via 0000:00:0f.0: version 2.2
    > ACPI: PCI Interrupt 0000:00:0f.0[B] -> GSI 20 (level, low) -> IRQ 16
    > sata_via 0000:00:0f.0: routed to hard irq line 10
    > scsi0 : sata_via
    > scsi1 : sata_via
    > ata1: SATA max UDMA/133 cmd 0x0001e800 ctl 0x0001e402 bmdma 0x0001d400
    > irq 16
    > ata2: SATA max UDMA/133 cmd 0x0001e000 ctl 0x0001d802 bmdma 0x0001d408
    > irq 16
    > ata1: SATA link down 1.5 Gbps (SStatus 0 SControl 300)
    > ata2: SATA link down 1.5 Gbps (SStatus 0 SControl 300)
    > ACPI: PCI Interrupt 0000:00:09.0[A] -> GSI 16 (level, low) -> IRQ 18
    > e100: eth0: e100_probe: addr 0xfdc00000, irq 18, MAC addr
    > 000:B7:85:0A:3F PCI: Enabling device 0000:00:11.6 (0000 -> 0001)
    > ACPI: PCI Interrupt 0000:00:11.6[C] -> GSI 22 (level, low) -> IRQ 19
    > usb 2-2: new low speed USB device using uhci_hcd and address 2
    > PCI: Setting latency timer of device 0000:00:11.6 to 64
    > usb 2-2: configuration #1 chosen from 1 choice
    > usbcore: registered new interface driver hiddev
    > ACPI: PCI interrupt for device 0000:00:11.6 disabled
    > VIA 82xx Modem: probe of 0000:00:11.6 failed with error -13
    > ACPI: PCI Interrupt 0000:00:11.5[C] -> GSI 22 (level, low) -> IRQ 19
    > PCI: Setting latency timer of device 0000:00:11.5 to 64
    > codec_read: codec 0 is not valid [0xfe0000]
    > codec_read: codec 0 is not valid [0xfe0000]
    > codec_read: codec 0 is not valid [0xfe0000]
    > codec_read: codec 0 is not valid [0xfe0000]
    > hiddev96: USB HID v1.10 Device [American Power Conversion Back-UPS RS
    > 1500 FW:8.g8 .D USB FW:g8 ] on usb-0000:00:10.1-2
    > usbcore: registered new interface driver usbhid
    > drivers/hid/usbhid/hid-core.c: v2.6:USB HID core driver
    > Adding 2361512k swap on /dev/hda10. Priority:-1 extents:1
    > across:2361512k EXT3 FS on hda1, internal journal
    > loop: module loaded
    > w83627hf: Found W83697HF chip at 0x290
    > fuse init (API version 7.8)
    > device-mapper: ioctl: 4.11.0-ioctl (2006-10-12) initialised:
    > dm-devel@redhat.com
    > kjournald starting. Commit interval 5 seconds
    > EXT3 FS on hda5, internal journal
    > EXT3-fs: mounted filesystem with ordered data mode.
    > kjournald starting. Commit interval 5 seconds
    > EXT3 FS on hda6, internal journal
    > EXT3-fs: mounted filesystem with ordered data mode.
    > kjournald starting. Commit interval 5 seconds
    > EXT3 FS on hda7, internal journal
    > EXT3-fs: mounted filesystem with ordered data mode.
    > kjournald starting. Commit interval 5 seconds
    > EXT3 FS on hda8, internal journal
    > EXT3-fs: mounted filesystem with ordered data mode.
    > kjournald starting. Commit interval 5 seconds
    > EXT3 FS on hda9, internal journal
    > EXT3-fs: mounted filesystem with ordered data mode.
    > kjournald starting. Commit interval 5 seconds
    > EXT3 FS on hda11, internal journal
    > EXT3-fs: mounted filesystem with ordered data mode.
    > kjournald starting. Commit interval 5 seconds
    > EXT3 FS on hda12, internal journal
    > EXT3-fs: mounted filesystem with ordered data mode.
    > ext3: No journal on filesystem on hdb1
    > ip_tables: (C) 2000-2006 Netfilter Core Team
    > Netfilter messages via NETLINK v0.30.
    > nf_conntrack version 0.5.0 (4089 buckets, 32712 max)
    > e100: eth0: e100_watchdog: link up, 100Mbps, full-duplex
    > NET: Registered protocol family 10
    > lo: Disabled Privacy Extensions
    > input: Power Button (FF) as /class/input/input3
    > ACPI: Power Button (FF) [PWRF]
    > input: Power Button (CM) as /class/input/input4
    > ACPI: Power Button (CM) [PWRB]
    > input: Sleep Button (CM) as /class/input/input5
    > ACPI: Sleep Button (CM) [SLPB]
    > eth0: no IPv6 routers present
    > vboxdrv: Trying to deactivate the NMI watchdog permanently...
    > vboxdrv: Successfully done.
    > vboxdrv: Found 1 processor cores.
    > vboxdrv: fAsync=0 u64DiffCores=1.
    > vboxdrv: TSC mode is 'synchronous', kernel timer mode is 'normal'.
    > vboxdrv: Successfully loaded version 1.6.4 (interface 0x00080000).
    > vmmon: module license 'unspecified' taints kernel.
    > [2923]: VMCI: Driver initialized.
    > [2923]: Module vmmon: registered with major=10 minor=165
    > [2923]: Module vmmon: initialized
    > /dev/vmnet: open called by PID 2952 (vmnet-bridge)
    > /dev/vmnet: hub 0 does not exist, allocating memory.
    > /dev/vmnet: port on hub 0 successfully opened
    > bridge-eth0: enabling the bridge
    > bridge-eth0: up
    > bridge-eth0: already up
    > bridge-eth0: attached
    > /dev/vmnet: open called by PID 2966 (vmnet-natd)
    > /dev/vmnet: hub 8 does not exist, allocating memory.
    > /dev/vmnet: port on hub 8 successfully opened
    > powernow-k8: Found 1 AMD Athlon(tm) 64 Processor 3200+ processors
    > (version 2.00.00)
    > powernow-k8: 0 : fid 0xe (2200 MHz), vid 0x2
    > powernow-k8: 1 : fid 0xc (2000 MHz), vid 0x6
    > powernow-k8: 2 : fid 0xa (1800 MHz), vid 0xa
    > powernow-k8: 3 : fid 0x2 (1000 MHz), vid 0x12
    > Marking TSC unstable due to: cpufreq changes.
    > Time: acpi_pm clocksource has been installed.
    > Clocksource tsc unstable (delta = -176950529 ns)
    > /dev/vmnet: open called by PID 3029 (vmnet-netifup)
    > /dev/vmnet: hub 1 does not exist, allocating memory.
    > /dev/vmnet: port on hub 1 successfully opened
    > /dev/vmnet: open called by PID 3030 (vmnet-netifup)
    > /dev/vmnet: port on hub 8 successfully opened
    > /dev/vmnet: open called by PID 3066 (vmnet-dhcpd)
    > /dev/vmnet: port on hub 1 successfully opened
    > /dev/vmnet: open called by PID 3047 (vmnet-dhcpd)
    > /dev/vmnet: port on hub 8 successfully opened
    > vmnet8: no IPv6 routers present
    > vmnet1: no IPv6 routers present
    > ext3: No journal on filesystem on hdb1
    > kjournald starting. Commit interval 5 seconds
    > EXT3 FS on hdb1, internal journal
    > EXT3-fs: mounted filesystem with ordered data mode.
    > hda: status error: status=0xd0 { Busy }
    > ide: failed opcode was: unknown
    > hda: DMA disabled
    > hdb: DMA disabled
    > hda: drive not ready for command
    > ide0: reset timed-out, status=0xd0
    > hda: lost interrupt
    > attempt to access beyond end of device
    > hda5: rw=0, want=8877388712, limit=29302497
    > attempt to access beyond end of device
    > hda5: rw=0, want=8877388712, limit=29302497
    > attempt to access beyond end of device
    > hda5: rw=0, want=8877388584, limit=29302497
    > attempt to access beyond end of device
    > hda5: rw=0, want=8885842944, limit=29302497
    > attempt to access beyond end of device
    > hda5: rw=0, want=8877388712, limit=29302497
    > hda: task_out_intr: status=0xd8 { Busy }
    > ide: failed opcode was: unknown
    > ide0: reset timed-out, status=0xd0
    > end_request: I/O error, dev hda, sector 2806748
    > Buffer I/O error on device hda5, logical block 278543
    > lost page write due to I/O error on hda5
    > end_request: I/O error, dev hda, sector 2806811
    > Buffer I/O error on device hda5, logical block 278551
    > lost page write due to I/O error on hda5
    > end_request: I/O error, dev hda, sector 2806835
    > Buffer I/O error on device hda5, logical block 278554
    > lost page write due to I/O error on hda5
    > end_request: I/O error, dev hda, sector 2806843
    > Buffer I/O error on device hda5, logical block 278555
    > lost page write due to I/O error on hda5
    > end_request: I/O error, dev hda, sector 2806851
    > Buffer I/O error on device hda5, logical block 278556
    > lost page write due to I/O error on hda5
    > end_request: I/O error, dev hda, sector 2806859
    > Buffer I/O error on device hda5, logical block 278557
    > lost page write due to I/O error on hda5
    > end_request: I/O error, dev hda, sector 2806867
    > Buffer I/O error on device hda5, logical block 278558
    > lost page write due to I/O error on hda5
    > end_request: I/O error, dev hda, sector 2806875
    > Buffer I/O error on device hda5, logical block 278559
    > lost page write due to I/O error on hda5
    > end_request: I/O error, dev hda, sector 2806883
    > Buffer I/O error on device hda5, logical block 278560
    > lost page write due to I/O error on hda5
    > end_request: I/O error, dev hda, sector 2806891
    > Buffer I/O error on device hda5, logical block 278561
    > lost page write due to I/O error on hda5
    > end_request: I/O error, dev hda, sector 2806899
    > end_request: I/O error, dev hda, sector 2806907
    > end_request: I/O error, dev hda, sector 2806915
    > end_request: I/O error, dev hda, sector 2806923
    > end_request: I/O error, dev hda, sector 2806931
    > end_request: I/O error, dev hda, sector 2806939
    > end_request: I/O error, dev hda, sector 2806947
    > end_request: I/O error, dev hda, sector 2806955
    > end_request: I/O error, dev hda, sector 2807011
    > end_request: I/O error, dev hda, sector 2807019
    > end_request: I/O error, dev hda, sector 2807027
    > end_request: I/O error, dev hda, sector 2807035
    > end_request: I/O error, dev hda, sector 2807043
    > end_request: I/O error, dev hda, sector 2807051
    > end_request: I/O error, dev hda, sector 2807059
    > end_request: I/O error, dev hda, sector 2807067
    > end_request: I/O error, dev hda, sector 2807075
    > end_request: I/O error, dev hda, sector 2807083
    > end_request: I/O error, dev hda, sector 2807091
    > end_request: I/O error, dev hda, sector 2807099
    > end_request: I/O error, dev hda, sector 2807107
    > end_request: I/O error, dev hda, sector 2807115
    > end_request: I/O error, dev hda, sector 2807123
    > end_request: I/O error, dev hda, sector 2807131
    > end_request: I/O error, dev hda, sector 2807139
    > end_request: I/O error, dev hda, sector 2807147
    > end_request: I/O error, dev hda, sector 2807155
    > end_request: I/O error, dev hda, sector 2807163
    > end_request: I/O error, dev hda, sector 2807171
    > end_request: I/O error, dev hda, sector 2807179
    > end_request: I/O error, dev hda, sector 2807187
    > end_request: I/O error, dev hda, sector 2807195
    > end_request: I/O error, dev hda, sector 2807203
    > end_request: I/O error, dev hda, sector 2807211
    > end_request: I/O error, dev hda, sector 2807219
    > end_request: I/O error, dev hda, sector 2807227
    > end_request: I/O error, dev hda, sector 2807235
    > end_request: I/O error, dev hda, sector 2807243
    > end_request: I/O error, dev hda, sector 2807251
    > end_request: I/O error, dev hda, sector 2807259
    > end_request: I/O error, dev hda, sector 2807267
    > end_request: I/O error, dev hda, sector 2807275
    > end_request: I/O error, dev hda, sector 2807283
    > end_request: I/O error, dev hda, sector 2807291
    > end_request: I/O error, dev hda, sector 2807299
    > end_request: I/O error, dev hda, sector 2807307
    > end_request: I/O error, dev hda, sector 2807315
    > end_request: I/O error, dev hda, sector 2807323
    > end_request: I/O error, dev hda, sector 2807331
    > end_request: I/O error, dev hda, sector 2807339
    > end_request: I/O error, dev hda, sector 2807795
    > end_request: I/O error, dev hda, sector 2825411
    > end_request: I/O error, dev hda, sector 2885699
    > end_request: I/O error, dev hda, sector 11893315
    > end_request: I/O error, dev hda, sector 19903083
    > end_request: I/O error, dev hda, sector 30929763
    > end_request: I/O error, dev hda, sector 31717203
    > end_request: I/O error, dev hda, sector 34075299
    > end_request: I/O error, dev hda, sector 34075443
    > end_request: I/O error, dev hda, sector 35911243
    > end_request: I/O error, dev hda, sector 35911851
    > end_request: I/O error, dev hda, sector 37483315
    > end_request: I/O error, dev hda, sector 39648483
    > end_request: I/O error, dev hda, sector 39648491
    > end_request: I/O error, dev hda, sector 40871067
    > end_request: I/O error, dev hda, sector 40873747
    > end_request: I/O error, dev hda, sector 40873867
    > end_request: I/O error, dev hda, sector 115275
    > end_request: I/O error, dev hda, sector 115279
    > end_request: I/O error, dev hda, sector 115281
    > end_request: I/O error, dev hda, sector 115283
    > end_request: I/O error, dev hda, sector 278745
    > end_request: I/O error, dev hda, sector 578403
    > end_request: I/O error, dev hda, sector 578411
    > end_request: I/O error, dev hda, sector 1102723
    > end_request: I/O error, dev hda, sector 1102747
    > end_request: I/O error, dev hda, sector 2675555
    > end_request: I/O error, dev hda, sector 2675563
    > end_request: I/O error, dev hda, sector 2675619
    > end_request: I/O error, dev hda, sector 2741115
    > end_request: I/O error, dev hda, sector 2741163
    > end_request: I/O error, dev hda, sector 2741171
    > end_request: I/O error, dev hda, sector 2741347
    > end_request: I/O error, dev hda, sector 2741459
    > end_request: I/O error, dev hda, sector 2741467
    > end_request: I/O error, dev hda, sector 2741475
    > end_request: I/O error, dev hda, sector 2741483
    > end_request: I/O error, dev hda, sector 2741491
    > end_request: I/O error, dev hda, sector 2741523
    > end_request: I/O error, dev hda, sector 2741603
    > end_request: I/O error, dev hda, sector 2741611
    > end_request: I/O error, dev hda, sector 2741771
    > end_request: I/O error, dev hda, sector 2741779
    > end_request: I/O error, dev hda, sector 2741915
    > end_request: I/O error, dev hda, sector 2741923
    > end_request: I/O error, dev hda, sector 2742067
    > end_request: I/O error, dev hda, sector 39976827
    > end_request: I/O error, dev hda, sector 39976875
    > end_request: I/O error, dev hda, sector 115287
    > end_request: I/O error, dev hda, sector 115297
    > end_request: I/O error, dev hda, sector 115299
    > end_request: I/O error, dev hda, sector 115303
    > end_request: I/O error, dev hda, sector 115305
    > end_request: I/O error, dev hda, sector 115307
    > end_request: I/O error, dev hda, sector 115309
    > end_request: I/O error, dev hda, sector 115311
    > end_request: I/O error, dev hda, sector 115317
    > end_request: I/O error, dev hda, sector 115319
    > end_request: I/O error, dev hda, sector 115321
    > end_request: I/O error, dev hda, sector 115323
    > end_request: I/O error, dev hda, sector 115325
    > end_request: I/O error, dev hda, sector 115327
    > end_request: I/O error, dev hda, sector 115349
    > end_request: I/O error, dev hda, sector 131191
    > end_request: I/O error, dev hda, sector 262213
    > end_request: I/O error, dev hda, sector 262215
    > end_request: I/O error, dev hda, sector 262221
    > end_request: I/O error, dev hda, sector 262223
    > end_request: I/O error, dev hda, sector 262449
    > end_request: I/O error, dev hda, sector 262565
    > end_request: I/O error, dev hda, sector 262585
    > end_request: I/O error, dev hda, sector 262609
    > end_request: I/O error, dev hda, sector 262679
    > Aborting journal on device hda7.
    > end_request: I/O error, dev hda, sector 39976875
    > end_request: I/O error, dev hda, sector 40871067
    > end_request: I/O error, dev hda, sector 40873747
    > end_request: I/O error, dev hda, sector 40873867
    > __journal_remove_journal_head: freeing b_frozen_data
    > __journal_remove_journal_head: freeing b_frozen_data
    > __journal_remove_journal_head: freeing b_frozen_data
    > Aborting journal on device hda5.
    > end_request: I/O error, dev hda, sector 2741115
    > end_request: I/O error, dev hda, sector 2741467
    > end_request: I/O error, dev hda, sector 2741915
    > end_request: I/O error, dev hda, sector 2806707
    > end_request: I/O error, dev hda, sector 2806843
    > end_request: I/O error, dev hda, sector 2806851
    > end_request: I/O error, dev hda, sector 2806859
    > end_request: I/O error, dev hda, sector 2806867
    > end_request: I/O error, dev hda, sector 2806947
    > end_request: I/O error, dev hda, sector 2807035
    > end_request: I/O error, dev hda, sector 2807043
    > end_request: I/O error, dev hda, sector 2807059
    > end_request: I/O error, dev hda, sector 2807067
    > end_request: I/O error, dev hda, sector 2807131
    > end_request: I/O error, dev hda, sector 2807147
    > end_request: I/O error, dev hda, sector 2741171
    > end_request: I/O error, dev hda, sector 2741347
    > end_request: I/O error, dev hda, sector 2741611
    > ext3_abort called.
    > EXT3-fs error (device hda7): ext3_journal_start_sb: Detected aborted
    > journal Remounting filesystem read-only
    > ext3_abort called.
    > EXT3-fs error (device hda5): ext3_journal_start_sb: Detected aborted
    > journal Remounting filesystem read-only
    > end_request: I/O error, dev hda, sector 1102763
    > EXT3-fs error (device hda5): ext3_get_inode_loc: unable to read inode
    > block - inode=32883, block=65545
    > end_request: I/O error, dev hda, sector 30929763
    > EXT3-fs error (device hda6): ext3_get_inode_loc: unable to read inode
    > block - inode=65052, block=131100
    > end_request: I/O error, dev hda, sector 29880963
    > printk: 145 messages suppressed.
    > Buffer I/O error on device hda6, logical block 0
    > lost page write due to I/O error on hda6
    > EXT3-fs error (device hda6) in ext3_reserve_inode_write: IO failure
    > end_request: I/O error, dev hda, sector 29880963
    > Buffer I/O error on device hda6, logical block 0
    > lost page write due to I/O error on hda6
    > end_request: I/O error, dev hda, sector 5379
    > end_request: I/O error, dev hda, sector 5381
    > end_request: I/O error, dev hda, sector 5383
    > Aborting journal on device hda1.
    > end_request: I/O error, dev hda, sector 2151299
    > EXT3-fs error (device hda5): ext3_get_inode_loc: unable to read inode
    > block - inode=98115, block=196612
    > ext3_abort called.
    > EXT3-fs error (device hda1): ext3_journal_start_sb: Detected aborted
    > journal Remounting filesystem read-only
    > end_request: I/O error, dev hda, sector 37483315
    > EXT3-fs error (device hda6): ext3_get_inode_loc: unable to read inode
    > block - inode=466454, block=950294
    > end_request: I/O error, dev hda, sector 29880963
    > printk: 1 messages suppressed.
    > Buffer I/O error on device hda6, logical block 0
    > lost page write due to I/O error on hda6
    > EXT3-fs error (device hda6) in ext3_reserve_inode_write: IO failure
    > end_request: I/O error, dev hda, sector 29880963
    > end_request: I/O error, dev hda, sector 1889155
    > EXT3-fs error (device hda5): ext3_get_inode_loc: unable to read inode
    > block - inode=81764, block=163844
    > end_request: I/O error, dev hda, sector 30929763
    > EXT3-fs error (device hda6): ext3_get_inode_loc: unable to read inode
    > block - inode=65052, block=131100
    > end_request: I/O error, dev hda, sector 29880963
    > EXT3-fs error (device hda6) in ext3_reserve_inode_write: IO failure
    > end_request: I/O error, dev hda, sector 29880963
    > end_request: I/O error, dev hda, sector 1102723
    > EXT3-fs error (device hda5): ext3_get_inode_loc: unable to read inode
    > block - inode=32712, block=65540
    > end_request: I/O error, dev hda, sector 6083459
    > EXT3-fs error (device hda5): ext3_get_inode_loc: unable to read inode
    > block - inode=343393, block=688132
    > end_request: I/O error, dev hda, sector 1102811
    > EXT3-fs error (device hda5): ext3_get_inode_loc: unable to read inode
    > block - inode=33086, block=65551
    > end_request: I/O error, dev hda, sector 1102811
    > EXT3-fs error (device hda5): ext3_get_inode_loc: unable to read inode
    > block - inode=33087, block=65551
    > end_request: I/O error, dev hda, sector 1102819
    > EXT3-fs error (device hda5): ext3_get_inode_loc: unable to read inode
    > block - inode=33112, block=65552
    > end_request: I/O error, dev hda, sector 7394579
    > EXT3-fs error (device hda5): ext3_get_inode_loc: unable to read inode
    > block - inode=426780, block=852022
    > end_request: I/O error, dev hda, sector 1103747
    > EXT3-fs error (device hda5): ext3_get_inode_loc: unable to read inode
    > block - inode=36808, block=65668
    > end_request: I/O error, dev hda, sector 6083523
    > EXT3-fs error (device hda5): ext3_get_inode_loc: unable to read inode
    > block - inode=343650, block=688140
    > end_request: I/O error, dev hda, sector 1102763
    > EXT3-fs error (device hda5): ext3_get_inode_loc: unable to read inode
    > block - inode=32894, block=65545
    > end_request: I/O error, dev hda, sector 1102723
    > EXT3-fs error (device hda5): ext3_get_inode_loc: unable to read inode
    > block - inode=32713, block=65540
    > end_request: I/O error, dev hda, sector 1102827
    > EXT3-fs error (device hda5): ext3_get_inode_loc: unable to read inode
    > block - inode=33125, block=65553
    > end_request: I/O error, dev hda, sector 3199875
    > EXT3-fs error (device hda5): ext3_get_inode_loc: unable to read inode
    > block - inode=163524, block=327684
    > end_request: I/O error, dev hda, sector 3462723
    > EXT3-fs error (device hda5): ext3_get_inode_loc: unable to read inode
    > block - inode=182707, block=360540
    > end_request: I/O error, dev hda, sector 29890819
    > Aborting journal on device hda6.
    > ext3_abort called.
    > EXT3-fs error (device hda6): ext3_journal_start_sb: Detected aborted
    > journal Remounting filesystem read-only
    > end_request: I/O error, dev hda, sector 40697075
    > printk: 4 messages suppressed.
    > Buffer I/O error on device hda7, logical block 131074
    > lost page write due to I/O error on hda7
    > end_request: I/O error, dev hda, sector 40697083
    > Buffer I/O error on device hda7, logical block 131075
    > lost page write due to I/O error on hda7
    > end_request: I/O error, dev hda, sector 40697091
    > Buffer I/O error on device hda7, logical block 131076
    > lost page write due to I/O error on hda7
    > end_request: I/O error, dev hda, sector 2675587
    > end_request: I/O error, dev hda, sector 2675595
    > end_request: I/O error, dev hda, sector 2675643
    > end_request: I/O error, dev hda, sector 2675651
    > end_request: I/O error, dev hda, sector 262603
    > printk: 4 messages suppressed.
    > Buffer I/O error on device hda1, logical block 131270
    > lost page write due to I/O error on hda1
    >
    > I had to power off and on my PC (couldn't do a normal shutdown and the
    > reset button didn't work).
    >
    >
    > Things were calm for maybe 10 minutes, then again:
    > hdb: dma_timer_expiry: dma status == 0x61
    > hdb: DMA timeout error
    > hdb: dma timeout error: status=0x58 { DriveReady SeekComplete
    > DataRequest } ide: failed opcode was: unknown
    > hda: DMA disabled
    > hdb: DMA disabled
    > ide0: reset: success
    >
    > I ran smartctl -a on both drives:
    > # smartctl -a /dev/hda
    > smartctl version 5.38 [i686-pc-linux-gnu] Copyright (C) 2002-8 Bruce
    > Allen Home page is http://smartmontools.sourceforge.net/
    >
    > === START OF INFORMATION SECTION ===
    > Model Family: Seagate Barracuda 7200.7 and 7200.7 Plus family
    > Device Model: ST380011A
    > Serial Number: 4JV5P7LN
    > Firmware Version: 8.01
    > User Capacity: 80,026,361,856 bytes
    > Device is: In smartctl database [for details use: -P show]
    > ATA Version is: 6
    > ATA Standard is: ATA/ATAPI-6 T13 1410D revision 2
    > Local Time is: Tue Aug 12 22:15:59 2008 PDT
    > SMART support is: Available - device has SMART capability.
    > SMART support is: Enabled
    >
    > === START OF READ SMART DATA SECTION ===
    > SMART overall-health self-assessment test result: PASSED
    >
    > General SMART Values:
    > Offline data collection status: (0x82) Offline data collection
    > activity was completed
    > without error. Auto Offline
    > Data Collection: Enabled.
    > Self-test execution status: ( 0) The previous self-test routine
    > completed
    > without error or no self-test
    > has ever
    > been run.
    > Total time to complete Offline
    > data collection: ( 430) seconds.
    > Offline data collection
    > capabilities: (0x5b) SMART execute Offline
    > immediate. Auto Offline data
    > collection on/off support.
    > Suspend Offline collection
    > upon new command.
    > Offline surface scan
    > supported. Self-test
    > supported. No Conveyance
    > Self-test supported.
    > Selective Self-test supported. SMART capabilities: (0x0003) Saves SMART data before
    > entering power-saving mode.
    > Supports SMART auto save
    > timer. Error logging capability: (0x01) Error logging
    > supported. General Purpose
    > Logging supported. Short self-test routine
    > recommended polling time: ( 1) minutes.
    > Extended self-test routine
    > recommended polling time: ( 58) minutes.
    >
    > SMART Attributes Data Structure revision number: 10
    > Vendor Specific SMART Attributes with Thresholds:
    > ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE
    > UPDATED WHEN_FAILED RAW_VALUE
    > 1 Raw_Read_Error_Rate 0x000f 060 057 006 Pre-fail
    > Always - 81109586
    > 3 Spin_Up_Time 0x0003 098 098 000 Pre-fail
    > Always - 0
    > 4 Start_Stop_Count 0x0032 100 100 020 Old_age
    > Always - 0
    > 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail
    > Always - 0
    > 7 Seek_Error_Rate 0x000f 082 060 030 Pre-fail
    > Always - 195706519
    > 9 Power_On_Hours 0x0032 075 075 000 Old_age
    > Always - 22212
    > 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail
    > Always - 0
    > 12 Power_Cycle_Count 0x0032 100 100 020 Old_age
    > Always - 120
    > 194 Temperature_Celsius 0x0022 032 048 000 Old_age Always - 32
    > 195 Hardware_ECC_Recovered 0x001a 060 057 000 Old_age Always - 81109586
    > 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0
    > 198 Offline_Uncorrectable 0x0010 100 100 000 Old_age
    > Offline - 0
    > 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0
    > 200 Multi_Zone_Error_Rate 0x0000 100 253 000 Old_age
    > Offline - 0
    > 202 TA_Increase_Count 0x0032 100 253 000 Old_age Always - 0
    >
    > SMART Error Log Version: 1
    > No Errors Logged
    >
    > SMART Self-test log structure revision number 1
    > Num Test_Description Status Remaining
    > LifeTime(hours) LBA_of_first_error
    > # 1 Extended offline Completed without error 00% 18951
    > -
    > # 2 Extended offline Completed without error 00% 18674
    > -
    > # 3 Extended offline Completed without error 00% 15957
    > -
    > # 4 Extended offline Completed without error 00% 14448
    > -
    >
    > SMART Selective self-test log data structure revision number 1
    > SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
    > 1 0 0 Not_testing
    > 2 0 0 Not_testing
    > 3 0 0 Not_testing
    > 4 0 0 Not_testing
    > 5 0 0 Not_testing
    > Selective self-test flags (0x0):
    > After scanning selected spans, do NOT read-scan remainder of disk.
    > If Selective self-test is pending on power-up, resume after 0 minute
    > delay.
    > # smartctl -a /dev/hdb
    > smartctl version 5.38 [i686-pc-linux-gnu] Copyright (C) 2002-8 Bruce
    > Allen Home page is http://smartmontools.sourceforge.net/
    >
    > === START OF INFORMATION SECTION ===
    > Device Model: QUANTUM FIREBALL EX6.4A
    > Serial Number: 376833611720
    > Firmware Version: A0A.0D00
    > User Capacity: 6,448,619,520 bytes
    > Device is: In smartctl database [for details use: -P show]
    > ATA Version is: 4
    > ATA Standard is: ATA/ATAPI-4 T13 1153D revision 15
    > Local Time is: Tue Aug 12 22:16:25 2008 PDT
    > SMART support is: Available - device has SMART capability.
    > SMART support is: Enabled
    >
    > Error SMART Status command failed: Input/output error
    > A mandatory SMART command failed: exiting. To continue, add one or
    > more '-T permissive' options.
    >
    > Then, my Linux pauses becuse hdb went funky. I rechecked my dmesg
    > (might old dupes from earlier):
    > hdb: dma_timer_expiry: dma status == 0x61
    > hdb: DMA timeout error
    > hdb: dma timeout error: status=0x58 { DriveReady SeekComplete
    > DataRequest } ide: failed opcode was: unknown
    > hda: DMA disabled
    > hdb: DMA disabled
    > ide0: reset: success
    > hdb: drive_cmd: status=0x7d { DriveReady DeviceFault SeekComplete
    > DataRequest CorrectedError Error }
    > hdb: drive_cmd: error=0x7d { DriveStatusError UncorrectableError
    > SectorIdNotFound AddrMarkNotFound }, LBAsect=226327933, sector=0
    > ide: failed opcode was: 0xb0
    > hdb: dma_timer_expiry: dma status == 0x61
    > hdb: DMA timeout error
    > hdb: dma timeout error: status=0x58 { DriveReady SeekComplete
    > DataRequest } ide: failed opcode was: unknown
    > hda: DMA disabled
    > hdb: DMA disabled
    > ide0: reset: success
    > hdb: dma_timer_expiry: dma status == 0x61
    > hdb: DMA timeout error
    > hdb: dma timeout error: status=0x58 { DriveReady SeekComplete
    > DataRequest } ide: failed opcode was: unknown
    > hda: DMA disabled
    > hdb: DMA disabled
    > ide0: reset: success
    > hdb: dma_timer_expiry: dma status == 0x41
    > hdb: DMA timeout error
    > hdb: dma timeout error: status=0x58 { DriveReady SeekComplete
    > DataRequest } ide: failed opcode was: unknown
    > hdb: DMA disabled
    > ide0: reset: success
    >
    >
    > # smartctl -a /dev/hdb
    > smartctl version 5.38 [i686-pc-linux-gnu] Copyright (C) 2002-8 Bruce
    > Allen Home page is http://smartmontools.sourceforge.net/
    >
    > === START OF INFORMATION SECTION ===
    > Device Model: QUANTUM FIREBALL EX6.4A
    > Serial Number: 376833611720
    > Firmware Version: A0A.0D00
    > User Capacity: 6,448,619,520 bytes
    > Device is: In smartctl database [for details use: -P show]
    > ATA Version is: 4
    > ATA Standard is: ATA/ATAPI-4 T13 1153D revision 15
    > Local Time is: Tue Aug 12 22:19:21 2008 PDT
    > SMART support is: Available - device has SMART capability.
    > SMART support is: Enabled
    >
    > === START OF READ SMART DATA SECTION ===
    > SMART overall-health self-assessment test result: PASSED
    >
    > General SMART Values:
    > Offline data collection status: (0x82) Offline data collection
    > activity was completed
    > without error. Auto Offline
    > Data Collection: Enabled.
    > Total time to complete Offline
    > data collection: ( 1) seconds.
    > Offline data collection
    > capabilities: (0x03) SMART execute Offline
    > immediate. Auto Offline data
    > collection on/off support.
    > Suspend Offline collection
    > upon new command.
    > No Offline surface scan
    > supported. No Self-test
    > supported. No Conveyance
    > Self-test supported. No
    > Selective Self-test supported. SMART capabilities: (0x0003) Saves SMART data before
    > entering power-saving mode.
    > Supports SMART auto save
    > timer. Error logging capability: (0x00) Error logging NOT
    > supported. No General Purpose
    > Logging support.
    > SMART Attributes Data Structure revision number: 7
    > Vendor Specific SMART Attributes with Thresholds:
    > ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE
    > UPDATED WHEN_FAILED RAW_VALUE
    > 1 Raw_Read_Error_Rate 0x0029 100 100 020 Pre-fail
    > Offline - 0
    > 3 Spin_Up_Time 0x0027 089 076 020 Pre-fail
    > Always - 1489
    > 4 Start_Stop_Count 0x0032 099 099 008 Old_age
    > Always - 1198
    > 5 Reallocated_Sector_Ct 0x0033 100 100 020 Pre-fail
    > Always - 0
    > 7 Seek_Error_Rate 0x000b 100 100 023 Pre-fail
    > Always - 0
    > 9 Power_On_Hours 0x0012 007 007 001 Old_age
    > Always - 61139
    > 11 Calibration_Retry_Count 0x0013 100 100 020 Pre-fail
    > Always - 0
    > 12 Power_Cycle_Count 0x0032 099 099 008 Old_age
    > Always - 1191
    > 13 Read_Soft_Error_Rate 0x000b 100 100 023 Pre-fail
    > Always - 0
    > 199 UDMA_CRC_Error_Count 0x001a 200 200 000 Old_age Always - 0
    >
    > Warning: device does not support Error Logging
    > SMART Error Log Version: 0
    > No Errors Logged
    >
    > Warning: device does not support Self Test Logging
    > SMART Self-test log structure revision number 0
    > Warning: ATA Specification requires self-test log structure revision
    > number = 1
    > No self-tests have been logged. [To run self-tests, use: smartctl -t]


    > Device does not support Selective Self Tests/Logging


    > What's going on with my HDDs?


    Something's died, Jim. You into necrophilia ?

    > I am not a hardware and Linux/Debian expert. My hardware specifications can be found here:
    > http://alpha.zimage.com/~ant/antfarm.../computers.txt
    > (secondary/backup computer). For now, I am going to unmount /dev/hdb to see if hdb is causing all this madness.


    There's certainly quite a few bad sectors on that drive.

    That shouldnt have produced the errors with the other drive tho so something else has died too.

    The system appears to be pretty comprehensively ****ed.

    It would be worth trying a spare power supply, it might be something as basic as that.

    Worth checking for bad caps on the motherboard too. These are the usually blue or
    black plastic covered post like things that stick up vertically from the motherboard surface.
    The tops should be flat. If any have bulged or have leaked, thats a bad cap and for someone
    like you the only real fix is to replace the motherboard. May be better to just bin the PC tho.



  5. Re: Bad disk controller? Dying HDD?

    On 8/12/2008 11:08 PM PT, Rod Speed typed:

    > Ant wrote:
    >> Hi. My old mini-tower PC's HDDs are acting crazy today. I came home
    >> and noticed my second drive wasn't there so I checked dmesg (deleted
    >> normal logs before hdb):
    >>
    >> hdb: dma_timer_expiry: dma status == 0x61
    >> hdb: DMA timeout error
    >> hdb: dma timeout error: status=0x58 { DriveReady SeekComplete
    >> DataRequest }
    >> ide: failed opcode was: unknown
    >> hda: DMA disabled
    >> hdb: DMA disabled
    >> ide0: reset: success
    >> hdb: dma_intr: status=0x7d { DriveReady DeviceFault SeekComplete
    >> DataRequest CorrectedError Error }
    >> hdb: dma_intr: error=0x7d { DriveStatusError UncorrectableError
    >> SectorIdNotFound AddrMarkNotFound }, LBAsect=226327933, sector=3522545
    >> ide: failed opcode was: unknown
    >> hdb: DMA disabled
    >> ide0: reset: success
    >> hdb: task_in_intr: status=0x7d { DriveReady DeviceFault SeekComplete
    >> DataRequest CorrectedError Error }
    >> hdb: task_in_intr: error=0x7d { DriveStatusError UncorrectableError
    >> SectorIdNotFound AddrMarkNotFound }, LBAsect=226327933, sector=2362513
    >> ide: failed opcode was: unknown
    >> ide0: reset: success
    >> hdb: task_in_intr: status=0x7d { DriveReady DeviceFault SeekComplete
    >> DataRequest CorrectedError Error }
    >> hdb: task_in_intr: error=0x7d { DriveStatusError UncorrectableError
    >> SectorIdNotFound AddrMarkNotFound }, LBAsect=226327933, sector=2362513
    >> ide: failed opcode was: unknown
    >> ide0: reset: success
    >> ABORTED IN=eth0 OUT= MAC=00:d0:b7:85:0a:3f:00:a0:c5:e3:18:a8:08:00
    >> SRC=216.86.199.5 DST=192.168.0.32 LEN=40 TOS=0x00 PREC=0x00 TTL=46
    >> ID=15957 DF PROTO=TCP SPT=6667 DPT=1788 SEQ=2622437680 ACK=0 WINDOW=0
    >> RES=0x00 RST URGP=0
    >> hdb: task_in_intr: status=0x7d { DriveReady DeviceFault SeekComplete
    >> DataRequest CorrectedError Error }
    >> hdb: task_in_intr: error=0x7d { DriveStatusError UncorrectableError
    >> SectorIdNotFound AddrMarkNotFound }, LBAsect=226327933, sector=3537401
    >> ide: failed opcode was: unknown
    >> ide0: reset: success
    >> hdb: task_in_intr: status=0x7d { DriveReady DeviceFault SeekComplete
    >> DataRequest CorrectedError Error }
    >> hdb: task_in_intr: error=0x7d { DriveStatusError UncorrectableError
    >> SectorIdNotFound AddrMarkNotFound }, LBAsect=226327933, sector=3537401
    >> ide: failed opcode was: unknown
    >> ide0: reset timed-out, status=0x90
    >> hdb: status error: status=0x7d { DriveReady DeviceFault SeekComplete
    >> DataRequest CorrectedError Error }
    >> hdb: status error: error=0x7d { DriveStatusError UncorrectableError
    >> SectorIdNotFound AddrMarkNotFound }, LBAsect=226327933, sector=3537401
    >> ide: failed opcode was: unknown
    >> end_request: I/O error, dev hdb, sector 3537401
    >> hdb: drive not ready for command
    >> hdb: status error: status=0x7d { DriveReady DeviceFault SeekComplete
    >> DataRequest CorrectedError Error }
    >> hdb: status error: error=0x7d { DriveStatusError UncorrectableError
    >> SectorIdNotFound AddrMarkNotFound }, LBAsect=226327933, sector=3537409
    >> ide: failed opcode was: unknown
    >> hdb: drive not ready for command
    >> ide0: reset timed-out, status=0x90
    >> end_request: I/O error, dev hdb, sector 3537409
    >> end_request: I/O error, dev hdb, sector 3537417
    >> end_request: I/O error, dev hdb, sector 3537425
    >> end_request: I/O error, dev hdb, sector 3537401
    >> end_request: I/O error, dev hdb, sector 3538825
    >> end_request: I/O error, dev hdb, sector 3538833
    >> end_request: I/O error, dev hdb, sector 3538841
    >> end_request: I/O error, dev hdb, sector 3538849
    >> end_request: I/O error, dev hdb, sector 3538825
    >> end_request: I/O error, dev hdb, sector 3537977
    >> end_request: I/O error, dev hdb, sector 3537985
    >> end_request: I/O error, dev hdb, sector 3537993
    >> end_request: I/O error, dev hdb, sector 3538001
    >> end_request: I/O error, dev hdb, sector 3537977
    >> end_request: I/O error, dev hdb, sector 3536889
    >> end_request: I/O error, dev hdb, sector 3536897
    >> end_request: I/O error, dev hdb, sector 3536905
    >> end_request: I/O error, dev hdb, sector 3536913
    >> end_request: I/O error, dev hdb, sector 3536889
    >> end_request: I/O error, dev hdb, sector 3539689
    >> end_request: I/O error, dev hdb, sector 3539697
    >> end_request: I/O error, dev hdb, sector 3539705
    >> end_request: I/O error, dev hdb, sector 3539713
    >> end_request: I/O error, dev hdb, sector 3539689
    >> end_request: I/O error, dev hdb, sector 3544185
    >> end_request: I/O error, dev hdb, sector 3544193
    >> end_request: I/O error, dev hdb, sector 3544201
    >> end_request: I/O error, dev hdb, sector 3544209
    >> end_request: I/O error, dev hdb, sector 3544185
    >> end_request: I/O error, dev hdb, sector 3540457
    >> end_request: I/O error, dev hdb, sector 3540465
    >> end_request: I/O error, dev hdb, sector 3540473
    >> end_request: I/O error, dev hdb, sector 3540481
    >> end_request: I/O error, dev hdb, sector 3540457
    >> end_request: I/O error, dev hdb, sector 3542089
    >> end_request: I/O error, dev hdb, sector 3542097
    >> end_request: I/O error, dev hdb, sector 3542105
    >> end_request: I/O error, dev hdb, sector 3542113
    >> end_request: I/O error, dev hdb, sector 3542089
    >> end_request: I/O error, dev hdb, sector 3542897
    >> end_request: I/O error, dev hdb, sector 3542905
    >> end_request: I/O error, dev hdb, sector 3542913
    >> end_request: I/O error, dev hdb, sector 3542921
    >> end_request: I/O error, dev hdb, sector 3542897
    >> end_request: I/O error, dev hdb, sector 7257
    >> end_request: I/O error, dev hdb, sector 7265
    >> end_request: I/O error, dev hdb, sector 7273
    >> journal_bmap: journal block not found at offset 12 on hdb1
    >> Aborting journal on device hdb1.
    >> end_request: I/O error, dev hdb, sector 7177
    >> Buffer I/O error on device hdb1, logical block 897
    >> lost page write due to I/O error on hdb1
    >> end_request: I/O error, dev hdb, sector 2362529
    >> Buffer I/O error on device hdb1, logical block 295316
    >> lost page write due to I/O error on hdb1
    >> ABORTED IN=eth0 OUT= MAC=00:d0:b7:85:0a:3f:00:a0:c5:e3:18:a8:08:00
    >> SRC=64.22.96.69 DST=192.168.0.32 LEN=40 TOS=0x00 PREC=0x00 TTL=50 ID=0
    >> DF PROTO=TCP SPT=35249 DPT=22 SEQ=481307265 ACK=0 WINDOW=0 RES=0x00
    >> RST URGP=0
    >> ABORTED IN=eth0 OUT= MAC=00:d0:b7:85:0a:3f:00:a0:c5:e3:18:a8:08:00
    >> SRC=64.22.96.69 DST=192.168.0.32 LEN=40 TOS=0x00 PREC=0x00 TTL=50 ID=0
    >> DF PROTO=TCP SPT=35249 DPT=22 SEQ=481307265 ACK=0 WINDOW=0 RES=0x00
    >> RST URGP=0
    >> end_request: I/O error, dev hdb, sector 3543081
    >> end_request: I/O error, dev hdb, sector 3543089
    >> end_request: I/O error, dev hdb, sector 3543097
    >> end_request: I/O error, dev hdb, sector 3543105
    >> end_request: I/O error, dev hdb, sector 3543081
    >> ext3_abort called.
    >> EXT3-fs error (device hdb1): ext3_journal_start_sb: Detected aborted
    >> journal
    >> Remounting filesystem read-only
    >> end_request: I/O error, dev hdb, sector 3533193
    >> end_request: I/O error, dev hdb, sector 3533201
    >> end_request: I/O error, dev hdb, sector 3533209
    >> end_request: I/O error, dev hdb, sector 3533217
    >> end_request: I/O error, dev hdb, sector 3533193
    >> end_request: I/O error, dev hdb, sector 3533193
    >> end_request: I/O error, dev hdb, sector 3533193
    >> end_request: I/O error, dev hdb, sector 3533193
    >> end_request: I/O error, dev hdb, sector 3533193
    >> end_request: I/O error, dev hdb, sector 3533193
    >> end_request: I/O error, dev hdb, sector 2362529
    >> EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    >> block - inode=72691, block=295316
    >> end_request: I/O error, dev hdb, sector 3533193
    >> end_request: I/O error, dev hdb, sector 3533193
    >> end_request: I/O error, dev hdb, sector 3533193
    >> end_request: I/O error, dev hdb, sector 3533193
    >> end_request: I/O error, dev hdb, sector 3533193
    >> end_request: I/O error, dev hdb, sector 3533193
    >> ABORTED IN=eth0 OUT= MAC=00:d0:b7:85:0a:3f:00:16:17:94:32:d6:08:00
    >> SRC=192.168.0.46 DST=192.168.0.32 LEN=40 TOS=0x00 PREC=0x00 TTL=64
    >> ID=230 PROTO=TCP SPT=1056 DPT=139 SEQ=1299343103 ACK=1299343103
    >> WINDOW=0 RES=0x00 RST URGP=0
    >> ABORTED IN=eth0 OUT= MAC=00:d0:b7:85:0a:3f:00:16:17:94:32:d6:08:00
    >> SRC=192.168.0.46 DST=192.168.0.32 LEN=40 TOS=0x00 PREC=0x00 TTL=64
    >> ID=1980 PROTO=TCP SPT=1261 DPT=139 SEQ=969640467 ACK=969640467
    >> WINDOW=0 RES=0x00 RST URGP=0
    >> end_request: I/O error, dev hdb, sector 2362721
    >> EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    >> block - inode=73086, block=295340
    >> end_request: I/O error, dev hdb, sector 2362801
    >> EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    >> block - inode=73240, block=295350
    >> end_request: I/O error, dev hdb, sector 2362753
    >> EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    >> block - inode=73146, block=295344
    >> end_request: I/O error, dev hdb, sector 2362729
    >> EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    >> block - inode=73092, block=295341
    >> end_request: I/O error, dev hdb, sector 2362729
    >> EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    >> block - inode=73093, block=295341
    >> end_request: I/O error, dev hdb, sector 2362745
    >> EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    >> block - inode=73121, block=295343
    >> end_request: I/O error, dev hdb, sector 2362729
    >> EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    >> block - inode=73089, block=295341
    >> end_request: I/O error, dev hdb, sector 4568761
    >> end_request: I/O error, dev hdb, sector 2362753
    >> EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    >> block - inode=73140, block=295344
    >> end_request: I/O error, dev hdb, sector 2362729
    >> EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    >> block - inode=73100, block=295341
    >> end_request: I/O error, dev hdb, sector 2362737
    >> EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    >> block - inode=73113, block=295342
    >> end_request: I/O error, dev hdb, sector 2362745
    >> EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    >> block - inode=73129, block=295343
    >> end_request: I/O error, dev hdb, sector 2362745
    >> EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    >> block - inode=73135, block=295343
    >> end_request: I/O error, dev hdb, sector 2362761
    >> EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    >> block - inode=73164, block=295345
    >> end_request: I/O error, dev hdb, sector 2362753
    >> EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    >> block - inode=73142, block=295344
    >> end_request: I/O error, dev hdb, sector 2362761
    >> EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    >> block - inode=73162, block=295345
    >> end_request: I/O error, dev hdb, sector 2362729
    >> EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    >> block - inode=73104, block=295341
    >> end_request: I/O error, dev hdb, sector 2362745
    >> EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    >> block - inode=73128, block=295343
    >> end_request: I/O error, dev hdb, sector 2362745
    >> EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    >> block - inode=73122, block=295343
    >> end_request: I/O error, dev hdb, sector 2362761
    >> EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    >> block - inode=73153, block=295345
    >> end_request: I/O error, dev hdb, sector 2362753
    >> EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    >> block - inode=73141, block=295344
    >> end_request: I/O error, dev hdb, sector 2362753
    >> EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    >> block - inode=73144, block=295344
    >> end_request: I/O error, dev hdb, sector 2362753
    >> EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    >> block - inode=73148, block=295344
    >> end_request: I/O error, dev hdb, sector 2362753
    >> EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    >> block - inode=73139, block=295344
    >> end_request: I/O error, dev hdb, sector 2362729
    >> EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    >> block - inode=73095, block=295341
    >> end_request: I/O error, dev hdb, sector 2362745
    >> EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    >> block - inode=73127, block=295343
    >> end_request: I/O error, dev hdb, sector 2362745
    >> EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    >> block - inode=73134, block=295343
    >> end_request: I/O error, dev hdb, sector 2362753
    >> EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    >> block - inode=73152, block=295344
    >> end_request: I/O error, dev hdb, sector 2362753
    >> EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    >> block - inode=73149, block=295344
    >> end_request: I/O error, dev hdb, sector 2362761
    >> EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    >> block - inode=73155, block=295345
    >> end_request: I/O error, dev hdb, sector 2362745
    >> EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    >> block - inode=73131, block=295343
    >> end_request: I/O error, dev hdb, sector 2362761
    >> EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    >> block - inode=73168, block=295345
    >> end_request: I/O error, dev hdb, sector 2362745
    >> EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    >> block - inode=73132, block=295343
    >> end_request: I/O error, dev hdb, sector 2362737
    >> EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    >> block - inode=73118, block=295342
    >> end_request: I/O error, dev hdb, sector 2362761
    >> EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    >> block - inode=73158, block=295345
    >> end_request: I/O error, dev hdb, sector 2362729
    >> EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    >> block - inode=73103, block=295341
    >> end_request: I/O error, dev hdb, sector 2588673
    >> end_request: I/O error, dev hdb, sector 2362729
    >> EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    >> block - inode=73101, block=295341
    >> end_request: I/O error, dev hdb, sector 2362753
    >> EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    >> block - inode=73138, block=295344
    >> end_request: I/O error, dev hdb, sector 2362761
    >> EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    >> block - inode=73167, block=295345
    >> end_request: I/O error, dev hdb, sector 2362729
    >> EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    >> block - inode=73102, block=295341
    >> end_request: I/O error, dev hdb, sector 2362761
    >> EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    >> block - inode=73165, block=295345
    >> end_request: I/O error, dev hdb, sector 2362745
    >> EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    >> block - inode=73125, block=295343
    >> end_request: I/O error, dev hdb, sector 2362737
    >> EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    >> block - inode=73110, block=295342
    >> end_request: I/O error, dev hdb, sector 2362737
    >> EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    >> block - inode=73109, block=295342
    >> end_request: I/O error, dev hdb, sector 2362769
    >> EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    >> block - inode=73169, block=295346
    >> end_request: I/O error, dev hdb, sector 3651025
    >> end_request: I/O error, dev hdb, sector 2362761
    >> EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    >> block - inode=73157, block=295345
    >> end_request: I/O error, dev hdb, sector 2362729
    >> EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    >> block - inode=73097, block=295341
    >> end_request: I/O error, dev hdb, sector 2362737
    >> EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    >> block - inode=73106, block=295342
    >> end_request: I/O error, dev hdb, sector 2362737
    >> EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    >> block - inode=73114, block=295342
    >> end_request: I/O error, dev hdb, sector 2362761
    >> EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    >> block - inode=73166, block=295345
    >> end_request: I/O error, dev hdb, sector 2362737
    >> EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    >> block - inode=73117, block=295342
    >> end_request: I/O error, dev hdb, sector 2362737
    >> EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    >> block - inode=73120, block=295342
    >> end_request: I/O error, dev hdb, sector 2362753
    >> EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    >> block - inode=73150, block=295344
    >> end_request: I/O error, dev hdb, sector 2362729
    >> EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    >> block - inode=73091, block=295341
    >> end_request: I/O error, dev hdb, sector 2362753
    >> EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    >> block - inode=73147, block=295344
    >> end_request: I/O error, dev hdb, sector 2362729
    >> EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    >> block - inode=73099, block=295341
    >> end_request: I/O error, dev hdb, sector 2362761
    >> EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    >> block - inode=73154, block=295345
    >> end_request: I/O error, dev hdb, sector 2362745
    >> EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    >> block - inode=73124, block=295343
    >> end_request: I/O error, dev hdb, sector 2362737
    >> EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    >> block - inode=73108, block=295342
    >> end_request: I/O error, dev hdb, sector 2362737
    >> EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    >> block - inode=73116, block=295342
    >> end_request: I/O error, dev hdb, sector 2362753
    >> EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    >> block - inode=73137, block=295344
    >> end_request: I/O error, dev hdb, sector 2362737
    >> EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    >> block - inode=73111, block=295342
    >> end_request: I/O error, dev hdb, sector 4568729
    >> end_request: I/O error, dev hdb, sector 2362737
    >> EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    >> block - inode=73119, block=295342
    >> end_request: I/O error, dev hdb, sector 2362729
    >> EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    >> block - inode=73098, block=295341
    >> end_request: I/O error, dev hdb, sector 4567841
    >> end_request: I/O error, dev hdb, sector 2362721
    >> EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    >> block - inode=73088, block=295340
    >> end_request: I/O error, dev hdb, sector 2362737
    >> EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    >> block - inode=73105, block=295342
    >> end_request: I/O error, dev hdb, sector 2362729
    >> EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    >> block - inode=73090, block=295341
    >> end_request: I/O error, dev hdb, sector 2362745
    >> EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    >> block - inode=73133, block=295343
    >> end_request: I/O error, dev hdb, sector 2362761
    >> EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    >> block - inode=73161, block=295345
    >> end_request: I/O error, dev hdb, sector 2362737
    >> EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    >> block - inode=73115, block=295342
    >> end_request: I/O error, dev hdb, sector 2362745
    >> EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    >> block - inode=73136, block=295343
    >> end_request: I/O error, dev hdb, sector 2362745
    >> EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    >> block - inode=73123, block=295343
    >> end_request: I/O error, dev hdb, sector 2362761
    >> EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    >> block - inode=73160, block=295345
    >> end_request: I/O error, dev hdb, sector 2362737
    >> EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    >> block - inode=73112, block=295342
    >> end_request: I/O error, dev hdb, sector 2362761
    >> EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    >> block - inode=73156, block=295345
    >> end_request: I/O error, dev hdb, sector 2362761
    >> EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    >> block - inode=73159, block=295345
    >> end_request: I/O error, dev hdb, sector 2362753
    >> EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    >> block - inode=73151, block=295344
    >> end_request: I/O error, dev hdb, sector 2362729
    >> EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    >> block - inode=73094, block=295341
    >> end_request: I/O error, dev hdb, sector 2362729
    >> EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    >> block - inode=73096, block=295341
    >> end_request: I/O error, dev hdb, sector 2362745
    >> EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    >> block - inode=73130, block=295343
    >> end_request: I/O error, dev hdb, sector 2362737
    >> EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    >> block - inode=73107, block=295342
    >> end_request: I/O error, dev hdb, sector 2362761
    >> EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    >> block - inode=73163, block=295345
    >> end_request: I/O error, dev hdb, sector 2362745
    >> EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    >> block - inode=73126, block=295343
    >> end_request: I/O error, dev hdb, sector 3648201
    >> end_request: I/O error, dev hdb, sector 2362753
    >> EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    >> block - inode=73143, block=295344
    >> end_request: I/O error, dev hdb, sector 2362753
    >> EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    >> block - inode=73145, block=295344
    >> end_request: I/O error, dev hdb, sector 2710017
    >> end_request: I/O error, dev hdb, sector 2605065
    >> end_request: I/O error, dev hdb, sector 3544825
    >> end_request: I/O error, dev hdb, sector 2362505
    >> EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    >> block - inode=72647, block=295313
    >> end_request: I/O error, dev hdb, sector 2362529
    >> EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    >> block - inode=72689, block=295316
    >> end_request: I/O error, dev hdb, sector 2362505
    >> EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    >> block - inode=72643, block=295313
    >> end_request: I/O error, dev hdb, sector 2362521
    >> EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    >> block - inode=72678, block=295315
    >> end_request: I/O error, dev hdb, sector 3522817
    >> end_request: I/O error, dev hdb, sector 2362521
    >> EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    >> block - inode=72682, block=295315
    >> end_request: I/O error, dev hdb, sector 2362521
    >> EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    >> block - inode=72687, block=295315
    >> end_request: I/O error, dev hdb, sector 2362505
    >> EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    >> block - inode=72648, block=295313
    >> end_request: I/O error, dev hdb, sector 2362521
    >> EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    >> block - inode=72683, block=295315
    >> end_request: I/O error, dev hdb, sector 2362505
    >> EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    >> block - inode=72650, block=295313
    >> end_request: I/O error, dev hdb, sector 2362505
    >> EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    >> block - inode=72649, block=295313
    >> end_request: I/O error, dev hdb, sector 2362521
    >> EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    >> block - inode=72673, block=295315
    >> end_request: I/O error, dev hdb, sector 2362505
    >> EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    >> block - inode=72653, block=295313
    >> end_request: I/O error, dev hdb, sector 2362505
    >> EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    >> block - inode=72641, block=295313
    >> end_request: I/O error, dev hdb, sector 2362521
    >> EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    >> block - inode=72674, block=295315
    >> end_request: I/O error, dev hdb, sector 2362521
    >> EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    >> block - inode=72685, block=295315
    >> end_request: I/O error, dev hdb, sector 2362521
    >> EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    >> block - inode=72676, block=295315
    >> end_request: I/O error, dev hdb, sector 2362521
    >> EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    >> block - inode=72686, block=295315
    >> end_request: I/O error, dev hdb, sector 3522553
    >> end_request: I/O error, dev hdb, sector 3524505
    >> end_request: I/O error, dev hdb, sector 2362521
    >> EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    >> block - inode=72681, block=295315
    >> end_request: I/O error, dev hdb, sector 2362505
    >> EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    >> block - inode=72645, block=295313
    >> end_request: I/O error, dev hdb, sector 2362505
    >> EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    >> block - inode=72646, block=295313
    >> end_request: I/O error, dev hdb, sector 2362521
    >> EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    >> block - inode=72675, block=295315
    >> end_request: I/O error, dev hdb, sector 2362505
    >> EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    >> block - inode=72651, block=295313
    >> end_request: I/O error, dev hdb, sector 2362521
    >> EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    >> block - inode=72680, block=295315
    >> end_request: I/O error, dev hdb, sector 2362521
    >> EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    >> block - inode=72679, block=295315
    >> end_request: I/O error, dev hdb, sector 2362505
    >> EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    >> block - inode=72654, block=295313
    >> end_request: I/O error, dev hdb, sector 2362505
    >> EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    >> block - inode=72655, block=295313
    >> end_request: I/O error, dev hdb, sector 2362521
    >> EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    >> block - inode=72677, block=295315
    >> end_request: I/O error, dev hdb, sector 2362505
    >> EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    >> block - inode=72656, block=295313
    >> end_request: I/O error, dev hdb, sector 2362521
    >> EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    >> block - inode=72684, block=295315
    >> end_request: I/O error, dev hdb, sector 2362497
    >> EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    >> block - inode=72640, block=295312
    >> end_request: I/O error, dev hdb, sector 2362505
    >> EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    >> block - inode=72642, block=295313
    >> end_request: I/O error, dev hdb, sector 2362505
    >> EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    >> block - inode=72644, block=295313
    >> end_request: I/O error, dev hdb, sector 2362529
    >> EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    >> block - inode=72690, block=295316
    >> end_request: I/O error, dev hdb, sector 2362505
    >> EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    >> block - inode=72652, block=295313
    >> end_request: I/O error, dev hdb, sector 2362521
    >> EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    >> block - inode=72688, block=295315
    >> end_request: I/O error, dev hdb, sector 5119177

    >
    >> I did an unmount of hdb, fdisk /dev/hdb, and it couldn't read it. I did a reboot, HDD showed up in CMOS/BIOS and
    >> Debian went to its safe mode and let me fsck it. fsck /dev/hdb said all ext3 journals got lost and
    >> reverted back to ext2. I fsck'ed. After reboot and remounting, it
    >> seems the files were OK? So I put journal back and things were OK.

    >
    >> A few minutes later, things go crazy again:
    >> $ dmesg
    >> e PFN ranges
    >> 0: 0 -> 130864
    >> On node 0 totalpages: 130864
    >> DMA zone: 32 pages used for memmap
    >> DMA zone: 0 pages reserved
    >> DMA zone: 4064 pages, LIFO batch:0
    >> Normal zone: 990 pages used for memmap
    >> Normal zone: 125778 pages, LIFO batch:31
    >> HighMem zone: 0 pages used for memmap
    >> DMI 2.3 present.
    >> ACPI: RSDP 000FA850, 0014 (r0 ACPIAM)
    >> ACPI: RSDT 1FF30000, 0030 (r1 A M I OEMRSDT 6000517 MSFT 97)
    >> ACPI: FACP 1FF30200, 0081 (r1 A M I OEMFACP 6000517 MSFT 97)
    >> ACPI: DSDT 1FF303E0, 3755 (r1 A0058 A0058002 2 MSFT 100000D)
    >> ACPI: FACS 1FF40000, 0040
    >> ACPI: APIC 1FF30390, 004A (r1 A M I OEMAPIC 6000517 MSFT 97)
    >> ACPI: OEMB 1FF40040, 003F (r1 A M I OEMBIOS 6000517 MSFT 97)
    >> ACPI: PM-Timer IO Port: 0x808
    >> ACPI: Local APIC address 0xfee00000
    >> ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
    >> Processor #0 15:12 APIC version 16
    >> ACPI: IOAPIC (id[0x01] address[0xfec00000] gsi_base[0])
    >> IOAPIC[0]: apic_id 1, version 3, address 0xfec00000, GSI 0-23
    >> ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
    >> ACPI: IRQ0 used by override.
    >> ACPI: IRQ2 used by override.
    >> ACPI: IRQ9 used by override.
    >> Enabling APIC mode: Flat. Using 1 I/O APICs
    >> Using ACPI (MADT) for SMP configuration information
    >> Allocating PCI resources starting at 30000000 (gap: 20000000:dff80000)
    >> Built 1 zonelists. Total pages: 129842
    >> Kernel command line: root=/dev/hda1 ro
    >> mapped APIC to ffffd000 (fee00000)
    >> mapped IOAPIC to ffffc000 (fec00000)
    >> Enabling fast FPU save and restore... done.
    >> Enabling unmasked SIMD FPU exception support... done.
    >> Initializing CPU#0
    >> PID hash table entries: 2048 (order: 11, 8192 bytes)
    >> Detected 2202.937 MHz processor.
    >> spurious 8259A interrupt: IRQ7.
    >> Console: colour VGA+ 80x25
    >> Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
    >> Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
    >> Memory: 514020k/523456k available (1702k kernel code, 8820k reserved,
    >> 663k data, 244k init, 0k highmem)
    >> virtual kernel memory layout:
    >> fixmap : 0xfff4e000 - 0xfffff000 ( 708 kB)
    >> pkmap : 0xff800000 - 0xffc00000 (4096 kB)
    >> vmalloc : 0xe0800000 - 0xff7fe000 ( 495 MB)
    >> lowmem : 0xc0000000 - 0xdff30000 ( 511 MB)
    >> .init : 0xc0355000 - 0xc0392000 ( 244 kB)
    >> .data : 0xc02a9827 - 0xc034f784 ( 663 kB)
    >> .text : 0xc0100000 - 0xc02a9827 (1702 kB)
    >> Checking if this processor honours the WP bit even in supervisor
    >> mode... Ok. Calibrating delay using timer specific routine.. 4410.78
    >> BogoMIPS (lpj=8821571)
    >> Security Framework v1.0.0 initialized
    >> SELinux: Disabled at boot.
    >> Capability LSM initialized
    >> Mount-cache hash table entries: 512
    >> CPU: After generic identify, caps: 078bfbff e1d3fbff 00000000 00000000
    >> 00000000 00000000 00000000
    >> CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
    >> CPU: L2 Cache: 512K (64 bytes/line)
    >> CPU: After all inits, caps: 078bfbff e1d3fbff 00000000 00000410
    >> 00000000 00000000 00000000
    >> Intel machine check architecture supported.
    >> Intel machine check reporting enabled on CPU#0.
    >> Compat vDSO mapped to ffffe000.
    >> Checking 'hlt' instruction... OK.
    >> SMP alternatives: switching to UP code
    >> Freeing SMP alternatives: 11k freed
    >> ACPI: Core revision 20070126
    >> CPU0: AMD Athlon(tm) 64 Processor 3200+ stepping 00
    >> Total of 1 processors activated (4410.78 BogoMIPS).
    >> ENABLING IO-APIC IRQs
    >> ..TIMER: vector=0x31 apic1=0 pin1=2 apic2=0 pin2=0
    >> Brought up 1 CPUs
    >> Booting paravirtualized kernel on bare hardware
    >> NET: Registered protocol family 16
    >> ACPI: bus type pci registered
    >> PCI: PCI BIOS revision 2.10 entry at 0xf0031, last bus=1
    >> PCI: Using configuration type 1
    >> Setting up standard PCI resources
    >> ACPI: Interpreter enabled
    >> ACPI: (supports S0 S1 S3 S4 S5)
    >> ACPI: Using IOAPIC for interrupt routing
    >> ACPI: PCI Root Bridge [PCI0] (0000:00)
    >> PCI: Probing PCI hardware (bus 00)
    >> PCI: Firmware left 0000:00:09.0 e100 interrupts enabled, disabling
    >> PCI: enabled onboard AC97/MC97 devices
    >> ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
    >> ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 7 10 *11 14 15)
    >> ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 7 *10 11 14 15)
    >> ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 7 10 11 14 15)
    >> ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 7 10 11 14 15) *0,
    >> disabled. ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 7 10 11 14 15)
    >> *0, disabled. ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 7 10 11 14
    >> 15) *0, disabled. ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 7 10 11
    >> 14 15) *0, disabled. ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 7 10
    >> 11 14 15) *0, disabled. Linux Plug and Play Support v0.97 (c) Adam
    >> Belay pnp: PnP ACPI init
    >> ACPI: bus type pnp registered
    >> pnp: PnP ACPI: found 13 devices
    >> ACPI: ACPI bus type pnp unregistered
    >> PnPBIOS: Disabled by ACPI PNP
    >> PCI: Using ACPI for IRQ routing
    >> PCI: If a device doesn't work, try "pci=routeirq". If it helps, post
    >> a report
    >> NET: Registered protocol family 8
    >> NET: Registered protocol family 20
    >> ACPI: RTC can wake from S4
    >> pnp: 00:09: iomem range 0xfec00000-0xfec00fff has been reserved
    >> pnp: 00:09: iomem range 0xfee00000-0xfee00fff has been reserved
    >> pnp: 00:09: iomem range 0xfff80000-0xffffffff could not be reserved
    >> pnp: 00:0c: iomem range 0x0-0x9ffff could not be reserved
    >> pnp: 00:0c: iomem range 0xc0000-0xdffff could not be reserved
    >> pnp: 00:0c: iomem range 0xe0000-0xfffff could not be reserved
    >> pnp: 00:0c: iomem range 0x100000-0x1ffeffff could not be reserved
    >> Time: tsc clocksource has been installed.
    >> PCI: Bridge: 0000:00:01.0
    >> IO window: disabled.
    >> MEM window: f9500000-fd6fffff
    >> PREFETCH window: e1400000-f13fffff
    >> PCI: Setting latency timer of device 0000:00:01.0 to 64
    >> NET: Registered protocol family 2
    >> IP route cache hash table entries: 4096 (order: 2, 16384 bytes)
    >> TCP established hash table entries: 16384 (order: 5, 196608 bytes)
    >> TCP bind hash table entries: 16384 (order: 5, 131072 bytes)
    >> TCP: Hash tables configured (established 16384 bind 16384)
    >> TCP reno registered
    >> checking if image is initramfs... it is
    >> Freeing initrd memory: 1305k freed
    >> audit: initializing netlink socket (disabled)
    >> audit(1218577017.172:1): initialized
    >> VFS: Disk quotas dquot_6.5.1
    >> Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
    >> io scheduler noop registered
    >> io scheduler anticipatory registered
    >> io scheduler deadline registered
    >> io scheduler cfq registered (default)
    >> PCI: VIA PCI bridge detected. Disabling DAC.
    >> Boot video device is 0000:01:00.0
    >> isapnp: Scanning for PnP cards...
    >> Switched to high resolution mode on CPU 0
    >> isapnp: No Plug & Play device found
    >> Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing
    >> enabled 00:0a: ttyS0 at I/O 0x2f8 (irq = 3) is a 16550A
    >> 00:0b: ttyS1 at I/O 0x3f8 (irq = 4) is a 16550A
    >> RAMDISK driver initialized: 16 RAM disks of 8192K size 1024 blocksize
    >> PNP: PS/2 Controller [PNP0303:PS2K,PNP0f03:PS2M] at 0x60,0x64 irq 1,12
    >> serio: i8042 KBD port at 0x60,0x64 irq 1
    >> serio: i8042 AUX port at 0x60,0x64 irq 12
    >> mice: PS/2 mouse device common for all mice
    >> TCP bic registered
    >> NET: Registered protocol family 1
    >> NET: Registered protocol family 17
    >> Using IPI No-Shortcut mode
    >> Freeing unused kernel memory: 244k freed
    >> Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
    >> ide: Assuming 33MHz system bus speed for PIO modes; override with
    >> idebus=xx VP_IDE: IDE controller at PCI slot 0000:00:0f.1
    >> ACPI: PCI Interrupt 0000:00:0f.1[A] -> GSI 20 (level, low) -> IRQ 16
    >> VP_IDE: chipset revision 6
    >> VP_IDE: not 100% native mode: will probe irqs later
    >> VP_IDE: VIA vt8237 (rev 00) IDE UDMA133 controller on pci0000:00:0f.1
    >> ide0: BM-DMA at 0xfc00-0xfc07, BIOS settings: hdaMA, hdbMA
    >> ide1: BM-DMA at 0xfc08-0xfc0f, BIOS settings: hdcMA, hddio
    >> Probing IDE interface ide0...
    >> input: AT Translated Set 2 keyboard as /class/input/input0
    >> hda: ST380011A, ATA DISK drive
    >> hdb: QUANTUM FIREBALL EX6.4A, ATA DISK drive
    >> ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
    >> Probing IDE interface ide1...
    >> hdc: TOSHIBA DVD-ROM SD-M1912, ATAPI CD/DVD-ROM drive
    >> ide1 at 0x170-0x177,0x376 on irq 15
    >> SCSI subsystem initialized
    >> libata version 2.21 loaded.
    >> hda: max request size: 512KiB
    >> hda: 156301488 sectors (80026 MB) w/2048KiB Cache, CHS=16383/255/63,
    >> UDMA(100)
    >> hda: cache flushes supported
    >> hda: hda1 hda2 < hda5 hda6 hda7 hda8 hda9 hda10 hda11 hda12 >
    >> hdb: max request size: 128KiB
    >> hdb: 12594960 sectors (6448 MB) w/418KiB Cache, CHS=13328/15/63,
    >> UDMA(33) hdb: cache flushes not supported
    >> hdb: hdb1
    >> kjournald starting. Commit interval 5 seconds
    >> EXT3-fs: mounted filesystem with ordered data mode.
    >> input: PC Speaker as /class/input/input1
    >> pci_hotplug: PCI Hot Plug PCI Core version: 0.5
    >> shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
    >> Real Time Clock Driver v1.12ac
    >> Floppy drive(s): fd0 is 1.44M
    >> FDC 0 is a post-1991 82077
    >> usbcore: registered new interface driver usbfs
    >> usbcore: registered new interface driver hub
    >> usbcore: registered new device driver usb
    >> Linux agpgart interface v0.102 (c) Dave Jones
    >> hdc: ATAPI 48X DVD-ROM drive, 512kB Cache, UDMA(33)
    >> Uniform CD-ROM driver Revision: 3.20
    >> USB Universal Host Controller Interface driver v3.0
    >> ACPI: PCI Interrupt 0000:00:10.0[A] -> GSI 21 (level, low) -> IRQ 17
    >> uhci_hcd 0000:00:10.0: UHCI Host Controller
    >> uhci_hcd 0000:00:10.0: new USB bus registered, assigned bus number 1
    >> uhci_hcd 0000:00:10.0: irq 17, io base 0x0000dc00
    >> usb usb1: configuration #1 chosen from 1 choice
    >> hub 1-0:1.0: USB hub found
    >> hub 1-0:1.0: 2 ports detected
    >> e100: Intel(R) PRO/100 Network Driver, 3.5.17-k4-NAPI
    >> e100: Copyright(c) 1999-2006 Intel Corporation
    >> ACPI: PCI Interrupt 0000:00:10.1[A] -> GSI 21 (level, low) -> IRQ 17
    >> uhci_hcd 0000:00:10.1: UHCI Host Controller
    >> uhci_hcd 0000:00:10.1: new USB bus registered, assigned bus number 2
    >> uhci_hcd 0000:00:10.1: irq 17, io base 0x0000ec00
    >> usb usb2: configuration #1 chosen from 1 choice
    >> hub 2-0:1.0: USB hub found
    >> hub 2-0:1.0: 2 ports detected
    >> ACPI: PCI Interrupt 0000:00:10.2[B] -> GSI 21 (level, low) -> IRQ 17
    >> uhci_hcd 0000:00:10.2: UHCI Host Controller
    >> uhci_hcd 0000:00:10.2: new USB bus registered, assigned bus number 3
    >> uhci_hcd 0000:00:10.2: irq 17, io base 0x0000c000
    >> usb usb3: configuration #1 chosen from 1 choice
    >> hub 3-0:1.0: USB hub found
    >> hub 3-0:1.0: 2 ports detected
    >> ACPI: PCI Interrupt 0000:00:10.3[B] -> GSI 21 (level, low) -> IRQ 17
    >> uhci_hcd 0000:00:10.3: UHCI Host Controller
    >> uhci_hcd 0000:00:10.3: new USB bus registered, assigned bus number 4
    >> uhci_hcd 0000:00:10.3: irq 17, io base 0x0000c400
    >> usb usb4: configuration #1 chosen from 1 choice
    >> hub 4-0:1.0: USB hub found
    >> hub 4-0:1.0: 2 ports detected
    >> ACPI: PCI Interrupt 0000:00:10.4[C] -> GSI 21 (level, low) -> IRQ 17
    >> ehci_hcd 0000:00:10.4: EHCI Host Controller
    >> ehci_hcd 0000:00:10.4: new USB bus registered, assigned bus number 5
    >> ehci_hcd 0000:00:10.4: irq 17, io mem 0xfd700000
    >> ehci_hcd 0000:00:10.4: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
    >> usb usb5: configuration #1 chosen from 1 choice
    >> hub 5-0:1.0: USB hub found
    >> hub 5-0:1.0: 8 ports detected
    >> input: ImPS/2 Generic Wheel Mouse as /class/input/input2
    >> agpgart: Detected AGP bridge 0
    >> agpgart: AGP aperture is 64M @ 0xf4000000
    >> sata_via 0000:00:0f.0: version 2.2
    >> ACPI: PCI Interrupt 0000:00:0f.0[B] -> GSI 20 (level, low) -> IRQ 16
    >> sata_via 0000:00:0f.0: routed to hard irq line 10
    >> scsi0 : sata_via
    >> scsi1 : sata_via
    >> ata1: SATA max UDMA/133 cmd 0x0001e800 ctl 0x0001e402 bmdma 0x0001d400
    >> irq 16
    >> ata2: SATA max UDMA/133 cmd 0x0001e000 ctl 0x0001d802 bmdma 0x0001d408
    >> irq 16
    >> ata1: SATA link down 1.5 Gbps (SStatus 0 SControl 300)
    >> ata2: SATA link down 1.5 Gbps (SStatus 0 SControl 300)
    >> ACPI: PCI Interrupt 0000:00:09.0[A] -> GSI 16 (level, low) -> IRQ 18
    >> e100: eth0: e100_probe: addr 0xfdc00000, irq 18, MAC addr
    >> 000:B7:85:0A:3F PCI: Enabling device 0000:00:11.6 (0000 -> 0001)
    >> ACPI: PCI Interrupt 0000:00:11.6[C] -> GSI 22 (level, low) -> IRQ 19
    >> usb 2-2: new low speed USB device using uhci_hcd and address 2
    >> PCI: Setting latency timer of device 0000:00:11.6 to 64
    >> usb 2-2: configuration #1 chosen from 1 choice
    >> usbcore: registered new interface driver hiddev
    >> ACPI: PCI interrupt for device 0000:00:11.6 disabled
    >> VIA 82xx Modem: probe of 0000:00:11.6 failed with error -13
    >> ACPI: PCI Interrupt 0000:00:11.5[C] -> GSI 22 (level, low) -> IRQ 19
    >> PCI: Setting latency timer of device 0000:00:11.5 to 64
    >> codec_read: codec 0 is not valid [0xfe0000]
    >> codec_read: codec 0 is not valid [0xfe0000]
    >> codec_read: codec 0 is not valid [0xfe0000]
    >> codec_read: codec 0 is not valid [0xfe0000]
    >> hiddev96: USB HID v1.10 Device [American Power Conversion Back-UPS RS
    >> 1500 FW:8.g8 .D USB FW:g8 ] on usb-0000:00:10.1-2
    >> usbcore: registered new interface driver usbhid
    >> drivers/hid/usbhid/hid-core.c: v2.6:USB HID core driver
    >> Adding 2361512k swap on /dev/hda10. Priority:-1 extents:1
    >> across:2361512k EXT3 FS on hda1, internal journal
    >> loop: module loaded
    >> w83627hf: Found W83697HF chip at 0x290
    >> fuse init (API version 7.8)
    >> device-mapper: ioctl: 4.11.0-ioctl (2006-10-12) initialised:
    >> dm-devel@redhat.com
    >> kjournald starting. Commit interval 5 seconds
    >> EXT3 FS on hda5, internal journal
    >> EXT3-fs: mounted filesystem with ordered data mode.
    >> kjournald starting. Commit interval 5 seconds
    >> EXT3 FS on hda6, internal journal
    >> EXT3-fs: mounted filesystem with ordered data mode.
    >> kjournald starting. Commit interval 5 seconds
    >> EXT3 FS on hda7, internal journal
    >> EXT3-fs: mounted filesystem with ordered data mode.
    >> kjournald starting. Commit interval 5 seconds
    >> EXT3 FS on hda8, internal journal
    >> EXT3-fs: mounted filesystem with ordered data mode.
    >> kjournald starting. Commit interval 5 seconds
    >> EXT3 FS on hda9, internal journal
    >> EXT3-fs: mounted filesystem with ordered data mode.
    >> kjournald starting. Commit interval 5 seconds
    >> EXT3 FS on hda11, internal journal
    >> EXT3-fs: mounted filesystem with ordered data mode.
    >> kjournald starting. Commit interval 5 seconds
    >> EXT3 FS on hda12, internal journal
    >> EXT3-fs: mounted filesystem with ordered data mode.
    >> ext3: No journal on filesystem on hdb1
    >> ip_tables: (C) 2000-2006 Netfilter Core Team
    >> Netfilter messages via NETLINK v0.30.
    >> nf_conntrack version 0.5.0 (4089 buckets, 32712 max)
    >> e100: eth0: e100_watchdog: link up, 100Mbps, full-duplex
    >> NET: Registered protocol family 10
    >> lo: Disabled Privacy Extensions
    >> input: Power Button (FF) as /class/input/input3
    >> ACPI: Power Button (FF) [PWRF]
    >> input: Power Button (CM) as /class/input/input4
    >> ACPI: Power Button (CM) [PWRB]
    >> input: Sleep Button (CM) as /class/input/input5
    >> ACPI: Sleep Button (CM) [SLPB]
    >> eth0: no IPv6 routers present
    >> vboxdrv: Trying to deactivate the NMI watchdog permanently...
    >> vboxdrv: Successfully done.
    >> vboxdrv: Found 1 processor cores.
    >> vboxdrv: fAsync=0 u64DiffCores=1.
    >> vboxdrv: TSC mode is 'synchronous', kernel timer mode is 'normal'.
    >> vboxdrv: Successfully loaded version 1.6.4 (interface 0x00080000).
    >> vmmon: module license 'unspecified' taints kernel.
    >> [2923]: VMCI: Driver initialized.
    >> [2923]: Module vmmon: registered with major=10 minor=165
    >> [2923]: Module vmmon: initialized
    >> /dev/vmnet: open called by PID 2952 (vmnet-bridge)
    >> /dev/vmnet: hub 0 does not exist, allocating memory.
    >> /dev/vmnet: port on hub 0 successfully opened
    >> bridge-eth0: enabling the bridge
    >> bridge-eth0: up
    >> bridge-eth0: already up
    >> bridge-eth0: attached
    >> /dev/vmnet: open called by PID 2966 (vmnet-natd)
    >> /dev/vmnet: hub 8 does not exist, allocating memory.
    >> /dev/vmnet: port on hub 8 successfully opened
    >> powernow-k8: Found 1 AMD Athlon(tm) 64 Processor 3200+ processors
    >> (version 2.00.00)
    >> powernow-k8: 0 : fid 0xe (2200 MHz), vid 0x2
    >> powernow-k8: 1 : fid 0xc (2000 MHz), vid 0x6
    >> powernow-k8: 2 : fid 0xa (1800 MHz), vid 0xa
    >> powernow-k8: 3 : fid 0x2 (1000 MHz), vid 0x12
    >> Marking TSC unstable due to: cpufreq changes.
    >> Time: acpi_pm clocksource has been installed.
    >> Clocksource tsc unstable (delta = -176950529 ns)
    >> /dev/vmnet: open called by PID 3029 (vmnet-netifup)
    >> /dev/vmnet: hub 1 does not exist, allocating memory.
    >> /dev/vmnet: port on hub 1 successfully opened
    >> /dev/vmnet: open called by PID 3030 (vmnet-netifup)
    >> /dev/vmnet: port on hub 8 successfully opened
    >> /dev/vmnet: open called by PID 3066 (vmnet-dhcpd)
    >> /dev/vmnet: port on hub 1 successfully opened
    >> /dev/vmnet: open called by PID 3047 (vmnet-dhcpd)
    >> /dev/vmnet: port on hub 8 successfully opened
    >> vmnet8: no IPv6 routers present
    >> vmnet1: no IPv6 routers present
    >> ext3: No journal on filesystem on hdb1
    >> kjournald starting. Commit interval 5 seconds
    >> EXT3 FS on hdb1, internal journal
    >> EXT3-fs: mounted filesystem with ordered data mode.
    >> hda: status error: status=0xd0 { Busy }
    >> ide: failed opcode was: unknown
    >> hda: DMA disabled
    >> hdb: DMA disabled
    >> hda: drive not ready for command
    >> ide0: reset timed-out, status=0xd0
    >> hda: lost interrupt
    >> attempt to access beyond end of device
    >> hda5: rw=0, want=8877388712, limit=29302497
    >> attempt to access beyond end of device
    >> hda5: rw=0, want=8877388712, limit=29302497
    >> attempt to access beyond end of device
    >> hda5: rw=0, want=8877388584, limit=29302497
    >> attempt to access beyond end of device
    >> hda5: rw=0, want=8885842944, limit=29302497
    >> attempt to access beyond end of device
    >> hda5: rw=0, want=8877388712, limit=29302497
    >> hda: task_out_intr: status=0xd8 { Busy }
    >> ide: failed opcode was: unknown
    >> ide0: reset timed-out, status=0xd0
    >> end_request: I/O error, dev hda, sector 2806748
    >> Buffer I/O error on device hda5, logical block 278543
    >> lost page write due to I/O error on hda5
    >> end_request: I/O error, dev hda, sector 2806811
    >> Buffer I/O error on device hda5, logical block 278551
    >> lost page write due to I/O error on hda5
    >> end_request: I/O error, dev hda, sector 2806835
    >> Buffer I/O error on device hda5, logical block 278554
    >> lost page write due to I/O error on hda5
    >> end_request: I/O error, dev hda, sector 2806843
    >> Buffer I/O error on device hda5, logical block 278555
    >> lost page write due to I/O error on hda5
    >> end_request: I/O error, dev hda, sector 2806851
    >> Buffer I/O error on device hda5, logical block 278556
    >> lost page write due to I/O error on hda5
    >> end_request: I/O error, dev hda, sector 2806859
    >> Buffer I/O error on device hda5, logical block 278557
    >> lost page write due to I/O error on hda5
    >> end_request: I/O error, dev hda, sector 2806867
    >> Buffer I/O error on device hda5, logical block 278558
    >> lost page write due to I/O error on hda5
    >> end_request: I/O error, dev hda, sector 2806875
    >> Buffer I/O error on device hda5, logical block 278559
    >> lost page write due to I/O error on hda5
    >> end_request: I/O error, dev hda, sector 2806883
    >> Buffer I/O error on device hda5, logical block 278560
    >> lost page write due to I/O error on hda5
    >> end_request: I/O error, dev hda, sector 2806891
    >> Buffer I/O error on device hda5, logical block 278561
    >> lost page write due to I/O error on hda5
    >> end_request: I/O error, dev hda, sector 2806899
    >> end_request: I/O error, dev hda, sector 2806907
    >> end_request: I/O error, dev hda, sector 2806915
    >> end_request: I/O error, dev hda, sector 2806923
    >> end_request: I/O error, dev hda, sector 2806931
    >> end_request: I/O error, dev hda, sector 2806939
    >> end_request: I/O error, dev hda, sector 2806947
    >> end_request: I/O error, dev hda, sector 2806955
    >> end_request: I/O error, dev hda, sector 2807011
    >> end_request: I/O error, dev hda, sector 2807019
    >> end_request: I/O error, dev hda, sector 2807027
    >> end_request: I/O error, dev hda, sector 2807035
    >> end_request: I/O error, dev hda, sector 2807043
    >> end_request: I/O error, dev hda, sector 2807051
    >> end_request: I/O error, dev hda, sector 2807059
    >> end_request: I/O error, dev hda, sector 2807067
    >> end_request: I/O error, dev hda, sector 2807075
    >> end_request: I/O error, dev hda, sector 2807083
    >> end_request: I/O error, dev hda, sector 2807091
    >> end_request: I/O error, dev hda, sector 2807099
    >> end_request: I/O error, dev hda, sector 2807107
    >> end_request: I/O error, dev hda, sector 2807115
    >> end_request: I/O error, dev hda, sector 2807123
    >> end_request: I/O error, dev hda, sector 2807131
    >> end_request: I/O error, dev hda, sector 2807139
    >> end_request: I/O error, dev hda, sector 2807147
    >> end_request: I/O error, dev hda, sector 2807155
    >> end_request: I/O error, dev hda, sector 2807163
    >> end_request: I/O error, dev hda, sector 2807171
    >> end_request: I/O error, dev hda, sector 2807179
    >> end_request: I/O error, dev hda, sector 2807187
    >> end_request: I/O error, dev hda, sector 2807195
    >> end_request: I/O error, dev hda, sector 2807203
    >> end_request: I/O error, dev hda, sector 2807211
    >> end_request: I/O error, dev hda, sector 2807219
    >> end_request: I/O error, dev hda, sector 2807227
    >> end_request: I/O error, dev hda, sector 2807235
    >> end_request: I/O error, dev hda, sector 2807243
    >> end_request: I/O error, dev hda, sector 2807251
    >> end_request: I/O error, dev hda, sector 2807259
    >> end_request: I/O error, dev hda, sector 2807267
    >> end_request: I/O error, dev hda, sector 2807275
    >> end_request: I/O error, dev hda, sector 2807283
    >> end_request: I/O error, dev hda, sector 2807291
    >> end_request: I/O error, dev hda, sector 2807299
    >> end_request: I/O error, dev hda, sector 2807307
    >> end_request: I/O error, dev hda, sector 2807315
    >> end_request: I/O error, dev hda, sector 2807323
    >> end_request: I/O error, dev hda, sector 2807331
    >> end_request: I/O error, dev hda, sector 2807339
    >> end_request: I/O error, dev hda, sector 2807795
    >> end_request: I/O error, dev hda, sector 2825411
    >> end_request: I/O error, dev hda, sector 2885699
    >> end_request: I/O error, dev hda, sector 11893315
    >> end_request: I/O error, dev hda, sector 19903083
    >> end_request: I/O error, dev hda, sector 30929763
    >> end_request: I/O error, dev hda, sector 31717203
    >> end_request: I/O error, dev hda, sector 34075299
    >> end_request: I/O error, dev hda, sector 34075443
    >> end_request: I/O error, dev hda, sector 35911243
    >> end_request: I/O error, dev hda, sector 35911851
    >> end_request: I/O error, dev hda, sector 37483315
    >> end_request: I/O error, dev hda, sector 39648483
    >> end_request: I/O error, dev hda, sector 39648491
    >> end_request: I/O error, dev hda, sector 40871067
    >> end_request: I/O error, dev hda, sector 40873747
    >> end_request: I/O error, dev hda, sector 40873867
    >> end_request: I/O error, dev hda, sector 115275
    >> end_request: I/O error, dev hda, sector 115279
    >> end_request: I/O error, dev hda, sector 115281
    >> end_request: I/O error, dev hda, sector 115283
    >> end_request: I/O error, dev hda, sector 278745
    >> end_request: I/O error, dev hda, sector 578403
    >> end_request: I/O error, dev hda, sector 578411
    >> end_request: I/O error, dev hda, sector 1102723
    >> end_request: I/O error, dev hda, sector 1102747
    >> end_request: I/O error, dev hda, sector 2675555
    >> end_request: I/O error, dev hda, sector 2675563
    >> end_request: I/O error, dev hda, sector 2675619
    >> end_request: I/O error, dev hda, sector 2741115
    >> end_request: I/O error, dev hda, sector 2741163
    >> end_request: I/O error, dev hda, sector 2741171
    >> end_request: I/O error, dev hda, sector 2741347
    >> end_request: I/O error, dev hda, sector 2741459
    >> end_request: I/O error, dev hda, sector 2741467
    >> end_request: I/O error, dev hda, sector 2741475
    >> end_request: I/O error, dev hda, sector 2741483
    >> end_request: I/O error, dev hda, sector 2741491
    >> end_request: I/O error, dev hda, sector 2741523
    >> end_request: I/O error, dev hda, sector 2741603
    >> end_request: I/O error, dev hda, sector 2741611
    >> end_request: I/O error, dev hda, sector 2741771
    >> end_request: I/O error, dev hda, sector 2741779
    >> end_request: I/O error, dev hda, sector 2741915
    >> end_request: I/O error, dev hda, sector 2741923
    >> end_request: I/O error, dev hda, sector 2742067
    >> end_request: I/O error, dev hda, sector 39976827
    >> end_request: I/O error, dev hda, sector 39976875
    >> end_request: I/O error, dev hda, sector 115287
    >> end_request: I/O error, dev hda, sector 115297
    >> end_request: I/O error, dev hda, sector 115299
    >> end_request: I/O error, dev hda, sector 115303
    >> end_request: I/O error, dev hda, sector 115305
    >> end_request: I/O error, dev hda, sector 115307
    >> end_request: I/O error, dev hda, sector 115309
    >> end_request: I/O error, dev hda, sector 115311
    >> end_request: I/O error, dev hda, sector 115317
    >> end_request: I/O error, dev hda, sector 115319
    >> end_request: I/O error, dev hda, sector 115321
    >> end_request: I/O error, dev hda, sector 115323
    >> end_request: I/O error, dev hda, sector 115325
    >> end_request: I/O error, dev hda, sector 115327
    >> end_request: I/O error, dev hda, sector 115349
    >> end_request: I/O error, dev hda, sector 131191
    >> end_request: I/O error, dev hda, sector 262213
    >> end_request: I/O error, dev hda, sector 262215
    >> end_request: I/O error, dev hda, sector 262221
    >> end_request: I/O error, dev hda, sector 262223
    >> end_request: I/O error, dev hda, sector 262449
    >> end_request: I/O error, dev hda, sector 262565
    >> end_request: I/O error, dev hda, sector 262585
    >> end_request: I/O error, dev hda, sector 262609
    >> end_request: I/O error, dev hda, sector 262679
    >> Aborting journal on device hda7.
    >> end_request: I/O error, dev hda, sector 39976875
    >> end_request: I/O error, dev hda, sector 40871067
    >> end_request: I/O error, dev hda, sector 40873747
    >> end_request: I/O error, dev hda, sector 40873867
    >> __journal_remove_journal_head: freeing b_frozen_data
    >> __journal_remove_journal_head: freeing b_frozen_data
    >> __journal_remove_journal_head: freeing b_frozen_data
    >> Aborting journal on device hda5.
    >> end_request: I/O error, dev hda, sector 2741115
    >> end_request: I/O error, dev hda, sector 2741467
    >> end_request: I/O error, dev hda, sector 2741915
    >> end_request: I/O error, dev hda, sector 2806707
    >> end_request: I/O error, dev hda, sector 2806843
    >> end_request: I/O error, dev hda, sector 2806851
    >> end_request: I/O error, dev hda, sector 2806859
    >> end_request: I/O error, dev hda, sector 2806867
    >> end_request: I/O error, dev hda, sector 2806947
    >> end_request: I/O error, dev hda, sector 2807035
    >> end_request: I/O error, dev hda, sector 2807043
    >> end_request: I/O error, dev hda, sector 2807059
    >> end_request: I/O error, dev hda, sector 2807067
    >> end_request: I/O error, dev hda, sector 2807131
    >> end_request: I/O error, dev hda, sector 2807147
    >> end_request: I/O error, dev hda, sector 2741171
    >> end_request: I/O error, dev hda, sector 2741347
    >> end_request: I/O error, dev hda, sector 2741611
    >> ext3_abort called.
    >> EXT3-fs error (device hda7): ext3_journal_start_sb: Detected aborted
    >> journal Remounting filesystem read-only
    >> ext3_abort called.
    >> EXT3-fs error (device hda5): ext3_journal_start_sb: Detected aborted
    >> journal Remounting filesystem read-only
    >> end_request: I/O error, dev hda, sector 1102763
    >> EXT3-fs error (device hda5): ext3_get_inode_loc: unable to read inode
    >> block - inode=32883, block=65545
    >> end_request: I/O error, dev hda, sector 30929763
    >> EXT3-fs error (device hda6): ext3_get_inode_loc: unable to read inode
    >> block - inode=65052, block=131100
    >> end_request: I/O error, dev hda, sector 29880963
    >> printk: 145 messages suppressed.
    >> Buffer I/O error on device hda6, logical block 0
    >> lost page write due to I/O error on hda6
    >> EXT3-fs error (device hda6) in ext3_reserve_inode_write: IO failure
    >> end_request: I/O error, dev hda, sector 29880963
    >> Buffer I/O error on device hda6, logical block 0
    >> lost page write due to I/O error on hda6
    >> end_request: I/O error, dev hda, sector 5379
    >> end_request: I/O error, dev hda, sector 5381
    >> end_request: I/O error, dev hda, sector 5383
    >> Aborting journal on device hda1.
    >> end_request: I/O error, dev hda, sector 2151299
    >> EXT3-fs error (device hda5): ext3_get_inode_loc: unable to read inode
    >> block - inode=98115, block=196612
    >> ext3_abort called.
    >> EXT3-fs error (device hda1): ext3_journal_start_sb: Detected aborted
    >> journal Remounting filesystem read-only
    >> end_request: I/O error, dev hda, sector 37483315
    >> EXT3-fs error (device hda6): ext3_get_inode_loc: unable to read inode
    >> block - inode=466454, block=950294
    >> end_request: I/O error, dev hda, sector 29880963
    >> printk: 1 messages suppressed.
    >> Buffer I/O error on device hda6, logical block 0
    >> lost page write due to I/O error on hda6
    >> EXT3-fs error (device hda6) in ext3_reserve_inode_write: IO failure
    >> end_request: I/O error, dev hda, sector 29880963
    >> end_request: I/O error, dev hda, sector 1889155
    >> EXT3-fs error (device hda5): ext3_get_inode_loc: unable to read inode
    >> block - inode=81764, block=163844
    >> end_request: I/O error, dev hda, sector 30929763
    >> EXT3-fs error (device hda6): ext3_get_inode_loc: unable to read inode
    >> block - inode=65052, block=131100
    >> end_request: I/O error, dev hda, sector 29880963
    >> EXT3-fs error (device hda6) in ext3_reserve_inode_write: IO failure
    >> end_request: I/O error, dev hda, sector 29880963
    >> end_request: I/O error, dev hda, sector 1102723
    >> EXT3-fs error (device hda5): ext3_get_inode_loc: unable to read inode
    >> block - inode=32712, block=65540
    >> end_request: I/O error, dev hda, sector 6083459
    >> EXT3-fs error (device hda5): ext3_get_inode_loc: unable to read inode
    >> block - inode=343393, block=688132
    >> end_request: I/O error, dev hda, sector 1102811
    >> EXT3-fs error (device hda5): ext3_get_inode_loc: unable to read inode
    >> block - inode=33086, block=65551
    >> end_request: I/O error, dev hda, sector 1102811
    >> EXT3-fs error (device hda5): ext3_get_inode_loc: unable to read inode
    >> block - inode=33087, block=65551
    >> end_request: I/O error, dev hda, sector 1102819
    >> EXT3-fs error (device hda5): ext3_get_inode_loc: unable to read inode
    >> block - inode=33112, block=65552
    >> end_request: I/O error, dev hda, sector 7394579
    >> EXT3-fs error (device hda5): ext3_get_inode_loc: unable to read inode
    >> block - inode=426780, block=852022
    >> end_request: I/O error, dev hda, sector 1103747
    >> EXT3-fs error (device hda5): ext3_get_inode_loc: unable to read inode
    >> block - inode=36808, block=65668
    >> end_request: I/O error, dev hda, sector 6083523
    >> EXT3-fs error (device hda5): ext3_get_inode_loc: unable to read inode
    >> block - inode=343650, block=688140
    >> end_request: I/O error, dev hda, sector 1102763
    >> EXT3-fs error (device hda5): ext3_get_inode_loc: unable to read inode
    >> block - inode=32894, block=65545
    >> end_request: I/O error, dev hda, sector 1102723
    >> EXT3-fs error (device hda5): ext3_get_inode_loc: unable to read inode
    >> block - inode=32713, block=65540
    >> end_request: I/O error, dev hda, sector 1102827
    >> EXT3-fs error (device hda5): ext3_get_inode_loc: unable to read inode
    >> block - inode=33125, block=65553
    >> end_request: I/O error, dev hda, sector 3199875
    >> EXT3-fs error (device hda5): ext3_get_inode_loc: unable to read inode
    >> block - inode=163524, block=327684
    >> end_request: I/O error, dev hda, sector 3462723
    >> EXT3-fs error (device hda5): ext3_get_inode_loc: unable to read inode
    >> block - inode=182707, block=360540
    >> end_request: I/O error, dev hda, sector 29890819
    >> Aborting journal on device hda6.
    >> ext3_abort called.
    >> EXT3-fs error (device hda6): ext3_journal_start_sb: Detected aborted
    >> journal Remounting filesystem read-only
    >> end_request: I/O error, dev hda, sector 40697075
    >> printk: 4 messages suppressed.
    >> Buffer I/O error on device hda7, logical block 131074
    >> lost page write due to I/O error on hda7
    >> end_request: I/O error, dev hda, sector 40697083
    >> Buffer I/O error on device hda7, logical block 131075
    >> lost page write due to I/O error on hda7
    >> end_request: I/O error, dev hda, sector 40697091
    >> Buffer I/O error on device hda7, logical block 131076
    >> lost page write due to I/O error on hda7
    >> end_request: I/O error, dev hda, sector 2675587
    >> end_request: I/O error, dev hda, sector 2675595
    >> end_request: I/O error, dev hda, sector 2675643
    >> end_request: I/O error, dev hda, sector 2675651
    >> end_request: I/O error, dev hda, sector 262603
    >> printk: 4 messages suppressed.
    >> Buffer I/O error on device hda1, logical block 131270
    >> lost page write due to I/O error on hda1
    >>
    >> I had to power off and on my PC (couldn't do a normal shutdown and the
    >> reset button didn't work).
    >>
    >>
    >> Things were calm for maybe 10 minutes, then again:
    >> hdb: dma_timer_expiry: dma status == 0x61
    >> hdb: DMA timeout error
    >> hdb: dma timeout error: status=0x58 { DriveReady SeekComplete
    >> DataRequest } ide: failed opcode was: unknown
    >> hda: DMA disabled
    >> hdb: DMA disabled
    >> ide0: reset: success
    >>
    >> I ran smartctl -a on both drives:
    >> # smartctl -a /dev/hda
    >> smartctl version 5.38 [i686-pc-linux-gnu] Copyright (C) 2002-8 Bruce
    >> Allen Home page is http://smartmontools.sourceforge.net/
    >>
    >> === START OF INFORMATION SECTION ===
    >> Model Family: Seagate Barracuda 7200.7 and 7200.7 Plus family
    >> Device Model: ST380011A
    >> Serial Number: 4JV5P7LN
    >> Firmware Version: 8.01
    >> User Capacity: 80,026,361,856 bytes
    >> Device is: In smartctl database [for details use: -P show]
    >> ATA Version is: 6
    >> ATA Standard is: ATA/ATAPI-6 T13 1410D revision 2
    >> Local Time is: Tue Aug 12 22:15:59 2008 PDT
    >> SMART support is: Available - device has SMART capability.
    >> SMART support is: Enabled
    >>
    >> === START OF READ SMART DATA SECTION ===
    >> SMART overall-health self-assessment test result: PASSED
    >>
    >> General SMART Values:
    >> Offline data collection status: (0x82) Offline data collection
    >> activity was completed
    >> without error. Auto Offline
    >> Data Collection: Enabled.
    >> Self-test execution status: ( 0) The previous self-test routine
    >> completed
    >> without error or no self-test
    >> has ever
    >> been run.
    >> Total time to complete Offline
    >> data collection: ( 430) seconds.
    >> Offline data collection
    >> capabilities: (0x5b) SMART execute Offline
    >> immediate. Auto Offline data
    >> collection on/off support.
    >> Suspend Offline collection
    >> upon new command.
    >> Offline surface scan
    >> supported. Self-test
    >> supported. No Conveyance
    >> Self-test supported.
    >> Selective Self-test supported. SMART capabilities: (0x0003) Saves SMART data before
    >> entering power-saving mode.
    >> Supports SMART auto save
    >> timer. Error logging capability: (0x01) Error logging
    >> supported. General Purpose
    >> Logging supported. Short self-test routine
    >> recommended polling time: ( 1) minutes.
    >> Extended self-test routine
    >> recommended polling time: ( 58) minutes.
    >>
    >> SMART Attributes Data Structure revision number: 10
    >> Vendor Specific SMART Attributes with Thresholds:
    >> ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE
    >> UPDATED WHEN_FAILED RAW_VALUE
    >> 1 Raw_Read_Error_Rate 0x000f 060 057 006 Pre-fail
    >> Always - 81109586
    >> 3 Spin_Up_Time 0x0003 098 098 000 Pre-fail
    >> Always - 0
    >> 4 Start_Stop_Count 0x0032 100 100 020 Old_age
    >> Always - 0
    >> 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail
    >> Always - 0
    >> 7 Seek_Error_Rate 0x000f 082 060 030 Pre-fail
    >> Always - 195706519
    >> 9 Power_On_Hours 0x0032 075 075 000 Old_age
    >> Always - 22212
    >> 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail
    >> Always - 0
    >> 12 Power_Cycle_Count 0x0032 100 100 020 Old_age
    >> Always - 120
    >> 194 Temperature_Celsius 0x0022 032 048 000 Old_age Always - 32
    >> 195 Hardware_ECC_Recovered 0x001a 060 057 000 Old_age Always - 81109586
    >> 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0
    >> 198 Offline_Uncorrectable 0x0010 100 100 000 Old_age
    >> Offline - 0
    >> 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0
    >> 200 Multi_Zone_Error_Rate 0x0000 100 253 000 Old_age
    >> Offline - 0
    >> 202 TA_Increase_Count 0x0032 100 253 000 Old_age Always - 0
    >>
    >> SMART Error Log Version: 1
    >> No Errors Logged
    >>
    >> SMART Self-test log structure revision number 1
    >> Num Test_Description Status Remaining
    >> LifeTime(hours) LBA_of_first_error
    >> # 1 Extended offline Completed without error 00% 18951
    >> -
    >> # 2 Extended offline Completed without error 00% 18674
    >> -
    >> # 3 Extended offline Completed without error 00% 15957
    >> -
    >> # 4 Extended offline Completed without error 00% 14448
    >> -
    >>
    >> SMART Selective self-test log data structure revision number 1
    >> SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
    >> 1 0 0 Not_testing
    >> 2 0 0 Not_testing
    >> 3 0 0 Not_testing
    >> 4 0 0 Not_testing
    >> 5 0 0 Not_testing
    >> Selective self-test flags (0x0):
    >> After scanning selected spans, do NOT read-scan remainder of disk.
    >> If Selective self-test is pending on power-up, resume after 0 minute
    >> delay.
    >> # smartctl -a /dev/hdb
    >> smartctl version 5.38 [i686-pc-linux-gnu] Copyright (C) 2002-8 Bruce
    >> Allen Home page is http://smartmontools.sourceforge.net/
    >>
    >> === START OF INFORMATION SECTION ===
    >> Device Model: QUANTUM FIREBALL EX6.4A
    >> Serial Number: 376833611720
    >> Firmware Version: A0A.0D00
    >> User Capacity: 6,448,619,520 bytes
    >> Device is: In smartctl database [for details use: -P show]
    >> ATA Version is: 4
    >> ATA Standard is: ATA/ATAPI-4 T13 1153D revision 15
    >> Local Time is: Tue Aug 12 22:16:25 2008 PDT
    >> SMART support is: Available - device has SMART capability.
    >> SMART support is: Enabled
    >>
    >> Error SMART Status command failed: Input/output error
    >> A mandatory SMART command failed: exiting. To continue, add one or
    >> more '-T permissive' options.
    >>
    >> Then, my Linux pauses becuse hdb went funky. I rechecked my dmesg
    >> (might old dupes from earlier):
    >> hdb: dma_timer_expiry: dma status == 0x61
    >> hdb: DMA timeout error
    >> hdb: dma timeout error: status=0x58 { DriveReady SeekComplete
    >> DataRequest } ide: failed opcode was: unknown
    >> hda: DMA disabled
    >> hdb: DMA disabled
    >> ide0: reset: success
    >> hdb: drive_cmd: status=0x7d { DriveReady DeviceFault SeekComplete
    >> DataRequest CorrectedError Error }
    >> hdb: drive_cmd: error=0x7d { DriveStatusError UncorrectableError
    >> SectorIdNotFound AddrMarkNotFound }, LBAsect=226327933, sector=0
    >> ide: failed opcode was: 0xb0
    >> hdb: dma_timer_expiry: dma status == 0x61
    >> hdb: DMA timeout error
    >> hdb: dma timeout error: status=0x58 { DriveReady SeekComplete
    >> DataRequest } ide: failed opcode was: unknown
    >> hda: DMA disabled
    >> hdb: DMA disabled
    >> ide0: reset: success
    >> hdb: dma_timer_expiry: dma status == 0x61
    >> hdb: DMA timeout error
    >> hdb: dma timeout error: status=0x58 { DriveReady SeekComplete
    >> DataRequest } ide: failed opcode was: unknown
    >> hda: DMA disabled
    >> hdb: DMA disabled
    >> ide0: reset: success
    >> hdb: dma_timer_expiry: dma status == 0x41
    >> hdb: DMA timeout error
    >> hdb: dma timeout error: status=0x58 { DriveReady SeekComplete
    >> DataRequest } ide: failed opcode was: unknown
    >> hdb: DMA disabled
    >> ide0: reset: success
    >>
    >>
    >> # smartctl -a /dev/hdb
    >> smartctl version 5.38 [i686-pc-linux-gnu] Copyright (C) 2002-8 Bruce
    >> Allen Home page is http://smartmontools.sourceforge.net/
    >>
    >> === START OF INFORMATION SECTION ===
    >> Device Model: QUANTUM FIREBALL EX6.4A
    >> Serial Number: 376833611720
    >> Firmware Version: A0A.0D00
    >> User Capacity: 6,448,619,520 bytes
    >> Device is: In smartctl database [for details use: -P show]
    >> ATA Version is: 4
    >> ATA Standard is: ATA/ATAPI-4 T13 1153D revision 15
    >> Local Time is: Tue Aug 12 22:19:21 2008 PDT
    >> SMART support is: Available - device has SMART capability.
    >> SMART support is: Enabled
    >>
    >> === START OF READ SMART DATA SECTION ===
    >> SMART overall-health self-assessment test result: PASSED
    >>
    >> General SMART Values:
    >> Offline data collection status: (0x82) Offline data collection
    >> activity was completed
    >> without error. Auto Offline
    >> Data Collection: Enabled.
    >> Total time to complete Offline
    >> data collection: ( 1) seconds.
    >> Offline data collection
    >> capabilities: (0x03) SMART execute Offline
    >> immediate. Auto Offline data
    >> collection on/off support.
    >> Suspend Offline collection
    >> upon new command.
    >> No Offline surface scan
    >> supported. No Self-test
    >> supported. No Conveyance
    >> Self-test supported. No
    >> Selective Self-test supported. SMART capabilities: (0x0003) Saves SMART data before
    >> entering power-saving mode.
    >> Supports SMART auto save
    >> timer. Error logging capability: (0x00) Error logging NOT
    >> supported. No General Purpose
    >> Logging support.
    >> SMART Attributes Data Structure revision number: 7
    >> Vendor Specific SMART Attributes with Thresholds:
    >> ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE
    >> UPDATED WHEN_FAILED RAW_VALUE
    >> 1 Raw_Read_Error_Rate 0x0029 100 100 020 Pre-fail
    >> Offline - 0
    >> 3 Spin_Up_Time 0x0027 089 076 020 Pre-fail
    >> Always - 1489
    >> 4 Start_Stop_Count 0x0032 099 099 008 Old_age
    >> Always - 1198
    >> 5 Reallocated_Sector_Ct 0x0033 100 100 020 Pre-fail
    >> Always - 0
    >> 7 Seek_Error_Rate 0x000b 100 100 023 Pre-fail
    >> Always - 0
    >> 9 Power_On_Hours 0x0012 007 007 001 Old_age
    >> Always - 61139
    >> 11 Calibration_Retry_Count 0x0013 100 100 020 Pre-fail
    >> Always - 0
    >> 12 Power_Cycle_Count 0x0032 099 099 008 Old_age
    >> Always - 1191
    >> 13 Read_Soft_Error_Rate 0x000b 100 100 023 Pre-fail
    >> Always - 0
    >> 199 UDMA_CRC_Error_Count 0x001a 200 200 000 Old_age Always - 0
    >>
    >> Warning: device does not support Error Logging
    >> SMART Error Log Version: 0
    >> No Errors Logged
    >>
    >> Warning: device does not support Self Test Logging
    >> SMART Self-test log structure revision number 0
    >> Warning: ATA Specification requires self-test log structure revision
    >> number = 1
    >> No self-tests have been logged. [To run self-tests, use: smartctl -t]

    >
    >> Device does not support Selective Self Tests/Logging

    >
    >> What's going on with my HDDs?

    >
    > Something's died, Jim. You into necrophilia ?


    :P


    >> I am not a hardware and Linux/Debian expert. My hardware specifications can be found here:
    >> http://alpha.zimage.com/~ant/antfarm.../computers.txt
    >> (secondary/backup computer). For now, I am going to unmount /dev/hdb to see if hdb is causing all this madness.

    >
    > There's certainly quite a few bad sectors on that drive.


    How can you tell? I am so used to chkdsk, scandisk, pretty images, etc.


    > That shouldnt have produced the errors with the other drive tho so something else has died too.


    True. So far, unmounting hdb hasn't resulted any symptoms. However, I
    haven't done much on it since I went to eat dinner and do other things.


    > The system appears to be pretty comprehensively ****ed.





    > It would be worth trying a spare power supply, it might be something as basic as that.


    OK, I will keep that in mind. My PSU in that box isn't that old. I had
    to replace it with a new one on 5/14/2007 according to
    http://alpha.zimage.com/~ant/antfarm/about/toys.html: "Replaced the dead
    Antec PSU in Linux/Debian box with a Fortron FSP650-80GLC PSU (650 watts)."


    > Worth checking for bad caps on the motherboard too. These are the usually blue or
    > black plastic covered post like things that stick up vertically from the motherboard surface.
    > The tops should be flat. If any have bulged or have leaked, thats a bad cap and for someone
    > like you the only real fix is to replace the motherboard. May be better to just bin the PC tho.


    OK, I will check again. The last time I opened this PC was in late
    January 2008, and I had several kernel panics and PC lockups due to a
    bad 512 MB Kingston memory (took a day to figure that out). This could
    be related, but then I don't recall any funny odors, saw any coloring on
    hardwares, bad caps, etc. Even my computer friend who build computers
    looked and didn't see anything back then and told me it was bad RAM. Hmm.

    Let's see how having hdb disabled go. hdb is mainly a storage and backup
    drive, and I already made a backup of it a few weeks ago (not much
    changed that I can recall).
    --
    "PLEASE tell your aardvark that I'm NOT an anthill!" --unknown
    /\___/\
    / /\ /\ \ Phil/Ant @ http://antfarm.home.dhs.org (Personal Web Site)
    | |o o| | Ant's Quality Foraged Links (AQFL): http://aqfl.net
    \ _ / Remove ANT from e-mail address: philpi@earthlink.netANT
    ( ) or ANTant@zimage.com
    Ant is currently not listening to any songs on his home computer.

  6. Re: Bad disk controller? Dying HDD?

    Ant wrote:
    > On 8/12/2008 11:08 PM PT, Rod Speed typed:
    >
    >> Ant wrote:
    >>> Hi. My old mini-tower PC's HDDs are acting crazy today. I came home
    >>> and noticed my second drive wasn't there so I checked dmesg (deleted
    >>> normal logs before hdb):


    >>> SMART Attributes Data Structure revision number: 7
    >>> Vendor Specific SMART Attributes with Thresholds:
    >>> ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE
    >>> UPDATED WHEN_FAILED RAW_VALUE
    >>> 1 Raw_Read_Error_Rate 0x0029 100 100 020 Pre-fail
    >>> Offline - 0
    >>> 3 Spin_Up_Time 0x0027 089 076 020 Pre-fail
    >>> Always - 1489
    >>> 4 Start_Stop_Count 0x0032 099 099 008 Old_age
    >>> Always - 1198
    >>> 5 Reallocated_Sector_Ct 0x0033 100 100 020 Pre-fail
    >>> Always - 0
    >>> 7 Seek_Error_Rate 0x000b 100 100 023 Pre-fail
    >>> Always - 0
    >>> 9 Power_On_Hours 0x0012 007 007 001 Old_age
    >>> Always - 61139
    >>> 11 Calibration_Retry_Count 0x0013 100 100 020 Pre-fail
    >>> Always - 0
    >>> 12 Power_Cycle_Count 0x0032 099 099 008 Old_age
    >>> Always - 1191
    >>> 13 Read_Soft_Error_Rate 0x000b 100 100 023 Pre-fail
    >>> Always - 0
    >>> 199 UDMA_CRC_Error_Count 0x001a 200 200 000 Old_age Always - 0 Warning: device does not support
    >>> Error Logging
    >>> SMART Error Log Version: 0
    >>> No Errors Logged
    >>>
    >>> Warning: device does not support Self Test Logging
    >>> SMART Self-test log structure revision number 0
    >>> Warning: ATA Specification requires self-test log structure revision
    >>> number = 1
    >>> No self-tests have been logged. [To run self-tests, use: smartctl
    >>> -t]

    >>
    >>> Device does not support Selective Self Tests/Logging

    >>
    >>> What's going on with my HDDs?

    >>
    >> Something's died, Jim. You into necrophilia ?

    >
    >> P

    >
    >
    >>> I am not a hardware and Linux/Debian expert. My hardware
    >>> specifications can be found here:
    >>> http://alpha.zimage.com/~ant/antfarm.../computers.txt
    >>> (secondary/backup computer). For now, I am going to unmount
    >>> /dev/hdb to see if hdb is causing all this madness.


    >> There's certainly quite a few bad sectors on that drive.


    > How can you tell?


    Thats the reallocated sector count in the SMART report.

    > I am so used to chkdsk, scandisk, pretty images, etc.


    A Jap would at least have the decency to disembowel itself.

    >> That shouldnt have produced the errors with the other drive tho so something else has died too.


    > True. So far, unmounting hdb hasn't resulted any symptoms. However, I haven't done much on it since I went to eat
    > dinner and do other things.


    >> The system appears to be pretty comprehensively ****ed.


    >


    >> It would be worth trying a spare power supply, it might be something as basic as that.


    > OK, I will keep that in mind. My PSU in that box isn't that old. I had to replace it with a new one on 5/14/2007
    > according to
    > http://alpha.zimage.com/~ant/antfarm/about/toys.html: "Replaced the
    > dead Antec PSU in Linux/Debian box with a Fortron FSP650-80GLC PSU
    > (650 watts)."


    >> Worth checking for bad caps on the motherboard too. These are the
    >> usually blue or black plastic covered post like things that stick up vertically from
    >> the motherboard surface. The tops should be flat. If any have bulged
    >> or have leaked, thats a bad cap and for someone like you the only
    >> real fix is to replace the motherboard. May be better to just bin
    >> the PC tho.


    > OK, I will check again. The last time I opened this PC was in late
    > January 2008, and I had several kernel panics and PC lockups due to a
    > bad 512 MB Kingston memory (took a day to figure that out). This could
    > be related, but then I don't recall any funny odors, saw any coloring
    > on hardwares, bad caps, etc. Even my computer friend who build
    > computers looked and didn't see anything back then and told me it was
    > bad RAM. Hmm.


    > Let's see how having hdb disabled go. hdb is mainly a storage and
    > backup drive, and I already made a backup of it a few weeks ago (not
    > much changed that I can recall).




  7. Re: Bad disk controller? Dying HDD?

    In comp.sys.ibm.pc.hardware.storage Ant wrote:
    > Hi. My old mini-tower PC's HDDs are acting crazy today. I came home and
    > noticed my second drive wasn't there so I checked dmesg (deleted normal
    > logs before hdb):


    From the SMART status, the Seagate (first drive) has read and
    seek errors, that could well be connected. The Quantum looks
    fine in SMART, but it is older (i.e. less reliable SMART
    implementation) and has nasty SectorIDNotFound errors in the
    log.

    So, what is going on indeed. I think either hdb is dying
    and messing with the bus as it does so, or you have a different
    problem. Attributes 1 and 7 on hda do not look good either.
    The errors in the log for hda could indeed be a controller
    issue, but nether could the errors for hdb or the SMART
    attributes 1 and 7 for hda. I would suspect that your PSU is
    going south and that unlean power is causing the problem.

    Arno





    > hdb: dma_timer_expiry: dma status == 0x61
    > hdb: DMA timeout error
    > hdb: dma timeout error: status=0x58 { DriveReady SeekComplete
    > DataRequest }
    > ide: failed opcode was: unknown
    > hda: DMA disabled
    > hdb: DMA disabled
    > ide0: reset: success
    > hdb: dma_intr: status=0x7d { DriveReady DeviceFault SeekComplete
    > DataRequest CorrectedError Error }
    > hdb: dma_intr: error=0x7d { DriveStatusError UncorrectableError
    > SectorIdNotFound AddrMarkNotFound }, LBAsect=226327933, sector=3522545
    > ide: failed opcode was: unknown
    > hdb: DMA disabled
    > ide0: reset: success
    > hdb: task_in_intr: status=0x7d { DriveReady DeviceFault SeekComplete
    > DataRequest CorrectedError Error }
    > hdb: task_in_intr: error=0x7d { DriveStatusError UncorrectableError
    > SectorIdNotFound AddrMarkNotFound }, LBAsect=226327933, sector=2362513
    > ide: failed opcode was: unknown
    > ide0: reset: success
    > hdb: task_in_intr: status=0x7d { DriveReady DeviceFault SeekComplete
    > DataRequest CorrectedError Error }
    > hdb: task_in_intr: error=0x7d { DriveStatusError UncorrectableError
    > SectorIdNotFound AddrMarkNotFound }, LBAsect=226327933, sector=2362513
    > ide: failed opcode was: unknown
    > ide0: reset: success
    > ABORTED IN=eth0 OUT= MAC=00:d0:b7:85:0a:3f:00:a0:c5:e3:18:a8:08:00
    > SRC=216.86.199.5 DST=192.168.0.32 LEN=40 TOS=0x00 PREC=0x00 TTL=46
    > ID=15957 DF PROTO=TCP SPT=6667 DPT=1788 SEQ=2622437680 ACK=0 WINDOW=0
    > RES=0x00 RST URGP=0
    > hdb: task_in_intr: status=0x7d { DriveReady DeviceFault SeekComplete
    > DataRequest CorrectedError Error }
    > hdb: task_in_intr: error=0x7d { DriveStatusError UncorrectableError
    > SectorIdNotFound AddrMarkNotFound }, LBAsect=226327933, sector=3537401
    > ide: failed opcode was: unknown
    > ide0: reset: success
    > hdb: task_in_intr: status=0x7d { DriveReady DeviceFault SeekComplete
    > DataRequest CorrectedError Error }
    > hdb: task_in_intr: error=0x7d { DriveStatusError UncorrectableError
    > SectorIdNotFound AddrMarkNotFound }, LBAsect=226327933, sector=3537401
    > ide: failed opcode was: unknown
    > ide0: reset timed-out, status=0x90
    > hdb: status error: status=0x7d { DriveReady DeviceFault SeekComplete
    > DataRequest CorrectedError Error }
    > hdb: status error: error=0x7d { DriveStatusError UncorrectableError
    > SectorIdNotFound AddrMarkNotFound }, LBAsect=226327933, sector=3537401
    > ide: failed opcode was: unknown
    > end_request: I/O error, dev hdb, sector 3537401
    > hdb: drive not ready for command
    > hdb: status error: status=0x7d { DriveReady DeviceFault SeekComplete
    > DataRequest CorrectedError Error }
    > hdb: status error: error=0x7d { DriveStatusError UncorrectableError
    > SectorIdNotFound AddrMarkNotFound }, LBAsect=226327933, sector=3537409
    > ide: failed opcode was: unknown
    > hdb: drive not ready for command
    > ide0: reset timed-out, status=0x90
    > end_request: I/O error, dev hdb, sector 3537409
    > end_request: I/O error, dev hdb, sector 3537417
    > end_request: I/O error, dev hdb, sector 3537425
    > end_request: I/O error, dev hdb, sector 3537401
    > end_request: I/O error, dev hdb, sector 3538825
    > end_request: I/O error, dev hdb, sector 3538833
    > end_request: I/O error, dev hdb, sector 3538841
    > end_request: I/O error, dev hdb, sector 3538849
    > end_request: I/O error, dev hdb, sector 3538825
    > end_request: I/O error, dev hdb, sector 3537977
    > end_request: I/O error, dev hdb, sector 3537985
    > end_request: I/O error, dev hdb, sector 3537993
    > end_request: I/O error, dev hdb, sector 3538001
    > end_request: I/O error, dev hdb, sector 3537977
    > end_request: I/O error, dev hdb, sector 3536889
    > end_request: I/O error, dev hdb, sector 3536897
    > end_request: I/O error, dev hdb, sector 3536905
    > end_request: I/O error, dev hdb, sector 3536913
    > end_request: I/O error, dev hdb, sector 3536889
    > end_request: I/O error, dev hdb, sector 3539689
    > end_request: I/O error, dev hdb, sector 3539697
    > end_request: I/O error, dev hdb, sector 3539705
    > end_request: I/O error, dev hdb, sector 3539713
    > end_request: I/O error, dev hdb, sector 3539689
    > end_request: I/O error, dev hdb, sector 3544185
    > end_request: I/O error, dev hdb, sector 3544193
    > end_request: I/O error, dev hdb, sector 3544201
    > end_request: I/O error, dev hdb, sector 3544209
    > end_request: I/O error, dev hdb, sector 3544185
    > end_request: I/O error, dev hdb, sector 3540457
    > end_request: I/O error, dev hdb, sector 3540465
    > end_request: I/O error, dev hdb, sector 3540473
    > end_request: I/O error, dev hdb, sector 3540481
    > end_request: I/O error, dev hdb, sector 3540457
    > end_request: I/O error, dev hdb, sector 3542089
    > end_request: I/O error, dev hdb, sector 3542097
    > end_request: I/O error, dev hdb, sector 3542105
    > end_request: I/O error, dev hdb, sector 3542113
    > end_request: I/O error, dev hdb, sector 3542089
    > end_request: I/O error, dev hdb, sector 3542897
    > end_request: I/O error, dev hdb, sector 3542905
    > end_request: I/O error, dev hdb, sector 3542913
    > end_request: I/O error, dev hdb, sector 3542921
    > end_request: I/O error, dev hdb, sector 3542897
    > end_request: I/O error, dev hdb, sector 7257
    > end_request: I/O error, dev hdb, sector 7265
    > end_request: I/O error, dev hdb, sector 7273
    > journal_bmap: journal block not found at offset 12 on hdb1
    > Aborting journal on device hdb1.
    > end_request: I/O error, dev hdb, sector 7177
    > Buffer I/O error on device hdb1, logical block 897
    > lost page write due to I/O error on hdb1
    > end_request: I/O error, dev hdb, sector 2362529
    > Buffer I/O error on device hdb1, logical block 295316
    > lost page write due to I/O error on hdb1
    > ABORTED IN=eth0 OUT= MAC=00:d0:b7:85:0a:3f:00:a0:c5:e3:18:a8:08:00
    > SRC=64.22.96.69 DST=192.168.0.32 LEN=40 TOS=0x00 PREC=0x00 TTL=50 ID=0
    > DF PROTO=TCP SPT=35249 DPT=22 SEQ=481307265 ACK=0 WINDOW=0 RES=0x00 RST
    > URGP=0
    > ABORTED IN=eth0 OUT= MAC=00:d0:b7:85:0a:3f:00:a0:c5:e3:18:a8:08:00
    > SRC=64.22.96.69 DST=192.168.0.32 LEN=40 TOS=0x00 PREC=0x00 TTL=50 ID=0
    > DF PROTO=TCP SPT=35249 DPT=22 SEQ=481307265 ACK=0 WINDOW=0 RES=0x00 RST
    > URGP=0
    > end_request: I/O error, dev hdb, sector 3543081
    > end_request: I/O error, dev hdb, sector 3543089
    > end_request: I/O error, dev hdb, sector 3543097
    > end_request: I/O error, dev hdb, sector 3543105
    > end_request: I/O error, dev hdb, sector 3543081
    > ext3_abort called.
    > EXT3-fs error (device hdb1): ext3_journal_start_sb: Detected aborted
    > journal
    > Remounting filesystem read-only
    > end_request: I/O error, dev hdb, sector 3533193
    > end_request: I/O error, dev hdb, sector 3533201
    > end_request: I/O error, dev hdb, sector 3533209
    > end_request: I/O error, dev hdb, sector 3533217
    > end_request: I/O error, dev hdb, sector 3533193
    > end_request: I/O error, dev hdb, sector 3533193
    > end_request: I/O error, dev hdb, sector 3533193
    > end_request: I/O error, dev hdb, sector 3533193
    > end_request: I/O error, dev hdb, sector 3533193
    > end_request: I/O error, dev hdb, sector 3533193
    > end_request: I/O error, dev hdb, sector 2362529
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=72691, block=295316
    > end_request: I/O error, dev hdb, sector 3533193
    > end_request: I/O error, dev hdb, sector 3533193
    > end_request: I/O error, dev hdb, sector 3533193
    > end_request: I/O error, dev hdb, sector 3533193
    > end_request: I/O error, dev hdb, sector 3533193
    > end_request: I/O error, dev hdb, sector 3533193
    > ABORTED IN=eth0 OUT= MAC=00:d0:b7:85:0a:3f:00:16:17:94:32:d6:08:00
    > SRC=192.168.0.46 DST=192.168.0.32 LEN=40 TOS=0x00 PREC=0x00 TTL=64
    > ID=230 PROTO=TCP SPT=1056 DPT=139 SEQ=1299343103 ACK=1299343103 WINDOW=0
    > RES=0x00 RST URGP=0
    > ABORTED IN=eth0 OUT= MAC=00:d0:b7:85:0a:3f:00:16:17:94:32:d6:08:00
    > SRC=192.168.0.46 DST=192.168.0.32 LEN=40 TOS=0x00 PREC=0x00 TTL=64
    > ID=1980 PROTO=TCP SPT=1261 DPT=139 SEQ=969640467 ACK=969640467 WINDOW=0
    > RES=0x00 RST URGP=0
    > end_request: I/O error, dev hdb, sector 2362721
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73086, block=295340
    > end_request: I/O error, dev hdb, sector 2362801
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73240, block=295350
    > end_request: I/O error, dev hdb, sector 2362753
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73146, block=295344
    > end_request: I/O error, dev hdb, sector 2362729
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73092, block=295341
    > end_request: I/O error, dev hdb, sector 2362729
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73093, block=295341
    > end_request: I/O error, dev hdb, sector 2362745
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73121, block=295343
    > end_request: I/O error, dev hdb, sector 2362729
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73089, block=295341
    > end_request: I/O error, dev hdb, sector 4568761
    > end_request: I/O error, dev hdb, sector 2362753
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73140, block=295344
    > end_request: I/O error, dev hdb, sector 2362729
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73100, block=295341
    > end_request: I/O error, dev hdb, sector 2362737
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73113, block=295342
    > end_request: I/O error, dev hdb, sector 2362745
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73129, block=295343
    > end_request: I/O error, dev hdb, sector 2362745
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73135, block=295343
    > end_request: I/O error, dev hdb, sector 2362761
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73164, block=295345
    > end_request: I/O error, dev hdb, sector 2362753
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73142, block=295344
    > end_request: I/O error, dev hdb, sector 2362761
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73162, block=295345
    > end_request: I/O error, dev hdb, sector 2362729
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73104, block=295341
    > end_request: I/O error, dev hdb, sector 2362745
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73128, block=295343
    > end_request: I/O error, dev hdb, sector 2362745
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73122, block=295343
    > end_request: I/O error, dev hdb, sector 2362761
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73153, block=295345
    > end_request: I/O error, dev hdb, sector 2362753
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73141, block=295344
    > end_request: I/O error, dev hdb, sector 2362753
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73144, block=295344
    > end_request: I/O error, dev hdb, sector 2362753
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73148, block=295344
    > end_request: I/O error, dev hdb, sector 2362753
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73139, block=295344
    > end_request: I/O error, dev hdb, sector 2362729
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73095, block=295341
    > end_request: I/O error, dev hdb, sector 2362745
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73127, block=295343
    > end_request: I/O error, dev hdb, sector 2362745
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73134, block=295343
    > end_request: I/O error, dev hdb, sector 2362753
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73152, block=295344
    > end_request: I/O error, dev hdb, sector 2362753
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73149, block=295344
    > end_request: I/O error, dev hdb, sector 2362761
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73155, block=295345
    > end_request: I/O error, dev hdb, sector 2362745
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73131, block=295343
    > end_request: I/O error, dev hdb, sector 2362761
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73168, block=295345
    > end_request: I/O error, dev hdb, sector 2362745
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73132, block=295343
    > end_request: I/O error, dev hdb, sector 2362737
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73118, block=295342
    > end_request: I/O error, dev hdb, sector 2362761
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73158, block=295345
    > end_request: I/O error, dev hdb, sector 2362729
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73103, block=295341
    > end_request: I/O error, dev hdb, sector 2588673
    > end_request: I/O error, dev hdb, sector 2362729
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73101, block=295341
    > end_request: I/O error, dev hdb, sector 2362753
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73138, block=295344
    > end_request: I/O error, dev hdb, sector 2362761
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73167, block=295345
    > end_request: I/O error, dev hdb, sector 2362729
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73102, block=295341
    > end_request: I/O error, dev hdb, sector 2362761
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73165, block=295345
    > end_request: I/O error, dev hdb, sector 2362745
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73125, block=295343
    > end_request: I/O error, dev hdb, sector 2362737
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73110, block=295342
    > end_request: I/O error, dev hdb, sector 2362737
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73109, block=295342
    > end_request: I/O error, dev hdb, sector 2362769
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73169, block=295346
    > end_request: I/O error, dev hdb, sector 3651025
    > end_request: I/O error, dev hdb, sector 2362761
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73157, block=295345
    > end_request: I/O error, dev hdb, sector 2362729
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73097, block=295341
    > end_request: I/O error, dev hdb, sector 2362737
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73106, block=295342
    > end_request: I/O error, dev hdb, sector 2362737
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73114, block=295342
    > end_request: I/O error, dev hdb, sector 2362761
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73166, block=295345
    > end_request: I/O error, dev hdb, sector 2362737
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73117, block=295342
    > end_request: I/O error, dev hdb, sector 2362737
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73120, block=295342
    > end_request: I/O error, dev hdb, sector 2362753
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73150, block=295344
    > end_request: I/O error, dev hdb, sector 2362729
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73091, block=295341
    > end_request: I/O error, dev hdb, sector 2362753
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73147, block=295344
    > end_request: I/O error, dev hdb, sector 2362729
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73099, block=295341
    > end_request: I/O error, dev hdb, sector 2362761
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73154, block=295345
    > end_request: I/O error, dev hdb, sector 2362745
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73124, block=295343
    > end_request: I/O error, dev hdb, sector 2362737
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73108, block=295342
    > end_request: I/O error, dev hdb, sector 2362737
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73116, block=295342
    > end_request: I/O error, dev hdb, sector 2362753
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73137, block=295344
    > end_request: I/O error, dev hdb, sector 2362737
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73111, block=295342
    > end_request: I/O error, dev hdb, sector 4568729
    > end_request: I/O error, dev hdb, sector 2362737
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73119, block=295342
    > end_request: I/O error, dev hdb, sector 2362729
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73098, block=295341
    > end_request: I/O error, dev hdb, sector 4567841
    > end_request: I/O error, dev hdb, sector 2362721
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73088, block=295340
    > end_request: I/O error, dev hdb, sector 2362737
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73105, block=295342
    > end_request: I/O error, dev hdb, sector 2362729
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73090, block=295341
    > end_request: I/O error, dev hdb, sector 2362745
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73133, block=295343
    > end_request: I/O error, dev hdb, sector 2362761
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73161, block=295345
    > end_request: I/O error, dev hdb, sector 2362737
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73115, block=295342
    > end_request: I/O error, dev hdb, sector 2362745
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73136, block=295343
    > end_request: I/O error, dev hdb, sector 2362745
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73123, block=295343
    > end_request: I/O error, dev hdb, sector 2362761
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73160, block=295345
    > end_request: I/O error, dev hdb, sector 2362737
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73112, block=295342
    > end_request: I/O error, dev hdb, sector 2362761
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73156, block=295345
    > end_request: I/O error, dev hdb, sector 2362761
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73159, block=295345
    > end_request: I/O error, dev hdb, sector 2362753
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73151, block=295344
    > end_request: I/O error, dev hdb, sector 2362729
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73094, block=295341
    > end_request: I/O error, dev hdb, sector 2362729
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73096, block=295341
    > end_request: I/O error, dev hdb, sector 2362745
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73130, block=295343
    > end_request: I/O error, dev hdb, sector 2362737
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73107, block=295342
    > end_request: I/O error, dev hdb, sector 2362761
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73163, block=295345
    > end_request: I/O error, dev hdb, sector 2362745
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73126, block=295343
    > end_request: I/O error, dev hdb, sector 3648201
    > end_request: I/O error, dev hdb, sector 2362753
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73143, block=295344
    > end_request: I/O error, dev hdb, sector 2362753
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=73145, block=295344
    > end_request: I/O error, dev hdb, sector 2710017
    > end_request: I/O error, dev hdb, sector 2605065
    > end_request: I/O error, dev hdb, sector 3544825
    > end_request: I/O error, dev hdb, sector 2362505
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=72647, block=295313
    > end_request: I/O error, dev hdb, sector 2362529
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=72689, block=295316
    > end_request: I/O error, dev hdb, sector 2362505
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=72643, block=295313
    > end_request: I/O error, dev hdb, sector 2362521
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=72678, block=295315
    > end_request: I/O error, dev hdb, sector 3522817
    > end_request: I/O error, dev hdb, sector 2362521
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=72682, block=295315
    > end_request: I/O error, dev hdb, sector 2362521
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=72687, block=295315
    > end_request: I/O error, dev hdb, sector 2362505
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=72648, block=295313
    > end_request: I/O error, dev hdb, sector 2362521
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=72683, block=295315
    > end_request: I/O error, dev hdb, sector 2362505
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=72650, block=295313
    > end_request: I/O error, dev hdb, sector 2362505
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=72649, block=295313
    > end_request: I/O error, dev hdb, sector 2362521
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=72673, block=295315
    > end_request: I/O error, dev hdb, sector 2362505
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=72653, block=295313
    > end_request: I/O error, dev hdb, sector 2362505
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=72641, block=295313
    > end_request: I/O error, dev hdb, sector 2362521
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=72674, block=295315
    > end_request: I/O error, dev hdb, sector 2362521
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=72685, block=295315
    > end_request: I/O error, dev hdb, sector 2362521
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=72676, block=295315
    > end_request: I/O error, dev hdb, sector 2362521
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=72686, block=295315
    > end_request: I/O error, dev hdb, sector 3522553
    > end_request: I/O error, dev hdb, sector 3524505
    > end_request: I/O error, dev hdb, sector 2362521
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=72681, block=295315
    > end_request: I/O error, dev hdb, sector 2362505
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=72645, block=295313
    > end_request: I/O error, dev hdb, sector 2362505
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=72646, block=295313
    > end_request: I/O error, dev hdb, sector 2362521
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=72675, block=295315
    > end_request: I/O error, dev hdb, sector 2362505
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=72651, block=295313
    > end_request: I/O error, dev hdb, sector 2362521
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=72680, block=295315
    > end_request: I/O error, dev hdb, sector 2362521
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=72679, block=295315
    > end_request: I/O error, dev hdb, sector 2362505
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=72654, block=295313
    > end_request: I/O error, dev hdb, sector 2362505
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=72655, block=295313
    > end_request: I/O error, dev hdb, sector 2362521
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=72677, block=295315
    > end_request: I/O error, dev hdb, sector 2362505
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=72656, block=295313
    > end_request: I/O error, dev hdb, sector 2362521
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=72684, block=295315
    > end_request: I/O error, dev hdb, sector 2362497
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=72640, block=295312
    > end_request: I/O error, dev hdb, sector 2362505
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=72642, block=295313
    > end_request: I/O error, dev hdb, sector 2362505
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=72644, block=295313
    > end_request: I/O error, dev hdb, sector 2362529
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=72690, block=295316
    > end_request: I/O error, dev hdb, sector 2362505
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=72652, block=295313
    > end_request: I/O error, dev hdb, sector 2362521
    > EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode
    > block - inode=72688, block=295315
    > end_request: I/O error, dev hdb, sector 5119177


    > I did an unmount of hdb, fdisk /dev/hdb, and it couldn't read it. I did
    > a reboot, HDD showed up in CMOS/BIOS and Debian went to its safe mode
    > and let me fsck it. fsck /dev/hdb said all ext3 journals got lost and
    > reverted back to ext2. I fsck'ed. After reboot and remounting, it seems
    > the files were OK? So I put journal back and things were OK.



    > A few minutes later, things go crazy again:
    > $ dmesg
    > e PFN ranges
    > 0: 0 -> 130864
    > On node 0 totalpages: 130864
    > DMA zone: 32 pages used for memmap
    > DMA zone: 0 pages reserved
    > DMA zone: 4064 pages, LIFO batch:0
    > Normal zone: 990 pages used for memmap
    > Normal zone: 125778 pages, LIFO batch:31
    > HighMem zone: 0 pages used for memmap
    > DMI 2.3 present.
    > ACPI: RSDP 000FA850, 0014 (r0 ACPIAM)
    > ACPI: RSDT 1FF30000, 0030 (r1 A M I OEMRSDT 6000517 MSFT 97)
    > ACPI: FACP 1FF30200, 0081 (r1 A M I OEMFACP 6000517 MSFT 97)
    > ACPI: DSDT 1FF303E0, 3755 (r1 A0058 A0058002 2 MSFT 100000D)
    > ACPI: FACS 1FF40000, 0040
    > ACPI: APIC 1FF30390, 004A (r1 A M I OEMAPIC 6000517 MSFT 97)
    > ACPI: OEMB 1FF40040, 003F (r1 A M I OEMBIOS 6000517 MSFT 97)
    > ACPI: PM-Timer IO Port: 0x808
    > ACPI: Local APIC address 0xfee00000
    > ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
    > Processor #0 15:12 APIC version 16
    > ACPI: IOAPIC (id[0x01] address[0xfec00000] gsi_base[0])
    > IOAPIC[0]: apic_id 1, version 3, address 0xfec00000, GSI 0-23
    > ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
    > ACPI: IRQ0 used by override.
    > ACPI: IRQ2 used by override.
    > ACPI: IRQ9 used by override.
    > Enabling APIC mode: Flat. Using 1 I/O APICs
    > Using ACPI (MADT) for SMP configuration information
    > Allocating PCI resources starting at 30000000 (gap: 20000000:dff80000)
    > Built 1 zonelists. Total pages: 129842
    > Kernel command line: root=/dev/hda1 ro
    > mapped APIC to ffffd000 (fee00000)
    > mapped IOAPIC to ffffc000 (fec00000)
    > Enabling fast FPU save and restore... done.
    > Enabling unmasked SIMD FPU exception support... done.
    > Initializing CPU#0
    > PID hash table entries: 2048 (order: 11, 8192 bytes)
    > Detected 2202.937 MHz processor.
    > spurious 8259A interrupt: IRQ7.
    > Console: colour VGA+ 80x25
    > Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
    > Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
    > Memory: 514020k/523456k available (1702k kernel code, 8820k reserved,
    > 663k data, 244k init, 0k highmem)
    > virtual kernel memory layout:
    > fixmap : 0xfff4e000 - 0xfffff000 ( 708 kB)
    > pkmap : 0xff800000 - 0xffc00000 (4096 kB)
    > vmalloc : 0xe0800000 - 0xff7fe000 ( 495 MB)
    > lowmem : 0xc0000000 - 0xdff30000 ( 511 MB)
    > .init : 0xc0355000 - 0xc0392000 ( 244 kB)
    > .data : 0xc02a9827 - 0xc034f784 ( 663 kB)
    > .text : 0xc0100000 - 0xc02a9827 (1702 kB)
    > Checking if this processor honours the WP bit even in supervisor mode... Ok.
    > Calibrating delay using timer specific routine.. 4410.78 BogoMIPS
    > (lpj=8821571)
    > Security Framework v1.0.0 initialized
    > SELinux: Disabled at boot.
    > Capability LSM initialized
    > Mount-cache hash table entries: 512
    > CPU: After generic identify, caps: 078bfbff e1d3fbff 00000000 00000000
    > 00000000 00000000 00000000
    > CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
    > CPU: L2 Cache: 512K (64 bytes/line)
    > CPU: After all inits, caps: 078bfbff e1d3fbff 00000000 00000410 00000000
    > 00000000 00000000
    > Intel machine check architecture supported.
    > Intel machine check reporting enabled on CPU#0.
    > Compat vDSO mapped to ffffe000.
    > Checking 'hlt' instruction... OK.
    > SMP alternatives: switching to UP code
    > Freeing SMP alternatives: 11k freed
    > ACPI: Core revision 20070126
    > CPU0: AMD Athlon(tm) 64 Processor 3200+ stepping 00
    > Total of 1 processors activated (4410.78 BogoMIPS).
    > ENABLING IO-APIC IRQs
    > ..TIMER: vector=0x31 apic1=0 pin1=2 apic2=0 pin2=0
    > Brought up 1 CPUs
    > Booting paravirtualized kernel on bare hardware
    > NET: Registered protocol family 16
    > ACPI: bus type pci registered
    > PCI: PCI BIOS revision 2.10 entry at 0xf0031, last bus=1
    > PCI: Using configuration type 1
    > Setting up standard PCI resources
    > ACPI: Interpreter enabled
    > ACPI: (supports S0 S1 S3 S4 S5)
    > ACPI: Using IOAPIC for interrupt routing
    > ACPI: PCI Root Bridge [PCI0] (0000:00)
    > PCI: Probing PCI hardware (bus 00)
    > PCI: Firmware left 0000:00:09.0 e100 interrupts enabled, disabling
    > PCI: enabled onboard AC97/MC97 devices
    > ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
    > ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 7 10 *11 14 15)
    > ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 7 *10 11 14 15)
    > ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 7 10 11 14 15)
    > ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 7 10 11 14 15) *0, disabled.
    > ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 7 10 11 14 15) *0, disabled.
    > ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 7 10 11 14 15) *0, disabled.
    > ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 7 10 11 14 15) *0, disabled.
    > ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 7 10 11 14 15) *0, disabled.
    > Linux Plug and Play Support v0.97 (c) Adam Belay
    > pnp: PnP ACPI init
    > ACPI: bus type pnp registered
    > pnp: PnP ACPI: found 13 devices
    > ACPI: ACPI bus type pnp unregistered
    > PnPBIOS: Disabled by ACPI PNP
    > PCI: Using ACPI for IRQ routing
    > PCI: If a device doesn't work, try "pci=routeirq". If it helps, post a
    > report
    > NET: Registered protocol family 8
    > NET: Registered protocol family 20
    > ACPI: RTC can wake from S4
    > pnp: 00:09: iomem range 0xfec00000-0xfec00fff has been reserved
    > pnp: 00:09: iomem range 0xfee00000-0xfee00fff has been reserved
    > pnp: 00:09: iomem range 0xfff80000-0xffffffff could not be reserved
    > pnp: 00:0c: iomem range 0x0-0x9ffff could not be reserved
    > pnp: 00:0c: iomem range 0xc0000-0xdffff could not be reserved
    > pnp: 00:0c: iomem range 0xe0000-0xfffff could not be reserved
    > pnp: 00:0c: iomem range 0x100000-0x1ffeffff could not be reserved
    > Time: tsc clocksource has been installed.
    > PCI: Bridge: 0000:00:01.0
    > IO window: disabled.
    > MEM window: f9500000-fd6fffff
    > PREFETCH window: e1400000-f13fffff
    > PCI: Setting latency timer of device 0000:00:01.0 to 64
    > NET: Registered protocol family 2
    > IP route cache hash table entries: 4096 (order: 2, 16384 bytes)
    > TCP established hash table entries: 16384 (order: 5, 196608 bytes)
    > TCP bind hash table entries: 16384 (order: 5, 131072 bytes)
    > TCP: Hash tables configured (established 16384 bind 16384)
    > TCP reno registered
    > checking if image is initramfs... it is
    > Freeing initrd memory: 1305k freed
    > audit: initializing netlink socket (disabled)
    > audit(1218577017.172:1): initialized
    > VFS: Disk quotas dquot_6.5.1
    > Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
    > io scheduler noop registered
    > io scheduler anticipatory registered
    > io scheduler deadline registered
    > io scheduler cfq registered (default)
    > PCI: VIA PCI bridge detected. Disabling DAC.
    > Boot video device is 0000:01:00.0
    > isapnp: Scanning for PnP cards...
    > Switched to high resolution mode on CPU 0
    > isapnp: No Plug & Play device found
    > Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing enabled
    > 00:0a: ttyS0 at I/O 0x2f8 (irq = 3) is a 16550A
    > 00:0b: ttyS1 at I/O 0x3f8 (irq = 4) is a 16550A
    > RAMDISK driver initialized: 16 RAM disks of 8192K size 1024 blocksize
    > PNP: PS/2 Controller [PNP0303:PS2K,PNP0f03:PS2M] at 0x60,0x64 irq 1,12
    > serio: i8042 KBD port at 0x60,0x64 irq 1
    > serio: i8042 AUX port at 0x60,0x64 irq 12
    > mice: PS/2 mouse device common for all mice
    > TCP bic registered
    > NET: Registered protocol family 1
    > NET: Registered protocol family 17
    > Using IPI No-Shortcut mode
    > Freeing unused kernel memory: 244k freed
    > Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
    > ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
    > VP_IDE: IDE controller at PCI slot 0000:00:0f.1
    > ACPI: PCI Interrupt 0000:00:0f.1[A] -> GSI 20 (level, low) -> IRQ 16
    > VP_IDE: chipset revision 6
    > VP_IDE: not 100% native mode: will probe irqs later
    > VP_IDE: VIA vt8237 (rev 00) IDE UDMA133 controller on pci0000:00:0f.1
    > ide0: BM-DMA at 0xfc00-0xfc07, BIOS settings: hdaMA, hdbMA
    > ide1: BM-DMA at 0xfc08-0xfc0f, BIOS settings: hdcMA, hddio
    > Probing IDE interface ide0...
    > input: AT Translated Set 2 keyboard as /class/input/input0
    > hda: ST380011A, ATA DISK drive
    > hdb: QUANTUM FIREBALL EX6.4A, ATA DISK drive
    > ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
    > Probing IDE interface ide1...
    > hdc: TOSHIBA DVD-ROM SD-M1912, ATAPI CD/DVD-ROM drive
    > ide1 at 0x170-0x177,0x376 on irq 15
    > SCSI subsystem initialized
    > libata version 2.21 loaded.
    > hda: max request size: 512KiB
    > hda: 156301488 sectors (80026 MB) w/2048KiB Cache, CHS=16383/255/63,
    > UDMA(100)
    > hda: cache flushes supported
    > hda: hda1 hda2 < hda5 hda6 hda7 hda8 hda9 hda10 hda11 hda12 >
    > hdb: max request size: 128KiB
    > hdb: 12594960 sectors (6448 MB) w/418KiB Cache, CHS=13328/15/63, UDMA(33)
    > hdb: cache flushes not supported
    > hdb: hdb1
    > kjournald starting. Commit interval 5 seconds
    > EXT3-fs: mounted filesystem with ordered data mode.
    > input: PC Speaker as /class/input/input1
    > pci_hotplug: PCI Hot Plug PCI Core version: 0.5
    > shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
    > Real Time Clock Driver v1.12ac
    > Floppy drive(s): fd0 is 1.44M
    > FDC 0 is a post-1991 82077
    > usbcore: registered new interface driver usbfs
    > usbcore: registered new interface driver hub
    > usbcore: registered new device driver usb
    > Linux agpgart interface v0.102 (c) Dave Jones
    > hdc: ATAPI 48X DVD-ROM drive, 512kB Cache, UDMA(33)
    > Uniform CD-ROM driver Revision: 3.20
    > USB Universal Host Controller Interface driver v3.0
    > ACPI: PCI Interrupt 0000:00:10.0[A] -> GSI 21 (level, low) -> IRQ 17
    > uhci_hcd 0000:00:10.0: UHCI Host Controller
    > uhci_hcd 0000:00:10.0: new USB bus registered, assigned bus number 1
    > uhci_hcd 0000:00:10.0: irq 17, io base 0x0000dc00
    > usb usb1: configuration #1 chosen from 1 choice
    > hub 1-0:1.0: USB hub found
    > hub 1-0:1.0: 2 ports detected
    > e100: Intel(R) PRO/100 Network Driver, 3.5.17-k4-NAPI
    > e100: Copyright(c) 1999-2006 Intel Corporation
    > ACPI: PCI Interrupt 0000:00:10.1[A] -> GSI 21 (level, low) -> IRQ 17
    > uhci_hcd 0000:00:10.1: UHCI Host Controller
    > uhci_hcd 0000:00:10.1: new USB bus registered, assigned bus number 2
    > uhci_hcd 0000:00:10.1: irq 17, io base 0x0000ec00
    > usb usb2: configuration #1 chosen from 1 choice
    > hub 2-0:1.0: USB hub found
    > hub 2-0:1.0: 2 ports detected
    > ACPI: PCI Interrupt 0000:00:10.2[B] -> GSI 21 (level, low) -> IRQ 17
    > uhci_hcd 0000:00:10.2: UHCI Host Controller
    > uhci_hcd 0000:00:10.2: new USB bus registered, assigned bus number 3
    > uhci_hcd 0000:00:10.2: irq 17, io base 0x0000c000
    > usb usb3: configuration #1 chosen from 1 choice
    > hub 3-0:1.0: USB hub found
    > hub 3-0:1.0: 2 ports detected
    > ACPI: PCI Interrupt 0000:00:10.3[B] -> GSI 21 (level, low) -> IRQ 17
    > uhci_hcd 0000:00:10.3: UHCI Host Controller
    > uhci_hcd 0000:00:10.3: new USB bus registered, assigned bus number 4
    > uhci_hcd 0000:00:10.3: irq 17, io base 0x0000c400
    > usb usb4: configuration #1 chosen from 1 choice
    > hub 4-0:1.0: USB hub found
    > hub 4-0:1.0: 2 ports detected
    > ACPI: PCI Interrupt 0000:00:10.4[C] -> GSI 21 (level, low) -> IRQ 17
    > ehci_hcd 0000:00:10.4: EHCI Host Controller
    > ehci_hcd 0000:00:10.4: new USB bus registered, assigned bus number 5
    > ehci_hcd 0000:00:10.4: irq 17, io mem 0xfd700000
    > ehci_hcd 0000:00:10.4: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
    > usb usb5: configuration #1 chosen from 1 choice
    > hub 5-0:1.0: USB hub found
    > hub 5-0:1.0: 8 ports detected
    > input: ImPS/2 Generic Wheel Mouse as /class/input/input2
    > agpgart: Detected AGP bridge 0
    > agpgart: AGP aperture is 64M @ 0xf4000000
    > sata_via 0000:00:0f.0: version 2.2
    > ACPI: PCI Interrupt 0000:00:0f.0[B] -> GSI 20 (level, low) -> IRQ 16
    > sata_via 0000:00:0f.0: routed to hard irq line 10
    > scsi0 : sata_via
    > scsi1 : sata_via
    > ata1: SATA max UDMA/133 cmd 0x0001e800 ctl 0x0001e402 bmdma 0x0001d400
    > irq 16
    > ata2: SATA max UDMA/133 cmd 0x0001e000 ctl 0x0001d802 bmdma 0x0001d408
    > irq 16
    > ata1: SATA link down 1.5 Gbps (SStatus 0 SControl 300)
    > ata2: SATA link down 1.5 Gbps (SStatus 0 SControl 300)
    > ACPI: PCI Interrupt 0000:00:09.0[A] -> GSI 16 (level, low) -> IRQ 18
    > e100: eth0: e100_probe: addr 0xfdc00000, irq 18, MAC addr 000:B7:85:0A:3F
    > PCI: Enabling device 0000:00:11.6 (0000 -> 0001)
    > ACPI: PCI Interrupt 0000:00:11.6[C] -> GSI 22 (level, low) -> IRQ 19
    > usb 2-2: new low speed USB device using uhci_hcd and address 2
    > PCI: Setting latency timer of device 0000:00:11.6 to 64
    > usb 2-2: configuration #1 chosen from 1 choice
    > usbcore: registered new interface driver hiddev
    > ACPI: PCI interrupt for device 0000:00:11.6 disabled
    > VIA 82xx Modem: probe of 0000:00:11.6 failed with error -13
    > ACPI: PCI Interrupt 0000:00:11.5[C] -> GSI 22 (level, low) -> IRQ 19
    > PCI: Setting latency timer of device 0000:00:11.5 to 64
    > codec_read: codec 0 is not valid [0xfe0000]
    > codec_read: codec 0 is not valid [0xfe0000]
    > codec_read: codec 0 is not valid [0xfe0000]
    > codec_read: codec 0 is not valid [0xfe0000]
    > hiddev96: USB HID v1.10 Device [American Power Conversion Back-UPS RS
    > 1500 FW:8.g8 .D USB FW:g8 ] on usb-0000:00:10.1-2
    > usbcore: registered new interface driver usbhid
    > drivers/hid/usbhid/hid-core.c: v2.6:USB HID core driver
    > Adding 2361512k swap on /dev/hda10. Priority:-1 extents:1 across:2361512k
    > EXT3 FS on hda1, internal journal
    > loop: module loaded
    > w83627hf: Found W83697HF chip at 0x290
    > fuse init (API version 7.8)
    > device-mapper: ioctl: 4.11.0-ioctl (2006-10-12) initialised:
    > dm-devel@redhat.com
    > kjournald starting. Commit interval 5 seconds
    > EXT3 FS on hda5, internal journal
    > EXT3-fs: mounted filesystem with ordered data mode.
    > kjournald starting. Commit interval 5 seconds
    > EXT3 FS on hda6, internal journal
    > EXT3-fs: mounted filesystem with ordered data mode.
    > kjournald starting. Commit interval 5 seconds
    > EXT3 FS on hda7, internal journal
    > EXT3-fs: mounted filesystem with ordered data mode.
    > kjournald starting. Commit interval 5 seconds
    > EXT3 FS on hda8, internal journal
    > EXT3-fs: mounted filesystem with ordered data mode.
    > kjournald starting. Commit interval 5 seconds
    > EXT3 FS on hda9, internal journal
    > EXT3-fs: mounted filesystem with ordered data mode.
    > kjournald starting. Commit interval 5 seconds
    > EXT3 FS on hda11, internal journal
    > EXT3-fs: mounted filesystem with ordered data mode.
    > kjournald starting. Commit interval 5 seconds
    > EXT3 FS on hda12, internal journal
    > EXT3-fs: mounted filesystem with ordered data mode.
    > ext3: No journal on filesystem on hdb1
    > ip_tables: (C) 2000-2006 Netfilter Core Team
    > Netfilter messages via NETLINK v0.30.
    > nf_conntrack version 0.5.0 (4089 buckets, 32712 max)
    > e100: eth0: e100_watchdog: link up, 100Mbps, full-duplex
    > NET: Registered protocol family 10
    > lo: Disabled Privacy Extensions
    > input: Power Button (FF) as /class/input/input3
    > ACPI: Power Button (FF) [PWRF]
    > input: Power Button (CM) as /class/input/input4
    > ACPI: Power Button (CM) [PWRB]
    > input: Sleep Button (CM) as /class/input/input5
    > ACPI: Sleep Button (CM) [SLPB]
    > eth0: no IPv6 routers present
    > vboxdrv: Trying to deactivate the NMI watchdog permanently...
    > vboxdrv: Successfully done.
    > vboxdrv: Found 1 processor cores.
    > vboxdrv: fAsync=0 u64DiffCores=1.
    > vboxdrv: TSC mode is 'synchronous', kernel timer mode is 'normal'.
    > vboxdrv: Successfully loaded version 1.6.4 (interface 0x00080000).
    > vmmon: module license 'unspecified' taints kernel.
    > [2923]: VMCI: Driver initialized.
    > [2923]: Module vmmon: registered with major=10 minor=165
    > [2923]: Module vmmon: initialized
    > /dev/vmnet: open called by PID 2952 (vmnet-bridge)
    > /dev/vmnet: hub 0 does not exist, allocating memory.
    > /dev/vmnet: port on hub 0 successfully opened
    > bridge-eth0: enabling the bridge
    > bridge-eth0: up
    > bridge-eth0: already up
    > bridge-eth0: attached
    > /dev/vmnet: open called by PID 2966 (vmnet-natd)
    > /dev/vmnet: hub 8 does not exist, allocating memory.
    > /dev/vmnet: port on hub 8 successfully opened
    > powernow-k8: Found 1 AMD Athlon(tm) 64 Processor 3200+ processors
    > (version 2.00.00)
    > powernow-k8: 0 : fid 0xe (2200 MHz), vid 0x2
    > powernow-k8: 1 : fid 0xc (2000 MHz), vid 0x6
    > powernow-k8: 2 : fid 0xa (1800 MHz), vid 0xa
    > powernow-k8: 3 : fid 0x2 (1000 MHz), vid 0x12
    > Marking TSC unstable due to: cpufreq changes.
    > Time: acpi_pm clocksource has been installed.
    > Clocksource tsc unstable (delta = -176950529 ns)
    > /dev/vmnet: open called by PID 3029 (vmnet-netifup)
    > /dev/vmnet: hub 1 does not exist, allocating memory.
    > /dev/vmnet: port on hub 1 successfully opened
    > /dev/vmnet: open called by PID 3030 (vmnet-netifup)
    > /dev/vmnet: port on hub 8 successfully opened
    > /dev/vmnet: open called by PID 3066 (vmnet-dhcpd)
    > /dev/vmnet: port on hub 1 successfully opened
    > /dev/vmnet: open called by PID 3047 (vmnet-dhcpd)
    > /dev/vmnet: port on hub 8 successfully opened
    > vmnet8: no IPv6 routers present
    > vmnet1: no IPv6 routers present
    > ext3: No journal on filesystem on hdb1
    > kjournald starting. Commit interval 5 seconds
    > EXT3 FS on hdb1, internal journal
    > EXT3-fs: mounted filesystem with ordered data mode.
    > hda: status error: status=0xd0 { Busy }
    > ide: failed opcode was: unknown
    > hda: DMA disabled
    > hdb: DMA disabled
    > hda: drive not ready for command
    > ide0: reset timed-out, status=0xd0
    > hda: lost interrupt
    > attempt to access beyond end of device
    > hda5: rw=0, want=8877388712, limit=29302497
    > attempt to access beyond end of device
    > hda5: rw=0, want=8877388712, limit=29302497
    > attempt to access beyond end of device
    > hda5: rw=0, want=8877388584, limit=29302497
    > attempt to access beyond end of device
    > hda5: rw=0, want=8885842944, limit=29302497
    > attempt to access beyond end of device
    > hda5: rw=0, want=8877388712, limit=29302497
    > hda: task_out_intr: status=0xd8 { Busy }
    > ide: failed opcode was: unknown
    > ide0: reset timed-out, status=0xd0
    > end_request: I/O error, dev hda, sector 2806748
    > Buffer I/O error on device hda5, logical block 278543
    > lost page write due to I/O error on hda5
    > end_request: I/O error, dev hda, sector 2806811
    > Buffer I/O error on device hda5, logical block 278551
    > lost page write due to I/O error on hda5
    > end_request: I/O error, dev hda, sector 2806835
    > Buffer I/O error on device hda5, logical block 278554
    > lost page write due to I/O error on hda5
    > end_request: I/O error, dev hda, sector 2806843
    > Buffer I/O error on device hda5, logical block 278555
    > lost page write due to I/O error on hda5
    > end_request: I/O error, dev hda, sector 2806851
    > Buffer I/O error on device hda5, logical block 278556
    > lost page write due to I/O error on hda5
    > end_request: I/O error, dev hda, sector 2806859
    > Buffer I/O error on device hda5, logical block 278557
    > lost page write due to I/O error on hda5
    > end_request: I/O error, dev hda, sector 2806867
    > Buffer I/O error on device hda5, logical block 278558
    > lost page write due to I/O error on hda5
    > end_request: I/O error, dev hda, sector 2806875
    > Buffer I/O error on device hda5, logical block 278559
    > lost page write due to I/O error on hda5
    > end_request: I/O error, dev hda, sector 2806883
    > Buffer I/O error on device hda5, logical block 278560
    > lost page write due to I/O error on hda5
    > end_request: I/O error, dev hda, sector 2806891
    > Buffer I/O error on device hda5, logical block 278561
    > lost page write due to I/O error on hda5
    > end_request: I/O error, dev hda, sector 2806899
    > end_request: I/O error, dev hda, sector 2806907
    > end_request: I/O error, dev hda, sector 2806915
    > end_request: I/O error, dev hda, sector 2806923
    > end_request: I/O error, dev hda, sector 2806931
    > end_request: I/O error, dev hda, sector 2806939
    > end_request: I/O error, dev hda, sector 2806947
    > end_request: I/O error, dev hda, sector 2806955
    > end_request: I/O error, dev hda, sector 2807011
    > end_request: I/O error, dev hda, sector 2807019
    > end_request: I/O error, dev hda, sector 2807027
    > end_request: I/O error, dev hda, sector 2807035
    > end_request: I/O error, dev hda, sector 2807043
    > end_request: I/O error, dev hda, sector 2807051
    > end_request: I/O error, dev hda, sector 2807059
    > end_request: I/O error, dev hda, sector 2807067
    > end_request: I/O error, dev hda, sector 2807075
    > end_request: I/O error, dev hda, sector 2807083
    > end_request: I/O error, dev hda, sector 2807091
    > end_request: I/O error, dev hda, sector 2807099
    > end_request: I/O error, dev hda, sector 2807107
    > end_request: I/O error, dev hda, sector 2807115
    > end_request: I/O error, dev hda, sector 2807123
    > end_request: I/O error, dev hda, sector 2807131
    > end_request: I/O error, dev hda, sector 2807139
    > end_request: I/O error, dev hda, sector 2807147
    > end_request: I/O error, dev hda, sector 2807155
    > end_request: I/O error, dev hda, sector 2807163
    > end_request: I/O error, dev hda, sector 2807171
    > end_request: I/O error, dev hda, sector 2807179
    > end_request: I/O error, dev hda, sector 2807187
    > end_request: I/O error, dev hda, sector 2807195
    > end_request: I/O error, dev hda, sector 2807203
    > end_request: I/O error, dev hda, sector 2807211
    > end_request: I/O error, dev hda, sector 2807219
    > end_request: I/O error, dev hda, sector 2807227
    > end_request: I/O error, dev hda, sector 2807235
    > end_request: I/O error, dev hda, sector 2807243
    > end_request: I/O error, dev hda, sector 2807251
    > end_request: I/O error, dev hda, sector 2807259
    > end_request: I/O error, dev hda, sector 2807267
    > end_request: I/O error, dev hda, sector 2807275
    > end_request: I/O error, dev hda, sector 2807283
    > end_request: I/O error, dev hda, sector 2807291
    > end_request: I/O error, dev hda, sector 2807299
    > end_request: I/O error, dev hda, sector 2807307
    > end_request: I/O error, dev hda, sector 2807315
    > end_request: I/O error, dev hda, sector 2807323
    > end_request: I/O error, dev hda, sector 2807331
    > end_request: I/O error, dev hda, sector 2807339
    > end_request: I/O error, dev hda, sector 2807795
    > end_request: I/O error, dev hda, sector 2825411
    > end_request: I/O error, dev hda, sector 2885699
    > end_request: I/O error, dev hda, sector 11893315
    > end_request: I/O error, dev hda, sector 19903083
    > end_request: I/O error, dev hda, sector 30929763
    > end_request: I/O error, dev hda, sector 31717203
    > end_request: I/O error, dev hda, sector 34075299
    > end_request: I/O error, dev hda, sector 34075443
    > end_request: I/O error, dev hda, sector 35911243
    > end_request: I/O error, dev hda, sector 35911851
    > end_request: I/O error, dev hda, sector 37483315
    > end_request: I/O error, dev hda, sector 39648483
    > end_request: I/O error, dev hda, sector 39648491
    > end_request: I/O error, dev hda, sector 40871067
    > end_request: I/O error, dev hda, sector 40873747
    > end_request: I/O error, dev hda, sector 40873867
    > end_request: I/O error, dev hda, sector 115275
    > end_request: I/O error, dev hda, sector 115279
    > end_request: I/O error, dev hda, sector 115281
    > end_request: I/O error, dev hda, sector 115283
    > end_request: I/O error, dev hda, sector 278745
    > end_request: I/O error, dev hda, sector 578403
    > end_request: I/O error, dev hda, sector 578411
    > end_request: I/O error, dev hda, sector 1102723
    > end_request: I/O error, dev hda, sector 1102747
    > end_request: I/O error, dev hda, sector 2675555
    > end_request: I/O error, dev hda, sector 2675563
    > end_request: I/O error, dev hda, sector 2675619
    > end_request: I/O error, dev hda, sector 2741115
    > end_request: I/O error, dev hda, sector 2741163
    > end_request: I/O error, dev hda, sector 2741171
    > end_request: I/O error, dev hda, sector 2741347
    > end_request: I/O error, dev hda, sector 2741459
    > end_request: I/O error, dev hda, sector 2741467
    > end_request: I/O error, dev hda, sector 2741475
    > end_request: I/O error, dev hda, sector 2741483
    > end_request: I/O error, dev hda, sector 2741491
    > end_request: I/O error, dev hda, sector 2741523
    > end_request: I/O error, dev hda, sector 2741603
    > end_request: I/O error, dev hda, sector 2741611
    > end_request: I/O error, dev hda, sector 2741771
    > end_request: I/O error, dev hda, sector 2741779
    > end_request: I/O error, dev hda, sector 2741915
    > end_request: I/O error, dev hda, sector 2741923
    > end_request: I/O error, dev hda, sector 2742067
    > end_request: I/O error, dev hda, sector 39976827
    > end_request: I/O error, dev hda, sector 39976875
    > end_request: I/O error, dev hda, sector 115287
    > end_request: I/O error, dev hda, sector 115297
    > end_request: I/O error, dev hda, sector 115299
    > end_request: I/O error, dev hda, sector 115303
    > end_request: I/O error, dev hda, sector 115305
    > end_request: I/O error, dev hda, sector 115307
    > end_request: I/O error, dev hda, sector 115309
    > end_request: I/O error, dev hda, sector 115311
    > end_request: I/O error, dev hda, sector 115317
    > end_request: I/O error, dev hda, sector 115319
    > end_request: I/O error, dev hda, sector 115321
    > end_request: I/O error, dev hda, sector 115323
    > end_request: I/O error, dev hda, sector 115325
    > end_request: I/O error, dev hda, sector 115327
    > end_request: I/O error, dev hda, sector 115349
    > end_request: I/O error, dev hda, sector 131191
    > end_request: I/O error, dev hda, sector 262213
    > end_request: I/O error, dev hda, sector 262215
    > end_request: I/O error, dev hda, sector 262221
    > end_request: I/O error, dev hda, sector 262223
    > end_request: I/O error, dev hda, sector 262449
    > end_request: I/O error, dev hda, sector 262565
    > end_request: I/O error, dev hda, sector 262585
    > end_request: I/O error, dev hda, sector 262609
    > end_request: I/O error, dev hda, sector 262679
    > Aborting journal on device hda7.
    > end_request: I/O error, dev hda, sector 39976875
    > end_request: I/O error, dev hda, sector 40871067
    > end_request: I/O error, dev hda, sector 40873747
    > end_request: I/O error, dev hda, sector 40873867
    > __journal_remove_journal_head: freeing b_frozen_data
    > __journal_remove_journal_head: freeing b_frozen_data
    > __journal_remove_journal_head: freeing b_frozen_data
    > Aborting journal on device hda5.
    > end_request: I/O error, dev hda, sector 2741115
    > end_request: I/O error, dev hda, sector 2741467
    > end_request: I/O error, dev hda, sector 2741915
    > end_request: I/O error, dev hda, sector 2806707
    > end_request: I/O error, dev hda, sector 2806843
    > end_request: I/O error, dev hda, sector 2806851
    > end_request: I/O error, dev hda, sector 2806859
    > end_request: I/O error, dev hda, sector 2806867
    > end_request: I/O error, dev hda, sector 2806947
    > end_request: I/O error, dev hda, sector 2807035
    > end_request: I/O error, dev hda, sector 2807043
    > end_request: I/O error, dev hda, sector 2807059
    > end_request: I/O error, dev hda, sector 2807067
    > end_request: I/O error, dev hda, sector 2807131
    > end_request: I/O error, dev hda, sector 2807147
    > end_request: I/O error, dev hda, sector 2741171
    > end_request: I/O error, dev hda, sector 2741347
    > end_request: I/O error, dev hda, sector 2741611
    > ext3_abort called.
    > EXT3-fs error (device hda7): ext3_journal_start_sb: Detected aborted journal
    > Remounting filesystem read-only
    > ext3_abort called.
    > EXT3-fs error (device hda5): ext3_journal_start_sb: Detected aborted journal
    > Remounting filesystem read-only
    > end_request: I/O error, dev hda, sector 1102763
    > EXT3-fs error (device hda5): ext3_get_inode_loc: unable to read inode
    > block - inode=32883, block=65545
    > end_request: I/O error, dev hda, sector 30929763
    > EXT3-fs error (device hda6): ext3_get_inode_loc: unable to read inode
    > block - inode=65052, block=131100
    > end_request: I/O error, dev hda, sector 29880963
    > printk: 145 messages suppressed.
    > Buffer I/O error on device hda6, logical block 0
    > lost page write due to I/O error on hda6
    > EXT3-fs error (device hda6) in ext3_reserve_inode_write: IO failure
    > end_request: I/O error, dev hda, sector 29880963
    > Buffer I/O error on device hda6, logical block 0
    > lost page write due to I/O error on hda6
    > end_request: I/O error, dev hda, sector 5379
    > end_request: I/O error, dev hda, sector 5381
    > end_request: I/O error, dev hda, sector 5383
    > Aborting journal on device hda1.
    > end_request: I/O error, dev hda, sector 2151299
    > EXT3-fs error (device hda5): ext3_get_inode_loc: unable to read inode
    > block - inode=98115, block=196612
    > ext3_abort called.
    > EXT3-fs error (device hda1): ext3_journal_start_sb: Detected aborted journal
    > Remounting filesystem read-only
    > end_request: I/O error, dev hda, sector 37483315
    > EXT3-fs error (device hda6): ext3_get_inode_loc: unable to read inode
    > block - inode=466454, block=950294
    > end_request: I/O error, dev hda, sector 29880963
    > printk: 1 messages suppressed.
    > Buffer I/O error on device hda6, logical block 0
    > lost page write due to I/O error on hda6
    > EXT3-fs error (device hda6) in ext3_reserve_inode_write: IO failure
    > end_request: I/O error, dev hda, sector 29880963
    > end_request: I/O error, dev hda, sector 1889155
    > EXT3-fs error (device hda5): ext3_get_inode_loc: unable to read inode
    > block - inode=81764, block=163844
    > end_request: I/O error, dev hda, sector 30929763
    > EXT3-fs error (device hda6): ext3_get_inode_loc: unable to read inode
    > block - inode=65052, block=131100
    > end_request: I/O error, dev hda, sector 29880963
    > EXT3-fs error (device hda6) in ext3_reserve_inode_write: IO failure
    > end_request: I/O error, dev hda, sector 29880963
    > end_request: I/O error, dev hda, sector 1102723
    > EXT3-fs error (device hda5): ext3_get_inode_loc: unable to read inode
    > block - inode=32712, block=65540
    > end_request: I/O error, dev hda, sector 6083459
    > EXT3-fs error (device hda5): ext3_get_inode_loc: unable to read inode
    > block - inode=343393, block=688132
    > end_request: I/O error, dev hda, sector 1102811
    > EXT3-fs error (device hda5): ext3_get_inode_loc: unable to read inode
    > block - inode=33086, block=65551
    > end_request: I/O error, dev hda, sector 1102811
    > EXT3-fs error (device hda5): ext3_get_inode_loc: unable to read inode
    > block - inode=33087, block=65551
    > end_request: I/O error, dev hda, sector 1102819
    > EXT3-fs error (device hda5): ext3_get_inode_loc: unable to read inode
    > block - inode=33112, block=65552
    > end_request: I/O error, dev hda, sector 7394579
    > EXT3-fs error (device hda5): ext3_get_inode_loc: unable to read inode
    > block - inode=426780, block=852022
    > end_request: I/O error, dev hda, sector 1103747
    > EXT3-fs error (device hda5): ext3_get_inode_loc: unable to read inode
    > block - inode=36808, block=65668
    > end_request: I/O error, dev hda, sector 6083523
    > EXT3-fs error (device hda5): ext3_get_inode_loc: unable to read inode
    > block - inode=343650, block=688140
    > end_request: I/O error, dev hda, sector 1102763
    > EXT3-fs error (device hda5): ext3_get_inode_loc: unable to read inode
    > block - inode=32894, block=65545
    > end_request: I/O error, dev hda, sector 1102723
    > EXT3-fs error (device hda5): ext3_get_inode_loc: unable to read inode
    > block - inode=32713, block=65540
    > end_request: I/O error, dev hda, sector 1102827
    > EXT3-fs error (device hda5): ext3_get_inode_loc: unable to read inode
    > block - inode=33125, block=65553
    > end_request: I/O error, dev hda, sector 3199875
    > EXT3-fs error (device hda5): ext3_get_inode_loc: unable to read inode
    > block - inode=163524, block=327684
    > end_request: I/O error, dev hda, sector 3462723
    > EXT3-fs error (device hda5): ext3_get_inode_loc: unable to read inode
    > block - inode=182707, block=360540
    > end_request: I/O error, dev hda, sector 29890819
    > Aborting journal on device hda6.
    > ext3_abort called.
    > EXT3-fs error (device hda6): ext3_journal_start_sb: Detected aborted journal
    > Remounting filesystem read-only
    > end_request: I/O error, dev hda, sector 40697075
    > printk: 4 messages suppressed.
    > Buffer I/O error on device hda7, logical block 131074
    > lost page write due to I/O error on hda7
    > end_request: I/O error, dev hda, sector 40697083
    > Buffer I/O error on device hda7, logical block 131075
    > lost page write due to I/O error on hda7
    > end_request: I/O error, dev hda, sector 40697091
    > Buffer I/O error on device hda7, logical block 131076
    > lost page write due to I/O error on hda7
    > end_request: I/O error, dev hda, sector 2675587
    > end_request: I/O error, dev hda, sector 2675595
    > end_request: I/O error, dev hda, sector 2675643
    > end_request: I/O error, dev hda, sector 2675651
    > end_request: I/O error, dev hda, sector 262603
    > printk: 4 messages suppressed.
    > Buffer I/O error on device hda1, logical block 131270
    > lost page write due to I/O error on hda1


    > I had to power off and on my PC (couldn't do a normal shutdown and the
    > reset button didn't work).



    > Things were calm for maybe 10 minutes, then again:
    > hdb: dma_timer_expiry: dma status == 0x61
    > hdb: DMA timeout error
    > hdb: dma timeout error: status=0x58 { DriveReady SeekComplete DataRequest }
    > ide: failed opcode was: unknown
    > hda: DMA disabled
    > hdb: DMA disabled
    > ide0: reset: success


    > I ran smartctl -a on both drives:
    > # smartctl -a /dev/hda
    > smartctl version 5.38 [i686-pc-linux-gnu] Copyright (C) 2002-8 Bruce Allen
    > Home page is http://smartmontools.sourceforge.net/


    > === START OF INFORMATION SECTION ===
    > Model Family: Seagate Barracuda 7200.7 and 7200.7 Plus family
    > Device Model: ST380011A
    > Serial Number: 4JV5P7LN
    > Firmware Version: 8.01
    > User Capacity: 80,026,361,856 bytes
    > Device is: In smartctl database [for details use: -P show]
    > ATA Version is: 6
    > ATA Standard is: ATA/ATAPI-6 T13 1410D revision 2
    > Local Time is: Tue Aug 12 22:15:59 2008 PDT
    > SMART support is: Available - device has SMART capability.
    > SMART support is: Enabled


    > === START OF READ SMART DATA SECTION ===
    > SMART overall-health self-assessment test result: PASSED


    > General SMART Values:
    > Offline data collection status: (0x82) Offline data collection activity
    > was completed without error.
    > Auto Offline Data Collection:
    > Enabled.
    > Self-test execution status: ( 0) The previous self-test routine
    > completed
    > without error or no self-test
    > has ever
    > been run.
    > Total time to complete Offline
    > data collection: ( 430) seconds.
    > Offline data collection
    > capabilities: (0x5b) SMART execute Offline immediate.
    > Auto Offline data collection
    > on/off support.
    > Suspend Offline collection upon new
    > command.
    > Offline surface scan supported.
    > Self-test supported.
    > No Conveyance Self-test supported.
    > Selective Self-test supported.
    > SMART capabilities: (0x0003) Saves SMART data before entering
    > power-saving mode.
    > Supports SMART auto save timer.
    > Error logging capability: (0x01) Error logging supported.
    > General Purpose Logging supported.
    > Short self-test routine
    > recommended polling time: ( 1) minutes.
    > Extended self-test routine
    > recommended polling time: ( 58) minutes.


    > SMART Attributes Data Structure revision number: 10
    > Vendor Specific SMART Attributes with Thresholds:
    > ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE
    > UPDATED WHEN_FAILED RAW_VALUE
    > 1 Raw_Read_Error_Rate 0x000f 060 057 006 Pre-fail
    > Always - 81109586
    > 3 Spin_Up_Time 0x0003 098 098 000 Pre-fail
    > Always - 0
    > 4 Start_Stop_Count 0x0032 100 100 020 Old_age
    > Always - 0
    > 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail
    > Always - 0
    > 7 Seek_Error_Rate 0x000f 082 060 030 Pre-fail
    > Always - 195706519
    > 9 Power_On_Hours 0x0032 075 075 000 Old_age
    > Always - 22212
    > 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail
    > Always - 0
    > 12 Power_Cycle_Count 0x0032 100 100 020 Old_age
    > Always - 120
    > 194 Temperature_Celsius 0x0022 032 048 000 Old_age Always
    > - 32
    > 195 Hardware_ECC_Recovered 0x001a 060 057 000 Old_age Always
    > - 81109586
    > 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always
    > - 0
    > 198 Offline_Uncorrectable 0x0010 100 100 000 Old_age
    > Offline - 0
    > 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always
    > - 0
    > 200 Multi_Zone_Error_Rate 0x0000 100 253 000 Old_age
    > Offline - 0
    > 202 TA_Increase_Count 0x0032 100 253 000 Old_age Always
    > - 0


    > SMART Error Log Version: 1
    > No Errors Logged


    > SMART Self-test log structure revision number 1
    > Num Test_Description Status Remaining
    > LifeTime(hours) LBA_of_first_error
    > # 1 Extended offline Completed without error 00% 18951
    > -
    > # 2 Extended offline Completed without error 00% 18674
    > -
    > # 3 Extended offline Completed without error 00% 15957
    > -
    > # 4 Extended offline Completed without error 00% 14448
    > -


    > SMART Selective self-test log data structure revision number 1
    > SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
    > 1 0 0 Not_testing
    > 2 0 0 Not_testing
    > 3 0 0 Not_testing
    > 4 0 0 Not_testing
    > 5 0 0 Not_testing
    > Selective self-test flags (0x0):
    > After scanning selected spans, do NOT read-scan remainder of disk.
    > If Selective self-test is pending on power-up, resume after 0 minute delay.


    > # smartctl -a /dev/hdb
    > smartctl version 5.38 [i686-pc-linux-gnu] Copyright (C) 2002-8 Bruce Allen
    > Home page is http://smartmontools.sourceforge.net/


    > === START OF INFORMATION SECTION ===
    > Device Model: QUANTUM FIREBALL EX6.4A
    > Serial Number: 376833611720
    > Firmware Version: A0A.0D00
    > User Capacity: 6,448,619,520 bytes
    > Device is: In smartctl database [for details use: -P show]
    > ATA Version is: 4
    > ATA Standard is: ATA/ATAPI-4 T13 1153D revision 15
    > Local Time is: Tue Aug 12 22:16:25 2008 PDT
    > SMART support is: Available - device has SMART capability.
    > SMART support is: Enabled


    > Error SMART Status command failed: Input/output error
    > A mandatory SMART command failed: exiting. To continue, add one or more
    > '-T permissive' options.


    > Then, my Linux pauses becuse hdb went funky. I rechecked my dmesg (might
    > old dupes from earlier):
    > hdb: dma_timer_expiry: dma status == 0x61
    > hdb: DMA timeout error
    > hdb: dma timeout error: status=0x58 { DriveReady SeekComplete DataRequest }
    > ide: failed opcode was: unknown
    > hda: DMA disabled
    > hdb: DMA disabled
    > ide0: reset: success
    > hdb: drive_cmd: status=0x7d { DriveReady DeviceFault SeekComplete
    > DataRequest CorrectedError Error }
    > hdb: drive_cmd: error=0x7d { DriveStatusError UncorrectableError
    > SectorIdNotFound AddrMarkNotFound }, LBAsect=226327933, sector=0
    > ide: failed opcode was: 0xb0
    > hdb: dma_timer_expiry: dma status == 0x61
    > hdb: DMA timeout error
    > hdb: dma timeout error: status=0x58 { DriveReady SeekComplete DataRequest }
    > ide: failed opcode was: unknown
    > hda: DMA disabled
    > hdb: DMA disabled
    > ide0: reset: success
    > hdb: dma_timer_expiry: dma status == 0x61
    > hdb: DMA timeout error
    > hdb: dma timeout error: status=0x58 { DriveReady SeekComplete DataRequest }
    > ide: failed opcode was: unknown
    > hda: DMA disabled
    > hdb: DMA disabled
    > ide0: reset: success
    > hdb: dma_timer_expiry: dma status == 0x41
    > hdb: DMA timeout error
    > hdb: dma timeout error: status=0x58 { DriveReady SeekComplete DataRequest }
    > ide: failed opcode was: unknown
    > hdb: DMA disabled
    > ide0: reset: success



    > # smartctl -a /dev/hdb
    > smartctl version 5.38 [i686-pc-linux-gnu] Copyright (C) 2002-8 Bruce Allen
    > Home page is http://smartmontools.sourceforge.net/


    > === START OF INFORMATION SECTION ===
    > Device Model: QUANTUM FIREBALL EX6.4A
    > Serial Number: 376833611720
    > Firmware Version: A0A.0D00
    > User Capacity: 6,448,619,520 bytes
    > Device is: In smartctl database [for details use: -P show]
    > ATA Version is: 4
    > ATA Standard is: ATA/ATAPI-4 T13 1153D revision 15
    > Local Time is: Tue Aug 12 22:19:21 2008 PDT
    > SMART support is: Available - device has SMART capability.
    > SMART support is: Enabled


    > === START OF READ SMART DATA SECTION ===
    > SMART overall-health self-assessment test result: PASSED


    > General SMART Values:
    > Offline data collection status: (0x82) Offline data collection activity
    > was completed without error.
    > Auto Offline Data Collection:
    > Enabled.
    > Total time to complete Offline
    > data collection: ( 1) seconds.
    > Offline data collection
    > capabilities: (0x03) SMART execute Offline immediate.
    > Auto Offline data collection
    > on/off support.
    > Suspend Offline collection upon new
    > command.
    > No Offline surface scan supported.
    > No Self-test supported.
    > No Conveyance Self-test supported.
    > No Selective Self-test supported.
    > SMART capabilities: (0x0003) Saves SMART data before entering
    > power-saving mode.
    > Supports SMART auto save timer.
    > Error logging capability: (0x00) Error logging NOT supported.
    > No General Purpose Logging support.


    > SMART Attributes Data Structure revision number: 7
    > Vendor Specific SMART Attributes with Thresholds:
    > ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE
    > UPDATED WHEN_FAILED RAW_VALUE
    > 1 Raw_Read_Error_Rate 0x0029 100 100 020 Pre-fail
    > Offline - 0
    > 3 Spin_Up_Time 0x0027 089 076 020 Pre-fail
    > Always - 1489
    > 4 Start_Stop_Count 0x0032 099 099 008 Old_age
    > Always - 1198
    > 5 Reallocated_Sector_Ct 0x0033 100 100 020 Pre-fail
    > Always - 0
    > 7 Seek_Error_Rate 0x000b 100 100 023 Pre-fail
    > Always - 0
    > 9 Power_On_Hours 0x0012 007 007 001 Old_age
    > Always - 61139
    > 11 Calibration_Retry_Count 0x0013 100 100 020 Pre-fail
    > Always - 0
    > 12 Power_Cycle_Count 0x0032 099 099 008 Old_age
    > Always - 1191
    > 13 Read_Soft_Error_Rate 0x000b 100 100 023 Pre-fail
    > Always - 0
    > 199 UDMA_CRC_Error_Count 0x001a 200 200 000 Old_age Always
    > - 0


    > Warning: device does not support Error Logging
    > SMART Error Log Version: 0
    > No Errors Logged


    > Warning: device does not support Self Test Logging
    > SMART Self-test log structure revision number 0
    > Warning: ATA Specification requires self-test log structure revision
    > number = 1
    > No self-tests have been logged. [To run self-tests, use: smartctl -t]



    > Device does not support Selective Self Tests/Logging



    > What's going on with my HDDs? I am not a hardware and Linux/Debian
    > expert. My hardware specifications can be found here:
    > http://alpha.zimage.com/~ant/antfarm.../computers.txt
    > (secondary/backup computer). For now, I am going to unmount /dev/hdb to
    > see if hdb is causing all this madness.


    > Thank you in advance.
    > --
    > /\___/\
    > / /\ /\ \ Phil/Ant @ http://antfarm.home.dhs.org (Personal Web Site)
    > | |o o| | Ant's Quality Foraged Links (AQFL): http://aqfl.net
    > \ _ / Remove ANT from e-mail address: philpi@earthlink.netANT
    > ( ) or ANTant@zimage.com
    > Ant is currently not listening to any songs on his home computer.


  8. Re: Bad disk controller? Dying HDD?

    On 8/13/2008 2:27 AM PT, Rod Speed typed:

    >>>> Hi. My old mini-tower PC's HDDs are acting crazy today. I came home
    >>>> and noticed my second drive wasn't there so I checked dmesg (deleted
    >>>> normal logs before hdb):

    >
    >>>> SMART Attributes Data Structure revision number: 7
    >>>> Vendor Specific SMART Attributes with Thresholds:
    >>>> ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE
    >>>> UPDATED WHEN_FAILED RAW_VALUE
    >>>> 1 Raw_Read_Error_Rate 0x0029 100 100 020 Pre-fail
    >>>> Offline - 0
    >>>> 3 Spin_Up_Time 0x0027 089 076 020 Pre-fail
    >>>> Always - 1489
    >>>> 4 Start_Stop_Count 0x0032 099 099 008 Old_age
    >>>> Always - 1198
    >>>> 5 Reallocated_Sector_Ct 0x0033 100 100 020 Pre-fail
    >>>> Always - 0
    >>>> 7 Seek_Error_Rate 0x000b 100 100 023 Pre-fail
    >>>> Always - 0
    >>>> 9 Power_On_Hours 0x0012 007 007 001 Old_age
    >>>> Always - 61139
    >>>> 11 Calibration_Retry_Count 0x0013 100 100 020 Pre-fail
    >>>> Always - 0
    >>>> 12 Power_Cycle_Count 0x0032 099 099 008 Old_age
    >>>> Always - 1191
    >>>> 13 Read_Soft_Error_Rate 0x000b 100 100 023 Pre-fail
    >>>> Always - 0
    >>>> 199 UDMA_CRC_Error_Count 0x001a 200 200 000 Old_age Always - 0 Warning: device does not support
    >>>> Error Logging
    >>>> SMART Error Log Version: 0
    >>>> No Errors Logged
    >>>>
    >>>> Warning: device does not support Self Test Logging
    >>>> SMART Self-test log structure revision number 0
    >>>> Warning: ATA Specification requires self-test log structure revision
    >>>> number = 1
    >>>> No self-tests have been logged. [To run self-tests, use: smartctl
    >>>> -t]
    >>>> Device does not support Selective Self Tests/Logging
    >>>> What's going on with my HDDs?
    >>> Something's died, Jim. You into necrophilia ?
    >>> P

    >>
    >>>> I am not a hardware and Linux/Debian expert. My hardware
    >>>> specifications can be found here:
    >>>> http://alpha.zimage.com/~ant/antfarm.../computers.txt
    >>>> (secondary/backup computer). For now, I am going to unmount
    >>>> /dev/hdb to see if hdb is causing all this madness.

    >
    >>> There's certainly quite a few bad sectors on that drive.

    >
    >> How can you tell?

    >
    > Thats the reallocated sector count in the SMART report.


    So I have 100 bad sectors? Am I reading that right?


    >> I am so used to chkdsk, scandisk, pretty images, etc.

    >
    > A Jap would at least have the decency to disembowel itself.
    >
    >>> That shouldnt have produced the errors with the other drive tho so something else has died too.

    >
    >> True. So far, unmounting hdb hasn't resulted any symptoms. However, I haven't done much on it since I went to eat
    >> dinner and do other things.


    >>> The system appears to be pretty comprehensively ****ed.

    >
    >>

    >
    >>> It would be worth trying a spare power supply, it might be something as basic as that.

    >
    >> OK, I will keep that in mind. My PSU in that box isn't that old. I had to replace it with a new one on 5/14/2007
    >> according to
    >> http://alpha.zimage.com/~ant/antfarm/about/toys.html: "Replaced the
    >> dead Antec PSU in Linux/Debian box with a Fortron FSP650-80GLC PSU
    >> (650 watts)."

    >
    >>> Worth checking for bad caps on the motherboard too. These are the
    >>> usually blue or black plastic covered post like things that stick up vertically from
    >>> the motherboard surface. The tops should be flat. If any have bulged
    >>> or have leaked, thats a bad cap and for someone like you the only
    >>> real fix is to replace the motherboard. May be better to just bin
    >>> the PC tho.

    >
    >> OK, I will check again. The last time I opened this PC was in late
    >> January 2008, and I had several kernel panics and PC lockups due to a
    >> bad 512 MB Kingston memory (took a day to figure that out). This could
    >> be related, but then I don't recall any funny odors, saw any coloring
    >> on hardwares, bad caps, etc. Even my computer friend who build
    >> computers looked and didn't see anything back then and told me it was
    >> bad RAM. Hmm.

    >
    >> Let's see how having hdb disabled go. hdb is mainly a storage and
    >> backup drive, and I already made a backup of it a few weeks ago (not
    >> much changed that I can recall).


    Still no problems yet overnight with hdb unmounted in Debian/Linux.
    --
    "... [Let us inquire] what glory there was in an omnipotent being
    torturing forever a puny little creature who could in no way defend
    himself? Would it be to the glory of a man to fry ants?" --Charlotte
    Perkins Gilman
    /\___/\
    / /\ /\ \ Phil/Ant @ http://antfarm.home.dhs.org (Personal Web Site)
    | |o o| | Ant's Quality Foraged Links (AQFL): http://aqfl.net
    \ _ / Remove ANT from e-mail address: philpi@earthlink.netANT
    ( ) or ANTant@zimage.com
    Ant is currently not listening to any songs on his home computer.

  9. Re: Bad disk controller? Dying HDD?

    On 8/13/2008 2:34 AM PT, Arno Wagner typed:

    > In comp.sys.ibm.pc.hardware.storage Ant wrote:
    >> Hi. My old mini-tower PC's HDDs are acting crazy today. I came home and
    >> noticed my second drive wasn't there so I checked dmesg (deleted normal
    >> logs before hdb):

    >
    > From the SMART status, the Seagate (first drive) has read and
    > seek errors, that could well be connected. The Quantum looks
    > fine in SMART, but it is older (i.e. less reliable SMART
    > implementation) and has nasty SectorIDNotFound errors in the
    > log.


    Thanks for the clarifications.


    > So, what is going on indeed. I think either hdb is dying
    > and messing with the bus as it does so, or you have a different
    > problem. Attributes 1 and 7 on hda do not look good either.
    > The errors in the log for hda could indeed be a controller
    > issue, but nether could the errors for hdb or the SMART
    > attributes 1 and 7 for hda. I would suspect that your PSU is
    > going south and that unlean power is causing the problem.


    Darn it, this Fortron FSP650-80GLC PSU (650 watts) isn't not that old
    either. Grr.

    So far, no errors overnight after unmounting hdb overnight...
    --
    "May 10,000 ants never invade your underwear drawer." --unknown
    /\___/\
    / /\ /\ \ Phil/Ant @ http://antfarm.home.dhs.org (Personal Web Site)
    | |o o| | Ant's Quality Foraged Links (AQFL): http://aqfl.net
    \ _ / Remove ANT from e-mail address: philpi@earthlink.netANT
    ( ) or ANTant@zimage.com
    Ant is currently not listening to any songs on his home computer.

  10. Re: Bad disk controller? Dying HDD?

    On Wed, 13 Aug 2008 13:57:01 UTC in comp.os.linux.hardware, Ant
    wrote:

    > Darn it, this Fortron FSP650-80GLC PSU (650 watts) isn't not that old
    > either. Grr.


    I've never heard of Fortron but that doesn't mean that they aren't any good.
    What I have seen before is IDE devices on the same cable interfering with each
    other when one of them is going south. You could try removing the 2nd device
    from the primary cable and attaching it to another one (if there is one) and see
    if that eliminates the errors on one or both of the drives.

    --
    Trevor Hemsley, Brighton, UK
    Trevor dot Hemsley at ntlworld dot com

  11. Re: Bad disk controller? Dying HDD?

    Ant wrote:
    > On 8/13/2008 2:27 AM PT, Rod Speed typed:
    >
    >>>>> Hi. My old mini-tower PC's HDDs are acting crazy today. I came home and noticed my second drive wasn't there so I
    >>>>> checked dmesg (deleted normal logs before hdb):


    >>>>> SMART Attributes Data Structure revision number: 7
    >>>>> Vendor Specific SMART Attributes with Thresholds:
    >>>>> ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE
    >>>>> UPDATED WHEN_FAILED RAW_VALUE
    >>>>> 1 Raw_Read_Error_Rate 0x0029 100 100 020 Pre-fail
    >>>>> Offline - 0
    >>>>> 3 Spin_Up_Time 0x0027 089 076 020 Pre-fail
    >>>>> Always - 1489
    >>>>> 4 Start_Stop_Count 0x0032 099 099 008 Old_age
    >>>>> Always - 1198
    >>>>> 5 Reallocated_Sector_Ct 0x0033 100 100 020 Pre-fail
    >>>>> Always - 0
    >>>>> 7 Seek_Error_Rate 0x000b 100 100 023 Pre-fail
    >>>>> Always - 0
    >>>>> 9 Power_On_Hours 0x0012 007 007 001 Old_age
    >>>>> Always - 61139
    >>>>> 11 Calibration_Retry_Count 0x0013 100 100 020 Pre-fail
    >>>>> Always - 0
    >>>>> 12 Power_Cycle_Count 0x0032 099 099 008 Old_age
    >>>>> Always - 1191
    >>>>> 13 Read_Soft_Error_Rate 0x000b 100 100 023 Pre-fail
    >>>>> Always - 0
    >>>>> 199 UDMA_CRC_Error_Count 0x001a 200 200 000 Old_age
    >>>>> Always - 0 Warning: device does not support Error Logging
    >>>>> SMART Error Log Version: 0
    >>>>> No Errors Logged
    >>>>>
    >>>>> Warning: device does not support Self Test Logging
    >>>>> SMART Self-test log structure revision number 0
    >>>>> Warning: ATA Specification requires self-test log structure
    >>>>> revision number = 1
    >>>>> No self-tests have been logged. [To run self-tests, use: smartctl
    >>>>> -t]
    >>>>> Device does not support Selective Self Tests/Logging
    >>>>> What's going on with my HDDs?
    >>>> Something's died, Jim. You into necrophilia ?
    >>>> P
    >>>
    >>>>> I am not a hardware and Linux/Debian expert. My hardware
    >>>>> specifications can be found here:
    >>>>> http://alpha.zimage.com/~ant/antfarm.../computers.txt
    >>>>> (secondary/backup computer). For now, I am going to unmount
    >>>>> /dev/hdb to see if hdb is causing all this madness.


    >>>> There's certainly quite a few bad sectors on that drive.


    >>> How can you tell?


    >> Thats the reallocated sector count in the SMART report.


    > So I have 100 bad sectors? Am I reading that right?


    No, 20, the last number, the raw value. Still very high.

    >>> I am so used to chkdsk, scandisk, pretty images, etc.


    >> A Jap would at least have the decency to disembowel itself.


    >>>> That shouldnt have produced the errors with the other drive tho so
    >>>> something else has died too.


    >>> True. So far, unmounting hdb hasn't resulted any symptoms. However,
    >>> I haven't done much on it since I went to eat dinner and do other
    >>> things.

    >
    >>>> The system appears to be pretty comprehensively ****ed.

    >>
    >>>

    >>
    >>>> It would be worth trying a spare power supply, it might be
    >>>> something as basic as that.

    >>
    >>> OK, I will keep that in mind. My PSU in that box isn't that old. I
    >>> had to replace it with a new one on 5/14/2007 according to
    >>> http://alpha.zimage.com/~ant/antfarm/about/toys.html: "Replaced the
    >>> dead Antec PSU in Linux/Debian box with a Fortron FSP650-80GLC PSU
    >>> (650 watts)."

    >>
    >>>> Worth checking for bad caps on the motherboard too. These are the
    >>>> usually blue or black plastic covered post like things that stick
    >>>> up vertically from the motherboard surface. The tops should be flat. If any have
    >>>> bulged or have leaked, thats a bad cap and for someone like you the only
    >>>> real fix is to replace the motherboard. May be better to just bin
    >>>> the PC tho.

    >>
    >>> OK, I will check again. The last time I opened this PC was in late
    >>> January 2008, and I had several kernel panics and PC lockups due to
    >>> a bad 512 MB Kingston memory (took a day to figure that out). This
    >>> could be related, but then I don't recall any funny odors, saw any
    >>> coloring on hardwares, bad caps, etc. Even my computer friend who build
    >>> computers looked and didn't see anything back then and told me it
    >>> was bad RAM. Hmm.

    >>
    >>> Let's see how having hdb disabled go. hdb is mainly a storage and
    >>> backup drive, and I already made a backup of it a few weeks ago (not
    >>> much changed that I can recall).


    > Still no problems yet overnight with hdb unmounted in Debian/Linux.


    Thats more likely to be due to an intermittent fault unless debian is so
    ****ed that it cant report which hd* has a problem with some bad sectors.



  12. Re: Bad disk controller? Dying HDD?

    Rod Speed wrote in news:6ggljiFfu426U1@mid.individual.net
    > Ant wrote:
    > > On 8/13/2008 2:27 AM PT, Rod Speed typed:
    > >
    > > > > > > Hi. My old mini-tower PC's HDDs are acting crazy today. I came home and noticed my second drive wasn't there so I
    > > > > > > checked dmesg (deleted normal logs before hdb):

    >
    > > > > > > SMART Attributes Data Structure revision number: 7
    > > > > > > Vendor Specific SMART Attributes with Thresholds:
    > > > > > > ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE
    > > > > > > UPDATED WHEN_FAILED RAW_VALUE
    > > > > > > 1 Raw_Read_Error_Rate 0x0029 100 100 020 Pre-fail
    > > > > > > Offline - 0
    > > > > > > 3 Spin_Up_Time 0x0027 089 076 020 Pre-fail
    > > > > > > Always - 1489
    > > > > > > 4 Start_Stop_Count 0x0032 099 099 008 Old_age
    > > > > > > Always - 1198
    > > > > > > 5 Reallocated_Sector_Ct 0x0033 100 100 020 Pre-fail
    > > > > > > Always - 0
    > > > > > > 7 Seek_Error_Rate 0x000b 100 100 023 Pre-fail
    > > > > > > Always - 0
    > > > > > > 9 Power_On_Hours 0x0012 007 007 001 Old_age
    > > > > > > Always - 61139
    > > > > > > 11 Calibration_Retry_Count 0x0013 100 100 020 Pre-fail
    > > > > > > Always - 0
    > > > > > > 12 Power_Cycle_Count 0x0032 099 099 008 Old_age
    > > > > > > Always - 1191
    > > > > > > 13 Read_Soft_Error_Rate 0x000b 100 100 023 Pre-fail
    > > > > > > Always - 0
    > > > > > > 199 UDMA_CRC_Error_Count 0x001a 200 200 000 Old_age
    > > > > > > Always - 0 Warning: device does not support Error Logging
    > > > > > > SMART Error Log Version: 0
    > > > > > > No Errors Logged
    > > > > > >
    > > > > > > Warning: device does not support Self Test Logging
    > > > > > > SMART Self-test log structure revision number 0
    > > > > > > Warning: ATA Specification requires self-test log structure
    > > > > > > revision number = 1
    > > > > > > No self-tests have been logged. [To run self-tests, use: smartctl
    > > > > > > -t]
    > > > > > > Device does not support Selective Self Tests/Logging
    > > > > > > What's going on with my HDDs?
    > > > > > Something's died, Jim. You into necrophilia ?
    > > > > > P
    > > > >
    > > > > > > I am not a hardware and Linux/Debian expert. My hardware
    > > > > > > specifications can be found here:
    > > > > > > http://alpha.zimage.com/~ant/antfarm.../computers.txt
    > > > > > > (secondary/backup computer). For now, I am going to unmount
    > > > > > > /dev/hdb to see if hdb is causing all this madness.

    >
    > > > > > There's certainly quite a few bad sectors on that drive.

    >
    > > > > How can you tell?

    >
    > > > Thats the reallocated sector count in the SMART report.

    >
    > > So I have 100 bad sectors? Am I reading that right?

    >
    > No, 20,


    > the last number,


    The one at the end of the line, how difficult can it be, right.
    Unless you're obviously braindead, of course.

    > the raw value.


    > Still very high.


    Yep.

    >
    > > > > I am so used to chkdsk, scandisk, pretty images, etc.

    >
    > > > A Jap would at least have the decency to disembowel itself.

    >
    > > > > > That shouldnt have produced the errors with the other drive tho so
    > > > > > something else has died too.

    >
    > > > > True. So far, unmounting hdb hasn't resulted any symptoms. However,
    > > > > I haven't done much on it since I went to eat dinner and do other
    > > > > things.

    > >
    > > > > > The system appears to be pretty comprehensively ****ed.
    > > >
    > > > >
    > > >
    > > > > > It would be worth trying a spare power supply, it might be
    > > > > > something as basic as that.
    > > >
    > > > > OK, I will keep that in mind. My PSU in that box isn't that old. I
    > > > > had to replace it with a new one on 5/14/2007 according to
    > > > > http://alpha.zimage.com/~ant/antfarm/about/toys.html: "Replaced the
    > > > > dead Antec PSU in Linux/Debian box with a Fortron FSP650-80GLC PSU
    > > > > (650 watts)."
    > > >
    > > > > > Worth checking for bad caps on the motherboard too. These are the
    > > > > > usually blue or black plastic covered post like things that stick
    > > > > > up vertically from the motherboard surface. The tops should be flat. If any have
    > > > > > bulged or have leaked, thats a bad cap and for someone like you the only
    > > > > > real fix is to replace the motherboard. May be better to just bin
    > > > > > the PC tho.
    > > >
    > > > > OK, I will check again. The last time I opened this PC was in late
    > > > > January 2008, and I had several kernel panics and PC lockups due to
    > > > > a bad 512 MB Kingston memory (took a day to figure that out). This
    > > > > could be related, but then I don't recall any funny odors, saw any
    > > > > coloring on hardwares, bad caps, etc. Even my computer friend who build
    > > > > computers looked and didn't see anything back then and told me it
    > > > > was bad RAM. Hmm.
    > > >
    > > > > Let's see how having hdb disabled go. hdb is mainly a storage and
    > > > > backup drive, and I already made a backup of it a few weeks ago (not
    > > > > much changed that I can recall).

    >
    > > Still no problems yet overnight with hdb unmounted in Debian/Linux.

    >
    > Thats more likely to be due to an intermittent fault unless debian is so
    > ****ed that it cant report which hd* has a problem with some bad sectors.


  13. Re: Bad disk controller? Dying HDD?

    > >>>>> Hi. My old mini-tower PC's HDDs are acting crazy today. I came home and noticed my second drive wasn't there so I
    > >>>>> checked dmesg (deleted normal logs before hdb):


    > >>>>> SMART Attributes Data Structure revision number: 7
    > >>>>> Vendor Specific SMART Attributes with Thresholds:
    > >>>>> ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE
    > >>>>> UPDATED WHEN_FAILED RAW_VALUE
    > >>>>> 1 Raw_Read_Error_Rate 0x0029 100 100 020 Pre-fail
    > >>>>> Offline - 0
    > >>>>> 3 Spin_Up_Time 0x0027 089 076 020 Pre-fail
    > >>>>> Always - 1489
    > >>>>> 4 Start_Stop_Count 0x0032 099 099 008 Old_age
    > >>>>> Always - 1198
    > >>>>> 5 Reallocated_Sector_Ct 0x0033 100 100 020 Pre-fail
    > >>>>> Always - 0
    > >>>>> 7 Seek_Error_Rate 0x000b 100 100 023 Pre-fail
    > >>>>> Always - 0
    > >>>>> 9 Power_On_Hours 0x0012 007 007 001 Old_age
    > >>>>> Always - 61139
    > >>>>> 11 Calibration_Retry_Count 0x0013 100 100 020 Pre-fail
    > >>>>> Always - 0
    > >>>>> 12 Power_Cycle_Count 0x0032 099 099 008 Old_age
    > >>>>> Always - 1191
    > >>>>> 13 Read_Soft_Error_Rate 0x000b 100 100 023 Pre-fail
    > >>>>> Always - 0
    > >>>>> 199 UDMA_CRC_Error_Count 0x001a 200 200 000 Old_age
    > >>>>> Always - 0 Warning: device does not support Error Logging
    > >>>>> SMART Error Log Version: 0
    > >>>>> No Errors Logged
    > >>>>>
    > >>>>> Warning: device does not support Self Test Logging
    > >>>>> SMART Self-test log structure revision number 0
    > >>>>> Warning: ATA Specification requires self-test log structure
    > >>>>> revision number = 1
    > >>>>> No self-tests have been logged. [To run self-tests, use: smartctl
    > >>>>> -t]
    > >>>>> Device does not support Selective Self Tests/Logging
    > >>>>> What's going on with my HDDs?
    > >>>> Something's died, Jim. You into necrophilia ?
    > >>>> P
    > >>>
    > >>>>> I am not a hardware and Linux/Debian expert. My hardware
    > >>>>> specifications can be found here:
    > >>>>> http://alpha.zimage.com/~ant/antfarm.../computers.txt
    > >>>>> (secondary/backup computer). For now, I am going to unmount
    > >>>>> /dev/hdb to see if hdb is causing all this madness.


    > >>>> There's certainly quite a few bad sectors on that drive.


    > >>> How can you tell?


    > >> Thats the reallocated sector count in the SMART report.


    > > So I have 100 bad sectors? Am I reading that right?


    > No, 20, the last number, the raw value. Still very high.


    Can you please kindly explain what these raw values mean? Are those 20
    bad sectors or something else?


    > >>> I am so used to chkdsk, scandisk, pretty images, etc.


    > >> A Jap would at least have the decency to disembowel itself.


    > >>>> That shouldnt have produced the errors with the other drive tho so
    > >>>> something else has died too.


    > >>> True. So far, unmounting hdb hasn't resulted any symptoms. However,
    > >>> I haven't done much on it since I went to eat dinner and do other
    > >>> things.

    > >
    > >>>> The system appears to be pretty comprehensively ****ed.
    > >>
    > >>>
    > >>
    > >>>> It would be worth trying a spare power supply, it might be
    > >>>> something as basic as that.
    > >>
    > >>> OK, I will keep that in mind. My PSU in that box isn't that old. I
    > >>> had to replace it with a new one on 5/14/2007 according to
    > >>> http://alpha.zimage.com/~ant/antfarm/about/toys.html: "Replaced the
    > >>> dead Antec PSU in Linux/Debian box with a Fortron FSP650-80GLC PSU
    > >>> (650 watts)."
    > >>
    > >>>> Worth checking for bad caps on the motherboard too. These are the
    > >>>> usually blue or black plastic covered post like things that stick
    > >>>> up vertically from the motherboard surface. The tops should be flat. If any have
    > >>>> bulged or have leaked, thats a bad cap and for someone like you the only
    > >>>> real fix is to replace the motherboard. May be better to just bin
    > >>>> the PC tho.
    > >>
    > >>> OK, I will check again. The last time I opened this PC was in late
    > >>> January 2008, and I had several kernel panics and PC lockups due to
    > >>> a bad 512 MB Kingston memory (took a day to figure that out). This
    > >>> could be related, but then I don't recall any funny odors, saw any
    > >>> coloring on hardwares, bad caps, etc. Even my computer friend who build
    > >>> computers looked and didn't see anything back then and told me it
    > >>> was bad RAM. Hmm.
    > >>
    > >>> Let's see how having hdb disabled go. hdb is mainly a storage and
    > >>> backup drive, and I already made a backup of it a few weeks ago (not
    > >>> much changed that I can recall).


    > > Still no problems yet overnight with hdb unmounted in Debian/Linux.


    > Thats more likely to be due to an intermittent fault unless debian is so
    > ****ed that it cant report which hd* has a problem with some bad sectors.


    Oh look, I found something new in my recent dmesg (wished it had dates
    and time stamps) showed even with unmounted hdb drive even though my PC
    isn't pausing from what I can tell remotely (ssh since I am at work):
    hdb: drive_cmd: status=0x7d { DriveReady DeviceFault SeekComplete
    DataRequest CorrectedError Error }
    hdb: drive_cmd: error=0x7d { DriveStatusError UncorrectableError SectorIdNotFound AddrMarkNotFound }, LBAsect=226327933, sector=0
    ide: failed opcode was: 0xb0
    hdb: status error: status=0x7d { DriveReady DeviceFault SeekComplete DataRequest CorrectedError Error }
    hdb: status error: error=0x7d { DriveStatusError UncorrectableError SectorIdNotFound AddrMarkNotFound }, LBAsect=226327933, sector=0
    ide: failed opcode was: 0xb0
    hdb: drive not ready for command

    Nothing for hda (good). If this gets a lot worse, I am going to shutdown
    the PC.


    I have a question, where do smartctl's test results go? I have never
    seen any results from them in the past, including dmesg:

    # smartctl -t long /dev/hdb
    smartctl version 5.38 [i686-pc-linux-gnu] Copyright (C) 2002-8 Bruce
    Allen
    Home page is http://smartmontools.sourceforge.net/

    === START OF OFFLINE IMMEDIATE AND SELF-TEST SECTION ===
    Warning: device does not support Self-Test functions.

    Sending command: "Execute SMART Extended self-test routine immediately
    in off-line mode".
    Drive command "Execute SMART Extended self-test routine immediately in
    off-line mode" successful.
    Testing has begun.


    According to man, it says it can take 10+ minutes but I see nothing.
    --
    "She's got ants in her pants." --unknown
    /\___/\
    / /\ /\ \ Ant @ http://antfarm.home.dhs.org (Personal Web Site)
    | |o o| | Ant's Quality Foraged Links (AQFL): http://aqfl.net
    \ _ / Please remove ANT if replying by e-mail.
    ( )

  14. Re: Bad disk controller? Dying HDD?

    In comp.sys.ibm.pc.hardware.storage Trevor Hemsley wrote:
    > On Wed, 13 Aug 2008 13:57:01 UTC in comp.os.linux.hardware, Ant
    > wrote:


    > > Darn it, this Fortron FSP650-80GLC PSU (650 watts) isn't not that old
    > > either. Grr.


    > I've never heard of Fortron but that doesn't mean that they aren't any good.
    > What I have seen before is IDE devices on the same cable interfering with each
    > other when one of them is going south. You could try removing the 2nd device
    > from the primary cable and attaching it to another one (if there is one) and see
    > if that eliminates the errors on one or both of the drives.


    Is unmounting hdb via umount command valid?
    --
    "She's got ants in her pants." --unknown
    /\___/\
    / /\ /\ \ Ant @ http://antfarm.home.dhs.org (Personal Web Site)
    | |o o| | Ant's Quality Foraged Links (AQFL): http://aqfl.net
    \ _ / Please remove ANT if replying by e-mail.
    ( )

  15. Re: Bad disk controller? Dying HDD?

    Some aussie moron just copied 75kB of ****e.

    "Rod Speed" wrote in message news:6gfc2pFfhd3iU1@mid.individual.net...
    > Ant wrote:
    > > Hi. My old mini-tower PC's HDDs are acting crazy today. I came home
    > > and noticed my second drive wasn't there so I checked dmesg (deleted
    > > normal logs before hdb):
    > >

    [snip]
    > I ran smartctl -a on both drives:
    > > # smartctl -a /dev/hda
    > > smartctl version 5.38 [i686-pc-linux-gnu] Copyright (C) 2002-8 Bruce
    > > Allen Home page is http://smartmontools.sourceforge.net/
    > >
    > > === START OF INFORMATION SECTION ===
    > > Model Family: Seagate Barracuda 7200.7 and 7200.7 Plus family
    > > Device Model: ST380011A
    > > Serial Number: 4JV5P7LN
    > > Firmware Version: 8.01
    > > User Capacity: 80,026,361,856 bytes
    > > Device is: In smartctl database [for details use: -P show]
    > > ATA Version is: 6
    > > ATA Standard is: ATA/ATAPI-6 T13 1410D revision 2
    > > Local Time is: Tue Aug 12 22:15:59 2008 PDT
    > > SMART support is: Available - device has SMART capability.
    > > SMART support is: Enabled
    > >
    > > === START OF READ SMART DATA SECTION ===
    > > SMART overall-health self-assessment test result: PASSED
    > >
    > > General SMART Values:
    > > Offline data collection status: (0x82) Offline data collection activity was completed
    > > without error.
    > > Auto Offline Data Collection: Enabled.
    > > Self-test execution status: ( 0) The previous self-test routine completed without
    > > error or no self-test has ever been run.
    > > Total time to complete Offline ata collection: ( 430) seconds.
    > > Offline data collection capabilities: (0x5b) SMART execute Offline immediate.
    > > Auto Offline data collection on/off support.
    > > Suspend Offline collection upon new command.
    > > Offline surface scan supported.
    > > Self-test supported.
    > > No Conveyance Self-test supported.
    > > Selective Self-test supported.
    > > SMART capabilities: (0x0003) Saves SMART data before entering power-saving mode.
    > > Supports SMART auto save timer.
    > > Error logging capability: (0x01) Error logging supported.
    > > General Purpose Logging supported.
    > > Short self-test routine recommended polling time: ( 1) minutes.
    > > Extended self-test routine recommended polling time: ( 58) minutes.
    > >
    > > SMART Attributes Data Structure revision number: 10
    > > Vendor Specific SMART Attributes with Thresholds:
    > > ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
    > > 1 Raw_Read_Error_Rate 0x000f 060 057 006 Pre-fail Always - 81109586
    > > 3 Spin_Up_Time 0x0003 098 098 000 Pre-fail Always - 0
    > > 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 0
    > > 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 0
    > > 7 Seek_Error_Rate 0x000f 082 060 030 Pre-fail Always - 195706519
    > > 9 Power_On_Hours 0x0032 075 075 000 Old_age Always - 22212
    > > 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0
    > > 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 120
    > > 194 Temperature_Celsius 0x0022 032 048 000 Old_age Always - 32
    > > 195 Hardware_ECC_Recovered 0x001a 060 057 000 Old_age Always - 81109586
    > > 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0
    > > 198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0
    > > 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0
    > > 200 Multi_Zone_Error_Rate 0x0000 100 253 000 Old_age Offline - 0
    > > 202 TA_Increase_Count 0x0032 100 253 000 Old_age Always - 0
    > >

    [snip]
    > >
    > >
    > > # smartctl -a /dev/hdb
    > > smartctl version 5.38 [i686-pc-linux-gnu] Copyright (C) 2002-8 Bruce
    > > Allen Home page is http://smartmontools.sourceforge.net/
    > >
    > > === START OF INFORMATION SECTION ===
    > > Device Model: QUANTUM FIREBALL EX6.4A
    > > Serial Number: 376833611720
    > > Firmware Version: A0A.0D00
    > > User Capacity: 6,448,619,520 bytes
    > > Device is: In smartctl database [for details use: -P show]
    > > ATA Version is: 4
    > > ATA Standard is: ATA/ATAPI-4 T13 1153D revision 15
    > > Local Time is: Tue Aug 12 22:19:21 2008 PDT
    > > SMART support is: Available - device has SMART capability.
    > > SMART support is: Enabled
    > >
    > > === START OF READ SMART DATA SECTION ===
    > > SMART overall-health self-assessment test result: PASSED
    > >
    > > General SMART Values:
    > > Offline data collection status: (0x82) Offline data collection activity was completed without error.
    > > Auto Offline Data Collection: Enabled.
    > > Total time to complete Offline data collection: ( 1) seconds.
    > > Offline data collection capabilities: (0x03) SMART execute Offline immediate.
    > > Auto Offline data collection on/off support.
    > > Suspend Offline collection upon new command.
    > > No Offline surface scan supported.
    > > No Self-test supported.
    > > No Conveyance Self-test supported.
    > > No Selective Self-test supported.
    > > SMART capabilities: (0x0003) Saves SMART data before entering power-saving mode.
    > > Supports SMART auto save timer.
    > > Error logging capability: (0x00) Error logging NOT supported.
    > > No General Purpose Logging support.
    > > SMART Attributes Data Structure revision number: 7
    > > Vendor Specific SMART Attributes with Thresholds:
    > > ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
    > > 1 Raw_Read_Error_Rate 0x0029 100 100 020 Pre-fail Offline - 0
    > > 3 Spin_Up_Time 0x0027 089 076 020 Pre-fail Always - 1489
    > > 4 Start_Stop_Count 0x0032 099 099 008 Old_age Always - 1198
    > > 5 Reallocated_Sector_Ct 0x0033 100 100 020 Pre-fail Always - 0
    > > 7 Seek_Error_Rate 0x000b 100 100 023 Pre-fail Always - 0
    > > 9 Power_On_Hours 0x0012 007 007 001 Old_age Always - 61139
    > > 11 Calibration_Retry_Count 0x0013 100 100 020 Pre-fail Always - 0
    > > 12 Power_Cycle_Count 0x0032 099 099 008 Old_age Always - 1191
    > > 13 Read_Soft_Error_Rate 0x000b 100 100 023 Pre-fail Always - 0
    > > 199 UDMA_CRC_Error_Count 0x001a 200 200 000 Old_age Always - 0
    > >
    > > Warning: device does not support Error Logging
    > > SMART Error Log Version: 0
    > > No Errors Logged
    > >
    > > Warning: device does not support Self Test Logging
    > > SMART Self-test log structure revision number 0
    > > Warning: ATA Specification requires self-test log structure revision
    > > number = 1
    > > No self-tests have been logged. [To run self-tests, use: smartctl -t]

    >
    > > Device does not support Selective Self Tests/Logging

    >
    > > What's going on with my HDDs?

    >
    > Something's died, Jim. You into necrophilia ?
    >
    > > I am not a hardware and Linux/Debian expert. My hardware specifications can be found here:
    > > http://alpha.zimage.com/~ant/antfarm.../computers.txt
    > > (secondary/backup computer). For now, I am going to unmount /dev/hdb to see if hdb is causing all this madness.

    >
    > There's certainly quite a few bad sectors on that drive.


    Yep, there certainly are. Those zero numbers are certainly impressive.

    >
    > That shouldnt have produced the errors with the other drive tho so something else has died too.


    Yeah, that something, could that be your brains, Roddy.

    >
    > The system appears to be pretty comprehensively ****ed.


    Yep, zero reallocated sectors, very very bad.

    >
    > It would be worth trying a spare power supply, it might be something as basic as that.
    >
    > Worth checking for bad caps on the motherboard too. These are the usually blue or
    > black plastic covered post like things that stick up vertically from the motherboard surface.
    > The tops should be flat. If any have bulged or have leaked, thats a bad cap and for someone
    > like you the only real fix is to replace the motherboard. May be better to just bin the PC tho.


    If only we could bin you, Roddy boy.

  16. Re: Bad disk controller? Dying HDD?

    Another moron that copied 75kB of ****e.

    Arno Wagner wrote in news:6gfo4tFfjlgbU1@mid.individual.net
    > In comp.sys.ibm.pc.hardware.storage Ant wrote:
    > > Hi. My old mini-tower PC's HDDs are acting crazy today. I came home and
    > > noticed my second drive wasn't there so I checked dmesg (deleted normal
    > > logs before hdb):


    > From the SMART status, the Seagate (first drive) has read and seek errors,


    As does every Seagate.

    > that could well be connected. The Quantum looks fine in SMART,


    > but it is older (i.e. less reliable SMART implementation)


    Utter nonsense.

    > and has nasty SectorIDNotFound errors in the log.


    That's a little bit more of a concern.

    >
    > So, what is going on indeed. I think either hdb is dying
    > and messing with the bus as it does so, or you have a different
    > problem. Attributes 1 and 7 on hda do not look good either.
    > The errors in the log for hda could indeed be a controller
    > issue, but nether could the errors for hdb or the SMART
    > attributes 1 and 7 for hda. I would suspect that your PSU is
    > going south and that unlean power is causing the problem.
    >
    > Arno
    >
    >

    [snip]

  17. Re: Bad disk controller? Dying HDD? (rich text)

    Rod Speed wrote in news:6gfnnmFfck97U1@mid.individual.net
    > Ant wrote:
    > > On 8/12/2008 11:08 PM PT, Rod Speed typed:
    > >
    > > > Ant wrote:
    > > > > Hi. My old mini-tower PC's HDDs are acting crazy today. I came home
    > > > > and noticed my second drive wasn't there so I checked dmesg (deleted
    > > > > normal logs before hdb):

    >
    > > > > SMART Attributes Data Structure revision number: 7
    > > > > Vendor Specific SMART Attributes with Thresholds:


    > > > > ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE

    [snip]
    > > > > 5 Reallocated_Sector_Ct 0x0033 100 100 020 Pre-fail Always - 0

    [snip]

    > > > Something's died, Jim.


    It certainly did.

    > > > You into necrophilia ?

    > >
    > > > P

    > >

    []
    >
    > > > There's certainly quite a few bad sectors on that drive.

    >
    > > How can you tell?


    > Thats the reallocated sector count in the SMART report.


    Pity it's zero, zip, nada, Roddy.
    You into necrophilia too, because your brain must have died.

    >
    > > I am so used to chkdsk, scandisk, pretty images, etc.


    > A Jap would at least have the decency to disembowel itself.


    But you are no Jap, Roddles, isn't that the real pity of it all.

    [snip]

  18. Re: Bad disk controller? Dying HDD?

    On Wed, 13 Aug 2008 18:28:20 UTC in comp.os.linux.hardware, ANTant@zimage.com
    (Ant) wrote:

    > > I've never heard of Fortron but that doesn't mean that they aren't any good.
    > > What I have seen before is IDE devices on the same cable interfering with each
    > > other when one of them is going south. You could try removing the 2nd device
    > > from the primary cable and attaching it to another one (if there is one) and see
    > > if that eliminates the errors on one or both of the drives.

    >
    > Is unmounting hdb via umount command valid?


    Not really, you need to get the drive off the cable to tell which means opening
    things up and performing surgery.

    --
    Trevor Hemsley, Brighton, UK
    Trevor dot Hemsley at ntlworld dot com

  19. Re: Bad disk controller? Dying HDD? (rich text)

    Squeeze wrote using X-Newsreader: Microsoft Outlook Express 6.00.2800.1437:

    ......
    > Pity it's zero, zip, nada, Roddy.
    > You into necrophilia too, because your brain must have died.
    >

    Just line breaks. And some brainfarts, yours included.
    >>
    >> > I am so used to chkdsk, scandisk, pretty images, etc.

    >
    >> A Jap would at least have the decency to disembowel itself.

    >
    > But you are no Jap, Roddles, isn't that the real pity of it all.
    >
    > [snip]
    >
    >
    rel=stylesheet>
    >
    >
    >
    >


    Uurghs. Not a brainfart. a HTMLfart. Go take a breath and a break from your
    computer and adjust your inadequate posting program.
    --
    vista policy violation: Microsoft optical mouse found penguin patterns
    on mousepad. Partition scan in progress to remove offending
    incompatible products. Reactivate MS software.
    Linux 2.6.24. [LinuxCounter#295241,ICQ#4918962]

  20. Re: Bad disk controller? Dying HDD?

    Squeeze wrote:

    > Some aussie moron just copied 75kB of ****e.
    >

    Some Outbug Excuse Abuser just TOFU'd 10 kByte of .... guess what?
    --
    vista policy violation: Microsoft optical mouse found penguin patterns
    on mousepad. Partition scan in progress to remove offending
    incompatible products. Reactivate MS software.
    Linux 2.6.24. [LinuxCounter#295241,ICQ#4918962]