Contenu | Rechercher | Menus

Annonce

Si vous avez des soucis pour rester connecté, déconnectez-vous puis reconnectez-vous depuis ce lien en cochant la case
Me connecter automatiquement lors de mes prochaines visites.

À propos de l'équipe du forum.

#1 Le 23/09/2020, à 13:15

ChrisForum

[ Résolu ] Erreurs lors d'un dmesg

Bonjour tout le monde

Débutant sous ubuntu 18.04 et nouveau sur ce forum , en m'informant pour comprendre comment fonctionne ce système d'exploitation , j'ai vu que l'on pouvait faire un "dmesg" sur le terminal  .

Hors voilà ce que j'obtiens en faisant "dmesg". Pour moi c'est du chinois mais je comprends bien qu'il y a un problème . Que dois je faire ?

Merci

Une longue partie noire puis 

out
                        res 41/40:78:88:6d:4c/00:00:01:00:00/40 Emask 0x9 (media error)
[  320.249196] ata1.00: status: { DRDY ERR }
[  320.249203] ata1.00: error: { UNC }
[  320.249220] ata1.00: failed command: WRITE FPDMA QUEUED
[  320.249259] ata1.00: cmd 61/b0:90:70:8a:c4/00:00:00:00:00/40 tag 18 ncq 90112 out
                        res 41/40:78:88:6d:4c/00:00:01:00:00/40 Emask 0x9 (media error)
[  320.249284] ata1.00: status: { DRDY ERR }
[  320.249296] ata1.00: error: { UNC }
[  320.252728] ata1.00: configured for UDMA/100
[  320.252781] sd 0:0:0:0: [sda] tag#14 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[  320.252798] sd 0:0:0:0: [sda] tag#14 Sense Key : Medium Error [current] [descriptor] 
[  320.252817] sd 0:0:0:0: [sda] tag#14 Add. Sense: Unrecovered read error - auto reallocate failed
[  320.252833] sd 0:0:0:0: [sda] tag#14 CDB: Read(10) 28 00 01 4c 6c d0 00 01 00 00
[  320.252843] blk_update_request: I/O error, dev sda, sector 21785992
[  320.252907] sd 0:0:0:0: [sda] tag#15 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[  320.252921] sd 0:0:0:0: [sda] tag#15 Sense Key : Medium Error [current] [descriptor] 
[  320.252942] sd 0:0:0:0: [sda] tag#15 Add. Sense: Unrecovered read error - auto reallocate failed
[  320.252957] sd 0:0:0:0: [sda] tag#15 CDB: Read(10) 28 00 01 4c 6d d0 00 01 00 00
[  320.252965] blk_update_request: I/O error, dev sda, sector 21786064
[  320.253011] sd 0:0:0:0: [sda] tag#16 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[  320.253025] sd 0:0:0:0: [sda] tag#16 Sense Key : Medium Error [current] [descriptor] 
[  320.253042] sd 0:0:0:0: [sda] tag#16 Add. Sense: Unrecovered read error - auto reallocate failed
[  320.253055] sd 0:0:0:0: [sda] tag#16 CDB: Write(10) 2a 00 01 84 63 b0 00 00 08 00
[  320.253064] blk_update_request: I/O error, dev sda, sector 25453488
[  320.253079] EXT4-fs warning (device sda1): ext4_end_bio:330: I/O error -5 writing to inode 812989 (offset 0 size 0 starting block 3181687)
[  320.253092] Buffer I/O error on device sda1, logical block 3181430
[  320.253133] sd 0:0:0:0: [sda] tag#17 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[  320.253146] sd 0:0:0:0: [sda] tag#17 Sense Key : Medium Error [current] [descriptor] 
[  320.253161] sd 0:0:0:0: [sda] tag#17 Add. Sense: Unrecovered read error - auto reallocate failed
[  320.253174] sd 0:0:0:0: [sda] tag#17 CDB: Write(10) 2a 00 00 46 da 68 00 00 08 00
[  320.253182] blk_update_request: I/O error, dev sda, sector 4643432
[  320.253195] EXT4-fs warning (device sda1): ext4_end_bio:330: I/O error -5 writing to inode 262795 (offset 0 size 0 starting block 580430)
[  320.253205] Buffer I/O error on device sda1, logical block 580173
[  320.253242] sd 0:0:0:0: [sda] tag#18 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[  320.253256] sd 0:0:0:0: [sda] tag#18 Sense Key : Medium Error [current] [descriptor] 
[  320.253269] sd 0:0:0:0: [sda] tag#18 Add. Sense: Unrecovered read error - auto reallocate failed
[  320.253281] sd 0:0:0:0: [sda] tag#18 CDB: Write(10) 2a 00 00 c4 8a 70 00 00 b0 00
[  320.253285] JBD2: Detected IO errors while flushing file data on sda1-8
[  320.253300] blk_update_request: I/O error, dev sda, sector 12880496
[  320.253354] ata1: EH complete
[  320.253419] Aborting journal on device sda1-8.
[  320.303079] EXT4-fs error (device sda1): ext4_journal_check_start:56: Detected aborted journal
[  320.303093] EXT4-fs (sda1): Remounting filesystem read-only
[  324.126936] ata1.00: exception Emask 0x0 SAct 0x38 SErr 0x0 action 0x0
[  324.126950] ata1.00: irq_stat 0x40000001
[  324.126959] ata1.00: failed command: READ FPDMA QUEUED
[  324.126979] ata1.00: cmd 60/08:18:88:6d:4c/00:00:01:00:00/40 tag 3 ncq 4096 in
                        res 41/40:08:88:6d:4c/00:00:01:00:00/40 Emask 0x409 (media error) <F>
