antiX live usb issue

[fehlix]

Have you tried different USB ports - different USB-sticks? (Hint: power-supply and consumption differs on sticks and ports)
Have you tried also with dd-live-usb?
Probably also a good idea to show Quick System Info ( inxi -Fxrz) from the problematic system.

[BitJam]

I had already looked at the version in antiX-17.4 and it was up to date along with the cli-shell-utils library. That read error really looks like a fragmentation problem. Running e4defrag should have fixed it. The problem seems to be that we are getting fragmentation that can't be fixed which prevents syslinux from reading the vmlinuz file.

The only other trick I have is to try the --force=nofuse option with the command line live-usb-maker program. I

We started seeing fragmentation errors after we started using fuseiso to mount the iso file. We fixed this in two ways, first we used cpio to copy the files to the new live-usb and then we also run e4defrag on vmlinuz. This is a subtle error. The files are getting copied correctly but timing issues change where on the "physical" device they get written.

I chose to always use fuseiso, not just when we need it so we would be more likely to catch errors like this.

AHA! antiX and MX use different versions of fuseiso so I think using --force=nofuse may fix it.

AntiX uses fuseiso-20070708-3.2+b1 while MX uses fuseiso9660-0.3-1.1+b1

[BitJam]

Turns out the executables in those two packages have different names "fuseiso" versus "fuseiso9660" but we were only looking for "fuseiso" so it was not being used at all in MX. Therefore the --force=nofuse should fix it in antiX.

[rs55]

kernels:
antix: 4.9.....
mx : liquorix 5.0........

[rs55]

You nailed it!
Running the cli version with --force=nofuse from antiX did the trick.

So- now I have a question:
If the only reason the live-usb was working in MX was because of a "bug" where it was asking for fuseio9660 rather than the correct name - just fuseio, is it likely this will get "fixed" in an mx update - which will cause that to also not work !!

I would like to bake this "nofuse" into the gui version - because I am now worried that using a live usb with persistence turned on and doing occasional remasters is going to fail in mx ??

[rs55]

In my antix, I uninstalled fuseiso and installed fuseiso9660. And now the gui works as well !!

So - now - I understand it is only working because the live-usb-maker is looking to run fuseio and failing to find it !

I dont understand all the details behind this fuseiso business, but live-iso is a critical part of mx and antix, so please dont run fuseiso just to experiment . At least not in the published versions of mx and antix.

[anticapitalista]

You nailed it!
Running the cli version with --force=nofuse from antiX did the trick.

So- now I have a question:
If the only reason the live-usb was working in MX was because of a "bug" where it was asking for fuseio9660 rather than the correct name - just fuseio, is it likely this will get "fixed" in an mx update - which will cause that to also not work !!

I would like to bake this "nofuse" into the gui version - because I am now worried that using a live usb with persistence turned on and doing occasional remasters is going to fail in mx ??

I'm seeing the same only with the gui live-usb-maker-gui-antix on antiX. The cli app (live-usb-maker) works ok without --force=nofuse

[fehlix]

I would like to bake this "nofuse" into the gui version - because I am now worried that using a live usb with persistence turned on and doing occasional remasters is going to fail in mx ??

Don't reacall fuseiso is used during remaster.

I dont understand all the details behind this fuseiso business, but live-iso is a critical part of mx and antix, so please dont run fuseiso just to experiment . At least not in the published versions of mx and antix.

There was a reason to introduce additonaly fuseiso, as within other situations live-usb-maker would fail without fuseiso, related to issue of loop-mounts on overlays mounted filesystems.
So it was rarely reported that fuseiso fail, we might consider to default / preselect to most appropriate alternative, imho.

[rs55]

Other than live-usb-maker , what other apps are using fuseiso?
I ask, because , if I uninstall it ( which makes live-usb work for me), i wonder if something else is going to break?

[Adrian]

Other than live-usb-maker , what other apps are using fuseiso?
I ask, because , if I uninstall it ( which makes live-usb work for me), i wonder if something else is going to break?

If something breaks when you remove it, then that package should declare fuseiso as a dependency.