Bug#641230: Can't complete installation due to warning about unencrypted swap
Package: installation-reports Image version: debian-testing-i386-netinst.iso (weekly-build, calendar week: 36, md5sum of iso: 39150c40504b2ca239ce072bf9882d0d) Boot method: USB stick (used iso image) Initial boot: [O] Detect network card:[O] Configure network: [O] Detect CD: [O] Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [E] Install base system:[ ] Clock/timezone setup: [ ] User/password setup:[ ] Install tasks: [ ] Install boot loader:[ ] Overall install:[ ] Comments/Problems: Installation gets started from USB-Stick (which was created by above mentioned iso-image) to a harddisk - both devices are connected via USB. The partition layout configured within the partitioner is this: http://nanl.de/debian/IMG_20110911_211158.jpg The error I get when selecting "Finish partitioning" and confirming the upcoming dialog by clicking "Yes" is this: http://nanl.de/debian/IMG_20110911_211143.jpg As a matter of fact there is no swap active, as indicated by: a) 'mount | grep swap' b) 'cat /proc/meminfo | grep SwapTotal' c) 'swapoff -a' doesn't do anything / doesn't help c) the partition layout itself (no unencrypted swap partition created) Inside the error I get presented two choices: "Go Back" and "Continue" - however both drop me back into the partitioner, so I'm not able at all to continue the installation. Regards mirko -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4e6d1649.5000...@nanl.de
Bug#641230: Can't complete installation due to warning about unencrypted swap
Addition: When deleting the swap-LV inside the partitioner - therewith not going to create swap-space - the error does not occur and I'm able to continue and complete the installation. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4e6d1ce5.3070...@nanl.de
Bug#980782: os-prober: linux-boot-prober returning "root=/dev/dm-X" line instead of expected "root=UUID=[UUID128]
Package: os-prober Version: 1.77 Severity: important I noticed when running update-grub on Debian stable and testing, that the resulting grub.cfg has lines as part of menuentres like: "linux [..] root=/dev/dm-X" for found linux installations on other block devices - in my case residing on LVs - ,instead of "root=UUID=[XXX]", which I'd have expected (and would favour). This is due to `linux-boot-prober` calling `mapdevfs` defined in "/usr/share/os-prober/common.sh". `mapdevfs` does a simple `readlink` on the path given. The other lines within the menuentry look fine, e.g.: "set root='lvmid/XX/YY'" or "search [..] --set=root [UUID]" GRUB_DISABLE_LINUX_UUID is undefined. Is this intentional and if so, why? -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (900, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-1-amd64 (SMP w/8 CPU threads) Kernel taint flags: TAINT_USER, TAINT_WARN Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages os-prober depends on: ii grub-common 2.04-12 ii libc62.31-9 os-prober recommends no packages. os-prober suggests no packages. -- no debconf information
Bug#980782: Acknowledgement (os-prober: linux-boot-prober returning "root=/dev/dm-X" line instead of expected "root=UUID=[UUID128])
Just adding, this isn't only a feature request but results in
non-bootable systems.
If one of the os-probe'd systems e.g. is also a Debian, it will drop
into an initramfs due to not finding the root device.
This is due to - within the initramfs - the VGs as part of the the LVM
system only get activated by certain naming schemes
("/usr/share/initramfs-tools/scripts/local-top/lvm2").
It tries ti figure out whether the rootfs resides on a LVM and if it
thinks it doesn't, the respective VG won't be activated, resulting in
the passed /dev/dm-X block device not being available.
Bug#980782: Info received (Bug#980782: Acknowledgement (os-prober: linux-boot-prober returning "root=/dev/dm-X" line instead of expected "root=UUID=[UUID128]))
Looking at /usr/share/initramfs-tools/scripts/local-top/lvm2 more closely, passing a UUID also wouldn't trigger a `vgchange -ay` here. But a path like /dev/mapper/X would. So maybe the question is rather: how to make os-prober return a "root=/dev/mapper/X" line instead of one containing a UUID(?)
