Peut-on réparer un système LVM?

Bonjour,

Sur le système LVM d’un disque externe, utilisé pour sauvegarder mes données avec un script rsync, je m’aperçois du message suivant:

mkdir: impossible de créer le répertoire « /mnt/seagateUSB4T_bkp/2026-02-14_21h-18m/work/eric »: Système de fichiers accessible en lecture seulement

Ce système fonctionnait bien depuis longtemps

Dans un 1er temps, en explorant tous les niveaux de l’arborescence, je ne trouve pas l’explication:

ll /mnt/seagateUSB4T_bkp/2026-02-17_09h-44m/
total 8
drwxr-xr-x 5 eric eric 4096 17 févr. 09:44 eric
drwxr-xr-x 3 eric eric 4096 17 févr. 09:44 work

Après enquête, je démonte le disque, désactive le VG, puis réactive le VG et remonte le disque.

dmesg renvoie de nombreuses erreurs:

948276.823321] Buffer I/O error on device dm-7, logical block 226754052
[948276.823325] Buffer I/O error on device dm-7, logical block 226754053
[948276.823326] Buffer I/O error on device dm-7, logical block 226754054
[948276.823327] Buffer I/O error on device dm-7, logical block 226754055
[948276.823327] Buffer I/O error on device dm-7, logical block 226754056
[948276.823328] Buffer I/O error on device dm-7, logical block 226754057
[948276.823329] Buffer I/O error on device dm-7, logical block 226754058
[948276.823329] Buffer I/O error on device dm-7, logical block 226754059
[948276.823330] Buffer I/O error on device dm-7, logical block 226754060
[948276.829720] EXT4-fs warning (device dm-7): ext4_end_bio:343: I/O error 10 writing to inode 161219528 starting block 226606634)
[948276.829724] Buffer I/O error on device dm-7, logical block 226606634
[948276.829781] EXT4-fs warning (device dm-7): ext4_end_bio:343: I/O error 10 writing to inode 161219529 starting block 226606641)
[948276.974357] EXT4-fs error (device dm-7): ext4_read_inode_bitmap:201: comm rsync: Cannot read inode bitmap - block_group = 19729, inode_bitmap = 646447121
[948276.977064] EXT4-fs warning (device dm-7): ext4_end_bio:343: I/O error 10 writing to inode 161628161 starting block 226754061)
[948276.977120] EXT4-fs warning (device dm-7): ext4_end_bio:343: I/O error 10 writing to inode 161628162 starting block 226754071)
[948276.977213] EXT4-fs warning (device dm-7): ext4_end_bio:343: I/O error 10 writing to inode 183108284 starting block 226754073)
[948277.139533] EXT4-fs warning (device dm-7): ext4_end_bio:343: I/O error 10 writing to inode 161628164 starting block 226606644)
[948277.139569] EXT4-fs warning (device dm-7): ext4_end_bio:343: I/O error 10 writing to inode 161628165 starting block 226606652)
[948277.139619] EXT4-fs warning (device dm-7): ext4_end_bio:343: I/O error 10 writing to inode 161628171 starting block 226606654)
[948279.623593] EXT4-fs warning (device dm-7): ext4_end_bio:343: I/O error 10 writing to inode 168593528 starting block 226754074)
[948281.010925] Aborting journal on device dm-7-8.
[948281.010930] buffer_io_error: 234 callbacks suppressed
[948281.010931] Buffer I/O error on dev dm-7, logical block 275283968, lost sync page write
[948281.010933] JBD2: I/O error when updating journal superblock for dm-7-8.
[948281.011206] EXT4-fs error (device dm-7): ext4_check_bdev_write_error:217: comm kworker/u32:1: Error while async write back metadata
[948281.011214] EXT4-fs error (device dm-7) in ext4_reserve_inode_write:5929: Journal has aborted
[948281.011217] EXT4-fs error (device dm-7): mpage_map_and_submit_extent:2548: inode #182452306: comm kworker/u32:1: mark_inode_dirty error
[948281.011220] EXT4-fs error (device dm-7): mpage_map_and_submit_extent:2550: comm kworker/u32:1: Failed to mark inode 182452306 dirty
[948281.011224] EXT4-fs error (device dm-7) in ext4_writepages:2868: Journal has aborted
[948281.011237] Buffer I/O error on dev dm-7, logical block 0, lost sync page write
[948281.011239] EXT4-fs (dm-7): I/O error while writing superblock
[948281.011244] EXT4-fs error (device dm-7): ext4_journal_check_start:83: comm kworker/u32:1: Detected aborted journal
[948281.011250] Buffer I/O error on dev dm-7, logical block 0, lost sync page write
[948281.011252] EXT4-fs (dm-7): I/O error while writing superblock
[948281.011253] EXT4-fs (dm-7): Remounting filesystem read-only
[948281.067449] EXT4-fs error (device dm-7): ext4_journal_check_start:83: comm rsync: Detected aborted journal
[948281.067461] Buffer I/O error on dev dm-7, logical block 0, lost sync page write
[948281.067463] EXT4-fs (dm-7): I/O error while writing superblock
[948281.067464] EXT4-fs (dm-7): Remounting filesystem read-only
[948281.067469] EXT4-fs error (device dm-7): ext4_journal_check_start:83: comm rsync: Detected aborted journal
[948281.067471] Buffer I/O error on dev dm-7, logical block 0, lost sync page write
[948281.067472] EXT4-fs (dm-7): I/O error while writing superblock
[948281.067473] EXT4-fs (dm-7): Remounting filesystem read-only
[948281.067476] EXT4-fs error (device dm-7): ext4_journal_check_start:83: comm rsync: Detected aborted journal
[948281.067478] Buffer I/O error on dev dm-7, logical block 0, lost sync page write
[948281.067478] EXT4-fs (dm-7): I/O error while writing superblock
[948281.067479] EXT4-fs (dm-7): Remounting filesystem read-only
[948281.067482] EXT4-fs error (device dm-7): ext4_journal_check_start:83: comm rsync: Detected aborted journal
[948281.067483] Buffer I/O error on dev dm-7, logical block 0, lost sync page write
[948281.067484] EXT4-fs (dm-7): I/O error while writing superblock
[948281.067487] Buffer I/O error on dev dm-7, logical block 0, lost sync page write
[948281.091812] Buffer I/O error on dev dm-7, logical block 0, lost sync page write
[948281.112846] Buffer I/O error on dev dm-7, logical block 0, lost sync page write
[948350.796285] EXT4-fs error: 1504 callbacks suppressed
[948350.796291] EXT4-fs error (device dm-7): ext4_journal_check_start:83: comm ls: Detected aborted journal
[948350.796320] buffer_io_error: 1501 callbacks suppressed
[948350.796321] Buffer I/O error on dev dm-7, logical block 0, lost sync page write
[948350.796327] EXT4-fs: 3007 callbacks suppressed
[948350.796328] EXT4-fs (dm-7): I/O error while writing superblock
[948350.796330] EXT4-fs (dm-7): Remounting filesystem read-only
[948350.796533] EXT4-fs error (device dm-7): ext4_get_inode_loc:4650: inode #92012545: block 368050208: comm ls: unable to read itable block
[948350.796559] Buffer I/O error on dev dm-7, logical block 0, lost sync page write
[948350.796562] EXT4-fs (dm-7): I/O error while writing superblock
[948423.854219] EXT4-fs error (device dm-7): ext4_journal_check_start:83: comm ls: Detected aborted journal
[948423.854259] Buffer I/O error on dev dm-7, logical block 0, lost sync page write
[948423.854265] EXT4-fs (dm-7): I/O error while writing superblock
[948423.854268] EXT4-fs (dm-7): Remounting filesystem read-only
[948435.373535] EXT4-fs error (device dm-7): ext4_get_inode_loc:4650: inode #92012545: block 368050208: comm ls: unable to read itable block
[948435.373573] Buffer I/O error on dev dm-7, logical block 0, lost sync page write
[948435.373578] EXT4-fs (dm-7): I/O error while writing superblock
[948485.114023] EXT4-fs error (device dm-7): ext4_journal_check_start:83: comm ls: Detected aborted journal
[948485.114059] Buffer I/O error on dev dm-7, logical block 0, lost sync page write
[948485.114064] EXT4-fs (dm-7): I/O error while writing superblock
[948485.114067] EXT4-fs (dm-7): Remounting filesystem read-only
[948514.331180] EXT4-fs error (device dm-7): ext4_journal_check_start:83: comm mkdir: Detected aborted journal
[948514.331222] Buffer I/O error on dev dm-7, logical block 0, lost sync page write
[948514.331230] EXT4-fs (dm-7): I/O error while writing superblock
[948514.331234] EXT4-fs (dm-7): Remounting filesystem read-only
[948514.331237] EXT4-fs error (device dm-7) in __ext4_new_inode:1088: Journal has aborted
[948514.331272] Buffer I/O error on dev dm-7, logical block 0, lost sync page write
[948514.331275] EXT4-fs (dm-7): I/O error while writing superblock
[948599.757786] EXT4-fs error (device dm-7): ext4_journal_check_start:83: comm bash: Detected aborted journal
[948599.757814] Buffer I/O error on dev dm-7, logical block 0, lost sync page write
[948599.757819] EXT4-fs (dm-7): I/O error while writing superblock
[948599.757821] EXT4-fs (dm-7): Remounting filesystem read-only
[948601.600466] EXT4-fs error (device dm-7): ext4_journal_check_start:83: comm bash: Detected aborted journal
[948601.600499] Buffer I/O error on dev dm-7, logical block 0, lost sync page write
[948601.600504] EXT4-fs (dm-7): I/O error while writing superblock
[948601.600507] EXT4-fs (dm-7): Remounting filesystem read-only
[948638.667782] EXT4-fs error (device dm-7): ext4_journal_check_start:83: comm mkdir: Detected aborted journal
[948638.667797] Buffer I/O error on dev dm-7, logical block 0, lost sync page write
[948638.667799] EXT4-fs (dm-7): I/O error while writing superblock
[948638.667800] EXT4-fs (dm-7): Remounting filesystem read-only
[948638.667801] EXT4-fs error (device dm-7) in __ext4_new_inode:1088: Journal has aborted
[948638.667811] Buffer I/O error on dev dm-7, logical block 0, lost sync page write
[948638.667812] EXT4-fs (dm-7): I/O error while writing superblock
[948951.931782] EXT4-fs error (device dm-7): ext4_get_inode_loc:4650: inode #92012545: block 368050208: comm ls: unable to read itable block
[948951.931811] Buffer I/O error on dev dm-7, logical block 0, lost sync page write
[948951.931815] EXT4-fs (dm-7): I/O error while writing superblock
[948966.678196] EXT4-fs warning: 12 callbacks suppressed
[948966.678202] EXT4-fs warning (device dm-7): htree_dirblock_to_tree:1083: inode #193986561: lblock 0: comm ls: error -5 reading directory block
[948966.678214] EXT4-fs error (device dm-7): ext4_journal_check_start:83: comm ls: Detected aborted journal
[948966.678231] Buffer I/O error on dev dm-7, logical block 0, lost sync page write
[948966.678235] EXT4-fs (dm-7): I/O error while writing superblock
[948966.678238] EXT4-fs (dm-7): Remounting filesystem read-only
[949005.436112] EXT4-fs error (device dm-7): ext4_get_inode_loc:4650: inode #92012545: block 368050208: comm ls: unable to read itable block
[949005.436148] Buffer I/O error on dev dm-7, logical block 0, lost sync page write
[949005.436153] EXT4-fs (dm-7): I/O error while writing superblock
[949021.183444] EXT4-fs error (device dm-7): ext4_get_inode_loc:4650: inode #92012545: block 368050208: comm ls: unable to read itable block
[949021.183484] Buffer I/O error on dev dm-7, logical block 0, lost sync page write
[949021.183488] EXT4-fs (dm-7): I/O error while writing superblock
[949021.183820] EXT4-fs warning (device dm-7): htree_dirblock_to_tree:1083: inode #92012545: lblock 0: comm ls: error -5 reading directory block
[949021.183828] EXT4-fs error (device dm-7): ext4_journal_check_start:83: comm ls: Detected aborted journal
[949021.183869] Buffer I/O error on dev dm-7, logical block 0, lost sync page write
[949021.183873] EXT4-fs (dm-7): I/O error while writing superblock
[949021.183876] EXT4-fs (dm-7): Remounting filesystem read-only
[949042.615350] EXT4-fs warning (device dm-7): htree_dirblock_to_tree:1083: inode #193986561: lblock 0: comm bash: error -5 reading directory block
[949044.016428] EXT4-fs warning (device dm-7): htree_dirblock_to_tree:1083: inode #193986561: lblock 0: comm bash: error -5 reading directory block
[949044.280653] EXT4-fs warning (device dm-7): htree_dirblock_to_tree:1083: inode #193986561: lblock 0: comm bash: error -5 reading directory block
[949045.788338] EXT4-fs warning (device dm-7): htree_dirblock_to_tree:1083: inode #193986561: lblock 0: comm ls: error -5 reading directory block
[949064.400819] EXT4-fs error (device dm-7): ext4_journal_check_start:83: comm ls: Detected aborted journal
[949064.400855] Buffer I/O error on dev dm-7, logical block 0, lost sync page write
[949064.400860] EXT4-fs (dm-7): I/O error while writing superblock
[949064.400863] EXT4-fs (dm-7): Remounting filesystem read-only
[949066.467318] EXT4-fs error (device dm-7): ext4_journal_check_start:83: comm ls: Detected aborted journal
[949066.467347] Buffer I/O error on dev dm-7, logical block 0, lost sync page write
[949066.467352] EXT4-fs (dm-7): I/O error while writing superblock
[949066.467354] EXT4-fs (dm-7): Remounting filesystem read-only
[949068.554154] EXT4-fs error (device dm-7): ext4_journal_check_start:83: comm ls: Detected aborted journal
[949068.554189] Buffer I/O error on dev dm-7, logical block 0, lost sync page write
[949068.554195] EXT4-fs (dm-7): I/O error while writing superblock
[949068.554198] EXT4-fs (dm-7): Remounting filesystem read-only
[949070.928336] EXT4-fs error (device dm-7): ext4_journal_check_start:83: comm ls: Detected aborted journal
[949070.928368] Buffer I/O error on dev dm-7, logical block 0, lost sync page write
[949070.928374] EXT4-fs (dm-7): I/O error while writing superblock
[949070.928376] EXT4-fs (dm-7): Remounting filesystem read-only
[949232.174280] EXT4-fs (dm-7): unmounting filesystem.
[949232.175905] Buffer I/O error on dev dm-7, logical block 0, lost sync page write
[949232.175909] EXT4-fs (dm-7): I/O error while writing superblock
[949235.386604] usb 1-2: USB disconnect, device number 21
[949235.440712] sd 0:0:0:0: [sda] Synchronizing SCSI cache
[949235.684483] sd 0:0:0:0: [sda] Synchronize Cache(10) failed: Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
[949239.844520] usb 1-2: new high-speed USB device number 28 using xhci_hcd
[949240.041392] usb 1-2: New USB device found, idVendor=0bc2, idProduct=231a, bcdDevice= 7.12
[949240.041407] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[949240.041412] usb 1-2: Product: Expansion
[949240.041426] usb 1-2: Manufacturer: Seagate
[949240.041429] usb 1-2: SerialNumber: NAAX94EB
[949240.067380] scsi host0: uas
[949240.078203] scsi 0:0:0:0: Direct-Access     Seagate  Expansion        0712 PQ: 0 ANSI: 6
[949240.081057] scsi 0:0:0:0: Attached scsi generic sg0 type 0
[949245.803896] sd 0:0:0:0: [sda] 7814037167 512-byte logical blocks: (4.00 TB/3.64 TiB)
[949245.803910] sd 0:0:0:0: [sda] 4096-byte physical blocks
[949245.804151] sd 0:0:0:0: [sda] Write Protect is off
[949245.804157] sd 0:0:0:0: [sda] Mode Sense: 53 00 00 08
[949245.804551] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[949245.804804] sd 0:0:0:0: [sda] Preferred minimum I/O size 4096 bytes
[949245.804818] sd 0:0:0:0: [sda] Optimal transfer size 33553920 bytes not a multiple of preferred minimum block size (4096 bytes)
[949245.885692]  sda: sda1
[949245.886236] sd 0:0:0:0: [sda] Attached SCSI disk
[949254.018892] EXT4-fs (dm-7): unable to read superblock
[949305.140088] Buffer I/O error on dev dm-7, logical block 838860784, async page read
[949308.001675]  sda: sda1
[949308.313001]  sda: sda1
[949332.310078] Buffer I/O error on dev dm-7, logical block 838860784, async page read
[949348.611010] Buffer I/O error on dev dm-7, logical block 838860784, async page read
[949348.611094] Buffer I/O error on dev dm-7, logical block 838860784, async page read
[949358.138108] Buffer I/O error on dev dm-7, logical block 838860784, async page read
[949411.509367] Buffer I/O error on dev dm-7, logical block 838860784, async page read
[949413.691194]  sda: sda1
[949414.030881]  sda: sda1
[949454.250666] Buffer I/O error on dev dm-7, logical block 838860784, async page read
[949658.801249] /dev/seagateUSB4T: Can't open blockdev

