[SOLVED] MX-18.3_x64, the installer stops with the message

[emisol]

Hello!
When trying to install MX-18.3_x64, the installer stops with the message

Code: Select all

Error: /boot/grub/theme/theme.txt

Error: invalid magic number
Error: you need to load the kernel first 4:141 missing separator after property name ‘fC’

I traced the only similar thread with a similar problem
viewtopic.php?f=92&t=48921
Unfortunately, I can't solve the problem.

I tried to install other versions of MX-18.3_x64, MX-18.3_August_x64, MX-19beta-1_x64, MX-17.1_x64, MX-17_x64. Unfortunately, the problem persists, only the error code changes, sometimes it is "X" sometimes "C"

Other distributions, not only Linux, I run without problems in Live mode, as well as I can install on an ssd disk.

What should I do?

[Huckleberry Finn]

Can you post the QSI as in my signature? And sometimes changing to Ahci mode in Bios solves such issues (also suggested for SSDs) (But if you have Win. too then don't hurry, you just need to do a few simple things in Regedit first, not to make it unbootable)

(Assuming you already checked the sum of the iso ...)

[emisol]

I do not have MX installed.
I burned on a pendrive
MX-18.3_August_x64.iso
MX-18.3_x64.iso
MX-19beta-1_x64.iso
MX-17.1_x64.iso
MX-17_x64.iso
I don't have Windows, the disk is installed on LVM Deepin, works fine.
The checksums I've checked are good

[fehlix]

I do not have MX installed.
I burned on a pendrive

What tool do you use to "install" / "burn on a pendrive" ?

[Huckleberry Finn]

I would try writing it alone (the classic way) to a small sized usb and compare what happens..

I also read such an interesting info: When you make a bootable Linux usb in Win. and eject the usb drive directly when the process is completed (without clicking the "remove media safely" etc. on the taskbar) , you get the message "invalid magic number".

Also:

Magic numbers are used to identifiy file-types on file-content (rather than file extensions). It works by reading some of the beginning bytes of a file and compare it with a table of known files which starts with that pattern ("file" does this). It seems your boot configuration is defect or the vmlinuz/initramfs images are not valid...

[emisol]

I'm sorry I didn't reply erlier.
I recorded all versions on a USB stick using Linux dd.
I did so with MX as well as with other distributions.
The problem occurred only with recorded MX.
I found the source of the problem is probably a pendrive.
When I recorded MX-18.3_August_x64.iso on another flash drive, it ran correctly as a live, and then I installed the image on the hard disk.
I have an updated full working OS.
Thank you for your interest and help.

[Huckleberry Finn]

You're welcome. So, will you edit the first post and add [SOLVED] at the title ?