Forum-Francophone-LinuxMint.fr


https://forum-francophone-linuxmint.fr/

Disque dur en mauvaise santé ?

https://forum-francophone-linuxmint.fr/viewtopic.php?t=4649

Page 1 sur 1

Disque dur en mauvaise santé ?

Posté : mar. 31 janv. 2017 07:46
par pingouinormand
Bonjour à tous,
Une collègue m'a confié son laptop qui ne démarrait plus. Le disque dur n'était plus reconnu au démarrage. Après avoir pas mal galéré pour désactiver le secure boot, j'ai réussi à lancer Mint via ma clé usb. En mode live usb, le disque dur n'apparaissait pas. J'ai alors tenté une installation en dur pour voir si le disque dur était reconnu. L'installation s'est déroulée normalement. Le disque a été reconnu.
Je trouve cependant le démarrage très lent (environ 2 minutes). Je me demande si le disque dur n'est pas un peu fatigué. J'ai déjà vérifié cela si ça peut aider :

Code : Tout sélectionner

viviane@viviane-HP-Pavilion-g6-Notebook-PC ~ $ sudo smartctl -s on -a /dev/sda1
smartctl 6.5 2016-01-24 r4214 [x86_64-linux-4.4.0-59-generic] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, http://www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Seagate Samsung SpinPoint M8 (AF)
Device Model:     ST1000LM024 HN-M101MBB
Serial Number:    S2SWJ9KCA01910
LU WWN Device Id: 5 0004cf 2088cde27
Firmware Version: 2AR10002
User Capacity:    1 000 204 886 016 bytes [1,00 TB]
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:   ACS-2, ATA8-ACS T13/1699-D revision 6
SATA Version is:  SATA 2.6, 3.0 Gb/s
Local Time is:    Tue Jan 31 07:35:04 2017 CET
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF ENABLE/DISABLE COMMANDS SECTION ===
SMART 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:      ( 113)	The previous self-test completed having
					the read element of the test failed.
Total time to complete Offline 
data collection: 		(13140) seconds.
Offline data collection
capabilities: 			 (0x51) SMART execute Offline immediate.
					No Auto Offline data collection support.
					Suspend Offline collection upon new
					command.
					No 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: 	 ( 219) minutes.
SCT capabilities: 	       (0x003d)	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       -       11130
  2 Throughput_Performance  0x0027   252   252   000    Pre-fail  Always       -       0
  3 Spin_Up_Time            0x0023   089   039   025    Pre-fail  Always       -       3451
  4 Start_Stop_Count        0x0032   097   097   000    Old_age   Always       -       3929
  5 Reallocated_Sector_Ct   0x0033   252   252   010    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x002f   252   252   051    Pre-fail  Always       -       0
  8 Seek_Time_Performance   0x0025   252   252   015    Pre-fail  Offline      -       0
  9 Power_On_Hours          0x0032   100   100   000    Old_age   Always       -       3626
 10 Spin_Retry_Count        0x0033   252   252   051    Pre-fail  Always       -       0
 11 Calibration_Retry_Count 0x0032   100   100   000    Old_age   Always       -       155
 12 Power_Cycle_Count       0x0032   097   097   000    Old_age   Always       -       4039
181 Program_Fail_Cnt_Total  0x0022   100   100   000    Old_age   Always       -       1274508
183 Runtime_Bad_Block       0x0032   252   252   010    Old_age   Always       -       0
184 End-to-End_Error        0x0033   252   252   048    Pre-fail  Always       -       0
186 Unknown_Attribute       0x0032   252   252   000    Old_age   Always       -       0
187 Reported_Uncorrect      0x0032   100   100   000    Old_age   Always       -       11036
188 Command_Timeout         0x0032   252   252   000    Old_age   Always       -       0
190 Airflow_Temperature_Cel 0x0002   068   043   040    Old_age   Always       -       32 (Min/Max 8/57)
191 G-Sense_Error_Rate      0x0022   100   100   000    Old_age   Always       -       304
192 Power-Off_Retract_Count 0x0022   252   252   000    Old_age   Always       -       0
193 Load_Cycle_Count        0x0032   083   083   000    Old_age   Always       -       175222
194 Temperature_Celsius     0x0002   064   043   000    Old_age   Always       -       32 (Min/Max 8/57)
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       -       3
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       -       14006

