[vDisk] failed to open 'dev/nvme0n11' in read-only mode ...

[matfeb]

Hi,

I'm trying to use a Ubuntu 20.10 vdi file but I have an error message.

[      0.469404] Initramfs unpacking failed : Decoding failed
[      1.779512] psmouse serio1 : synaptics : Unable to query device : -5
ERROR: failed to open '/dev/nvme0n11' in read-only mode: No such file or directory
Failed to mount exfat fs -5
Failed to find image location

I have installed ubuntu 20.10 64 bits in Virtual Box on a Windows 10 64 bits system with the help of your documentation, then launched the ventoy script to transform the vdi.

Regards,

[ventoy]

Initramfs unpacking failed
Is the vdi file corrupted? Did you copy the vdi file to USB stick and boot from Ventoy or you boot the vdi file in your hdd and boot with Ventoy?

Please check that whether the vdi file still boot ok in the virtualbox?

[matfeb]

Ok, well I have a particular configuration.

Is the vdi file corrupted? Did you copy the vdi file to USB stick and boot from Ventoy or you boot the vdi file in your hdd and boot with Ventoy?

I'm not booting from an USB key, I have a Thunderbolt 3 case with an nvme inside. But it's the same as an USB key.
ISO are working great by the way.

Image is working in VirtualBox, I've just tried. Linking the vdi file to the VM from the NVMe external disk.
I have tried to change the controler device from SATA to NVMe but it's not working.
Now I have a black screen instead of error messages.

[matfeb]

I have booted in rescue mode and I have one more error message :

Lockdown: vtoydump: /dev/mem,kmem,port is restricted; see man kernel_lockdown.7
ERROR: failed to open '/dev/nvme0n11' in read-only mode: No such file or directory
Failed to mount exfat fs -5
Failed to find image location

https://www.mankier.com/7/kernel_lockdown

I'm booting with secure boot but I authorized the bios as written in your documentation.

[matfeb]

Ok, I have disabled the secure boot and the system is booting.

It seems that vdi is not compatible with secure boot ?

[ventoy]

Maybe something about kernel_lockdown feature. It is automatically turned on when secure boot in enabled.
I'm not very sure and will test it later.

[matfeb]

Ok thanks.
Anyway if I disable secure boot, it's working.

[ventoy]

OK. I have fixed it. It will be ok in the next Ventoy release.
If you want you can also try it as follows:

1. Boot the vdi file in VirtualBox. Download and run the latest vtoyboot-1.0.8 https://github.com/ventoy/vtoyboot/releases/tag/v1.0.8

2. You need to update grub.cfg file in the VTOYEFI partition on the disk which Ventoy installed.
   The grub.cfg file is in grub\grub.cfg and the latest is in https://github.com/ventoy/Ventoy/blob/master/INSTALL/grub/grub.cfg

[matfeb]

Ok thanks, let me try tomorrow I will give you a feedback and close the issue.

[matfeb]

Ok it's working with secure boot.
Many thanks !