Tails boot failure: "no supported filesystem images found at /live" about ventoy

[Perkolator]

Hooray. Just updated Ventoy to 1.0.16 and tried to boot tails-amd64-4.8.iso and it worked!

[Perkolator]

I just tried to boot tails-amd64-4.8.iso in UEFI mode and it says: "no bootfile found for UEFI". Secure boot disabled in bios and ventoy.

Everything else I tried has been working just fine. Ventoy is the first tool that actually has worked for me, well, almost 100%. :) Amazing tool! Thank you!

These other isos I tried: clonezilla live (both variants), linux mint 20 cinnamon and xfce, kde neon, systemrescuecd, win8.1.1, win10_2004, win10_LTSC_2019_eval.

Just tails wont work. Any ideas why? And should it even? I tried to google about this but I failed to gain more knowledge.

[ventoy]

Please just cat /ventoy/log and send me the log, thanks!

[estevaog3]

Here it's the result of cat /ventoy/log

[ventoy]

I tested tails-amd64-4.0.iso with ventoy-1.0.08 in my laptop (legacy bios) but it worked well :(

[estevaog3]

This could be a hardware specific issue, maybe, I don't know.
I'm downloading tails 4.6, which is the latest release, if it works, then it's fine for me.

[estevaog3]

Just to let you know, @ventoy. I downloaded the Tails 4.6 image for USB, since that's what I'm using. It's a .img file, not .iso. So I copied it to my USB stick and it didn't appeared on Ventoy's menu.
So I appended .iso to the file name, and it appears now, but I can't boot in both UEFI and BIOS mode with my laptop that supports those boot modes.

• In UEFI mode, I got this error after choosing tails on Ventoy's menu:
  
• In BIOS mode, this is the error:
  
  So, a possible workaround it would be to download the version of tails-amd64-4.6 for DVDs, since it's a .iso file. That's what I'm going to try next.

[estevaog3]

So, a possible workaround it would be to download the version of tails-amd64-4.6 for DVDs, since it's a .iso file. That's what I'm going to try next.

I've tested it, and it didn't work.

• In BIOS mode I got the following error:
  
• In UEFI mode I couldn't find the /ventoy/log file (as you can see in the figure below, there's no /ventoy diretory):
  

Let me know If you need some specs about the laptop that I used this time (and in the previous comment as well).

[shigutso]

I'm having the same issue.
I am able to boot Ubuntu, UBCD, Windows 10, Android x86, etc but not Tails OS.
Very old laptop (BIOS only, no UEFI)
Ventoy 1.0.17
Tested tails-amd64-4.8.iso and tails-amd64-4.9.iso

Logs:

============== VENTOY =================
377 blocks
5724 blocks
kenel version=Linux version 5.7.0-1-amd64 ([email protected]) (gcc version 9.3.0 (Debian 9.3.0-14), GNU ld (GNU Binutils for Debian) 2.34) #1 SMP Debian 5.7.6-1 (2020-06-24)
kenel cmdline=BOOT_IMAGE=/live/vmlinuz initrd=/live/initrd.img boot=live config live-media=removable nopersistence noprompt timezone=Etc/UTC block.events_dfl_poll_msecs=1000 splash noautologin module=Tails slab_nomerge slub_debug=FZP mce=0 vsyscall=none page_poison=1 init_on_alloc=1 init_on_free=1 mds=full,nosmt  noapic noapm nodma nomce nolapic nomodeset nosmp vga=normal
remove whole sbin directory
=====ventoy_unpack_initramfs: #/initrd001 0 3037 /initrd001_tmp#
vtx=3037 cat
62 blocks
=====ventoy_unpack_initramfs: #/initrd001 436 3037 /initrd001_tmp#
vtx=3037 cat
5868 blocks
=====ventoy_unpack_initramfs: #/initrd001 212 FD37 /initrd001_tmp#
vtx=FD37 xzcat
311981 blocks
Now hand over to ventoy.sh
#### install vtoytool #####
try /ventoy/tool/vtoytool/00/ ...
vtoytool_64 OK
use vtoy_fuse_iso_64
use unsquashfs_64
use unsquashfs_64
kernel version
Linux version 5.7.0-1-amd64 ([email protected]) (gcc version 9.3.0 (Debian 9.3.0-14), GNU ld (GNU Binutils for Debian) 2.34) #1 SMP Debian 5.7.6-1 (2020-06-24)
OS=###debian###
##### distribution = tails ######
ventoy_os_install_dmsetup /dev/sdb ...
device mapper module is NOT loaded, now load it...
KO=/lib/modules/5.7.0-1-amd64/kernel/drivers/md/dm-mod.ko
dmsetup install finish, now check it...
No devices found
dmsetup work ok
create_ventoy_device_mapper /dev/sdb --readonly
dmsetup avaliable in system /sbin/dmsetup
device-mapper module check success
==== create ventoy device mapper success ====
replace block device link /dev/sdb2...
sdb2 is USB device

[Perkolator]

