boot error

[bcreighton]

Can I use snapshot, then MX Linux USB Maker, and just do a fresh install to solve this problem?

[Eadwine Rose]

If your system itself is faulty you will be taking that along in the snapshot, and the consequent install.

[bcreighton]

But, it seems to boot and work fine when I use a MX Linux made USB copy?

[j2mcgreg]

But, it seems to boot and work fine when I use a MX Linux made USB copy?

But you will only really know through use.

[bcreighton]

"In Linux, newer isn't always better. The best solution is the one that works." Amen.

Guess there is only 1 way to find out.

[bcreighton]

OK, tried new install from MX Linux USB. Exact same error. Rebooted into usb live, ran gparted, checked partitions. Main partition was fine. The fat 32 partition succeeded, no errors, but when it tried to grow file system to fill the partition using libparted, it threw an error with no additional information.

Am I at an end? Should I just do a fresh install?

[bcreighton]

Yea, fresh install, same result. Installed graphic card's codecs, no dice. Think thats it. Odd, the same OS runs off my USB stick without a hitch. Can't figure that one out, but I give up

[j2mcgreg]

Yea, fresh install, same result. Installed graphic card's codecs, no dice. Think thats it. Odd, the same OS runs off my USB stick without a hitch. Can't figure that one out, but I give up

The MX Live system runs in ram only which is why it seems to work. But when you try to access the HDD, it crashes so it seems obvious that the HDD is the problem.

[Minnie the Moocher]

@bcreighton

Nope, they're not related to any hdd / ssd issues, nothing to worry, even ignorable.

A Bios update might solve such issues when available. Or:

... a number of ACPI error messages ...

... you can add

Code: Select all

loglevel=3

in kernel parameters box in "MX Boot Options".

Code: Select all

	loglevel=	[KNL,EARLY]
			All Kernel Messages with a loglevel smaller than the
			console loglevel will be printed to the console. It can
			also be changed with klogd or other programs. The
			loglevels are defined as follows:

			0 (KERN_EMERG)		system is unusable
			1 (KERN_ALERT)		action must be taken immediately
			2 (KERN_CRIT)		critical conditions
			3 (KERN_ERR)		error conditions
			4 (KERN_WARNING)	warning conditions
			5 (KERN_NOTICE)		normal but significant condition
			6 (KERN_INFO)		informational
			7 (KERN_DEBUG)		debug-level messages

i.e. loglevel=0 will print emergency messages only (when system is about to crash or is unstable).

In fact quiet is the equivalent of loglevel=4 that's why the system lets the "warning" messages be printed. By the way, no matter you use loglevel 3 or less they're still recorded in log files (in case one needs to search/inquire something). You can also change the splash to nosplash if you prefer the flowing text (like me) but you don't have to.

You can also try (add) the:

Code: Select all

intremap=off

parameter.

[Heliosstyx]

In my opinion your hard-disk will be dead soon. I had the same troubles under Fedora 40: freeze, boot error etc. : the reason was my hard-disk had reached its end of life. Replace your hard-disk with an SSD and your troubles will fly away.