Évidemment, je pourrais récupérer le disque et supprimer le LVM qui n’a plus lieu d’être, pour repartir sur des bases saines.

Mais outre la perte d’archives importantes, je me sentirais peut-être un peu plus heureux si j’apprenais qu’il existe une solution pour récupérer un système LVM. (si c’est bien le problème…)

Merci de m’a voir lu

PS
quelques informations actuelles sur le système:

sudo vgscan
Found volume group "seagateUSB4T" using metadata type lvm2

sudo df -h | egrep  mapper
(rien)

sudo pvdisplay | egrep 'Physical|Name|PV Size|Allocatable'
--- Physical volume ---
  PV Name               /dev/sda1
  VG Name               seagateUSB4T
  PV Size               <3,64 TiB / not usable 2,00 MiB
  Allocatable           yes 

sudo vgdisplay | egrep "Volume group|VG Name| PE|VG UUID"
 --- Volume group ---
  VG Name               seagateUSB4T
  PE Size               4,00 MiB
  Total PE              953861
  Alloc PE / Size       819200 / 3,12 TiB
  Free  PE / Size       134661 / <526,02 GiB
  VG UUID               7wvg2m-Z3uV-uDZV-YgUH-aYN2-jV94-3kAfik

sudo lvdisplay | egrep "Logical|Name|Path|Size"
--- Logical volume ---
  LV Path                /dev/seagateUSB4T/bkp
  LV Name                bkp
  VG Name                seagateUSB4T
  LV Size                3,12 TiB

Mettre du LVM sur un disque externe de sauvegarde n’est pas très utile. Mieux vaut utiliser tout l’espace et faire des répertoires en fonction de ce que tu y mets.

Initialement, j’avais 2 partitions, c’est pourquoi j’avais installé LVM. Ensuite j’ai réparti les 2 partitions sur 2 disques et gardé une seule partition. Ça a fonctionné des mois, peut-être olus d’un an.

En attendant, s’il y a une petite chance de récupérer mes données, avant de reformater effectivement sans LVM.
J’ai essayé d’explorer avec smartctl, mais impossible, quel que soit le type donné (le test donne sat ou ata, aucun n’est reconnu).

merci

Surprise!
j’ai débranché le disque USB, puis relancé mon script, et (jusqu’ici) tout semble fonctionner comme attendu.

1 J'aime

Y’a plus qu’à notifier que le sujet est résolu :wink:
Si tu ne sais pas comment faire, merci de lire les règles d’usage.