Error upgrade MX21 - MX23 without reinstall

[Adlermania]

which may be have left over. So not sure how to fix this "mess".
Perhaps, as already requested, boot with MX LiveUSB -> Boot Rescue -> efi GRUB loader
and select MX23 efiLoader.

Just did this, it shows 1 second the blue screen with booting MX Linux 6.10. and then directly the error from my first post.

[fehlix]

which may be have left over. So not sure how to fix this "mess".
Perhaps, as already requested, boot with MX LiveUSB -> Boot Rescue -> efi GRUB loader
and select MX23 efiLoader.

Just did this, it shows 1 second the blue screen with booting MX Linux 6.10. and then directly the error from my first post.

Are you saying you don't get a GRUB menu? Otherwise select another kernel on the GRUB menu under advanced.

[Adlermania]

Yes maybe 1 second the screen with Booting Debian from Linux 6.10.... and then the error.
I just went into Advanced Options but cant see another Kernel there. Tried rollback option, but same error.

[Eadwine Rose]

Respect to Fehlix for trying to help you to fix this mess.. but to be honest, at this point you would have been done a while ago by installing 23 clean after backing up your important files. I'd suggest going this route and stop spending energy trying to fix what we have no idea went wrong.

[Charlie Brown]

Yes I upgraded from MX19 to 21, over one year before, everything worked fine, and now from 21 to 23...

Yes. A clean install takes 10-15 min or so, plus it's fresh, healthy.. And your customizations etc. are already in home folder ..

This one looks like something experimental.

[MadMax]

Agreed. You can always TRY an in-place upgrade, but if it doesn't work after some tinkering, you have to be ready to scrap it and just do a clean install instead. In-place upgrades are not officially recommended for a reason.

[fehlix]

Respect to Fehlix for trying to help you to fix this mess.. but to be honest, at this point you would have been done a while ago by installing 23 clean after backing up your important files. I'd suggest going this route and stop spending energy trying to fix what we have no idea went wrong.

+1 ...
Also not sure why they have weakened the warning within the migration instructions.
IIRC, that had a strong warning kind of "For experts only." or something like that.
OK, they strongly recommend to have a backup in any kind. e.g by making Snapshot ISO.

But anyway, last attempt to try fxing the "mess":
Within the chroot-rescue-scan terminal ,
try get rid of the show stopper during kernel + intrd build:

Code: Select all

apt purge "virtualbox*"

This may trigger finish the kernel build process.
may be followed by

Code: Select all

apt install -f

and

Code: Select all

apt autoremove

[Adlermania]

It worked =)! Thank you so much for the help!
It just booted into the new system. Do I still have to change the mirrors or something like that, as one of the browsers shows it would be outdated.
Anyway I will save my data and do a clean install next time.

[fehlix]

It worked =)! Thank you so much for the help!
It just booted into the new system. Do I still have to change the mirrors or something like that, as one of the browsers shows it would be outdated.
Anyway I will save my data and do a clean install next time.

Good work. Something left to tidy up:
Open terminal as normal user:
* Remove leftover efiloader from ESP

Code: Select all

sudo rm -r /boot/efi/EFI/MX19

Clear old invalid entries from NVRAM's efi's boot options list:
First check:

Code: Select all

efibootmgr -v | grep MX19

In case it is still listed as "Boot0000"

Code: Select all

Boot0000* MX19	HD(1,GPT,5a9f62e3-fb09-414c-8e42-544f1e458f14,0x800,0x100000)/File(\EFI\MX19\GRUBX64.EFI)

* remove this way:

Code: Select all

sudo efibootmgr --verbose --delete-bootnum --bootnum 00000

or shorter:

Code: Select all

sudo efibootmgr -v -B -b 0

Good luck.

[vicco]

I'm facing a similar issue here. I did an upgrade following these steps https://mxlinux.org/wiki/system/upgradi ... nstalling/

A kernel panic occurred at reboot; I was able to boot using Kernel: 6.1.0-9mx-ahs-amd64 [6.1.27-1~mx21ahs+1]. Inside it, trying to upgrade the mxinstaller produced the following error:

Error! Your kernel headers for kernel 5.10.0-19-amd64 cannot be found at /lib/modules/5.10.0-19-amd64/build or /lib/modules/5.10.0-19-amd64/source.
Please install the linux-headers-5.10.0-19-amd64 package or use the --kernelsourcedir option to tell DKMS where it's located.

It seems to me that something in the upgrade did not work, as it intends to revert to MX21 kernels. I wonder if there's a way to fix this and get the system working properly. I already applied autoremove and autopurge, but the problem is still there.