[Bug 1580308] Re: update-initramfs cryptsetup must correctly take into account PARTLABEL inside /etc/fstab
cryptsetup: WARNING: failed to detect canonical device is fixed in cryptsetup/2:2.0.3-2 - https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=784881 The version is not available in Ubuntu 18.10 - https://packages.ubuntu.com/bionic-updates/cryptsetup - which means initramfs update fail for encrypted disks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1580308 Title: update-initramfs cryptsetup must correctly take into account PARTLABEL inside /etc/fstab To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1580308/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1580308] Re: update-initramfs cryptsetup must correctly take into account PARTLABEL inside /etc/fstab
Not included in 18.04 LTS. This causes servers to hang after update and reboot - https://community.scaleway.com/t/arm64-hangs-with-ubuntu-18-04 -fully-updated/7681 ** Also affects: cryptsetup (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1580308 Title: update-initramfs cryptsetup must correctly take into account PARTLABEL inside /etc/fstab To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1580308/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1580308] Re: update-initramfs cryptsetup must correctly take into account PARTLABEL inside /etc/fstab
I got it [1] now also for the first time when doing apt upgrade and it is pretty scary when considering that /dev/sda3 is the root folder [2]. [1] ... Setting up update-manager-core (1:17.04.8) ... Setting up update-manager (1:17.04.8) ... Processing triggers for libc-bin (2.24-9ubuntu2.2) ... Processing triggers for initramfs-tools (0.125ubuntu9) ... update-initramfs: Generating /boot/initrd.img-4.11.8-041108-generic cryptsetup: WARNING: failed to detect canonical device of /dev/sda3 cryptsetup: WARNING: could not determine root device from /etc/fstab [2] df Filesystem 1K-blocks Used Available Use% Mounted on udev 16353300 0 16353300 0% /dev tmpfs 3276344108148 3168196 4% /run /dev/sda351343840 16054812 32651204 33% / tmpfs16381712700604 15681108 5% /dev/shm tmpfs5120 4 5116 1% /run/lock tmpfs16381712 0 16381712 0% /sys/fs/cgroup /dev/loop0 85120 85120 0 100% /snap/core/3017 /dev/loop2 83456 83456 0 100% /snap/core/2898 /dev/sda1 523248 1176522072 1% /boot/efi /dev/sda4 419291016 332865984 86408648 80% /home tmpfs 327634064 3276276 1% /run/user/1000 /home/me/.Private 419291016 332865984 86408648 80% /home/me /dev/loop3 85120 85120 0 100% /snap/core/3247 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1580308 Title: update-initramfs cryptsetup must correctly take into account PARTLABEL inside /etc/fstab To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1580308/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1580308] Re: update-initramfs cryptsetup must correctly take into account PARTLABEL inside /etc/fstab
# more /etc/fstab /dev/md1/ ext3defaults,noatime 1 1 /dev/sda2 noneswapsw /dev/sdb2 noneswapsw /dev/vg00/usr /usrext4noatime,errors=remount-ro 0 2 /dev/vg00/var /varext4noatime,errors=remount-ro 0 2 /dev/vg00/home /home ext4noatime,errors=remount-ro 0 2 #/dev/hdd/data /data ext4noatime,errors=remount-ro 0 2 proc/proc procnodev,noexec,nosuid 0 0 # mount sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime) proc on /proc type proc (rw,nosuid,nodev,noexec,relatime) udev on /dev type devtmpfs (rw,nosuid,relatime,size=8154408k,nr_inodes=2038602,mode=755) devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000) tmpfs on /run type tmpfs (rw,nosuid,noexec,relatime,size=1641468k,mode=755) /dev/md1 on / type ext3 (rw,noatime,data=ordered) /dev/mapper/vg00-usr on /usr type ext4 (rw,noatime,errors=remount-ro,data=ordered) securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime) tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev) tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k) tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755) cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/lib/systemd/systemd-cgroups-agent,name=systemd) pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime) cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer) cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory) cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,nosuid,nodev,noexec,relatime,perf_event) cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls,net_prio) cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpu,cpuacct) cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset,clone_children) cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio) cgroup on /sys/fs/cgroup/hugetlb type cgroup (rw,nosuid,nodev,noexec,relatime,hugetlb) cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices) cgroup on /sys/fs/cgroup/pids type cgroup (rw,nosuid,nodev,noexec,relatime,pids) systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=30,pgrp=1,timeout=0,minproto=5,maxproto=5,direct) mqueue on /dev/mqueue type mqueue (rw,relatime) debugfs on /sys/kernel/debug type debugfs (rw,relatime) hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime) fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime) /dev/mapper/vg00-home on /home type ext4 (rw,noatime,errors=remount-ro,data=ordered) /dev/mapper/vg00-var on /var type ext4 (rw,noatime,errors=remount-ro,data=ordered) tmpfs on /run/user/0 type tmpfs (rw,nosuid,nodev,relatime,size=1641468k,mode=700) # cat /etc/mdadm/mdadm.conf # mdadm.conf # # Please refer to mdadm.conf(5) for information about this file. # # by default (built-in), scan all partitions (/proc/partitions) and all # containers for MD superblocks. alternatively, specify devices to scan, using # wildcards if desired. #DEVICE partitions containers # auto-create devices with Debian standard permissions CREATE owner=root group=disk mode=0660 auto=yes # automatically tag new arrays as belonging to the local system HOMEHOST # instruct the monitoring daemon where to send mail alerts MAILADDR root # definitions of existing MD arrays ARRAY /dev/md1 UUID=6d35e4d9:3952fbd3:1f51fb89:78ee93fe level=raid1 num-devices=2 devices=/dev/sda1,/dev/sdb1 ARRAY /dev/md3 UUID=682d55c0:d40b40c9:1f51fb89:78ee93fe level=raid1 num-devices=2 devices=/dev/sda3,/dev/sdb3 #ARRAY /dev/md11 level=raid1 num-devices=2 devices=/dev/sdc1,/dev/sdd1 # /usr/share/mdadm/mkconf # mdadm.conf # # Please refer to mdadm.conf(5) for information about this file. # # by default (built-in), scan all partitions (/proc/partitions) and all # containers for MD superblocks. alternatively, specify devices to scan, using # wildcards if desired. #DEVICE partitions containers # auto-create devices with Debian standard permissions CREATE owner=root group=disk mode=0660 auto=yes # automatically tag new arrays as belonging to the local system HOMEHOST # instruct the monitoring daemon where to send mail alerts MAILADDR root # definitions of existing MD arrays ARRAY /dev/md1 UUID=6d35e4d9:3952fbd3:1f51fb89:78ee93fe ARRAY /dev/md3 UUID=682d55c0:d40b40c9:1f51fb89:78ee93fe # mdadm --misc --detail /dev/md1 /dev/md1: Version : 0.90 Creation Time : Wed May 3 16:13:21 2017 Raid Level : raid1 Array Size : 4194240 (4.00 GiB 4.29 GB) Used Dev Size : 4194240 (4.00 GiB 4.29 GB) Raid Devices : 2 Total Devices : 2 Preferred Minor : 1
[Bug 1580308] Re: update-initramfs cryptsetup must correctly take into account PARTLABEL inside /etc/fstab
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: initramfs-tools (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1580308 Title: update-initramfs cryptsetup must correctly take into account PARTLABEL inside /etc/fstab To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1580308/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1580308] Re: update-initramfs cryptsetup must correctly take into account PARTLABEL inside /etc/fstab
I am NOT using 'btrfs'. I am using 'PARTLABEL' in '/etc/fstab'. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1580308 Title: update-initramfs cryptsetup must correctly take into account PARTLABEL inside /etc/fstab To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1580308/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1580308] Re: update-initramfs cryptsetup must correctly take into account PARTLABEL inside /etc/fstab
Are you using btrfs? If so, the relevant Debian bug report is probably https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784881 ** Bug watch added: Debian Bug tracker #784881 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784881 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1580308 Title: update-initramfs cryptsetup must correctly take into account PARTLABEL inside /etc/fstab To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1580308/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1580308] Re: update-initramfs cryptsetup must correctly take into account PARTLABEL inside /etc/fstab
Doing updates with apt-get, I get messages like cryptsetup: WARNING: failed to detect canonical device of /dev/sdXY Besides the warning message, everything seems to run fine. I'm using ubuntu 16.04 with recent updates. related: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=671056 ** Bug watch added: Debian Bug tracker #671056 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=671056 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1580308 Title: update-initramfs cryptsetup must correctly take into account PARTLABEL inside /etc/fstab To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1580308/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1580308] Re: update-initramfs cryptsetup must correctly take into account PARTLABEL inside /etc/fstab
The warning appears although I use UUIDs all over the place in my /etc/fstab. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1580308 Title: update-initramfs cryptsetup must correctly take into account PARTLABEL inside /etc/fstab To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1580308/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1580308] Re: update-initramfs cryptsetup must correctly take into account PARTLABEL inside /etc/fstab
A also need to add that my hard disks are unencrypted from the perspective of the OS (I use hardware encrypted SSDs). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1580308 Title: update-initramfs cryptsetup must correctly take into account PARTLABEL inside /etc/fstab To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1580308/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
