Re: Debian bookwork / grub2 / LVM / RAID / dm-integrity fails to boot
Additional info: On Wed, May 22, 2024 at 08:49:56AM +0200, Marc SCHAEFER wrote: > Having /boot on a LVM non enabled dm-integrity logical volume does not > work either, as soon as there is ANY LVM dm-integrity enabled logical > volume anywhere (even not linked to booting), grub2 complains (at boot > time or at update-grub) about the rimage LV. I found this [1], quoting: "I'd also like to share an issue I've discovered: if /boot's partition is a LV, then there must not be a raidintegrity LV anywhere before that LV inside the same VG. Otherwise, update-grub will show an error (disk `lvmid/.../...' not found) and GRUB cannot boot. So it's best if you put /boot into its own VG. (PS: Errors like unknown node '..._rimage_0 can be ignored.)" So, the work-around seems to be to simple have /boot not on a LVM VG where any LV has dm-integrity enabled. I will try this work-around and report back here. As I said, I can live with /boot on RAID without dm-integrity, as long as the rest can be dm-integrity+raid protected. [1] https://unix.stackexchange.com/questions/717763/lvm2-integrity-feature-breaks-lv-activation
Re: Debian bookwork / grub2 / LVM / RAID / dm-integrity fails to boot
Hello, On Tue, May 21, 2024 at 08:41:58PM +0200, Franco Martelli wrote: > I can only recommend you to read carefully the Wiki: > https://raid.wiki.kernel.org/index.php/Dm-integrity I did, and it looks it does not seem to document anything pertaining to my issue: 1) I don't use integritysetup (from LUKS), but LVM RAID PVs -- I don't use LUKS encryption anyway on that system 2) the issue is not the kernel not supporting it, because when the system is up, it works (I have done tests to destroy part of the underlying devices, they get detected and fixed correctly) 3) the issue is not with the initrd -- I added the dm-integrity module and rebuilt the initrd (and actually the bug happens before grub2 loads the kernel & init) -- or at least "not yet"! maybe this will fail later :) 4) actually the issue is just grub2, be it when the system is up (it complains about the special subvolumes) or at boot time Having /boot on a LVM non enabled dm-integrity logical volume does not work either, as soon as there is ANY LVM dm-integrity enabled logical volume anywhere (even not linked to booting), grub2 complains (at boot time or at update-grub) about the rimage LV.
Re: systemd-resolved resolving fails sometimes on Debian12
On Mon, Mar 04, 2024 at 02:03:32PM +0800, jeremy ardley wrote: > I completely removed system-resolved as when it is installed it changes the > DNS configuration to be non-standard The issues described in this thread are related to libnss-resolve, which is no longer installed in the Debian 12 cloud images. In most cases, I don't recommend removing systemd-resolved, as it is responsible for managing the contents of /etc/resolv.conf based on the information provided in the DHCP lease. If you're managing /etc/resolv.conf yourself, then you can remove systemd-resolved. > > Thank you for the ideas, I may use them but first I would like to do > > something about the obvious bug in systemd-resolved. The name resolution issue with nss-resolve is tracked upstream at https://github.com/systemd/systemd/issues/29069 and the cloud team's response to it is discussed in the thread starting with https://lists.debian.org/debian-cloud/2024/03/msg00017.html The issue is not present in the current cloud images for AWS or other environments. Since the impacted configuration was common to the cloud images but not the default installation, it might have been worth engaging directly with the cloud community. You can file bug reports against cloud.debian.org or reach out to us on #debian-cloud or debian-cl...@lists.debian.org. Most of us aren't regular readers of debian-user. noah (for the cloud team)
Re: Debian bookwork / grub2 / LVM / RAID / dm-integrity fails to boot
On 20/05/24 at 14:35, Marc SCHAEFER wrote: Any idea what could be the problem? Any way to just make grub2 ignore the rimage (sub)volumes at setup and boot time? (I could live with / aka vg1/root not using dm-integrity, as long as the data/docker/etc volumes are integrity-protected) ? Or how to make grub 100% compatible with a vg1/root using dm-integrity (that would be obviously the final goal!) Thank you for any pointers! I can only recommend you to read carefully the Wiki: https://raid.wiki.kernel.org/index.php/Dm-integrity HTH kind regards -- Franco Martelli
