The fix is already in git:
https://salsa.debian.org/grub-team/grub … f6acddbba9

Correct. It's the user that has to change their behavior. On the second run of the installer, don't partition the disk. Use the partitions you created on the first run.

Yes, runit-init. I have the same symlinks for /sbin/init and /sbin/shutdown.

gettys and ssh had run scripts before the runit-services package existed. My daedalus-runit doesn't have that package. Last time I ran apt-upgrade on that VM was March 2022. It still has kernel 5.15.

My /usr/share/runit/meta has the same as yours plus acpid and irqbalance. I think I got the acpid scripts from the antix collection (run script is identical) but I don't know where the irqbalance script came from.

I did a chimaera-runit upgrade to daedalus over a year ago, before the runit-services package existed. Did you run into any conflicts between extra run scripts you added and the ones from the services package?

Try the mini.iso. At the boot menu, select Advanced options, then Expert Install. You can choose to install daedalus, excalibur or ceres right after the mirror selection. This one boots uefi mode in qemu for me.
https://pkgmaster.devuan.org/devuan/dis … t/mini.iso

I think you need to install shim-unsigned before running the installer. There's also a shim-signed package that I assume goes with the grub*signed packages. You might need to install the necessary signed packages or possibly turn off secure boot.

There's no need to backport a newer version. Pull the source from daedalus to alter the version in daedalus.

If you used 'adduser' to create the user, the primary group of the same name will be created at the same time. The user will also be added to the users group but will not be added to other groups unless you made some changes to the EXTRA_GROUPS settings in /etc/adduser.conf.

id <username> will show you what groups a user belongs to.

It sounds like you installed the bootloader to the flash drive instead of the internal hard drive or didn't install the bootloader at all.

Boot the system with the flash drive plugged in. Open a terminal and as root (or with sudo) run fdisk -l to see which drive is which. I assume this system uses legacy bios boot. If it's uefi, we need to talk more before you do anything else.

Then you can run grub-install and update-grub. Assuming that fdisk tells you that /dev/sda is your internal hard drive, run the following.

grub-install /dev/sda
update-grub

Change sda to whatever is really your first hard drive if it's not showing drives in the right order. Sometimes booting from usb results in a mis-match between what grub sees and what the kernel sees.

Then you should be able to reboot and start the system without the flash drive.

czeekaj,

I recently changed something in refractasnapshot regarding encryption. In 10.3.0 (in daedalus) you can turn off the initrd check for encryption support because cryptsetup changed. There's no longer an option in /etc/initramfs-tools/initramfs.conf for CRYPTSETUP=y. I'm pretty sure this applies to Chimaera, too. Look in /etc/refractasnapshot.conf for more details.

Here's that section in the conf file:

# Change this to "no" (or comment it) to turn off all initrd checks. 
# In Bookworm/Daedalus use this instead of initrd_crypt=yes 
# if you want encrypted persistence. Make sure to have all necessary
# cryptsetup packages installed.
initramfs_checks="yes"
# Prepare the initrd to support encrypted volumes. Uncomment this
# if you plan to use the snapshot on a live usb with an encrypted
# persistent volume. This will edit /etc/cryptsetup-initramfs/conf-hook
# to set CRYPTSETUP=y (This does not work right in Bookworm/Daedalus)

#initrd_crypt="yes"

For xfs support you need to install something in the system, and it will be included in the snapshot. When it comes to installing with refractainstaller, pre-format your xfs partitions and tell the install not to format.

For multiple grub types, the way I deal with it is to have grub-efi-amd64 and efibootmgr installed, also all of the grub-*-bin packages installed, and then put the deb packages for grub-pc and grub-efi-ia32 in the root of the filesystem before you make the snapshot. If you boot in bios mode, the installer will ask if you want to copy grub-pc and install the bootloader. I don't know anything about grub-coreboot, but if it's a replacement for grub-pc, you could include the deb package and install it manually at the proper time or maybe edit the script to use it. (I'd have to look at my code to recall how/where to do that.)

For me, amd64 netinstall iso work on bare metal in bios or uefi modes.

I can't get that iso to boot in qemu or virtualbox in uefi, but bios mode works.
The sfdisk activate trick didn't help.
If I attached the cdrom to the sata interface in vbox, I could hit ESC and then exit to get to the uefi menu that includes "Boot from file" but I couldn't get any files to boot.

I can't get the rc5 netinstall iso to boot in uefi mode in qemu or vbox.

For the hardware boots, I used a usb stick prepared with dd.

The bootloader section of the installer does not give you a choice of uefi or bios. That choice is made when you boot the system. You can check this by booting the installer media and when you get to the first screen asking about locale, press alt-F2 to open a shell and run ls /sys/firmware/efi and if that directory exists, you booted in uefi mode.

If the boot device menu doesn't exist or doesn't give you a choice between legacy or uefi for the usb, then check your motherboard settings for the boot order or possibly whether to use legacy or uefi first on removable media.