HDD en vias de destruccion? clicks y errores

Archivado
Hola, os cuento:

mas o menos por septiembre me cambie el HDD del portatil, y pasa lo siguiente:

cada X horas, (no muy seguido, ni cuando esta leyendo escribiendo... vamos aleatorio del todo pero bastante de vez en cuando) hace un click bastante audible, nada sutil... pero no hay paron de actividad ni nada, es el sonido pero sigue funcionando sin ningun imprevisto....


por otro lado tengo cuatro particiones, 3 de ellas ext3.

el otro dia, haciendo el checkeo durante el arranque, dio un error en sda3... y hoy en sda2.

el error es el siguiente:

"Error reading block xxxxxx (attempt to read block from filesystem resulted in short read) while getting next inode from scan"

saber, se lo que significa literalmente... (vamos se ingles xD) pero no se lo que significa realmente.

acto seguido me deja reiniciar o reparar manualmente.. ahi ya no hay mas misterio.

es grave? hay herramientas de diagnostico ademas del propio fsck?puede deberse a un error puntual y al hacer fsck en distintos dias a cada particion me estoy emparanoyando?

decidme cosas por favor ;)


gracias.
s.m.a.r.t. es tu amigo :D
Si el disco es Seagate (y aunque esto no tenga nada que ver con Soft. Libre), puedes escanearlo a consciencia con las Seagate Seatools. Es un disquete de arranque.
No hace falta ni que grabes la imagen en ningun sitio, puedes dejarla en el HDD y añadir una entrada a tu menu.lst de GRUB (si usas GRUB, claro), para arrancarla, mediante memdisk, que si no me equivoco, viene con Syslinux.
O si pasas de lios y tienes disquetera y disquetes, pues a lo tradicional XD
no es seagate, es samsung.

he echado un ojo al wiki de arch para ver como va el tema smart.

el HDD lo soporta y esta activado. este es el log de errores segun "smartctl -l error /dev/sda"

