antiX live usb issue

[dolphin_oracle]

I've been running some tests, with different compression schemes and kernels, and so far I cannot reproduce the issue rs55 is having with the latest LUM tools.

I've been using MX-18 with the liquourix 5.0.3 kernel, as well as the stock MX 4.19 kernel, and lz4, lzo, and default snapshot compression options.

is there another variable to test?

This is all with stretch repos. Should I try the testing ones?

[rs55]

I've been running some tests, with different compression schemes and kernels, and so far I cannot reproduce the issue rs55 is having with the latest LUM tools.

I've been using MX-18 with the liquourix 5.0.3 kernel, as well as the stock MX 4.19 kernel, and lz4, lzo, and default snapshot compression options.

is there another variable to test?

This is all with stretch repos. Should I try the testing ones?

Hi Dolphin: Did you upgrade the LUM today? If so , both fuseiso and fuseiso9660 should be installed and the latest versions of lum.
Looks like you are also using thinkpads from my generation! If it all works for you - then I am indeed an outlier and maybe folks can stop worrying about my specific issue. I have gone back to yesterday's version of things that works on my machines - and will avoid upgrading anything for now. I am also on liquorix 5.0.1 and use lz4. My systems are stable - so I am off to do my taxes!

[BitJam]

Looks like you are also using thinkpads from my generation! If it all works for you - then I am indeed an outlier and maybe folks can stop worrying about my specific issue. I have gone back to yesterday's version of things that works on my machines - and will avoid upgrading anything for now. I am also on liquorix 5.0.1 and use lz4. My systems are stable - so I am off to do my taxes!

It seems like you are tired of working on this and I don't blame you. I'd be tired of it too. Thank you so much for all the help you have provided us. You've gone over and above the call of duty. It is users like you who help us improve MX and antiX! Thank you!

Even if the problem is only on your system, I'd still like to track it down and figure out what is going on. If you ever want to return to this someday, the first thing I would suggest is to make sure only one live-usb is plugged in when you boot. If you have two live-usbs plugged in then the kernel from one could be trying to read the linuxfs file from the other and cause the lz4 problem.

In hindsight, when I asked you to run "dmesg | tail" after the live-usb failed to boot, I should have also asked you to run "uname -r" to be sure of what kernel was running. If you can create live-usbs that gives that lz4 error with a kernel that has lz4 support, especially if they can do it reliably when booted on a variety of systems then I would dearly love to get my hands on one.

Again, thank you for all of your help.

[rs55]

Looks like you are also using thinkpads from my generation! If it all works for you - then I am indeed an outlier and maybe folks can stop worrying about my specific issue. I have gone back to yesterday's version of things that works on my machines - and will avoid upgrading anything for now. I am also on liquorix 5.0.1 and use lz4. My systems are stable - so I am off to do my taxes!

It seems like you are tired of working on this and I don't blame you. I'd be tired of it too. Thank you so much for all the help you have provided us. You've gone over and above the call of duty. It is users like you who help us improve MX and antiX! Thank you!

Even if the problem is only on your system, I'd still like to track it down and figure out what is going on. If you ever want to return to this someday, the first thing I would suggest is to make sure only one live-usb is plugged in when you boot. If you have two live-usbs plugged in then the kernel from one could be trying to read the linuxfs file from the other and cause the lz4 problem.

In hindsight, when I asked you to run "dmesg | tail" after the live-usb failed to boot, I should have also asked you to run "uname -r" to be sure of what kernel was running. If you can create live-usbs that gives that lz4 error with a kernel that has lz4 support, especially if they can do it reliably when booted on a variety of systems then I would dearly love to get my hands on one.

Again, thank you for all of your help.

Iam back! OK , here is the situation with the new lum. It works on my Antix17.4 with kernel 4.20... .
On MX18.1 : with kernel 4.9... - it failed with the lz4 error. I guess kernel 4.9 cannot do lz4.
Yesterday I also tried liquorix 5.0... - that failed with Error: mount: mounting /dev/loop0 on live/linux failed: Invalid argument

