(Erro de Inicialização no Ubuntu 20.04) Error: Failure Reading Sector 0x100800 from hd1 [RESOLVIDO]

Buckminster
(usa Debian)

Enviado em 29/07/2021 - 02:22h

Aguarde o teste terminar.

Vicking
(usa Ubuntu)

Enviado em 29/07/2021 - 19:42h

Ontem por volta de umas 02:13 inicializei o teste que foi passado pelo SO que iria estar pronto umas 04:27 da manhã mas acabei desistindo por não ter notado nenhuma atualização até umas 03:47, agora estou executando novamente o SMART inicializado umas 17:30 e pouco da tarde e está assim:

ubuntu@ubuntu:~$ sudo smartctl -a /dev/sda 

smartctl 7.1 2019-12-30 r5022 [x86_64-linux-5.4.0-42-generic] (local build)

Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org



=== START OF INFORMATION SECTION ===

Model Family:     Seagate Samsung SpinPoint M8 (AF)

Device Model:     ST640LM001 HN-M640MBB

Serial Number:    S2ULJ9DC609222

LU WWN Device Id: 5 0004cf 207c6032e

Firmware Version: 2AR10002

User Capacity:    640,135,028,736 bytes [640 GB]

Sector Sizes:     512 bytes logical, 4096 bytes physical

Rotation Rate:    5400 rpm

Form Factor:      2.5 inches

Device is:        In smartctl database [for details use: -P show]

ATA Version is:   ATA8-ACS T13/1699-D revision 6

SATA Version is:  SATA 3.0, 3.0 Gb/s (current: 3.0 Gb/s)

Local Time is:    Thu Jul 29 22:12:00 2021 UTC

SMART support is: Available - device has SMART capability.

SMART support is: Enabled



=== START OF READ SMART DATA SECTION ===

SMART overall-health self-assessment test result: PASSED



General SMART Values:

Offline data collection status:  (0x00)	Offline data collection activity

					was never started.

					Auto Offline Data Collection: Disabled.

Self-test execution status:      ( 121)	The previous self-test completed having

					the read element of the test failed.

Total time to complete Offline 

data collection: 		( 8520) seconds.

Offline data collection

capabilities: 			 (0x5b) SMART execute Offline immediate.

					Auto Offline data collection on/off support.

					Suspend Offline collection upon new

					command.

					Offline surface scan supported.

					Self-test supported.

					No Conveyance Self-test supported.

					Selective Self-test supported.

SMART capabilities:            (0x0003)	Saves SMART data before entering

					power-saving mode.

					Supports SMART auto save timer.

Error logging capability:        (0x01)	Error logging supported.

					General Purpose Logging supported.

Short self-test routine 

recommended polling time: 	 (   2) minutes.

Extended self-test routine

recommended polling time: 	 ( 142) minutes.

SCT capabilities: 	       (0x003f)	SCT Status supported.

					SCT Error Recovery Control supported.

					SCT Feature Control supported.

					SCT Data Table supported.



SMART Attributes Data Structure revision number: 16

Vendor Specific SMART Attributes with Thresholds:

ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE

  1 Raw_Read_Error_Rate     0x002f   100   100   051    Pre-fail  Always       -       4496

  2 Throughput_Performance  0x0026   252   252   000    Old_age   Always       -       0

  3 Spin_Up_Time            0x0023   089   089   025    Pre-fail  Always       -       3471

  4 Start_Stop_Count        0x0032   087   087   000    Old_age   Always       -       13252

  5 Reallocated_Sector_Ct   0x0033   252   252   010    Pre-fail  Always       -       0

  7 Seek_Error_Rate         0x002e   252   252   051    Old_age   Always       -       0

  8 Seek_Time_Performance   0x0024   252   252   015    Old_age   Offline      -       0

  9 Power_On_Hours          0x0032   100   100   000    Old_age   Always       -       18851

 10 Spin_Retry_Count        0x0032   252   252   051    Old_age   Always       -       0

 11 Calibration_Retry_Count 0x0032   086   086   000    Old_age   Always       -       14750

 12 Power_Cycle_Count       0x0032   087   087   000    Old_age   Always       -       13194

191 G-Sense_Error_Rate      0x0022   100   100   000    Old_age   Always       -       576

192 Power-Off_Retract_Count 0x0022   252   252   000    Old_age   Always       -       0

194 Temperature_Celsius     0x0002   064   051   000    Old_age   Always       -       28 (Min/Max 15/49)

195 Hardware_ECC_Recovered  0x003a   100   100   000    Old_age   Always       -       0

196 Reallocated_Event_Count 0x0032   252   252   000    Old_age   Always       -       0

197 Current_Pending_Sector  0x0032   100   100   000    Old_age   Always       -       1

198 Offline_Uncorrectable   0x0030   252   252   000    Old_age   Offline      -       0

