#1 Le 14/12/2024, à 19:57
- Geefray
Reparation de secteurs endommagés sur disques durs
Bonjour, quand je rentre dans l'utilitaire de disque, j'obtiens ce message : Le disque est sain, 3048 secteurs endommagés (41 ℃ / 106 ℉)
J'ai essayé la commande ci-après pour vérifier l'état de mon disque:
$sudo smartctl -a /dev/sda
smartctl 7.4 2023-08-01 r5530 [x86_64-linux-6.8.0-50-generic] (local build)
Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Model Family: Seagate Laptop HDD
Device Model: ST500LT012-9WS142
Serial Number: W0V77NZM
LU WWN Device Id: 5 000c50 06027b5ae
Firmware Version: 0001YAM1
User Capacity: 500107862016 bytes [500 GB]
Sector Sizes: 512 bytes logical, 4096 bytes physical
Rotation Rate: 5400 rpm
Form Factor: 2.5 inches
Device is: In smartctl database 7.3/5528
ATA Version is: ATA8-ACS T13/1699-D revision 4
SATA Version is: SATA 2.6, 3.0 Gb/s (current: 3.0 Gb/s)
Local Time is: Sat Dec 14 18:55:24 2024 WAT
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: (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: ( 95) minutes.
SCT capabilities: (0x103d) 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 0x002f 115 085 006 Pre-fail Always - 88734504
3 Spin_Up_Time 0x0023 099 099 000 Pre-fail Always - 0
4 Start_Stop_Count 0x0032 093 093 000 Old_age Always - 7991
5 Reallocated_Sector_Ct 0x0033 082 082 036 Pre-fail Always - 3048
7 Seek_Error_Rate 0x002f 062 057 030 Pre-fail Always - 730400672178
9 Power_On_Hours 0x0032 086 086 000 Old_age Always - 12836
10 Spin_Retry_Count 0x0033 100 100 097 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 093 093 000 Old_age Always - 7240
183 Runtime_Bad_Block 0x0032 100 100 000 Old_age Always - 0
184 End-to-End_Error 0x0033 100 100 097 Pre-fail Always - 0
187 Reported_Uncorrect 0x0032 001 001 000 Old_age Always - 2807
188 Command_Timeout 0x0032 100 092 000 Old_age Always - 455280623870
189 High_Fly_Writes 0x003a 100 100 000 Old_age Always - 0
190 Airflow_Temperature_Cel 0x0022 060 039 045 Old_age Always In_the_past 40 (Min/Max 30/41 #332)
191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 183
192 Power-Off_Retract_Count 0x0022 100 100 000 Old_age Always - 1786
193 Load_Cycle_Count 0x0032 018 018 000 Old_age Always - 164202
194 Temperature_Celsius 0x0022 040 061 000 Old_age Always - 40 (0 13 0 0 0)
196 Reallocated_Event_Count 0x0032 082 082 000 Old_age Always - 3048
197 Current_Pending_Sector 0x0032 100 061 000 Old_age Always - 0
198 Offline_Uncorrectable 0x0030 100 100 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x0032 200 196 000 Old_age Always - 699
254 Free_Fall_Sensor 0x0032 100 100 000 Old_age Always - 0
SMART Error Log Version: 1
ATA Error Count: 2851 (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 2851 occurred at disk power-on lifetime: 12569 hours (523 days + 17 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 27 3c 63 00 Error: WP at LBA = 0x00633c27 = 6503463
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 08 58 9e 83 40 00 01:00:05.234 WRITE FPDMA QUEUED
60 00 20 c1 33 74 4f 00 01:00:05.230 READ FPDMA QUEUED
60 00 01 27 3c 63 40 00 01:00:05.230 READ FPDMA QUEUED
60 00 20 51 2f 74 4f 00 01:00:05.227 READ FPDMA QUEUED
60 00 38 f8 ec 43 48 00 01:00:05.226 READ FPDMA QUEUED
Error 2850 occurred at disk power-on lifetime: 12569 hours (523 days + 17 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 26 3c 63 00 Error: UNC at LBA = 0x00633c26 = 6503462
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 01 81 f3 07 40 00 01:00:02.395 READ FPDMA QUEUED
60 00 01 26 3c 63 40 00 01:00:02.394 READ FPDMA QUEUED
60 00 20 e1 34 74 4f 00 01:00:02.388 READ FPDMA QUEUED
60 00 01 80 f3 07 40 00 01:00:02.372 READ FPDMA QUEUED
61 00 40 c0 8f 93 46 00 01:00:02.371 WRITE FPDMA QUEUED
Error 2849 occurred at disk power-on lifetime: 12569 hours (523 days + 17 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 25 3c 63 00 Error: UNC at LBA = 0x00633c25 = 6503461
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 01 25 3c 63 40 00 00:59:59.546 READ FPDMA QUEUED
61 00 08 c0 91 8f 40 00 00:59:59.546 WRITE FPDMA QUEUED
61 00 08 18 34 61 40 00 00:59:59.545 WRITE FPDMA QUEUED
60 00 20 20 97 62 49 00 00:59:59.545 READ FPDMA QUEUED
61 00 80 20 9b 4e 42 00 00:59:59.544 WRITE FPDMA QUEUED
Error 2848 occurred at disk power-on lifetime: 12569 hours (523 days + 17 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 24 3c 63 00 Error: WP at LBA = 0x00633c24 = 6503460
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 08 08 e7 13 4b 00 00:59:56.716 WRITE FPDMA QUEUED
60 00 01 24 3c 63 40 00 00:59:56.716 READ FPDMA QUEUED
60 00 50 78 4e 46 48 00 00:59:56.715 READ FPDMA QUEUED
60 00 20 68 6e 2f 46 00 00:59:56.703 READ FPDMA QUEUED
61 00 48 b0 d1 2e 40 00 00:59:56.702 WRITE FPDMA QUEUED
Error 2847 occurred at disk power-on lifetime: 12569 hours (523 days + 17 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 23 3c 63 00 Error: WP at LBA = 0x00633c23 = 6503459
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 08 70 34 61 40 00 00:59:53.854 WRITE FPDMA QUEUED
61 00 08 f0 33 61 40 00 00:59:53.853 WRITE FPDMA QUEUED
61 00 28 18 b1 8d 40 00 00:59:53.852 WRITE FPDMA QUEUED
61 00 08 70 34 61 40 00 00:59:53.851 WRITE FPDMA QUEUED
61 00 50 58 59 39 40 00 00:59:53.851 WRITE FPDMA QUEUED
SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Short offline Completed without error 00% 12798 -
# 2 Short offline Interrupted (host reset) 80% 10262 -
# 3 Offline Aborted by host 90% 10262 -
# 4 Offline Aborted by host 90% 10233 -
# 5 Offline Aborted by host 90% 10232 -
# 6 Offline Aborted by host 90% 9845 -
# 7 Short offline Aborted by host 90% 9689 -
# 8 Offline Aborted by host 90% 9689 -
# 9 Short offline Aborted by host 90% 9680 -
#10 Offline Aborted by host 90% 9680 -
#11 Extended offline Aborted by host 90% 6145 -
#12 Short offline Aborted by host 90% 6145 -
#13 Short offline Aborted by host 90% 6145 -
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.
The above only provides legacy SMART information - try 'smartctl -x' for moreHors ligne
#2 Le 14/12/2024, à 20:35
- geole
Re : Reparation de secteurs endommagés sur disques durs
Bonjour.
Il faut comprendre.
3048 secteurs endommagés ont été correctement réparés
5 Reallocated_Sector_Ct 0x0033 082 082 036 Pre-fail Always - 3048Il reste 0 secteur endommagé à réparer.
197 Current_Pending_Sector 0x0032 100 061 000 Old_age Always - 0Tout va bien car il reste un sacré paquet de secteurs de secours disponibles. ((3048/(100-82)*82=13885 et depuis 267 heures, aucune nouvelle erreur.
9 Power_On_Hours 0x0032 086 086 000 Old_age Always - 12836
Error 2850 occurred at disk power-on lifetime: 12569 hours.tDernière modification par geole (Le 14/12/2024, à 20:52)
Les grilles de l'installateur https://doc.ubuntu-fr.org/tutoriel/inst … _subiquity
Je défie QUICONQUE de trouver une discussion où j'aurais suggéré de remplacer un SSD par un disque dur.
Les partitions EXT4 des disques externes => https://forum.ubuntu-fr.org/viewtopic.p … #p22697248
Hors ligne
#3 Le 15/12/2024, à 04:50
- Geefray
Re : Reparation de secteurs endommagés sur disques durs
geole a écrit :
Bonjour.
Il faut comprendre.
3048 secteurs endommagés ont été correctement réparés5 Reallocated_Sector_Ct 0x0033 082 082 036 Pre-fail Always - 3048Il reste 0 secteur endommagé à réparer.
197 Current_Pending_Sector 0x0032 100 061 000 Old_age Always - 0Tout va bien car il reste un sacré paquet de secteurs de secours disponibles. ((3048/(100-82)*82=13885 et depuis 267 heures, aucune nouvelle erreur.
9 Power_On_Hours 0x0032 086 086 000 Old_age Always - 12836 Error 2850 occurred at disk power-on lifetime: 12569 hours.t
Merci beaucoup pour les explications
Hors ligne
#4 Le 15/12/2024, à 05:06
- Geefray
Re : Reparation de secteurs endommagés sur disques durs
J'utilise la version 24.04.1 d'Ubuntu, mais mon démarrage graphique est extrêmement lent, je peux attendre jusqu'a 5 mn avant d'accès à mon poste de travail. Et du coup je pensais que c'était lié au disque dur. Et du coup j'ai tapé la commande : systemd-analyze critical-chain pour afficher la liste de service et leur temps de démarrage. Je me demande si je dois désactiver l'interface graphique au démarrage
The time when unit became active or started is printed after the "@" character.
The time the unit took to start is printed after the "+" character.
multi-user.target @1min 53.149s
└─plymouth-quit-wait.service @1min 2.713s +50.433s
└─systemd-user-sessions.service @1min 2.619s +73ms
└─network.target @1min 2.121s
└─NetworkManager.service @48.505s +13.615s
└─dbus.service @36.554s +11.935s
└─basic.target @36.504s
└─sockets.target @36.504s
└─libvirtd-ro.socket @36.503s
└─libvirtd.socket @36.489s +13ms
└─sysinit.target @36.418s
└─systemd-resolved.service @35.486s +931ms
└─systemd-tmpfiles-setup.service @34.999s +450ms
└─systemd-journal-flush.service @8.646s +26.284s
└─systemd-remount-fs.service @8.134s +147ms
└─systemd-journald.socket @7.852s
└─-.mount @7.745s
└─-.slice @7.744sHors ligne
#5 Le 15/12/2024, à 09:00
- xubu1957
Re : Reparation de secteurs endommagés sur disques durs
Bonjour,
Montre la carte graphique :
lspci -vnn | grep -A 12 '\''[030[02]\]' | grep -Ei "vga|3d|display|kernel"uname -aecho $XDG_SESSION_TYPEla liste des anomalies de démarrage :
journalctl --no-pager -b -p erret :
ls -l /var/crashdpkg -l | grep -v ^iien te servant du Retour utilisable de commande
Conseils pour les nouveaux demandeurs et pas qu'eux
Important : Pensez à passer vos sujets en [Réso|u] lorsque ceux-ci le sont, au début du titre en cliquant sur Modifier sous le premier message, et un bref récapitulatif de la solution à la fin de celui-ci. Merci. Membre de Linux-Azur
En ligne
#6 Le 15/12/2024, à 17:04
- fred-cavernedufond
Re : Reparation de secteurs endommagés sur disques durs
Pour comparaison, voici ce que j'ai dans ma bécane avec une config de dix ans d'age ; 4Go de RAM et une vielle carte Nvidia. C'est quand meme moins...
patrick@patrick-MS-7309:~$ systemd-analyze critical-chain
The time when unit became active or started is printed after the "@" character.
The time the unit took to start is printed after the "+" character.
graphical.target @45.790s
└─multi-user.target @45.787s
└─plymouth-quit-wait.service @18.781s +27.004s
└─systemd-user-sessions.service @18.669s +93ms
└─network.target @18.632s
└─NetworkManager.service @15.147s +3.482s
└─dbus.service @15.128s
└─basic.target @15.033s
└─sockets.target @15.033s
└─snapd.socket @15.024s +8ms
└─sysinit.target @14.975s
└─snapd.apparmor.service @13.901s +1.073s
└─apparmor.service @11.996s +1.891s
└─local-fs.target @11.993s
└─run-snapd-ns-snapd\x2ddesktop\x2dintegration.mnt.mount @32.490s
└─run-snapd-ns.mount @21.734s
└─local-fs-pre.target @4.092s
└─systemd-tmpfiles-setup-dev.service @4.006s +84ms
└─systemd-sysusers.service @3.731s +269ms
└─systemd-remount-fs.service @3.621s +95ms
└─systemd-journald.socket @3.531s
└─-.mount @3.498s
└─-.slice @3.498s
patrick@patrick-MS-7309:~$ et sur le laptop plus récent :
graphical.target @9.293s
└─multi-user.target @9.293s
└─postfix.service @9.291s +1ms
└─postfix@-.service @8.194s +1.091s
└─network-online.target @8.174s
└─NetworkManager-wait-online.service @2.384s +5.789s
└─NetworkManager.service @2.196s +158ms
└─dbus.service @2.193s
└─basic.target @2.184s
└─sockets.target @2.183s
└─snapd.socket @2.175s +7ms
└─sysinit.target @2.152s
└─snapd.apparmor.service @2.025s +125ms
└─apparmor.service @1.819s +195ms
└─local-fs.target @1.809s
└─run-snapd-ns-snapd\x2ddesktop\x2dintegration.mnt.mount @3.652s
└─run-snapd-ns.mount @2.535s
└─swap.target @1.857s
└─dev-zram0.swap @2.444s
└─dev-zram0.device @2.353sDernière modification par fred-cavernedufond (Le 15/12/2024, à 21:56)
Fred
Ubuntu 22.04 & 24.04 LTS
Hors ligne