So- today, after success with Antix, I decided to install that same antix4.20... kernel in MX , created a new snapshot and created a live-usb. Failed , with the same error message.

So- since the kernels are the same, there is something else about MX18.1 that causes the new LUM to fail , while it works on Antix17.4.
The other difference is the antix snapshot was about 2 GB, while the MX snapshot was 8GB. Dont know if the size matters.

[BitJam]

I'm glad you're back!

Again, make sure only one live-usb is plugged into the machine you are booting. Then use the option bp=e when you boot. This will drop you to a shell if there is an error. When this happens run:

Code: Select all

dmesg | tail
uname -r

The first command should show us what caused the problem. Maybe it is the lz4 error message again or maybe it is something different. The second command verifies which kernel is running so we can check the kernel config and see what features are enabled and disabled.

Also, if you make a live-usb that fails to boot only when you don't use "--force=nofuse" then in addition to the above, I also want to see the portion of the live-usb.log file for the session that created the broken live-usb.

From a user's perspective the important thing is simply whether it failed or not but for those of us trying to fix it, we need to know the exact situation and the reason why it failed.

[rs55]

I'm glad you're back!

Again, make sure only one live-usb is plugged into the machine you are booting. Then use the option bp=e when you boot. This will drop you to a shell if there is an error. When this happens run:

Code: Select all

dmesg | tail
uname -r

The first command should show us what caused the problem. Maybe it is the lz4 error message again or maybe it is something different. The second command verifies which kernel is running so we can check the kernel config and see what features are enabled and disabled.

Also, if you make a live-usb that fails to boot only when you don't use "--force=nofuse" then in addition to the above, I also want to see the portion of the live-usb.log file for the session that created the broken live-usb.

From a user's perspective the important thing is simply whether it failed or not but for those of us trying to fix it, we need to know the exact situation and the reason why it failed.

dmesg : FAT-fs (sdb2): utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive!
( thats the only line that seemed like an error msg)
unmae -r : 4.20.12-antix.1-amd64-snp

(I dont know how to copy all the messages from dmesg to paste here- its on another laptop)

[rs55]

I'm glad you're back!

Again, make sure only one live-usb is plugged into the machine you are booting. Then use the option bp=e when you boot. This will drop you to a shell if there is an error. When this happens run:

Code: Select all

dmesg | tail
uname -r

The first command should show us what caused the problem. Maybe it is the lz4 error message again or maybe it is something different. The second command verifies which kernel is running so we can check the kernel config and see what features are enabled and disabled.

Also, if you make a live-usb that fails to boot only when you don't use "--force=nofuse" then in addition to the above, I also want to see the portion of the live-usb.log file for the session that created the broken live-usb.

From a user's perspective the important thing is simply whether it failed or not but for those of us trying to fix it, we need to know the exact situation and the reason why it failed.

dmesg : FAT-fs (sdb2): utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive!
( thats the only line that seemed like an error msg)
unmae -r : 4.20.12-antix.1-amd64-snp

(I dont know how to copy all the messages from dmesg to paste here- its on another laptop)

where would I find the log file for the failed lum ?

[dolphin_oracle]

/var/log/live-usb-maker.log

[rs55]

/var/log/live-usb-maker.log

see attached. Also - to confirm: uname -r : 4.20.12-antix.1-amd64-smp
Also: with --force=nofuse , the usb boots up fine
This log is for the failed usb creation ( without the --nofuse)

live usb log.txt

[rs55]

/var/log/live-usb-maker.log

see attached. Also - to confirm: uname -r : 4.20.12-antix.1-amd64-smp
Also: with --force=nofuse , the usb boots up fine
This log is for the failed usb creation ( without the --nofuse)live usb log.txt

The mystery ( at least to me) is - this exact same kernel, running this exact same version of lum, works fine from the antix17.4 install ( Control Center - gui).