199 UDMA_CRC_Error_Count    0x0036   200   200   000    Old_age   Always       -       0

200 Multi_Zone_Error_Rate   0x002a   100   100   000    Old_age   Always       -       2444

223 Load_Retry_Count        0x0032   086   086   000    Old_age   Always       -       14750

225 Load_Cycle_Count        0x0032   094   094   000    Old_age   Always       -       68532

254 Free_Fall_Sensor        0x0032   100   100   000    Old_age   Always       -       275



SMART Error Log Version: 1

ATA Error Count: 2643 (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 2643 occurred at disk power-on lifetime: 18850 hours (785 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 00 08 10 e0  Error: UNC 8 sectors at LBA = 0x00100800 = 1050624



  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 00 08 10 e0 00      00:00:06.070  READ DMA

  c8 00 08 00 08 00 e0 00      00:00:06.070  READ DMA

  ef 10 02 00 00 00 a0 00      00:00:06.070  SET FEATURES [Enable SATA feature]

  27 00 00 00 00 00 e0 00      00:00:06.070  READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]

  ec 00 00 00 00 00 a0 00      00:00:06.070  IDENTIFY DEVICE



Error 2642 occurred at disk power-on lifetime: 18850 hours (785 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 00 08 10 e0  Error: UNC 8 sectors at LBA = 0x00100800 = 1050624



  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 00 08 10 e0 00      00:00:06.068  READ DMA

  c8 00 08 f0 07 10 e0 00      00:00:06.068  READ DMA

  25 00 08 f0 7f 85 e0 00      00:00:06.068  READ DMA EXT

  c8 00 08 80 07 10 e0 00      00:00:06.068  READ DMA

  25 00 08 80 7f 85 e0 00      00:00:06.068  READ DMA EXT



Error 2641 occurred at disk power-on lifetime: 18850 hours (785 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 00 08 10 e0  Error: UNC 8 sectors at LBA = 0x00100800 = 1050624



  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 00 08 10 e0 00      00:00:06.036  READ DMA

  ef 10 02 00 00 00 a0 00      00:00:06.036  SET FEATURES [Enable SATA feature]

  27 00 00 00 00 00 e0 00      00:00:06.036  READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]

  ec 00 00 00 00 00 a0 00      00:00:06.036  IDENTIFY DEVICE

  ef 03 46 00 00 00 a0 00      00:00:06.036  SET FEATURES [Set transfer mode]



Error 2640 occurred at disk power-on lifetime: 18850 hours (785 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 00 08 10 e0  Error: UNC 8 sectors at LBA = 0x00100800 = 1050624



  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 00 08 10 e0 00      00:00:06.034  READ DMA

  25 00 08 f0 7f 85 e0 00      00:00:06.034  READ DMA EXT

  25 00 08 80 7f 85 e0 00      00:00:06.034  READ DMA EXT

  c8 00 20 08 00 00 e0 00      00:00:06.034  READ DMA

  c8 00 08 00 00 00 e0 00      00:00:06.034  READ DMA



Error 2639 occurred at disk power-on lifetime: 18850 hours (785 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 00 08 10 e0  Error: UNC 8 sectors at LBA = 0x00100800 = 1050624



  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 00 08 10 e0 00      00:00:06.033  READ DMA

  ef 10 02 00 00 00 a0 00      00:00:06.033  SET FEATURES [Enable SATA feature]

  27 00 00 00 00 00 e0 00      00:00:06.033  READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]

  ec 00 00 00 00 00 a0 00      00:00:06.033  IDENTIFY DEVICE

  ef 03 46 00 00 00 a0 00      00:00:06.033  SET FEATURES [Set transfer mode]



SMART Self-test log structure revision number 1

Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error

# 1  Extended offline    Completed: read failure       90%     18850         1050624

# 2  Extended offline    Completed: read failure       90%     18850         1050624

# 3  Extended offline    Completed: read failure       90%     18850         1050624

# 4  Extended offline    Completed: read failure       90%     18846         1050624

# 5  Extended offline    Completed: read failure       90%     18846         1050624

# 6  Extended offline    Completed: read failure       90%     18844         1050624

# 7  Extended offline    Completed: read failure       90%     18844         1050624

# 8  Extended offline    Completed: read failure       90%     18844         1050624



SMART Selective self-test log data structure revision number 0

Note: revision number not 1 implies that no selective self-test has ever been run

 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS

    1        0        0  Completed_read_failure [90% left] (0-65535)

    2        0        0  Not_testing

    3        0        0  Not_testing

    4        0        0  Not_testing

    5        0        0  Not_testing

Selective self-test flags (0x0):

  After scanning selected spans, do NOT read-scan remainder of disk.

If Selective self-test is pending on power-up, resume after 0 minute delay.

 

Test will complete after Thu Jul 29 23:04:27 2021 UTC 

mas notei que esse (1 0 0 Completed_read_failure [90% left] (0-65535)) não está saindo mais dessa quantia desde então até mesmo quando executei o teste ontem, isto é normal constar? o que só mudou foi quando executei este teste várias vezes após ter interrompido algumas vezes quando dei o comando: sudo smartctl -l selftest /dev/sda ... Como saber pelo terminal o término do teste? Hoje também ia instalar por cima da minha partição /dev/sda atual novamente uma formatação original de fábrica daí apareceu uma tela que até consta que a partição ainda mantém a mesma capacidade de tamanho e uso, seria uma boa idéia criar outra partição junto com essa corrompida para tentar resgatar os dados?

Por enquanto no resumo esse foi o resultado após ter inicializado e interrompido o teste algumas vezes por não ter notado o progresso:

ubuntu@ubuntu:~$ sudo smartctl -l selftest /dev/sda 

smartctl 7.1 2019-12-30 r5022 [x86_64-linux-5.4.0-42-generic] (local build)

Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org



=== 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

# 1  Extended offline    Completed: read failure       90%     18850         1050624

# 2  Extended offline    Completed: read failure       90%     18850         1050624

# 3  Extended offline    Completed: read failure       90%     18850         1050624

# 4  Extended offline    Completed: read failure       90%     18846         1050624

# 5  Extended offline    Completed: read failure       90%     18846         1050624

# 6  Extended offline    Completed: read failure       90%     18844         1050624

# 7  Extended offline    Completed: read failure       90%     18844         1050624

# 8  Extended offline    Completed: read failure       90%     18844         1050624

 

Daí agora (20:12) o teste terminou e está a mesma coisa aquela saída

leandropscardua
(usa Ubuntu)

Enviado em 29/07/2021 - 21:24h

A contagem Reallocated_Sector_Ct parece indicar a presença de badblocks. Tente este artigo
https://diolinux.com.br/tutoriais/verificando-badblocks-no-ubuntu.html
Dependendo do tamanho da partição o comando pode demorar, mas deixe rodar até o final.

Vicking
(usa Ubuntu)

Enviado em 29/07/2021 - 22:01h

Vi que há dois comandos a serem realizados para tal fim, que é um que somente lê e outro que lê, escreve e verifica. Qual dos dois eu executo?? Estou por enquanto executando o primeiro, quanto badblocks com certeza tem sim, tanto que quando executei um fsck no dev/sda2 ou no dev/sda ele não fez e só consegui fazer o fsck no dev/sda1.

leandropscardua
(usa Ubuntu)

Enviado em 29/07/2021 - 22:10h

Segue o artigo na ordem. Um comando q só lê executa mais rápido. Serve p diagnóstico rápido pq o comando completo pode demorar bastante (bastante mesmo).
Vc precisa desmontar o sistema de arquivo p rodar o fsck.

Vicking
(usa Ubuntu)

Enviado em 30/07/2021 - 00:26h

Eis o resultado do primeiro teste

ubuntu@ubuntu:~$ sudo badblocks -sv -c 1024 /dev/sda

Checking blocks 0 to 625131863

Checking for bad blocks (read-only test): 525312% done, 0:10 elapsed. (0/0/0 errors)

525313% done, 0:12 elapsed. (1/0/0 errors)

525314% done, 0:14 elapsed. (2/0/0 errors)

525315% done, 0:16 elapsed. (3/0/0 errors)

done                                                 

Pass completed, 4 bad blocks found. (4/0/0 errors)

 

Mas daí depois acabei executando o comando sudo e2fsck -l 32768 /dev/sda mas no meio da execução apareceram "infinitas" perguntas pedindo para eu dar yes relativo a fix em seções, mas acabei cancelando essa execução por ter achado estranho essa série de perguntas e refiz aquele comando sudo fsck -l /dev/sda e ele fez sozinho a limpeza dos badblocks! Felizmente consegui resolver o problema!! Estive assustado enquanto estive fazendo fsck pelas primeiras vezes achando que fosse físico o problema, mas que ótimo que foi lógico! Muito obrigado a todos aqui que me ajudaram!!

Buckminster
(usa Debian)

Enviado em 30/07/2021 - 16:48h

Ficou o registro de 5 ou 6 erros do tipo abaixo na inicialização do disco:
"Error 2640 occurred at disk power-on lifetime: 18850 hours (785 days + 10 hours) When the command that caused the error occurred, the device was active or idle."

Acredito que o problema, obviamente, foi causado pelos travamentos, desligamentos e reinicios forçados.
Por isso que eu estava achando estranho o fsck ter funcionado na /dev/sda1 e não na /dev/sda2.
Por isso a indicação de usar o SMART Data. Às vezes somente por mexer no hd com o SMART ou com o fsck mesmo que só para testes costuma resolver, é demorado, mas é melhor do que perder os dados.
Eu sempre mantenho backup dos dados mais importantes.
Bom que resolveu e não perdeu os dados.