Erros Random EXT4 FS

2

Estou tendo um problema com fio no meu laptop. Funciona bem, mas quase todas as horas a tela congela. Quando eu forçar o desligamento e iniciá-lo novamente, vejo problemas semelhantes a este:

Aúnicasoluçãoqueencontreiévirarolaptopporalgunssegundosantesdeiniciá-lonovamente.IssomeajudaavermeuUbuntufuncionarnormalmentesemessesproblemasdeFS.

Atualização:Estaéasaídasmartctl:

smartctl6.52016-01-24r4214[i686-linux-4.15.0-32-generic](localbuild)Copyright(C)2002-16,BruceAllen,ChristianFranke,www.smartmontools.org===STARTOFINFORMATIONSECTION===ModelFamily:SeagateLaptopSSHDDeviceModel:ST500LM000-SSHD-8GBSerialNumber:W761F5WCLUWWNDeviceId:5000c5007c440eb8FirmwareVersion:LIV5UserCapacity:500107862016bytes[500GB]SectorSizes:512byteslogical,4096bytesphysicalRotationRate:5400rpmFormFactor:2.5inchesDeviceis:Insmartctldatabase[fordetailsuse:-Pshow]ATAVersionis:ATA8-ACS,ACS-3T13/2161-Drevision3bSATAVersionis:SATA3.0,6.0Gb/s(current:6.0Gb/s)LocalTimeis:FriAug1714:37:512018CESTSMARTsupportis:Available-devicehasSMARTcapability.SMARTsupportis:Enabled===STARTOFREADSMARTDATASECTION===SMARToverall-healthself-assessmenttestresult:PASSEDSeevendor-specificAttributelistformarginalAttributes.GeneralSMARTValues:Offlinedatacollectionstatus:(0x82)Offlinedatacollectionactivitywascompletedwithouterror.AutoOfflineDataCollection:Enabled.Self-testexecutionstatus:(0)Thepreviousself-testroutinecompletedwithouterrorornoself-testhaseverbeenrun.TotaltimetocompleteOfflinedatacollection:(128)seconds.Offlinedatacollectioncapabilities:(0x7b)SMARTexecuteOfflineimmediate.AutoOfflinedatacollectionon/offsupport.SuspendOfflinecollectionuponnewcommand.Offlinesurfacescansupported.Self-testsupported.ConveyanceSelf-testsupported.SelectiveSelf-testsupported.SMARTcapabilities:(0x0003)SavesSMARTdatabeforeenteringpower-savingmode.SupportsSMARTautosavetimer.Errorloggingcapability:(0x01)Errorloggingsupported.GeneralPurposeLoggingsupported.Shortself-testroutinerecommendedpollingtime:(1)minutes.Extendedself-testroutinerecommendedpollingtime:(96)minutes.Conveyanceself-testroutinerecommendedpollingtime:(2)minutes.SCTcapabilities:(0x1081)SCTStatussupported.SMARTAttributesDataStructurerevisionnumber:10VendorSpecificSMARTAttributeswithThresholds:ID#ATTRIBUTE_NAMEFLAGVALUEWORSTTHRESHTYPEUPDATEDWHEN_FAILEDRAW_VALUE1Raw_Read_Error_Rate0x000f114099034Pre-failAlways-817590803Spin_Up_Time0x0003098098000Pre-failAlways-04Start_Stop_Count0x0032097097020Old_ageAlways-38655Reallocated_Sector_Ct0x0033100100010Pre-failAlways-07Seek_Error_Rate0x000f072060030Pre-failAlways-1637451956469Power_On_Hours0x0032080080000Old_ageAlways-17649(1151510)10Spin_Retry_Count0x0013100100097Pre-failAlways-012Power_Cycle_Count0x0032096096020Old_ageAlways-4175184End-to-End_Error0x0032096096099Old_ageAlwaysFAILING_NOW4187Reported_Uncorrect0x0032098098000Old_ageAlways-2188Command_Timeout0x0032100094000Old_ageAlways-25770197149189High_Fly_Writes0x003a100100000Old_ageAlways-0190Airflow_Temperature_Cel0x0022058036045Old_ageAlwaysIn_the_past42(Min/Max42/46#389)191G-Sense_Error_Rate0x0032100100000Old_ageAlways-0192Power-Off_Retract_Count0x0032100100000Old_ageAlways-1213193Load_Cycle_Count0x0032098098000Old_ageAlways-4834194Temperature_Celsius0x0022042064000Old_ageAlways-42(012000)196Reallocated_Event_Count0x000f080080030Pre-failAlways-17711(441040)197Current_Pending_Sector0x0012100100000Old_ageAlways-0198Offline_Uncorrectable0x0010100100000Old_ageOffline-0199UDMA_CRC_Error_Count0x003e200200000Old_ageAlways-0254Free_Fall_Sensor0x0032100100000Old_ageAlways-0SMARTErrorLogVersion:1ATAErrorCount:7(devicelogcontainsonlythemostrecentfiveerrors)CR=CommandRegister[HEX]FR=FeaturesRegister[HEX]SC=SectorCountRegister[HEX]SN=SectorNumberRegister[HEX]CL=CylinderLowRegister[HEX]CH=CylinderHighRegister[HEX]DH=Device/HeadRegister[HEX]DC=DeviceCommandRegister[HEX]ER=Errorregister[HEX]ST=Statusregister[HEX]Powered_Up_Timeismeasuredfrompoweron,andprintedasDDd+hh:mm:SS.ssswhereDD=days,hh=hours,mm=minutes,SS=sec,andsss=millisec.It"wraps" after 49.710 days.

