Dotaz: chyby hdd ve /var/log/messages

[hyperion]

Dec 13 10:30:10 umi hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Dec 13 10:30:10 umi hdb: dma_intr: error=0x40 { UncorrectableError }, LBAsect=121694807, high=7, low=4254295, sector=121694807
Dec 13 10:30:10 umi ide: failed opcode was: unknown
Dec 13 10:30:10 umi end_request: I/O error, dev hdb, sector 121694807
Dec 13 10:30:10 umi ReiserFS: hdb1: warning: vs-13070: reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [3693 8898 0x0 SD]
Dec 13 10:30:14 umi hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Dec 13 10:30:14 umi hdb: dma_intr: error=0x40 { UncorrectableError }, LBAsect=105121823, high=6, low=4458527, sector=105121823
Dec 13 10:30:14 umi ide: failed opcode was: unknown
Dec 13 10:30:14 umi end_request: I/O error, dev hdb, sector 105121823
Dec 13 10:30:14 umi ReiserFS: hdb1: warning: vs-13070: reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [3693 195 0x0 SD]
Dec 13 10:30:18 umi hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Dec 13 10:30:18 umi hdb: dma_intr: error=0x40 { UncorrectableError }, LBAsect=105134023, high=6, low=4470727, sector=105134023
Dec 13 10:30:18 umi ide: failed opcode was: unknown
Dec 13 10:30:18 umi end_request: I/O error, dev hdb, sector 105134023
Dec 13 10:30:18 umi ReiserFS: hdb1: warning: vs-13070: reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [3693 813 0x0 SD]
Dec 13 10:30:22 umi hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Dec 13 10:30:22 umi hdb: dma_intr: error=0x40 { UncorrectableError }, LBAsect=105121823, high=6, low=4458527, sector=105121823
Dec 13 10:30:22 umi ide: failed opcode was: unknown
Dec 13 10:30:22 umi end_request: I/O error, dev hdb, sector 105121823
Dec 13 10:30:22 umi ReiserFS: hdb1: warning: vs-13070: reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [3693 167 0x0 SD]
Dec 13 10:30:26 umi hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Dec 13 10:30:26 umi hdb: dma_intr: error=0x40 { UncorrectableError }, LBAsect=121694807, high=7, low=4254295, sector=121694807
Dec 13 10:30:26 umi ide: failed opcode was: unknown
Dec 13 10:30:26 umi end_request: I/O error, dev hdb, sector 121694807
Dec 13 10:30:26 umi ReiserFS: hdb1: warning: vs-13070: reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [3693 10211 0x0 SD]
Dec 13 10:30:30 umi hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Dec 13 10:30:30 umi hdb: dma_intr: error=0x40 { UncorrectableError }, LBAsect=105121823, high=6, low=4458527, sector=105121823
Dec 13 10:30:30 umi ide: failed opcode was: unknown
Dec 13 10:30:30 umi end_request: I/O error, dev hdb, sector 105121823
Dec 13 10:30:30 umi ReiserFS: hdb1: warning: vs-13070: reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [3693 413 0x0 SD]
Dec 13 10:30:34 umi hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Dec 13 10:30:34 umi hdb: dma_intr: error=0x40 { UncorrectableError }, LBAsect=121694807, high=7, low=4254295, sector=121694807
Dec 13 10:30:34 umi ide: failed opcode was: unknown
Dec 13 10:30:34 umi end_request: I/O error, dev hdb, sector 121694807
Dec 13 10:30:34 umi ReiserFS: hdb1: warning: vs-13070: reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [3693 9128 0x0 SD]
Dec 13 10:30:38 umi hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Dec 13 10:30:38 umi hdb: dma_intr: error=0x40 { UncorrectableError }, LBAsect=105124079, high=6, low=4460783, sector=105124079
Dec 13 10:30:38 umi ide: failed opcode was: unknown
Dec 13 10:30:38 umi end_request: I/O error, dev hdb, sector 105124079
Dec 13 10:30:38 umi ReiserFS: hdb1: warning: vs-13070: reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [3693 166 0x0 SD]
Dec 13 10:30:43 umi hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Dec 13 10:30:43 umi hdb: dma_intr: error=0x40 { UncorrectableError }, LBAsect=465818, high=0, low=465818, sector=465815
Dec 13 10:30:43 umi ide: failed opcode was: unknown
Dec 13 10:30:43 umi end_request: I/O error, dev hdb, sector 465815
Dec 13 10:30:43 umi ReiserFS: hdb1: warning: vs-13070: reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [2 10830 0x0 SD]

je cas udelat harddisku paaapaaa? da se to nejak opravit? dekuji.

Odpovědi

[i]

Rozhodně rychle zálohovat

Pak zkusit jiné jádro (může to být chyba s ovladačem řadiče)...

[hyperion]

hdparm -I na ten disk normalne funguje, mam v /etc/fstab kontrolu pri startu a taky v pohode.. vidim adresare (vylistuju ls), ale ls -alF uz ne a jejich obsah taky ne( pristup odmitnut). nestacilo by to jenom znovu zformatovat (nakopnutej filesystem) nebo je to horsi?

[jan markus]

zkuste tu chybovou hlasku predhodit googlu. (tedy bez tech ciselnych hodnot)

ja jsem to zkusil a v jednom prispevku kdosi kdesi psal, ze mel stejny problem u easyRAID R5A. napsal pry o tom vyrobci, ten mu poslal update firmware a byl klid...