[  324.126988] ata1.00: status: { DRDY ERR }
[  324.126994] ata1.00: error: { UNC }
[  324.127003] ata1.00: failed command: READ FPDMA QUEUED
[  324.127021] ata1.00: cmd 60/d8:20:f0:5b:31/00:00:01:00:00/40 tag 4 ncq 110592 in
                        res 41/40:20:88:6d:4c/00:00:01:00:00/40 Emask 0x9 (media error)
[  324.127029] ata1.00: status: { DRDY ERR }
[  324.127035] ata1.00: error: { UNC }
[  324.127042] ata1.00: failed command: READ FPDMA QUEUED
[  324.127060] ata1.00: cmd 60/a0:28:b0:12:2c/00:00:01:00:00/40 tag 5 ncq 81920 in
                        res 41/40:20:88:6d:4c/00:00:01:00:00/40 Emask 0x9 (media error)
[  324.127068] ata1.00: status: { DRDY ERR }
[  324.127074] ata1.00: error: { UNC }
[  324.130220] ata1.00: configured for UDMA/100
[  324.130266] sd 0:0:0:0: [sda] tag#3 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[  324.130281] sd 0:0:0:0: [sda] tag#3 Sense Key : Medium Error [current] [descriptor] 
[  324.130294] sd 0:0:0:0: [sda] tag#3 Add. Sense: Unrecovered read error - auto reallocate failed
[  324.130309] sd 0:0:0:0: [sda] tag#3 CDB: Read(10) 28 00 01 4c 6d 88 00 00 08 00
[  324.130318] blk_update_request: I/O error, dev sda, sector 21785992
[  324.130370] sd 0:0:0:0: [sda] tag#4 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[  324.130382] sd 0:0:0:0: [sda] tag#4 Sense Key : Medium Error [current] [descriptor] 
[  324.130395] sd 0:0:0:0: [sda] tag#4 Add. Sense: Unrecovered read error - auto reallocate failed
[  324.130411] sd 0:0:0:0: [sda] tag#4 CDB: Read(10) 28 00 01 31 5b f0 00 00 d8 00
[  324.130419] blk_update_request: I/O error, dev sda, sector 20012016
[  324.130461] sd 0:0:0:0: [sda] tag#5 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[  324.130474] sd 0:0:0:0: [sda] tag#5 Sense Key : Medium Error [current] [descriptor] 
[  324.130486] sd 0:0:0:0: [sda] tag#5 Add. Sense: Unrecovered read error - auto reallocate failed
[  324.130499] sd 0:0:0:0: [sda] tag#5 CDB: Read(10) 28 00 01 2c 12 b0 00 00 a0 00
[  324.130506] blk_update_request: I/O error, dev sda, sector 19665584
[  324.130557] ata1: EH complete
[  327.929002] ata1.00: exception Emask 0x0 SAct 0x2a00000 SErr 0x0 action 0x0
[  327.929016] ata1.00: irq_stat 0x40000008
[  327.929027] ata1.00: failed command: READ FPDMA QUEUED
[  327.929051] ata1.00: cmd 60/08:a8:88:6d:4c/00:00:01:00:00/40 tag 21 ncq 4096 in
                        res 41/40:08:88:6d:4c/00:00:01:00:00/40 Emask 0x409 (media error) <F>
[  327.929061] ata1.00: status: { DRDY ERR }
[  327.929068] ata1.00: error: { UNC }
[  327.932375] ata1.00: configured for UDMA/100
[  327.932412] sd 0:0:0:0: [sda] tag#21 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[  327.932421] sd 0:0:0:0: [sda] tag#21 Sense Key : Medium Error [current] [descriptor] 
[  327.932444] sd 0:0:0:0: [sda] tag#21 Add. Sense: Unrecovered read error - auto reallocate failed
[  327.932455] sd 0:0:0:0: [sda] tag#21 CDB: Read(10) 28 00 01 4c 6d 88 00 00 08 00
[  327.932462] blk_update_request: I/O error, dev sda, sector 21785992
[  327.932499] ata1: EH complete

