#26 Le 04/08/2025, à 08:12
- bibitoi74
Re : Lanteur du système [RESOLU]
bussiere@bussiere-Aspire-E1-531:~$ sudo apt-get install --no-install-recommends smartmontools
[sudo] Mot de passe de bussiere :
Lecture des listes de paquets... Fait
Construction de l'arbre des dépendances... Fait
Lecture des informations d'état... Fait
smartmontools est déjà la version la plus récente (7.4-2build1).
0 mis à jour, 0 nouvellement installés, 0 à enlever et 0 non mis à jour.
bussiere@bussiere-Aspire-E1-531:~$
Longue vie a LINUX.
Hors ligne
#27 Le 04/08/2025, à 08:23
- geole
Re : Lanteur du système [RESOLU]
Ce n'est pas un 1 mais un a
Si l'arrêt de hier est intempestif, installe un logiciel de transfert de fichier
if test -z $(which pastebinit); then sudo apt install -y pastebinit;fi
et publie ce retour composé de deux lignes
journalctl --since "2025-08-03 17:40" --until "2025-08-03 17:51:36" -n 2500 |pastebinit
Pour les commandes, utilise le copier/coller
Dernière modification par geole (Le 04/08/2025, à 08:24)
Les grilles de l'installateur https://doc.ubuntu-fr.org/tutoriel/inst … _subiquity
Les partitions EXT4 des disques externes => https://forum.ubuntu-fr.org/viewtopic.p … #p22697248
Hors ligne
#28 Le 04/08/2025, à 08:24
- bibitoi74
Re : Lanteur du système [RESOLU]
bussiere@bussiere-Aspire-E1-531:~$ sudo smartctl -s on -a /dev/sda
smartctl 7.4 2023-08-01 r5530 [x86_64-linux-6.8.0-71-generic] (local build)
Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Model Family: Hitachi/HGST Travelstar Z5K500
Device Model: Hitachi HTS545050A7E380
Serial Number: TEK51A39HZYX7S
LU WWN Device Id: 5 000cca 71edc2aeb
Firmware Version: GG2OA920
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 6
SATA Version is: SATA 2.6, 3.0 Gb/s
Local Time is: Mon Aug 4 08:23:39 2025 CEST
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: ( 0) The previous self-test routine completed
without error or no self-test has ever
been run.
Total time to complete Offline
data collection: ( 45) 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: ( 117) 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 0x000b 100 100 062 Pre-fail Always - 0
2 Throughput_Performance 0x0005 100 100 040 Pre-fail Offline - 0
3 Spin_Up_Time 0x0007 214 214 033 Pre-fail Always - 1
4 Start_Stop_Count 0x0012 091 091 000 Old_age Always - 14846
5 Reallocated_Sector_Ct 0x0033 100 100 005 Pre-fail Always - 0
7 Seek_Error_Rate 0x000b 100 100 067 Pre-fail Always - 0
8 Seek_Time_Performance 0x0005 100 100 040 Pre-fail Offline - 0
9 Power_On_Hours 0x0012 057 057 000 Old_age Always - 18972
10 Spin_Retry_Count 0x0013 100 100 060 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 096 096 000 Old_age Always - 7268
191 G-Sense_Error_Rate 0x000a 100 100 000 Old_age Always - 0
192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 128
193 Load_Cycle_Count 0x0012 038 038 000 Old_age Always - 623005
194 Temperature_Celsius 0x0002 193 193 000 Old_age Always - 31 (Min/Max 8/46)
196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 0
197 Current_Pending_Sector 0x0022 100 100 000 Old_age Always - 0
198 Offline_Uncorrectable 0x0008 100 100 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x000a 200 200 000 Old_age Always - 0
223 Load_Retry_Count 0x000a 100 100 000 Old_age Always - 0
SMART Error Log Version: 1
ATA Error Count: 4096 (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 4096 occurred at disk power-on lifetime: 13911 hours (579 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 08 78 c6 4a 00 Error: UNC at LBA = 0x004ac678 = 4900472
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 98 60 5d 59 40 00 00:01:26.625 READ FPDMA QUEUED
60 60 90 80 2d c5 40 00 00:01:26.517 READ FPDMA QUEUED
60 00 88 58 e8 20 40 00 00:01:26.372 READ FPDMA QUEUED
60 08 80 78 c6 4a 40 00 00:01:26.363 READ FPDMA QUEUED
60 00 78 b8 ed 20 40 00 00:01:26.362 READ FPDMA QUEUED
Error 4095 occurred at disk power-on lifetime: 13911 hours (579 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 08 78 c6 4a 00 Error: UNC at LBA = 0x004ac678 = 4900472
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 08 b0 b8 0f 41 40 00 00:01:19.720 READ FPDMA QUEUED
60 08 a8 08 08 c0 40 00 00:01:19.663 READ FPDMA QUEUED
60 20 a0 88 59 28 40 00 00:01:17.251 READ FPDMA QUEUED
60 80 98 00 a6 a4 40 00 00:01:17.250 READ FPDMA QUEUED
60 e0 90 b8 49 59 40 00 00:01:17.250 READ FPDMA QUEUED
Error 4094 occurred at disk power-on lifetime: 13911 hours (579 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 88 78 c6 4a 00 Error: UNC at LBA = 0x004ac678 = 4900472
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 68 80 f6 a5 40 00 00:01:13.270 READ FPDMA QUEUED
60 00 60 80 f5 a5 40 00 00:01:13.269 READ FPDMA QUEUED
60 00 58 80 f4 a5 40 00 00:01:13.267 READ FPDMA QUEUED
60 20 50 70 86 49 40 00 00:01:13.266 READ FPDMA QUEUED
60 78 48 30 57 49 40 00 00:01:13.252 READ FPDMA QUEUED
Error 4093 occurred at disk power-on lifetime: 12165 hours (506 days + 21 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 12 80 e1 3c 00 Error: UNC at LBA = 0x003ce180 = 3989888
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 08 28 08 9e 7c 40 00 00:19:24.494 READ FPDMA QUEUED
60 40 18 0a 35 7e 40 00 00:19:24.494 READ FPDMA QUEUED
61 08 10 30 78 75 40 00 00:19:24.494 WRITE FPDMA QUEUED
60 01 08 70 e7 3f 40 00 00:19:24.494 READ FPDMA QUEUED
60 08 08 50 e6 2e 40 00 00:19:24.493 READ FPDMA QUEUED
Error 4092 occurred at disk power-on lifetime: 12165 hours (506 days + 21 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 02 80 e1 3c 00 Error: UNC at LBA = 0x003ce180 = 3989888
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 08 78 c8 0b 80 40 00 00:19:20.796 READ FPDMA QUEUED
60 30 10 22 42 22 40 00 00:19:20.793 READ FPDMA QUEUED
60 01 10 48 9d c2 40 00 00:19:20.792 READ FPDMA QUEUED
60 08 78 52 42 22 40 00 00:19:20.788 READ FPDMA QUEUED
60 22 20 08 ae 24 40 00 00:19:20.788 READ FPDMA QUEUED
SMART Self-test log structure revision number 1
No self-tests have been logged. [To run self-tests, use: smartctl -t]
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 more
bussiere@bussiere-Aspire-E1-531:~$
Longue vie a LINUX.
Hors ligne
#29 Le 04/08/2025, à 08:28
- bibitoi74
Re : Lanteur du système [RESOLU]
ussiere@bussiere-Aspire-E1-531:~$ if test -z $(which pastebinit); then sudo apt install -y pastebinit;fi
Lecture des listes de paquets... Fait
Construction de l'arbre des dépendances... Fait
Lecture des informations d'état... Fait
Les NOUVEAUX paquets suivants seront installés :
pastebinit
0 mis à jour, 1 nouvellement installés, 0 à enlever et 0 non mis à jour.
Il est nécessaire de prendre 14,3 ko dans les archives.
Après cette opération, 143 ko d'espace disque supplémentaires seront utilisés.
Réception de :1 http://fr.archive.ubuntu.com/ubuntu noble/main amd64 pastebinit all 1.6.2-1 [14,3 kB]
14,3 ko réceptionnés en 0s (87,6 ko/s)
Sélection du paquet pastebinit précédemment désélectionné.
(Lecture de la base de données... 218112 fichiers et répertoires déjà i
nstallés.)
Préparation du dépaquetage de .../pastebinit_1.6.2-1_all.deb ...
Dépaquetage de pastebinit (1.6.2-1) ...
Paramétrage de pastebinit (1.6.2-1) ...
Traitement des actions différées (« triggers ») pour man-db (2.12.0-4bu
ild2) ...
bussiere@bussiere-Aspire-E1-531:~$
Longue vie a LINUX.
Hors ligne
#30 Le 04/08/2025, à 08:30
- bibitoi74
Re : Lanteur du système [RESOLU]
bussiere@bussiere-Aspire-E1-531:~$ journalctl --since "2025-08-03 17:40" --until "2025-08-03 17:51:36" -n 2500 |pastebinit
N'a pas pu contacter le serveur : HTTP Error 400: Bad Request
bussiere@bussiere-Aspire-E1-531:~$
Longue vie a LINUX.
Hors ligne
#31 Le 04/08/2025, à 08:32
- geole
Re : Lanteur du système [RESOLU]
Ton disque est en très bon état. Cependant c'est un disque lent ' 'Rotation Rate: 5400 rpm') comme beaucoup de disques.
graphical.target @1min 41.923s
est un temps démarrage normal dans ce contexte, Si tu veux améliorer il faut installer un ssd.
Je ne le sens pas responsable de la lenteur que tu signales. Au fait, décris-la pour un cas concret.
journalctl --since "2025-08-03 17:40" --until "2025-08-03 17:50" -n 1000
Dernière modification par geole (Le 04/08/2025, à 08:34)
Les grilles de l'installateur https://doc.ubuntu-fr.org/tutoriel/inst … _subiquity
Les partitions EXT4 des disques externes => https://forum.ubuntu-fr.org/viewtopic.p … #p22697248
Hors ligne
#32 Le 04/08/2025, à 08:40
- bibitoi74
Re : Lanteur du système [RESOLU]
Bonjour
Quelque fois sur Firefox le système redémarre et a la suit me demande le mot de passe de la session et me reouvre ou j’étais mes toujours un peu lent
Longue vie a LINUX.
Hors ligne
#33 Le 04/08/2025, à 10:44
- bibitoi74
Re : Lanteur du système [RESOLU]
Ça a l'air plus rapide sans coupure ni redémarrage.
Encore merci a tout les aidants que ce forum puisse durer long temps.
Je vais ajouter résolu merci.
Dernière modification par bibitoi74 (Le 04/08/2025, à 10:44)
Longue vie a LINUX.
Hors ligne