SMART Error Log Version: 1
ATA Error Count: 96 (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 96 occurred at disk power-on lifetime: 966 hours (40 days + 6 hours)
  When the command that caused the error occurred, the device was in an unknown state.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 08 9b 41 1d e4  Error: UNC 8 sectors at LBA = 0x041d419b = 69026203

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  c8 00 08 9b 41 1d e4 00      00:06:01.625  READ DMA
  ec 00 00 00 00 00 a0 00      00:06:00.437  IDENTIFY DEVICE
  ef 03 46 00 00 00 a0 00      00:06:00.437  SET FEATURES [Set transfer mode]
  ec 00 00 00 00 00 a0 00      00:06:00.437  IDENTIFY DEVICE

Error 95 occurred at disk power-on lifetime: 966 hours (40 days + 6 hours)
  When the command that caused the error occurred, the device was in an unknown state.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 08 93 41 1d e4  Error: UNC 8 sectors at LBA = 0x041d4193 = 69026195

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  c8 00 08 93 41 1d e4 00      00:05:51.562  READ DMA
  ec 00 00 00 00 00 a0 00      00:05:50.437  IDENTIFY DEVICE
  ef 03 46 00 00 00 a0 00      00:05:50.437  SET FEATURES [Set transfer mode]
  ec 00 00 00 00 00 a0 00      00:05:50.437  IDENTIFY DEVICE

Error 94 occurred at disk power-on lifetime: 966 hours (40 days + 6 hours)
  When the command that caused the error occurred, the device was in an unknown state.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  01 51 08 93 41 1d e4  Error: AMNF 8 sectors at LBA = 0x041d4193 = 69026195

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  c8 00 08 93 41 1d e4 00      00:05:50.375  READ DMA
  ec 00 00 00 00 00 a0 00      00:05:47.937  IDENTIFY DEVICE
  ef 03 46 00 00 00 a0 00      00:05:47.937  SET FEATURES [Set transfer mode]
  ec 00 00 00 00 00 a0 00      00:05:47.937  IDENTIFY DEVICE

Error 93 occurred at disk power-on lifetime: 966 hours (40 days + 6 hours)
  When the command that caused the error occurred, the device was in an unknown state.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 08 93 41 1d e4  Error: UNC 8 sectors at LBA = 0x041d4193 = 69026195

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  c8 00 08 93 41 1d e4 00      00:05:47.875  READ DMA
  ec 00 00 00 00 00 a0 00      00:05:46.687  IDENTIFY DEVICE
  ef 03 46 00 00 00 a0 00      00:05:46.687  SET FEATURES [Set transfer mode]
  ec 00 00 00 00 00 a0 00      00:05:46.625  IDENTIFY DEVICE

Error 92 occurred at disk power-on lifetime: 966 hours (40 days + 6 hours)
  When the command that caused the error occurred, the device was in an unknown state.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 08 93 41 1d e4  Error: UNC 8 sectors at LBA = 0x041d4193 = 69026195

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  c8 00 08 93 41 1d e4 00      00:05:46.562  READ DMA
  ec 00 00 00 00 00 a0 00      00:05:45.375  IDENTIFY DEVICE
  ef 03 46 00 00 00 a0 00      00:05:43.500  SET FEATURES [Set transfer mode]
  ec 00 00 00 00 00 a0 00      00:05:43.500  IDENTIFY DEVICE




contiene los ultimos 5 errores, y si no descifro mal, son de hace 40 dias... (contando solo el tiempo que lleva encendido?)

no se si debo preocuparme o no xD
jorchube escribió:no es seagate, es samsung.

he echado un ojo al wiki de arch para ver como va el tema smart.

el HDD lo soporta y esta activado. este es el log de errores segun "smartctl -l error /dev/sda"

SMART Error Log Version: 1
ATA Error Count: 96 (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 96 occurred at disk power-on lifetime: 966 hours (40 days + 6 hours)
  When the command that caused the error occurred, the device was in an unknown state.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 08 9b 41 1d e4  Error: UNC 8 sectors at LBA = 0x041d419b = 69026203

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  c8 00 08 9b 41 1d e4 00      00:06:01.625  READ DMA
  ec 00 00 00 00 00 a0 00      00:06:00.437  IDENTIFY DEVICE
  ef 03 46 00 00 00 a0 00      00:06:00.437  SET FEATURES [Set transfer mode]
  ec 00 00 00 00 00 a0 00      00:06:00.437  IDENTIFY DEVICE

Error 95 occurred at disk power-on lifetime: 966 hours (40 days + 6 hours)
  When the command that caused the error occurred, the device was in an unknown state.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 08 93 41 1d e4  Error: UNC 8 sectors at LBA = 0x041d4193 = 69026195

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  c8 00 08 93 41 1d e4 00      00:05:51.562  READ DMA
  ec 00 00 00 00 00 a0 00      00:05:50.437  IDENTIFY DEVICE
  ef 03 46 00 00 00 a0 00      00:05:50.437  SET FEATURES [Set transfer mode]
  ec 00 00 00 00 00 a0 00      00:05:50.437  IDENTIFY DEVICE

Error 94 occurred at disk power-on lifetime: 966 hours (40 days + 6 hours)
  When the command that caused the error occurred, the device was in an unknown state.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  01 51 08 93 41 1d e4  Error: AMNF 8 sectors at LBA = 0x041d4193 = 69026195

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  c8 00 08 93 41 1d e4 00      00:05:50.375  READ DMA
  ec 00 00 00 00 00 a0 00      00:05:47.937  IDENTIFY DEVICE
  ef 03 46 00 00 00 a0 00      00:05:47.937  SET FEATURES [Set transfer mode]
  ec 00 00 00 00 00 a0 00      00:05:47.937  IDENTIFY DEVICE

Error 93 occurred at disk power-on lifetime: 966 hours (40 days + 6 hours)
  When the command that caused the error occurred, the device was in an unknown state.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 08 93 41 1d e4  Error: UNC 8 sectors at LBA = 0x041d4193 = 69026195

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  c8 00 08 93 41 1d e4 00      00:05:47.875  READ DMA
  ec 00 00 00 00 00 a0 00      00:05:46.687  IDENTIFY DEVICE
  ef 03 46 00 00 00 a0 00      00:05:46.687  SET FEATURES [Set transfer mode]
  ec 00 00 00 00 00 a0 00      00:05:46.625  IDENTIFY DEVICE

Error 92 occurred at disk power-on lifetime: 966 hours (40 days + 6 hours)
  When the command that caused the error occurred, the device was in an unknown state.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 08 93 41 1d e4  Error: UNC 8 sectors at LBA = 0x041d4193 = 69026195

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  c8 00 08 93 41 1d e4 00      00:05:46.562  READ DMA
  ec 00 00 00 00 00 a0 00      00:05:45.375  IDENTIFY DEVICE
  ef 03 46 00 00 00 a0 00      00:05:43.500  SET FEATURES [Set transfer mode]
  ec 00 00 00 00 00 a0 00      00:05:43.500  IDENTIFY DEVICE




contiene los ultimos 5 errores, y si no descifro mal, son de hace 40 dias... (contando solo el tiempo que lleva encendido?)

no se si debo preocuparme o no xD


mmm... dime que tienes hdparm -B 254 /dev/sda en tu /etc/rc.local

Tengo pesadillas con el hd de mi portátil XD
http://bbs.archlinux.org/viewtopic.php?id=39258
theogre escribió:
mmm... dime que tienes hdparm -B 254 /dev/sda en tu /etc/rc.local

Tengo pesadillas con el hd de mi portátil XD
http://bbs.archlinux.org/viewtopic.php?id=39258



no, no tengo eso en rc.local... procedo a añadirlo.


pd: he visto tu post en los foros de arch... bueno, el load cycle count de mi hdd es 100875...
Pues usa Hutil que es la herramienta de Samsung.
Lo único que esto de añadir
hdparm -B 254 /dev/sda en tu /etc/rc.local
no deberia hacerse sólo cuando estas tirando de bateria? lo digo porque tengo instalado el laptool-tools, y me parece que eso lo modifica sólo cuando esté en modo bateria.

Ya me habeis metido la parana en el body.

Salu2
Cuantos años tiene el HD? Muchos fabricantes dan una vida util de 5 años y a mi se me han cascao discos con 3 años, lo digo porq si es muy viejo tal vez los errores se produzcan cada vez más... haz copias de seguridad.
ZX80 escribió:Cuantos años tiene el HD? Muchos fabricantes dan una vida util de 5 años y a mi se me han cascao discos con 3 años, lo digo porq si es muy viejo tal vez los errores se produzcan cada vez más... haz copias de seguridad.


jorchube escribió:Hola, os cuento:

mas o menos por septiembre me cambie el HDD del portatil, y pasa lo siguiente:
[...]
mis discos duros pueden tener tranquilamente 8 años y ahi siguen, dandole duro.
gracias por la ayuda a todos (incluso a ZX80, aunque parece que lee con prisas xDDD)

con hdparm -B 254 ha dejado de hacer los clicks

snake, tendre en cuenta Hutil

os seguire informando de irregularidades o avances, thanx ;)


EDIT: he pasado el ultimate bootcd.... dice que no hay fallos en mi hdd... que si siguen los problemas que mire a ver si tengo virus xDDDDDDDDDDD


(gracias)
11 respuestas
Archivado
Volver a Software libre