Dernière modification par ChrisForum (Le 24/09/2020, à 03:28)

Hors ligne

#2 Le 23/09/2020, à 13:28

geole

Re : [ Résolu ] Erreurs lors d'un dmesg

Bonjour
Il faudrait regarder l'état du disque avec l'application  https://doc.ubuntu-fr.org/smartmontools

sudo apt-get install --no-install-recommends smartmontools 

et poster le retour de cette commande pour interprétation

sudo smartctl   -s on  -a /dev/sda

Dernière modification par geole (Le 23/09/2020, à 13:30)


Les grilles de l'installateur https://doc.ubuntu-fr.org/tutoriel/inst … _subiquity
"gedit admin:///etc/fstab" est proscrit,  utilisez "pkexec env DISPLAY=$DISPLAY XAUTHORITY=$XAUTHORITY xdg-open /etc/fstab" Voir  https://doc.ubuntu-fr.org/gedit
Les partitions EXT4 des disques externes => https://forum.ubuntu-fr.org/viewtopic.p … #p22697248

Hors ligne

#3 Le 23/09/2020, à 20:09

ChrisForum

Re : [ Résolu ] Erreurs lors d'un dmesg

Bonsoir

Merci pour cette rapide réponse .
Voici ce que j'obtiens .

=== START OF INFORMATION SECTION ===
Model Family:     Toshiba 2.5" HDD MQ01ABF...
Device Model:     TOSHIBA MQ01ABF050
Serial Number:    335CC4AIT
LU WWN Device Id: 5 000039 4a38817ab
Firmware Version: AM003M
User Capacity:    500 107 862 016 bytes [500 GB]
Sector Size:      512 bytes logical/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:    Wed Sep 23 21:00:58 2020 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: 	 ( 118) 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       -       1309
  4 Start_Stop_Count        0x0032   100   100   000    Old_age   Always       -       1301
  5 Reallocated_Sector_Ct   0x0033   100   100   050    Pre-fail  Always       -       56
  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   084   084   000    Old_age   Always       -       6457
 10 Spin_Retry_Count        0x0033   125   100   030    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       1293
191 G-Sense_Error_Rate      0x0032   100   100   000    Old_age   Always       -       270
192 Power-Off_Retract_Count 0x0032   100   100   000    Old_age   Always       -       100
193 Load_Cycle_Count        0x0032   091   091   000    Old_age   Always       -       99300
194 Temperature_Celsius     0x0022   100   100   000    Old_age   Always       -       38 (Min/Max 12/50)
196 Reallocated_Event_Count 0x0032   100   100   000    Old_age   Always       -       7
197 Current_Pending_Sector  0x0032   100   100   000    Old_age   Always       -       1952
198 Offline_Uncorrectable   0x0030   100   100   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x0032   200   200   000    Old_age   Always       -       0
220 Disk_Shift              0x0002   100   100   000    Old_age   Always       -       0
222 Loaded_Hours            0x0032   085   085   000    Old_age   Always       -       6192
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       -       257
240 Head_Flying_Hours       0x0001   100   100   001    Pre-fail  Offline      -       0

