# Timeshift: disque USB en boucle **URL:** \ **Category:** Support Debian\ **Created:** [Juillet 3, 2025, 2:13 UTC](https://www.debian-fr.org/t/timeshift-disque-usb-en-boucle/91309 "2025-07-03T14:13:02Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![josephtux](https://www.debian-fr.org/user_avatar/www.debian-fr.org/josephtux/32/3985_2.png) [@josephtux](https://www.debian-fr.org/u/josephtux)\ **Post date:** [Juillet 3, 2025, 2:13 UTC](https://www.debian-fr.org/t/timeshift-disque-usb-en-boucle/91309/1 "2025-07-03T14:13:03Z")
Bonjour, (oui déjà de retour 😉) peut-être à l’origine des récents problèmes? Après une restauration par _timeshift_ qui semble s’être bien passée, j’ai reconfiguré le plan et les filtres de _timeshift_, une première sauvegarde a été rapisement réalisée. Le problème: depuis ce matin, _le disque du timeshift_ ne cesse de clignoter (et de chauffer), n’écrit rien, apparemment n’efface rien et notamment pas le répertoire que `ps` indique: ``` $ps auxw | egrep timeshift root 96647 51.7 0.1 407732 110520 ? Ssl 15:00 33:18 timeshift --check --scripted root 96706 0.8 0.0 3524 1544 ? D 15:00 0:33 rm -rfv /run/timeshift/96647/backup/timeshift/snapshots/2025-06-26_21-00-09/ ``` Je suppose que `timeshift` rencontre un obstacle et tente vainement la commande `rm` indiquée, car `timeshift/snapshots/2025-06-26_21-00-09/` est toujours présent et «bien rempli». Mais je ne vois rien d’anormal dans les droits de ce répertoire et de ses premiers niveaux de sous-répertoires. _top_ place timeshift en 1er, avec 85 à 100% de CPU! `# kill 96706` a stoppé les 2 processus ---
**Author:** ![fran.b](https://www.debian-fr.org/letter_avatar_proxy/v4/letter/f/d78d45/32.png) [@fran.b](https://www.debian-fr.org/u/fran.b)\ **Post date:** [Juillet 4, 2025, 6:56 UTC](https://www.debian-fr.org/t/timeshift-disque-usb-en-boucle/91309/2 "2025-07-04T06:56:30Z")
> [@josephtux](#): > > `/timeshi` As tu regardé le contenu des logs (/varlog/syslog ou journalctl -xu, j’ignore si timeshift en a un propre)? As tu essayé d’effacer toi même le repertoire? ---
**Author:** ![josephtux](https://www.debian-fr.org/user_avatar/www.debian-fr.org/josephtux/32/3985_2.png) [@josephtux](https://www.debian-fr.org/u/josephtux)\ **Post date:** [Juillet 4, 2025, 9:32 UTC](https://www.debian-fr.org/t/timeshift-disque-usb-en-boucle/91309/3 "2025-07-04T09:32:13Z")
Bonjour, Après avoir tué les processus _timeshift_, le disque éteint: Je lance _timeshift-gui_ via le menu _Mate_. La fenêtre s’ouvre normalement, je lance la commande _créer_. Et la fenêtre se ferme, sans lancer la création de sauvegarde. Il y a 2 fichiers de log (à cette heure) dans `/var/log/timeshift/` : 2025-07-04\_11-00-01\_backup.log qui contient ces 2 lignes: ``` # cat !$ cat 2025-07-04_11-00-01_backup.log [11:00:01] Main: check_dependencies() [11:00:01] Another instance of this application is running (PID=191615) ``` et un fichier `2025-07-04_11-09-02_gui.log` très copieusement rempli (201 lignes): ``` cat 2025-07-04_11-00-01_backup.log [11:00:01] Main: check_dependencies() [11:00:01] Another instance of this application is running (PID=191615) root@Leopard:/var/log/timeshift# cat 2025-07-04_11-09-02_gui.log [11:09:02] Journal de session: /var/log/timeshift/2025-07-04_11-09-02_gui.log [11:09:02] Distribution: debian "12" [11:09:02] DIST_ID: debian [11:09:02] Main: check_dependencies() [11:09:02] [Attention] Lock invalide supprimé [11:09:02] Main: add_default_exclude_entries() [11:09:02] Main: add_default_exclude_entries(): exit [11:09:02] update_partitions() [11:09:02] Device: get_disk_space_using_df(): 8 [11:09:02] Device: get_mounted_filesystems_using_mtab(): 8 [11:09:02] Device: get_filesystems(): 19 [11:09:02] partition list updated [11:09:02] detect_system_devices() [11:09:02] /boot/efi est mappé au périphérique: /dev/nvme0n1p1, UUID=5FC7-2F70 [11:09:02] / est mappé au périphérique: /dev/dm-0, UUID=adc517ba-a451-4bd5-bdd2-235862aafe35 [11:09:02] Searching subvolume for system at path: / [11:09:02] Users: eric root [11:09:02] Encrypted home users: [11:09:02] Encrypted home dirs: [11:09:02] Encrypted private dirs: [11:09:02] Main: load_app_config() [11:09:02] Configuration chargée: /etc/timeshift/timeshift.json [11:09:02] IconManager: init() [11:09:02] found images directory: /usr/share/timeshift/images [11:09:02] Main(): ok [11:09:02] Main: initialize_repo() [11:09:02] backup_uuid=5ecc1c9a-b5d1-42d6-bd24-9c1ca73c3adf [11:09:02] backup_parent_uuid= [11:09:02] Setting snapshot device from config file [11:09:02] repo: creating from uuid [11:09:02] SnapshotRepo: from_uuid(): RSYNC [11:09:02] uuid=5ecc1c9a-b5d1-42d6-bd24-9c1ca73c3adf [11:09:02] SnapshotRepo: init_from_device() [11:09:02] [11:09:02] SnapshotRepo: unlock_and_mount_devices() [11:09:02] device=/dev/sda1 [11:09:02] SnapshotRepo: unlock_and_mount_device() [11:09:02] device=/dev/sda1 [11:09:02] Device: get_mounted_filesystems_using_mtab(): 8 [11:09:02] ------------------ [11:09:02] arg=5ecc1c9a-b5d1-42d6-bd24-9c1ca73c3adf, device=/dev/sda1 [11:09:02] /run/timeshift/191615/backup [11:09:02] /media/eric/Tosh2Tbleu1ext4 [11:09:02] ------------------ [11:09:02] Device: get_mounted_filesystems_using_mtab(): 8 [11:09:07] Mounted '/dev/sda1' at '/run/timeshift/631747/backup' [11:09:07] SnapshotRepo: load_snapshots() [11:09:07] loading snapshots from '/run/timeshift/631747/backup/timeshift/snapshots': 18 found [11:09:07] SnapshotRepo: unlock_and_mount_device(): exit [11:09:07] Périphérique sélectionné pour les instantanés: /dev/sda1 [11:09:07] Espace disponible: 831,9 GB [11:09:07] SnapshotRepo: check_status() [11:09:07] SnapshotRepo: available() [11:09:07] is_available: ok [11:09:07] SnapshotRepo: has_snapshots() [11:09:07] SnapshotRepo: has_space() - 0 required (0 B) [11:09:07] Device: get_disk_space_using_df(): 1 [11:09:07] Périphérique pour les instantanés: '/dev/sda1' [11:09:07] Emplacement des snapshots: /run/timeshift/631747/backup [11:09:07] Valider [11:09:07] 18 instantanés, 831,9 GB libre [11:09:07] Statut: HAS_SNAPSHOTS_HAS_SPACE [11:09:07] [11:09:07] SnapshotRepo: check_status(): exit [11:09:07] SnapshotRepo: init_from_device(): exit [11:09:07] SnapshotRepo: from_uuid(): exit [11:09:07] Main: initialize_repo(): exit [11:09:07] MainWindow: MainWindow() [11:09:07] SnapshotListBox: SnapshotListBox() [11:09:07] SnapshotListBox: SnapshotListBox(): exit [11:09:07] MainWindow: MainWindow(): exit [11:09:07] MainWindow(): init_delayed() [11:09:07] SnapshotRepo: available() [11:09:07] is_available: ok [11:09:07] SnapshotRepo: available() [11:09:07] is_available: ok [11:09:07] SnapshotRepo: load_snapshots() [11:09:07] loading snapshots from '/run/timeshift/631747/backup/timeshift/snapshots': 18 found [11:09:07] SnapshotRepo: check_status() [11:09:07] SnapshotRepo: available() [11:09:07] is_available: ok [11:09:07] SnapshotRepo: has_snapshots() [11:09:07] SnapshotRepo: has_space() - 0 required (0 B) [11:09:07] Device: get_disk_space_using_df(): 1 [11:09:07] Périphérique pour les instantanés: '/dev/sda1' [11:09:07] Emplacement des snapshots: /run/timeshift/631747/backup [11:09:07] Valider [11:09:07] 18 instantanés, 831,9 GB libre [11:09:07] Statut: HAS_SNAPSHOTS_HAS_SPACE [11:09:07] [11:09:07] SnapshotRepo: check_status(): exit [11:09:07] SnapshotRepo: has_snapshots() [11:09:07] SnapshotRepo: has_snapshots() [11:09:07] MainWindow(): init_delayed(): exit [11:09:13] SnapshotRepo: available() [11:09:13] is_available: ok [11:09:13] BackupWindow: BackupWindow() [11:09:13] EstimateBox: EstimateBox() [11:09:13] EstimateBox: EstimateBox(): exit [11:09:13] BackupDeviceBox: BackupDeviceBox() [11:09:13] BackupDeviceBox: BackupDeviceBox(): exit [11:09:13] BackupBox: BackupBox() [11:09:13] BackupBox: BackupBox(): exit [11:09:13] BackupFinishBox: BackupFinishBox() [11:09:13] BackupFinishBox: BackupFinishBox(): exit [11:09:13] BackupWindow: BackupWindow(): exit [11:09:13] SnapshotRepo: available() [11:09:13] is_available: ok [11:09:13] SnapshotRepo: has_space() - 0 required (0 B) [11:09:13] Device: get_disk_space_using_df(): 1 [11:09:13] [11:09:13] page: 2 [11:09:13] Main: create_snapshot() [11:09:13] SnapshotRepo: has_space() - 0 required (0 B) [11:09:13] Device: get_disk_space_using_df(): 1 [11:09:13] Main: backup_and_rotate() [11:09:13] SnapshotRepo: available() [11:09:13] is_available: ok [11:09:13] ------------------------------------------------------------------------------ [11:09:13] Création d'un nouvel instantané...(RSYNC) [11:09:13] Enregistrement sur le périphérique: /dev/sda1, monté sur le chemin: /run/timeshift/631747/backup [11:09:13] E: Erreur lors de la création du répertoire /run/timeshift/631747/backup/timeshift/snapshots/2025-07-04_11-09-13 : Système de fichiers accessible en lecture seulement [11:09:13] E: Échec lors de la création du dossier: /run/timeshift/631747/backup/timeshift/snapshots/2025-07-04_11-09-13 [11:09:13] E: Erreur lors de la création du répertoire /run/timeshift/631747/backup/timeshift/snapshots/2025-07-04_11-09-13 : Système de fichiers accessible en lecture seulement [11:09:13] E: Échec lors de la création du dossier: /run/timeshift/631747/backup/timeshift/snapshots/2025-07-04_11-09-13/localhost [11:09:13] Lien à partir de l'instantané: 2025-07-03_11-58-11 [11:09:13] Main: save_exclude_list_for_backup() [11:09:13] Main: create_exclude_list_for_backup() [11:09:13] Main: create_exclude_list_for_backup(): exit [11:09:13] E: Erreur lors de la création du répertoire /run/timeshift/631747/backup/timeshift/snapshots/2025-07-04_11-09-13 : Système de fichiers accessible en lecture seulement [11:09:13] E: Échec lors de la création du dossier: /run/timeshift/631747/backup/timeshift/snapshots/2025-07-04_11-09-13 [11:09:13] E: Erreur lors de l’ouverture du fichier « /run/timeshift/631747/backup/timeshift/snapshots/2025-07-04_11-09-13/exclude.list » : Aucun fichier ou dossier de ce type [11:09:13] E: Impossible d'écrire le fichier: /run/timeshift/631747/backup/timeshift/snapshots/2025-07-04_11-09-13/exclude.list [11:09:13] E: Impossible de sauvegarder la liste d'exclusion [11:09:13] Échec lors de la création de l'instantané [11:09:13] ------------------------------------------------------------------------------ [11:09:13] SnapshotRepo: load_snapshots() [11:09:13] loading snapshots from '/run/timeshift/631747/backup/timeshift/snapshots': 18 found [11:09:13] E: rm: impossible de supprimer '/run/timeshift/631747/backup/timeshift/snapshots-boot/2025-06-02_19-00-10': Système de fichiers accessible en lecture seulement rm: impossible de supprimer '/run/timeshift/631747/backup/timeshift/snapshots-boot/2025-03-17_16-38-23': Système de fichiers accessible en lecture seulement rm: impossible de supprimer '/run/timeshift/631747/backup/timeshift/snapshots-boot/2025-04-13_20-00-10': Système de fichiers accessible en lecture seulement rm: impossible de supprimer '/run/timeshift/631747/backup/timeshift/snapshots-boot/2025-04-13_18-49-08': Système de fichiers accessible en lecture seulement rm: impossible de supprimer '/run/timeshift/631747/backup/timeshift/snapshots-boot/2025-04-18_11-18-05': Système de fichiers accessible en lecture seulement [11:09:13] E: Erreur lors de la suppression de liens symboliques: 'snapshots-boot' [11:09:13] E: rm: impossible de supprimer '/run/timeshift/631747/backup/timeshift/snapshots-hourly/': Système de fichiers accessible en lecture seulement [11:09:13] E: Erreur lors de la suppression de liens symboliques: 'snapshots-hourly' [11:09:13] E: rm: impossible de supprimer '/run/timeshift/631747/backup/timeshift/snapshots-daily/2025-06-25_19-00-09': Système de fichiers accessible en lecture seulement rm: impossible de supprimer '/run/timeshift/631747/backup/timeshift/snapshots-daily/2025-06-26_19-00-07': Système de fichiers accessible en lecture seulement rm: impossible de supprimer '/run/timeshift/631747/backup/timeshift/snapshots-daily/2024-04-20_00-05-47': Système de fichiers accessible en lecture seulement [11:09:13] E: Erreur lors de la suppression de liens symboliques: 'snapshots-daily' [11:09:13] E: rm: impossible de supprimer '/run/timeshift/631747/backup/timeshift/snapshots-weekly/2025-06-09_19-00-01': Système de fichiers accessible en lecture seulement rm: impossible de supprimer '/run/timeshift/631747/backup/timeshift/snapshots-weekly/2025-06-23_19-00-01': Système de fichiers accessible en lecture seulement rm: impossible de supprimer '/run/timeshift/631747/backup/timeshift/snapshots-weekly/2025-06-16_19-00-06': Système de fichiers accessible en lecture seulement rm: impossible de supprimer '/run/timeshift/631747/backup/timeshift/snapshots-weekly/2024-04-20_00-05-47': Système de fichiers accessible en lecture seulement [11:09:13] E: Erreur lors de la suppression de liens symboliques: 'snapshots-weekly' [11:09:13] E: rm: impossible de supprimer '/run/timeshift/631747/backup/timeshift/snapshots-monthly/2025-06-02_19-00-10': Système de fichiers accessible en lecture seulement rm: impossible de supprimer '/run/timeshift/631747/backup/timeshift/snapshots-monthly/2024-04-20_00-05-47': Système de fichiers accessible en lecture seulement [11:09:13] E: Erreur lors de la suppression de liens symboliques: 'snapshots-monthly' [11:09:13] E: rm: impossible de supprimer '/run/timeshift/631747/backup/timeshift/snapshots-ondemand/2024-08-25_14-11-41': Système de fichiers accessible en lecture seulement rm: impossible de supprimer '/run/timeshift/631747/backup/timeshift/snapshots-ondemand/2024-12-14_15-57-28': Système de fichiers accessible en lecture seulement rm: impossible de supprimer '/run/timeshift/631747/backup/timeshift/snapshots-ondemand/2024-08-14_16-20-51': Système de fichiers accessible en lecture seulement rm: impossible de supprimer '/run/timeshift/631747/backup/timeshift/snapshots-ondemand/2024-08-29_19-29-59': Système de fichiers accessible en lecture seulement rm: impossible de supprimer '/run/timeshift/631747/backup/timeshift/snapshots-ondemand/2024-12-20_18-49-51': Système de fichiers accessible en lecture seulement rm: impossible de supprimer '/run/timeshift/631747/backup/timeshift/snapshots-ondemand/2025-01-03_12-57-05': Système de fichiers accessible en lecture seulement rm: impossible de supprimer '/run/timeshift/631747/backup/timeshift/snapshots-ondemand/2024-04-17_15-10-29': Système de fichiers accessible en lecture seulement rm: impossible de supprimer '/run/timeshift/631747/backup/timeshift/snapshots-ondemand/2023-11-10_19-19-19': Système de fichiers accessible en lecture seulement rm: impossible de supprimer '/run/timeshift/631747/backup/timeshift/snapshots-ondemand/2024-04-20_00-05-47': Système de fichiers accessible en lecture seulement rm: impossible de supprimer '/run/timeshift/631747/backup/timeshift/snapshots-ondemand/2024-11-10_17-11-42': Système de fichiers accessible en lecture seulement [11:09:13] E: Erreur lors de la suppression de liens symboliques: 'snapshots-ondemand' [11:09:13] E: ln: impossible de créer le lien symbolique '/run/timeshift/631747/backup/timeshift/snapshots-ondemand/2023-11-10_19-19-19': Le fichier existe [11:09:13] E: Erreur lors de la création de liens symboliques: snapshots-ondemand [11:09:13] [11:09:13] page: 3 [11:09:14] SnapshotRepo: available() [11:09:14] is_available: ok [11:09:14] SnapshotRepo: load_snapshots() [11:09:14] loading snapshots from '/run/timeshift/631747/backup/timeshift/snapshots': 18 found [11:09:14] SnapshotRepo: check_status() [11:09:14] SnapshotRepo: available() [11:09:14] is_available: ok [11:09:14] SnapshotRepo: has_snapshots() [11:09:14] SnapshotRepo: has_space() - 0 required (0 B) [11:09:14] Device: get_disk_space_using_df(): 1 [11:09:14] Périphérique pour les instantanés: '/dev/sda1' [11:09:14] Emplacement des snapshots: /run/timeshift/631747/backup [11:09:14] Valider [11:09:14] 18 instantanés, 831,9 GB libre [11:09:14] Statut: HAS_SNAPSHOTS_HAS_SPACE [11:09:14] [11:09:14] SnapshotRepo: check_status(): exit [11:09:14] SnapshotRepo: has_snapshots() [11:09:14] SnapshotRepo: has_snapshots() ``` Autre curiosité: ``` $mount | egrep /dev/sda /dev/sda1 on /media/eric/Tosh2Tbleu1ext4 type ext4 (rw,nosuid,nodev,relatime,errors=remount-ro,stripe=32751,uhelper=udisks2) /dev/sda1 on /run/timeshift/191615/backup type ext4 (rw,relatime,errors=remount-ro,stripe=32751) /dev/sda1 on /run/timeshift/631747/backup type ext4 (rw,relatime,errors=remount-ro,stripe=32751) ``` le support de la sauvegarde usb (sda1) est monté 3 fois Les droits sont: ``` /media/eric$ls -ltr /media/eric/ | egrep Tosh2Tbleu1ext4 drwxr-xr-x 4 eric root 4096 24_12_22-17:08 Tosh2Tbleu1ext4 /media/eric$ls -ltr /media/eric/Tosh2Tbleu1ext4 total 20 drwx------ 2 root root 16384 18_09_07-19:34 lost+found drwxr-xr-x 9 root root 4096 25_06_30-17:02 timeshift /media/eric$ls -ltr /media/eric/Tosh2Tbleu1ext4/timeshift/ total 28 drwxr-xr-x 2 root root 4096 25_06_30-17:02 snapshots-hourly drwxr-xr-x 2 root root 4096 25_06_30-17:02 snapshots-ondemand drwxr-xr-x 2 root root 4096 25_06_30-17:02 snapshots-monthly drwxr-xr-x 2 root root 4096 25_06_30-17:02 snapshots-boot drwxr-xr-x 2 root root 4096 25_06_30-17:02 snapshots-weekly drwxr-xr-x 2 root root 4096 25_06_30-17:02 snapshots-daily drwxr-xr-x 21 root root 4096 25_07_03-12:11 snapshots ``` **L’indication clé:** impossible à root d’effacer un fichier: accessible en lecture seulement ``` /media/eric/Tosh2Tbleu1ext4/timeshift/snapshots# rm jdupes.list rm: impossible de supprimer 'jdupes.list': Système de fichiers accessible en lecture seulement # ls -ltr jdupes.list -rw-r--r-- 1 root root 334323056 16 août 2024 jdupes.list ``` pourtant il est bien affiché: `rw` à tous les niveaux ---
**Author:** ![josephtux](https://www.debian-fr.org/user_avatar/www.debian-fr.org/josephtux/32/3985_2.png) [@josephtux](https://www.debian-fr.org/u/josephtux)\ **Post date:** [Juillet 4, 2025, 10:11 UTC](https://www.debian-fr.org/t/timeshift-disque-usb-en-boucle/91309/4 "2025-07-04T10:11:31Z")
Un extrait de dmesg: ``` 83456.398717] EXT4-fs (sda1): Remounting filesystem read-only [83456.399328] EXT4-fs error (device sda1): ext4_journal_check_start:83: comm rm: Detected aborted journal [83456.409839] EXT4-fs (sda1): Remounting filesystem read-only [83456.409946] EXT4-fs error (device sda1): ext4_journal_check_start:83: comm rm: Detected aborted journal [83456.420936] EXT4-fs (sda1): Remounting filesystem read-only [83612.006746] perf: interrupt took too long (6244 > 6235), lowering kernel.perf_event_max_sample_rate to 32000 [84079.093944] EXT4-fs error: 27 callbacks suppressed [84079.093946] EXT4-fs error (device sda1): ext4_journal_check_start:83: comm timeshift-gtk: Detected aborted journal [84079.119084] EXT4-fs: 27 callbacks suppressed [84079.119097] EXT4-fs (sda1): Remounting filesystem read-only [84079.119113] EXT4-fs error (device sda1) in __ext4_new_inode:1088: Journal has aborted [84079.129982] EXT4-fs (sda1): Remounting filesystem read-only [84079.130351] EXT4-fs error (device sda1): ext4_journal_check_start:83: comm timeshift-gtk: Detected aborted journal [84079.141073] EXT4-fs (sda1): Remounting filesystem read-only [84079.141085] EXT4-fs error (device sda1) in __ext4_new_inode:1088: Journal has aborted [84079.152173] EXT4-fs (sda1): Remounting filesystem read-only [84079.153039] EXT4-fs error (device sda1): ext4_journal_check_start:83: comm timeshift-gtk: Detected aborted journal [84079.163312] EXT4-fs (sda1): Remounting filesystem read-only [84079.163335] EXT4-fs error (device sda1) in __ext4_new_inode:1088: Journal has aborted [84079.174553] EXT4-fs (sda1): Remounting filesystem read-only ``` pourtant je vois le contraire avec `mount` comme avec `ls -l` montrés ci-dessus, (ou vois-je mal?) ---
**Author:** ![Clochette](https://www.debian-fr.org/user_avatar/www.debian-fr.org/clochette/32/8757_2.png) [@Clochette](https://www.debian-fr.org/u/Clochette)\ **Post date:** [Juillet 4, 2025, 10:40 UTC](https://www.debian-fr.org/t/timeshift-disque-usb-en-boucle/91309/5 "2025-07-04T10:40:04Z")
Tu as des erreurs avec le file system apparemment, le problème viens sans doute de là, est-ce un vieux disque ? ---
**Author:** ![josephtux](https://www.debian-fr.org/user_avatar/www.debian-fr.org/josephtux/32/3985_2.png) [@josephtux](https://www.debian-fr.org/u/josephtux)\ **Post date:** [Juillet 4, 2025, 11:46 UTC](https://www.debian-fr.org/t/timeshift-disque-usb-en-boucle/91309/6 "2025-07-04T11:46:06Z")
Je ne sais pas, qu’est-ce qu’un vieux disque? $sudo lshw | egrep -A25 /dev/sda1 nom logique: /dev/sda1 nom logique: /media/eric/Tosh2Tbleu1ext4 nom logique: /run/timeshift/191615/backup nom logique: /run/timeshift/631747/backup version: 1.0 numéro de série: 5ecc1c9a-b5d1-42d6-bd24-9c1ca73c3adf taille: 1863GiB capacité: 1863GiB fonctionnalités: primary bootable journaled extended\_attributes large\_files huge\_files dir\_nlink recover extents ext4 ext2 initialized configuration: created=2018-09-07 19:34:48 filesystem=ext4 label=Tosh2Tbleu1ext4 lastmountpoint=/run/timeshift/1177/backup modified=2025-07-04 11:28:37 mount.fstype=ext4 mount.options=rw,relatime,errors=remount-ro,stripe=32751 mounted=2025-07-03 11:48:37 state=mounted $sudo smartctl -a /dev/sda smartctl 7.3 2022-02-28 r5338 [x86\_64-linux-6.1.0-37-amd64] (local build) Copyright (C) 2002-22, Bruce Allen, Christian Franke, [www.smartmontools.org](http://www.smartmontools.org) === START OF INFORMATION SECTION === Model Family: Toshiba 2.5" HDD MQ03UBB… Device Model: TOSHIBA MQ03UBB200 Serial Number: 471BT81UT LU WWN Device Id: 0 000000 000000000 Firmware Version: JP050U User Capacity: 2 000 398 934 016 bytes [2,00 TB] Sector Sizes: 512 bytes logical, 4096 bytes physical Rotation Rate: 5400 rpm Form Factor: 2.5 inches Device is: In smartctl database 7.3/5319 ATA Version is: ATA8-ACS (minor revision not indicated) SATA Version is: SATA 3.0, 3.0 Gb/s (current: 3.0 Gb/s) Local Time is: Fri Jul 4 13:45:21 2025 CEST SMART support is: Available - device has SMART capability. SMART support is: Enabled === START OF READ SMART DATA SECTION === SMART Status not supported: Incomplete response, ATA output registers missing SMART overall-health self-assessment test result: PASSED Warning: This result is based on an Attribute check. 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: ( 402) 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 - 4487 4 Start\_Stop\_Count 0x0032 100 100 000 Old\_age Always - 5272 5 Reallocated\_Sector\_Ct 0x0033 100 100 050 Pre-fail Always - 0 7 Seek\_Error\_Rate 0x000b 100 100 050 Pre-fail Always - 0 8 Seek\_Time\_Performance 0x0005 100 100 050 Pre-fail Offline - 0 9 Power\_On\_Hours 0x0032 076 076 000 Old\_age Always - 9728 10 Spin\_Retry\_Count 0x0033 205 100 030 Pre-fail Always - 0 12 Power\_Cycle\_Count 0x0032 100 100 000 Old\_age Always - 339 191 G-Sense\_Error\_Rate 0x0032 100 100 000 Old\_age Always - 3 192 Power-Off\_Retract\_Count 0x0032 100 100 000 Old\_age Always - 50 193 Load\_Cycle\_Count 0x0032 100 100 000 Old\_age Always - 6502 194 Temperature\_Celsius 0x0022 100 100 000 Old\_age Always - 27 (Min/Max 14/46) 196 Reallocated\_Event\_Count 0x0032 100 100 000 Old\_age Always - 0 197 Current\_Pending\_Sector 0x0032 100 100 000 Old\_age Always - 0 198 Offline\_Uncorrectable 0x0030 100 100 000 Old\_age Offline - 0 199 UDMA\_CRC\_Error\_Count 0x0032 200 200 000 Old\_age Always - 0 220 Disk\_Shift 0x0002 100 100 000 Old\_age Always - 0 222 Loaded\_Hours 0x0032 100 100 000 Old\_age Always - 343 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 - 275 240 Head\_Flying\_Hours 0x0001 100 100 001 Pre-fail Offline - 0 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 sur l’age: > [@josephtux](#): > > 9 Power\_On\_Hours 0x0032 076 076 000 Old\_age Always - 9728 > 10 Spin\_Retry\_Count 0x0033 205 100 030 Pre-fail Always - 0 > 12 Power\_Cycle\_Count 0x0032 100 100 000 Old\_age Always - 339 > 191 G-Sense\_Error\_Rate 0x0032 100 100 000 Old\_age Always - 3 > 192 Power-Off\_Retract\_Count 0x0032 100 100 000 Old\_age Always - 50 > 193 Load\_Cycle\_Count 0x0032 100 100 000 Old\_age Always - 6502 > 194 Temperature\_Celsius 0x0022 100 100 000 Old\_age Always - 27 (Min/Max 14/46) > 196 Reallocated\_Event\_Count 0x0032 100 100 000 Old\_age Always - 0 > 197 Current\_Pending\_Sector 0x0032 100 100 000 Old\_age Always - 0 > 198 Offline\_Uncorrectable 0x0030 100 100 000 Old\_age Offline - 0 > 199 UDMA\_CRC\_Error\_Count 0x0032 200 200 000 Old\_age Always - 0 > 220 Disk\_Shift 0x0002 100 100 000 Old\_age Always - 0 > 222 Loaded\_Hours 0x0032 100 100 000 Old\_age Always - 343 > 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 - 275 > 240 Head\_Flying\_Hours 0x0001 100 100 001 Pre-fail Offline - 0 Il ya aussi, sur gparted, une icone (une clé?) : ![gpartedSurTosh2Tbleu](https://www.debian-fr.org/uploads/default/original/2X/1/1f86ba9b23de866b24a82bdcd5fca23f5bfd88c6.png) Je ne sais pas pourquoi il y a un «drapeau boot», puisque ce n’est pas (je suppose) un disque de démarrage, exclusivement réservé à ttimeshift. ---
**Author:** ![josephtux](https://www.debian-fr.org/user_avatar/www.debian-fr.org/josephtux/32/3985_2.png) [@josephtux](https://www.debian-fr.org/u/josephtux)\ **Post date:** [Juillet 4, 2025, 11:58 UTC](https://www.debian-fr.org/t/timeshift-disque-usb-en-boucle/91309/7 "2025-07-04T11:58:56Z")
Je trouve d’autres dysfonctionnements sur mon système: (donc sur un autre support) - le chemin absolu devient nécessaire: Par exemple, si je fais `ls -l fichier` sur des fichiers récemment créés (par exemple une capture d’écran) en étant dans le répertoire `/home/user/`, ce fichier ne s’affiche pas, mais` ls -l /home/user/fichier` montre qu’il est bien là - Je n’ai plus de son