Buenas. Despues de hacer una parada en mi equipo por mantenimiento, me
he fijado que hay dos particiones, concretamente /home y /home/usuario,
que no han querido montarse. Al intentarlo, me salen estos errores:

Sep 27 22:58:37 Elvira kernel: hda: dma_intr: status=0x51 { DriveReady
SeekComplete Error }
Sep 27 22:58:39 Elvira kernel: hda: dma_intr: error=0x40 {
UncorrectableError }, LBAsect=73324828, sector=73324828
Sep 27 22:58:39 Elvira kernel: ide: failed opcode was: unknown
Sep 27 22:58:39 Elvira kernel: end_request: I/O error, dev hda, sector
73324828
Sep 27 22:58:39 Elvira kernel: printk: 1 messages suppressed.
Sep 27 22:58:39 Elvira kernel: hda: dma_intr: status=0x51 { DriveReady
SeekComplete Error }
Sep 27 22:58:39 Elvira kernel: hda: dma_intr: error=0x40 {
UncorrectableError }, LBAsect=73324828, sector=73324828
Sep 27 22:58:39 Elvira kernel: ide: failed opcode was: unknown
Sep 27 22:58:39 Elvira kernel: end_request: I/O error, dev hda, sector
73324828
Sep 27 22:59:05 Elvira kernel: hda: dma_intr: status=0x51 { DriveReady
SeekComplete Error }
Sep 27 22:59:05 Elvira kernel: hda: dma_intr: error=0x40 {
UncorrectableError }, LBAsect=29354962, sector=29354962
Sep 27 22:59:05 Elvira kernel: ide: failed opcode was: unknown
Sep 27 22:59:05 Elvira kernel: end_request: I/O error, dev hda, sector
29354962
Sep 27 22:59:06 Elvira kernel: hda: dma_intr: status=0x51 { DriveReady
SeekComplete Error }
Sep 27 22:59:06 Elvira kernel: hda: dma_intr: error=0x40 {
UncorrectableError }, LBAsect=29354963, sector=29354963
Sep 27 22:59:06 Elvira kernel: ide: failed opcode was: unknown
Sep 27 22:59:06 Elvira kernel: end_request: I/O error, dev hda, sector
29354963
[..]
Sep 27 22:59:27 Elvira kernel: printk: 2 messages suppressed.

Por lo que he leido por ahi, creo que se me esta muriendo el disco duro.
Lo curioso es que esta "muerte" se esta centrando unica y exclusivamente
en las particiones de datos de usuarios. Ni la particion raiz, ni /boot,
ni /var, que las tengo en el mismo disco duro, en diferentes
particiones, he notado error alguno.
Lo malo de esto, ademas, es que no puedo montarlas, por lo que me es
imposible recuperar los datos nuevos respecto al backup que tengo hecho.
Cuando intento montarlo, obtengo esto:

mount: tipo de sistema de ficheros incorrecto, opción incorrecta,
superbloque incorrecto en /dev/hda3, falta la página de códigos,
o algún otro error
En algunos casos se encuentra información en syslog, pruebe
dmesg | tail o algo parecido

Alguien me da un soplo de esperanza? Un saludo.

Hola Juan - Casa <jmoral***arrakis.es>
el Thu, 27 Sep 2007 23:34:07 +0200 escribiste:

> Alguien me da un soplo de esperanza? Un saludo.

Puesto que los errores hacen referencia al DMA, tal vez
si lo desactivas (no recuerdo cómo, quizás con hdparm),
la cosa mejore, al menos para poder salvar las particiones.

Para saber si el disco se está muriendo prueba con smartmontools.

--
Gonzalo Pérez de Olaguer Córdoba <gpoc***iies.es>
PGP key 2861C704 --- F206 5671 6789 425D 111C 1302 214F 1934 2861 C704

Hola Juan - Casa <jmoral***arrakis.es>
el Thu, 27 Sep 2007 23:34:07 +0200 escribiste:

> Alguien me da un soplo de esperanza? Un saludo.

Puesto que los errores hacen referencia al DMA, tal vez
si lo desactivas (no recuerdo cómo, quizás con hdparm),
la cosa mejore, al menos para poder salvar las particiones.

Para saber si el disco se está muriendo prueba con smartmontools.

--
Gonzalo Pérez de Olaguer Córdoba <gpoc***iies.es>
PGP key 2861C704 --- F206 5671 6789 425D 111C 1302 214F 1934 2861 C704

