Disco NTFS com erro em S.M.A.R.T

Question

Eu tenho um disco NTFS onde eu armazeno meus dados, depois de um problema com um adaptador IDE / SATA ruim (que estava desligando meu disco) o S.M.A.R.T está mostrando erros.

Eu quero saber o que mais preciso fazer para verificar e corrigir qualquer erro neste disco.

Eu usei o fsck para verificar o disco, mas não é para mim.

    andre@PITCAIRN:~$ sudo fsck /dev/sdb1
fsck from util-linux 2.20.1
Mounting volume... OK
Processing of $MFT and $MFTMirr completed successfully.
Checking the alternate boot sector... OK
NTFS volume version is 3.1.
NTFS partition /dev/sdb1 was processed successfully.

O S.M.A.R.T

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   115   099   006    Pre-fail  Always       -       95292924
  3 Spin_Up_Time            0x0003   100   100   000    Pre-fail  Always       -       0
  4 Start_Stop_Count        0x0032   097   097   020    Old_age   Always       -       3419
  5 Reallocated_Sector_Ct   0x0033   100   100   036    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x000f   067   060   030    Pre-fail  Always       -       5425551
  9 Power_On_Hours          0x0032   093   093   000    Old_age   Always       -       6345
 10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   099   099   020    Old_age   Always       -       1501
183 Runtime_Bad_Block       0x0032   100   100   000    Old_age   Always       -       0
184 End-to-End_Error        0x0032   100   100   099    Old_age   Always       -       0
187 Reported_Uncorrect      0x0032   046   046   000    Old_age   Always       -       54
188 Command_Timeout         0x0032   100   100   000    Old_age   Always       -       0
189 High_Fly_Writes         0x003a   100   100   000    Old_age   Always       -       0
190 Airflow_Temperature_Cel 0x0022   062   048   045    Old_age   Always       -       38 (Min/Max 31/39)
194 Temperature_Celsius     0x0022   038   052   000    Old_age   Always       -       38 (0 19 0 0 0)
195 Hardware_ECC_Recovered  0x001a   041   022   000    Old_age   Always       -       95292924
197 Current_Pending_Sector  0x0012   100   100   000    Old_age   Always       -       20
198 Offline_Uncorrectable   0x0010   100   100   000    Old_age   Offline      -       20
199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always       -       0
240 Head_Flying_Hours       0x0000   100   253   000    Old_age   Offline      -       96499325213315
241 Total_LBAs_Written      0x0000   100   253   000    Old_age   Offline      -       2999278438
242 Total_LBAs_Read         0x0000   100   253   000    Old_age   Offline      -       866573403

E o erro em S.M.A.R.T

