Problem with EasyOS

[measter]

This CI release should have fixed it.
https://github.com/ventoy/Ventoy/actions...2257350810
https://www.ventoy.net/en/doc_github_ci.html

I've used CI #776 to get past the dax obstacle on Easy /dax/dax.ko not found which was successful in getting to the EasyOS boot menu and process, but does not boot EasyOS 3.4.5 or 3.4.7 to the desktop.

I'm not a developer/coder; I'm just a previously Windows now longtime linux user of intermediate expertise.  My experience w/ Ventoy from linux Web has been very good/ excellent/ for dozens of linux distro/s; previously I used Win Yumi for multibooting. The purpose of this report is to rebut some information present at several pages at Ventoy which say Easy OS works w/ Ventoy.

Easy OS,
28 EasyOS
easy-2.3.2-amd64.img

I'm not rebutting the last example in terms of that old v. of Easy, because the current v. of EasyOS is 3.4.7 and my testing has been w/ current Ventoys 1.0.51-1.074  + the Ventoy CI #776 which is 05080402. 

There are currently 2 Ventoy-related topics at the EasyOS forum, one started by someone about the /dax/dax.ko issue which I consider solved by the Ventoy CI #776, and one started by me about the /real/ problem for EasyOS and Ventoy.
https://forum.puppylinux.com/viewtopic.php?t=5980

Basically, the problem is that Easy's modus operandi at boot time causes it to need to write an .sfs

One-time only operation, creating a snapshot of EasyOS
This will allow future follback with the Easy Version Control Manager
Populating: /mnt/ventoy2/easyos/releases/easy-3.4.7
initrd vmlinux easy.sfs cp: write error: No space left on device
This copy failed:
cp /mnt/ventoy1/easy.sfs /mnt/ventoy2/easyos/sfs/easyos/oe/dunfell/easy_3.4.7_amd64.sfs
It is possible that the drive is failing.
Attempting to copy again...
cp: write error: No space left on device

That attempted boot was Ventoy upped to CI #776 or 05080402 which solves the failure at the dax step.