[Touch-packages] [Bug 2008638] Re: apport-gtk crashed with urllib.error.HTTPError in http_error_default(): HTTP Error 502: Bad Gateway
Hello I work with UBUNTU 22.04.2 LTS and when i want to report a bug with ubuntu-bug the connection is not possible. NETWORK PROBLEM Cannot connect to crash database, please check your Internet connection. HTTP error 502: Bad Gateway But i can connect me to bugs.launchpad.net and post to this message. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/2008638 Title: apport-gtk crashed with urllib.error.HTTPError in http_error_default(): HTTP Error 502: Bad Gateway Status in Apport: Fix Committed Status in apport package in Ubuntu: Confirmed Bug description: Had a Nautlius crash prior to this error. ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: apport-gtk 2.26.0-0ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CrashReports: 640:1201:124:38512857:2023-02-24 12:17:00.435185909 -0500:2023-02-24 12:17:01.435185909 -0500:/var/crash/_usr_bin_gnome-shell.1201.crash 640:1000:1000:90509:2023-02-26 10:18:25.277171373 -0500:2023-02-26 10:18:26.277171373 -0500:/var/crash/_usr_share_apport_apport-gtk.1000.crash 600:116:124:37:2023-02-26 10:18:21.948992294 -0500:2023-02-18 17:59:57.688578533 -0500:/var/crash/_usr_bin_nautilus.1000.uploaded 640:1000:124:14955989:2023-02-26 10:16:50.213119506 -0500:2023-02-26 10:17:03.637664041 -0500:/var/crash/_usr_bin_nautilus.1000.crash 664:1000:1000:0:2023-02-26 10:17:03.617663168 -0500:2023-02-26 10:17:03.617663168 -0500:/var/crash/_usr_bin_nautilus.1000.upload CurrentDesktop: ubuntu:GNOME Date: Sun Feb 26 10:18:26 2023 ExecutablePath: /usr/share/apport/apport-gtk InstallationDate: Installed on 2023-02-13 (12 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221209) InterpreterPath: /usr/bin/python3.11 JournalErrors: Feb 26 10:18:26 hostname systemd[2030]: update-notifier-crash.service: Failed with result 'exit-code'. Feb 26 10:18:26 hostname systemd[2030]: Failed to start Notification regarding a crash report. PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gtk ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= Python3Details: /usr/bin/python3.11, Python 3.11.1, python3-minimal, 3.11.1-3 PythonArgs: ['/usr/share/apport/apport-gtk'] PythonDetails: N/A SourcePackage: apport Title: apport-gtk crashed with urllib.error.HTTPError in http_error_default(): HTTP Error 502: Bad Gateway UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/2008638/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2000625] Re: cp command loop when using ntfs3 package
Sorry This bug ins not in the good sectionIt is now https://bugs.launchpad.net/ubuntu/+source/evince/+bug/2000626 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu. https://bugs.launchpad.net/bugs/2000625 Title: cp command loop when using ntfs3 package Status in e2fsprogs package in Ubuntu: New Bug description: Hello. I'm on ubuntu 22.04, I saw that ntfs3 is supposed to correctly write to an NTFS partition. I inform you that this is not the case. Here is my quick test First try on EFI computer: I remove the NTFS-3G package to be sure not to use it. When I detect that the cp command is no longer responding, I kill the process. Nothing is happening. I shut down the computer. During the shutdown phase, I am informed twice that the cp command is running. On reboot, I cannot access the partition. But I succeed in read-only mode. I run another normal ubuntu which tells me that I have to use windows to do an chkdsk But windows refuse to start, I duplicate by the dd command the NTFS partition in a larger NTFS partition stored in an external disk. Then I delete the NTFS partition from the internal disk. Then I repare windows. After restarting windows, I find that its disk space manager cannot access to the duplicate partition on external disk. There's no answer. So no letter to do the CHKDSK command. I decide to be more methodical in order to open a discussion and make a script to see a little what is happening. See the rest. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/2000625/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2000625] Re: cp command loop when using ntfs3 package
Second try on LEGACY computer: I make a script based on cp command. I try it on a normal NTFS partition in NTFS-3G. It ends perfectly well. I restart it on the same partition mounted in NTF3 He blocks. I make on another disk two partitions of identical size. I launch on one. It hangs almost in the same place. I launch on the other. It hangs in exactly the same place. This makes me open the bug. I can provide you with some information. First disque root@b:~# Na=0 Nb=25 time for (( I=$Na; I < $Nb; I++ )); do for (( J=$Na; J < $Nb; J++ )); do for (( K=$Na; K < $Nb; K++ )); do echo -n -e avancement $I $J $K "\r \a"; for (( L=$Na; L < $Nb; L++ )); do mkdir -p $Rep/$I/$J/$K/$L ; for (( M=$Na; M < $Nb; M++ )); do cp FIC $Rep/$I/$J/$K/$L/$M; done; done; done; done; done avancement 14 3 18 Second disk root@b:~# mount -v -t ntfs3 /dev/sdd10 /$Rep mount: /media/root/TestNTFS1: /dev/sdd10 déjà monté sur /media/root/TestNTFS1. root@b:~# root@b:~# Na=0 Nb=25 time for (( I=$Na; I < $Nb; I++ )); do for (( J=$Na; J < $Nb; J++ )); do for (( K=$Na; K < $Nb; K++ )); do echo -n -e avancement $I $J $K "\r \a"; for (( L=$Na; L < $Nb; L++ )); do mkdir -p $Rep/$I/$J/$K/$L ; for (( M=$Na; M < $Nb; M++ )); do cp FIC $Rep/$I/$J/$K/$L/$M; done; done; done; done; done avancement 15 3 10 root@b:~# root@b:~# dd if=/dev/zero of=FIC count=1 bs=1K Rep=/media/root/TestNTFS2 mkdir $Rep mount -v -t ntfs3 /dev/sdd11 /$Rep Na=0 Nb=25 1+0 enregistrements lus 1+0 enregistrements écrits 1024 octets (1,0 kB, 1,0 KiB) copiés, 0,000783991 s, 1,3 MB/s mount : /dev/sdd11 monté sur /media/root/TestNTFS2. root@b:~# root@b:~# time for (( I=$Na; I < $Nb; I++ )); do for (( J=$Na; J < $Nb; J++ )); do for (( K=$Na; K < $Nb; K++ )); do echo -n -e avancement $I $J $K "\r \a"; for (( L=$Na; L < $Nb; L++ )); do mkdir -p $Rep/$I/$J/$K/$L ; for (( M=$Na; M < $Nb; M++ )); do cp FIC $Rep/$I/$J/$K/$L/$M; done; done; done; done; done avancement 15 3 10 Stats by df command a@b:~$ sudo df -ah |egrep "Taille|root" Sys. de fichiers Taille Utilisé Dispo Uti% Monté sur /dev/sdb6 99G 28G 71G 29% /media/root/TestNTFS /dev/sdd10 60G 30G 31G 50% /media/root/TestNTFS1 /dev/sdd11 60G 30G 31G 50% /media/root/TestNTFS2 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu. https://bugs.launchpad.net/bugs/2000625 Title: cp command loop when using ntfs3 package Status in e2fsprogs package in Ubuntu: New Bug description: Hello. I'm on ubuntu 22.04, I saw that ntfs3 is supposed to correctly write to an NTFS partition. I inform you that this is not the case. Here is my quick test First try on EFI computer: I remove the NTFS-3G package to be sure not to use it. When I detect that the cp command is no longer responding, I kill the process. Nothing is happening. I shut down the computer. During the shutdown phase, I am informed twice that the cp command is running. On reboot, I cannot access the partition. But I succeed in read-only mode. I run another normal ubuntu which tells me that I have to use windows to do an chkdsk But windows refuse to start, I duplicate by the dd command the NTFS partition in a larger NTFS partition stored in an external disk. Then I delete the NTFS partition from the internal disk. Then I repare windows. After restarting windows, I find that its disk space manager cannot access to the duplicate partition on external disk. There's no answer. So no letter to do the CHKDSK command. I decide to be more methodical in order to open a discussion and make a script to see a little what is happening. See the rest. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/2000625/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2000625] [NEW] cp command loop when using ntfs3 package
Public bug reported: Hello. I'm on ubuntu 22.04, I saw that ntfs3 is supposed to correctly write to an NTFS partition. I inform you that this is not the case. Here is my quick test First try on EFI computer: I remove the NTFS-3G package to be sure not to use it. When I detect that the cp command is no longer responding, I kill the process. Nothing is happening. I shut down the computer. During the shutdown phase, I am informed twice that the cp command is running. On reboot, I cannot access the partition. But I succeed in read-only mode. I run another normal ubuntu which tells me that I have to use windows to do an chkdsk But windows refuse to start, I duplicate by the dd command the NTFS partition in a larger NTFS partition stored in an external disk. Then I delete the NTFS partition from the internal disk. Then I repare windows. After restarting windows, I find that its disk space manager cannot access to the duplicate partition on external disk. There's no answer. So no letter to do the CHKDSK command. I decide to be more methodical in order to open a discussion and make a script to see a little what is happening. See the rest. ** Affects: e2fsprogs (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu. https://bugs.launchpad.net/bugs/2000625 Title: cp command loop when using ntfs3 package Status in e2fsprogs package in Ubuntu: New Bug description: Hello. I'm on ubuntu 22.04, I saw that ntfs3 is supposed to correctly write to an NTFS partition. I inform you that this is not the case. Here is my quick test First try on EFI computer: I remove the NTFS-3G package to be sure not to use it. When I detect that the cp command is no longer responding, I kill the process. Nothing is happening. I shut down the computer. During the shutdown phase, I am informed twice that the cp command is running. On reboot, I cannot access the partition. But I succeed in read-only mode. I run another normal ubuntu which tells me that I have to use windows to do an chkdsk But windows refuse to start, I duplicate by the dd command the NTFS partition in a larger NTFS partition stored in an external disk. Then I delete the NTFS partition from the internal disk. Then I repare windows. After restarting windows, I find that its disk space manager cannot access to the duplicate partition on external disk. There's no answer. So no letter to do the CHKDSK command. I decide to be more methodical in order to open a discussion and make a script to see a little what is happening. See the rest. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/2000625/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1972099] [NEW] computer startup crashes when NFS partition is inaccessible
Public bug reported: Hello. When the NFS partition described in the /etc/fstab file is not accessible (The server is down) starting the computer in version 22.04 is impossible. Message: "you are in emergency mode. After logging, type "journal -xb to view system log This was not the case in previous versions. The computer waited 90 seconds and booted without the NFS partition. I tried adding the nofail or nobootwait options but it didn't work. The line is coded this way: 192.168.0.31:/media/MyDatas /media/NFS defaults,user,auto,_netdev,bg What is the correct solution? Thank you for your reply ** Affects: util-linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1972099 Title: computer startup crashes when NFS partition is inaccessible Status in util-linux package in Ubuntu: New Bug description: Hello. When the NFS partition described in the /etc/fstab file is not accessible (The server is down) starting the computer in version 22.04 is impossible. Message: "you are in emergency mode. After logging, type "journal -xb to view system log This was not the case in previous versions. The computer waited 90 seconds and booted without the NFS partition. I tried adding the nofail or nobootwait options but it didn't work. The line is coded this way: 192.168.0.31:/media/MyDatas /media/NFS defaults,user,auto,_netdev,bg What is the correct solution? Thank you for your reply To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1972099/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1962409] Re: ZFS: The content of the /etc/crypttab file is bad
Hello Same problem withe beta jammy. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1962409 Title: ZFS: The content of the /etc/crypttab file is bad Status in systemd package in Ubuntu: New Bug description: Hello I just installed the zfs 22.04 encrypted version on an external drive. When I launch the installed software, there is a loss of time of 90 seconds looking for the partition containing the swap. Would it be possible to replace the device name with a UUID name in the /etc/crypttab? Indeed at the time of installation the disk is SDC but it becomes SDA or SDB during startup... cat /etc/crypttab cryptoswap/dev/sdc2 /dev/urandomswap,initramfs blkid | grep LUKS /dev/sda2: UUID="6897cf48-5e28-4163-9de5-056b1385063c" TYPE="crypto_LUKS" PARTUUID="a8a79383-adb6-eb4c-95b6-fd40affd90d0" /dev/zd0: UUID="e516377f-ee45-46e2-a3b0-03869113269a" TYPE="crypto_LUKS" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1962409/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1962409] Re: ZFS: The content of the /etc/crypttab file is bad
Hello Same problem with this version jammy-desktop-amd64.iso 2022-03-21 08:38 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1962409 Title: ZFS: The content of the /etc/crypttab file is bad Status in systemd package in Ubuntu: New Bug description: Hello I just installed the zfs 22.04 encrypted version on an external drive. When I launch the installed software, there is a loss of time of 90 seconds looking for the partition containing the swap. Would it be possible to replace the device name with a UUID name in the /etc/crypttab? Indeed at the time of installation the disk is SDC but it becomes SDA or SDB during startup... cat /etc/crypttab cryptoswap/dev/sdc2 /dev/urandomswap,initramfs blkid | grep LUKS /dev/sda2: UUID="6897cf48-5e28-4163-9de5-056b1385063c" TYPE="crypto_LUKS" PARTUUID="a8a79383-adb6-eb4c-95b6-fd40affd90d0" /dev/zd0: UUID="e516377f-ee45-46e2-a3b0-03869113269a" TYPE="crypto_LUKS" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1962409/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1962061] Re: ZFS Key load error: Failed to open key material file: No such file or directory
Hello This version is now good. jammy-desktop-amd64.iso 2022-03-21 08:38 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1962061 Title: ZFS Key load error: Failed to open key material file: No such file or directory Status in systemd package in Ubuntu: New Bug description: Hello The message is Key load error: Failed to open key material file: No such file or directory Command: mount -o zfsutil -t zfs rpool/ROOT/ubuntu_ui69ph /root// Message: filesystem 'rpool/ROOT/ubuntu_ui69ph' can not be mounted: Permission denied filesystem 'rpool/ROOT/ubuntu_ui69ph' can not be mounted: Permission denied Hello I recently installed an encrypted ZFS 22.04 version. She boots well. I can do the updates and reboot except that now the reboot is impossible because of the message above. I suspect that access to the encryption keys has become impossible. The reason could be a borrowing of these keys by another O.S. with poor quality playback. For example forget to free the key file because the incident is systematic have a good day To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1962061/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1962387] Re: EFI is not on the drive
Hello Same problem with this version jammy-desktop-amd64.iso 2022-03-21 08:38 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1962387 Title: EFI is not on the drive Status in systemd package in Ubuntu: New Bug description: Hello I just installed the latest release jammy made on Feb 26 in an ZFS external hard drive. I would have liked the part of BOOT EFI to also go to the external hard drive and not to the internal hard drive. It is true that it is an error which certainly dates from the creation of the EFI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1962387/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1960083] Re: dirname applet missing from initramfs
Hello This version is goodjammy-desktop-amd64.iso 2022-03-21 08:38 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to busybox in Ubuntu. https://bugs.launchpad.net/bugs/1960083 Title: dirname applet missing from initramfs Status in busybox package in Ubuntu: Fix Released Status in zfs-linux package in Ubuntu: Fix Released Bug description: The initramfs is currently being built without the dirname applet. This is causing issues with zfs encrypted devices, as cryptsetup is attempting to use dirname to determine the location of the system key. This results in the following error: /init: line 971: dirname: not found followed by a prompt that is missing the zpool name. For example "Please unlock disk keystore-" rather than "Please unlock disk keystore-rpool". After entering the password, the user is dropped to an initramfs shell. It appears that this was caused by a change in cryptsetup to suddenly need dirname to function properly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/1960083/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1961055] Re: Key load error: Failed to open key material file: No such file or directory
Hello This version in now goodjammy-desktop-amd64.iso 2022-03-21 08:38 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1961055 Title: Key load error: Failed to open key material file: No such file or directory Status in systemd package in Ubuntu: New Bug description: Hello This morning I downloaded the UBUNTU JAMMY version which had just been made an hour earlier. I installed it asking for encryption. When I boot, the password is asked. He is accepted. But root mount is denied. ... find: /dev/zvol: No such file or directory key load error: Failed to open key matéral file No such file or directory Message filesystem rpool/ROOT/ubuntu_trj428 canot be mounted: permission denied Picture is here https://zupimages.net/viewer.php?id=22/07/v372.jpg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1961055/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1962409] Re: ZFS: The content of the /etc/crypttab file is bad
** Description changed: Hello I just installed the zfs 22.04 encrypted version on an external drive. When I launch the installed software, there is a loss of time of 90 seconds looking for the partition containing the swap. Would it be possible to replace the device name with a UUID name in the /etc/crypttab? - Indeed at the time of installation the disk is SDC but it becomes SDA during startup... - + Indeed at the time of installation the disk is SDC but it becomes SDA or SDB during startup... + cat /etc/crypttab cryptoswap/dev/sdc2 /dev/urandomswap,initramfs blkid | grep LUKS /dev/sda2: UUID="6897cf48-5e28-4163-9de5-056b1385063c" TYPE="crypto_LUKS" PARTUUID="a8a79383-adb6-eb4c-95b6-fd40affd90d0" /dev/zd0: UUID="e516377f-ee45-46e2-a3b0-03869113269a" TYPE="crypto_LUKS" -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1962409 Title: ZFS: The content of the /etc/crypttab file is bad Status in systemd package in Ubuntu: New Bug description: Hello I just installed the zfs 22.04 encrypted version on an external drive. When I launch the installed software, there is a loss of time of 90 seconds looking for the partition containing the swap. Would it be possible to replace the device name with a UUID name in the /etc/crypttab? Indeed at the time of installation the disk is SDC but it becomes SDA or SDB during startup... cat /etc/crypttab cryptoswap/dev/sdc2 /dev/urandomswap,initramfs blkid | grep LUKS /dev/sda2: UUID="6897cf48-5e28-4163-9de5-056b1385063c" TYPE="crypto_LUKS" PARTUUID="a8a79383-adb6-eb4c-95b6-fd40affd90d0" /dev/zd0: UUID="e516377f-ee45-46e2-a3b0-03869113269a" TYPE="crypto_LUKS" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1962409/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1962409] [NEW] ZFS: The content of the /etc/crypttab file is bad
Public bug reported: Hello I just installed the zfs 22.04 encrypted version on an external drive. When I launch the installed software, there is a loss of time of 90 seconds looking for the partition containing the swap. Would it be possible to replace the device name with a UUID name in the /etc/crypttab? Indeed at the time of installation the disk is SDC but it becomes SDA during startup... cat /etc/crypttab cryptoswap /dev/sdc2 /dev/urandomswap,initramfs blkid | grep LUKS /dev/sda2: UUID="6897cf48-5e28-4163-9de5-056b1385063c" TYPE="crypto_LUKS" PARTUUID="a8a79383-adb6-eb4c-95b6-fd40affd90d0" /dev/zd0: UUID="e516377f-ee45-46e2-a3b0-03869113269a" TYPE="crypto_LUKS" ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1962409 Title: ZFS: The content of the /etc/crypttab file is bad Status in systemd package in Ubuntu: New Bug description: Hello I just installed the zfs 22.04 encrypted version on an external drive. When I launch the installed software, there is a loss of time of 90 seconds looking for the partition containing the swap. Would it be possible to replace the device name with a UUID name in the /etc/crypttab? Indeed at the time of installation the disk is SDC but it becomes SDA during startup... cat /etc/crypttab cryptoswap/dev/sdc2 /dev/urandomswap,initramfs blkid | grep LUKS /dev/sda2: UUID="6897cf48-5e28-4163-9de5-056b1385063c" TYPE="crypto_LUKS" PARTUUID="a8a79383-adb6-eb4c-95b6-fd40affd90d0" /dev/zd0: UUID="e516377f-ee45-46e2-a3b0-03869113269a" TYPE="crypto_LUKS" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1962409/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1962061] Re: ZFS Key load error: Failed to open key material file: No such file or directory
Hello SOLVED with new Daily jammy-desktop-amd64.iso 2022-02-26 08:21 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1962061 Title: ZFS Key load error: Failed to open key material file: No such file or directory Status in systemd package in Ubuntu: New Bug description: Hello The message is Key load error: Failed to open key material file: No such file or directory Command: mount -o zfsutil -t zfs rpool/ROOT/ubuntu_ui69ph /root// Message: filesystem 'rpool/ROOT/ubuntu_ui69ph' can not be mounted: Permission denied filesystem 'rpool/ROOT/ubuntu_ui69ph' can not be mounted: Permission denied Hello I recently installed an encrypted ZFS 22.04 version. She boots well. I can do the updates and reboot except that now the reboot is impossible because of the message above. I suspect that access to the encryption keys has become impossible. The reason could be a borrowing of these keys by another O.S. with poor quality playback. For example forget to free the key file because the incident is systematic have a good day To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1962061/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1962387] [NEW] EFI is not on the drive
Public bug reported: Hello I just installed the latest release jammy made on Feb 26 in an ZFS external hard drive. I would have liked the part of BOOT EFI to also go to the external hard drive and not to the internal hard drive. It is true that it is an error which certainly dates from the creation of the EFI ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Attachment added: "some commands" https://bugs.launchpad.net/bugs/1962387/+attachment/5563988/+files/EFI.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1962387 Title: EFI is not on the drive Status in systemd package in Ubuntu: New Bug description: Hello I just installed the latest release jammy made on Feb 26 in an ZFS external hard drive. I would have liked the part of BOOT EFI to also go to the external hard drive and not to the internal hard drive. It is true that it is an error which certainly dates from the creation of the EFI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1962387/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1962061] Re: ZFS Key load error: Failed to open key material file: No such file or directory
The little script that makes ZFS booting impossible. sudo -i #1) Montage des partitions contenant le logiciel rmdir /ZFS zpool import -N -R /ZFS rpool && sleep 5 zfs set canmount=on rpool && zfs mount -v rpool for var in $(zfs list | grep ROOT/ubuntu|cut -d" " -f1) do echo $var zfs set canmount=on $var && zfs mount -v $var sleep 1 done #2) On récupère la séquence de boot. Mais c'est celle obtenue en mode recovery et pas la dernière !!! journalctl -b -p err -D /ZFS/var/log/journal >/home/a/boot-ERR.txt journalctl -b-D /ZFS/var/log/journal >/home/a/boot-TOT.txt #3) On démonte le root for var in $(zfs list | tac | grep ROOT/ubuntu|cut -d" " -f1) do echo $var zfs unmount $var && zfs set canmount=off $var && sleep 1 done zfs unmount rpool && zfs set canmount=off rpool && sleep 1 umount -v --recursive /ZFS zpool export rpool zpool list ** Attachment added: "The little script that makes ZFS booting impossible." https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1962061/+attachment/5563870/+files/CHROOTnormal.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1962061 Title: ZFS Key load error: Failed to open key material file: No such file or directory Status in systemd package in Ubuntu: New Bug description: Hello The message is Key load error: Failed to open key material file: No such file or directory Command: mount -o zfsutil -t zfs rpool/ROOT/ubuntu_ui69ph /root// Message: filesystem 'rpool/ROOT/ubuntu_ui69ph' can not be mounted: Permission denied filesystem 'rpool/ROOT/ubuntu_ui69ph' can not be mounted: Permission denied Hello I recently installed an encrypted ZFS 22.04 version. She boots well. I can do the updates and reboot except that now the reboot is impossible because of the message above. I suspect that access to the encryption keys has become impossible. The reason could be a borrowing of these keys by another O.S. with poor quality playback. For example forget to free the key file because the incident is systematic have a good day To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1962061/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1962061] Re: ZFS Key load error: Failed to open key material file: No such file or directory
The little script that makes ZFS booting impossible. ** Attachment added: "The little script that makes ZFS booting impossible." https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1962061/+attachment/5563869/+files/CHROOTchiffr%C3%A9.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1962061 Title: ZFS Key load error: Failed to open key material file: No such file or directory Status in systemd package in Ubuntu: New Bug description: Hello The message is Key load error: Failed to open key material file: No such file or directory Command: mount -o zfsutil -t zfs rpool/ROOT/ubuntu_ui69ph /root// Message: filesystem 'rpool/ROOT/ubuntu_ui69ph' can not be mounted: Permission denied filesystem 'rpool/ROOT/ubuntu_ui69ph' can not be mounted: Permission denied Hello I recently installed an encrypted ZFS 22.04 version. She boots well. I can do the updates and reboot except that now the reboot is impossible because of the message above. I suspect that access to the encryption keys has become impossible. The reason could be a borrowing of these keys by another O.S. with poor quality playback. For example forget to free the key file because the incident is systematic have a good day To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1962061/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1962061] Re: ZFS Key load error: Failed to open key material file: No such file or directory
Hello. To advance this problem, I decided to redo a brand new installation without using encryption. I can also boot several times without any difficulty. With another O.S. in version 22.04 installed in an EXT4 partition, I launched the script to access this ZFS partition. The problem is reproduced in a simpler way. The boot does not finish despite waiting about an hour. I took a screenshot which I am attaching. I know the problem is systematic. Using the quoted script, I can access the log. But I see that the log has not yet been created. I am only allowed to boot into recovery mode. It's a little better. The boot hangs less I am attaching the errors encountered and the entire trace of the log. All this is obtained by the aforementioned script. I'm willing to admit that my script isn't up to snuff. however this should absolutely not prevent ZFS from booting. I don't know whether to do another bug report or if it can stay in this one. Good research and good editing. ** Attachment added: "photograph of unencrypted ZFS boot hang" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1962061/+attachment/5563868/+files/boot.JPG -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1962061 Title: ZFS Key load error: Failed to open key material file: No such file or directory Status in systemd package in Ubuntu: New Bug description: Hello The message is Key load error: Failed to open key material file: No such file or directory Command: mount -o zfsutil -t zfs rpool/ROOT/ubuntu_ui69ph /root// Message: filesystem 'rpool/ROOT/ubuntu_ui69ph' can not be mounted: Permission denied filesystem 'rpool/ROOT/ubuntu_ui69ph' can not be mounted: Permission denied Hello I recently installed an encrypted ZFS 22.04 version. She boots well. I can do the updates and reboot except that now the reboot is impossible because of the message above. I suspect that access to the encryption keys has become impossible. The reason could be a borrowing of these keys by another O.S. with poor quality playback. For example forget to free the key file because the incident is systematic have a good day To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1962061/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1962061] Re: ZFS Key load error: Failed to open key material file: No such file or directory
Helle Hello Here is the access sequence to the encrypted partition from another O.S. zpool import -N -R /ZFS rpool && sleep 10 if [ -e /dev/zvol/rpool/keystore ] ; then cryptsetup -v open /dev/zvol/rpool/keystore keystore-rpool && sleep 10 mkdir -p /run/keystore/rpool mount -v /dev/mapper/keystore-rpool /run/keystore/rpool && sleep 10 fi Here is an encrypted partition release sequence from another O.S. which prevents the boot of the encrypted partition shutdown or crash of O.S. Another zpool export rpool && shutdown Antoher umount -v /run/keystore/rpool && sleep 5 cryptsetup -v close /dev/mapper/keystore-rpool && sleep 5 zpool export rpool shutdown Here is the correct sequence of freeing encrypted partition from another O.S. which allows the boot of the encrypted partition. But first you have to go through the recovery option. There's probably a better solution. umount -v /run/keystore/rpool && sleep 5 cryptsetup -v luksClose /dev/mapper/keystore-rpool && sleep 5 zpool export rpool && zpool list shutdown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1962061 Title: ZFS Key load error: Failed to open key material file: No such file or directory Status in systemd package in Ubuntu: New Bug description: Hello The message is Key load error: Failed to open key material file: No such file or directory Command: mount -o zfsutil -t zfs rpool/ROOT/ubuntu_ui69ph /root// Message: filesystem 'rpool/ROOT/ubuntu_ui69ph' can not be mounted: Permission denied filesystem 'rpool/ROOT/ubuntu_ui69ph' can not be mounted: Permission denied Hello I recently installed an encrypted ZFS 22.04 version. She boots well. I can do the updates and reboot except that now the reboot is impossible because of the message above. I suspect that access to the encryption keys has become impossible. The reason could be a borrowing of these keys by another O.S. with poor quality playback. For example forget to free the key file because the incident is systematic have a good day To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1962061/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1962061] [NEW] ZFS Key load error: Failed to open key material file: No such file or directory
Public bug reported: Hello The message is Key load error: Failed to open key material file: No such file or directory Command: mount -o zfsutil -t zfs rpool/ROOT/ubuntu_ui69ph /root// Message: filesystem 'rpool/ROOT/ubuntu_ui69ph' can not be mounted: Permission denied filesystem 'rpool/ROOT/ubuntu_ui69ph' can not be mounted: Permission denied Hello I recently installed an encrypted ZFS 22.04 version. She boots well. I can do the updates and reboot except that now the reboot is impossible because of the message above. I suspect that access to the encryption keys has become impossible. The reason could be a borrowing of these keys by another O.S. with poor quality playback. For example forget to free the key file because the incident is systematic have a good day ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1962061 Title: ZFS Key load error: Failed to open key material file: No such file or directory Status in systemd package in Ubuntu: New Bug description: Hello The message is Key load error: Failed to open key material file: No such file or directory Command: mount -o zfsutil -t zfs rpool/ROOT/ubuntu_ui69ph /root// Message: filesystem 'rpool/ROOT/ubuntu_ui69ph' can not be mounted: Permission denied filesystem 'rpool/ROOT/ubuntu_ui69ph' can not be mounted: Permission denied Hello I recently installed an encrypted ZFS 22.04 version. She boots well. I can do the updates and reboot except that now the reboot is impossible because of the message above. I suspect that access to the encryption keys has become impossible. The reason could be a borrowing of these keys by another O.S. with poor quality playback. For example forget to free the key file because the incident is systematic have a good day To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1962061/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1961055] Re: Key load error: Failed to open key material file: No such file or directory
Hello I worked around the problem by removing the words quiet splash from the entry menus of the /boot/grub/grub.cfg file so that I could enter the password. But the swap partition is not mounted. Probably because is name is now SDA2 and not SDC2 which was the name during installation on a external drive. sudo blkid | grep sda2 /dev/sda2: UUID="99ce927e-67ae-4e9a-93f1-ac637af7f34f" TYPE="crypto_LUKS" PARTUUID="caada0e6-030f-5143-93f8-8534629af79c" a@a:~$ df -h Sys. de fichiers Taille Utilisé Dispo Uti% Monté sur tmpfs 583M2,1M 581M 1% /run /dev/mapper/keystore-rpool 437M 28K 404M 1% /run/keystore/rpool rpool/ROOT/ubuntu_trj428 444G3,1G 441G 1% / tmpfs 2,9G3,3M 2,9G 1% /dev/shm tmpfs 5,0M4,0K 5,0M 1% /run/lock rpool/USERDATA/root_77w87m 441G384K 441G 1% /root rpool/ROOT/ubuntu_trj428/var/mail 441G256K 441G 1% /var/mail rpool/ROOT/ubuntu_trj428/var/snap 441G1,9M 441G 1% /var/snap rpool/ROOT/ubuntu_trj428/var/www 441G256K 441G 1% /var/www rpool/ROOT/ubuntu_trj428/srv 441G256K 441G 1% /srv rpool/USERDATA/a_77w87m441G102M 441G 1% /home/a rpool/ROOT/ubuntu_trj428/var/spool 441G384K 441G 1% /var/spool rpool/ROOT/ubuntu_trj428/var/games 441G256K 441G 1% /var/games rpool/ROOT/ubuntu_trj428/usr/local 441G512K 441G 1% /usr/local rpool/ROOT/ubuntu_trj428/var/lib 442G1,3G 441G 1% /var/lib rpool/ROOT/ubuntu_trj428/var/lib/AccountsService 441G256K 441G 1% /var/lib/AccountsService rpool/ROOT/ubuntu_trj428/var/lib/NetworkManager441G256K 441G 1% /var/lib/NetworkManager rpool/ROOT/ubuntu_trj428/var/lib/apt 441G 96M 441G 1% /var/lib/apt rpool/ROOT/ubuntu_trj428/var/lib/dpkg 441G 51M 441G 1% /var/lib/dpkg rpool/ROOT/ubuntu_trj428/var/log 441G3,2M 441G 1% /var/log bpool/BOOT/ubuntu_trj428 1,8G 85M 1,7G 5% /boot /dev/sdb1 98M 32M 67M 32% /boot/efi tmpfs 583M 11M 573M 2% /run/user/1000 note The goog name seems /run/keystore/rpool journalctl -b -p err févr. 17 00:33:23 a systemd[1]: Timed out waiting for device /dev/sdc2 . -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1961055 Title: Key load error: Failed to open key material file: No such file or directory Status in systemd package in Ubuntu: New Bug description: Hello This morning I downloaded the UBUNTU JAMMY version which had just been made an hour earlier. I installed it asking for encryption. When I boot, the password is asked. He is accepted. But root mount is denied. ... find: /dev/zvol: No such file or directory key load error: Failed to open key matéral file No such file or directory Message filesystem rpool/ROOT/ubuntu_trj428 canot be mounted: permission denied Picture is here https://zupimages.net/viewer.php?id=22/07/v372.jpg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1961055/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1961055] Re: Key load error: Failed to open key material file: No such file or directory
** Description changed: Hello This morning I downloaded the UBUNTU JAMMY version which had just been made an hour earlier. I installed it asking for encryption. When I boot, the password is asked. He is accepted. But root mount is denied. ... find: /dev/zvol: No such file or directory key load error: Failed to open key matéral file No such file or directory Message filesystem rpool/ROOT/ubuntu_trj428 canot be mounted: permission denied - - Picture will come + Picture is here https://zupimages.net/viewer.php?id=22/07/v372.jpg -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1961055 Title: Key load error: Failed to open key material file: No such file or directory Status in systemd package in Ubuntu: New Bug description: Hello This morning I downloaded the UBUNTU JAMMY version which had just been made an hour earlier. I installed it asking for encryption. When I boot, the password is asked. He is accepted. But root mount is denied. ... find: /dev/zvol: No such file or directory key load error: Failed to open key matéral file No such file or directory Message filesystem rpool/ROOT/ubuntu_trj428 canot be mounted: permission denied Picture is here https://zupimages.net/viewer.php?id=22/07/v372.jpg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1961055/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1961055] [NEW] Key load error: Failed to open key material file: No such file or directory
Public bug reported: Hello This morning I downloaded the UBUNTU JAMMY version which had just been made an hour earlier. I installed it asking for encryption. When I boot, the password is asked. He is accepted. But root mount is denied. ... find: /dev/zvol: No such file or directory key load error: Failed to open key matéral file No such file or directory Message filesystem rpool/ROOT/ubuntu_trj428 canot be mounted: permission denied Picture will come ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1961055 Title: Key load error: Failed to open key material file: No such file or directory Status in systemd package in Ubuntu: New Bug description: Hello This morning I downloaded the UBUNTU JAMMY version which had just been made an hour earlier. I installed it asking for encryption. When I boot, the password is asked. He is accepted. But root mount is denied. ... find: /dev/zvol: No such file or directory key load error: Failed to open key matéral file No such file or directory Message filesystem rpool/ROOT/ubuntu_trj428 canot be mounted: permission denied Picture will come To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1961055/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1960083] Re: dirname applet missing from initramfs
Hello Oh!!! jammy-desktop-amd64.iso 2022-02-16 08:353.1GDesktop image for 64-bit PC (AMD64) computers (standard download) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to busybox in Ubuntu. https://bugs.launchpad.net/bugs/1960083 Title: dirname applet missing from initramfs Status in busybox package in Ubuntu: Fix Released Status in zfs-linux package in Ubuntu: Confirmed Bug description: The initramfs is currently being built without the dirname applet. This is causing issues with zfs encrypted devices, as cryptsetup is attempting to use dirname to determine the location of the system key. This results in the following error: /init: line 971: dirname: not found followed by a prompt that is missing the zpool name. For example "Please unlock disk keystore-" rather than "Please unlock disk keystore-rpool". After entering the password, the user is dropped to an initramfs shell. It appears that this was caused by a change in cryptsetup to suddenly need dirname to function properly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/1960083/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1960083] Re: dirname applet missing from initramfs
I just downloaded the iso today, then I redid an installation But it's still the version minus one I don't know how to update the ISO I just downloaded before installing it -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to busybox in Ubuntu. https://bugs.launchpad.net/bugs/1960083 Title: dirname applet missing from initramfs Status in busybox package in Ubuntu: Fix Released Status in zfs-linux package in Ubuntu: Confirmed Bug description: The initramfs is currently being built without the dirname applet. This is causing issues with zfs encrypted devices, as cryptsetup is attempting to use dirname to determine the location of the system key. This results in the following error: /init: line 971: dirname: not found followed by a prompt that is missing the zpool name. For example "Please unlock disk keystore-" rather than "Please unlock disk keystore-rpool". After entering the password, the user is dropped to an initramfs shell. It appears that this was caused by a change in cryptsetup to suddenly need dirname to function properly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/1960083/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1960083] Re: dirname applet missing from initramfs
Hello Are you sure? https://zupimages.net/viewer.php?id=22/07/fxcb.jpg -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to busybox in Ubuntu. https://bugs.launchpad.net/bugs/1960083 Title: dirname applet missing from initramfs Status in busybox package in Ubuntu: Fix Released Status in zfs-linux package in Ubuntu: Confirmed Bug description: The initramfs is currently being built without the dirname applet. This is causing issues with zfs encrypted devices, as cryptsetup is attempting to use dirname to determine the location of the system key. This results in the following error: /init: line 971: dirname: not found followed by a prompt that is missing the zpool name. For example "Please unlock disk keystore-" rather than "Please unlock disk keystore-rpool". After entering the password, the user is dropped to an initramfs shell. It appears that this was caused by a change in cryptsetup to suddenly need dirname to function properly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/1960083/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1939238] Re: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
hello a completely lost user => https://forum.ubuntu-fr.org/viewtopic.php?id=2066473 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu. https://bugs.launchpad.net/bugs/1939238 Title: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY. Status in e2fsprogs package in Ubuntu: New Bug description: Hello This problem did not occur on my computer. https://nsa40.casimages.com/img/2021/08/07/210807015400327092.png It occurs in users who are not competent. This week, the French forum collapsed over this incident. I think changing the advice phrase might improve understanding of the action to be taken. Can these lines " ( i.e.. without -a or -p options) fsck existed with status code 4 The root file system on /dev/ requires a manual fsck" become "execute this command 'fsck -y /dev/xx' to do a manual fsck on the root file system." ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-terminal 3.38.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Aug 8 15:16:28 2021 ExecutablePath: /usr/libexec/gnome-terminal-server InstallationDate: Installed on 2020-08-02 (370 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: gnome-terminal UpgradeStatus: Upgraded to hirsute on 2021-07-11 (27 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1939238/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1939238] Re: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
Hello I still say that the action proposed by these lines " dev/XXX: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY ( i.e.. without -a or -p options) fsck existed with status code 4 The root file system on /dev/ requires a manual fsck" Is not easy to understand. So I suggested a change of presentation that could become this one: "busybox allows you to manually repair the software partition if you hit 'fsck /dev/xx' to its command "(initramfs)". When the repair is complete, type the word 'exit' in order to continue the boot sequence." -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu. https://bugs.launchpad.net/bugs/1939238 Title: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY. Status in e2fsprogs package in Ubuntu: New Bug description: Hello This problem did not occur on my computer. https://nsa40.casimages.com/img/2021/08/07/210807015400327092.png It occurs in users who are not competent. This week, the French forum collapsed over this incident. I think changing the advice phrase might improve understanding of the action to be taken. Can these lines " ( i.e.. without -a or -p options) fsck existed with status code 4 The root file system on /dev/ requires a manual fsck" become "execute this command 'fsck -y /dev/xx' to do a manual fsck on the root file system." ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-terminal 3.38.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Aug 8 15:16:28 2021 ExecutablePath: /usr/libexec/gnome-terminal-server InstallationDate: Installed on 2020-08-02 (370 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: gnome-terminal UpgradeStatus: Upgraded to hirsute on 2021-07-11 (27 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1939238/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1939238] Re: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
Hello "It asks me to do an fsk manually if I read between the lines, and I don't understand what that means or what to do." => https://forum.ubuntu-fr.org/viewtopic.php?pid=22480277#p22480277 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu. https://bugs.launchpad.net/bugs/1939238 Title: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY. Status in e2fsprogs package in Ubuntu: New Bug description: Hello This problem did not occur on my computer. https://nsa40.casimages.com/img/2021/08/07/210807015400327092.png It occurs in users who are not competent. This week, the French forum collapsed over this incident. I think changing the advice phrase might improve understanding of the action to be taken. Can these lines " ( i.e.. without -a or -p options) fsck existed with status code 4 The root file system on /dev/ requires a manual fsck" become "execute this command 'fsck -y /dev/xx' to do a manual fsck on the root file system." ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-terminal 3.38.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Aug 8 15:16:28 2021 ExecutablePath: /usr/libexec/gnome-terminal-server InstallationDate: Installed on 2020-08-02 (370 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: gnome-terminal UpgradeStatus: Upgraded to hirsute on 2021-07-11 (27 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1939238/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1939238] Re: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
Hello Thanks for your answer but 99.999% of basic users are unable to answer repair software English questions other than "YES". However the sentence can become "EXECUTE THIS COMMAND 'fsck /dev/xx' to do a manual fsck on the root file system." If the answer "yes" completely destroys the software, just reinstall it! NOTE: A competent user does not store his personal data in the partition containing the software. He stores them elsewhere! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu. https://bugs.launchpad.net/bugs/1939238 Title: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY. Status in e2fsprogs package in Ubuntu: New Bug description: Hello This problem did not occur on my computer. https://nsa40.casimages.com/img/2021/08/07/210807015400327092.png It occurs in users who are not competent. This week, the French forum collapsed over this incident. I think changing the advice phrase might improve understanding of the action to be taken. Can these lines " ( i.e.. without -a or -p options) fsck existed with status code 4 The root file system on /dev/ requires a manual fsck" become "execute this command 'fsck -y /dev/xx' to do a manual fsck on the root file system." ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-terminal 3.38.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Aug 8 15:16:28 2021 ExecutablePath: /usr/libexec/gnome-terminal-server InstallationDate: Installed on 2020-08-02 (370 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: gnome-terminal UpgradeStatus: Upgraded to hirsute on 2021-07-11 (27 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1939238/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1926624] Re: failed to start commit a transient machine-id on disk
The journal log ** Attachment added: "T" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1926624/+attachment/5493340/+files/T -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1926624 Title: failed to start commit a transient machine-id on disk Status in systemd package in Ubuntu: New Bug description: Hello. I installed the Hirsute Hippo version (21.04) in a partition of a USB stick. The boot is slow. This is certainly normal. But a lot of "time-out" messages are reported in the log. The first one met is "failed to start commit a transient machine-id on disk". I do not know that they will be the consequences. Is it possible to configure the waiting time? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1926624/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1926624] [NEW] failed to start commit a transient machine-id on disk
Public bug reported: Hello. I installed the Hirsute Hippo version (21.04) in a partition of a USB stick. The boot is slow. This is certainly normal. But a lot of "time-out" messages are reported in the log. The first one met is "failed to start commit a transient machine-id on disk". I do not know that they will be the consequences. Is it possible to configure the waiting time? ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1926624 Title: failed to start commit a transient machine-id on disk Status in systemd package in Ubuntu: New Bug description: Hello. I installed the Hirsute Hippo version (21.04) in a partition of a USB stick. The boot is slow. This is certainly normal. But a lot of "time-out" messages are reported in the log. The first one met is "failed to start commit a transient machine-id on disk". I do not know that they will be the consequences. Is it possible to configure the waiting time? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1926624/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1922380] Re: remove shim-signed very difficult
Hello.
I'm confused. When I type the words correctly, it works.
Traitement des actions différées (« triggers ») pour man-db (2.9.4-2) ...
root@a:~# apt purge shim-signed
Lecture des listes de paquets... Fait
Construction de l'arbre des dépendances... Fait
Lecture des informations d'état... Fait
Veuillez utiliser « apt autoremove » pour les supprimer.
Les paquets suivants seront ENLEVÉS :
shim-signed*
ATTENTION : Les paquets essentiels suivants vont être enlevés.
Vous NE devez PAS faire ceci, à moins de savoir exactement ce
que vous êtes en train de faire.
shim-signed
0 mis à jour, 0 nouvellement installés, 1 à enlever et 41 non mis à jour.
Après cette opération, 2 734 ko d'espace disque seront libérés.
Vous êtes sur le point de faire quelque chose de potentiellement dangereux
Pour continuer, tapez la phrase « Oui, faites ce que je vous dis ! »
?]Oui, faites ce que je vous dis !
dpkg: avertissement: problème contourné par utilisation de --force :
dpkg: avertissement: this is a protected package; it should not be removed
(Lecture de la base de données... 153953 fichiers et répertoires déjà
installés.)
Suppression de shim-signed (1.45+15+1552672080.a4a1fbe-0ubuntu2) ...
(Lecture de la base de données... 153940 fichiers et répertoires déjà
installés.)
Purge des fichiers de configuration de shim-signed
(1.45+15+1552672080.a4a1fbe-0ubuntu2) ...
root@a:~#
however
root@a:~# apt purge shim-signed --force
E: L'option --force de la ligne de commande n'est pas reconnue quand elle est
utilisée avec d'autres options.
root@a:~# apt purge --force shim-signed
E: L'option --force de la ligne de commande n'est pas reconnue quand elle est
utilisée avec d'autres options.
root@a:~#
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1922380
Title:
remove shim-signed very difficult
Status in apt package in Ubuntu:
Incomplete
Bug description:
Hello
I don't want the shim-signed anymore, but I need an additional password to
remove it.
This error is for all version of ubuntu.
I am sure I am entering the correct one because I entered it using a
copy paste technique.
Have pity on those who do not know English well !!
apt purge shim-signed
Lecture des listes de paquets... Fait
Construction de l'arbre des dépendances
Lecture des informations d'état... Fait
Les paquets suivants ont été installés automatiquement et ne sont plus
nécessaires :
mokutil shim
Veuillez utiliser « apt autoremove » pour les supprimer.
Les paquets suivants seront ENLEVÉS :
shim-signed*
ATTENTION : Les paquets essentiels suivants vont être enlevés.
Vous NE devez PAS faire ceci, à moins de savoir exactement ce
que vous êtes en train de faire.
shim-signed
0 mis à jour, 0 nouvellement installés, 1 à enlever et 0 non mis à jour.
Après cette opération, 2 734 ko d'espace disque seront libérés.
Vous êtes sur le point de faire quelque chose de potentiellement dangereux
Pour continuer, tapez la phrase « Oui, faites ce que je vous dis ! »
?]Oui, faites ce que je vous dis !
Annulation.
root@a:~# export LANG=us
root@a:~# apt purge shim-signed
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer
required:
mokutil shim
Use 'apt autoremove' to remove them.
The following packages will be REMOVED:
shim-signed*
WARNING: The following essential packages will be removed.
This should NOT be done unless you know exactly what you are doing!
shim-signed
0 upgraded, 0 newly installed, 1 to remove and 171 not upgraded.
After this operation, 2734 kB disk space will be freed.
You are about to do something potentially harmful.
To continue type in the phrase 'Yes, do as I say!'
?] Yes, do as I say!
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = "fr_FR:fr_CA",
LC_ALL = (unset),
LC_TIME = "fr_FR.UTF-8",
LC_MONETARY = "fr_FR.UTF-8",
LC_ADDRESS = "fr_FR.UTF-8",
LC_TELEPHONE = "fr_FR.UTF-8",
LC_NAME = "fr_FR.UTF-8",
LC_MEASUREMENT = "fr_FR.UTF-8",
LC_IDENTIFICATION = "fr_FR.UTF-8",
LC_NUMERIC = "fr_FR.UTF-8",
LC_PAPER = "fr_FR.UTF-8",
LANG = "us"
are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").
locale: Cannot set LC_CTYPE to default locale: No such file or directory
locale: Cannot set LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory
dpkg: warning: overriding problem because --force enabled:
dpkg: warning: this is a protected package; it should not be removed
(Reading database ... 211327 files and directories
[Touch-packages] [Bug 1906702] Re: The boot_delay parameter is not interpreted by the correct boot module.
** Summary changed: - The boot_delay parameter is not interpreted by the correct boot modude + The boot_delay parameter is not interpreted by the correct boot module. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1906702 Title: The boot_delay parameter is not interpreted by the correct boot module. Status in initramfs-tools package in Ubuntu: New Bug description: Hello. Normal computer booting is no longer possible. However, this computer boots up without any difficulty using recovery mode. A first research shows that the normal boot does not reach the phase of delivery of the trace in the file /var/log/journal. If he did that, it would be possible to recover the trace with a live USB. (Journalctl -b -D /mnt/var/log/journal). It is possible to see the boot traces on the screen. But it ends with a black screen and the cursor blinking. The trace lines run so fast that it is impossible to read them. To solve this problem, I found in a lot of documentations, the "boot-delay" parameter which is described as: boot_delay = Milliseconds to delay each printk during boot. Values larger than 10 seconds (1) are changed to no delay (0). Format: integer ( in https://www.kernel.org/doc/html/latest/admin-guide/kernel- parameters.html?highlight=kernel%20parameters) So I modified the /boot/grub/grub.cfg file (Ubuntu 20.04.1) to put this setting in a place that I think is good (line 167) Here is its current content linux /boot/vmlinuz-5.4.0-56-generic root = UUID = ec732fcc-7338-46a2-91e0-1c883e26d0f9 ro nomodeset debug ignore_loglevel nomodeset boot_delay=180 But the boot is absolutely not going the way I wanted! With the value 0, the start-up delay is 2 seconds. With the value 60, the start delay is 85 seconds. With the value 120, the start delay is 185 seconds. With the value 180, the start delay is 275 seconds. I had not considered this delay at the start. When the start is done, the lines continue to scroll at full speed. My wish was to set the value 9876. But after 4 hours, the start-up still had not taken place. Thank you for dealing with the problem as best as possible: Software or documentation correction? Good week. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1906702/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1906702] [NEW] The boot_delay parameter is not interpreted by the correct boot modude
Public bug reported: Hello. Normal computer booting is no longer possible. However, this computer boots up without any difficulty using recovery mode. A first research shows that the normal boot does not reach the phase of delivery of the trace in the file /var/log/journal. If he did that, it would be possible to recover the trace with a live USB. (Journalctl -b -D /mnt/var/log/journal). It is possible to see the boot traces on the screen. But it ends with a black screen and the cursor blinking. The trace lines run so fast that it is impossible to read them. To solve this problem, I found in a lot of documentations, the "boot-delay" parameter which is described as: boot_delay = Milliseconds to delay each printk during boot. Values larger than 10 seconds (1) are changed to no delay (0). Format: integer ( in https://www.kernel.org/doc/html/latest/admin-guide/kernel- parameters.html?highlight=kernel%20parameters) So I modified the /boot/grub/grub.cfg file (Ubuntu 20.04.1) to put this setting in a place that I think is good (line 167) Here is its current content linux /boot/vmlinuz-5.4.0-56-generic root = UUID = ec732fcc-7338-46a2-91e0-1c883e26d0f9 ro nomodeset debug ignore_loglevel nomodeset boot_delay=180 But the boot is absolutely not going the way I wanted! With the value 0, the start-up delay is 2 seconds. With the value 60, the start delay is 85 seconds. With the value 120, the start delay is 185 seconds. With the value 180, the start delay is 275 seconds. I had not considered this delay at the start. When the start is done, the lines continue to scroll at full speed. My wish was to set the value 9876. But after 4 hours, the start-up still had not taken place. Thank you for dealing with the problem as best as possible: Software or documentation correction? Good week. ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Attachment added: "/boot/grub/grub.cfg" https://bugs.launchpad.net/bugs/1906702/+attachment/5440680/+files/grub.cfg -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1906702 Title: The boot_delay parameter is not interpreted by the correct boot modude Status in initramfs-tools package in Ubuntu: New Bug description: Hello. Normal computer booting is no longer possible. However, this computer boots up without any difficulty using recovery mode. A first research shows that the normal boot does not reach the phase of delivery of the trace in the file /var/log/journal. If he did that, it would be possible to recover the trace with a live USB. (Journalctl -b -D /mnt/var/log/journal). It is possible to see the boot traces on the screen. But it ends with a black screen and the cursor blinking. The trace lines run so fast that it is impossible to read them. To solve this problem, I found in a lot of documentations, the "boot-delay" parameter which is described as: boot_delay = Milliseconds to delay each printk during boot. Values larger than 10 seconds (1) are changed to no delay (0). Format: integer ( in https://www.kernel.org/doc/html/latest/admin-guide/kernel- parameters.html?highlight=kernel%20parameters) So I modified the /boot/grub/grub.cfg file (Ubuntu 20.04.1) to put this setting in a place that I think is good (line 167) Here is its current content linux /boot/vmlinuz-5.4.0-56-generic root = UUID = ec732fcc-7338-46a2-91e0-1c883e26d0f9 ro nomodeset debug ignore_loglevel nomodeset boot_delay=180 But the boot is absolutely not going the way I wanted! With the value 0, the start-up delay is 2 seconds. With the value 60, the start delay is 85 seconds. With the value 120, the start delay is 185 seconds. With the value 180, the start delay is 275 seconds. I had not considered this delay at the start. When the start is done, the lines continue to scroll at full speed. My wish was to set the value 9876. But after 4 hours, the start-up still had not taken place. Thank you for dealing with the problem as best as possible: Software or documentation correction? Good week. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1906702/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1890133] Re: User login screen is not offered
Contents Of dpkg ** Attachment added: "Contents Of dpkg" https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1890133/+attachment/5398249/+files/dpkg.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1890133 Title: User login screen is not offered Status in dbus package in Ubuntu: New Bug description: Hello. I know how to solve some connection problems. I can't find enough explanation to understand the cause of this problem! It seems to loop forever on the user login and network acquisition sequences. First stage "try ubuntu before installing it" This step goes smoothly. The present screen forces you to choose the NOMODESET option. which has become very easy .. I didn't notice anything abnormal. Second step "Install ubuntu" I didn't notice anything abnormal. Initially I had chosen not to update the software during installation and to automatically log in the user. I restarted the installation by asking to update the software during the installation and to propose the user connection grid. There is no change Third step "The normal boot" The screen proposing to enter the username does not appear regardless of the chosen kernel. Removing the two "quiet splash" options allows you to see a significant amount of failed and the loop that seems eternal. I even waited over 30 minutes Fourth step "Boot recovery" The recovery screen is displayed. I can do the proposed actions. Some go wrong. For example, the fsck command says the partition is "already mounted". I don't think the problem is there. The most important is the network enable command which does not seem to indicate any errors and which does not activate the network! Ping 8.8.8.8 says network is not operational Fifth step "The start by CHROOT" This technique allows me to access the log of the installed instance (journalctl -D / mnt / var / log / journald) and find the first level of errors. Some advice says to dig deeper with the systemctl command but this one does not work in chroot mode. Sixth step "The diagnosis". As the normal boot never ends except by power-off, I used the recovery mode to access the logs of the previous boot. It is not that easy. I put in .txt files that I will send to you. I think reading the contents of some of these files will allow you to give me additional commands to find the cause of the problem. Thanks in advance. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1890133/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1890133] Re: User login screen is not offered
The Ubuntu version ** Attachment added: "The Ubuntu version" https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1890133/+attachment/5398253/+files/Version.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1890133 Title: User login screen is not offered Status in dbus package in Ubuntu: New Bug description: Hello. I know how to solve some connection problems. I can't find enough explanation to understand the cause of this problem! It seems to loop forever on the user login and network acquisition sequences. First stage "try ubuntu before installing it" This step goes smoothly. The present screen forces you to choose the NOMODESET option. which has become very easy .. I didn't notice anything abnormal. Second step "Install ubuntu" I didn't notice anything abnormal. Initially I had chosen not to update the software during installation and to automatically log in the user. I restarted the installation by asking to update the software during the installation and to propose the user connection grid. There is no change Third step "The normal boot" The screen proposing to enter the username does not appear regardless of the chosen kernel. Removing the two "quiet splash" options allows you to see a significant amount of failed and the loop that seems eternal. I even waited over 30 minutes Fourth step "Boot recovery" The recovery screen is displayed. I can do the proposed actions. Some go wrong. For example, the fsck command says the partition is "already mounted". I don't think the problem is there. The most important is the network enable command which does not seem to indicate any errors and which does not activate the network! Ping 8.8.8.8 says network is not operational Fifth step "The start by CHROOT" This technique allows me to access the log of the installed instance (journalctl -D / mnt / var / log / journald) and find the first level of errors. Some advice says to dig deeper with the systemctl command but this one does not work in chroot mode. Sixth step "The diagnosis". As the normal boot never ends except by power-off, I used the recovery mode to access the logs of the previous boot. It is not that easy. I put in .txt files that I will send to you. I think reading the contents of some of these files will allow you to give me additional commands to find the cause of the problem. Thanks in advance. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1890133/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1890133] Re: User login screen is not offered
Contents of Journalctl ** Attachment added: "Contents of Journalctl" https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1890133/+attachment/5398248/+files/Journal.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1890133 Title: User login screen is not offered Status in dbus package in Ubuntu: New Bug description: Hello. I know how to solve some connection problems. I can't find enough explanation to understand the cause of this problem! It seems to loop forever on the user login and network acquisition sequences. First stage "try ubuntu before installing it" This step goes smoothly. The present screen forces you to choose the NOMODESET option. which has become very easy .. I didn't notice anything abnormal. Second step "Install ubuntu" I didn't notice anything abnormal. Initially I had chosen not to update the software during installation and to automatically log in the user. I restarted the installation by asking to update the software during the installation and to propose the user connection grid. There is no change Third step "The normal boot" The screen proposing to enter the username does not appear regardless of the chosen kernel. Removing the two "quiet splash" options allows you to see a significant amount of failed and the loop that seems eternal. I even waited over 30 minutes Fourth step "Boot recovery" The recovery screen is displayed. I can do the proposed actions. Some go wrong. For example, the fsck command says the partition is "already mounted". I don't think the problem is there. The most important is the network enable command which does not seem to indicate any errors and which does not activate the network! Ping 8.8.8.8 says network is not operational Fifth step "The start by CHROOT" This technique allows me to access the log of the installed instance (journalctl -D / mnt / var / log / journald) and find the first level of errors. Some advice says to dig deeper with the systemctl command but this one does not work in chroot mode. Sixth step "The diagnosis". As the normal boot never ends except by power-off, I used the recovery mode to access the logs of the previous boot. It is not that easy. I put in .txt files that I will send to you. I think reading the contents of some of these files will allow you to give me additional commands to find the cause of the problem. Thanks in advance. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1890133/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1890133] Re: User login screen is not offered
Contents of NetworkManager ** Attachment added: "Contents of NetworkManager" https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1890133/+attachment/5398250/+files/NetworkManager.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1890133 Title: User login screen is not offered Status in dbus package in Ubuntu: New Bug description: Hello. I know how to solve some connection problems. I can't find enough explanation to understand the cause of this problem! It seems to loop forever on the user login and network acquisition sequences. First stage "try ubuntu before installing it" This step goes smoothly. The present screen forces you to choose the NOMODESET option. which has become very easy .. I didn't notice anything abnormal. Second step "Install ubuntu" I didn't notice anything abnormal. Initially I had chosen not to update the software during installation and to automatically log in the user. I restarted the installation by asking to update the software during the installation and to propose the user connection grid. There is no change Third step "The normal boot" The screen proposing to enter the username does not appear regardless of the chosen kernel. Removing the two "quiet splash" options allows you to see a significant amount of failed and the loop that seems eternal. I even waited over 30 minutes Fourth step "Boot recovery" The recovery screen is displayed. I can do the proposed actions. Some go wrong. For example, the fsck command says the partition is "already mounted". I don't think the problem is there. The most important is the network enable command which does not seem to indicate any errors and which does not activate the network! Ping 8.8.8.8 says network is not operational Fifth step "The start by CHROOT" This technique allows me to access the log of the installed instance (journalctl -D / mnt / var / log / journald) and find the first level of errors. Some advice says to dig deeper with the systemctl command but this one does not work in chroot mode. Sixth step "The diagnosis". As the normal boot never ends except by power-off, I used the recovery mode to access the logs of the previous boot. It is not that easy. I put in .txt files that I will send to you. I think reading the contents of some of these files will allow you to give me additional commands to find the cause of the problem. Thanks in advance. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1890133/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1890133] [NEW] User login screen is not offered
Public bug reported: Hello. I know how to solve some connection problems. I can't find enough explanation to understand the cause of this problem! It seems to loop forever on the user login and network acquisition sequences. First stage "try ubuntu before installing it" This step goes smoothly. The present screen forces you to choose the NOMODESET option. which has become very easy .. I didn't notice anything abnormal. Second step "Install ubuntu" I didn't notice anything abnormal. Initially I had chosen not to update the software during installation and to automatically log in the user. I restarted the installation by asking to update the software during the installation and to propose the user connection grid. There is no change Third step "The normal boot" The screen proposing to enter the username does not appear regardless of the chosen kernel. Removing the two "quiet splash" options allows you to see a significant amount of failed and the loop that seems eternal. I even waited over 30 minutes Fourth step "Boot recovery" The recovery screen is displayed. I can do the proposed actions. Some go wrong. For example, the fsck command says the partition is "already mounted". I don't think the problem is there. The most important is the network enable command which does not seem to indicate any errors and which does not activate the network! Ping 8.8.8.8 says network is not operational Fifth step "The start by CHROOT" This technique allows me to access the log of the installed instance (journalctl -D / mnt / var / log / journald) and find the first level of errors. Some advice says to dig deeper with the systemctl command but this one does not work in chroot mode. Sixth step "The diagnosis". As the normal boot never ends except by power-off, I used the recovery mode to access the logs of the previous boot. It is not that easy. I put in .txt files that I will send to you. I think reading the contents of some of these files will allow you to give me additional commands to find the cause of the problem. Thanks in advance. ** Affects: dbus (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1890133 Title: User login screen is not offered Status in dbus package in Ubuntu: New Bug description: Hello. I know how to solve some connection problems. I can't find enough explanation to understand the cause of this problem! It seems to loop forever on the user login and network acquisition sequences. First stage "try ubuntu before installing it" This step goes smoothly. The present screen forces you to choose the NOMODESET option. which has become very easy .. I didn't notice anything abnormal. Second step "Install ubuntu" I didn't notice anything abnormal. Initially I had chosen not to update the software during installation and to automatically log in the user. I restarted the installation by asking to update the software during the installation and to propose the user connection grid. There is no change Third step "The normal boot" The screen proposing to enter the username does not appear regardless of the chosen kernel. Removing the two "quiet splash" options allows you to see a significant amount of failed and the loop that seems eternal. I even waited over 30 minutes Fourth step "Boot recovery" The recovery screen is displayed. I can do the proposed actions. Some go wrong. For example, the fsck command says the partition is "already mounted". I don't think the problem is there. The most important is the network enable command which does not seem to indicate any errors and which does not activate the network! Ping 8.8.8.8 says network is not operational Fifth step "The start by CHROOT" This technique allows me to access the log of the installed instance (journalctl -D / mnt / var / log / journald) and find the first level of errors. Some advice says to dig deeper with the systemctl command but this one does not work in chroot mode. Sixth step "The diagnosis". As the normal boot never ends except by power-off, I used the recovery mode to access the logs of the previous boot. It is not that easy. I put in .txt files that I will send to you. I think reading the contents of some of these files will allow you to give me additional commands to find the cause of the problem. Thanks in advance. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1890133/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1860917] Re: uas_eh_abort_handler uas-tag inflight OUT
Hello The incident is always present with the most recent ubuntu version. a@a:~$ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=20.04 DISTRIB_CODENAME=focal DISTRIB_DESCRIPTION="Ubuntu Focal Fossa (development branch)" a@a:~$ a@a:~$ a@a:~$ sudo apt update Atteint :1 http://fr.archive.ubuntu.com/ubuntu focal InRelease Atteint :2 http://fr.archive.ubuntu.com/ubuntu focal-updates InRelease Atteint :3 http://security.ubuntu.com/ubuntu focal-security InRelease Atteint :4 http://fr.archive.ubuntu.com/ubuntu focal-backports InRelease Lecture des listes de paquets... Fait Construction de l'arbre des dépendances Lecture des informations d'état... Fait Tous les paquets sont à jour. a@a:~$ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu. https://bugs.launchpad.net/bugs/1860917 Title: uas_eh_abort_handler uas-tag inflight OUT Status in e2fsprogs package in Ubuntu: New Bug description: 591/5000 Hello To try to understand this incident ( https://bugs.launchpad.net/ubuntu/+source/gpart/+bug/1857914 ) which systematically occurs in version 19.10 and which I cannot (yet?) reproduce in version 18.04.03, I made a test game. Using this test game consisting only of cp and diff commands, I caused a similar problem. The first visible consequence which seems serious to me: The copied file is not identical to the sending file. It seems that the blocks are shifted. It would be desirable for the user to be warned that the written files have become incorrect. Thank you for your advice. Journalctl says only janv. 26 13:29:35 a kernel: EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null) janv. 26 13:30:12 a kernel: sd 6:0:0:0: [sdb] tag#16 uas_eh_abort_handler 0 uas-tag 17 inflight: OUT janv. 26 13:30:12 a kernel: sd 6:0:0:0: [sdb] tag#16 CDB: Write(10) 2a 00 00 0f ec 00 00 04 00 00 janv. 26 14:22:48 a kernel: EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null) a@a:~$ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1860917/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1860917] Re: uas_eh_abort_handler uas-tag inflight OUT
** Attachment added: "Trace of execution" https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1860917/+attachment/5331562/+files/Bug1857914-102-176-8192Mo-SDB10bis.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu. https://bugs.launchpad.net/bugs/1860917 Title: uas_eh_abort_handler uas-tag inflight OUT Status in e2fsprogs package in Ubuntu: New Bug description: 591/5000 Hello To try to understand this incident ( https://bugs.launchpad.net/ubuntu/+source/gpart/+bug/1857914 ) which systematically occurs in version 19.10 and which I cannot (yet?) reproduce in version 18.04.03, I made a test game. Using this test game consisting only of cp and diff commands, I caused a similar problem. The first visible consequence which seems serious to me: The copied file is not identical to the sending file. It seems that the blocks are shifted. It would be desirable for the user to be warned that the written files have become incorrect. Thank you for your advice. Journalctl says only janv. 26 13:29:35 a kernel: EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null) janv. 26 13:30:12 a kernel: sd 6:0:0:0: [sdb] tag#16 uas_eh_abort_handler 0 uas-tag 17 inflight: OUT janv. 26 13:30:12 a kernel: sd 6:0:0:0: [sdb] tag#16 CDB: Write(10) 2a 00 00 0f ec 00 00 04 00 00 janv. 26 14:22:48 a kernel: EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null) a@a:~$ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1860917/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1860917] Re: uas_eh_abort_handler uas-tag inflight OUT
** Attachment added: "File contains three scripts to make the bug" https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1860917/+attachment/5324759/+files/BUG13.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu. https://bugs.launchpad.net/bugs/1860917 Title: uas_eh_abort_handler uas-tag inflight OUT Status in e2fsprogs package in Ubuntu: New Bug description: 591/5000 Hello To try to understand this incident ( https://bugs.launchpad.net/ubuntu/+source/gpart/+bug/1857914 ) which systematically occurs in version 19.10 and which I cannot (yet?) reproduce in version 18.04.03, I made a test game. Using this test game consisting only of cp and diff commands, I caused a similar problem. The first visible consequence which seems serious to me: The copied file is not identical to the sending file. It seems that the blocks are shifted. It would be desirable for the user to be warned that the written files have become incorrect. Thank you for your advice. Journalctl says only janv. 26 13:29:35 a kernel: EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null) janv. 26 13:30:12 a kernel: sd 6:0:0:0: [sdb] tag#16 uas_eh_abort_handler 0 uas-tag 17 inflight: OUT janv. 26 13:30:12 a kernel: sd 6:0:0:0: [sdb] tag#16 CDB: Write(10) 2a 00 00 0f ec 00 00 04 00 00 janv. 26 14:22:48 a kernel: EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null) a@a:~$ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1860917/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1860917] Re: uas_eh_abort_handler uas-tag inflight OUT
ATTENTION This error is new. and it is because of use of logical device not un good order!!! Feb 02 10:59:19 a systemd[1315]: mnt-USBsdb3.mount: Succeeded. Feb 02 10:59:39 a kernel: blk_update_request: I/O error, dev sdb, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0 Feb 02 10:59:39 a kernel: blk_update_request: I/O error, dev sdb, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0 Feb 02 10:59:39 a kernel: blk_update_request: I/O error, dev sdb, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0 Feb 02 10:59:39 a kernel: blk_update_request: I/O error, dev sdb, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0 Feb 02 10:59:57 a kernel: usb 4-2: new SuperSpeed Gen 1 USB device number 3 using xhci_hcd ** Attachment added: "Trace of one execution" https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1860917/+attachment/5324760/+files/Bug1857914-102-176-8192Mo.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu. https://bugs.launchpad.net/bugs/1860917 Title: uas_eh_abort_handler uas-tag inflight OUT Status in e2fsprogs package in Ubuntu: New Bug description: 591/5000 Hello To try to understand this incident ( https://bugs.launchpad.net/ubuntu/+source/gpart/+bug/1857914 ) which systematically occurs in version 19.10 and which I cannot (yet?) reproduce in version 18.04.03, I made a test game. Using this test game consisting only of cp and diff commands, I caused a similar problem. The first visible consequence which seems serious to me: The copied file is not identical to the sending file. It seems that the blocks are shifted. It would be desirable for the user to be warned that the written files have become incorrect. Thank you for your advice. Journalctl says only janv. 26 13:29:35 a kernel: EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null) janv. 26 13:30:12 a kernel: sd 6:0:0:0: [sdb] tag#16 uas_eh_abort_handler 0 uas-tag 17 inflight: OUT janv. 26 13:30:12 a kernel: sd 6:0:0:0: [sdb] tag#16 CDB: Write(10) 2a 00 00 0f ec 00 00 04 00 00 janv. 26 14:22:48 a kernel: EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null) a@a:~$ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1860917/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1860917] Re: uas_eh_abort_handler uas-tag inflight OUT
Hello. Thank you for your involvement in this problem. My goal is to make ubuntu better. I accidentally encountered this incident in a real context. I knew that changing partition size is risky and impossible with a partition in use. That's why I duplicated it on an external disk. I found that the problem was reproducible. As the partition size was around 300 GiB, this took a long time. I managed to make a 40 GB test game. I was then able to reproduce the incident on 12 partitions. I think I eliminated the material cause by doing the tests - Badblocks with a partition making up the entire disk. - Writing single sectors on approximately 95% of the disk space then re-reading with control of what is read is indeed what is expected. - Impossible to reproduce the incident if using the ext3 format - Impossible to reproduce the incident in the same session. A boot or a disconnection must take place for each incident. - Unable to carry out the incident in version 18.04.03 My diagnosis is that there is a functioning problem in the hard drive application link when the UAS driver is used. I worked as much as possible to reduce the size of the partition so that the execution times were acceptable. Now, I cause the incident systematically with an 8 GB partition. I do not know how to do less despite all the possible tests. I find it important to diagnose the problem to avoid that the future version 20.04 also have this behavior. I don't know if it's in the UAS module, the resize2fs module or maybe the mount module. You will find attached a file containing the mode of realization of the incident with 1) a script making 250 files of 30 Mio. 2) a script formatting the partition and transferring the files then deleting the first files. it seems to me that this is the key element in the making of the incident. 3) A script doing the size reduction. Another file contained resulted from an execution. I was able to do the incidents with the following quantities of files: 250 - 150 250 - 125 200 - 125 176 - 102 I cannot produce the incident with the couple 174-100. This seems to me to be a problem of volumetry that UAS treats badly. I remain available to put the trace options that you will advise me. I am ready to open a new problem with the mount module and the UAS module because there is not the same function as in version 18.04.3 for the management of logical partitions which are not in the same order as the physical structure. The UAS module is now automatically disabled. It's probably better this way. I use google translation to answer you Thanks. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu. https://bugs.launchpad.net/bugs/1860917 Title: uas_eh_abort_handler uas-tag inflight OUT Status in e2fsprogs package in Ubuntu: New Bug description: 591/5000 Hello To try to understand this incident ( https://bugs.launchpad.net/ubuntu/+source/gpart/+bug/1857914 ) which systematically occurs in version 19.10 and which I cannot (yet?) reproduce in version 18.04.03, I made a test game. Using this test game consisting only of cp and diff commands, I caused a similar problem. The first visible consequence which seems serious to me: The copied file is not identical to the sending file. It seems that the blocks are shifted. It would be desirable for the user to be warned that the written files have become incorrect. Thank you for your advice. Journalctl says only janv. 26 13:29:35 a kernel: EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null) janv. 26 13:30:12 a kernel: sd 6:0:0:0: [sdb] tag#16 uas_eh_abort_handler 0 uas-tag 17 inflight: OUT janv. 26 13:30:12 a kernel: sd 6:0:0:0: [sdb] tag#16 CDB: Write(10) 2a 00 00 0f ec 00 00 04 00 00 janv. 26 14:22:48 a kernel: EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null) a@a:~$ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1860917/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1860917] Re: uas_eh_abort_handler uas-tag inflight OUT
** Attachment added: "Bug with only SDB5 partition" https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1860917/+attachment/5323754/+files/Bug1857914-sdb5.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu. https://bugs.launchpad.net/bugs/1860917 Title: uas_eh_abort_handler uas-tag inflight OUT Status in e2fsprogs package in Ubuntu: New Bug description: 591/5000 Hello To try to understand this incident ( https://bugs.launchpad.net/ubuntu/+source/gpart/+bug/1857914 ) which systematically occurs in version 19.10 and which I cannot (yet?) reproduce in version 18.04.03, I made a test game. Using this test game consisting only of cp and diff commands, I caused a similar problem. The first visible consequence which seems serious to me: The copied file is not identical to the sending file. It seems that the blocks are shifted. It would be desirable for the user to be warned that the written files have become incorrect. Thank you for your advice. Journalctl says only janv. 26 13:29:35 a kernel: EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null) janv. 26 13:30:12 a kernel: sd 6:0:0:0: [sdb] tag#16 uas_eh_abort_handler 0 uas-tag 17 inflight: OUT janv. 26 13:30:12 a kernel: sd 6:0:0:0: [sdb] tag#16 CDB: Write(10) 2a 00 00 0f ec 00 00 04 00 00 janv. 26 14:22:48 a kernel: EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null) a@a:~$ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1860917/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1860917] Re: uas_eh_abort_handler uas-tag inflight OUT
** Attachment added: "Bug with SDB6 only" https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1860917/+attachment/5323755/+files/Bug1857914-sdb6.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu. https://bugs.launchpad.net/bugs/1860917 Title: uas_eh_abort_handler uas-tag inflight OUT Status in e2fsprogs package in Ubuntu: New Bug description: 591/5000 Hello To try to understand this incident ( https://bugs.launchpad.net/ubuntu/+source/gpart/+bug/1857914 ) which systematically occurs in version 19.10 and which I cannot (yet?) reproduce in version 18.04.03, I made a test game. Using this test game consisting only of cp and diff commands, I caused a similar problem. The first visible consequence which seems serious to me: The copied file is not identical to the sending file. It seems that the blocks are shifted. It would be desirable for the user to be warned that the written files have become incorrect. Thank you for your advice. Journalctl says only janv. 26 13:29:35 a kernel: EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null) janv. 26 13:30:12 a kernel: sd 6:0:0:0: [sdb] tag#16 uas_eh_abort_handler 0 uas-tag 17 inflight: OUT janv. 26 13:30:12 a kernel: sd 6:0:0:0: [sdb] tag#16 CDB: Write(10) 2a 00 00 0f ec 00 00 04 00 00 janv. 26 14:22:48 a kernel: EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null) a@a:~$ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1860917/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1860917] Re: uas_eh_abort_handler uas-tag inflight OUT
** Attachment added: "Bug with only SDB2 partition" https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1860917/+attachment/5323763/+files/Bug1857914-sdb2.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu. https://bugs.launchpad.net/bugs/1860917 Title: uas_eh_abort_handler uas-tag inflight OUT Status in e2fsprogs package in Ubuntu: New Bug description: 591/5000 Hello To try to understand this incident ( https://bugs.launchpad.net/ubuntu/+source/gpart/+bug/1857914 ) which systematically occurs in version 19.10 and which I cannot (yet?) reproduce in version 18.04.03, I made a test game. Using this test game consisting only of cp and diff commands, I caused a similar problem. The first visible consequence which seems serious to me: The copied file is not identical to the sending file. It seems that the blocks are shifted. It would be desirable for the user to be warned that the written files have become incorrect. Thank you for your advice. Journalctl says only janv. 26 13:29:35 a kernel: EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null) janv. 26 13:30:12 a kernel: sd 6:0:0:0: [sdb] tag#16 uas_eh_abort_handler 0 uas-tag 17 inflight: OUT janv. 26 13:30:12 a kernel: sd 6:0:0:0: [sdb] tag#16 CDB: Write(10) 2a 00 00 0f ec 00 00 04 00 00 janv. 26 14:22:48 a kernel: EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null) a@a:~$ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1860917/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1860917] Re: uas_eh_abort_handler uas-tag inflight OUT
Hello. When I decide to reduce the size of a partition stored in an external drive and formatted in EXT4 after booting with ubuntu 19.10, this partition is destroyed. it seems abnormal to me. This is systematic for the twelve partitions and twelve boots in the prepared context. If several partitions are reduced in the same passage, only the first in the list is destroyed. The others are well treated! Failure does not occur if another external drive is used. The incident does not occur if the partition is formatted in EXT3 or if the size reduction is done with ubuntu 18.04.3 Some results will be provided as an attachment Here is the script used. export LC_ALL=POSIX Size=35957760k Debug="-d 60" Trace=Bug1857914-ThreePartitions.txt date>$Trace for Part in sdb1 sdb6 sdb7 ;do sudo umount /dev/$Part echo "check file system on /dev/$Part for errors with command sudo e2fsck -f -y -v /dev/$Part >>$TRACE" >>$Trace sudo e2fsck -f -y -v /dev/$Part 2>>$Trace >>$Trace echo " shrink for /dev/$Part with command sudo resize2fs $Debug -p /dev/$Part $Size >>$Trace" >>$Trace sudo resize2fs $Debug -p /dev/$Part $Size 2>>$Trace >>$Trace echo "check file system on /dev/$Part for errors with command sudo e2fsck -f -n -v /dev/$Part >>$TRACE" >>$Trace sudo e2fsck -f -n -v /dev/$Part 2>>$Trace >>$Trace echo "check for erreur on UAS module with command journalctl -b | egrep "resize2fs|uas_eh_abort_handler" >>$TRACE" >>$Trace done journalctl -b | grep -E "resize2fs|CDB|uas_eh_abort_handler|I/O error|sdb" >>$Trace date>>$Trace cat $Trace ** Attachment added: "An execution with three partitions" https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1860917/+attachment/5323753/+files/Bug1857914-ThreePartitions.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu. https://bugs.launchpad.net/bugs/1860917 Title: uas_eh_abort_handler uas-tag inflight OUT Status in e2fsprogs package in Ubuntu: New Bug description: 591/5000 Hello To try to understand this incident ( https://bugs.launchpad.net/ubuntu/+source/gpart/+bug/1857914 ) which systematically occurs in version 19.10 and which I cannot (yet?) reproduce in version 18.04.03, I made a test game. Using this test game consisting only of cp and diff commands, I caused a similar problem. The first visible consequence which seems serious to me: The copied file is not identical to the sending file. It seems that the blocks are shifted. It would be desirable for the user to be warned that the written files have become incorrect. Thank you for your advice. Journalctl says only janv. 26 13:29:35 a kernel: EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null) janv. 26 13:30:12 a kernel: sd 6:0:0:0: [sdb] tag#16 uas_eh_abort_handler 0 uas-tag 17 inflight: OUT janv. 26 13:30:12 a kernel: sd 6:0:0:0: [sdb] tag#16 CDB: Write(10) 2a 00 00 0f ec 00 00 04 00 00 janv. 26 14:22:48 a kernel: EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null) a@a:~$ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1860917/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1860917] Re: uas_eh_abort_handler uas-tag inflight OUT
** Package changed: ubuntu => e2fsprogs (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu. https://bugs.launchpad.net/bugs/1860917 Title: uas_eh_abort_handler uas-tag inflight OUT Status in e2fsprogs package in Ubuntu: New Bug description: 591/5000 Hello To try to understand this incident ( https://bugs.launchpad.net/ubuntu/+source/gpart/+bug/1857914 ) which systematically occurs in version 19.10 and which I cannot (yet?) reproduce in version 18.04.03, I made a test game. Using this test game consisting only of cp and diff commands, I caused a similar problem. The first visible consequence which seems serious to me: The copied file is not identical to the sending file. It seems that the blocks are shifted. It would be desirable for the user to be warned that the written files have become incorrect. Thank you for your advice. Journalctl says only janv. 26 13:29:35 a kernel: EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null) janv. 26 13:30:12 a kernel: sd 6:0:0:0: [sdb] tag#16 uas_eh_abort_handler 0 uas-tag 17 inflight: OUT janv. 26 13:30:12 a kernel: sd 6:0:0:0: [sdb] tag#16 CDB: Write(10) 2a 00 00 0f ec 00 00 04 00 00 janv. 26 14:22:48 a kernel: EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null) a@a:~$ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1860917/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1860544] Re: package uuid-runtime 2.34-0.1ubuntu2.1 failed to install/upgrade: installed uuid-runtime package post-installation script subprocess returned error exit status 1
Me also -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1860544 Title: package uuid-runtime 2.34-0.1ubuntu2.1 failed to install/upgrade: installed uuid-runtime package post-installation script subprocess returned error exit status 1 Status in util-linux package in Ubuntu: Confirmed Bug description: during update, the updater sent this message ProblemType: Package DistroRelease: Ubuntu 19.10 Package: uuid-runtime 2.34-0.1ubuntu2.1 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 Date: Wed Jan 22 13:12:14 2020 ErrorMessage: installed uuid-runtime package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2017-06-01 (964 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Python3Details: /usr/bin/python3.7, Python 3.7.5, python3-minimal, 3.7.5-1 PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.17-1 RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.4 SourcePackage: util-linux Title: package uuid-runtime 2.34-0.1ubuntu2.1 failed to install/upgrade: installed uuid-runtime package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to eoan on 2019-10-22 (91 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1860544/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1857914] Re: resize2fs destroy the content of the partition
Hello I cannot reproduce the incident with this method export LC_ALL=POSIX sudo mke2fs -t ext4 /USB1910bis/fs.img 30G mke2fs 1.45.3 (14-Jul-2019) Creating regular file /mnt/USB1910bis/fs.img Creating filesystem with 7864320 4k blocks and 1966080 inodes Filesystem UUID: 2cf9eafb-628c-45d3-b452-6bdf785ae24d Superblock backups stored on blocks: 32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208, 4096000 Allocating group tables: done Writing inode tables: done Creating journal (32768 blocks): done Writing superblocks and filesystem accounting information: done sudo mount -v -o loop /USB1910bis/fs.img /mnt mount: /dev/loop12 mounted on /mnt. It is necessary to copy files because when the partition does not contain any, it can shrink without difficulty sudo ls -ls /mnt total 20 4 drwx-- 20 root root 4096 Jan 2 13:20 P2 16 drwx-- 2 root root 16384 Jan 2 12:56 lost+found sudo umount -v /mnt umount: /mnt unmounted sudo e2fsck -fy /USB1910bis/fs.img e2fsck 1.45.3 (14-Jul-2019) Pass 1: Checking inodes, blocks, and sizes Pass 2: Checking directory structure Pass 3: Checking directory connectivity Pass 4: Checking reference counts Pass 5: Checking group summary information /USB1910bis/fs.img: 3929/1966080 files (0.4% non-contiguous), 3978206/7864320 blocks sudo resize2fs /USB1910bis/fs.img 20G resize2fs 1.45.3 (14-Jul-2019) Resizing the filesystem on /USB1910bis/fs.img to 5242880 (4k) blocks. The filesystem on /USB1910bis/fs.img is now 5242880 (4k) blocks long. sudo e2fsck -fy /USB1910bis/fs.img e2fsck 1.45.3 (14-Jul-2019) Pass 1: Checking inodes, blocks, and sizes Pass 2: Checking directory structure Pass 3: Checking directory connectivity Pass 4: Checking reference counts Pass 5: Checking group summary information /USB1910bis/fs.img: 3929/1310720 files (0.4% non-contiguous), 3937075/5242880 blocks sudo mount -v -o loop /USB1910bis/fs.img /mnt mount: /dev/loop12 mounted on /mnt. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu. https://bugs.launchpad.net/bugs/1857914 Title: resize2fs destroy the content of the partition Status in e2fsprogs package in Ubuntu: New Bug description: Hello The used version of ubuntu is 19.10 So the used version of ubuntu is GParted 0.32.0 and the used of resize2fs is 1.45.3 (14-Jul-2019) I wanted to shrink by 20 GB the size of an old partition created with ubuntu 18.04 and stored on an external hard drive connected by USB3. The process says it works perfectly well see attachment file But the partition can no longer be mounted. The message is: mount: /mnt/sdb2 : wrong fs type, bad option, bad superblock on /dev/sdb2, missing codepage or helper program, or other error. if I do the stupidity to launch the fsk command to repair, I find all the files and directory in the special directory called Lost + found Being able to remake the original content, I have seen four times that it gives this unpleasant result. It also allows me to change the scenario. - If I use an internal disk partition instead of the external disk, you're fine. - If I use version 18.04, everything is fine even if I use the external disk - If I make a new partition on the external disk in version 19.10, I can shrink also without any problem. So I think there is a software regression for a very specific context. Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1857914/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1857914] [NEW] resize2fs destroy the content of the partition
Public bug reported: Hello The used version of ubuntu is 19.10 So the used version of ubuntu is GParted 0.32.0 and the used of resize2fs is 1.45.3 (14-Jul-2019) I wanted to shrink by 20 GB the size of an old partition created with ubuntu 18.04 and stored on an external hard drive connected by USB3. The process says it works perfectly well see attachment file But the partition can no longer be mounted. The message is: mount: /mnt/sdb2 : wrong fs type, bad option, bad superblock on /dev/sdb2, missing codepage or helper program, or other error. if I do the stupidity to launch the fsk command to repair, I find all the files and directory in the special directory called Lost + found Being able to remake the original content, I have seen four times that it gives this unpleasant result. It also allows me to change the scenario. - If I use an internal disk partition instead of the external disk, you're fine. - If I use version 18.04, everything is fine even if I use the external disk - If I make a new partition on the external disk in version 19.10, I can shrink also without any problem. So I think there is a software regression for a very specific context. Thanks. ** Affects: e2fsprogs (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Three traces" https://bugs.launchpad.net/bugs/1857914/+attachment/5316522/+files/Traces.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu. https://bugs.launchpad.net/bugs/1857914 Title: resize2fs destroy the content of the partition Status in e2fsprogs package in Ubuntu: New Bug description: Hello The used version of ubuntu is 19.10 So the used version of ubuntu is GParted 0.32.0 and the used of resize2fs is 1.45.3 (14-Jul-2019) I wanted to shrink by 20 GB the size of an old partition created with ubuntu 18.04 and stored on an external hard drive connected by USB3. The process says it works perfectly well see attachment file But the partition can no longer be mounted. The message is: mount: /mnt/sdb2 : wrong fs type, bad option, bad superblock on /dev/sdb2, missing codepage or helper program, or other error. if I do the stupidity to launch the fsk command to repair, I find all the files and directory in the special directory called Lost + found Being able to remake the original content, I have seen four times that it gives this unpleasant result. It also allows me to change the scenario. - If I use an internal disk partition instead of the external disk, you're fine. - If I use version 18.04, everything is fine even if I use the external disk - If I make a new partition on the external disk in version 19.10, I can shrink also without any problem. So I think there is a software regression for a very specific context. Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1857914/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