tails-amd64-4.9.iso working here in UEFI and GPT (secure boot disabled) just fine with Ventoy 1.0.17.

[shigutso]

Just tested Ventoy 1.0.18 on the same laptop after checking the changelog
tails-amd64-4.9.iso now boots!

Thanks @ventoy :D

[Perkolator]

tails-amd64-4.9.iso working in UEFI and GPT (secure boot disabled) with Ventoy 1.0.18, BUT, it's really slow now, booting and opening programs after boot to the desktop. With Ventoy 1.0.17 it was fast/normal. Every other iso is working just fine and not slow.

[Zeik0s]

tails-amd64-4.12.iso doesn't work with Ventoy 1.0.27 🤔

[Perkolator]

tails-amd64-4.12.iso doesn't work with Ventoy 1.0.27

It works but it is super super super slow to start and use.. like I described in my previous message. Something changed in Ventoy 1.0.18 which made Tails awfully slow.

[ventoy]

What about the latest Ventoy release?

[Zeik0s]

Will recheck and give feedback when i tried.

[Perkolator]

tails-amd64-4.23.iso is still a tad slow to load up but then on desktop using it seems to be just normal, every application I tried to open was quite fast to open. No complaints from me. Thanks for ventoy, great tool.

[ventoy]

OK I will close it now.
If you still have problem with latest Ventoy release, you can reopen the issue.

[gthubs]

UPD: This comment is useless. Looks like a problem was not in Ventoy

Hello, I had similar problem with lastest versions (tails-amd64-4.23.iso and Ventoy 1.0.55)

The main problem is that loading tails in UEFI mode takes almost 3 times longer than in BIOS (legacy) mode: 1 minute 30 seconds vs 36 seconds! In UEFI mode for about 1 minute I don't see any activity (flash and HDD LEDs are not blinking), why is there such a delay?

Also I'm using a flash drive with a write protect switch. If protection is active, then in UEFI mode, tails does't load at all, after 1:30 an error:

mount: mounting /dev/mapper/ventoy on /live/medium failed: No such file or directory error
No supported filesystem images found at /live

In /ventoy/log I see

create_ventoy_device_mapper /dev/sde
dmsetup avaliable in system /ventoy/tool/dmsetup
device-mapper module check success
device-mapper: reload ioctl failed: Read-only file system
Command failed
=== create ventoy device mapper failed ====

In legacy mode, there are no problems, loading is fine with write protection enabled.

P.S Thanks to the developer for Ventoy, a great utility. I really hope that he can solve the problems with UEFI

[steve6375]

I have not checked recent versions, but Tails may try to modify the USB drive on first boot?
https://rmprepusb.blogspot.com/2020/01/direct-uefi64-boot-from-tails-24-using.html

[gthubs]

I have not checked recent versions, but Tails may try to modify the USB drive on first boot? https://rmprepusb.blogspot.com/2020/01/direct-uefi64-boot-from-tails-24-using.html

No, I checked isolinux\live64.cfg in tails-amd64-4.23.iso, there is no union=aufs parameter

My problem partially decided. I downloaded Tails-AMD64-4.23.img instead of Tails-AMD64-4.23.ISO, now loading in UEFI mode occurs without errors and quickly, but only when the flash drive is connected to the USB port 2. When using USB 3.0, the problem remained, but I think the reason is not in Ventoy, but in the Tails itself or in my old computer

[ventoy]

@gthubs
Use this CI release to see whether still with the long delay in UEFI mode for the ISO file.
https://github.com/ventoy/Ventoy/actions/runs/1359055022

[gthubs]

@ventoy Yes, this version solved the long startup problem in UEFI! With Ventoy 1.0.55, the loading tails-amd64-4.23.iso is 1:36 (from the moment I select tails in Grub and until the welcome screen appears), after updating to 10191236 the time was reduced to 0:38. I checked it about 10 times on 2 flash drives.

Thanks a lot for the quick fix, I hope it will be included in the next release. Is there any hope of getting tails to run in UEFI with drive write protection?

[ventoy]

@gthubs
The fix will be included in the next release.
Currently I have no idea about why legacy BIOS OK but UEFI fail when you enable the hardware protection.
So

1. When you enable hardware protection whether other ISO boot ok in UEFI mode?(e.g. Ubuntu/Debian ...)

[gthubs]

@ventoy
I've tried kubuntu-21.10-desktop-amd64.iso and debian-live-9.13.0-amd64-xfce.iso -no problems with flash drive write protection enabled and on any USB port (3.0 / 2.0). I found out that Tails-AMD64-4.23.img (not iso) is also capable of booting with write protection enabled, but only when using a USB 2.0 port. I am satisfied with this option, perhaps the problem is in the Tails distribution itself (if I have time I will try to write it without ventoy and check)

[ventoy]

OK.
Ventoy can work OK even USB hardware protect is enabled, this is an important and valuable feature of Ventoy.
So as you said, the problem may be in the Tails distribution itself since other distros work OK.