Hola Juan - Casa <jmoral***arrakis.es>
el Thu, 27 Sep 2007 23:34:07 +0200 escribiste:

> Alguien me da un soplo de esperanza? Un saludo.

Puesto que los errores hacen referencia al DMA, tal vez
si lo desactivas (no recuerdo cómo, quizás con hdparm),
la cosa mejore, al menos para poder salvar las particiones.

Para saber si el disco se está muriendo prueba con smartmontools.

--
Gonzalo Pérez de Olaguer Córdoba <gpoc***iies.es>
PGP key 2861C704 --- F206 5671 6789 425D 111C 1302 214F 1934 2861 C704

Gonzalo Pérez de Olaguer Córdoba escribió:

> Puesto que los errores hacen referencia al DMA, tal vez
> si lo desactivas (no recuerdo cómo, quizás con hdparm),
> la cosa mejore, al menos para poder salvar las particiones.

Buenas. Algo cambia. Ahora el error es del tipo:

Sep 28 00:09:37 Elvira kernel: hda: task_in_intr: status=0x59 {
DriveReady SeekComplete DataRequest Error }
Sep 28 00:09:37 Elvira kernel: hda: task_in_intr: error=0x40 {
UncorrectableError }, LBAsect=29354962, sector=29354962
Sep 28 00:09:37 Elvira kernel: ide: failed opcode was: unknown
Sep 28 00:09:37 Elvira kernel: end_request: I/O error, dev hda, sector
29354962

Ademas, le he pasado el smartctl, del paquete smartmontools, el test
"smarctl -t offline /dev/hda", y esto es lo que me sale cuando lo saco
por la bitacora del SMT:

=== START OF READ SMART DATA SECTION ===
SMART Error Log Version: 1
ATA Error Count: 6100 (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 6100 occurred at disk power-on lifetime: 31485 hours (1311 days +
21 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 59 08 d2 eb bf e1 Error: UNC at LBA = 0x01bfebd2 = 29354962

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
20 00 08 d2 eb bf e1 08 08:14:10.640 READ SECTOR(S)
20 00 08 c2 db bf e1 08 08:14:10.640 READ SECTOR(S)
20 00 08 aa db bf e1 08 08:14:10.624 READ SECTOR(S)
20 00 08 a2 db bf e1 08 08:14:10.624 READ SECTOR(S)
20 00 02 a4 db bf e1 08 08:14:10.624 READ SECTOR(S)

Error 6099 occurred at disk power-on lifetime: 31485 hours (1311 days +
21 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 59 08 1c d9 5e e4 Error: UNC at LBA = 0x045ed91c = 73324828

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
20 00 08 1c d9 5e e4 08 08:13:21.152 READ SECTOR(S)
20 00 08 fc c8 5e e4 08 08:13:21.152 READ SECTOR(S)
20 00 08 e4 c8 5e e4 08 08:13:21.152 READ SECTOR(S)
20 00 08 dc c8 5e e4 08 08:13:21.136 READ SECTOR(S)
20 00 08 d4 c8 5e e4 08 08:13:21.136 READ SECTOR(S)

Error 6098 occurred at disk power-on lifetime: 31485 hours (1311 days +
21 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 59 08 d2 eb bf e1 Error: UNC at LBA = 0x01bfebd2 = 29354962

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
20 00 08 d2 eb bf e1 08 08:13:09.328 READ SECTOR(S)
20 00 08 c2 db bf e1 08 08:13:09.328 READ SECTOR(S)
20 00 08 aa db bf e1 08 08:13:09.328 READ SECTOR(S)
20 00 08 a2 db bf e1 08 08:13:09.328 READ SECTOR(S)
20 00 02 a4 db bf e1 08 08:13:09.328 READ SECTOR(S)

Error 6097 occurred at disk power-on lifetime: 31485 hours (1311 days +
21 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 59 08 1c d9 5e e4 Error: UNC at LBA = 0x045ed91c = 73324828

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
20 00 08 1c d9 5e e4 08 08:12:25.072 READ SECTOR(S)
20 00 08 fc c8 5e e4 08 08:12:25.072 READ SECTOR(S)
20 00 08 e4 c8 5e e4 08 08:12:25.072 READ SECTOR(S)
20 00 08 dc c8 5e e4 08 08:12:25.072 READ SECTOR(S)
20 00 08 d4 c8 5e e4 08 08:12:25.056 READ SECTOR(S)

Error 6096 occurred at disk power-on lifetime: 31485 hours (1311 days +
21 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 59 08 d2 eb bf e1 Error: UNC at LBA = 0x01bfebd2 = 29354962

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
20 00 08 d2 eb bf e1 08 08:09:55.392 READ SECTOR(S)
20 00 08 c2 db bf e1 08 08:09:55.392 READ SECTOR(S)
20 00 08 aa db bf e1 08 08:09:55.392 READ SECTOR(S)
20 00 08 a2 db bf e1 08 08:09:55.392 READ SECTOR(S)
20 00 02 a4 db bf e1 08 08:09:55.392 READ SECTOR(S)

Como puedes ver, me dice los errores, pero no se interpretar mucho mas.
Seguire haciendo tests a ver. Un saludo, y gracias.

Gonzalo Pérez de Olaguer Córdoba escribió:

> Puesto que los errores hacen referencia al DMA, tal vez
> si lo desactivas (no recuerdo cómo, quizás con hdparm),
> la cosa mejore, al menos para poder salvar las particiones.

Buenas. Algo cambia. Ahora el error es del tipo:

Sep 28 00:09:37 Elvira kernel: hda: task_in_intr: status=0x59 {
DriveReady SeekComplete DataRequest Error }
Sep 28 00:09:37 Elvira kernel: hda: task_in_intr: error=0x40 {
UncorrectableError }, LBAsect=29354962, sector=29354962
Sep 28 00:09:37 Elvira kernel: ide: failed opcode was: unknown
Sep 28 00:09:37 Elvira kernel: end_request: I/O error, dev hda, sector
29354962

Ademas, le he pasado el smartctl, del paquete smartmontools, el test
"smarctl -t offline /dev/hda", y esto es lo que me sale cuando lo saco
por la bitacora del SMT:

=== START OF READ SMART DATA SECTION ===
SMART Error Log Version: 1
ATA Error Count: 6100 (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 6100 occurred at disk power-on lifetime: 31485 hours (1311 days +
21 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 59 08 d2 eb bf e1 Error: UNC at LBA = 0x01bfebd2 = 29354962

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
20 00 08 d2 eb bf e1 08 08:14:10.640 READ SECTOR(S)
20 00 08 c2 db bf e1 08 08:14:10.640 READ SECTOR(S)
20 00 08 aa db bf e1 08 08:14:10.624 READ SECTOR(S)
20 00 08 a2 db bf e1 08 08:14:10.624 READ SECTOR(S)
20 00 02 a4 db bf e1 08 08:14:10.624 READ SECTOR(S)

Error 6099 occurred at disk power-on lifetime: 31485 hours (1311 days +
21 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 59 08 1c d9 5e e4 Error: UNC at LBA = 0x045ed91c = 73324828

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
20 00 08 1c d9 5e e4 08 08:13:21.152 READ SECTOR(S)
20 00 08 fc c8 5e e4 08 08:13:21.152 READ SECTOR(S)
20 00 08 e4 c8 5e e4 08 08:13:21.152 READ SECTOR(S)
20 00 08 dc c8 5e e4 08 08:13:21.136 READ SECTOR(S)
20 00 08 d4 c8 5e e4 08 08:13:21.136 READ SECTOR(S)

Error 6098 occurred at disk power-on lifetime: 31485 hours (1311 days +
21 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 59 08 d2 eb bf e1 Error: UNC at LBA = 0x01bfebd2 = 29354962

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
20 00 08 d2 eb bf e1 08 08:13:09.328 READ SECTOR(S)
20 00 08 c2 db bf e1 08 08:13:09.328 READ SECTOR(S)
20 00 08 aa db bf e1 08 08:13:09.328 READ SECTOR(S)
20 00 08 a2 db bf e1 08 08:13:09.328 READ SECTOR(S)
20 00 02 a4 db bf e1 08 08:13:09.328 READ SECTOR(S)

Error 6097 occurred at disk power-on lifetime: 31485 hours (1311 days +
21 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 59 08 1c d9 5e e4 Error: UNC at LBA = 0x045ed91c = 73324828

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
20 00 08 1c d9 5e e4 08 08:12:25.072 READ SECTOR(S)
20 00 08 fc c8 5e e4 08 08:12:25.072 READ SECTOR(S)
20 00 08 e4 c8 5e e4 08 08:12:25.072 READ SECTOR(S)
20 00 08 dc c8 5e e4 08 08:12:25.072 READ SECTOR(S)
20 00 08 d4 c8 5e e4 08 08:12:25.056 READ SECTOR(S)

Error 6096 occurred at disk power-on lifetime: 31485 hours (1311 days +
21 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 59 08 d2 eb bf e1 Error: UNC at LBA = 0x01bfebd2 = 29354962

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
20 00 08 d2 eb bf e1 08 08:09:55.392 READ SECTOR(S)
20 00 08 c2 db bf e1 08 08:09:55.392 READ SECTOR(S)
20 00 08 aa db bf e1 08 08:09:55.392 READ SECTOR(S)
20 00 08 a2 db bf e1 08 08:09:55.392 READ SECTOR(S)
20 00 02 a4 db bf e1 08 08:09:55.392 READ SECTOR(S)

Como puedes ver, me dice los errores, pero no se interpretar mucho mas.
Seguire haciendo tests a ver. Un saludo, y gracias.

Gonzalo Pérez de Olaguer Córdoba escribió:

> Puesto que los errores hacen referencia al DMA, tal vez
> si lo desactivas (no recuerdo cómo, quizás con hdparm),
> la cosa mejore, al menos para poder salvar las particiones.

Buenas. Algo cambia. Ahora el error es del tipo:

Sep 28 00:09:37 Elvira kernel: hda: task_in_intr: status=0x59 {
DriveReady SeekComplete DataRequest Error }
Sep 28 00:09:37 Elvira kernel: hda: task_in_intr: error=0x40 {
UncorrectableError }, LBAsect=29354962, sector=29354962
Sep 28 00:09:37 Elvira kernel: ide: failed opcode was: unknown
Sep 28 00:09:37 Elvira kernel: end_request: I/O error, dev hda, sector
29354962

Ademas, le he pasado el smartctl, del paquete smartmontools, el test
"smarctl -t offline /dev/hda", y esto es lo que me sale cuando lo saco
por la bitacora del SMT:

=== START OF READ SMART DATA SECTION ===
SMART Error Log Version: 1
ATA Error Count: 6100 (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 6100 occurred at disk power-on lifetime: 31485 hours (1311 days +
21 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 59 08 d2 eb bf e1 Error: UNC at LBA = 0x01bfebd2 = 29354962

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
20 00 08 d2 eb bf e1 08 08:14:10.640 READ SECTOR(S)
20 00 08 c2 db bf e1 08 08:14:10.640 READ SECTOR(S)
20 00 08 aa db bf e1 08 08:14:10.624 READ SECTOR(S)
20 00 08 a2 db bf e1 08 08:14:10.624 READ SECTOR(S)
20 00 02 a4 db bf e1 08 08:14:10.624 READ SECTOR(S)

Error 6099 occurred at disk power-on lifetime: 31485 hours (1311 days +
21 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 59 08 1c d9 5e e4 Error: UNC at LBA = 0x045ed91c = 73324828

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
20 00 08 1c d9 5e e4 08 08:13:21.152 READ SECTOR(S)
20 00 08 fc c8 5e e4 08 08:13:21.152 READ SECTOR(S)
20 00 08 e4 c8 5e e4 08 08:13:21.152 READ SECTOR(S)
20 00 08 dc c8 5e e4 08 08:13:21.136 READ SECTOR(S)
20 00 08 d4 c8 5e e4 08 08:13:21.136 READ SECTOR(S)

Error 6098 occurred at disk power-on lifetime: 31485 hours (1311 days +
21 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 59 08 d2 eb bf e1 Error: UNC at LBA = 0x01bfebd2 = 29354962

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
20 00 08 d2 eb bf e1 08 08:13:09.328 READ SECTOR(S)
20 00 08 c2 db bf e1 08 08:13:09.328 READ SECTOR(S)
20 00 08 aa db bf e1 08 08:13:09.328 READ SECTOR(S)
20 00 08 a2 db bf e1 08 08:13:09.328 READ SECTOR(S)
20 00 02 a4 db bf e1 08 08:13:09.328 READ SECTOR(S)

Error 6097 occurred at disk power-on lifetime: 31485 hours (1311 days +
21 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 59 08 1c d9 5e e4 Error: UNC at LBA = 0x045ed91c = 73324828

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
20 00 08 1c d9 5e e4 08 08:12:25.072 READ SECTOR(S)
20 00 08 fc c8 5e e4 08 08:12:25.072 READ SECTOR(S)
20 00 08 e4 c8 5e e4 08 08:12:25.072 READ SECTOR(S)
20 00 08 dc c8 5e e4 08 08:12:25.072 READ SECTOR(S)
20 00 08 d4 c8 5e e4 08 08:12:25.056 READ SECTOR(S)

Error 6096 occurred at disk power-on lifetime: 31485 hours (1311 days +
21 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 59 08 d2 eb bf e1 Error: UNC at LBA = 0x01bfebd2 = 29354962

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
20 00 08 d2 eb bf e1 08 08:09:55.392 READ SECTOR(S)
20 00 08 c2 db bf e1 08 08:09:55.392 READ SECTOR(S)
20 00 08 aa db bf e1 08 08:09:55.392 READ SECTOR(S)
20 00 08 a2 db bf e1 08 08:09:55.392 READ SECTOR(S)
20 00 02 a4 db bf e1 08 08:09:55.392 READ SECTOR(S)

Como puedes ver, me dice los errores, pero no se interpretar mucho mas.
Seguire haciendo tests a ver. Un saludo, y gracias.

On 2007-09-28, Juan - Casa <jmoral***arrakis.es> wrote:
> Gonzalo Pérez de Olaguer Córdoba escribió:
>
>> Puesto que los errores hacen referencia al DMA, tal vez
>> si lo desactivas (no recuerdo cómo, quizás con hdparm),
>> la cosa mejore, al menos para poder salvar las particiones.
>>
>> Para saber si el disco se está muriendo prueba con smartmontools.
>
> Buenas. Otro de los test que he pasado, me suelta esto:
>
> Elvira:~# smartctl -l selftest /dev/hda
> smartctl version 5.36 [i686-pc-linux-gnu] Copyright (C) 2002-6 Bruce Allen
> Home page is http://smartmontools.sourceforge.net/
>
>=== START OF READ SMART DATA SECTION ===
> SMART Self-test log structure revision number 1
> Num Test_Description Status Remaining
> LifeTime(hours) LBA_of_first_error
> # 3 Extended offline Completed: read failure 40% 23642
> 26985027

Yo no sé mucho inglés, pero ¿ aquí dice que no puede leer el
40% de los sectores ?

Si es así, recuerda que cuando un disco empieza a fallar, ya poco se
puede hacer.

Un saludo.

On 2007-09-28, Juan - Casa <jmoral***arrakis.es> wrote:
> Gonzalo Pérez de Olaguer Córdoba escribió:
>
>> Puesto que los errores hacen referencia al DMA, tal vez
>> si lo desactivas (no recuerdo cómo, quizás con hdparm),
>> la cosa mejore, al menos para poder salvar las particiones.
>>
>> Para saber si el disco se está muriendo prueba con smartmontools.
>
> Buenas. Otro de los test que he pasado, me suelta esto:
>
> Elvira:~# smartctl -l selftest /dev/hda
> smartctl version 5.36 [i686-pc-linux-gnu] Copyright (C) 2002-6 Bruce Allen
> Home page is http://smartmontools.sourceforge.net/
>
>=== START OF READ SMART DATA SECTION ===
> SMART Self-test log structure revision number 1
> Num Test_Description Status Remaining
> LifeTime(hours) LBA_of_first_error
> # 3 Extended offline Completed: read failure 40% 23642
> 26985027

Yo no sé mucho inglés, pero ¿ aquí dice que no puede leer el
40% de los sectores ?

Si es así, recuerda que cuando un disco empieza a fallar, ya poco se
puede hacer.

Un saludo.

On 2007-09-28, Juan - Casa <jmoral***arrakis.es> wrote:
> Gonzalo Pérez de Olaguer Córdoba escribió:
>
>> Puesto que los errores hacen referencia al DMA, tal vez
>> si lo desactivas (no recuerdo cómo, quizás con hdparm),
>> la cosa mejore, al menos para poder salvar las particiones.
>>
>> Para saber si el disco se está muriendo prueba con smartmontools.
>
> Buenas. Otro de los test que he pasado, me suelta esto:
>
> Elvira:~# smartctl -l selftest /dev/hda
> smartctl version 5.36 [i686-pc-linux-gnu] Copyright (C) 2002-6 Bruce Allen
> Home page is http://smartmontools.sourceforge.net/
>
>=== START OF READ SMART DATA SECTION ===
> SMART Self-test log structure revision number 1
> Num Test_Description Status Remaining
> LifeTime(hours) LBA_of_first_error
> # 3 Extended offline Completed: read failure 40% 23642
> 26985027

Yo no sé mucho inglés, pero ¿ aquí dice que no puede leer el
40% de los sectores ?

Si es así, recuerda que cuando un disco empieza a fallar, ya poco se
puede hacer.

Un saludo.