SSD se démonte et remonte en lecture seule / Rsync

[hubert]

J’ai un PC portable (Thinkpad P53) sur lequel j’ai installé Mint 21 sur un SSD M.2
Et ai ajouté en interne un SSD SATA-III (de 4 To), pour en faire mon "disque Datas" ; Il s’agit d’un disque neuf que j’ai formaté en ext4.

Afin de copier mes données, depuis un disque externe (USB), sur mon disque Datas j’utilise Grsync.
Scénario problématique : La copie se lance, de nombreux dossiers et fichiers sont copiés et puis… paf en cours de route toutes les copies passent en échec : je n’ai plus les droits d’écriture sur le disque ! Mon disque s'est démonté et a remonté aussitôt mais en lecture seule (pendant la copie) !
Seul moyen de le remettre en rw : reboot du PC.
J’ai cherché sur différents forums mais je ne trouve pas de solution. J’ai essayé avec différentes options de "mount" (dans l'utilitaire Disques).
Je sèche et suis preneur d’idées…

[hubert]

Voilà ce qu'il y a (extrait) en sortie de "sudo dmesg" lors du crash...

Code : Tout sélectionner

[  200.292573] ata3.00: exception Emask 0x0 SAct 0x400000 SErr 0x0 action 0x6 frozen
[  200.292597] ata3.00: failed command: WRITE FPDMA QUEUED
[  200.292603] ata3.00: cmd 61/c0:b0:40:fe:80/02:00:d5:00:00/40 tag 22 ncq dma 360448 out
                        res 40/00:ff:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[  200.292627] ata3.00: status: { DRDY }
[  200.292638] ata3: hard resetting link
[  205.652764] ata3: link is slow to respond, please be patient (ready=0)
[  210.332796] ata3: COMRESET failed (errno=-16)
[  210.332819] ata3: hard resetting link
[  215.688558] ata3: link is slow to respond, please be patient (ready=0)
[  220.368846] ata3: COMRESET failed (errno=-16)
[  220.368868] ata3: hard resetting link
[  225.720874] ata3: link is slow to respond, please be patient (ready=0)
[  255.424975] ata3: COMRESET failed (errno=-16)
[  255.424997] ata3: limiting SATA link speed to 3.0 Gbps
[  255.425002] ata3: hard resetting link
[  260.476985] ata3: COMRESET failed (errno=-16)
[  260.477009] ata3: reset failed, giving up
[  260.477016] ata3.00: disabled
[  260.477051] ata3: EH complete
[  260.477099] sd 2:0:0:0: [sda] tag#10 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=89s
[  260.477110] sd 2:0:0:0: [sda] tag#10 CDB: ATA command pass through(16) 85 06 20 00 00 00 00 00 00 00 00 00 00 00 e5 00
[  260.477139] sd 2:0:0:0: [sda] tag#11 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=90s
[  260.477149] sd 2:0:0:0: [sda] tag#11 CDB: Write(16) 8a 00 00 00 00 00 d5 80 fe 40 00 00 02 c0 00 00
[  260.477154] blk_update_request: I/O error, dev sda, sector 3582000704 op 0x1:(WRITE) flags 0x800 phys_seg 88 prio class 0
[  260.477408] sd 2:0:0:0: [sda] tag#23 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
[  260.477421] sd 2:0:0:0: [sda] tag#23 CDB: Synchronize Cache(10) 35 00 00 00 00 00 00 00 00 00
[  260.477429] blk_update_request: I/O error, dev sda, sector 3905159320 op 0x1:(WRITE) flags 0x800 phys_seg 1 prio class 0
[  260.477458] Aborting journal on device sda-8.
[  260.477506] sd 2:0:0:0: [sda] tag#24 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
[  260.477519] sd 2:0:0:0: [sda] tag#24 CDB: Write(16) 8a 00 00 00 00 00 e8 c4 00 00 00 00 00 08 00 00
[  260.477526] blk_update_request: I/O error, dev sda, sector 3905159168 op 0x1:(WRITE) flags 0x800 phys_seg 1 prio class 0
[  260.477543] blk_update_request: I/O error, dev sda, sector 3905159168 op 0x1:(WRITE) flags 0x800 phys_seg 1 prio class 0
[  260.477556] Buffer I/O error on dev sda, logical block 488144896, lost sync page write
[  260.477579] JBD2: Error -5 detected when updating journal superblock for sda-8.
[  260.477880] sd 2:0:0:0: [sda] tag#21 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
[  260.477899] sd 2:0:0:0: [sda] tag#21 CDB: Read(16) 88 00 00 00 00 00 43 01 01 80 00 00 00 08 00 00
[  260.477906] blk_update_request: I/O error, dev sda, sector 1124139392 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0
[  260.477944] EXT4-fs error (device sda): __ext4_find_entry:1682: inode #35127313: comm rsync: reading directory lblock 0
[  260.478030] sd 2:0:0:0: [sda] tag#22 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
[  260.478042] sd 2:0:0:0: [sda] tag#22 CDB: Write(16) 8a 00 00 00 00 00 00 00 00 00 00 00 00 08 00 00
[  260.478048] blk_update_request: I/O error, dev sda, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 1 prio class 0
[  260.478067] blk_update_request: I/O error, dev sda, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 1 prio class 0
[  260.478081] Buffer I/O error on dev sda, logical block 0, lost sync page write
[  260.478125] EXT4-fs (sda): I/O error while writing superblock
[  260.478135] EXT4-fs (sda): Remounting filesystem read-only
[  260.478343] sd 2:0:0:0: [sda] tag#0 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
[  260.478352] sd 2:0:0:0: [sda] tag#0 CDB: Read(16) 88 00 00 00 00 00 43 01 01 80 00 00 00 08 00 00
[  260.478356] blk_update_request: I/O error, dev sda, sector 1124139392 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0
[  260.478376] EXT4-fs error (device sda): __ext4_find_entry:1682: inode #35127313: comm rsync: reading directory lblock 0

[hubert]

Pas de miracle c'est mon disque qui était défectueux...