GNUinOS - Libre

aitor · 2026-03-19 11:48:10

@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.

prospero · 2026-03-19 20:17:51

aitor wrote:

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).

aitor · 2026-03-19 21:31:23

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`

aitor · 2026-03-20 12:39:28

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.

aitor · Yesterday 01:33:27

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 pbkdf2

and d-i with encryption worked. I updated the image.

prospero · Yesterday 21:15:45

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.

aitor · Yesterday 21:39:36

are you in qemu?

prospero · Yesterday 23:11:01

Yes, QEMU/KVM on virt-manager.

aitor · Today 02:00:21

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_console

3) 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) exit

Thanks a lot for your patience, prospero!!

Last edited by aitor (Today 02:09:59)

prospero · Today 15:01:22

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?

aitor · Today 20:37:31

Same at me.

I managed installing the image with Qemu and the following steps in BusyBox worked for me:

Load modules

(initrmafs) modprobe  virtio_pci
(initrmafs) modprobe  virtio_blk
(initrmafs) modprobe  virtio_scsi
(initramfs) modprobe ext4

Check partitions:

(initramfs) cat /cryptroot/crypttab | cut -d: -f1
vda3_crypt
(initramfs) blkid | grep crypto_LUKS | cut -d' ' -f1
/dev/vda3

Unlock vda3_crypt (adapt it to your needs) typing your encryption password:

(initramfs) cryptsetup luksOpen /dev/vda3 vda3_crypt
Enter passphrase for /dev/vda3:

Activate LVM:

(initramfs) lvm vgchange -ay

Scan /dev/mapper with ls -l /dev/mapper and mount the *-root logical volume (don't forget to load the ext4 module first):

(initramfs) mount /dev/mapper/genuen--vg-root /root

At this point, the way to get out of Busybox isn't that straightforward. Like live-boot, most of initramfs scripts leave a trace when they run. To prevent BusyBox from asking you to unlock vda3_crypt again after exiting (a process that will fail because the device is busy), we manually create the said control file so that the system can find it and recognize that the mountpoint already exists:

touch /run/initramfs/fsck-root

Now we make use of switch_root in order to replace the current process with the real system:

exec switch_root /root /sbin/init

Good look!

Last edited by aitor (Today 21:09:36)

The officially official Devuan Forum!

#251 2026-03-19 11:48:10

Re: GNUinOS - Libre

#252 2026-03-19 20:17:51

Re: GNUinOS - Libre

#253 2026-03-19 21:31:23

Re: GNUinOS - Libre

#254 2026-03-20 12:39:28

Re: GNUinOS - Libre

#255 Yesterday 01:33:27

Re: GNUinOS - Libre

#256 Yesterday 21:15:45

Re: GNUinOS - Libre

#257 Yesterday 21:39:36

Re: GNUinOS - Libre

#258 Yesterday 23:11:01

Re: GNUinOS - Libre

#259 Today 02:00:21

Re: GNUinOS - Libre

#260 Today 15:01:22

Re: GNUinOS - Libre

#261 Today 20:37:31

Re: GNUinOS - Libre

Board footer