J’ai un probleme avec mon serveur (laptop i3/3G/500G) qui refuse de fonctionner. lorsque je le redémarre, il me demande de faire un fsck manuel de sda6. ce que j’ai fait et j’ai pu le démarrer. après quelques heures il est devenu inaccessible.
j’ai reçu un tas de mail de smart statuant qu’il y a 2 secteurs instables.
j’ai effectué cette commande que j’ai vu sur le forum il y a 3 jours :
admin@home:~$ sudo smartctl -a /dev/sda
smartctl 6.6 2017-11-05 r4594 [x86_64-linux-4.19.0-16-amd64] (local build)
Copyright (C) 2002-17, Bruce Allen, Christian Franke, www.smartmontools.org=== START OF INFORMATION SECTION ===
Model Family: Seagate Momentus 5400.6
Device Model: ST9500325AS
Serial Number: 6VESTVXS
LU WWN Device Id: 5 000c50 0372d2ad7
Firmware Version: 0001SDM1
User Capacity: 500 107 862 016 bytes [500 GB]
Sector Size: 512 bytes logical/physical
Rotation Rate: 5400 rpm
Device is: In smartctl database [for details use: -P show]
ATA Version is: ATA8-ACS T13/1699-D revision 4
SATA Version is: SATA 2.6, 3.0 Gb/s
Local Time is: Thu Jun 24 20:30:24 2021 CEST
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
See vendor-specific Attribute list for marginal Attributes.General SMART Values:
Offline data collection status: (0x82) Offline data collection activity
was completed without error.
Auto Offline Data Collection: Enabled.
Self-test execution status: ( 0) The previous self-test routine completed
without error or no self-test has ever
been run.
Total time to complete Offline
data collection: ( 0) seconds.
Offline data collection
capabilities: (0x7b) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
Offline surface scan supported.
Self-test supported. 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: ( 1) minutes.
Extended self-test routine
recommended polling time: ( 142) minutes.
Conveyance self-test routine
recommended polling time: ( 2) minutes.
SCT capabilities: (0x103b) SCT Status supported.
SCT Error Recovery Control supported.
SCT Feature Control supported.
SCT Data Table supported.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 102 089 006 Pre-fail Always - 18108584
3 Spin_Up_Time 0x0003 098 098 000 Pre-fail Always - 0
4 Start_Stop_Count 0x0032 099 099 020 Old_age Always - 1698
5 Reallocated_Sector_Ct 0x0033 096 096 036 Pre-fail Always - 95
7 Seek_Error_Rate 0x000f 089 060 030 Pre-fail Always - 861843224
9 Power_On_Hours 0x0032 057 057 000 Old_age Always - 38076
10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 099 099 020 Old_age Always - 1423
184 End-to-End_Error 0x0032 100 100 099 Old_age Always - 0
187 Reported_Uncorrect 0x0032 001 001 000 Old_age Always - 577
188 Command_Timeout 0x0032 100 096 000 Old_age Always - 8590065687
189 High_Fly_Writes 0x003a 100 100 000 Old_age Always - 0
190 Airflow_Temperature_Cel 0x0022 060 032 045 Old_age Always In_the_past 40 (225 206 42 28 0)
191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 329
192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 103
193 Load_Cycle_Count 0x0032 037 037 000 Old_age Always - 126218
194 Temperature_Celsius 0x0022 040 068 000 Old_age Always - 40 (0 12 0 0 0)
195 Hardware_ECC_Recovered 0x001a 053 046 000 Old_age Always - 18108584
197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 2
198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 2
199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0
254 Free_Fall_Sensor 0x0032 100 100 000 Old_age Always - 0SMART Error Log Version: 1
ATA Error Count: 417 (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 417 occurred at disk power-on lifetime: 38075 hours (1586 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 SC SN CL CH DH
40 51 00 ff ff ff 0f Error: WP 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
61 00 68 ff ff ff 4f 00 3d+10:04:16.688 WRITE FPDMA QUEUED
60 00 08 ff ff ff 4f 00 3d+10:04:16.686 READ FPDMA QUEUED
ef 10 03 00 00 00 a0 00 3d+10:04:16.683 SET FEATURES [Enable SATA feature]
27 00 00 00 00 00 e0 00 3d+10:04:16.672 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
ec 00 00 00 00 00 a0 00 3d+10:04:16.670 IDENTIFY DEVICE
Error 416 occurred at disk power-on lifetime: 38075 hours (1586 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 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 10 ff ff ff 4f 00 3d+10:04:13.910 READ FPDMA QUEUED
60 00 08 ff ff ff 4f 00 3d+10:04:11.434 READ FPDMA QUEUED
60 00 08 ff ff ff 4f 00 3d+10:04:11.433 READ FPDMA QUEUED
60 00 08 ff ff ff 4f 00 3d+10:04:11.420 READ FPDMA QUEUED
60 00 08 ff ff ff 4f 00 3d+10:04:11.413 READ FPDMA QUEUEDError 415 occurred at disk power-on lifetime: 38075 hours (1586 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 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 3d+09:56:30.189 READ FPDMA QUEUED
60 00 18 ff ff ff 4f 00 3d+09:56:30.188 READ FPDMA QUEUED
60 00 10 ff ff ff 4f 00 3d+09:56:30.188 READ FPDMA QUEUED
60 00 08 ff ff ff 4f 00 3d+09:56:30.186 READ FPDMA QUEUED
61 00 08 ff ff ff 4f 00 3d+09:56:30.185 WRITE FPDMA QUEUEDError 414 occurred at disk power-on lifetime: 38075 hours (1586 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 SC SN CL CH DH
40 51 00 ff ff ff 0f Error: WP 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
61 00 a8 ff ff ff 4f 00 3d+09:56:27.427 WRITE FPDMA QUEUED
61 00 10 ff ff ff 4f 00 3d+09:56:27.427 WRITE FPDMA QUEUED
60 00 18 ff ff ff 4f 00 3d+09:56:27.426 READ FPDMA QUEUED
60 00 10 ff ff ff 4f 00 3d+09:56:27.424 READ FPDMA QUEUED
60 00 18 ff ff ff 4f 00 3d+09:56:27.417 READ FPDMA QUEUEDError 413 occurred at disk power-on lifetime: 38006 hours (1583 days + 14 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 13:17:00.200 READ FPDMA QUEUED
61 00 08 ff ff ff 4f 00 13:17:00.200 WRITE FPDMA QUEUED
61 00 08 00 08 6b 40 00 13:17:00.199 WRITE FPDMA QUEUED
60 00 08 ff ff ff 4f 00 13:17:00.199 READ FPDMA QUEUED
60 00 00 ff ff ff 4f 00 13:17:00.197 READ FPDMA QUEUEDSMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error1 Short offline Completed: read failure 80% 37367 813889353
2 Short offline Completed: read failure 90% 37026 813890509
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.admin@home:~$
je suis plutôt un utilisateur windows, j’ai commencé à me familiariser avec linux il y a 3 mois (depuis que j’ai découvert yunohost).
Donc, que dois-je faire dans l’immédiat ? (j’ai éteint le pc parce que je n’ai pas le temps de m’en occuper ces jours ci en plus j’ai eu peur de perdre mes données).
la méthode la plus sûre pour récupérer les données ? est ce que le fait de cloner le disque sur un nouveau est envisageable? est ce que le disque est mort ?