I tried the traditional method from @51lieal 's guide and following links :
and achieved this structure with a few changes in the code (luks2, no header or separate boot and header etc):
Install was successful, except for two error messages which didn’t prevent a successful boot.
- For the lvcreate commands for root-pool and vm-pool
“/usr/sbin/dmeventd: stat failed: No such file or directory
WARNING: Failed to monitor qubes_dom0/root-pool”
- During the first reboot, the lightdm.service failed to start and a couple of lines of Ext2fs4 errors came up. I just rebooted again, and the “complete configuration” gui came up. The rest went well to a successful boot.
One funny thing is happening though.
The luks encrypted sdb4 appears as a device in the USB applet.
When mounted in an AppVM, it appears with a lock symbol and asks for password when clicked.
On password supply, it again reappears as unencrypted drive in the applet. This time the options exclude the AppVM where it was decrypted.
If I mount this in another AppVM, it doesn’t appear at all. I even followed the steps creating a Volume-group “qubes_storage” etc replicating the steps for root-pool and vm-pool, including the ext4 filesystem formatting. The outcome is the same.
Any hints or suggestions please?