MX Linux Forum

Like fehlix I think you crash before systemd, but systemd is problematic on Live environment that's one of the main reason we boot by default to sysVinit. Try to edit the kernel line (you should have an option before it boots to edit the line, I guess it depends on how exactly you boot).

When you take a snapshot you have an option to edit the kernel line too. Maybe we should filter out systemd option by default, @fehlix, what do you think?

fehlix wrote: Wed Jan 24, 2024 11:12 am Maybe post the log files, perhaps for both mx-snapshot and mx-live-usb-maker,
probably still be accessible through QSI-tool.

attached

Adrian wrote: Wed Jan 24, 2024 11:15 am
When you take a snapshot you have an option to edit the kernel line too. Maybe we should filter out systemd option by default, @fehlix, what do you think?

I boot systemd but when making snapshots, systemd is not in my boot options by default (nor do I add it).

Minutes ago I started up my desktop tower computer from the HDD as I always do and had some weird activity: some box appeared first which I've NEVER seen before. I think that box wanted me to pick something but it disappeared soon and more bizarre behavior occurred. Somehow I opened up Pale Moon just to consult this forum-- I didn't want to just re-boot because I thought maybe things will be far worse if I do that.

With MX23, I'm using 6.6.12-1-liquorix-amd64 which is the latest in this series.

Is this strange, weird start-up and early OS operation behavior I encountered the same as what was happening to the originator of this thread?

Did you post in a wrong thread, what does have to do with the kernel panic?

Adrian, I'm no expert in kernel panics. I just thought what happened to me might be the same as or similar to what happened to the MX user who started this thread. With reliable, steady MX, everything always goes well for me every day for years and then suddenly, out-of-the-blue, something bizarre occurs and I don't know what to make of it nor know what to do to end it. I suppose I can just re-boot now and see if the same thing happens, but tell me first if that's a good idea to do.

sps7 wrote: Wed Jan 24, 2024 11:55 am Adrian, I'm no expert in kernel panics. I just thought what happened to me might be the same as or similar to what happened to the MX user who started this thread. With reliable, steady MX, everything always goes well for me every day for years and then suddenly, out-of-the-blue, something bizarre occurs and I don't know what to make of it nor know what to do to end it. I suppose I can just re-boot now and see if the same thing happens, but tell me first if that's a good idea to do.

Doesn't sound anything related, you'd know if you have a kernel panic.

OK, thanks Adrian.

It's the OP again, so I made a snapshot on a sysvinit session, and I still get kernel panic.
new logs attached.
The snapshot log is a link because it was to large to upload.
https://www.dropbox.com/scl/fi/ugf1e9ph ... 4akvg&dl=0

how about your excludes file?