Error 7 occurred at disk power-on lifetime: 16948 hours (706 days + 4 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      00:00:25.320  READ FPDMA QUEUED
  60 00 20 ff ff ff 4f 00      00:00:25.319  READ FPDMA QUEUED
  60 00 60 88 da 7f 41 00      00:00:25.309  READ FPDMA QUEUED
  60 00 20 ff ff ff 4f 00      00:00:25.288  READ FPDMA QUEUED
  60 00 08 ff ff ff 4f 00      00:00:25.284  READ FPDMA QUEUED

Error 6 occurred at disk power-on lifetime: 966 hours (40 days + 6 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 10 c5 a5 00  Error: UNC at LBA = 0x00a5c510 = 10863888

  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 88 79 42 43 00      00:00:18.239  READ FPDMA QUEUED
  60 00 08 80 79 42 43 00      00:00:18.239  READ FPDMA QUEUED
  60 00 a8 10 c8 84 40 00      00:00:18.237  READ FPDMA QUEUED
  60 00 08 78 79 42 43 00      00:00:18.237  READ FPDMA QUEUED
  60 00 00 e0 c6 84 40 00      00:00:18.237  READ FPDMA QUEUED

Error 5 occurred at disk power-on lifetime: 966 hours (40 days + 6 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 10 c5 a5 00  Error: UNC at LBA = 0x00a5c510 = 10863888

  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 28 00 48 f8 40 00      00:00:13.615  READ FPDMA QUEUED
  60 00 08 08 0e 44 40 00      00:00:13.609  READ FPDMA QUEUED
  60 00 18 60 d0 e6 40 00      00:00:13.608  READ FPDMA QUEUED
  60 00 08 b8 a8 e6 40 00      00:00:13.608  READ FPDMA QUEUED
  60 00 28 10 9b e6 40 00      00:00:13.607  READ FPDMA QUEUED

Error 4 occurred at disk power-on lifetime: 32 hours (1 days + 8 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 76 9d b6 01  Error: UNC at LBA = 0x01b69d76 = 28745078

  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 80 60 9d b6 41 00      00:01:10.856  READ FPDMA QUEUED
  61 00 08 68 89 59 40 00      00:01:10.747  WRITE FPDMA QUEUED
  61 00 08 88 f6 3c 40 00      00:01:10.747  WRITE FPDMA QUEUED
  2f 00 01 10 00 00 20 00      00:01:10.494  READ LOG EXT
  60 00 40 c8 25 4c 41 00      00:01:10.441  READ FPDMA QUEUED

Error 3 occurred at disk power-on lifetime: 32 hours (1 days + 8 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 76 9d b6 01  Error: UNC at LBA = 0x01b69d76 = 28745078

  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 80 60 9d b6 41 00      00:00:53.242  READ FPDMA QUEUED
  61 00 80 40 ba 44 41 00      00:00:53.241  WRITE FPDMA QUEUED
  61 00 10 10 f7 86 40 00      00:00:53.241  WRITE FPDMA QUEUED
  60 00 40 98 b7 1e 42 00      00:00:53.216  READ FPDMA QUEUED
  60 00 08 60 9d b6 41 00      00:00:53.169  READ FPDMA QUEUED

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Vendor (0x50)       Completed without error       00%         1         -

SMART Selective self-test log data structure revision number 1
 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  Not_testing
    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.

Eu fiz um FSCK na inicialização para consertar o problema, mas isso não ajudou. Você tem alguma solução ?

    
por 4m1nh4j1 17.08.2018 / 12:26

3 respostas

1

Backup imediatamente

Compre um HDD / SSD externo adicional e faça um backup completo do CloneZilla Live agora mesmo! A oferta inoperante de que seu disco está em perigo iminente de falha é o seguinte parâmetro:

184 End-to-End_Error 0x0032 096 096 099 Old_age Always FAILING_NOW 4

Especialmente como você tem esse problema há um mês: < Sabe-se que os HDDs não morrem imediatamente, mas dão um amplo aviso, como sons de cliques, erros aleatórios, ... enquanto os SSDs morrem repentinamente sem aviso, a menos que você meça regularmente o status SMART deles.

A regra básica para as unidades é:

  • HDDs morrem uma morte lenta e dolorosa como o câncer
  • SSDs morrem de repente, como um ataque cardíaco
por 18.08.2018 / 00:18
1

Impossível responder.

Se o seu sistema estiver instável e, portanto, incapaz de encerrar corretamente, ter erros no sistema de arquivos (de forma aleatória, já que isso depende da atividade do disco no momento da falha) deve ser considerado normal.

Este não é um problema do sistema de arquivos, e não um problema do fsck, você tem que consertar o que está causando o congelamento do sistema, em primeiro lugar.

    
por 17.08.2018 / 12:30
0

De acordo com a saída smartctl , sua unidade está falhando agora .

Faça um backup separado de tudo nele. Não sobrescreva quaisquer backups anteriores (alguns arquivos já podem estar corrompidos, não queremos sobrescrever o bom backup).

Em seguida, substitua a unidade por uma nova e comece a comparar o novo backup com o último backup válido conhecido para ver quanto foi destruído.

    
por 17.08.2018 / 18:04