You are not logged in.
@prospero: could you give me some details about the circumstances that led you to that point? I upgraded an encrypted gnuinos daedalus disk using vdev to genuen excalibur, and everything is working fine. Vdev recognizes the /dev/mapper/gnuinos--vg-root volume from the original installation, despite the annoying mdadm-related messages.
If you work systematically, things will come by itself (Lev D. Landau)
Offline
Vdev recognizes the /dev/mapper/gnuinos--vg-root volume from the original installation, despite the annoying mdadm-related messages.
I have been running the live system then text-installing on a VM, first without LVM then both with and without LVM.
At some point I tried the automated install with LVM, which is when I got the message about /dev/mapper/devuan--vg-root (instead of /dev/mapper/genuen--vg-root).
Offline
Thanks, prospero.
My installation attempt was interrupted here:
grub-installer: grub-install: error: attempt to install to encrypted disk without cryptodisk enabled.
Set `GRUB_ENABLE_CRYPTODISK=y` in file `/etc/default/grub`If you work systematically, things will come by itself (Lev D. Landau)
Offline
It seems that libcryptseup-udeb is using the argon2id algorithm in Excalibur, but grub < 2.14 doesn't support it. It's possible to rebuild the udeb package, but i'll try to configure LUKS2 within the preseed.cfg file giving preference to the standard pbkdf2 algorithm in d-i. On the other hand, cryptsetup-initramfs was missing in the system.
If you work systematically, things will come by itself (Lev D. Landau)
Offline
I added the following lines to the preseed.cfg file:
# Explicitly force the use of LUKS2
d-i partman-crypto/crypto_type string luks2
# Pass the specific arguments to cryptsetup
# grub-2.12 is not compatible with argon2id algorithm; use PBKDF2 instead
d-i partman-crypto/passphrase/options string --pbkdf pbkdf2and d-i with encryption worked. I updated the image.
If you work systematically, things will come by itself (Lev D. Landau)
Offline
There must be something wrong with the VM settings here. After installing with encryption I am getting:
cryptsetup: Waiting for encrypted source device
UUID=123456x7-8y90-*...
Gave up waiting for root file system device.Followed by the usual idle BusyBox.
Offline
Yes, QEMU/KVM on virt-manager.
Offline
First, I've been running all my tests in Legacy BIOS, but today I discovered that a dependency was missing for grub-efi-amd64, that is, grub-efi-amd64-unsigned. Therefore, I've updated the ISO to prevent the installer from failing.
Second, I guess that some virtio modules are missing in the initrd. Can you try the following commands in the BusyBox console?
1) Check whether the nodes in /dev have be created:
(initramfs) ls -l /dev/vda*For sure, you won't get anything, even thought vdev doesn't ignore them (lines 93-96 in vdevd/helpers/LINUX/disk.sh).
2) Ensure that vdev is still running (via `pidof vdevd`) as it ought to be because the init-bottom scripts have not been invoked yet. Then try to load the following modules:
(initrmafs) modprobe virtio_pci
(initrmafs) modprobe virtio_blk
(initrmafs) modprobe virtio_scsi
(initrmafs) modprobe virtio_ring
(initrmafs) modprobe virtio_console3) Check again the nodes:
(initramfs) ls -l /dev/vda*Do they appear now? If so, you would be able to go ahead with the boot process by exiting:
(initramfs) exitThanks a lot for your patience, prospero!!
Last edited by aitor (Today 02:09:59)
If you work systematically, things will come by itself (Lev D. Landau)
Offline
Yes, the vda* nodes now appear, but I am sent back to the Box with:
ALERT! /dev/mapper/genuen--vg-root does not exist. Dropping to a shell!Should I edit the content of /proc/cmdline, or should /dev/mapper/ be populated in some way?
Offline