#1 Le 31/08/2025, à 11:15
- vato21
ubuntu 22.04 bug ou cassé ?
Bonjour
Ce matin j'utilise mon pc portable ubuntu 22.04 comme d'habitude, celui fonctionne bien, sauf que dans la matinée, mon pc s'eteint
Je le rallume et depuis, ce message s'affiche
[img]=https://drive.google.com/file/d/1Uc8QaDH_u_4hsKpRuUNuiVy9ebsQuy6K/view?usp=drivesdk[/img]
Svp, qui pourrait m'expliquer ce qu'il se passe?
Merci.
Vato21
"Smile now..... Cry later."
Hors ligne
#2 Le 31/08/2025, à 11:21
- geole
Re : ubuntu 22.04 bug ou cassé ?
Bonjour
Ce matin j'utilise mon pc portable ubuntu 22.04 comme d'habitude, celui fonctionne bien, sauf que dans la matinée, mon pc s'eteint
Je le rallume et depuis, ce message s'affichehttps://drive.google.com/file/d/1Uc8QaD … p=drivesdk
Svp, qui pourrait m'expliquer ce qu'il se passe?
Merci.
Bonjour.
L’accès à ton image est compliquée. Peut-tu poster ailleurs. Voir ce lien. paragraphe 2.2
Dernière modification par geole (Le 31/08/2025, à 11:23)
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
En ligne
#3 Le 31/08/2025, à 11:22
- xubu1957
Re : ubuntu 22.04 bug ou cassé ?
Conseils pour les nouveaux demandeurs et pas qu'eux
Important : Pensez à passer vos sujets en [ Résolu ] 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
Hors ligne
#4 Le 31/08/2025, à 11:23
- vato21
Re : ubuntu 22.04 bug ou cassé ?
bonjour,
j'ai fait une photo de ce qui s'affiche sur mon pc, comment afficher la photo directement? svp
Vato21
"Smile now..... Cry later."
Hors ligne
#5 Le 31/08/2025, à 11:25
- geole
Re : ubuntu 22.04 bug ou cassé ?
On a donné deux liens.
Je ne sais pas pourquoi mais je viens de pouvoir y accéder.
Fais ce qui est indiqué!
Lorsque cela plante, tu appuies sur la touche entrée puis tu frappes
fsck -yv /dev/sda5
Dernière modification par geole (Le 31/08/2025, à 11:28)
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
En ligne
#7 Le 31/08/2025, à 11:30
- geole
Re : ubuntu 22.04 bug ou cassé ?
Fais ce qui est indiqué!
Lorsque cela plante, tu appuies sur la touche entrée puis tu frappes
fsck -yv /dev/sda5
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
En ligne
#9 Le 31/08/2025, à 11:43
- geole
Re : ubuntu 22.04 bug ou cassé ?
Tente de rebooter!
Peut-être la commande exit puis reboot sinon le bouton arrêt/marche.
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
En ligne
#10 Le 31/08/2025, à 11:47
- vato21
Re : ubuntu 22.04 bug ou cassé ?
j'ai deja fait 2 redemarrage forcé, et c'est tjr pareille
Vato21
"Smile now..... Cry later."
Hors ligne
#11 Le 31/08/2025, à 11:58
- vato21
Re : ubuntu 22.04 bug ou cassé ?
je viens de refaire un redemarage en maintenant F12, le pc redemarre normalement...
ouf.
merci à tout le monde
Vato21
"Smile now..... Cry later."
Hors ligne
#12 Le 31/08/2025, à 11:59
- xubu1957
Re : ubuntu 22.04 bug ou cassé ?
Donne la liste des anomalies de démarrage :
journalctl --no-pager -b -p err
la carte graphique :
lspci -vnn | grep -A 12 '\''[030[02]\]' | grep -Ei "vga|3d|display|kernel"
uname -a
ubuntu-drivers devices
dpkg -l | grep nvidia
d'éventuels paquets cassés :
dpkg -l | grep -v ^ii
et :
ls -l /var/crash
en te servant du Retour utilisable de commande.
Conseils pour les nouveaux demandeurs et pas qu'eux
Important : Pensez à passer vos sujets en [ Résolu ] 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
Hors ligne
#13 Le 31/08/2025, à 12:00
- geole
Re : ubuntu 22.04 bug ou cassé ?
Boote avec le support d’installation
Choisis essayer avant d’installer.
Installe smartmontools
Publie l’état du disque ( Chapitre 3)
Refais encore la commande fsck.
Dernière modification par geole (Le 31/08/2025, à 12:48)
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
En ligne
#14 Le 31/08/2025, à 12:40
- vato21
Re : ubuntu 22.04 bug ou cassé ?
alors retour de commandes demandés:
anomalies demarrage:
sam@sam-SATELLITE-C660:~$ journalctl --no-pager -b -p err
août 31 12:27:56 sam-SATELLITE-C660 kernel: nouveau 0000:01:00.0: DRM: failed to create ce channel, -22
août 31 12:27:56 sam-SATELLITE-C660 kernel: Bluetooth: hci0: BCM: firmware Patch file not found, tried:
août 31 12:27:56 sam-SATELLITE-C660 kernel: Bluetooth: hci0: BCM: 'brcm/BCM20702A1-050d-065a.hcd'
août 31 12:27:56 sam-SATELLITE-C660 kernel: Bluetooth: hci0: BCM: 'brcm/BCM-050d-065a.hcd'
août 31 12:28:12 sam-SATELLITE-C660 bluetoothd[912]: Failed to set mode: Failed (0x03)
août 31 12:28:18 sam-SATELLITE-C660 wpa_supplicant[946]: bgscan simple: Failed to enable signal strength monitoring
août 31 12:28:38 sam-SATELLITE-C660 systemd[1170]: Failed to start Application launched by gnome-session-binary.
août 31 12:28:40 sam-SATELLITE-C660 kernel: nouveau 0000:01:00.0: msvld: unable to load firmware data
août 31 12:28:40 sam-SATELLITE-C660 kernel: nouveau 0000:01:00.0: msvld: init failed, -19
août 31 12:29:01 sam-SATELLITE-C660 systemd[1170]: Failed to start Application launched by gnome-session-binary.
sam@sam-SATELLITE-C660:~$
Vato21
"Smile now..... Cry later."
Hors ligne
#15 Le 31/08/2025, à 12:41
- vato21
Re : ubuntu 22.04 bug ou cassé ?
pour la carte graphique:
sam@sam-SATELLITE-C660:~$ lspci -vnn | grep -A 12 '\''[030[02]\]' | grep -Ei "vga|3d|display|kernel"
uname -a
ubuntu-drivers devices
dpkg -l | grep nvidia
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GT218M [GeForce 315M] [10de:0a7a] (rev a2) (prog-if 00 [VGA controller])
Kernel driver in use: nouveau
Kernel modules: nvidiafb, nouveau
Linux sam-SATELLITE-C660 6.8.0-78-generic #78~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Wed Aug 13 14:32:06 UTC 2 x86_64 x86_64 x86_64 GNU/Linux
ii nvidia-settings 510.47.03-0ubuntu1 amd64 Tool for configuring the NVIDIA graphics driver
ii screen-resolution-extra 0.18.2ubuntu0.1 all Extension for the nvidia-settings control panel
sam@sam-SATELLITE-C660:~$
Vato21
"Smile now..... Cry later."
Hors ligne
#16 Le 31/08/2025, à 12:42
- vato21
Re : ubuntu 22.04 bug ou cassé ?
et derniere commande:
sam@sam-SATELLITE-C660:~$ ls -l /var/crash
total 0
sam@sam-SATELLITE-C660:~$
Vato21
"Smile now..... Cry later."
Hors ligne
#17 Le 31/08/2025, à 12:45
- geole
Re : ubuntu 22.04 bug ou cassé ?
Comme ton ordinateur a planté méchamment,
Installe smartmontools
Publie l’état du disque ( Chapitre 3).
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
En ligne
#18 Le 31/08/2025, à 12:46
- vato21
Re : ubuntu 22.04 bug ou cassé ?
et le retour de smartmontools:
sam@sam-SATELLITE-C660:~$ sudo smartctl -s on -a /dev/sdX
[sudo] Mot de passe de sam :
smartctl 7.2 2020-12-30 r5155 [x86_64-linux-6.8.0-78-generic] (local build)
Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org
Smartctl open device: /dev/sdX failed: No such device
sam@sam-SATELLITE-C660:~$
Vato21
"Smile now..... Cry later."
Hors ligne
#19 Le 31/08/2025, à 12:53
- vato21
Re : ubuntu 22.04 bug ou cassé ?
retour:
sam@sam-SATELLITE-C660:~$ sudo smartctl -s on -a /dev/sda
[sudo] Mot de passe de sam :
smartctl 7.2 2020-12-30 r5155 [x86_64-linux-6.8.0-78-generic] (local build)
Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Model Family: Toshiba 2.5" HDD MQ01ABD...
Device Model: TOSHIBA MQ01ABD050V
Serial Number: 9691SKHYS
LU WWN Device Id: 5 000039 745603aea
Firmware Version: AX0U1Q
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 [for details use: -P show]
ATA Version is: ATA8-ACS (minor revision not indicated)
SATA Version is: SATA 2.6, 3.0 Gb/s (current: 3.0 Gb/s)
Local Time is: Sun Aug 31 12:50:20 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: ( 120) 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: ( 121) 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 050 Pre-fail Always - 0
2 Throughput_Performance 0x0005 100 100 050 Pre-fail Offline - 0
3 Spin_Up_Time 0x0027 100 100 001 Pre-fail Always - 1554
4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 4723
5 Reallocated_Sector_Ct 0x0033 100 100 050 Pre-fail Always - 0
7 Seek_Error_Rate 0x000b 100 100 050 Pre-fail Always - 0
8 Seek_Time_Performance 0x0005 100 100 050 Pre-fail Offline - 0
9 Power_On_Hours 0x0032 086 086 000 Old_age Always - 5737
10 Spin_Retry_Count 0x0033 194 100 030 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 1599
191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 177
192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 177
193 Load_Cycle_Count 0x0032 100 100 000 Old_age Always - 5066
194 Temperature_Celsius 0x0022 100 100 000 Old_age Always - 39 (Min/Max 13/45)
196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 0
197 Current_Pending_Sector 0x0032 100 100 000 Old_age Always - 0
198 Offline_Uncorrectable 0x0030 100 100 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 1471
220 Disk_Shift 0x0002 100 100 000 Old_age Always - 0
222 Loaded_Hours 0x0032 087 087 000 Old_age Always - 5561
223 Load_Retry_Count 0x0032 100 100 000 Old_age Always - 0
224 Load_Friction 0x0022 100 100 000 Old_age Always - 0
226 Load-in_Time 0x0026 100 100 000 Old_age Always - 189
240 Head_Flying_Hours 0x0001 100 100 001 Pre-fail Offline - 0
SMART Error Log Version: 1
ATA Error Count: 1471 (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 1471 occurred at disk power-on lifetime: 3808 hours (158 days + 16 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
-- -- -- -- -- -- --
84 51 00 6e 01 00 e0 Error: ABRT at LBA = 0x0000016e = 366
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
c5 00 08 67 01 00 e0 00 00:03:25.466 WRITE MULTIPLE
ec 03 08 00 00 00 a0 00 00:03:25.465 IDENTIFY DEVICE
ef 03 08 00 00 00 a0 00 00:03:25.464 SET FEATURES [Set transfer mode]
ec 00 01 01 00 00 a0 00 00:03:25.463 IDENTIFY DEVICE
ff ff ff ff ff ff ff 0c 00:03:25.312 [VENDOR SPECIFIC]
Error 1470 occurred at disk power-on lifetime: 3808 hours (158 days + 16 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
-- -- -- -- -- -- --
84 51 01 6e 01 00 e0 Error: ABRT at LBA = 0x0000016e = 366
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
c5 00 08 67 01 00 e0 00 00:03:24.944 WRITE MULTIPLE
ec 03 08 00 00 00 a0 00 00:03:24.943 IDENTIFY DEVICE
ef 03 08 00 00 00 a0 00 00:03:24.942 SET FEATURES [Set transfer mode]
ec 00 01 01 00 00 a0 00 00:03:24.941 IDENTIFY DEVICE
ff ff ff ff ff ff ff 0c 00:03:24.790 [VENDOR SPECIFIC]
Error 1469 occurred at disk power-on lifetime: 3808 hours (158 days + 16 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
-- -- -- -- -- -- --
84 51 01 6e 01 00 e0 Error: ABRT at LBA = 0x0000016e = 366
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
c5 00 08 67 01 00 e0 00 00:03:24.422 WRITE MULTIPLE
ec 03 08 00 00 00 a0 00 00:03:24.421 IDENTIFY DEVICE
ef 03 08 00 00 00 a0 00 00:03:24.420 SET FEATURES [Set transfer mode]
ec 00 01 01 00 00 a0 00 00:03:24.419 IDENTIFY DEVICE
ff ff ff ff ff ff ff 0c 00:03:24.268 [VENDOR SPECIFIC]
Error 1468 occurred at disk power-on lifetime: 3808 hours (158 days + 16 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
-- -- -- -- -- -- --
84 51 01 6e 01 00 e0 Error: ABRT at LBA = 0x0000016e = 366
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
c5 00 08 67 01 00 e0 00 00:03:23.900 WRITE MULTIPLE
ec 03 08 00 00 00 a0 00 00:03:23.899 IDENTIFY DEVICE
ef 03 08 00 00 00 a0 00 00:03:23.898 SET FEATURES [Set transfer mode]
ec 00 01 01 00 00 a0 00 00:03:23.897 IDENTIFY DEVICE
ff ff ff ff ff ff ff 0c 00:03:23.746 [VENDOR SPECIFIC]
Error 1467 occurred at disk power-on lifetime: 3808 hours (158 days + 16 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
-- -- -- -- -- -- --
84 51 01 6e 01 00 e0 Error: ABRT at LBA = 0x0000016e = 366
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
c5 00 08 67 01 00 e0 00 00:03:23.378 WRITE MULTIPLE
ec 03 08 00 00 00 a0 00 00:03:23.377 IDENTIFY DEVICE
ef 03 08 00 00 00 a0 00 00:03:23.376 SET FEATURES [Set transfer mode]
ec 00 01 01 00 00 a0 00 00:03:23.375 IDENTIFY DEVICE
ff ff ff ff ff ff ff 0c 00:03:23.224 [VENDOR SPECIFIC]
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% 3867 -
# 2 Short offline Completed without error 00% 3784 -
# 3 Short offline Completed without error 00% 3751 -
# 4 Short offline Completed without error 00% 3721 -
# 5 Short offline Aborted by host 70% 3721 -
# 6 Short offline Completed without error 00% 3687 -
# 7 Short offline Completed without error 00% 3646 -
# 8 Short offline Aborted by host 30% 3646 -
# 9 Short offline Interrupted (host reset) 80% 3626 -
#10 Short offline Completed without error 00% 3603 -
#11 Short offline Aborted by host 40% 3603 -
#12 Short offline Completed without error 00% 3573 -
#13 Short offline Completed without error 00% 3543 -
#14 Short offline Completed without error 00% 3513 -
#15 Short offline Completed without error 00% 3483 -
#16 Short offline Completed without error 00% 3453 -
#17 Short offline Completed without error 00% 3423 -
#18 Short offline Completed without error 00% 3392 -
#19 Short offline Completed without error 00% 3362 -
#20 Short offline Aborted by host 30% 3362 -
#21 Short offline Completed without error 00% 3332 -
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.
sam@sam-SATELLITE-C660:~$
Vato21
"Smile now..... Cry later."
Hors ligne
#20 Le 31/08/2025, à 13:00
- geole
Re : ubuntu 22.04 bug ou cassé ?
Rien de particulier à signaler pour le disque.
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
En ligne
#21 Le 31/08/2025, à 13:04
- xubu1957
Re : ubuntu 22.04 bug ou cassé ?
Fournis les retours de :
sudo apt update
Conseils pour les nouveaux demandeurs et pas qu'eux
Important : Pensez à passer vos sujets en [ Résolu ] 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
Hors ligne
#22 Le 31/08/2025, à 13:06
- vato21
Re : ubuntu 22.04 bug ou cassé ?
voila
sam@sam-SATELLITE-C660:~$ sudo smartctl -s on -a /dev/sda
[sudo] Mot de passe de sam :
smartctl 7.2 2020-12-30 r5155 [x86_64-linux-6.8.0-78-generic] (local build)
Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Model Family: Toshiba 2.5" HDD MQ01ABD...
Device Model: TOSHIBA MQ01ABD050V
Serial Number: 9691SKHYS
LU WWN Device Id: 5 000039 745603aea
Firmware Version: AX0U1Q
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 [for details use: -P show]
ATA Version is: ATA8-ACS (minor revision not indicated)
SATA Version is: SATA 2.6, 3.0 Gb/s (current: 3.0 Gb/s)
Local Time is: Sun Aug 31 12:50:20 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: ( 120) 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: ( 121) 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 050 Pre-fail Always - 0
2 Throughput_Performance 0x0005 100 100 050 Pre-fail Offline - 0
3 Spin_Up_Time 0x0027 100 100 001 Pre-fail Always - 1554
4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 4723
5 Reallocated_Sector_Ct 0x0033 100 100 050 Pre-fail Always - 0
7 Seek_Error_Rate 0x000b 100 100 050 Pre-fail Always - 0
8 Seek_Time_Performance 0x0005 100 100 050 Pre-fail Offline - 0
9 Power_On_Hours 0x0032 086 086 000 Old_age Always - 5737
10 Spin_Retry_Count 0x0033 194 100 030 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 1599
191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 177
192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 177
193 Load_Cycle_Count 0x0032 100 100 000 Old_age Always - 5066
194 Temperature_Celsius 0x0022 100 100 000 Old_age Always - 39 (Min/Max 13/45)
196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 0
197 Current_Pending_Sector 0x0032 100 100 000 Old_age Always - 0
198 Offline_Uncorrectable 0x0030 100 100 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 1471
220 Disk_Shift 0x0002 100 100 000 Old_age Always - 0
222 Loaded_Hours 0x0032 087 087 000 Old_age Always - 5561
223 Load_Retry_Count 0x0032 100 100 000 Old_age Always - 0
224 Load_Friction 0x0022 100 100 000 Old_age Always - 0
226 Load-in_Time 0x0026 100 100 000 Old_age Always - 189
240 Head_Flying_Hours 0x0001 100 100 001 Pre-fail Offline - 0
SMART Error Log Version: 1
ATA Error Count: 1471 (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 1471 occurred at disk power-on lifetime: 3808 hours (158 days + 16 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
-- -- -- -- -- -- --
84 51 00 6e 01 00 e0 Error: ABRT at LBA = 0x0000016e = 366
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
c5 00 08 67 01 00 e0 00 00:03:25.466 WRITE MULTIPLE
ec 03 08 00 00 00 a0 00 00:03:25.465 IDENTIFY DEVICE
ef 03 08 00 00 00 a0 00 00:03:25.464 SET FEATURES [Set transfer mode]
ec 00 01 01 00 00 a0 00 00:03:25.463 IDENTIFY DEVICE
ff ff ff ff ff ff ff 0c 00:03:25.312 [VENDOR SPECIFIC]
Error 1470 occurred at disk power-on lifetime: 3808 hours (158 days + 16 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
-- -- -- -- -- -- --
84 51 01 6e 01 00 e0 Error: ABRT at LBA = 0x0000016e = 366
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
c5 00 08 67 01 00 e0 00 00:03:24.944 WRITE MULTIPLE
ec 03 08 00 00 00 a0 00 00:03:24.943 IDENTIFY DEVICE
ef 03 08 00 00 00 a0 00 00:03:24.942 SET FEATURES [Set transfer mode]
ec 00 01 01 00 00 a0 00 00:03:24.941 IDENTIFY DEVICE
ff ff ff ff ff ff ff 0c 00:03:24.790 [VENDOR SPECIFIC]
Error 1469 occurred at disk power-on lifetime: 3808 hours (158 days + 16 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
-- -- -- -- -- -- --
84 51 01 6e 01 00 e0 Error: ABRT at LBA = 0x0000016e = 366
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
c5 00 08 67 01 00 e0 00 00:03:24.422 WRITE MULTIPLE
ec 03 08 00 00 00 a0 00 00:03:24.421 IDENTIFY DEVICE
ef 03 08 00 00 00 a0 00 00:03:24.420 SET FEATURES [Set transfer mode]
ec 00 01 01 00 00 a0 00 00:03:24.419 IDENTIFY DEVICE
ff ff ff ff ff ff ff 0c 00:03:24.268 [VENDOR SPECIFIC]
Error 1468 occurred at disk power-on lifetime: 3808 hours (158 days + 16 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
-- -- -- -- -- -- --
84 51 01 6e 01 00 e0 Error: ABRT at LBA = 0x0000016e = 366
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
c5 00 08 67 01 00 e0 00 00:03:23.900 WRITE MULTIPLE
ec 03 08 00 00 00 a0 00 00:03:23.899 IDENTIFY DEVICE
ef 03 08 00 00 00 a0 00 00:03:23.898 SET FEATURES [Set transfer mode]
ec 00 01 01 00 00 a0 00 00:03:23.897 IDENTIFY DEVICE
ff ff ff ff ff ff ff 0c 00:03:23.746 [VENDOR SPECIFIC]
Error 1467 occurred at disk power-on lifetime: 3808 hours (158 days + 16 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
-- -- -- -- -- -- --
84 51 01 6e 01 00 e0 Error: ABRT at LBA = 0x0000016e = 366
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
c5 00 08 67 01 00 e0 00 00:03:23.378 WRITE MULTIPLE
ec 03 08 00 00 00 a0 00 00:03:23.377 IDENTIFY DEVICE
ef 03 08 00 00 00 a0 00 00:03:23.376 SET FEATURES [Set transfer mode]
ec 00 01 01 00 00 a0 00 00:03:23.375 IDENTIFY DEVICE
ff ff ff ff ff ff ff 0c 00:03:23.224 [VENDOR SPECIFIC]
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% 3867 -
# 2 Short offline Completed without error 00% 3784 -
# 3 Short offline Completed without error 00% 3751 -
# 4 Short offline Completed without error 00% 3721 -
# 5 Short offline Aborted by host 70% 3721 -
# 6 Short offline Completed without error 00% 3687 -
# 7 Short offline Completed without error 00% 3646 -
# 8 Short offline Aborted by host 30% 3646 -
# 9 Short offline Interrupted (host reset) 80% 3626 -
#10 Short offline Completed without error 00% 3603 -
#11 Short offline Aborted by host 40% 3603 -
#12 Short offline Completed without error 00% 3573 -
#13 Short offline Completed without error 00% 3543 -
#14 Short offline Completed without error 00% 3513 -
#15 Short offline Completed without error 00% 3483 -
#16 Short offline Completed without error 00% 3453 -
#17 Short offline Completed without error 00% 3423 -
#18 Short offline Completed without error 00% 3392 -
#19 Short offline Completed without error 00% 3362 -
#20 Short offline Aborted by host 30% 3362 -
#21 Short offline Completed without error 00% 3332 -
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.
sam@sam-SATELLITE-C660:~$
sam@sam-SATELLITE-C660:~$ sudo apt update
[sudo] Mot de passe de sam :
Atteint :1 http://fr.archive.ubuntu.com/ubuntu jammy InRelease
Réception de :2 http://fr.archive.ubuntu.com/ubuntu jammy-updates InRelease [128 kB]
Réception de :3 http://fr.archive.ubuntu.com/ubuntu jammy-backports InRelease [127 kB]
Ign :4 https://ppa.launchpadcontent.net/indicator-brightness/ppa/ubuntu jammy InRelease
Err :5 https://ppa.launchpadcontent.net/indicator-brightness/ppa/ubuntu jammy Release
404 Not Found [IP : 2620:2d:4000:1::81 443]
Atteint :6 http://archive.ubuntu.com/ubuntu jammy InRelease
Réception de :7 http://fr.archive.ubuntu.com/ubuntu jammy-updates/main i386 Packages [870 kB]
Réception de :8 http://fr.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages [2882 kB]
Réception de :9 http://fr.archive.ubuntu.com/ubuntu jammy-updates/main amd64 DEP-11 Metadata [112 kB]
Réception de :10 http://fr.archive.ubuntu.com/ubuntu jammy-updates/restricted amd64 DEP-11 Metadata [212 B]
Réception de :11 http://fr.archive.ubuntu.com/ubuntu jammy-updates/universe amd64 Packages [1227 kB]
Réception de :12 http://fr.archive.ubuntu.com/ubuntu jammy-updates/universe i386 Packages [782 kB]
Réception de :13 http://fr.archive.ubuntu.com/ubuntu jammy-updates/universe amd64 DEP-11 Metadata [359 kB]
Réception de :14 http://fr.archive.ubuntu.com/ubuntu jammy-updates/multiverse amd64 DEP-11 Metadata [940 B]
Réception de :15 http://fr.archive.ubuntu.com/ubuntu jammy-backports/main amd64 DEP-11 Metadata [7072 B]
Réception de :16 http://fr.archive.ubuntu.com/ubuntu jammy-backports/restricted amd64 DEP-11 Metadata [212 B]
Réception de :17 http://fr.archive.ubuntu.com/ubuntu jammy-backports/universe amd64 DEP-11 Metadata [26,0 kB]
Réception de :18 http://fr.archive.ubuntu.com/ubuntu jammy-backports/multiverse amd64 DEP-11 Metadata [212 B]
Réception de :19 http://security.ubuntu.com/ubuntu jammy-security InRelease [129 kB]
Réception de :20 http://security.ubuntu.com/ubuntu jammy-security/main amd64 DEP-11 Metadata [54,6 kB]
Réception de :21 http://security.ubuntu.com/ubuntu jammy-security/restricted amd64 DEP-11 Metadata [208 B]
Réception de :22 http://security.ubuntu.com/ubuntu jammy-security/universe amd64 DEP-11 Metadata [125 kB]
Réception de :23 http://security.ubuntu.com/ubuntu jammy-security/multiverse amd64 DEP-11 Metadata [208 B]
Lecture des listes de paquets... Fait
E: Le dépôt https://ppa.launchpadcontent.net/indicator-brightness/ppa/ubuntu jammy Release n'a pas de fichier Release.
N: Les mises à jour depuis un tel dépôt ne peuvent s'effectuer de manière sécurisée, et sont donc désactivées par défaut.
N: Voir les pages de manuel d'apt-secure(8) pour la création des dépôts et les détails de configuration d'un utilisateur.
sam@sam-SATELLITE-C660:~$
Vato21
"Smile now..... Cry later."
Hors ligne
#23 Le 31/08/2025, à 13:43
- geole
Re : ubuntu 22.04 bug ou cassé ?
E: Le dépôt https://ppa.launchpadcontent.net/indicator-brightness/ppa/ubuntu jammy Release n'a pas de fichier Release.
Supprime le ppa qui n’existe plus puis relance la commande de listage
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
En ligne
#24 Le 31/08/2025, à 13:59
- vato21
Re : ubuntu 22.04 bug ou cassé ?
voici:
sam@sam-SATELLITE-C660:~$ sudo add-apt-repository --remove ppa:ppa.launchpadcontent.net/indicator-brightness/
[sudo] Mot de passe de sam :
joUnable to handle repository shortcut 'ppa:ppa.launchpadcontent.net/indicator-brightness/'
sam@sam-SATELLITE-C660:~$ sudo apt update
Atteint :1 http://fr.archive.ubuntu.com/ubuntu jammy InRelease
Atteint :2 http://fr.archive.ubuntu.com/ubuntu jammy-updates InRelease
Atteint :3 http://fr.archive.ubuntu.com/ubuntu jammy-backports InRelease
Atteint :4 http://security.ubuntu.com/ubuntu jammy-security InRelease
Ign :5 https://ppa.launchpadcontent.net/indicator-brightness/ppa/ubuntu jammy InRelease
Err :6 https://ppa.launchpadcontent.net/indicator-brightness/ppa/ubuntu jammy Release
404 Not Found [IP : 2620:2d:4000:1::81 443]
Atteint :7 http://archive.ubuntu.com/ubuntu jammy InRelease
Lecture des listes de paquets... Fait
E: Le dépôt https://ppa.launchpadcontent.net/indicator-brightness/ppa/ubuntu jammy Release n'a pas de fichier Release.
N: Les mises à jour depuis un tel dépôt ne peuvent s'effectuer de manière sécurisée, et sont donc désactivées par défaut.
N: Voir les pages de manuel d'apt-secure(8) pour la création des dépôts et les détails de configuration d'un utilisateur.
sam@sam-SATELLITE-C660:~$
Vato21
"Smile now..... Cry later."
Hors ligne
#25 Le 31/08/2025, à 13:59
- xubu1957
Re : ubuntu 22.04 bug ou cassé ?
Pour le dégager :
sudo add-apt-repository -ry ppa:indicator-brightness/ppa
puis :
sudo apt clean && sudo apt update
Conseils pour les nouveaux demandeurs et pas qu'eux
Important : Pensez à passer vos sujets en [ Résolu ] 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
Hors ligne