tedy bych se poohlednul na strankach vyrobce po aktualizaci fw, osmelil bych se, pomodlil bych se,... ;)

[hyperion]

nemam RAID radic..

disk se fakt louci..:

fsck.reiserfs --rebuild-tree /dev/hdb

..
..
Skipping 9105 blocks (super block, journal, bitmaps) 21954575 blocks will be read
0%                                                    left 21910023, 11138 /sec
The problem has occurred looks like a hardware problem. If you have
bad blocks, we advise you to get a new hard drive, because once you
get one bad block  that the disk  drive internals  cannot hide from
your sight,the chances of getting more are generally said to become
much higher  (precise statistics are unknown to us), and  this disk
drive is probably not expensive enough  for you to you to risk your
time and  data on it.  If you don't want to follow that follow that
advice then  if you have just a few bad blocks,  try writing to the
bad blocks  and see if the drive remaps  the bad blocks (that means
it takes a block  it has  in reserve  and allocates  it for use for
of that block number).  If it cannot remap the block,  use badblock
option (-B) with  reiserfs utils to handle this block correctly.

bread: Cannot read the block (58202): (Input/output error).

Neúspěšně ukončen (SIGABRT)

[David Jež]

Mrkni co ti řekne SMART.
-djz

[Stanislav Motyčka]

ano, presne tak, treba pozret smart ->

smartctl -l error /dev/hdb

[hyperion]

smartctl -l error /dev/hdb
smartctl version 5.33 [x86_64-pc-linux-gnu] Copyright (C) 2002-4 Bruce Allen
Home page is http://smartmontools.sourceforge.net/

=== START OF READ SMART DATA SECTION ===
SMART Error Log Version: 1
ATA Error Count: 205 (device log contains only the most recent five errors)
        CR = Command Register [HEX]
        FR = Features Register [HEX]
        SC = Sector Count Register [HEX]
        SN = Sector Number Register [HEX]
        CL = Cylinder Low Register [HEX]
        CH = Cylinder High Register [HEX]
        DH = Device/Head Register [HEX]
        DC = Device Command Register [HEX]
        ER = Error register [HEX]
        ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.

Error 205 occurred at disk power-on lifetime: 11675 hours (486 days + 11 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 08 c7 37 44 f0  Error: UNC 8 sectors at LBA = 0x004437c7 = 4470727

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  25 00 08 c7 37 44 f0 00      06:15:00.351  READ DMA EXT
  25 00 08 77 6d 49 f0 00      06:14:56.244  READ DMA EXT
  35 00 08 67 b0 1f f0 00      06:14:56.240  WRITE DMA EXT
  25 00 08 cf ef 7e f0 00      06:14:56.228  READ DMA EXT
  25 00 08 b7 00 84 f0 00      06:14:56.212  READ DMA EXT

Error 204 occurred at disk power-on lifetime: 11675 hours (486 days + 11 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 08 1f 08 44 f0  Error: UNC 8 sectors at LBA = 0x0044081f = 4458527

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  25 00 08 1f 08 44 f0 00      06:15:00.351  READ DMA EXT
  25 00 08 87 58 64 f0 00      06:14:56.244  READ DMA EXT
  35 00 10 8f 68 00 f0 00      06:14:56.240  WRITE DMA EXT
  25 00 08 57 ea 40 f0 00      06:14:56.228  READ DMA EXT
  25 00 08 b7 8c 53 f0 00      06:14:56.212  READ DMA EXT

Error 203 occurred at disk power-on lifetime: 11675 hours (486 days + 11 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 08 57 ea 40 f0  Error: UNC 8 sectors at LBA = 0x0040ea57 = 4254295

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  25 00 08 57 ea 40 f0 00      06:13:43.459  READ DMA EXT
  25 00 08 b7 8c 53 f0 00      06:14:56.244  READ DMA EXT
  25 00 08 97 3b 4a f0 00      06:14:56.240  READ DMA EXT
  25 00 08 c7 ea 53 f0 00      06:14:56.228  READ DMA EXT
  25 00 08 07 e6 06 f0 00      06:14:56.212  READ DMA EXT

Error 202 occurred at disk power-on lifetime: 11674 hours (486 days + 10 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 08 57 ea 40 f0  Error: UNC 8 sectors at LBA = 0x0040ea57 = 4254295

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  25 00 08 57 ea 40 f0 00      06:06:24.966  READ DMA EXT
  25 00 08 b7 8c 53 f0 00      06:08:00.342  READ DMA EXT
  25 00 08 07 e6 06 f0 00      06:08:00.324  READ DMA EXT
  25 00 08 7f 5a df f0 00      06:08:00.311  READ DMA EXT
  35 00 08 57 8d 6e f0 00      06:08:00.282  WRITE DMA EXT

Error 201 occurred at disk power-on lifetime: 11673 hours (486 days + 9 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 08 1f 08 44 f0  Error: UNC 8 sectors at LBA = 0x0044081f = 4458527

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  25 00 08 1f 08 44 f0 00      04:59:40.007  READ DMA EXT
  25 00 08 67 b0 1f f0 00      04:59:39.993  READ DMA EXT
  25 00 08 67 e8 7f f0 00      04:59:39.973  READ DMA EXT
  25 00 08 9f 23 44 f0 00      04:58:52.420  READ DMA EXT
  25 00 08 07 e6 06 f0 00      04:58:52.318  READ DMA EXT