Would be interesting which kind of M2 device the OP has in his PC.

I have installed ASCII on a M2 nvme device without issues. I used a gparted live CD to pre-partition the disk. But also the installer should be able to do the job in manual mode.

Good luck, Rolf

The nvme SSD does not matter. ASCII also installs easily on nvme.

The issue is grub and efi with Beowulf, refer to https://dev1galaxy.org/viewtopic.php?id=2676.

Needs to be fixed in the installer.

Rolf

What hinders you to use fstab? I mount ntfs partitions with boot with entries like:

# Windows
UUID=xxxxxx 	/mnt/Windows	ntfs-3g		rw,uid=1000,gid=1000,auto,users

Works like a charm for many years already.

Rolf

Are you sure you get a root terminal? Or is the prompt more like this one:

username@computername:~$ 

Rolf

I can confirm that it is present on ASCII CD/DVD 1 and the Beowulf netinstall dated Feb 19.

The selection is only possible in expert mode as mentioned before. Look for "Load installer components from CD". In there tick the second choice from the top: "choose init". The selection itself happens as one of the last topics in the install before reboot.

Rolf

Observation: you haven't set a path in the script.

2nd guess: trying to write a log during shutdown might not work.

Regards, Rolf

Are the cryptdisk erros to be expected?

Thanks, Rolf

Would be easier if I could paste in a screenshot. I don't like these external file sharing hosters.

With the local declaration, I get the following display:

[ ok ] Unmounting local filesystems ... done
* ERROR: cryptdisks failed to stop
* ERROR: cryptdisks-early failed to stop

The shutdown is fast as expected now.

Without the declaration there are additional messages.
When checking my secondary PC again versus the encrypted VM on my main PC, it now looks like the messages I see are related to missing devices in a USB multi-card-reader. They also appear during the boot in an early phase.

The messages look like this:

  /dev/sdc: open failed: No medium found
  /dev/sdd: open failed: No medium found
  /dev/sde: open failed: No medium found
  /dev/sdf: open failed: No medium found
  /dev/sdg: open failed: No medium found

Rolf

Tried to find the line

local dst src key opts opencount major minor

in the new file as a hook or any hint for the patch that shuts down the LVM before the luks container, and failed.

I was able to apply the patch for ASCII, the patch and the description was sufficient for me. But for the new situation in Beowulf I do not understand enough about scripting and scripts to understand in detail what is happening there and how to possibly attack the problem.

To clarify: I got an LVM inside the luks container.

My impression: the new cryptdisks-functions just looks at encrypted volumes and does not take into account that a LVM may be included.

Thanks, Rolf

Remark: I use the classical setup with an un-encrypted boot partition, a system partition which is encrypted, and on top of that a LVM with at least two volumes for root and swap.

This is a feature request. Please add mate-tweak to at least mate-desktop-environment-extra. In Buster, this is done.

Helps to adjust the behaviour.

Is this worth to raise a bug request?

Thanks, Rolf

Tested your proposal on my faulty VBox Beowulf on efi. Works, removing  grub-efi-amd64-signed followed by a  grub-install does the job.

Maybe this post will help others.

Have a nice evening, thank you again, Rolf

BTW: my secondary PC now is on Beowulf. Some questions remain for other threads.

Thank you, that description contains the amount of detail I needed. The grub-efi-amd64-signed really was installed, I must have overlooked that fact in my previous searches.

Then I did grub-install --bootloader-id=debian followed by an update-grub.

Now I have got a non-working devuan efi entry, and a working debian efi entry. In any case, now I am logged in as root on my secondary PC.

I think I spend a grub-install --bootloader-id=devuan later.

Thank you for your help, Rolf