HD Apresenta Defeito - Log Gsmartcontrol

1. HD Apresenta Defeito - Log Gsmartcontrol

Leandro Silva
ExtremeLick

(usa Ubuntu)

Enviado em 22/06/2022 - 18:01h

Olá,
Boa Noite!

Houve uma queda de energia esses dias e notei que meu HD começou a fazer barulho. Pesquisando encontrei a indicação de uso do Gsmartcontrol para análise, porém, ao rodá-lo (pelo linux mint no pendrive) ele para poucos minutos após iniciar, e pede para eu verificar o log. Se eu tentar usar o Gsmartcontrol a partir do meu sistema operacional (instalado no HD) Linux Mint, o software nem abre.

Enfim, não entendo o log, alguém poderia me ajudar? Estou com medo de perder meus dados repentinamente.

Muito Obrigado.

Complete error log:

SMART Extended Comprehensive Error Log Version: 1 (6 sectors)
Device Error Count: 178 (device log contains only the most recent 24 errors)
CR = Command Register
FEATR = Features Register
COUNT = Count (was: Sector Count) Register
LBA_48 = Upper bytes of LBA High/Mid/Low Registers ] ATA-8
LH = LBA High (was: Cylinder High) Register ] LBA
LM = LBA Mid (was: Cylinder Low) Register ] Register
LL = LBA Low (was: Sector Number) Register ]
DV = Device (was: Device/Head) Register
DC = Device Control Register
ER = Error register
ST = Status register
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 178 [9] occurred at disk power-on lifetime: 27395 hours (1141 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 COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 00 00 00 00 1c 86 b8 40 00 Error: UNC at LBA = 0x001c86b8 = 1869496

Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
60 00 20 00 b8 00 00 00 1c 86 a0 40 08 09:46:25.230 READ FPDMA QUEUED
60 00 18 00 b0 00 00 00 1c 75 88 40 08 09:46:25.227 READ FPDMA QUEUED
60 00 08 00 a8 00 00 00 1c 75 80 40 08 09:46:25.221 READ FPDMA QUEUED
60 00 08 00 a0 00 00 00 25 dc 78 40 08 09:46:25.214 READ FPDMA QUEUED
60 00 08 00 98 00 00 00 25 dc 90 40 08 09:46:25.192 READ FPDMA QUEUED

Error 177 [8] occurred at disk power-on lifetime: 27372 hours (1140 days + 12 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 00 00 00 06 9d 8c c0 40 00 Error: UNC at LBA = 0x069d8cc0 = 110988480

Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
60 01 00 00 a0 00 00 02 56 ed a0 40 08 08:19:32.736 READ FPDMA QUEUED
60 00 08 00 98 00 00 06 9d 8c c0 40 08 08:19:32.724 READ FPDMA QUEUED
60 00 d8 00 90 00 00 01 ca 62 c8 40 08 08:19:32.717 READ FPDMA QUEUED
60 01 00 00 88 00 00 01 ca 67 c8 40 08 08:19:32.716 READ FPDMA QUEUED
60 00 a0 00 80 00 00 06 9d a2 58 40 08 08:19:32.708 READ FPDMA QUEUED

Error 176 [7] occurred at disk power-on lifetime: 27372 hours (1140 days + 12 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 00 00 00 06 9d 81 60 40 00 Error: UNC at LBA = 0x069d8160 = 110985568

Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
60 00 e0 00 b8 00 00 06 9d 80 98 40 08 08:19:27.488 READ FPDMA QUEUED
60 00 e0 00 b0 00 00 06 9d 7f b8 40 08 08:19:27.488 READ FPDMA QUEUED
60 00 d8 00 a8 00 00 06 9d 84 c8 40 08 08:19:27.487 READ FPDMA QUEUED
60 01 00 00 a0 00 00 06 9d 7e b8 40 08 08:19:27.483 READ FPDMA QUEUED
60 00 d0 00 98 00 00 06 9d 82 f8 40 08 08:19:27.481 READ FPDMA QUEUED

Error 175 [6] occurred at disk power-on lifetime: 27372 hours (1140 days + 12 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 00 00 00 06 9d 8c c0 40 00 Error: UNC at LBA = 0x069d8cc0 = 110988480

Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
60 00 98 00 40 00 00 06 9d 8c 58 40 08 08:19:23.000 READ FPDMA QUEUED
60 00 b0 00 38 00 00 06 9d 96 78 40 08 08:19:23.000 READ FPDMA QUEUED
60 01 00 00 30 00 00 06 9d 94 d0 40 08 08:19:22.993 READ FPDMA QUEUED
60 01 00 00 28 00 00 06 9d 97 28 40 08 08:19:22.968 READ FPDMA QUEUED
60 01 00 00 20 00 00 06 9d 83 c8 40 08 08:19:22.967 READ FPDMA QUEUED

Error 174 [5] occurred at disk power-on lifetime: 27315 hours (1138 days + 3 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 00 00 00 00 33 31 98 40 00 Error: UNC at LBA = 0x00333198 = 3355032

Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
60 00 20 00 50 00 00 00 33 31 80 40 08 00:59:19.970 READ FPDMA QUEUED
60 00 40 00 48 00 00 00 c2 8a 40 40 08 00:59:19.970 READ FPDMA QUEUED
60 00 20 00 40 00 00 00 33 31 60 40 08 00:59:19.969 READ FPDMA QUEUED
60 00 20 00 38 00 00 00 33 31 40 40 08 00:59:19.969 READ FPDMA QUEUED
60 00 40 00 30 00 00 00 c2 8a 00 40 08 00:59:19.969 READ FPDMA QUEUED

Error 173 [4] occurred at disk power-on lifetime: 27315 hours (1138 days + 3 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 00 00 00 00 33 42 c0 40 00 Error: UNC at LBA = 0x003342c0 = 3359424

Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
60 00 08 00 48 00 00 00 4b 72 b0 40 08 00:47:24.107 READ FPDMA QUEUED
60 00 08 00 20 00 00 00 3e af 70 40 08 00:47:22.086 READ FPDMA QUEUED
60 00 08 00 68 00 00 00 55 03 70 40 08 00:47:22.084 READ FPDMA QUEUED
60 00 08 00 d8 00 00 00 3c ab a8 40 08 00:47:22.084 READ FPDMA QUEUED
60 00 08 00 60 00 00 00 56 82 78 40 08 00:47:22.081 READ FPDMA QUEUED

Error 172 [3] occurred at disk power-on lifetime: 27271 hours (1136 days + 7 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 00 00 00 00 1c c9 e8 40 00 Error: UNC at LBA = 0x001cc9e8 = 1886696

Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
60 00 40 00 08 00 00 00 1c c9 c0 40 08 07:38:08.825 READ FPDMA QUEUED
60 00 40 00 00 00 00 00 1c c9 80 40 08 07:38:08.825 READ FPDMA QUEUED
60 00 40 00 f8 00 00 00 1c c9 40 40 08 07:38:08.825 READ FPDMA QUEUED
60 00 40 00 68 00 00 00 1c c9 00 40 08 07:38:08.824 READ FPDMA QUEUED
60 00 40 00 60 00 00 00 1c c8 c0 40 08 07:38:08.824 READ FPDMA QUEUED

Error 171 [2] occurred at disk power-on lifetime: 27199 hours (1133 days + 7 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 00 00 00 00 1c be 48 40 00 Error: UNC at LBA = 0x001cbe48 = 1883720

Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
60 00 08 00 88 00 00 00 4c 0b b8 40 08 00:05:44.965 READ FPDMA QUEUED
61 00 08 00 80 00 00 09 74 9a 40 40 08 00:05:44.744 WRITE FPDMA QUEUED
61 00 10 00 78 00 00 09 74 95 10 40 08 00:05:44.744 WRITE FPDMA QUEUED
61 00 08 00 70 00 00 09 74 30 40 40 08 00:05:44.744 WRITE FPDMA QUEUED
61 00 08 00 68 00 00 08 f4 30 68 40 08 00:05:44.744 WRITE FPDMA QUEUED

Error 170 [1] occurred at disk power-on lifetime: 27195 hours (1133 days + 3 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 00 00 00 00 1c 86 b8 40 00 Error: UNC at LBA = 0x001c86b8 = 1869496

Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
60 00 08 00 78 00 00 00 1c 86 b8 40 08 08:08:00.422 READ FPDMA QUEUED
60 00 08 00 70 00 00 00 1c 0a 90 40 08 08:08:00.422 READ FPDMA QUEUED
60 00 08 00 b8 00 00 00 1c 8c d0 40 08 08:08:00.421 READ FPDMA QUEUED
60 00 08 00 b0 00 00 00 1c 8d 40 40 08 08:08:00.421 READ FPDMA QUEUED
60 00 08 00 a8 00 00 00 1c 0b c0 40 08 08:08:00.421 READ FPDMA QUEUED

Error 169 [0] occurred at disk power-on lifetime: 27191 hours (1132 days + 23 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 00 00 00 00 34 66 78 40 00 Error: UNC at LBA = 0x00346678 = 3434104

Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
60 00 20 00 78 00 00 00 34 66 60 40 08 04:04:37.983 READ FPDMA QUEUED
60 00 20 00 70 00 00 00 14 ff 80 40 08 04:04:37.982 READ FPDMA QUEUED
60 00 10 00 68 00 00 00 14 b9 c0 40 08 04:04:37.982 READ FPDMA QUEUED
60 00 18 00 60 00 00 00 14 b8 c0 40 08 04:04:37.982 READ FPDMA QUEUED
60 00 08 00 58 00 00 00 14 b6 48 40 08 04:04:37.982 READ FPDMA QUEUED

Error 168 [23] occurred at disk power-on lifetime: 27103 hours (1129 days + 7 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 00 00 00 10 22 8d 38 40 00 Error: UNC at LBA = 0x10228d38 = 270699832

Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
60 02 b8 00 08 00 00 10 22 91 48 40 08 03:11:37.346 READ FPDMA QUEUED
60 05 48 00 00 00 00 10 22 8c 00 40 08 03:11:37.346 READ FPDMA QUEUED
60 04 00 00 f8 00 00 10 22 88 00 40 08 03:11:37.344 READ FPDMA QUEUED
60 04 00 00 98 00 00 10 22 84 00 40 08 03:11:37.326 READ FPDMA QUEUED
61 00 68 00 f0 00 00 09 25 d4 40 40 08 03:11:37.324 WRITE FPDMA QUEUED

Error 167 [22] occurred at disk power-on lifetime: 27096 hours (1129 days + 0 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 00 00 00 06 9e f5 18 40 00 Error: WP at LBA = 0x069ef518 = 111080728

Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
61 00 20 00 48 00 00 02 56 d8 88 40 08 04:01:07.953 WRITE FPDMA QUEUED
61 00 08 00 40 00 00 02 56 d8 78 40 08 04:01:07.953 WRITE FPDMA QUEUED
61 00 18 00 38 00 00 02 56 d7 d0 40 08 04:01:07.953 WRITE FPDMA QUEUED
61 00 18 00 30 00 00 02 56 d7 b0 40 08 04:01:07.953 WRITE FPDMA QUEUED
61 00 30 00 28 00 00 02 56 d7 50 40 08 04:01:07.953 WRITE FPDMA QUEUED

Error 166 [21] occurred at disk power-on lifetime: 27096 hours (1129 days + 0 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 00 00 00 06 9e f5 18 40 00 Error: UNC at LBA = 0x069ef518 = 111080728

Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
60 04 78 00 48 00 00 06 9e f6 00 40 08 04:01:02.074 READ FPDMA QUEUED
60 06 00 00 40 00 00 06 9e f0 00 40 08 04:01:02.072 READ FPDMA QUEUED
60 04 00 00 38 00 00 06 9a 2c 00 40 08 04:01:02.072 READ FPDMA QUEUED
60 0a 00 00 30 00 00 06 9a 22 00 40 08 04:01:02.064 READ FPDMA QUEUED
61 00 48 00 28 00 00 00 2f 3a 18 40 08 04:01:02.058 WRITE FPDMA QUEUED

Error 165 [20] occurred at disk power-on lifetime: 27055 hours (1127 days + 7 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 00 00 00 00 33 19 c0 40 00 Error: WP at LBA = 0x003319c0 = 3348928

Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
61 00 28 00 00 00 00 07 b9 f9 d8 40 08 09:44:01.240 WRITE FPDMA QUEUED
60 00 10 00 30 00 00 00 25 2c 80 40 08 09:44:00.825 READ FPDMA QUEUED
60 00 20 00 f0 00 00 00 23 d3 a0 40 08 09:43:59.825 READ FPDMA QUEUED
60 00 40 00 28 00 00 00 33 19 c0 40 08 09:43:58.803 READ FPDMA QUEUED
60 00 40 00 e8 00 00 00 0e c9 c0 40 08 09:43:58.767 READ FPDMA QUEUED

Error 164 [19] occurred at disk power-on lifetime: 27055 hours (1127 days + 7 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 00 00 00 00 1c a7 68 40 00 Error: UNC at LBA = 0x001ca768 = 1877864

Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
60 00 08 00 50 00 00 00 1c a7 68 40 08 09:16:49.197 READ FPDMA QUEUED
60 00 08 00 e8 00 00 00 16 e8 a8 40 08 09:16:49.197 READ FPDMA QUEUED
61 00 88 00 f0 00 00 09 bb 4d 68 40 08 09:16:49.197 WRITE FPDMA QUEUED
60 00 08 00 e0 00 00 00 1e 14 c8 40 08 09:16:49.197 READ FPDMA QUEUED
61 00 a0 00 d8 00 00 12 09 6f 00 40 08 09:16:49.188 WRITE FPDMA QUEUED

Error 163 [18] occurred at disk power-on lifetime: 26948 hours (1122 days + 20 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 00 00 00 00 1c be 48 40 00 Error: UNC at LBA = 0x001cbe48 = 1883720

Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
60 00 10 00 00 00 00 0a 1d 20 d0 40 08 00:38:27.614 READ FPDMA QUEUED
60 00 18 00 f8 00 00 0a 1d 20 b0 40 08 00:38:27.614 READ FPDMA QUEUED
60 00 08 00 b8 00 00 0a 1d 20 98 40 08 00:38:27.614 READ FPDMA QUEUED
60 00 50 00 b0 00 00 0a 1d 20 20 40 08 00:38:27.614 READ FPDMA QUEUED
61 00 48 00 a0 00 00 09 d3 8c 90 40 08 00:38:27.538 WRITE FPDMA QUEUED

Error 162 [17] occurred at disk power-on lifetime: 26948 hours (1122 days + 20 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 00 00 00 00 1c 9b c8 40 00 Error: WP at LBA = 0x001c9bc8 = 1874888

Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
61 00 08 00 f8 00 00 09 74 30 40 40 08 00:38:04.517 WRITE FPDMA QUEUED
61 00 08 00 b8 00 00 07 36 d0 30 40 08 00:38:04.517 WRITE FPDMA QUEUED
61 00 08 00 b0 00 00 07 35 c7 a8 40 08 00:38:04.517 WRITE FPDMA QUEUED
61 00 08 00 a8 00 00 07 34 ae 60 40 08 00:38:04.517 WRITE FPDMA QUEUED
61 00 08 00 a0 00 00 07 34 53 00 40 08 00:38:04.517 WRITE FPDMA QUEUED

Error 161 [16] occurred at disk power-on lifetime: 26881 hours (1120 days + 1 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 00 00 00 00 1c 92 58 40 00 Error: UNC at LBA = 0x001c9258 = 1872472

Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
60 00 10 00 30 00 00 00 53 72 f0 40 08 03:20:43.326 READ FPDMA QUEUED
60 00 20 00 90 00 00 00 53 e0 e0 40 08 03:20:43.326 READ FPDMA QUEUED
60 00 10 00 28 00 00 00 53 8b 30 40 08 03:20:43.326 READ FPDMA QUEUED
60 00 20 00 88 00 00 00 53 dc a0 40 08 03:20:43.326 READ FPDMA QUEUED
60 00 10 00 80 00 00 00 53 dc 80 40 08 03:20:43.325 READ FPDMA QUEUED

Error 160 [15] occurred at disk power-on lifetime: 26703 hours (1112 days + 15 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 00 00 00 01 60 0a 58 40 00 Error: UNC at LBA = 0x01600a58 = 23071320

Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
60 00 08 00 68 00 00 01 60 0a 58 40 08 03:55:46.172 READ FPDMA QUEUED
61 00 38 00 00 00 00 09 c8 3d 98 40 08 03:55:46.172 WRITE FPDMA QUEUED
61 00 08 00 f0 00 00 01 46 74 10 40 08 03:55:46.172 WRITE FPDMA QUEUED
61 00 08 00 e8 00 00 01 bc a8 10 40 08 03:55:46.172 WRITE FPDMA QUEUED
61 00 08 00 e0 00 00 0e 0d 78 10 40 08 03:55:46.172 WRITE FPDMA QUEUED

Error 159 [14] occurred at disk power-on lifetime: 26703 hours (1112 days + 15 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 00 00 00 01 60 0a 58 40 00 Error: WP at LBA = 0x01600a58 = 23071320

Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
61 00 08 00 d8 00 00 0e 0d 78 10 40 08 03:55:43.357 WRITE FPDMA QUEUED
61 00 08 00 d0 00 00 01 bc a8 10 40 08 03:55:43.357 WRITE FPDMA QUEUED
61 00 08 00 c8 00 00 01 46 74 10 40 08 03:55:43.357 WRITE FPDMA QUEUED
61 00 38 00 a8 00 00 09 c8 3d 98 40 08 03:55:43.264 WRITE FPDMA QUEUED
60 00 08 00 a0 00 00 01 60 0a 58 40 08 03:55:42.486 READ FPDMA QUEUED

Error 158 [13] occurred at disk power-on lifetime: 26703 hours (1112 days + 15 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 00 00 00 01 60 0a 58 40 00 Error: UNC at LBA = 0x01600a58 = 23071320

Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
60 01 00 00 50 00 00 01 60 09 80 40 08 03:55:38.282 READ FPDMA QUEUED
60 00 80 00 48 00 00 01 60 09 00 40 08 03:55:38.282 READ FPDMA QUEUED
60 00 80 00 40 00 00 01 60 08 80 40 08 03:55:38.281 READ FPDMA QUEUED
60 01 00 00 38 00 00 01 60 07 80 40 08 03:55:38.281 READ FPDMA QUEUED
60 00 80 00 30 00 00 01 60 07 00 40 08 03:55:38.281 READ FPDMA QUEUED

Error 157 [12] occurred at disk power-on lifetime: 26703 hours (1112 days + 15 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 00 00 00 01 5f f3 10 40 00 Error: UNC at LBA = 0x015ff310 = 23065360

Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
60 01 00 00 78 00 00 09 52 42 60 40 08 03:55:33.276 READ FPDMA QUEUED
61 00 18 00 70 00 00 0f 8c 14 e8 40 08 03:55:33.275 WRITE FPDMA QUEUED
60 00 08 00 f0 00 00 01 5f f3 10 40 08 03:55:33.274 READ FPDMA QUEUED
61 00 10 00 c8 00 00 0f 8c 10 d0 40 08 03:55:33.274 WRITE FPDMA QUEUED
61 00 48 00 b8 00 00 0f 8c 10 f8 40 08 03:55:33.274 WRITE FPDMA QUEUED

Error 156 [11] occurred at disk power-on lifetime: 26703 hours (1112 days + 15 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 00 00 00 01 5f f3 10 40 00 Error: WP at LBA = 0x015ff310 = 23065360

Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
61 00 58 00 b0 00 00 09 c8 3d 00 40 08 03:55:31.338 WRITE FPDMA QUEUED
60 00 08 00 48 00 00 01 5f f3 10 40 08 03:55:28.566 READ FPDMA QUEUED
61 00 10 00 40 00 00 06 39 74 40 40 08 03:55:26.528 WRITE FPDMA QUEUED
61 00 08 00 c0 00 00 0f 74 30 18 40 08 03:55:26.225 WRITE FPDMA QUEUED
61 00 08 00 b8 00 00 0f 34 30 58 40 08 03:55:26.225 WRITE FPDMA QUEUED

Error 155 [10] occurred at disk power-on lifetime: 26703 hours (1112 days + 15 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 00 00 00 01 5f f3 10 40 00 Error: WP at LBA = 0x015ff310 = 23065360

Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
61 00 78 00 70 00 00 0b 46 bc 28 40 08 03:53:32.807 WRITE FPDMA QUEUED
61 00 10 00 a0 00 00 00 01 cf 30 40 08 03:53:29.839 WRITE FPDMA QUEUED
60 00 08 00 10 00 00 01 5f f3 10 40 08 03:53:29.715 READ FPDMA QUEUED
60 00 30 00 98 00 00 02 58 3b 00 40 08 03:53:29.708 READ FPDMA QUEUED
60 00 08 00 90 00 00 02 58 3a e0 40 08 03:53:29.708 READ FPDMA QUEUED




  


2. Re: HD Apresenta Defeito - Log Gsmartcontrol

Henrique
Henrique-RJ

(usa Outra)

Enviado em 22/06/2022 - 20:02h

Tem certeza que o ruído vem do HD ?

O ruído pode estar vindo do cooler do processador ou da fonte fazendo você pensar que vem do HD.



3. Re: HD Apresenta Defeito - Log Gsmartcontrol

leandro peçanha scardua
leandropscardua

(usa Ubuntu)

Enviado em 22/06/2022 - 22:37h

- Seu hd teve 178 problemas, mas o log só mostrou 24 (Device Error Count: 178 (device log contains only the most recent 24 errors))
- desses 24, os erros estão concentrados em 04 regiões (entre 900Mb e 2Gb, entre 52Gb e 53Gb, entre 10Gb e 11Gb e em 129 Gb). Vou mandar os calculos abaixo p vc revisar se eu errei alguma coisa
- há dois tipos de erro: Error: UNC at LBA | Error: WP at LBA (o primeiro é de leitura e acho que é badblock, o segundo é de escrita e não sei o que pode ser)
- o disco tem 27372 hours (1140 days + 12 hours) de uso
- os últimos dias foram movimentados, com quase 01 problema por dia ((1141 days + 11 hours) / (1140 days + 12 hours)

o que fazer:
- backup dos dados e começar a providenciar outro disco
- rodar fdisk e ver em quais partições estão essas regiões e se alguma dessas regiões estiver na partição de swap, criar outra partição de swap mais pro fim do disco, habilitaá-la e apagar a partição de swap, deixando como espaço não alocado (mas só se houver setores defeituosos na área de swap). Você pode fazer isso para cada região, mas o relatório tem apenas 24 regiões de 178!!!!!!!!
- vc pode tentar mapear os blocos com problema c o comando badblocks, mas pode demorar bastante(muitas e muitas horas) ou pode zerar o hd com o comando dd e esperar que a controladora do hd remapeie para você.



calculo dos setores com setor de 512 bytes.
1869496 x 512 = 957181952 = 912,83 Mb
110988480 x 512 = 56826101760 = 52,92Gb
110985568 x 512 = 56824610816 = 52,92Gb
110988480 x 512 = 56826101760 = 52,92Gb
3355032 x 512 = 1717776384 = 1,59Gb
3359424 x 512 = 1720025088 = 1,60Gb
1886696 x 512 = 965988352 = 921,23Mb
1883720 x 512 = 964464640 = 919,78Mb
1869496 x 512 = 957181952 = 912,83Mb
3434104 x 512 = 1758261248 = 1,63Gb
270699832 x 512 = 138598313984 = 129,07Gb
111080728 x 512 = 56873332736 = 52,96Gb
111080728 x 512 = 56873332736 = 52,96Gb
3348928 x 512 = 1714651136 = 1,59Gb
1877864 x 512 = 961466368 = 916,92Mb
1883720 x 512 = 964464640 = 919,78Mb
1874888 x 512 = 959942656 = 915,47Mb
1872472 x 512 = 958705664 = 914,29Mb
23071320 x 512 = 11812515840 = 11,00Gb
23071320 x 512 = 11812515840 = 11,00Gb
23071320 x 512 = 11812515840 = 11,00Gb
23065360 x 512 = 11809464320 = 10,99Gb
23065360 x 512 = 11809464320 = 10,99Gb
23065360 x 512 = 11809464320 = 10,99Gb



4. Re: HD Apresenta Defeito - Log Gsmartcontrol

Henrique
Henrique-RJ

(usa Outra)

Enviado em 23/06/2022 - 07:31h

Se o ruído estiver vindo realmente do HD, tente trocar de cabo e de porta SATA pois esses erros podem ser causados por mal contato dos mesmos. Depois avalie se resolveu.



5. Re: HD Apresenta Defeito - Log Gsmartcontrol

Clodoaldo Santos
clodoaldops

(usa Linux Mint)

Enviado em 23/06/2022 - 08:46h

-se está com medo de perder seus dados faça backup urgente num HD externo
-depois tente resolver problema do HD do seu PC
-Gsmartcontrol dando alerta é melhor não dar bobeira




6. Re: HD Apresenta Defeito - Log Gsmartcontrol

Leandro Silva
ExtremeLick

(usa Ubuntu)

Enviado em 23/06/2022 - 08:55h

Henrique-RJ escreveu:

Tem certeza que o ruído vem do HD ?

O ruído pode estar vindo do cooler do processador ou da fonte fazendo você pensar que vem do HD.


Sim, o ruído realmente é do HD. Eu não relatei no post, mas o que aconteceu foi o seguinte:

- Caiu energia durante à tarde, aí aparentemente meu PC estava normal (pois o usei por várias horas sem nada acontecer), mas quando foi de madrugada ele começou ficar em loop desligando e ligando, em alguns momentos ele ficava ligado por alguns minutos. Surgiu até mesmo um problema que ao plugar qualquer coisa na entrada usb o computador desligava imediatamente, pensei que fosse fonte ou placa mãe, mas como eu já pensava em comprar uma fonte, fiz isso, parou os desligamentos e o problema ao usar usb. O problema principal creio que de fato fosse a fonte. Porém, o HD começou com esse barulho, além de que é possível sentir quando ele dá tipo uma rápida travada ao fazer determinadas ações, fora o fato do software não conseguir analisar os erros no HD. Sei que o Gsmartcontrol informa que ele fez a leitura com erros, e mostra o valor de 10%. Tenho que tirar prints.


Outra dúvida que fica, será que corro risco de além de ter danificado a fonte e o HD, outros componentes possam ter sido comprometidos: Placa mãe, processador, memória? é muito azar!!!

Agradeço a ajuda de todos!!!


7. Re: HD Apresenta Defeito - Log Gsmartcontrol

Leandro Silva
ExtremeLick

(usa Ubuntu)

Enviado em 23/06/2022 - 09:03h


Henrique-RJ escreveu:

Se o ruído estiver vindo realmente do HD, tente trocar de cabo e de porta SATA pois esses erros podem ser causados por mal contato dos mesmos. Depois avalie se resolveu.


Farei o teste aqui. Muito Obrigado.


8. Re: HD Apresenta Defeito - Log Gsmartcontrol

Leandro Silva
ExtremeLick

(usa Ubuntu)

Enviado em 23/06/2022 - 09:10h


leandropscardua escreveu:

- Seu hd teve 178 problemas, mas o log só mostrou 24 (Device Error Count: 178 (device log contains only the most recent 24 errors))
- desses 24, os erros estão concentrados em 04 regiões (entre 900Mb e 2Gb, entre 52Gb e 53Gb, entre 10Gb e 11Gb e em 129 Gb). Vou mandar os calculos abaixo p vc revisar se eu errei alguma coisa
- há dois tipos de erro: Error: UNC at LBA | Error: WP at LBA (o primeiro é de leitura e acho que é badblock, o segundo é de escrita e não sei o que pode ser)
- o disco tem 27372 hours (1140 days + 12 hours) de uso
- os últimos dias foram movimentados, com quase 01 problema por dia ((1141 days + 11 hours) / (1140 days + 12 hours)

o que fazer:
- backup dos dados e começar a providenciar outro disco
- rodar fdisk e ver em quais partições estão essas regiões e se alguma dessas regiões estiver na partição de swap, criar outra partição de swap mais pro fim do disco, habilitaá-la e apagar a partição de swap, deixando como espaço não alocado (mas só se houver setores defeituosos na área de swap). Você pode fazer isso para cada região, mas o relatório tem apenas 24 regiões de 178!!!!!!!!
- vc pode tentar mapear os blocos com problema c o comando badblocks, mas pode demorar bastante(muitas e muitas horas) ou pode zerar o hd com o comando dd e esperar que a controladora do hd remapeie para você.



calculo dos setores com setor de 512 bytes.
1869496 x 512 = 957181952 = 912,83 Mb
110988480 x 512 = 56826101760 = 52,92Gb
110985568 x 512 = 56824610816 = 52,92Gb
110988480 x 512 = 56826101760 = 52,92Gb
3355032 x 512 = 1717776384 = 1,59Gb
3359424 x 512 = 1720025088 = 1,60Gb
1886696 x 512 = 965988352 = 921,23Mb
1883720 x 512 = 964464640 = 919,78Mb
1869496 x 512 = 957181952 = 912,83Mb
3434104 x 512 = 1758261248 = 1,63Gb
270699832 x 512 = 138598313984 = 129,07Gb
111080728 x 512 = 56873332736 = 52,96Gb
111080728 x 512 = 56873332736 = 52,96Gb
3348928 x 512 = 1714651136 = 1,59Gb
1877864 x 512 = 961466368 = 916,92Mb
1883720 x 512 = 964464640 = 919,78Mb
1874888 x 512 = 959942656 = 915,47Mb
1872472 x 512 = 958705664 = 914,29Mb
23071320 x 512 = 11812515840 = 11,00Gb
23071320 x 512 = 11812515840 = 11,00Gb
23071320 x 512 = 11812515840 = 11,00Gb
23065360 x 512 = 11809464320 = 10,99Gb
23065360 x 512 = 11809464320 = 10,99Gb
23065360 x 512 = 11809464320 = 10,99Gb


Muito Obrigado.


9. Re: HD Apresenta Defeito - Log Gsmartcontrol

Henrique
Henrique-RJ

(usa Outra)

Enviado em 23/06/2022 - 09:16h

Isso já está parecendo indício de curto no sistema.

Eu faria um teste com outra fonte boa por uns dias nem que fosse emprestada até por alguma assistência técnica.



10. Re: HD Apresenta Defeito - Log Gsmartcontrol

Leandro Silva
ExtremeLick

(usa Ubuntu)

Enviado em 23/06/2022 - 10:47h


Henrique-RJ escreveu:

Isso já está parecendo indício de curto no sistema.

Eu faria um teste com outra fonte boa por uns dias nem que fosse emprestada até por alguma assistência técnica.


Fonte foi trocada já, comprei uma nova. Mas a queda de energia provavelmente também afetou o HD. Agora meu medo é de além desses dois itens outros terem sido danificados de alguma forma, embora só estou notando o HD.


11. Re: HD Apresenta Defeito - Log Gsmartcontrol

Henrique
Henrique-RJ

(usa Outra)

Enviado em 23/06/2022 - 11:06h


ExtremeLick escreveu:
Fonte foi trocada já, comprei uma nova. Mas a queda de energia provavelmente também afetou o HD. Agora meu medo é de além desses dois itens outros terem sido danificados de alguma forma, embora só estou notando o HD.


Testa o HD com outro cabo da fonte e com o cabo de dados SATA invertido e em outra porta SATA da placa-mãe e avalia como ficou.








Patrocínio

Site hospedado pelo provedor RedeHost.
Linux banner
Linux banner

Destaques

Artigos

Dicas

Tópicos

Top 10 do mês

Scripts