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.

Pages : 1 2 3 … 6

nombre réponses : 25

#0 -1 »  [RESOLU] Disque systéme qui passe en lecture seule après qques minutes » Le 23/01/2019, à 17:14

Soipacon
Réponses : 22

Bonjour à tous.
Je m'arrache les cheveux depuis quelques temps avec un problème assez étrange :

Quand je démarre mon pc (un ssd pour le système et plusieurs hdd), tout se passe bien et tout semble fonctionner.
Puis après quelques minutes, parfois quelques heures, ma partition ext4 montée sur "/" passe en lecture seule, les autres partitions ("/home" et disques de données ne sont pas impactées).
Résultat: système complètement instable, tous les programmes qui ont besoin d'écrire sur "/" ne fonctionnent plus.

Indice important :
Ce problème est apparu après une installation de windows 10 sur un hdd à part et utilisation d'un soft pour avoir accès à mes partitions ext4 depuis windows (Linux File Systems for Windows by Paragon Software).
Après l'installation j'ai du réparer GRUB et lancer manuellement un fsck sur "/" (il y a eu des erreurs corrigées), après quoi tout avait l'air de fonctionner.
A noter que le démarrage rapide de windows a bien été désactivé, encore que je ne vois pas trop comment ça pourrait poser problème avec une partition ext4 ?

J'ai longuement écumé les forums mais là vraiment je câle.

Quelqu'un aurait il une idée de génie qui expliquerai tout ça ?

Merci

#1 Re : -1 »  [RESOLU] Disque systéme qui passe en lecture seule après qques minutes » Le 23/01/2019, à 17:49

Soipacon
Réponses : 22

Oui mais c'est un vieux pc qui avait dejà son disque ubuntu...

Il y a des chances pour que ça se termine par une réinstall propre d'ubuntu mais j'aurai quand même bien aimé comprendre ce qui se passe.

#2 Re : -1 »  [RESOLU] Disque systéme qui passe en lecture seule après qques minutes » Le 23/01/2019, à 19:13

Soipacon
Réponses : 22

Merci de ton aide. 

sudo smartctl  -s   on    -a    /dev/sdX

Me renvoi ceci :