SMART Error Log Version: 1
ATA Error Count: 54 (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 54 occurred at disk power-on lifetime: 6088 hours (253 days + 16 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 00 ff ff ff 0f  Error: UNC at LBA = 0x0fffffff = 268435455

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 00 08 ff ff ff 4f 00      10:17:38.985  READ FPDMA QUEUED
  60 00 08 ff ff ff 4f 00      10:17:38.983  READ FPDMA QUEUED
  60 00 08 ff ff ff 4f 00      10:17:38.971  READ FPDMA QUEUED
  60 00 08 ff ff ff 4f 00      10:17:38.970  READ FPDMA QUEUED
  60 00 08 ff ff ff 4f 00      10:17:38.970  READ FPDMA QUEUED

Error 53 occurred at disk power-on lifetime: 6088 hours (253 days + 16 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 00 ff ff ff 0f  Error: UNC at LBA = 0x0fffffff = 268435455

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 00 08 ff ff ff 4f 00      10:17:35.999  READ FPDMA QUEUED
  60 00 08 ff ff ff 4f 00      10:17:35.999  READ FPDMA QUEUED
  60 00 08 ff ff ff 4f 00      10:17:35.998  READ FPDMA QUEUED
  60 00 08 ff ff ff 4f 00      10:17:35.998  READ FPDMA QUEUED
  60 00 08 ff ff ff 4f 00      10:17:35.998  READ FPDMA QUEUED

Error 52 occurred at disk power-on lifetime: 6088 hours (253 days + 16 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 00 ff ff ff 0f  Error: UNC at LBA = 0x0fffffff = 268435455

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 00 08 ff ff ff 4f 00      10:17:29.920  READ FPDMA QUEUED
  27 00 00 00 00 00 e0 00      10:17:29.918  READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
  ec 00 00 00 00 00 a0 00      10:17:29.909  IDENTIFY DEVICE
  ef 03 45 00 00 00 a0 00      10:17:29.909  SET FEATURES [Set transfer mode]
  27 00 00 00 00 00 e0 00      10:17:29.909  READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]

Error 51 occurred at disk power-on lifetime: 6088 hours (253 days + 16 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 00 ff ff ff 0f  Error: UNC at LBA = 0x0fffffff = 268435455

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 00 08 ff ff ff 4f 00      10:17:27.106  READ FPDMA QUEUED
  27 00 00 00 00 00 e0 00      10:17:27.104  READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
  ec 00 00 00 00 00 a0 00      10:17:27.095  IDENTIFY DEVICE
  ef 03 45 00 00 00 a0 00      10:17:27.095  SET FEATURES [Set transfer mode]
  27 00 00 00 00 00 e0 00      10:17:27.095  READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]

Error 50 occurred at disk power-on lifetime: 6088 hours (253 days + 16 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 00 ff ff ff 0f  Error: UNC at LBA = 0x0fffffff = 268435455

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 00 08 ff ff ff 4f 00      10:17:24.293  READ FPDMA QUEUED
  60 00 08 ff ff ff 4f 00      10:17:24.279  READ FPDMA QUEUED
  60 00 08 ff ff ff 4f 00      10:17:24.279  READ FPDMA QUEUED
  60 00 08 ff ff ff 4f 00      10:17:24.279  READ FPDMA QUEUED
  60 00 08 ff ff ff 4f 00      10:17:24.279  READ FPDMA QUEUED

Estou executando o autoteste estendido neste disco com o UNMOUNTED.

    

Answer 1

Você tem 20 setores defeituosos na unidade. Eles podem simplesmente ter se tornado corruptos, por exemplo, devido à perda repentina de energia no meio de uma gravação. Você pode tentar escrever zeros para eles e ver se eles voltam. Você precisará identificar os números do setor em questão, que você pode ver no log de erros, o primeiro é 268435455. Primeiro, tente lê-lo para verificar se está ruim:

sudo dd if=/dev/sdb bs=512 of=/dev/null count=1 iflag=direct skip=268435455

Se esta é uma unidade de setor 4k, use 4096 para bs = em vez de 512. Isso deve dar um erro. Em caso afirmativo, escreva-o com zeros:

sudo dd if=/dev/zero bs=512 of=/dev/sdb seek=268435455 count=1 oflag=direct

Verifique o comando antes de apertar enter; se você não entender exatamente, você pode destruir dados.

Repita isso para cada um dos setores no log de erros e, em seguida, verifique o status do SMART novamente. A contagem pendente deve diminuir. Se a contagem realocada subir, os setores serão fisicamente danificados e você deverá substituir a unidade. Se não, deve estar bem. Você pode tentar executar o autoteste SMART longo para encontrar mais setores defeituosos.

    

Answer 2

Você já fez tudo o que é necessário para reparar a unidade. O SMART é um sistema de monitoramento que é um recurso do controlador de disco rígido, portanto, a única coisa que o sistema operacional faz é mostrar os dados coletados pelo sistema SMART. Você não pode redefini-la, portanto, se a SMART tiver detectado algo considerado errado, será lembrado para sempre. Os erros detectados pelo SMART não são necessariamente um sinal de uma falha na unidade, no entanto, é possível que realmente haja algo errado. Em qualquer caso, certifique-se de criar bons backups que você deve fazer de qualquer maneira.