SMART Error Log Version: 1
ATA Error Count: 18902 (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 18902 occurred at disk power-on lifetime: 6457 hours (269 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 41 e0 88 6d 4c 40  Error: WP at LBA = 0x004c6d88 = 5008776

  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 08 e8 00 08 00 40 00      00:29:58.540  WRITE FPDMA QUEUED
  60 08 e0 88 6d 4c 40 00      00:29:58.540  READ FPDMA QUEUED
  ea 00 00 00 00 00 a0 00      00:29:58.517  FLUSH CACHE EXT
  61 08 90 00 08 00 40 00      00:29:58.517  WRITE FPDMA QUEUED
  61 08 88 f8 23 c4 40 00      00:29:58.517  WRITE FPDMA QUEUED

Error 18901 occurred at disk power-on lifetime: 6457 hours (269 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 41 18 88 6d 4c 40  Error: WP at LBA = 0x004c6d88 = 5008776

  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 08 20 90 6e 48 40 00      00:29:58.432  WRITE FPDMA QUEUED
  60 08 18 88 6d 4c 40 00      00:29:54.731  READ FPDMA QUEUED
  60 08 10 80 6d 4c 40 00      00:29:54.731  READ FPDMA QUEUED
  60 08 08 78 6d 4c 40 00      00:29:54.731  READ FPDMA QUEUED
  60 08 00 70 6d 4c 40 00      00:29:54.730  READ FPDMA QUEUED

Error 18900 occurred at disk power-on lifetime: 6457 hours (269 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 41 d8 88 6d 4c 40  Error: UNC at LBA = 0x004c6d88 = 5008776

  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 e0 d0 6d 4c 40 00      00:29:54.621  READ FPDMA QUEUED
  60 00 d8 d0 6c 4c 40 00      00:29:50.898  READ FPDMA QUEUED
  60 00 d0 d0 6b 4c 40 00      00:29:50.886  READ FPDMA QUEUED
  60 00 c8 d0 6a 4c 40 00      00:29:50.879  READ FPDMA QUEUED
  60 00 c0 d0 69 4c 40 00      00:29:50.858  READ FPDMA QUEUED

Error 18899 occurred at disk power-on lifetime: 6456 hours (269 days + 0 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 41 78 58 08 40 40  Error: UNC at LBA = 0x00400858 = 4196440

  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 58 08 40 40 00      00:24:01.632  READ FPDMA QUEUED
  ef 10 02 00 00 00 a0 00      00:24:01.629  SET FEATURES [Enable SATA feature]
  27 00 00 00 00 00 e0 00      00:24:01.628  READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
  ec 00 00 00 00 00 a0 00      00:24:01.628  IDENTIFY DEVICE
  ef 03 45 00 00 00 a0 00      00:24:01.627  SET FEATURES [Set transfer mode]

Error 18898 occurred at disk power-on lifetime: 6456 hours (269 days + 0 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 41 48 58 08 40 40  Error: UNC at LBA = 0x00400858 = 4196440

  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 48 58 08 40 40 00      00:23:57.830  READ FPDMA QUEUED
  ef 10 02 00 00 00 a0 00      00:23:57.821  SET FEATURES [Enable SATA feature]
  27 00 00 00 00 00 e0 00      00:23:57.821  READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
  ec 00 00 00 00 00 a0 00      00:23:57.820  IDENTIFY DEVICE
  ef 03 45 00 00 00 a0 00      00:23:57.819  SET FEATURES [Set transfer mode]

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.

christophe@christophe-SATELLITE-PRO-C850-1LC:~$ sudo smartctl 

Hors ligne

#4 Le 23/09/2020, à 20:30

geole

Re : [ Résolu ] Erreurs lors d'un dmesg

ChrisForum a écrit :
=== START OF INFORMATION SECTION ===
Model Family:     Toshiba 2.5" HDD MQ01ABF...
Device Model:     TOSHIBA MQ01ABF050

ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  5 Reallocated_Sector_Ct   0x0033   100   100   050    Pre-fail  Always       -       56
  9 Power_On_Hours          0x0032   084   084   000    Old_age   Always       -       6457
197 Current_Pending_Sector  0x0032   100   100   000    Old_age   Always       -       1952

SMART Error Log Version: 1
Error 18902 occurred at disk power-on lifetime: 6457 hours (269 days + 1 hours)
Error 18901 occurred at disk power-on lifetime: 6457 hours (269 days + 1 hours)
Error 18900 occurred at disk power-on lifetime: 6457 hours (269 days + 1 hours)
Error 18899 occurred at disk power-on lifetime: 6456 hours (269 days + 0 hours)
Error 18898 occurred at disk power-on lifetime: 6456 hours (269 days + 0 hours) 

Disque à remplacer avant qu'il ne soit trop tard.
Il n'a su réparer que 56 secteurs. Il en reste 1952 à réparer malgré 18902 tentatives de réparation en 6457 heures de fonctionnement.

Notons que l'O.S. trouve que cela se dégrade rapidement.

EXT4-fs error (device sda1): ext4_journal_check_start:56: Detected aborted journal
[  320.303093] EXT4-fs (sda1): Remounting filesystem read-only 

Dernière modification par geole (Le 23/09/2020, à 20:44)


Les grilles de l'installateur https://doc.ubuntu-fr.org/tutoriel/inst … _subiquity
"gedit admin:///etc/fstab" est proscrit,  utilisez "pkexec env DISPLAY=$DISPLAY XAUTHORITY=$XAUTHORITY xdg-open /etc/fstab" Voir  https://doc.ubuntu-fr.org/gedit
Les partitions EXT4 des disques externes => https://forum.ubuntu-fr.org/viewtopic.p … #p22697248

Hors ligne

#5 Le 24/09/2020, à 03:25

ChrisForum

Re : [ Résolu ] Erreurs lors d'un dmesg

Bonjour

C’est ce que je craignais , maintenant j’en suis sûr  smile .

Donc j’ai déjà sauvegardé toutes mes donnés .
Merci beaucoup Geole.

Hors ligne