smartctl 6.6 2016-05-31 r4324 [x86_64-linux-4.15.0-43-generic] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     SanDisk based SSDs
Device Model:     SanDisk SDSSDP128G
Serial Number:    152755404172
LU WWN Device Id: 5 001b44 e9c83798c
Firmware Version: 3.2.0
User Capacity:    126035288064 bytes [126 GB]
Sector Size:      512 bytes logical/physical
Rotation Rate:    Solid State Device
Form Factor:      1.8 inches
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ACS-2 T13/2015-D revision 3
SATA Version is:  SATA 3.0, 6.0 Gb/s (current: 3.0 Gb/s)
Local Time is:    Wed Jan 23 18:07:21 2019 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:      (   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: 			 (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: 	 (  21) minutes.

SMART Attributes Data Structure revision number: 1
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  5 Reallocated_Sector_Ct   0x0002   100   100   000    Old_age   Always       -       0
  9 Power_On_Hours          0x0002   100   100   000    Old_age   Always       -       16475
 12 Power_Cycle_Count       0x0002   100   100   000    Old_age   Always       -       1354
165 Total_Write/Erase_Count 0x0002   100   100   000    Old_age   Always       -       147579
171 Program_Fail_Count      0x0002   100   100   000    Old_age   Always       -       0
172 Erase_Fail_Count        0x0002   100   100   000    Old_age   Always       -       0
173 Avg_Write/Erase_Count   0x0002   100   100   000    Old_age   Always       -       37
174 Unexpect_Power_Loss_Ct  0x0002   100   100   000    Old_age   Always       -       43
187 Reported_Uncorrect      0x0002   100   100   000    Old_age   Always       -       0
194 Temperature_Celsius     0x0022   070   030   000    Old_age   Always       -       30 (Min/Max 4/41)
230 Perc_Write/Erase_Count  0x0002   100   100   000    Old_age   Always       -       123
232 Perc_Avail_Resrvd_Space 0x0003   100   100   005    Pre-fail  Always       -       0
234 Perc_Write/Erase_Ct_BC  0x0002   100   100   000    Old_age   Always       -       475
241 Total_LBAs_Written      0x0002   100   100   000    Old_age   Always       -       10209771382
242 Total_LBAs_Read         0x0002   100   100   000    Old_age   Always       -       15891743965

SMART Error Log Version: 1
No Errors Logged

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Extended offline    Aborted by host               90%     15194         -

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.

Dès que le problème apparaitra je posterai la réponse à la 2e commande.

#3 Re : -1 »  [RESOLU] Disque systéme qui passe en lecture seule après qques minutes » Le 23/01/2019, à 21:07

Soipacon
Réponses : 22

Et maintenant je suis à nouveau en lecture seule.

dmesg | tail -200

Me renvoi 

[ 3371.815847] EXT4-fs warning (device sda1): ext4_dirent_csum_verify:353: inode #12714410: comm rsync: No space for directory leaf checksum. Please run e2fsck -D.
[ 3371.815854] EXT4-fs error (device sda1): ext4_find_entry:1447: inode #12714410: comm rsync: checksumming directory block 0
[ 3501.526594] EXT4-fs warning (device sdb1): ext4_dirent_csum_verify:353: inode #1364167: comm rsync: No space for directory leaf checksum. Please run e2fsck -D.
[ 3501.526602] EXT4-fs error (device sdb1): htree_dirblock_to_tree:977: inode #1364167: comm rsync: Directory block failed checksum
[ 3501.529613] Aborting journal on device sdb1-8.
[ 3501.532497] EXT4-fs (sdb1): Remounting filesystem read-only
[ 3501.532634] EXT4-fs error (device sdb1): ext4_journal_check_start:61: Detected aborted journal
[ 3584.110458] systemd-journald[371]: Failed to write entry (21 items, 603 bytes), ignoring: Read-only file system
[ 3584.110534] systemd-journald[371]: Failed to write entry (21 items, 694 bytes), ignoring: Read-only file system
[ 3584.110568] systemd-journald[371]: Failed to write entry (21 items, 603 bytes), ignoring: Read-only file system
[ 3584.110601] systemd-journald[371]: Failed to write entry (21 items, 694 bytes), ignoring: Read-only file system
[ 3584.110631] systemd-journald[371]: Failed to write entry (21 items, 603 bytes), ignoring: Read-only file system
[ 3584.110661] systemd-journald[371]: Failed to write entry (21 items, 694 bytes), ignoring: Read-only file system
[ 3584.110691] systemd-journald[371]: Failed to write entry (21 items, 603 bytes), ignoring: Read-only file system
[ 3584.110731] systemd-journald[371]: Failed to write entry (21 items, 694 bytes), ignoring: Read-only file system
[ 3584.110761] systemd-journald[371]: Failed to write entry (21 items, 603 bytes), ignoring: Read-only file system
[ 3584.110797] systemd-journald[371]: Failed to write entry (21 items, 694 bytes), ignoring: Read-only file system
[ 3603.778443] systemd-journald[371]: Failed to write entry (24 items, 566 bytes), ignoring: Read-only file system
[ 3603.779305] systemd-journald[371]: Failed to write entry (21 items, 603 bytes), ignoring: Read-only file system
[ 3603.779384] systemd-journald[371]: Failed to write entry (21 items, 694 bytes), ignoring: Read-only file system
[ 3603.779442] systemd-journald[371]: Failed to write entry (21 items, 603 bytes), ignoring: Read-only file system
[ 3603.779499] systemd-journald[371]: Failed to write entry (21 items, 694 bytes), ignoring: Read-only file system
[ 3603.779546] systemd-journald[371]: Failed to write entry (21 items, 582 bytes), ignoring: Read-only file system
[ 3603.779743] systemd-journald[371]: Failed to write entry (21 items, 603 bytes), ignoring: Read-only file system
[ 3603.779793] systemd-journald[371]: Failed to write entry (21 items, 694 bytes), ignoring: Read-only file system
[ 3603.779848] systemd-journald[371]: Failed to write entry (21 items, 603 bytes), ignoring: Read-only file system
[ 3603.779904] systemd-journald[371]: Failed to write entry (21 items, 694 bytes), ignoring: Read-only file system
[ 3610.326333] systemd-journald[371]: Failed to write entry (22 items, 622 bytes), ignoring: Read-only file system
[ 3610.326977] systemd-journald[371]: Failed to write entry (21 items, 603 bytes), ignoring: Read-only file system
[ 3610.327027] systemd-journald[371]: Failed to write entry (21 items, 694 bytes), ignoring: Read-only file system
[ 3610.327055] systemd-journald[371]: Failed to write entry (21 items, 582 bytes), ignoring: Read-only file system
[ 3610.327083] systemd-journald[371]: Failed to write entry (21 items, 603 bytes), ignoring: Read-only file system
[ 3610.327109] systemd-journald[371]: Failed to write entry (21 items, 694 bytes), ignoring: Read-only file system
[ 3610.327312] systemd-journald[371]: Failed to write entry (21 items, 603 bytes), ignoring: Read-only file system
[ 3610.327343] systemd-journald[371]: Failed to write entry (21 items, 694 bytes), ignoring: Read-only file system
[ 3610.327369] systemd-journald[371]: Failed to write entry (21 items, 603 bytes), ignoring: Read-only file system
[ 3610.327395] systemd-journald[371]: Failed to write entry (21 items, 694 bytes), ignoring: Read-only file system
[ 3759.189999] systemd-journald[371]: Failed to write entry (22 items, 622 bytes), ignoring: Read-only file system
[ 3759.190052] systemd-journald[371]: Failed to write entry (22 items, 618 bytes), ignoring: Read-only file system
[ 3759.190242] systemd-journald[371]: Failed to write entry (21 items, 603 bytes), ignoring: Read-only file system
[ 3759.190321] systemd-journald[371]: Failed to write entry (21 items, 694 bytes), ignoring: Read-only file system
[ 3759.190402] systemd-journald[371]: Failed to write entry (21 items, 582 bytes), ignoring: Read-only file system
[ 3759.190437] systemd-journald[371]: Failed to write entry (21 items, 603 bytes), ignoring: Read-only file system
[ 3759.190471] systemd-journald[371]: Failed to write entry (21 items, 694 bytes), ignoring: Read-only file system
[ 3759.190508] systemd-journald[371]: Failed to write entry (21 items, 603 bytes), ignoring: Read-only file system
[ 3759.190542] systemd-journald[371]: Failed to write entry (21 items, 694 bytes), ignoring: Read-only file system
[ 3759.190574] systemd-journald[371]: Failed to write entry (21 items, 603 bytes), ignoring: Read-only file system
[ 3964.601481] systemd-journald[371]: Failed to write entry (26 items, 679 bytes), ignoring: Read-only file system
[ 3964.601792] systemd-journald[371]: Failed to write entry (21 items, 603 bytes), ignoring: Read-only file system
[ 3964.601882] systemd-journald[371]: Failed to write entry (21 items, 694 bytes), ignoring: Read-only file system
[ 3964.602050] systemd-journald[371]: Failed to write entry (21 items, 582 bytes), ignoring: Read-only file system
[ 3964.602105] systemd-journald[371]: Failed to write entry (21 items, 603 bytes), ignoring: Read-only file system
[ 3964.602150] systemd-journald[371]: Failed to write entry (21 items, 694 bytes), ignoring: Read-only file system
[ 3964.602193] systemd-journald[371]: Failed to write entry (21 items, 603 bytes), ignoring: Read-only file system
[ 3964.602240] systemd-journald[371]: Failed to write entry (21 items, 694 bytes), ignoring: Read-only file system
[ 3964.602368] systemd-journald[371]: Failed to write entry (21 items, 603 bytes), ignoring: Read-only file system
[ 3964.602520] systemd-journald[371]: Failed to write entry (21 items, 694 bytes), ignoring: Read-only file system
[ 4380.884100] systemd-journald[371]: Failed to write entry (22 items, 543 bytes), ignoring: Read-only file system
[ 4380.884298] systemd-journald[371]: Failed to write entry (21 items, 603 bytes), ignoring: Read-only file system
[ 4380.884334] systemd-journald[371]: Failed to write entry (21 items, 694 bytes), ignoring: Read-only file system
[ 4380.884363] systemd-journald[371]: Failed to write entry (21 items, 582 bytes), ignoring: Read-only file system
[ 4380.884460] systemd-journald[371]: Failed to write entry (21 items, 603 bytes), ignoring: Read-only file system
[ 4380.884515] systemd-journald[371]: Failed to write entry (21 items, 694 bytes), ignoring: Read-only file system
[ 4380.884541] systemd-journald[371]: Failed to write entry (21 items, 603 bytes), ignoring: Read-only file system
[ 4380.884567] systemd-journald[371]: Failed to write entry (21 items, 694 bytes), ignoring: Read-only file system
[ 4380.884594] systemd-journald[371]: Failed to write entry (21 items, 603 bytes), ignoring: Read-only file system
[ 4380.884621] systemd-journald[371]: Failed to write entry (21 items, 694 bytes), ignoring: Read-only file system
[ 4840.145079] systemd-journald[371]: Failed to write entry (29 items, 824 bytes), ignoring: Read-only file system
[ 4840.145160] systemd-journald[371]: Failed to write entry (28 items, 797 bytes), ignoring: Read-only file system
[ 4840.145497] systemd-journald[371]: Failed to write entry (21 items, 603 bytes), ignoring: Read-only file system
[ 4840.145553] systemd-journald[371]: Failed to write entry (21 items, 694 bytes), ignoring: Read-only file system
[ 4840.145611] systemd-journald[371]: Failed to write entry (21 items, 582 bytes), ignoring: Read-only file system
[ 4840.145660] systemd-journald[371]: Failed to write entry (21 items, 603 bytes), ignoring: Read-only file system
[ 4840.145708] systemd-journald[371]: Failed to write entry (21 items, 694 bytes), ignoring: Read-only file system
[ 4840.145751] systemd-journald[371]: Failed to write entry (21 items, 603 bytes), ignoring: Read-only file system
[ 4840.145793] systemd-journald[371]: Failed to write entry (21 items, 694 bytes), ignoring: Read-only file system
[ 4840.145836] systemd-journald[371]: Failed to write entry (21 items, 603 bytes), ignoring: Read-only file system
[ 5140.153713] systemd-journald[371]: Failed to write entry (29 items, 824 bytes), ignoring: Read-only file system
[ 5140.164107] systemd-journald[371]: Failed to write entry (21 items, 603 bytes), ignoring: Read-only file system
[ 5140.164300] systemd-journald[371]: Failed to write entry (21 items, 694 bytes), ignoring: Read-only file system
[ 5140.164370] systemd-journald[371]: Failed to write entry (21 items, 582 bytes), ignoring: Read-only file system
[ 5140.164437] systemd-journald[371]: Failed to write entry (21 items, 603 bytes), ignoring: Read-only file system
[ 5140.164500] systemd-journald[371]: Failed to write entry (21 items, 694 bytes), ignoring: Read-only file system
[ 5140.164580] systemd-journald[371]: Failed to write entry (21 items, 603 bytes), ignoring: Read-only file system
[ 5140.164652] systemd-journald[371]: Failed to write entry (21 items, 694 bytes), ignoring: Read-only file system
[ 5140.166247] systemd-journald[371]: Failed to write entry (21 items, 603 bytes), ignoring: Read-only file system
[ 5140.166351] systemd-journald[371]: Failed to write entry (21 items, 694 bytes), ignoring: Read-only file system
[ 5162.227523] perf: interrupt took too long (2506 > 2500), lowering kernel.perf_event_max_sample_rate to 79750
[ 5162.228747] systemd-journald[371]: Failed to write entry (9 items, 313 bytes), ignoring: Read-only file system
[ 5162.229530] systemd-journald[371]: Failed to write entry (21 items, 603 bytes), ignoring: Read-only file system
[ 5162.229653] systemd-journald[371]: Failed to write entry (21 items, 694 bytes), ignoring: Read-only file system
[ 5162.229800] systemd-journald[371]: Failed to write entry (21 items, 603 bytes), ignoring: Read-only file system
[ 5162.229908] systemd-journald[371]: Failed to write entry (21 items, 694 bytes), ignoring: Read-only file system
[ 5162.230019] systemd-journald[371]: Failed to write entry (21 items, 582 bytes), ignoring: Read-only file system
[ 5162.230301] systemd-journald[371]: Failed to write entry (21 items, 603 bytes), ignoring: Read-only file system
[ 5162.230354] systemd-journald[371]: Failed to write entry (21 items, 694 bytes), ignoring: Read-only file system
[ 5162.230389] systemd-journald[371]: Failed to write entry (21 items, 603 bytes), ignoring: Read-only file system
[ 5162.230424] systemd-journald[371]: Failed to write entry (21 items, 694 bytes), ignoring: Read-only file system
[ 5418.780096] systemd-journald[371]: Failed to write entry (28 items, 799 bytes), ignoring: Read-only file system
[ 5418.782247] systemd-journald[371]: Failed to write entry (22 items, 849 bytes), ignoring: Read-only file system
[ 5418.782479] systemd-journald[371]: Failed to write entry (21 items, 603 bytes), ignoring: Read-only file system
[ 5418.782533] systemd-journald[371]: Failed to write entry (21 items, 694 bytes), ignoring: Read-only file system
[ 5418.782580] systemd-journald[371]: Failed to write entry (21 items, 582 bytes), ignoring: Read-only file system
[ 5418.782623] systemd-journald[371]: Failed to write entry (21 items, 603 bytes), ignoring: Read-only file system
[ 5418.782674] systemd-journald[371]: Failed to write entry (21 items, 694 bytes), ignoring: Read-only file system
[ 5418.782722] systemd-journald[371]: Failed to write entry (21 items, 603 bytes), ignoring: Read-only file system
[ 5418.782765] systemd-journald[371]: Failed to write entry (21 items, 694 bytes), ignoring: Read-only file system
[ 5418.783154] systemd-journald[371]: Failed to write entry (21 items, 603 bytes), ignoring: Read-only file system
[ 5558.617209] systemd-journald[371]: Failed to write entry (22 items, 622 bytes), ignoring: Read-only file system
[ 5558.617348] systemd-journald[371]: Failed to write entry (22 items, 618 bytes), ignoring: Read-only file system
[ 5558.617862] systemd-journald[371]: Failed to write entry (21 items, 603 bytes), ignoring: Read-only file system
[ 5558.617976] systemd-journald[371]: Failed to write entry (21 items, 694 bytes), ignoring: Read-only file system
[ 5558.618081] systemd-journald[371]: Failed to write entry (21 items, 582 bytes), ignoring: Read-only file system
[ 5558.618207] systemd-journald[371]: Failed to write entry (21 items, 603 bytes), ignoring: Read-only file system
[ 5558.618315] systemd-journald[371]: Failed to write entry (21 items, 694 bytes), ignoring: Read-only file system
[ 5558.618435] systemd-journald[371]: Failed to write entry (21 items, 603 bytes), ignoring: Read-only file system
[ 5558.618547] systemd-journald[371]: Failed to write entry (21 items, 694 bytes), ignoring: Read-only file system
[ 5558.618652] systemd-journald[371]: Failed to write entry (21 items, 603 bytes), ignoring: Read-only file system
[ 5740.169631] systemd-journald[371]: Failed to write entry (29 items, 824 bytes), ignoring: Read-only file system
[ 5740.169773] systemd-journald[371]: Failed to write entry (28 items, 797 bytes), ignoring: Read-only file system
[ 5740.170243] systemd-journald[371]: Failed to write entry (22 items, 849 bytes), ignoring: Read-only file system
[ 5740.171614] systemd-journald[371]: Failed to write entry (21 items, 603 bytes), ignoring: Read-only file system
[ 5740.171656] systemd-journald[371]: Failed to write entry (21 items, 694 bytes), ignoring: Read-only file system
[ 5740.171692] systemd-journald[371]: Failed to write entry (21 items, 603 bytes), ignoring: Read-only file system
[ 5740.171725] systemd-journald[371]: Failed to write entry (21 items, 694 bytes), ignoring: Read-only file system
[ 5740.171758] systemd-journald[371]: Failed to write entry (21 items, 603 bytes), ignoring: Read-only file system
[ 5740.171790] systemd-journald[371]: Failed to write entry (21 items, 694 bytes), ignoring: Read-only file system
[ 5740.171832] systemd-journald[371]: Failed to write entry (21 items, 603 bytes), ignoring: Read-only file system
[ 6014.621721] systemd-journald[371]: Failed to write entry (28 items, 799 bytes), ignoring: Read-only file system
[ 6014.627063] systemd-journald[371]: Failed to write entry (26 items, 707 bytes), ignoring: Read-only file system
[ 6014.627240] systemd-journald[371]: Failed to write entry (22 items, 849 bytes), ignoring: Read-only file system
[ 6014.627868] systemd-journald[371]: Failed to write entry (21 items, 603 bytes), ignoring: Read-only file system
[ 6014.627908] systemd-journald[371]: Failed to write entry (21 items, 694 bytes), ignoring: Read-only file system
[ 6014.627940] systemd-journald[371]: Failed to write entry (21 items, 582 bytes), ignoring: Read-only file system
[ 6014.627987] systemd-journald[371]: Failed to write entry (21 items, 603 bytes), ignoring: Read-only file system
[ 6014.628022] systemd-journald[371]: Failed to write entry (21 items, 694 bytes), ignoring: Read-only file system
[ 6014.628055] systemd-journald[371]: Failed to write entry (21 items, 603 bytes), ignoring: Read-only file system
[ 6014.628088] systemd-journald[371]: Failed to write entry (21 items, 694 bytes), ignoring: Read-only file system
[ 6640.195595] systemd-journald[371]: Failed to write entry (29 items, 824 bytes), ignoring: Read-only file system
[ 6640.195715] systemd-journald[371]: Failed to write entry (28 items, 797 bytes), ignoring: Read-only file system
[ 6640.196641] systemd-journald[371]: Failed to write entry (21 items, 603 bytes), ignoring: Read-only file system
[ 6640.196693] systemd-journald[371]: Failed to write entry (21 items, 694 bytes), ignoring: Read-only file system
[ 6640.196742] systemd-journald[371]: Failed to write entry (21 items, 603 bytes), ignoring: Read-only file system
[ 6640.196775] systemd-journald[371]: Failed to write entry (21 items, 694 bytes), ignoring: Read-only file system
[ 6640.196807] systemd-journald[371]: Failed to write entry (21 items, 603 bytes), ignoring: Read-only file system
[ 6640.196839] systemd-journald[371]: Failed to write entry (21 items, 694 bytes), ignoring: Read-only file system
[ 6640.196869] systemd-journald[371]: Failed to write entry (21 items, 582 bytes), ignoring: Read-only file system
[ 6640.196900] systemd-journald[371]: Failed to write entry (21 items, 603 bytes), ignoring: Read-only file system
[ 6940.204139] systemd-journald[371]: Failed to write entry (29 items, 824 bytes), ignoring: Read-only file system
[ 6940.204680] systemd-journald[371]: Failed to write entry (21 items, 603 bytes), ignoring: Read-only file system
[ 6940.204724] systemd-journald[371]: Failed to write entry (21 items, 694 bytes), ignoring: Read-only file system
[ 6940.204784] systemd-journald[371]: Failed to write entry (21 items, 582 bytes), ignoring: Read-only file system
[ 6940.205124] systemd-journald[371]: Failed to write entry (21 items, 603 bytes), ignoring: Read-only file system
[ 6940.205162] systemd-journald[371]: Failed to write entry (21 items, 694 bytes), ignoring: Read-only file system
[ 6940.205189] systemd-journald[371]: Failed to write entry (21 items, 603 bytes), ignoring: Read-only file system
[ 6940.205215] systemd-journald[371]: Failed to write entry (21 items, 694 bytes), ignoring: Read-only file system
[ 6940.205243] systemd-journald[371]: Failed to write entry (21 items, 603 bytes), ignoring: Read-only file system
[ 6940.205269] systemd-journald[371]: Failed to write entry (21 items, 694 bytes), ignoring: Read-only file system
[ 6960.973742] systemd-journald[371]: Failed to write entry (22 items, 543 bytes), ignoring: Read-only file system
[ 6960.974536] systemd-journald[371]: Failed to write entry (21 items, 603 bytes), ignoring: Read-only file system
[ 6960.974605] systemd-journald[371]: Failed to write entry (21 items, 694 bytes), ignoring: Read-only file system
[ 6960.974654] systemd-journald[371]: Failed to write entry (21 items, 582 bytes), ignoring: Read-only file system
[ 6960.974956] systemd-journald[371]: Failed to write entry (21 items, 603 bytes), ignoring: Read-only file system
[ 6960.975011] systemd-journald[371]: Failed to write entry (21 items, 694 bytes), ignoring: Read-only file system
[ 6960.975056] systemd-journald[371]: Failed to write entry (21 items, 603 bytes), ignoring: Read-only file system
[ 6960.975101] systemd-journald[371]: Failed to write entry (21 items, 694 bytes), ignoring: Read-only file system
[ 6960.975158] systemd-journald[371]: Failed to write entry (21 items, 603 bytes), ignoring: Read-only file system
[ 6960.975202] systemd-journald[371]: Failed to write entry (21 items, 694 bytes), ignoring: Read-only file system
[ 7024.693719] systemd-journald[371]: Failed to write entry (28 items, 667 bytes), ignoring: Read-only file system
[ 7024.694552] systemd-journald[371]: Failed to write entry (21 items, 603 bytes), ignoring: Read-only file system
[ 7024.694602] systemd-journald[371]: Failed to write entry (21 items, 694 bytes), ignoring: Read-only file system
[ 7024.694641] systemd-journald[371]: Failed to write entry (21 items, 582 bytes), ignoring: Read-only file system
[ 7024.694853] systemd-journald[371]: Failed to write entry (21 items, 603 bytes), ignoring: Read-only file system
[ 7024.694889] systemd-journald[371]: Failed to write entry (21 items, 694 bytes), ignoring: Read-only file system
[ 7024.694923] systemd-journald[371]: Failed to write entry (21 items, 603 bytes), ignoring: Read-only file system
[ 7024.694956] systemd-journald[371]: Failed to write entry (21 items, 694 bytes), ignoring: Read-only file system
[ 7024.694989] systemd-journald[371]: Failed to write entry (21 items, 603 bytes), ignoring: Read-only file system
[ 7024.695022] systemd-journald[371]: Failed to write entry (21 items, 694 bytes), ignoring: Read-only file system
[ 7030.491913] systemd-journald[371]: Failed to write entry (24 items, 847 bytes), ignoring: Read-only file system
[ 7030.491978] systemd-journald[371]: Failed to write entry (24 items, 747 bytes), ignoring: Read-only file system
[ 7043.725219] systemd-journald[371]: Failed to write entry (24 items, 736 bytes), ignoring: Read-only file system
[ 7043.725769] systemd-journald[371]: Failed to write entry (21 items, 603 bytes), ignoring: Read-only file system
[ 7043.725806] systemd-journald[371]: Failed to write entry (21 items, 694 bytes), ignoring: Read-only file system
[ 7043.725830] systemd-journald[371]: Failed to write entry (21 items, 582 bytes), ignoring: Read-only file system
[ 7043.726116] systemd-journald[371]: Failed to write entry (21 items, 603 bytes), ignoring: Read-only file system
[ 7043.726144] systemd-journald[371]: Failed to write entry (21 items, 694 bytes), ignoring: Read-only file system
[ 7043.726170] systemd-journald[371]: Failed to write entry (21 items, 603 bytes), ignoring: Read-only file system
[ 7043.726195] systemd-journald[371]: Failed to write entry (21 items, 694 bytes), ignoring: Read-only file system
[ 7043.726220] systemd-journald[371]: Failed to write entry (21 items, 603 bytes), ignoring: Read-only file system
[ 7043.726245] systemd-journald[371]: Failed to write entry (21 items, 694 bytes), ignoring: Read-only file system
[ 7070.183022] systemd-journald[371]: Failed to write entry (24 items, 673 bytes), ignoring: Read-only file system
[ 7070.183199] systemd-journald[371]: Failed to write entry (24 items, 656 bytes), ignoring: Read-only file system
[ 7070.183402] systemd-journald[371]: Failed to write entry (21 items, 603 bytes), ignoring: Read-only file system
[ 7070.183444] systemd-journald[371]: Failed to write entry (21 items, 694 bytes), ignoring: Read-only file system
[ 7070.183479] systemd-journald[371]: Failed to write entry (21 items, 582 bytes), ignoring: Read-only file system
[ 7070.183517] systemd-journald[371]: Failed to write entry (21 items, 603 bytes), ignoring: Read-only file system
[ 7070.183556] systemd-journald[371]: Failed to write entry (21 items, 694 bytes), ignoring: Read-only file system
[ 7070.183590] systemd-journald[371]: Failed to write entry (21 items, 603 bytes), ignoring: Read-only file system
[ 7070.183628] systemd-journald[371]: Failed to write entry (21 items, 694 bytes), ignoring: Read-only file system
[ 7070.183663] systemd-journald[371]: Failed to write entry (21 items, 603 bytes), ignoring: Read-only file system

Merci encore à ceux qui se penchent sur mon problème.

#4 Re : -1 »  [RESOLU] Disque systéme qui passe en lecture seule après qques minutes » Le 23/01/2019, à 21:52

Soipacon
Réponses : 22

df -h --->

Sys. de fichiers Taille Utilisé Dispo Uti% Monté sur
udev               1,7G       0  1,7G   0% /dev
tmpfs              345M    3,3M  341M   1% /run
/dev/sdb1           28G     13G   14G  47% /
tmpfs              1,7G    320M  1,4G  19% /dev/shm
tmpfs              5,0M    4,0K  5,0M   1% /run/lock
tmpfs              1,7G       0  1,7G   0% /sys/fs/cgroup
/dev/sdb2           83G    8,8G   70G  12% /home
/dev/sda1          458G    163G  272G  38% /media/jerome/donnees_old_mint
tmpfs              345M     40K  344M   1% /run/user/1000
/dev/sdc1          1,4T    1,2T   93G  93% /media/jerome/Videos
/dev/sdc2          1,4T    601G  706G  46% /media/jerome/Sauvegardes

df -i --->

Sys. de fichiers   Inœuds IUtil.   ILibre IUti% Monté sur
udev               424041    560   423481    1% /dev
tmpfs              440342   1036   439306    1% /run
/dev/sdb1         1831424 433501  1397923   24% /
tmpfs              440342    394   439948    1% /dev/shm
tmpfs              440342      6   440336    1% /run/lock
tmpfs              440342     18   440324    1% /sys/fs/cgroup
/dev/sdb2         5545984  84668  5461316    2% /home
/dev/sda1        30531584 655051 29876533    3% /media/jerome/donnees_old_mint
tmpfs              440342     32   440310    1% /run/user/1000
/dev/sdc1        91553792   4954 91548838    1% /media/jerome/Videos
/dev/sdc2        91594752 107246 91487506    1% /media/jerome/Sauvegardes

sudo smartctl  -s   on    -a  /dev/sdb     --->

smartctl 6.6 2016-05-31 r4324 [x86_64-linux-4.15.0-43-generic] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     SanDisk based SSDs
Device Model:     SanDisk SDSSDP128G
Serial Number:    152755404172
LU WWN Device Id: 5 001b44 e9c83798c
Firmware Version: 3.2.0
User Capacity:    126035288064 bytes [126 GB]
Sector Size:      512 bytes logical/physical
Rotation Rate:    Solid State Device
Form Factor:      1.8 inches
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ACS-2 T13/2015-D revision 3
SATA Version is:  SATA 3.0, 6.0 Gb/s (current: 3.0 Gb/s)
Local Time is:    Wed Jan 23 20:51:44 2019 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:      (   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: 			 (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: 	 (  21) minutes.

SMART Attributes Data Structure revision number: 1
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  5 Reallocated_Sector_Ct   0x0002   100   100   000    Old_age   Always       -       0
  9 Power_On_Hours          0x0002   100   100   000    Old_age   Always       -       16477
 12 Power_Cycle_Count       0x0002   100   100   000    Old_age   Always       -       1354
165 Total_Write/Erase_Count 0x0002   100   100   000    Old_age   Always       -       147677
171 Program_Fail_Count      0x0002   100   100   000    Old_age   Always       -       0
172 Erase_Fail_Count        0x0002   100   100   000    Old_age   Always       -       0
173 Avg_Write/Erase_Count   0x0002   100   100   000    Old_age   Always       -       37
174 Unexpect_Power_Loss_Ct  0x0002   100   100   000    Old_age   Always       -       43
187 Reported_Uncorrect      0x0002   100   100   000    Old_age   Always       -       0
194 Temperature_Celsius     0x0022   069   031   000    Old_age   Always       -       31 (Min/Max 4/41)
230 Perc_Write/Erase_Count  0x0002   100   100   000    Old_age   Always       -       123
232 Perc_Avail_Resrvd_Space 0x0003   100   100   005    Pre-fail  Always       -       0
234 Perc_Write/Erase_Ct_BC  0x0002   100   100   000    Old_age   Always       -       475
241 Total_LBAs_Written      0x0002   100   100   000    Old_age   Always       -       10217548238
242 Total_LBAs_Read         0x0002   100   100   000    Old_age   Always       -       15898515733

SMART Error Log Version: 1
No Errors Logged

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Extended offline    Aborted by host               90%     15194         -

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.

#5 Re : -1 »  [RESOLU] Disque systéme qui passe en lecture seule après qques minutes » Le 24/01/2019, à 11:43

Soipacon
Réponses : 22

Désolé j'ai été maladroit dans ma manière de donner mes retours, j'y ferai plus attention.

Pour être clair, seul sdb est un ssd (c'est mon disque "système"), les autres sont des hdd de données.
Et sdb ne contient aucune donnée importante

Donc pour la dernière commande j'ai :

jerome@mint-old:~$ sudo lsblk -o name,fstype,label,size,mountpoint | grep -Ev "loop|sr[0-9]"; echo; echo; ls -l /dev/disk/by-id/ | grep -v part[0-9]
[sudo] Mot de passe de jerome : 
NAME   FSTYPE LABEL         SIZE MOUNTPOINT
sda                       465,8G 
└─sda1 ext4               465,8G /media/jerome/donnees_old_mint
sdb                       117,4G 
├─sdb1 ext4                  28G /
├─sdb2 ext4                84,6G /home
└─sdb3 swap                 4,9G [SWAP]
sdc                         2,7T 
├─sdc1 ext4   Videos        1,4T /media/jerome/Videos
└─sdc2 ext4   Sauvegardes   1,4T /media/jerome/Sauvegardes


total 0
lrwxrwxrwx 1 root root  9 janv. 23 18:04 ata-SanDisk_SDSSDP128G_152755404172 -> ../../sdb
lrwxrwxrwx 1 root root  9 janv. 23 18:04 ata-ST3000DM001-1ER166_Z5034SA8 -> ../../sdc
lrwxrwxrwx 1 root root  9 janv. 23 18:04 ata-ST500DM002-1BD142_Z3TDV19P -> ../../sda
lrwxrwxrwx 1 root root  9 janv. 23 18:04 ata-TSSTcorp_CDDVDW_SH-S223Q -> ../../sr0
lrwxrwxrwx 1 root root  9 janv. 23 18:04 wwn-0x5000c5004fbfd2ac -> ../../sda
lrwxrwxrwx 1 root root  9 janv. 23 18:04 wwn-0x5000c50091759431 -> ../../sdc
lrwxrwxrwx 1 root root  9 janv. 23 18:04 wwn-0x5001b44e9c83798c -> ../../sdb

Tu me disais :

Les commandes df montrent qu'il y a plein de place de libre, c'est en contradiction avec le début de la trace. Normalement, il devrait  y avoir un message disant manque de place.
On voit que cela traine depuis presque une heure.
Ne ferais-tu pas une commande de copie?

Je ne suis pas certain de comprendre "commande de copie" mais je dirai non, je ne fais rien de spécial...

Merci de ton aide et de tes conseils

#6 Re : -1 »  [RESOLU] Disque systéme qui passe en lecture seule après qques minutes » Le 24/01/2019, à 20:16

Soipacon
Réponses : 22

Bon je vais tacher d'être plus rigoureux dans mes explications !

Pour le disque système sdb (/dev/disk/by-id/ata-SanDisk_SDSSDP128G_152755404172)
C'est un vieux ssd, il ne serait pas vraiment etonnant qu'il soit en fin de vie.
Aucunes données dessus, uniquement le système.

jerome@mint-old:~$ sudo smartctl -s on -a /dev/disk/by-id/ata-SanDisk_SDSSDP128G_152755404172
[sudo] Mot de passe de jerome : 
smartctl 6.6 2016-05-31 r4324 [x86_64-linux-4.15.0-43-generic] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     SanDisk based SSDs
Device Model:     SanDisk SDSSDP128G
Serial Number:    152755404172
LU WWN Device Id: 5 001b44 e9c83798c
Firmware Version: 3.2.0
User Capacity:    126035288064 bytes [126 GB]
Sector Size:      512 bytes logical/physical
Rotation Rate:    Solid State Device
Form Factor:      1.8 inches
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ACS-2 T13/2015-D revision 3
SATA Version is:  SATA 3.0, 6.0 Gb/s (current: 3.0 Gb/s)
Local Time is:    Thu Jan 24 18:58:45 2019 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:      (   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: 			 (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: 	 (  21) minutes.

SMART Attributes Data Structure revision number: 1
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  5 Reallocated_Sector_Ct   0x0002   100   100   000    Old_age   Always       -       0
  9 Power_On_Hours          0x0002   100   100   000    Old_age   Always       -       16499
 12 Power_Cycle_Count       0x0002   100   100   000    Old_age   Always       -       1354
165 Total_Write/Erase_Count 0x0002   100   100   000    Old_age   Always       -       147973
171 Program_Fail_Count      0x0002   100   100   000    Old_age   Always       -       0
172 Erase_Fail_Count        0x0002   100   100   000    Old_age   Always       -       0
173 Avg_Write/Erase_Count   0x0002   100   100   000    Old_age   Always       -       37
174 Unexpect_Power_Loss_Ct  0x0002   100   100   000    Old_age   Always       -       43
187 Reported_Uncorrect      0x0002   100   100   000    Old_age   Always       -       0
194 Temperature_Celsius     0x0022   070   030   000    Old_age   Always       -       30 (Min/Max 4/41)
230 Perc_Write/Erase_Count  0x0002   100   100   000    Old_age   Always       -       123
232 Perc_Avail_Resrvd_Space 0x0003   100   100   005    Pre-fail  Always       -       0
234 Perc_Write/Erase_Ct_BC  0x0002   100   100   000    Old_age   Always       -       477
241 Total_LBAs_Written      0x0002   100   100   000    Old_age   Always       -       10242292584
242 Total_LBAs_Read         0x0002   100   100   000    Old_age   Always       -       15907692273

SMART Error Log Version: 1
No Errors Logged

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Extended offline    Aborted by host               90%     15194         -

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.

Pour le disque sda (/dev/disk/by-id/ata-ST500DM002-1BD142_Z3TDV19P)
C'est un très vieux hdd, je veux bien croire qu'il soit fatigué.
Il contient des données mais rien d'important (tout existe en sauvegarde sur des disques plus récents)

jerome@mint-old:~$ sudo smartctl -s on -o on -a /dev/disk/by-id/ata-ST500DM002-1BD142_Z3TDV19P
[sudo] Mot de passe de jerome : 
smartctl 6.6 2016-05-31 r4324 [x86_64-linux-4.15.0-43-generic] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Seagate Barracuda 7200.14 (AF)
Device Model:     ST500DM002-1BD142
Serial Number:    Z3TDV19P
LU WWN Device Id: 5 000c50 04fbfd2ac
Firmware Version: KC45
User Capacity:    500107862016 bytes [500 GB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    7200 rpm
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ATA8-ACS T13/1699-D revision 4
SATA Version is:  SATA 3.0, 6.0 Gb/s (current: 3.0 Gb/s)
Local Time is:    Thu Jan 24 19:02:14 2019 CET
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF ENABLE/DISABLE COMMANDS SECTION ===
SMART Enabled.
SMART Automatic Offline Testing Enabled every four hours.

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

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: 		(  592) seconds.
Offline data collection
capabilities: 			 (0x7b) SMART execute Offline immediate.
					Auto Offline data collection on/off support.
					Suspend Offline collection upon new
					command.
					Offline surface scan supported.
					Self-test supported.
					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: 	 (   1) minutes.
Extended self-test routine
recommended polling time: 	 (  78) minutes.
Conveyance self-test routine
recommended polling time: 	 (   2) minutes.
SCT capabilities: 	       (0x303f)	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     0x000f   108   099   006    Pre-fail  Always       -       16845032
  3 Spin_Up_Time            0x0003   100   098   000    Pre-fail  Always       -       0
  4 Start_Stop_Count        0x0032   098   098   020    Old_age   Always       -       2167
  5 Reallocated_Sector_Ct   0x0033   100   100   036    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x000f   084   060   030    Pre-fail  Always       -       4629208399
  9 Power_On_Hours          0x0032   071   071   000    Old_age   Always       -       25504
 10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   098   098   020    Old_age   Always       -       2136
183 Runtime_Bad_Block       0x0032   100   100   000    Old_age   Always       -       0
184 End-to-End_Error        0x0032   100   100   099    Old_age   Always       -       0
187 Reported_Uncorrect      0x0032   100   100   000    Old_age   Always       -       0
188 Command_Timeout         0x0032   100   099   000    Old_age   Always       -       1 1 1
189 High_Fly_Writes         0x003a   100   100   000    Old_age   Always       -       0
190 Airflow_Temperature_Cel 0x0022   068   059   045    Old_age   Always       -       32 (Min/Max 31/35)
194 Temperature_Celsius     0x0022   032   041   000    Old_age   Always       -       32 (0 13 0 0 0)
195 Hardware_ECC_Recovered  0x001a   052   036   000    Old_age   Always       -       16845032
197 Current_Pending_Sector  0x0012   100   100   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0010   100   100   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always       -       0
240 Head_Flying_Hours       0x0000   100   253   000    Old_age   Offline      -       25469h+36m+23.557s
241 Total_LBAs_Written      0x0000   100   253   000    Old_age   Offline      -       158476092
242 Total_LBAs_Read         0x0000   100   253   000    Old_age   Offline      -       4169702485

SMART Error Log Version: 1
No Errors Logged

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.

Pour le disque sdc (/dev/disk/by-id/ata-ST3000DM001-1ER166_Z5034SA8)
C'est un hdd bien plus récent qui ne tourne pas très souvent (sauvegardes en tous genre...)
Il contient des données auxquelles je tiens un peu quand même.

jerome@mint-old:~$ sudo smartctl -s on -o on -a /dev/disk/by-id/ata-ST3000DM001-1ER166_Z5034SA8
smartctl 6.6 2016-05-31 r4324 [x86_64-linux-4.15.0-43-generic] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Seagate Barracuda 7200.14 (AF)
Device Model:     ST3000DM001-1ER166
Serial Number:    Z5034SA8
LU WWN Device Id: 5 000c50 091759431
Firmware Version: CC26
User Capacity:    3000592982016 bytes [3,00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    7200 rpm
Form Factor:      3.5 inches
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ACS-2, ACS-3 T13/2161-D revision 3b
SATA Version is:  SATA 3.1, 6.0 Gb/s (current: 3.0 Gb/s)
Local Time is:    Thu Jan 24 19:06:24 2019 CET
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF ENABLE/DISABLE COMMANDS SECTION ===
SMART Enabled.
SMART Automatic Offline Testing Enabled every four hours.

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

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: 		(   89) seconds.
Offline data collection
capabilities: 			 (0x7b) SMART execute Offline immediate.
					Auto Offline data collection on/off support.
					Suspend Offline collection upon new
					command.
					Offline surface scan supported.
					Self-test supported.
					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: 	 (   1) minutes.
Extended self-test routine
recommended polling time: 	 ( 314) minutes.
Conveyance self-test routine
recommended polling time: 	 (   2) minutes.
SCT capabilities: 	       (0x1085)	SCT Status 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     0x000f   118   099   006    Pre-fail  Always       -       197650472
  3 Spin_Up_Time            0x0003   095   094   000    Pre-fail  Always       -       0
  4 Start_Stop_Count        0x0032   100   100   020    Old_age   Always       -       171
  5 Reallocated_Sector_Ct   0x0033   100   100   010    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x000f   064   060   030    Pre-fail  Always       -       2772292
  9 Power_On_Hours          0x0032   095   095   000    Old_age   Always       -       4957
 10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   020    Old_age   Always       -       82
183 Runtime_Bad_Block       0x0032   100   100   000    Old_age   Always       -       0
184 End-to-End_Error        0x0032   100   100   099    Old_age   Always       -       0
187 Reported_Uncorrect      0x0032   100   100   000    Old_age   Always       -       0
188 Command_Timeout         0x0032   100   100   000    Old_age   Always       -       1 2 2
189 High_Fly_Writes         0x003a   100   100   000    Old_age   Always       -       0
190 Airflow_Temperature_Cel 0x0022   067   052   045    Old_age   Always       -       33 (Min/Max 32/35)
191 G-Sense_Error_Rate      0x0032   100   100   000    Old_age   Always       -       0
192 Power-Off_Retract_Count 0x0032   100   100   000    Old_age   Always       -       13
193 Load_Cycle_Count        0x0032   100   100   000    Old_age   Always       -       1245
194 Temperature_Celsius     0x0022   033   048   000    Old_age   Always       -       33 (0 14 0 0 0)
197 Current_Pending_Sector  0x0012   100   100   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0010   100   100   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always       -       0
240 Head_Flying_Hours       0x0000   100   253   000    Old_age   Offline      -       815h+34m+30.006s
241 Total_LBAs_Written      0x0000   100   253   000    Old_age   Offline      -       3968937288
242 Total_LBAs_Read         0x0000   100   253   000    Old_age   Offline      -       1863601340

SMART Error Log Version: 1
No Errors Logged

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.

Donc si les deux premiers doivent mourir, je ne serai pas vraiment surpris, ni vraiment embêté.

Donc je pense que je vais tenter un e2fsck, (à moins que quelqu'un ait une meilleure solution) et si ça casse tout ... ben tant pis pour moi !

Pour info je n'ai pas les moyens d'avoir uniquement du matos neuf donc je fais avec les moyens du bord, en restant conscient des risques...

Encore un grand Merci pour tous vos conseils et infos ( je ne connaissais même pas la notion de "désignation immuable") , je me coucherai moins bête ce soir.

#7 Re : -1 »  [RESOLU] Disque systéme qui passe en lecture seule après qques minutes » Le 24/01/2019, à 22:18

Soipacon
Réponses : 22

J'ai donc tenté ceci depuis une session live "mint 19" :

sudo umount -v /dev/sdb1
 sudo e2fsck -D /dev/sdb1

Et ça m'a donné ça : 

mint@mint:~$ sudo su
root@mint:/home/mint# umount -v /dev/sdb1
umount: /dev/sdb1: not mounted.
root@mint:/home/mint# e2fsck -D /dev/sdb1
e2fsck 1.44.1 (24-Mar-2018)
/dev/sdb1 contains a file system with errors, check forced.
Pass 1: Checking inodes, blocks, and sizes
Deleted inode 1180386 has zero dtime.  Fix<y>? yes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 3A: Optimizing directories
Inode 396703 extent tree (at level 1) could be shorter.  Fix<y>? yes
Inode 523434 extent tree (at level 1) could be shorter.  Fix<y>? yes
Inode 808496 extent tree (at level 1) could be shorter.  Fix<y>? yes
Inode 938097 extent tree (at level 1) could be shorter.  Fix<y>? yes
Inode 1048403 extent tree (at level 1) could be shorter.  Fix<y>? yes
Inode 1076046 extent tree (at level 1) could be shorter.  Fix<y>? yes
Inode 1193943 extent tree (at level 1) could be shorter.  Fix<y>? yes
Inode 1353809 extent tree (at level 1) could be shorter.  Fix<y>? yes
Inode 1581823 extent tree (at level 1) could be shorter.  Fix ('a' enables 'yes' to all) <y>? yes
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Inode bitmap differences:  -1180386
Fix ('a' enables 'yes' to all) <y>? yes
Free inodes count wrong for group #144 (10, counted=11).
Fix ('a' enables 'yes' to all) <y>? yes
Free inodes count wrong (1397925, counted=1397926).
Fix ('a' enables 'yes' to all) <y>? yes

/dev/sdb1: ***** FILE SYSTEM WAS MODIFIED *****
/dev/sdb1: 433498/1831424 files (0.1% non-contiguous), 3300516/7323904 blocks

Pour le sda1 ça m'a retourné que la partition est clean.

#8 Re : -1 »  [RESOLU] Disque systéme qui passe en lecture seule après qques minutes » Le 24/01/2019, à 23:25

Soipacon
Réponses : 22

Et le problème semble être toujours là...

dmesg | tail -200

me donne : 

[  925.484911] EXT4-fs warning (device sdb1): ext4_dirent_csum_verify:353: inode #1454620: comm rsync: No space for directory leaf checksum. Please run e2fsck -D.
[  925.484919] EXT4-fs error (device sdb1): htree_dirblock_to_tree:977: inode #1454620: comm rsync: Directory block failed checksum
[  925.488511] Aborting journal on device sdb1-8.
[  925.490556] EXT4-fs (sdb1): Remounting filesystem read-only
[  925.491932] EXT4-fs error (device sdb1): ext4_journal_check_start:61: Detected aborted journal
[ 1796.267102] systemd-journald[373]: Failed to write entry (21 items, 603 bytes), ignoring: Read-only file system
[ 1796.267320] systemd-journald[373]: Failed to write entry (21 items, 694 bytes), ignoring: Read-only file system
[ 1796.267384] systemd-journald[373]: Failed to write entry (21 items, 603 bytes), ignoring: Read-only file system

Par contre rien concernant sda1 ...

#9 Re : -1 »  [RESOLU] Disque systéme qui passe en lecture seule après qques minutes » Le 25/01/2019, à 15:03

Soipacon
Réponses : 22

Bonjour,

jerome@mint-old:~$ cat /etc/fstab | grep ext4
UUID=641267e8-55a2-4a11-9c65-0d1d409d97f0 /               ext4    errors=remount-ro 0       1
UUID=5f7aac64-94ba-4466-9ab0-2113f3dd2976 /home           ext4    defaults        0       2
UUID=6336578c-3f11-4c82-ba75-9004bfcda023 /media/jerome/donnees_old_mint ext4    defaults        0       2

et  

jerome@mint-old:~$ cat /etc/lsb-release
DISTRIB_ID=LinuxMint
DISTRIB_RELEASE=19
DISTRIB_CODENAME=tara
DISTRIB_DESCRIPTION="Linux Mint 19 Tara"

Je crois effectivement que je vais réinstaller en conservant mon /home

Je reviendrai poster ici ce WE pour dire si le problème a été résolu, si un jour ça peut aider quelqu'un...

En tous cas merci pour ton aide et pour le temps que tu m'as consacré, j'aurai appris pas mal de choses au passage et je serai plus prudent avec windows à l'avenir !

#10 Re : -1 »  [RESOLU] Disque systéme qui passe en lecture seule après qques minutes » Le 02/02/2019, à 10:50

Soipacon
Réponses : 22

Bon et bien après réinstallation le problème est toujours présent, j'en conclu donc que mon SSD est HS.

Le problème est donc résolu, ou en tous cas identifié.

Merci

#11 -1 »  [RESOLU] Virtualbox : USB ne marche qu'en root » Le 30/01/2008, à 18:31

Soipacon
Réponses : 2

Bonjour à  tous,

Comme l'indique mon titre, je ne parviens a utiliser mes périphériques usb qu'en lançant VirtualBox en root.

Si je le lance normalement avec mon user à  moi, les périphériques usb sont détectés, je peux leur associer des filtres, mais quand je lance la machine virtuelle, dans "périphériques usb", ils apparaissent grisés sans auncun moyen de les activer ou désactiver.
Je précise que j'ai bien activer l'usb avant le premier lancement de la machine (au cas ou...) et que mon user fait bien parti du groupe vboxuser.
J'utilise Virtualbox 1.5.4 (pas la version ose)
Jespère avoir été clair dans mon explication.

Pour la prise en charge de l'usb, j'ai suivi la doc d'ubuntu-fr

Merci si vous avez des idées.

Jérà´me

#12 Re : -1 »  [RESOLU] Virtualbox : USB ne marche qu'en root » Le 30/01/2008, à 21:22

Soipacon
Réponses : 2

Merci pour ta réponse mais j'ai résolu mon problème en repartant calmement à zéro et en refaisant tout calmement... Et ça marche !!
Désolé d'avoir encombré ce très précieux forum pour rien.
Merci à la communauté.

#13 Re : -1 »  Rendre les menus Gnome plus réactifs » Le 02/01/2008, à 23:03

Soipacon
Réponses : 11

L'astuce est intéressante et fonctionne bien chez moi mais quand je lance une application depuis le terminal, il me dit : 

jerome@ubuntu : ~ $ evince
/home/jerome/.gtkrc-2.0:3: error: scanner: unterminated string constant - e.g. `style'

Et puis l'application se lance correctement... mais bon ça fait pas trés propre.

Quelqu'un a une idée ? Parce que pour moi c'est du chinois !
Merci

#14 Re : -1 »  Rendre les menus Gnome plus réactifs » Le 02/01/2008, à 23:05

Soipacon
Réponses : 11
ppmt a écrit :

et la bonne commande a faire c'est:

echo "gtk-menu-popup-delay = 0"| tee -a .gtkrc-2.0

Ah ben oui comme ça c'est tout bon ! J'avoue avoir été bien bête sur ce coup là  !!:P
Merci à  toi.

#15 Re : -1 »  Changement de disque dur sans réinstaller » Le 27/12/2007, à 14:16

Soipacon
Réponses : 6

Bonjour à  tous,

Je vais faire un petit up de ce sujet car j'ai exactement le même souci :

La procédure décrite semble a ma portée mais je me pose quelques questions :
Je vais changer mon DD de 20Go pour un beaucoup plus gros (320Go sans doutes),
Je vais donc en profiter pour créer des partitions plus grandes et une partition de plus pour des données. (ça allait jusqu'à  hda5 et aprés il y aura un hda6) Pour la restauration j'ai cru comprendre que ça ne devait pas poser de problème (avec partimage), mais comment mon système va t'il voir cela ?

Est-ce qu'à  chaque démarrage il re-vérifie les "références des partitions" ou bien va t'il falloir que je lui indique manuellement les modifications.

Je ne sais pas si ma question est bien claire mais j'espère que vous me comprendrez.

Merci à  tous pour vos lumières.

#16 Re : -1 »  Codage caractère dans le shell » Le 28/12/2007, à 20:00

Soipacon
Réponses : 2

Exactement pareil pareil pour moi.
---> up
Merci à  ceux qui auraient une idée. wink

#17 Re : -1 »  HOW TO : Changer les couleurs par défaut de l'usplash » Le 03/06/2006, à 10:38

Soipacon
Réponses : 51

@phoenix818 :
Si tu regardes bien tu verras que je me suis pas trop creusé... j'ai juste pris une photo de mon écran pendant le démarrage. tongue
Mais il y a sans doutes des méthodes plus élégantes.

@misteraph :
Essai de mettre une option vga dans ton fichier /boot/grub/menu.lst comme ça par exemple :

title		Ubuntu, kernel 2.6.15-23-k7
root		(hd0,1)
kernel		/boot/vmlinuz-2.6.15-23-k7 root=/dev/hda2 ro vga=771 quiet splash
initrd		/boot/initrd.img-2.6.15-23-k7
savedefault
boot

Chez moi la résolution par défaut ne passe pas et j'ai juste un écran noir aussi.

#18 Re : -1 »  HOW TO : Changer les couleurs par défaut de l'usplash » Le 20/06/2006, à 20:49

Soipacon
Réponses : 51

Essais toi aussi de mettre une option vga=771 (ou autre) dans ton fichier /boot/grub/menu.lst

#19 Re : -1 »  [Suggestion] Theme unifié » Le 05/06/2006, à 13:07

Soipacon
Réponses : 3

Vas voir par là https://wiki.ubuntu.com/UbuntuWeeklyNewsletter/Issue1 , ils parlent de ça :

Edgy Planning

Planning for the next release of Ubuntu, Edgy, has now begun. We are collecting ideas on the wiki page and will be converting them into specs for the developers summit in Paris later this month. Please add any ideas you have.

https://wiki.ubuntu.com/CommunityEdgyIdeas

Matt Zimmerman, our fearless CTO, has a list of Edgy ideas as well:

https://wiki.ubuntu.com/MattZimmerman/EdgyIdeas

#20 Re : -1 »  l'instable c'est la Edgy Eft.... » Le 03/06/2006, à 18:27

Soipacon
Réponses : 16

Peut-être faudrait il renommer ce forum en 'quand Dapper était instable' ou un truc comme ça, et créer un forum vierge nommé 'unstable (actuellement Edgy Eft)', ça permettrait aux sujet 'actifs' de rester afin de pouvoir être débattus et il y aurait un vrai forum unstable... Mais tant que les dépots d'Edgy Eft ne sont pas disponibles ce n'est pas trop gênant.

#21 Re : -1 »  Xgl, compiz, et charge cpu. » Le 03/06/2006, à 20:45

Soipacon
Réponses : 4

Merci de vous intéresser à mon cas. wink

@NicoA380 : Sans xgl, la commande glxinfo | grep rend me retourne :

direct rendering: Yes
OpenGL renderer string: GeForce 6100/PCI/SSE2/3DNOW!
GL_NVX_conditional_render, GL_SGIS_generate_mipmap, GL_SGIS_texture_lod,

Et le driver est bien nvidia.
J'ai suivi la méthode 2 du wiki.
Par contre quand je dis plein écran, c'est presque pareil si je ne fais que maximiser la fenêtre.

@max63 :
Ok donc pour la video en plein écran ça a l'air comme pour moi, c'est fluide mais ça bouffe !
Par contre, si je déplace une fenêtre rapidement sur le bureau, là je monte bien à 70-80% de cpu ... avec un sempron 2800+ oc à 2200MHz
PS : Je viens de me rendre compte que sans xgl, Xorg me prend pas mal de cpu lui aussi si je déplace une fenêtre rapidement...

Je pense que ça vient de ma carte graphique intégrée dont les performances sont sans doutes bien inférieures à celles d'une cg agp ou pcie, mais j'aimerai bien qu'un spécialiste du hardware me confirme ça.


En tous cas merci pour vos réponses

#22 Re : -1 »  Mises à jours automatiques : A la Windows ? » Le 31/05/2006, à 09:08

Soipacon
Réponses : 25

@ Haddock
Ca a changé de nom, maintenant ça s'appelle 'gestionnaire de canaux logiciels'

#23 Re : -1 »  Mises à jours automatiques : A la Windows ? » Le 31/05/2006, à 10:01

Soipacon
Réponses : 25

L'icône n'apparait que lorsque des mises à jour sont disponibles au moment ou l'update notifier le vérifie (une fois par jour par défaut je crois)
Si vraiment elle n'apparait pas, as tu une zone de notification dans ton tableau de bord ?

#24 Re : -1 »  comment passer sous dapper ? » Le 31/05/2006, à 10:51

Soipacon
Réponses : 21

Normalement quand Dapper sera en version stable, un simple 

gksudo update-manager

devrait suffire, et tu devras avoir l'option genre 'une version plus récente de votre systeme d'exploitation est disponible, voulez vous mettre à jour ?'.
Tu n'as plus qu'a choisir cette option.
Le -d c'est si tu veux le faire avant...

Pages : 1 2 3 … 6