#1 Le 04/02/2026, à 11:21
- geole
(RESOLU par abandon de refind) Volume corrupt
Bonjour
Je viens d'installer la daily téléchargée avant-hier
Pas de problème d'installation mais boot impossible avec message
ERROR: Volume Corrupt while loading vmlimuz-6.18.0-9_generic
Mais une nouvelle daily est en cours de téléchargement.
Nouvelle version installée
Même problème
Mais il a fallu plus de 11 minutes avant que /target soit créé....
a@a:/mnt/Installation$ grep happy journalctl.txt
Feb 04 12:01:12 ubuntu subiquity_log.5086[10113]: devsync happy - path /dev/sda now exists
Feb 04 12:01:21 ubuntu subiquity_log.5086[10113]: devsync happy - path /dev/sda now exists
Feb 04 12:01:31 ubuntu subiquity_log.5086[10113]: devsync happy - path /dev/sda now exists
Feb 04 12:01:39 ubuntu subiquity_log.5086[10113]: devsync happy - path /dev/sda now exists
Feb 04 12:02:02 ubuntu subiquity_log.5086[10113]: devsync happy - path /dev/sda now exists
Feb 04 12:02:10 ubuntu subiquity_log.5086[10113]: devsync happy - path /dev/sda now exists
Feb 04 12:02:18 ubuntu subiquity_log.5086[10113]: devsync happy - path /dev/sda now exists
Feb 04 12:02:30 ubuntu subiquity_log.5086[10113]: devsync happy - path /dev/sda now exists
Feb 04 12:02:35 ubuntu subiquity_log.5086[10113]: devsync happy - path /dev/sda now exists
Feb 04 12:02:46 ubuntu subiquity_log.5086[10113]: devsync happy - path /dev/sda now exists
Feb 04 12:02:52 ubuntu subiquity_log.5086[10113]: devsync happy - path /dev/sda now exists
Feb 04 12:03:00 ubuntu subiquity_log.5086[10113]: devsync happy - path /dev/sda now exists
Feb 04 12:03:08 ubuntu subiquity_log.5086[10113]: devsync happy - path /dev/sda now exists
Feb 04 12:03:20 ubuntu subiquity_log.5086[10113]: devsync happy - path /dev/sda now exists
Feb 04 12:03:25 ubuntu subiquity_log.5086[10113]: devsync happy - path /dev/sda now exists
Feb 04 12:03:37 ubuntu subiquity_log.5086[10113]: devsync happy - path /dev/sda now exists
Feb 04 12:03:42 ubuntu subiquity_log.5086[10113]: devsync happy - path /dev/sda now exists
Feb 04 12:03:53 ubuntu subiquity_log.5086[10113]: devsync happy - path /dev/sda now exists
Feb 04 12:03:59 ubuntu subiquity_log.5086[10113]: devsync happy - path /dev/sda now exists
Feb 04 12:04:11 ubuntu subiquity_log.5086[10113]: devsync happy - path /dev/sda now exists
Feb 04 12:04:16 ubuntu subiquity_log.5086[10113]: devsync happy - path /dev/sda now exists
Feb 04 12:04:25 ubuntu subiquity_log.5086[10113]: devsync happy - path /dev/sda now exists
Feb 04 12:04:37 ubuntu subiquity_log.5086[10113]: devsync happy - path /dev/sda now exists
Feb 04 12:04:42 ubuntu subiquity_log.5086[10113]: devsync happy - path /dev/sda now exists
Feb 04 12:04:53 ubuntu subiquity_log.5086[10113]: devsync happy - path /dev/sda now exists
Feb 04 12:04:58 ubuntu subiquity_log.5086[10113]: devsync happy - path /dev/sda now exists
Feb 04 12:05:10 ubuntu subiquity_log.5086[10113]: devsync happy - path /dev/sda now exists
Feb 04 12:05:15 ubuntu subiquity_log.5086[10113]: devsync happy - path /dev/sda now exists
Feb 04 12:05:27 ubuntu subiquity_log.5086[10113]: devsync happy - path /dev/sda now exists
Feb 04 12:05:32 ubuntu subiquity_log.5086[10113]: devsync happy - path /dev/sda now exists
Feb 04 12:05:40 ubuntu subiquity_log.5086[10113]: devsync happy - path /dev/sda now exists
Feb 04 12:05:48 ubuntu subiquity_log.5086[10113]: devsync happy - path /dev/sda now exists
Feb 04 12:05:56 ubuntu subiquity_log.5086[10113]: devsync happy - path /dev/sda now exists
Feb 04 12:06:08 ubuntu subiquity_log.5086[10113]: devsync happy - path /dev/sda now exists
Feb 04 12:06:13 ubuntu subiquity_log.5086[10113]: devsync happy - path /dev/sda now exists
Feb 04 12:06:25 ubuntu subiquity_log.5086[10113]: devsync happy - path /dev/sda now exists
Feb 04 12:06:30 ubuntu subiquity_log.5086[10113]: devsync happy - path /dev/sda now exists
Feb 04 12:06:42 ubuntu subiquity_log.5086[10113]: devsync happy - path /dev/sda now exists
Feb 04 12:06:48 ubuntu subiquity_log.5086[10113]: devsync happy - path /dev/sda now exists
Feb 04 12:06:59 ubuntu subiquity_log.5086[10113]: devsync happy - path /dev/sda now exists
Feb 04 12:07:04 ubuntu subiquity_log.5086[10113]: devsync happy - path /dev/sda now exists
Feb 04 12:07:15 ubuntu subiquity_log.5086[10113]: devsync happy - path /dev/sda now exists
Feb 04 12:07:20 ubuntu subiquity_log.5086[10113]: devsync happy - path /dev/sda now exists
Feb 04 12:07:32 ubuntu subiquity_log.5086[10113]: devsync happy - path /dev/sda now exists
Feb 04 12:07:37 ubuntu subiquity_log.5086[10113]: devsync happy - path /dev/sda now exists
Feb 04 12:07:49 ubuntu subiquity_log.5086[10113]: devsync happy - path /dev/sda now exists
Feb 04 12:07:54 ubuntu subiquity_log.5086[10113]: devsync happy - path /dev/sda now exists
Feb 04 12:08:02 ubuntu subiquity_log.5086[10113]: devsync happy - path /dev/sda now exists
Feb 04 12:08:14 ubuntu subiquity_log.5086[10113]: devsync happy - path /dev/sda now exists
Feb 04 12:08:19 ubuntu subiquity_log.5086[10113]: devsync happy - path /dev/sda now exists
Feb 04 12:08:30 ubuntu subiquity_log.5086[10113]: devsync happy - path /dev/sda now exists
Feb 04 12:08:36 ubuntu subiquity_log.5086[10113]: devsync happy - path /dev/sda now exists
Feb 04 12:08:44 ubuntu subiquity_log.5086[10113]: devsync happy - path /dev/sda now exists
Feb 04 12:08:53 ubuntu subiquity_log.5086[10113]: devsync happy - path /dev/sda now exists
Feb 04 12:09:05 ubuntu subiquity_log.5086[10113]: devsync happy - path /dev/sda now exists
Feb 04 12:09:10 ubuntu subiquity_log.5086[10113]: devsync happy - path /dev/sda now exists
Feb 04 12:09:22 ubuntu subiquity_log.5086[10113]: devsync happy - path /dev/sda now exists
Feb 04 12:09:27 ubuntu subiquity_log.5086[10113]: devsync happy - path /dev/sda now exists
Feb 04 12:09:38 ubuntu subiquity_log.5086[10113]: devsync happy - path /dev/sda now exists
Feb 04 12:09:44 ubuntu subiquity_log.5086[10113]: devsync happy - path /dev/sda now exists
Feb 04 12:09:56 ubuntu subiquity_log.5086[10113]: devsync happy - path /dev/sda now exists
Feb 04 12:10:01 ubuntu subiquity_log.5086[10113]: devsync happy - path /dev/sda now exists
Feb 04 12:10:12 ubuntu subiquity_log.5086[10113]: devsync happy - path /dev/sda now exists
Feb 04 12:10:17 ubuntu subiquity_log.5086[10113]: devsync happy - path /dev/sda now exists
Feb 04 12:10:29 ubuntu subiquity_log.5086[10113]: devsync happy - path /dev/sda now exists
Feb 04 12:10:34 ubuntu subiquity_log.5086[10113]: devsync happy - path /dev/sda now exists
Feb 04 12:10:46 ubuntu subiquity_log.5086[10113]: devsync happy - path /dev/sda now exists
Feb 04 12:10:51 ubuntu subiquity_log.5086[10113]: devsync happy - path /dev/sda now exists
Feb 04 12:11:02 ubuntu subiquity_log.5086[10113]: devsync happy - path /dev/sda now exists
Feb 04 12:11:14 ubuntu subiquity_log.5086[10113]: devsync happy - path /dev/sda now exists
Feb 04 12:11:19 ubuntu subiquity_log.5086[10113]: devsync happy - path /dev/sda now exists
Feb 04 12:11:31 ubuntu subiquity_log.5086[10113]: devsync happy - path /dev/sda now exists
Feb 04 12:11:36 ubuntu subiquity_log.5086[10113]: devsync happy - path /dev/sda now exists
Feb 04 12:11:49 ubuntu subiquity_log.5086[10113]: devsync happy - path /dev/sda now exists
Feb 04 12:11:54 ubuntu subiquity_log.5086[10113]: devsync happy - path /dev/sda now exists
Feb 04 12:12:02 ubuntu subiquity_log.5086[10113]: devsync happy - path /dev/sda now exists
Feb 04 12:12:14 ubuntu subiquity_log.5086[10113]: devsync happy - path /dev/sda now exists
Feb 04 12:12:19 ubuntu subiquity_log.5086[10113]: devsync happy - path /dev/sda now exists
Feb 04 12:12:31 ubuntu subiquity_log.5086[10113]: devsync happy - path /dev/sda now exists
Feb 04 12:12:37 ubuntu subiquity_log.5086[10113]: devsync happy - path /dev/sda now exists
Feb 04 12:12:49 ubuntu subiquity_log.5086[10113]: devsync happy - path /dev/sda now exists
Feb 04 12:12:54 ubuntu subiquity_log.5086[10113]: devsync happy - path /dev/sda now exists
Feb 04 12:13:05 ubuntu subiquity_log.5086[10113]: devsync happy - path /dev/sda now exists
Feb 04 12:13:11 ubuntu subiquity_log.5086[10113]: devsync happy - path /dev/sda now exists
Feb 04 12:13:23 ubuntu subiquity_log.5086[10113]: devsync happy - path /dev/sda now exists
Feb 04 12:13:28 ubuntu subiquity_log.5086[10113]: devsync happy - path /dev/sda now exists
Feb 04 12:13:40 ubuntu subiquity_log.5086[10113]: devsync happy - path /dev/sda now exists
Feb 04 12:13:46 ubuntu subiquity_log.5086[10113]: devsync happy - path /dev/sda now exists
Feb 04 12:13:58 ubuntu subiquity_log.5086[10113]: devsync happy - path /dev/sda now exists
Feb 04 12:14:03 ubuntu subiquity_log.5086[10113]: devsync happy - path /dev/sda now exists
Feb 04 12:14:14 ubuntu subiquity_log.5086[10113]: devsync happy - path /dev/sda now exists
Feb 04 12:14:20 ubuntu subiquity_log.5086[10113]: devsync happy - path /dev/sda now exists
Feb 04 12:14:32 ubuntu subiquity_log.5086[10113]: devsync happy - path /dev/sda now exists
Feb 04 12:14:38 ubuntu subiquity_log.5086[10113]: devsync happy - path /dev/sda now exists
Feb 04 12:14:50 ubuntu subiquity_log.5086[10113]: devsync happy - path /dev/sda now exists
Feb 04 12:14:55 ubuntu subiquity_log.5086[10113]: devsync happy - path /dev/sda now exists
Feb 04 12:23:51 ubuntu subiquity_log.5086[18952]: devsync happy - path /dev/sda now exists
Feb 04 12:24:01 ubuntu subiquity_log.5086[18952]: devsync happy - path /dev/sda now existsA noter une installation partie en boucle avec 100% de consommation processeur après avoir choisi d installer le home dans une autre partition.
Dernière modification par geole (Le 13/02/2026, à 11:22)
Les grilles de l'installateur https://doc.ubuntu-fr.org/tutoriel/inst … _subiquity
Les partitions EXT4 des disques externes => https://forum.ubuntu-fr.org/viewtopic.p … #p22697248
Hors ligne
#2 Le 06/02/2026, à 00:10
- geole
Re : (RESOLU par abandon de refind) Volume corrupt
Bonsoir
Toujours le même problème avec l ISO fournie cet après-midi
D autre part, qui a pu réaliser une installation personnalisée en demandant la création d une partition dédiée à home
Les grilles de l'installateur https://doc.ubuntu-fr.org/tutoriel/inst … _subiquity
Les partitions EXT4 des disques externes => https://forum.ubuntu-fr.org/viewtopic.p … #p22697248
Hors ligne
#3 Le 06/02/2026, à 16:33
- geole
Re : (RESOLU par abandon de refind) Volume corrupt
Bonjour
Et cela continue avec le nouvel ISO de ce jour.
Les grilles de l'installateur https://doc.ubuntu-fr.org/tutoriel/inst … _subiquity
Les partitions EXT4 des disques externes => https://forum.ubuntu-fr.org/viewtopic.p … #p22697248
Hors ligne
#4 Le 13/02/2026, à 11:19
- geole
Re : (RESOLU par abandon de refind) Volume corrupt
Bonjour
Comme cela continue avec la nouvelle ISO, j'ai mis en doute le logiciel de boot REFIND pour utiliser le grub.
Donc problème résolu.
Je suppose que les fichiers de boot compressés utilisent un autre algorithmique que refind ne connait pas.
lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu Resolute Raccoon (development branch)
Release: 26.04
Codename: resolute
df -htext4
Sys. de fichiers Taille Utilisé Dispo Uti% Monté sur
/dev/sda10 30G 11G 18G 39% /
ls -l initrd.img-*
-rw------- 1 root root 37533147 Feb 13 08:42 initrd.img-6.19.0-3-generic
ls -l vmlinuz-*
-rw------- 1 root root 17508424 Jan 26 22:53 vmlinuz-6.19.0-3-genericNota. Pour pouvoir faire l'installation dans une partition dédiée au home, J'iai du demander le formatage de la partition home autrement l'installateur ne mettait pas en route.
Dernière modification par geole (Le 13/02/2026, à 11:53)
Les grilles de l'installateur https://doc.ubuntu-fr.org/tutoriel/inst … _subiquity
Les partitions EXT4 des disques externes => https://forum.ubuntu-fr.org/viewtopic.p … #p22697248
Hors ligne
#5 Le 05/03/2026, à 19:34
- geole
Re : (RESOLU par abandon de refind) Volume corrupt
Bonjour
Toujours le même problème avec la dernière DAILY. Mais j'ai trouvé un contournement en demandant à refind de lancer le grub EFI.
A noter que si on veut procéder à une installation en absence de réseau, l'installateur ne refuse pas mais au bout de trois heures d'attente, on constate que la partition target ne contient que le répertoire boot.
Dernière modification par geole (Le 05/03/2026, à 19:38)
Les grilles de l'installateur https://doc.ubuntu-fr.org/tutoriel/inst … _subiquity
Les partitions EXT4 des disques externes => https://forum.ubuntu-fr.org/viewtopic.p … #p22697248
Hors ligne
#6 Le 18/03/2026, à 12:25
- geole
Re : (RESOLU par abandon de refind) Volume corrupt
Bonjour
Aujourd hui, installation d une nouvelle version qui est bien détectée par refind.
Mais beaucoup de lignes en rouge.........
lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu Resolute Raccoon (development branch)
Release: 26.04
Codename: resoluteuname -a
Linux a 7.0.0-7-generic #7-Ubuntu SMP PREEMPT_DYNAMIC Thu Mar 12 11:34:39 UTC 2026 x86_64 GNU/Linuxjournalctl --no-pager -b -p err
mars 18 11:12:10 localhost.localdomain (udev-worker)[289]: tty0: Failed to find and pin callout binary "/sbin/initqueue": No such file or directory
mars 18 11:12:10 localhost.localdomain (udev-worker)[278]: card0: Failed to find and pin callout binary "/usr/lib/snapd/snap-device-helper": No such file or directory
mars 18 11:12:10 localhost.localdomain (udev-worker)[278]: card0: Failed to find and pin callout binary "/usr/lib/snapd/snap-device-helper": No such file or directory
mars 18 11:12:10 localhost.localdomain (udev-worker)[278]: card0: Failed to find and pin callout binary "/usr/lib/snapd/snap-device-helper": No such file or directory
mars 18 11:12:10 localhost.localdomain (udev-worker)[278]: card0: Failed to find and pin callout binary "/usr/lib/snapd/snap-device-helper": No such file or directory
mars 18 11:12:10 localhost.localdomain (udev-worker)[278]: card0: Failed to find and pin callout binary "/usr/lib/snapd/snap-device-helper": No such file or directory
mars 18 11:12:10 localhost.localdomain (udev-worker)[278]: card0: Failed to find and pin callout binary "/usr/lib/snapd/snap-device-helper": No such file or directory
mars 18 11:12:10 localhost.localdomain (udev-worker)[278]: card0: Failed to find and pin callout binary "/usr/lib/snapd/snap-device-helper": No such file or directory
mars 18 11:12:10 localhost.localdomain (udev-worker)[278]: card0: Failed to find and pin callout binary "/usr/lib/snapd/snap-device-helper": No such file or directory
mars 18 11:12:10 localhost.localdomain (udev-worker)[278]: card0: Failed to find and pin callout binary "/usr/lib/snapd/snap-device-helper": No such file or directory
mars 18 11:12:10 localhost.localdomain (udev-worker)[278]: card0: Failed to find and pin callout binary "/usr/lib/snapd/snap-device-helper": No such file or directory
mars 18 11:12:10 localhost.localdomain (udev-worker)[278]: card0: Failed to find and pin callout binary "/usr/lib/snapd/snap-device-helper": No such file or directory
mars 18 11:12:10 localhost.localdomain (udev-worker)[278]: card0: Failed to find and pin callout binary "/usr/lib/snapd/snap-device-helper": No such file or directory
mars 18 11:12:10 localhost.localdomain (udev-worker)[278]: card0: Failed to find and pin callout binary "/usr/lib/snapd/snap-device-helper": No such file or directory
mars 18 11:12:10 localhost.localdomain (udev-worker)[278]: card0: Failed to find and pin callout binary "/usr/lib/snapd/snap-device-helper": No such file or directory
mars 18 11:12:10 localhost.localdomain (udev-worker)[278]: card0-Unknown-1: Failed to find and pin callout binary "/usr/lib/snapd/snap-device-helper": No such file or directory
mars 18 11:12:10 localhost.localdomain (udev-worker)[278]: card0-Unknown-1: Failed to find and pin callout binary "/usr/lib/snapd/snap-device-helper": No such file or directory
mars 18 11:12:10 localhost.localdomain (udev-worker)[278]: card0-Unknown-1: Failed to find and pin callout binary "/usr/lib/snapd/snap-device-helper": No such file or directory
mars 18 11:12:10 localhost.localdomain (udev-worker)[278]: card0-Unknown-1: Failed to find and pin callout binary "/usr/lib/snapd/snap-device-helper": No such file or directory
mars 18 11:12:10 localhost.localdomain (udev-worker)[278]: card0-Unknown-1: Failed to find and pin callout binary "/usr/lib/snapd/snap-device-helper": No such file or directory
mars 18 11:12:10 localhost.localdomain (udev-worker)[278]: card0-Unknown-1: Failed to find and pin callout binary "/usr/lib/snapd/snap-device-helper": No such file or directory
mars 18 11:12:10 localhost.localdomain (udev-worker)[278]: card0-Unknown-1: Failed to find and pin callout binary "/usr/lib/snapd/snap-device-helper": No such file or directory
mars 18 11:12:10 localhost.localdomain (udev-worker)[278]: card0-Unknown-1: Failed to find and pin callout binary "/usr/lib/snapd/snap-device-helper": No such file or directory
mars 18 11:12:10 localhost.localdomain (udev-worker)[278]: card0-Unknown-1: Failed to find and pin callout binary "/usr/lib/snapd/snap-device-helper": No such file or directory
mars 18 11:12:10 localhost.localdomain (udev-worker)[278]: card0-Unknown-1: Failed to find and pin callout binary "/usr/lib/snapd/snap-device-helper": No such file or directory
mars 18 11:12:10 localhost.localdomain (udev-worker)[278]: card0-Unknown-1: Failed to find and pin callout binary "/usr/lib/snapd/snap-device-helper": No such file or directory
mars 18 11:12:10 localhost.localdomain (udev-worker)[278]: card0-Unknown-1: Failed to find and pin callout binary "/usr/lib/snapd/snap-device-helper": No such file or directory
mars 18 11:12:10 localhost.localdomain (udev-worker)[278]: card0-Unknown-1: Failed to find and pin callout binary "/usr/lib/snapd/snap-device-helper": No such file or directory
mars 18 11:12:10 localhost.localdomain (udev-worker)[278]: card0-Unknown-1: Failed to find and pin callout binary "/usr/lib/snapd/snap-device-helper": No such file or directory
mars 18 11:12:10 localhost.localdomain (udev-worker)[273]: full: Failed to find and pin callout binary "/usr/lib/snapd/snap-device-helper": No such file or directory
mars 18 11:12:10 localhost.localdomain (udev-worker)[273]: full: Failed to find and pin callout binary "/usr/lib/snapd/snap-device-helper": No such file or directory
mars 18 11:12:10 localhost.localdomain (udev-worker)[266]: system: Failed to find and pin callout binary "/usr/lib/snapd/snap-device-helper": No such file or directory
mars 18 11:12:10 localhost.localdomain (udev-worker)[266]: system: Failed to find and pin callout binary "/usr/lib/snapd/snap-device-helper": No such file or directory
mars 18 11:12:10 localhost.localdomain (udev-worker)[266]: system: Failed to find and pin callout binary "/usr/lib/snapd/snap-device-helper": No such file or directory
mars 18 11:12:10 localhost.localdomain (udev-worker)[266]: system: Failed to find and pin callout binary "/usr/lib/snapd/snap-device-helper": No such file or directory
mars 18 11:12:10 localhost.localdomain (udev-worker)[266]: system: Failed to find and pin callout binary "/usr/lib/snapd/snap-device-helper": No such file or directory
mars 18 11:12:10 localhost.localdomain (udev-worker)[266]: system: Failed to find and pin callout binary "/usr/lib/snapd/snap-device-helper": No such file or directory
mars 18 11:12:10 localhost.localdomain (udev-worker)[266]: system: Failed to find and pin callout binary "/usr/lib/snapd/snap-device-helper": No such file or directory
mars 18 11:12:10 localhost.localdomain (udev-worker)[266]: system: Failed to find and pin callout binary "/usr/lib/snapd/snap-device-helper": No such file or directory
mars 18 11:12:10 localhost.localdomain (udev-worker)[266]: system: Failed to find and pin callout binary "/usr/lib/snapd/snap-device-helper": No such file or directory
mars 18 11:12:10 localhost.localdomain (udev-worker)[266]: system: Failed to find and pin callout binary "/usr/lib/snapd/snap-device-helper": No such file or directory
mars 18 11:12:10 localhost.localdomain (udev-worker)[266]: system: Failed to find and pin callout binary "/usr/lib/snapd/snap-device-helper": No such file or directory
mars 18 11:12:10 localhost.localdomain (udev-worker)[266]: system: Failed to find and pin callout binary "/usr/lib/snapd/snap-device-helper": No such file or directory
mars 18 11:12:10 localhost.localdomain (udev-worker)[266]: system: Failed to find and pin callout binary "/usr/lib/snapd/snap-device-helper": No such file or directory
mars 18 11:12:10 localhost.localdomain (udev-worker)[266]: system: Failed to find and pin callout binary "/usr/lib/snapd/snap-device-helper": No such file or directory
mars 18 11:13:17 a kernel: nouveau 0000:01:00.0: msvld: unable to load firmware data
mars 18 11:13:17 a kernel: nouveau 0000:01:00.0: msvld: init failed, -19
mars 18 11:13:17 a kernel: nouveau 0000:01:00.0: gr: TRAP ch 3 [007fb02000 gst-plugin-scan[2436]]
mars 18 11:13:17 a kernel: nouveau 0000:01:00.0: gr: GPC0/PROP trap: 00000020 [RT_HEIGHT_OVERRUN] x = 48, y = 16, format = 37, storage type = 0
mars 18 11:13:17 a kernel: nouveau 0000:01:00.0: gr: TRAP ch 3 [007fb02000 gst-plugin-scan[2436]]
mars 18 11:13:17 a kernel: nouveau 0000:01:00.0: gr: GPC0/PROP trap: 00000020 [RT_HEIGHT_OVERRUN] x = 48, y = 16, format = 37, storage type = 0
mars 18 11:13:17 a kernel: nouveau 0000:01:00.0: gr: TRAP ch 3 [007fb02000 gst-plugin-scan[2436]]
mars 18 11:13:17 a kernel: nouveau 0000:01:00.0: gr: GPC0/PROP trap: 00000020 [RT_HEIGHT_OVERRUN] x = 48, y = 16, format = 37, storage type = 0
mars 18 11:13:21 a kernel: nouveau 0000:01:00.0: gr: TRAP ch 2 [007fb54000 gst-plugin-scan[3147]]
mars 18 11:13:21 a kernel: nouveau 0000:01:00.0: gr: GPC0/PROP trap: 00000020 [RT_HEIGHT_OVERRUN] x = 48, y = 16, format = 37, storage type = 0
mars 18 11:13:21 a kernel: nouveau 0000:01:00.0: gr: TRAP ch 2 [007fb54000 gst-plugin-scan[3147]]
mars 18 11:13:21 a kernel: nouveau 0000:01:00.0: gr: GPC0/PROP trap: 00000020 [RT_HEIGHT_OVERRUN] x = 48, y = 16, format = 37, storage type = 0
mars 18 11:13:21 a kernel: nouveau 0000:01:00.0: gr: TRAP ch 2 [007fb54000 gst-plugin-scan[3147]]
mars 18 11:13:21 a kernel: nouveau 0000:01:00.0: gr: GPC0/PROP trap: 00000020 [RT_HEIGHT_OVERRUN] x = 48, y = 16, format = 37, storage type = 0
mars 18 11:13:21 a kernel: nouveau 0000:01:00.0: gr: TRAP ch 2 [007fb54000 gst-plugin-scan[3147]]
mars 18 11:13:21 a kernel: nouveau 0000:01:00.0: gr: GPC0/PROP trap: 00000020 [RT_HEIGHT_OVERRUN] x = 48, y = 16, format = 37, storage type = 0
mars 18 11:13:21 a kernel: nouveau 0000:01:00.0: gr: TRAP ch 2 [007fb54000 gst-plugin-scan[3147]]
mars 18 11:13:21 a kernel: nouveau 0000:01:00.0: gr: GPC0/PROP trap: 00000020 [RT_HEIGHT_OVERRUN] x = 48, y = 16, format = 37, storage type = 0
mars 18 11:13:21 a kernel: nouveau 0000:01:00.0: gr: TRAP ch 2 [007fb54000 gst-plugin-scan[3147]]
mars 18 11:13:21 a kernel: nouveau 0000:01:00.0: gr: GPC0/PROP trap: 00000020 [RT_HEIGHT_OVERRUN] x = 48, y = 16, format = 37, storage type = 0
mars 18 11:13:21 a kernel: nouveau 0000:01:00.0: gr: TRAP ch 2 [007fb54000 gst-plugin-scan[3147]]
mars 18 11:13:21 a kernel: nouveau 0000:01:00.0: gr: GPC0/PROP trap: 00000020 [RT_HEIGHT_OVERRUN] x = 48, y = 16, format = 37, storage type = 0
mars 18 11:13:21 a kernel: nouveau 0000:01:00.0: gr: TRAP ch 2 [007fb54000 gst-plugin-scan[3147]]
mars 18 11:13:21 a kernel: nouveau 0000:01:00.0: gr: GPC0/PROP trap: 00000020 [RT_HEIGHT_OVERRUN] x = 48, y = 16, format = 37, storage type = 0
mars 18 11:13:21 a kernel: nouveau 0000:01:00.0: gr: TRAP ch 3 [007fb02000 gst-plugin-scan[3147]]
mars 18 11:13:21 a kernel: nouveau 0000:01:00.0: gr: GPC0/PROP trap: 00000020 [RT_HEIGHT_OVERRUN] x = 48, y = 16, format = 37, storage type = 0
mars 18 11:13:21 a kernel: nouveau 0000:01:00.0: gr: TRAP ch 3 [007fb02000 gst-plugin-scan[3147]]
mars 18 11:13:21 a kernel: nouveau 0000:01:00.0: gr: GPC0/PROP trap: 00000020 [RT_HEIGHT_OVERRUN] x = 48, y = 16, format = 37, storage type = 0
mars 18 11:13:21 a kernel: nouveau 0000:01:00.0: gr: TRAP ch 3 [007fb02000 gst-plugin-scan[3147]]
mars 18 11:13:21 a kernel: nouveau 0000:01:00.0: gr: GPC0/PROP trap: 00000020 [RT_HEIGHT_OVERRUN] x = 48, y = 16, format = 37, storage type = 0
mars 18 11:13:22 a gdm-password][3043]: gkr-pam: unable to locate daemon control file
mars 18 11:13:29 a kernel: nouveau 0000:01:00.0: msvld: unable to load firmware data
mars 18 11:13:29 a kernel: nouveau 0000:01:00.0: msvld: init failed, -19
mars 18 11:13:29 a kernel: nouveau 0000:01:00.0: gr: TRAP ch 4 [007fa34000 gst-plugin-scan[3827]]
mars 18 11:13:29 a kernel: nouveau 0000:01:00.0: gr: GPC0/PROP trap: 00000020 [RT_HEIGHT_OVERRUN] x = 48, y = 16, format = 37, storage type = 0
mars 18 11:13:29 a kernel: nouveau 0000:01:00.0: gr: TRAP ch 4 [007fa34000 gst-plugin-scan[3827]]
mars 18 11:13:29 a kernel: nouveau 0000:01:00.0: gr: GPC0/PROP trap: 00000020 [RT_HEIGHT_OVERRUN] x = 48, y = 16, format = 37, storage type = 0
mars 18 11:13:29 a kernel: nouveau 0000:01:00.0: gr: TRAP ch 4 [007fa34000 gst-plugin-scan[3827]]
mars 18 11:13:29 a kernel: nouveau 0000:01:00.0: gr: GPC0/PROP trap: 00000020 [RT_HEIGHT_OVERRUN] x = 48, y = 16, format = 37, storage type = 0
mars 18 11:13:30 a systemd[3200]: Failed to start app-gnome-im\x2dlaunch-3870.scope - Application launched by gnome-session-service.
mars 18 11:13:35 a kernel: nouveau 0000:01:00.0: gr: TRAP ch 3 [007fb02000 gst-plugin-scan[4411]]
mars 18 11:13:35 a kernel: nouveau 0000:01:00.0: gr: GPC0/PROP trap: 00000020 [RT_HEIGHT_OVERRUN] x = 48, y = 16, format = 37, storage type = 0
mars 18 11:13:35 a kernel: nouveau 0000:01:00.0: gr: TRAP ch 3 [007fb02000 gst-plugin-scan[4411]]
mars 18 11:13:35 a kernel: nouveau 0000:01:00.0: gr: GPC0/PROP trap: 00000020 [RT_HEIGHT_OVERRUN] x = 48, y = 16, format = 37, storage type = 0
mars 18 11:13:35 a kernel: nouveau 0000:01:00.0: gr: TRAP ch 3 [007fb02000 gst-plugin-scan[4411]]
mars 18 11:13:35 a kernel: nouveau 0000:01:00.0: gr: GPC0/PROP trap: 00000020 [RT_HEIGHT_OVERRUN] x = 48, y = 16, format = 37, storage type = 0
mars 18 11:13:35 a kernel: nouveau 0000:01:00.0: gr: TRAP ch 3 [007fb02000 gst-plugin-scan[4411]]
mars 18 11:13:35 a kernel: nouveau 0000:01:00.0: gr: GPC0/PROP trap: 00000020 [RT_HEIGHT_OVERRUN] x = 48, y = 16, format = 37, storage type = 0
mars 18 11:13:35 a kernel: nouveau 0000:01:00.0: gr: TRAP ch 3 [007fb02000 gst-plugin-scan[4411]]
mars 18 11:13:35 a kernel: nouveau 0000:01:00.0: gr: GPC0/PROP trap: 00000020 [RT_HEIGHT_OVERRUN] x = 48, y = 16, format = 37, storage type = 0
mars 18 11:13:35 a kernel: nouveau 0000:01:00.0: gr: TRAP ch 3 [007fb02000 gst-plugin-scan[4411]]
mars 18 11:13:35 a kernel: nouveau 0000:01:00.0: gr: GPC0/PROP trap: 00000020 [RT_HEIGHT_OVERRUN] x = 48, y = 16, format = 37, storage type = 0
mars 18 11:13:35 a kernel: nouveau 0000:01:00.0: gr: TRAP ch 3 [007fb02000 gst-plugin-scan[4411]]
mars 18 11:13:35 a kernel: nouveau 0000:01:00.0: gr: GPC0/PROP trap: 00000020 [RT_HEIGHT_OVERRUN] x = 48, y = 16, format = 37, storage type = 0
mars 18 11:13:35 a kernel: nouveau 0000:01:00.0: gr: TRAP ch 3 [007fb02000 gst-plugin-scan[4411]]
mars 18 11:13:35 a kernel: nouveau 0000:01:00.0: gr: GPC0/PROP trap: 00000020 [RT_HEIGHT_OVERRUN] x = 48, y = 16, format = 37, storage type = 0
mars 18 11:13:35 a kernel: nouveau 0000:01:00.0: gr: TRAP ch 4 [007fa78000 gst-plugin-scan[4411]]
mars 18 11:13:35 a kernel: nouveau 0000:01:00.0: gr: GPC0/PROP trap: 00000020 [RT_HEIGHT_OVERRUN] x = 48, y = 16, format = 37, storage type = 0
mars 18 11:13:35 a kernel: nouveau 0000:01:00.0: gr: TRAP ch 4 [007fa78000 gst-plugin-scan[4411]]
mars 18 11:13:35 a kernel: nouveau 0000:01:00.0: gr: GPC0/PROP trap: 00000020 [RT_HEIGHT_OVERRUN] x = 48, y = 16, format = 37, storage type = 0
mars 18 11:13:35 a kernel: nouveau 0000:01:00.0: gr: TRAP ch 4 [007fa78000 gst-plugin-scan[4411]]
mars 18 11:13:35 a kernel: nouveau 0000:01:00.0: gr: GPC0/PROP trap: 00000020 [RT_HEIGHT_OVERRUN] x = 48, y = 16, format = 37, storage type = 0
mars 18 11:13:38 a kernel: nouveau 0000:01:00.0: msvld: unable to load firmware data
mars 18 11:13:38 a kernel: nouveau 0000:01:00.0: msvld: init failed, -19
mars 18 11:13:38 a kernel: nouveau 0000:01:00.0: gr: TRAP ch 3 [007fb0b000 gst-plugin-scan[4786]]
mars 18 11:13:38 a kernel: nouveau 0000:01:00.0: gr: GPC0/PROP trap: 00000020 [RT_HEIGHT_OVERRUN] x = 48, y = 16, format = 37, storage type = 0
mars 18 11:13:38 a kernel: nouveau 0000:01:00.0: gr: TRAP ch 3 [007fb0b000 gst-plugin-scan[4786]]
mars 18 11:13:38 a kernel: nouveau 0000:01:00.0: gr: GPC0/PROP trap: 00000020 [RT_HEIGHT_OVERRUN] x = 48, y = 16, format = 37, storage type = 0
mars 18 11:13:38 a kernel: nouveau 0000:01:00.0: gr: TRAP ch 3 [007fb0b000 gst-plugin-scan[4786]]
mars 18 11:13:38 a kernel: nouveau 0000:01:00.0: gr: GPC0/PROP trap: 00000020 [RT_HEIGHT_OVERRUN] x = 48, y = 16, format = 37, storage type = 0
mars 18 11:13:38 a kernel: nouveau 0000:01:00.0: gr: TRAP ch 4 [007fb08000 gst-plugin-scan[4785]]
mars 18 11:13:38 a kernel: nouveau 0000:01:00.0: gr: GPC0/PROP trap: 00000020 [RT_HEIGHT_OVERRUN] x = 48, y = 16, format = 37, storage type = 0
mars 18 11:13:38 a kernel: nouveau 0000:01:00.0: gr: TRAP ch 3 [007fb0b000 gst-plugin-scan[4786]]
mars 18 11:13:38 a kernel: nouveau 0000:01:00.0: gr: GPC0/PROP trap: 00000020 [RT_HEIGHT_OVERRUN] x = 48, y = 16, format = 37, storage type = 0
mars 18 11:13:38 a kernel: nouveau 0000:01:00.0: gr: TRAP ch 3 [007fb0b000 gst-plugin-scan[4786]]
mars 18 11:13:38 a kernel: nouveau 0000:01:00.0: gr: GPC0/PROP trap: 00000020 [RT_HEIGHT_OVERRUN] x = 48, y = 16, format = 37, storage type = 0
mars 18 11:13:38 a kernel: nouveau 0000:01:00.0: gr: TRAP ch 3 [007fb0b000 gst-plugin-scan[4786]]
mars 18 11:13:38 a kernel: nouveau 0000:01:00.0: gr: GPC0/PROP trap: 00000020 [RT_HEIGHT_OVERRUN] x = 48, y = 16, format = 37, storage type = 0
mars 18 11:13:38 a kernel: nouveau 0000:01:00.0: gr: TRAP ch 3 [007fb0b000 gst-plugin-scan[4786]]
mars 18 11:13:38 a kernel: nouveau 0000:01:00.0: gr: GPC0/PROP trap: 00000020 [RT_HEIGHT_OVERRUN] x = 48, y = 16, format = 37, storage type = 0
mars 18 11:13:38 a kernel: nouveau 0000:01:00.0: gr: TRAP ch 3 [007fb0b000 gst-plugin-scan[4786]]
mars 18 11:13:38 a kernel: nouveau 0000:01:00.0: gr: GPC0/PROP trap: 00000020 [RT_HEIGHT_OVERRUN] x = 48, y = 16, format = 37, storage type = 0
mars 18 11:13:38 a kernel: nouveau 0000:01:00.0: gr: TRAP ch 5 [007fb02000 gst-plugin-scan[4786]]
mars 18 11:13:38 a kernel: nouveau 0000:01:00.0: gr: GPC0/PROP trap: 00000020 [RT_HEIGHT_OVERRUN] x = 48, y = 16, format = 37, storage type = 0
mars 18 11:13:38 a kernel: nouveau 0000:01:00.0: gr: TRAP ch 4 [007fb08000 gst-plugin-scan[4785]]
mars 18 11:13:38 a kernel: nouveau 0000:01:00.0: gr: GPC0/PROP trap: 00000020 [RT_HEIGHT_OVERRUN] x = 48, y = 16, format = 37, storage type = 0
mars 18 11:13:38 a kernel: nouveau 0000:01:00.0: gr: TRAP ch 4 [007fb08000 gst-plugin-scan[4786]]
mars 18 11:13:38 a kernel: nouveau 0000:01:00.0: gr: GPC0/PROP trap: 00000020 [RT_HEIGHT_OVERRUN] x = 48, y = 16, format = 37, storage type = 0
mars 18 11:13:38 a kernel: nouveau 0000:01:00.0: gr: TRAP ch 5 [007fb02000 gst-plugin-scan[4785]]
mars 18 11:13:38 a kernel: nouveau 0000:01:00.0: gr: GPC0/PROP trap: 00000020 [RT_HEIGHT_OVERRUN] x = 48, y = 16, format = 37, storage type = 0
mars 18 11:13:38 a kernel: nouveau 0000:01:00.0: gr: TRAP ch 4 [007fb08000 gst-plugin-scan[4786]]
mars 18 11:13:38 a kernel: nouveau 0000:01:00.0: gr: GPC0/PROP trap: 00000020 [RT_HEIGHT_OVERRUN] x = 48, y = 16, format = 37, storage type = 0
mars 18 11:13:39 a kernel: nouveau 0000:01:00.0: msvld: unable to load firmware data
mars 18 11:13:39 a kernel: nouveau 0000:01:00.0: msvld: init failed, -19
mars 18 11:13:39 a kernel: nouveau 0000:01:00.0: gr: TRAP ch 3 [007fb0a000 gst-plugin-scan[4939]]
mars 18 11:13:39 a kernel: nouveau 0000:01:00.0: gr: GPC0/PROP trap: 00000020 [RT_HEIGHT_OVERRUN] x = 48, y = 16, format = 37, storage type = 0
mars 18 11:13:39 a kernel: nouveau 0000:01:00.0: gr: TRAP ch 3 [007fb0a000 gst-plugin-scan[4939]]
mars 18 11:13:39 a kernel: nouveau 0000:01:00.0: gr: GPC0/PROP trap: 00000020 [RT_HEIGHT_OVERRUN] x = 48, y = 16, format = 37, storage type = 0
mars 18 11:13:39 a kernel: nouveau 0000:01:00.0: gr: TRAP ch 3 [007fb0a000 gst-plugin-scan[4939]]
mars 18 11:13:39 a kernel: nouveau 0000:01:00.0: gr: GPC0/PROP trap: 00000020 [RT_HEIGHT_OVERRUN] x = 48, y = 16, format = 37, storage type = 0sudo apt update
Atteint : 1 http://security.ubuntu.com/ubuntu resolute-security InRelease
Atteint : 2 http://archive.ubuntu.com/ubuntu resolute InRelease
Atteint : 3 http://archive.ubuntu.com/ubuntu resolute-updates InRelease
Atteint : 4 http://archive.ubuntu.com/ubuntu resolute-backports InRelease
Tous les paquets sont à jour.Les grilles de l'installateur https://doc.ubuntu-fr.org/tutoriel/inst … _subiquity
Les partitions EXT4 des disques externes => https://forum.ubuntu-fr.org/viewtopic.p … #p22697248
Hors ligne