SMART Error Log Version: 1
ATA Error Count: 5
	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 5 occurred at disk power-on lifetime: 3615 hours (150 days + 15 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 00 00 00 40

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  18 9f 18 9f 18 f0 18 9f      10:54:18.685  RECALIBRATE [RET-4]
  00 00 00 00 00 00 00 00      00:00:00.033  NOP [Abort queued commands]
  e0 00 74 58 74 78 a0 00      00:00:00.034  STANDBY IMMEDIATE
  60 00 00 58 74 78 40 00      00:00:00.034  READ FPDMA QUEUED
  60 00 00 58 6c 78 40 00      00:00:00.034  READ FPDMA QUEUED

Error 4 occurred at disk power-on lifetime: 2935 hours (122 days + 7 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 00 00 00 40

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  18 9f 18 9f 18 f0 18 9f      10:54:18.685  RECALIBRATE [RET-4]
  00 00 00 00 00 00 00 00      00:00:00.107  NOP [Abort queued commands]
  60 00 1b e0 2b 4d 40 00      00:00:00.108  READ FPDMA QUEUED
  60 00 08 28 fe 3a 40 00      00:00:00.108  READ FPDMA QUEUED
  60 00 00 78 ea 2d 40 00      00:00:00.108  READ FPDMA QUEUED

Error 3 occurred at disk power-on lifetime: 2665 hours (111 days + 1 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 b8 e8 00 78 40

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  01 9f 18 9f 18 f0 18 9f      10:54:18.685  [RESERVED]
  00 00 00 00 00 00 00 00      00:00:05.020  NOP [Abort queued commands]
  61 00 08 b8 02 85 c0 00      00:00:05.059  WRITE FPDMA QUEUED
  60 00 80 a0 d2 78 40 00      00:00:05.059  READ FPDMA QUEUED
  61 00 08 30 6e 6d c0 00      00:00:05.059  WRITE FPDMA QUEUED

Error 2 occurred at disk power-on lifetime: 2045 hours (85 days + 5 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 00 00 00 40

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  18 9f 18 9f 18 f0 18 9f      10:54:18.685  RECALIBRATE [RET-4]
  00 00 00 00 00 00 00 00      00:00:00.003  NOP [Abort queued commands]
  60 00 00 c8 06 9d 40 00      00:00:00.005  READ FPDMA QUEUED
  60 00 00 e0 c7 58 40 00      00:00:00.005  READ FPDMA QUEUED
  60 00 00 80 2f c1 40 00      00:00:00.005  READ FPDMA QUEUED

Error 1 occurred at disk power-on lifetime: 1863 hours (77 days + 15 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 00 00 00 40

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  01 9f 18 9f 18 f0 18 9f      10:54:18.685  [RESERVED]
  00 00 00 00 00 00 00 00      00:00:00.051  NOP [Abort queued commands]
  e0 00 b4 dd 01 90 a0 00      00:00:00.052  STANDBY IMMEDIATE
  60 00 00 dd 01 90 40 00      00:00:00.052  READ FPDMA QUEUED
  60 00 e0 d5 ed 8f 40 00      00:00:00.052  READ 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: read failure       10%      3626         1272430872
# 2  Extended offline    Completed: read failure       50%      3622         1272430872
# 3  Short offline       Completed: read failure       10%      3620         1272430872
# 4  Extended offline    Aborted by host               90%      3620         -
# 5  Short offline       Completed: read failure       10%      3620         1272430872
# 6  Short offline       Completed: read failure       10%      3620         1272430872
# 7  Short offline       Completed: read failure       10%      3620         1272430872
# 8  Short offline       Aborted by host               90%      3620         -
# 9  Short offline       Completed: read failure       10%      3619         1272430872
#10  Extended offline    Aborted by host               90%      3619         -
#11  Short offline       Interrupted (host reset)      90%      3619         -
#12  Short offline       Completed: read failure       10%      3619         1272430872
#13  Extended offline    Completed: read failure       10%      3619         1272430872
#14  Extended offline    Interrupted (host reset)      90%      3616         -
#15  Short offline       Completed: read failure       90%      3616         1272430872
#16  Short offline       Completed: read failure       90%      3615         1272430872
#17  Extended offline    Aborted by host               90%      3615         -
#18  Short offline       Completed: read failure       90%      3615         0

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 [10% 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.

Re: Disque dur en mauvaise santé ?

Posté : mar. 31 janv. 2017 07:56
par bouledogue
Hello Il faut mettre tout ca dans des balises codes en éditant ton message stp ;) car là ça prend vraiment trop de place :D
Mon dd démarre aussi en 2mn, il est en effet fatigué.
Ça peut faire l'affaire pour commencer, et pourquoi pas investir dans un ssd plus tard pour le transformer radicalement, si ton amie apprécie Linux, plutôt que de racheter un neuf :roll: ;)

Re: Disque dur en mauvaise santé ?

Posté : mar. 31 janv. 2017 08:25
par mpat
salut pas dit que c'est ton disque qui ralentit tout. regardes ce que donne les commandes ci-dessous

Code : Tout sélectionner

systemd-analyze

Code : Tout sélectionner

systemd-analyze blame

Re: Disque dur en mauvaise santé ?

Posté : mar. 31 janv. 2017 09:30
par zeb
Hello ;)
bouledogue a écrit :Il faut mettre tout ca dans des balises codes en éditant ton message stp ;) car là ça prend vraiment trop de place :D
Mon dd démarre aussi en 2mn, il est en effet fatigué.
;) Voila qui est fait 8-)

Re: Disque dur en mauvaise santé ?

Posté : mar. 31 janv. 2017 13:06
par pingouinormand
Désolé pour les balises codes. Je pensais l'avoir fait. :? Merci Zebulon de l'avoir fait pour moi.

Voici les retours demandés par mpat :

Code : Tout sélectionner

viviane@viviane-HP-Pavilion-g6-Notebook-PC ~ $ systemd-analyze
Startup finished in 4.531s (firmware) + 4.625s (loader) + 13.162s (kernel) + 24.852s (userspace) = 47.172s
viviane@viviane-HP-Pavilion-g6-Notebook-PC ~ $ systemd-analyze blame
         10.608s ModemManager.service
          7.757s dev-sda2.device
          6.603s loadcpufreq.service
          6.426s networking.service
          6.303s grub-common.service
          5.166s systemd-logind.service
          4.820s ondemand.service
          4.442s NetworkManager.service
          4.382s console-kit-log-system-start.service
          4.132s pppd-dns.service
          4.126s rsyslog.service
          3.580s accounts-daemon.service
          3.492s systemd-user-sessions.service
          3.464s ufw.service
          2.510s lvm2-monitor.service
          2.485s thermald.service
          2.418s polkitd.service
          2.356s systemd-tmpfiles-setup-dev.service
          2.130s keyboard-setup.service
          2.024s apt-daily.service
          1.842s systemd-fsck@dev-disk-by\x2duuid-15A1\x2dDDF4.service
          1.683s virtualbox-guest-utils.service
          1.653s systemd-modules-load.service
lines 1-23...skipping...
         10.608s ModemManager.service
          7.757s dev-sda2.device
          6.603s loadcpufreq.service
          6.426s networking.service
          6.303s grub-common.service
          5.166s systemd-logind.service
          4.820s ondemand.service
          4.442s NetworkManager.service
          4.382s console-kit-log-system-start.service
          4.132s pppd-dns.service
          4.126s rsyslog.service
          3.580s accounts-daemon.service
          3.492s systemd-user-sessions.service
          3.464s ufw.service
          2.510s lvm2-monitor.service
          2.485s thermald.service
          2.418s polkitd.service
          2.356s systemd-tmpfiles-setup-dev.service
          2.130s keyboard-setup.service
          2.024s apt-daily.service
          1.842s systemd-fsck@dev-disk-by\x2duuid-15A1\x2dDDF4.service
          1.683s virtualbox-guest-utils.service
          1.653s systemd-modules-load.service
          1.634s irqbalance.service
          1.526s plymouth-start.service
          1.419s console-setup.service
          1.229s systemd-journald.service
          1.195s systemd-tmpfiles-setup.service
          1.166s speech-dispatcher.service
          1.057s avahi-daemon.service
           970ms iio-sensor-proxy.service
           941ms hddtemp.service
           935ms lm-sensors.service
           715ms wpa_supplicant.service
           712ms binfmt-support.service
           640ms upower.service
           600ms systemd-udevd.service
           592ms systemd-sysctl.service
           592ms plymouth-read-write.service
           572ms systemd-rfkill.service
           564ms plymouth-quit.service
           562ms plymouth-quit-wait.service
           522ms systemd-backlight@backlight:radeon_bl0.service
           454ms dev-mqueue.mount

Re: Disque dur en mauvaise santé ?

Posté : mar. 31 janv. 2017 13:42
par mpat
re. tu sais déjà gagner pas mal de secondes en enlevant le modem-manager ( qui est pour les ancienne connexion lorsqu'un pc avait une carte modem.

Code : Tout sélectionner

sudo systemctl stop ModemManager

Code : Tout sélectionner

sudo systemctl stop ModemManager.service

Code : Tout sélectionner

sudo apt-get purge modemmanager
as-tu créer une partition swap et est-elle active ?

Re: Disque dur en mauvaise santé ?

Posté : mar. 31 janv. 2017 19:34
par pingouinormand
Merci pour toutes les commandes que je vais entrer.
as-tu créer une partition swap et est-elle active ?
Il y une partition swap de 6Go qui a été créée à l'installation. Elle est active mais le PC ne l'utilise pas. 6Go de ram sont installés.

Je viens aussi de découvrir un message étrange écrit en rouge.
Image
Heures au format UTC+02:00
Page 1 sur 1

Développé par phpBB® Forum Software © phpBB Limited

Traduit par phpBB-fr.com