Page 1 of 1
Error upgrade MX21 - MX23 without reinstall
Posted: Sat Sep 16, 2023 1:34 pm
by Adlermania
Hey guys,
I need your help please. I went step by step through this process
https://mxlinux.org/wiki/system/upgradi ... nstalling/
Point 6, reboot, I get the following error and the system won´t boot at all:
Code: Select all
[0.012453] [Firmware Bug]: TSC_DEADLINE disabled due to Errata; please update microcode to version: 0xb2 (or later)
[0.068416] x86/cpu: SGX disabled by BIOS.
[0.068448] RETBleed: WARNING: Spectre v2 mitigation leaves CPU vulnerable to RETBleed attacks, data leaks possible!
[0.283399] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block (0,0)
[0.283413] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 6.1.0-12-amd64 #1 Debian 6.1.52-1
[0.283423] Hardware name: System manufacturer System Product Name/H110M-A/M.2, BIOS 2003 09/19/2016
[0.283433] Call Trace:
[0.283438] <Task>
[0.283443] dump_stack_lvl+0x44/0x5c
[0.283451] panic+0x118/0x2ed
[0.283458] mount_block_root+0x1d3/0x1e6
[0.283466] prepare_namespace+0x136/0x165
[0.283473] kernel_init_freeable+0x25c/0x286
[0.283481] ? rest_init-0xd0/0xd0
[0.283487] kernel_init+0x16/0x130
[0.283492] ret_from_fork+0x22/0x30
[0.283500] </TASK>
[0.283541] Kernel Offset: 0x11800000 from 0xffffffff81000000 (relocation renage: 0xffffffff800000000-0xfffffffbfffff)
[0.283554] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) ]---
How can I rescue my system, I didn´t make a snapshot =/
Re: Error upgrade MX21 - MX23 without reinstall
Posted: Sat Sep 16, 2023 1:47 pm
by Charlie Brown
If you have any live media (no matter what distro and new/old and no matter usb/dvd etc) just boot with and at least you can save your home folder to somewhere else.
Re: Error upgrade MX21 - MX23 without reinstall
Posted: Sat Sep 16, 2023 2:08 pm
by Adlermania
Can I not undo the installation or choose another boot option with the live media? I put MX 23 now on an USB stick.
Re: Error upgrade MX21 - MX23 without reinstall
Posted: Sat Sep 16, 2023 2:39 pm
by Charlie Brown
Completely reverting back seems not to be that easy (also it would't be a clean/healthy system anymore imho).
In fact, it seems to be a kernel panic (about the new default 6.1). "Maybe" you can try Boot Rescue menus on live session ..
Re: Error upgrade MX21 - MX23 without reinstall
Posted: Sat Sep 16, 2023 2:47 pm
by dolphin_oracle
perhaps and an "update-grub" is in order.
Re: Error upgrade MX21 - MX23 without reinstall
Posted: Sat Sep 16, 2023 3:21 pm
by Adlermania
I started the MX 23 Live ISO and choosed Grub reinstall ESP in my root directory. Choosed to boot from Kernel 5.10.
Now I get this error at reboot:
error: symbol "grub_is_lockdown " not found
Re: Error upgrade MX21 - MX23 without reinstall
Posted: Sat Sep 16, 2023 3:36 pm
by Adlermania
what about the rollback option?
Re: Error upgrade MX21 - MX23 without reinstall
Posted: Sat Sep 16, 2023 4:04 pm
by fehlix
Adlermania wrote: Sat Sep 16, 2023 3:21 pm
I started the MX 23 Live ISO and choosed Grub reinstall ESP in my root directory.
I do understand the first part, but have no idea what you meant with the 2nd part:"choosed Grub reinstall ESP in my root directory."
Pleas explain with a bit more context what you actually mean.
Adlermania wrote: Sat Sep 16, 2023 3:21 pm
error: symbol "grub_is_lockdown " not found
Yes, something with different GRUB versions potentially related with secureboot, or GRUB was note properly re-inatlled during your "upgrade" exercise
Suggest: first to post QSI "Quick System Info" when booted from MX-23 Live USB.
Next: I guess, just reinstall GRUB proporly may fix this issue.
Re: Error upgrade MX21 - MX23 without reinstall
Posted: Sat Sep 16, 2023 6:23 pm
by Adlermania
What I did so far, I opened the terminal in the live environment and mounted my sda2 root partition and sda1 boot.
Code: Select all
sudo mount /dev/sda2 /mnt
sudo mount /dev/sda1 /mnt/boot/efi
for i in /dev /dev/pts /proc /sys /run; do sudo mount -B $i /mnt$i; done
sudo chroot /mnt
Re: Error upgrade MX21 - MX23 without reinstall
Posted: Sat Sep 16, 2023 6:30 pm
by Adlermania
QSI
Code: Select all
System:
Kernel: 6.1.0-10-amd64 [6.1.38-2] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
parameters: BOOT_IMAGE=/antiX/vmlinuz quiet splasht nosplash
Desktop: Fluxbox v: 1.3.7 info: tint2 vt: 7 dm: LightDM v: 1.26.0 Distro: MX-23_fluxbox_x64
Libretto July 31 2023 base: Debian GNU/Linux 12 (bookworm)
Machine:
Type: Desktop Mobo: ASUSTeK model: H110M-A/M.2 v: Rev X.0x serial: <superuser required>
UEFI-[Legacy]: American Megatrends v: 2003 date: 09/19/2016
CPU:
Info: model: Intel Core i7-6700K bits: 64 type: MT MCP arch: Skylake-S gen: core 6 level: v3
note: check built: 2015 process: Intel 14nm family: 6 model-id: 0x5E (94) stepping: 3
microcode: 0x84
Topology: cpus: 1x cores: 4 tpc: 2 threads: 8 smt: enabled cache: L1: 256 KiB
desc: d-4x32 KiB; i-4x32 KiB L2: 1024 KiB desc: 4x256 KiB L3: 8 MiB desc: 1x8 MiB
Speed (MHz): avg: 2801 high: 4000 min/max: 800/4200 scaling: driver: intel_pstate
governor: powersave cores: 1: 4000 2: 4000 3: 4000 4: 800 5: 4000 6: 813 7: 800 8: 4000
bogomips: 63999
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities:
Type: itlb_multihit status: KVM: VMX disabled
Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable
Type: mds status: Vulnerable: Clear CPU buffers attempted, no microcode; SMT vulnerable
Type: meltdown mitigation: PTI
Type: mmio_stale_data status: Vulnerable: Clear CPU buffers attempted, no microcode; SMT
vulnerable
Type: retbleed status: Vulnerable
Type: spec_store_bypass status: Vulnerable
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2 mitigation: Retpolines, STIBP: disabled, RSB filling, PBRSB-eIBRS: Not
affected
Type: srbds status: Vulnerable: No microcode
Type: tsx_async_abort status: Vulnerable: Clear CPU buffers attempted, no microcode; SMT
vulnerable
Graphics:
Device-1: Intel HD Graphics 530 vendor: ASUSTeK driver: i915 v: kernel arch: Gen-9
process: Intel 14n built: 2015-16 ports: active: HDMI-A-2 empty: DP-1,HDMI-A-1 bus-ID: 00:02.0
chip-ID: 8086:1912 class-ID: 0300
Device-2: Logitech C922 Pro Stream Webcam type: USB driver: snd-usb-audio,uvcvideo
bus-ID: 1-3:3 chip-ID: 046d:085c class-ID: 0102 serial: <filter>
Display: x11 server: X.Org v: 1.21.1.7 driver: X: loaded: modesetting unloaded: fbdev,vesa
dri: iris gpu: i915 display-ID: :0 screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.00x11.22") s-diag: 582mm (22.93")
Monitor-1: HDMI-A-2 mapped: HDMI-2 model: Samsung S24F350 serial: <filter> built: 2019
res: 1920x1080 hz: 60 dpi: 94 gamma: 1.2 size: 521x293mm (20.51x11.54") diag: 598mm (23.5")
ratio: 16:9 modes: max: 1920x1080 min: 720x400
API: OpenGL v: 4.6 Mesa 22.3.6 renderer: Mesa Intel HD Graphics 530 (SKL GT2)
direct-render: Yes
Audio:
Device-1: Intel 100 Series/C230 Series Family HD Audio vendor: ASUSTeK driver: snd_hda_intel
v: kernel bus-ID: 1-3:3 chip-ID: 046d:085c bus-ID: 00:1f.3 chip-ID: 8086:a170 class-ID: 0102
serial: <filter> class-ID: 0403
Device-2: Logitech C922 Pro Stream Webcam type: USB driver: snd-usb-audio,uvcvideo
API: ALSA v: k6.1.0-10-amd64 status: kernel-api tools: alsamixer,amixer
Server-1: PipeWire v: 0.3.65 status: active with: 1: pipewire-pulse status: active
2: wireplumber status: active 3: pipewire-alsa type: plugin 4: pw-jack type: plugin
tools: pactl,pw-cat,pw-cli,wpctl
Network:
Device-1: Intel Ethernet I219-V vendor: ASUSTeK driver: e1000e v: kernel port: N/A
bus-ID: 00:1f.6 chip-ID: 8086:15b8 class-ID: 0200
IF: eth0 state: up speed: 100 Mbps duplex: full mac: <filter>
Drives:
Local Storage: total: 461.96 GiB used: 219.3 GiB (47.5%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/sda maj-min: 8:0 vendor: Toshiba model: TR150 size: 447.13 GiB block-size:
physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 12.3 scheme: GPT
ID-2: /dev/sdb maj-min: 8:16 type: USB model: General USB Flash Disk size: 14.82 GiB
block-size: physical: 512 B logical: 512 B type: SSD serial: <filter> rev: 1.0 scheme: MBR
SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
Partition:
Message: No partition data found.
Swap:
Alert: No swap data was found.
Sensors:
System Temperatures: cpu: 33.0 C mobo: N/A
Fan Speeds (RPM): N/A
Repos:
Packages: pm: dpkg pkgs: 1809 libs: 886 tools: apt,apt-get,aptitude,nala,synaptic pm: rpm pkgs: 0
pm: flatpak pkgs: 0
No active apt repos in: /etc/apt/sources.list
Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
1: deb http://deb.debian.org/debian bookworm-updates main contrib non-free non-free-firmware
Active apt repos in: /etc/apt/sources.list.d/debian.list
1: deb http://deb.debian.org/debian bookworm main contrib non-free non-free-firmware
2: deb http://security.debian.org/debian-security bookworm-security main contrib non-free non-free-firmware
Active apt repos in: /etc/apt/sources.list.d/mx.list
1: deb http://mxrepo.com/mx/repo/ bookworm main non-free
Info:
Processes: 234 Uptime: 2h 30m wakeups: 1 Memory: 15.52 GiB used: 8.69 GiB (56.0%) Init: SysVinit
v: 3.06 runlevel: 5 default: graphical tool: systemctl Compilers: gcc: 12 Client: shell wrapper
v: 5.2.15-release inxi: 3.3.26
Boot Mode: BIOS (legacy, CSM, MBR)
Re: Error upgrade MX21 - MX23 without reinstall
Posted: Sat Sep 16, 2023 6:37 pm
by fehlix
Adlermania wrote: Sat Sep 16, 2023 6:23 pm
What I did so far, I opened the terminal in the live environment and mounted my sda3 root partition and sda1 boot.
Code: Select all
sudo mount /dev/sda3 /mnt
sudo mount /dev/sda1 /mnt/boot/efi
for i in /dev /dev/pts /proc /sys /run; do sudo mount -B $i /mnt$i; done
sudo chroot /mnt
but when I run chroot /mnt
or chroot /mnt /usr/bin/bash
I get the error: chroot: failed to run command ‘/bin/bash’: No such file or directory
revert your chroot and try this:
to add: Your QSI from MX-23 LiveUSB indicates it was booted in
Boot Mode: BIOS (legacy, CSM, MBR)
Which means you cannot run "grub-install" within the chroot in order to
create a new efi-grub-loader onto the ESP, (mounted on /boot/efi).
You need to boot within UEFI-boot mode with the LiveUSB to create
a new efi-grub bootloader and "install" GRUB onto the ESP.
Re: Error upgrade MX21 - MX23 without reinstall
Posted: Sat Sep 16, 2023 7:42 pm
by Adlermania
I booted with UEFI now. QSI;
Code: Select all
System:
Kernel: 6.1.0-10-amd64 [6.1.38-2] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
parameters: BOOT_IMAGE=/antiX/vmlinuz quiet splasht nosplash
Desktop: Fluxbox v: 1.3.7 info: tint2 vt: 7 dm: LightDM v: 1.26.0 Distro: MX-23_fluxbox_x64
Libretto July 31 2023 base: Debian GNU/Linux 12 (bookworm)
Machine:
Type: Desktop Mobo: ASUSTeK model: H110M-A/M.2 v: Rev X.0x serial: <superuser required>
UEFI: American Megatrends v: 2003 date: 09/19/2016
CPU:
Info: model: Intel Core i7-6700K bits: 64 type: MT MCP arch: Skylake-S gen: core 6 level: v3
note: check built: 2015 process: Intel 14nm family: 6 model-id: 0x5E (94) stepping: 3
microcode: 0x84
Topology: cpus: 1x cores: 4 tpc: 2 threads: 8 smt: enabled cache: L1: 256 KiB
desc: d-4x32 KiB; i-4x32 KiB L2: 1024 KiB desc: 4x256 KiB L3: 8 MiB desc: 1x8 MiB
Speed (MHz): avg: 3200 high: 4000 min/max: 800/4200 scaling: driver: intel_pstate
governor: powersave cores: 1: 4000 2: 4000 3: 4000 4: 4000 5: 800 6: 4000 7: 4000 8: 800
bogomips: 63999
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities:
Type: itlb_multihit status: KVM: VMX disabled
Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable
Type: mds status: Vulnerable: Clear CPU buffers attempted, no microcode; SMT vulnerable
Type: meltdown mitigation: PTI
Type: mmio_stale_data status: Vulnerable: Clear CPU buffers attempted, no microcode; SMT
vulnerable
Type: retbleed status: Vulnerable
Type: spec_store_bypass status: Vulnerable
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2 mitigation: Retpolines, STIBP: disabled, RSB filling, PBRSB-eIBRS: Not
affected
Type: srbds status: Vulnerable: No microcode
Type: tsx_async_abort status: Vulnerable: Clear CPU buffers attempted, no microcode; SMT
vulnerable
Graphics:
Device-1: Intel HD Graphics 530 vendor: ASUSTeK driver: i915 v: kernel arch: Gen-9
process: Intel 14n built: 2015-16 ports: active: HDMI-A-2 empty: DP-1,HDMI-A-1 bus-ID: 00:02.0
chip-ID: 8086:1912 class-ID: 0300
Device-2: Logitech C922 Pro Stream Webcam type: USB driver: snd-usb-audio,uvcvideo
bus-ID: 1-3:3 chip-ID: 046d:085c class-ID: 0102 serial: <filter>
Display: x11 server: X.Org v: 1.21.1.7 driver: X: loaded: modesetting unloaded: fbdev,vesa
dri: iris gpu: i915 display-ID: :0 screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.00x11.22") s-diag: 582mm (22.93")
Monitor-1: HDMI-A-2 mapped: HDMI-2 model: Samsung S24F350 serial: <filter> built: 2019
res: 1920x1080 hz: 60 dpi: 94 gamma: 1.2 size: 521x293mm (20.51x11.54") diag: 598mm (23.5")
ratio: 16:9 modes: max: 1920x1080 min: 720x400
API: OpenGL v: 4.6 Mesa 22.3.6 renderer: Mesa Intel HD Graphics 530 (SKL GT2)
direct-render: Yes
Audio:
Device-1: Intel 100 Series/C230 Series Family HD Audio vendor: ASUSTeK driver: snd_hda_intel
v: kernel bus-ID: 1-3:3 bus-ID: 00:1f.3 chip-ID: 046d:085c chip-ID: 8086:a170 class-ID: 0102
class-ID: 0403 serial: <filter>
Device-2: Logitech C922 Pro Stream Webcam type: USB driver: snd-usb-audio,uvcvideo
API: ALSA v: k6.1.0-10-amd64 status: kernel-api tools: alsamixer,amixer
Server-1: PipeWire v: 0.3.65 status: active with: 1: pipewire-pulse status: active
2: wireplumber status: active 3: pipewire-alsa type: plugin 4: pw-jack type: plugin
tools: pactl,pw-cat,pw-cli,wpctl
Network:
Device-1: Intel Ethernet I219-V vendor: ASUSTeK driver: e1000e v: kernel port: N/A
bus-ID: 00:1f.6 chip-ID: 8086:15b8 class-ID: 0200
IF: eth0 state: up speed: 100 Mbps duplex: full mac: <filter>
Drives:
Local Storage: total: 461.96 GiB used: 0 KiB (0.0%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/sda maj-min: 8:0 vendor: Toshiba model: TR150 size: 447.13 GiB block-size:
physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 12.3 scheme: GPT
ID-2: /dev/sdb maj-min: 8:16 type: USB model: General USB Flash Disk size: 14.82 GiB
block-size: physical: 512 B logical: 512 B type: SSD serial: <filter> rev: 1.0 scheme: MBR
SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
Partition:
Message: No partition data found.
Swap:
Alert: No swap data was found.
Sensors:
System Temperatures: cpu: 38.0 C mobo: N/A
Fan Speeds (RPM): N/A
Repos:
Packages: pm: dpkg pkgs: 1807 libs: 886 tools: apt,apt-get,aptitude,nala,synaptic pm: rpm pkgs: 0
pm: flatpak pkgs: 0
No active apt repos in: /etc/apt/sources.list
Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
1: deb http://deb.debian.org/debian bookworm-updates main contrib non-free non-free-firmware
Active apt repos in: /etc/apt/sources.list.d/debian.list
1: deb http://deb.debian.org/debian bookworm main contrib non-free non-free-firmware
2: deb http://security.debian.org/debian-security bookworm-security main contrib non-free non-free-firmware
Active apt repos in: /etc/apt/sources.list.d/mx.list
1: deb http://mxrepo.com/mx/repo/ bookworm main non-free
Info:
Processes: 218 Uptime: 0m wakeups: 1 Memory: 15.52 GiB used: 858.7 MiB (5.4%) Init: SysVinit
v: 3.06 runlevel: 5 default: graphical tool: systemctl Compilers: gcc: 12 Client: shell wrapper
v: 5.2.15-release inxi: 3.3.26
Boot Mode: UEFI
chroot didnt work because I accidentally mounted sda3 home instead of sda2 root. Now it doesnt show an error if I type chroot /mnt
Re: Error upgrade MX21 - MX23 without reinstall
Posted: Sat Sep 16, 2023 7:44 pm
by Adlermania
How can I install the grub bootloader properly now?
Re: Error upgrade MX21 - MX23 without reinstall
Posted: Sat Sep 16, 2023 8:16 pm
by fehlix
Adlermania wrote: Sat Sep 16, 2023 7:44 pm
How can I install the grub bootloader properly now?
On MX-23 Live USB with UEFI boot mode:
* do unmount all partitions you manually mounted
* run
If the installed system was found and listed select the found
you'll get a chroot-terminal:
run in chroot terminal
Code: Select all
grub-install --force-extra-removable --target=x86_64-efi --bootloader-id=MX23 --recheck --efi-directory=/boot/efi
next update grub config, which provides the grub menu:
Any error copy and paste the command and any error messages:
Als check any old entries in NVRAM and on the ESP
Check nvram:
Check ESP:
Copy / paste the command text output somewhere.
And in case the system would still not boot properly,
post those texts also.
Leave chroot with exit or Ctrl+d
reboot with some luck into the new system.
Re: Error upgrade MX21 - MX23 without reinstall
Posted: Sat Sep 16, 2023 8:29 pm
by Adlermania
chroot> efibootmgr -v
Code: Select all
BootCurrent: 0003
Timeout: 1 seconds
BootOrder: 0002,0003,0004,0000,0001
Boot0000* MX19 HD(1,GPT,5a9f62e3-fb09-414c-8e42-544f1e458f14,0x800,0x100000)/File(\EFI\MX19\GRUBX64.EFI)
Boot0001* Hard Drive BBS(HD,,0x0)..GO..NO........o.T.O.S.H.I.B.A.-.T.R.1.5.0....................A...........................>..Gd-.;.A..MQ..L.6.6.B.Q.2.6.P.Q.8.K.U.X. . . . . . . . ........BO
Boot0002* MX23 HD(1,GPT,5a9f62e3-fb09-414c-8e42-544f1e458f14,0x800,0x100000)/File(\EFI\MX23\grubx64.efi)
Boot0003* UEFI: General USB Flash Disk 1.0, Partition 1 PciRoot(0x0)/Pci(0x14,0x0)/USB(0,0)/HD(1,MBR,0x33e55512,0x4d4,0x45ec)..BO
Boot0004* USB BBS(HD,,0x0)..GO..NO........c.G.e.n.e.r.a.l. .U.S.B. .F.l.a.s.h. .D.i.s.k. .1...0....................A.......................6..Gd-.;.A..MQ..L.1.2.5.9.0.0.0.0.0.0.0.0.1.2.2.A........BO
(MX_23_Libretto_) Sun Sep 17 02:23:29 /
chroot> find /boot/efi -ls
Code: Select all
1 4 drwxr-xr-x 3 root root 4096 Jan 1 1970 /boot/efi
113 4 drwxr-xr-x 5 root root 4096 Sep 16 21:05 /boot/efi/EFI
122 4 drwxr-xr-x 2 root root 4096 Dec 27 2020 /boot/efi/EFI/MX19
124 128 -rwxr-xr-x 1 root root 131072 Dec 27 2020 /boot/efi/EFI/MX19/grubx64.efi
118 4 drwxr-xr-x 2 root root 4096 Dec 27 2020 /boot/efi/EFI/BOOT
120 136 -rwxr-xr-x 1 root root 139264 Sep 17 02:22 /boot/efi/EFI/BOOT/BOOTX64.EFI
114 4 drwxr-xr-x 2 root root 4096 Sep 16 21:05 /boot/efi/EFI/MX23
115 136 -rwxr-xr-x 1 root root 139264 Sep 17 02:22 /boot/efi/EFI/MX23/grubx64.efi
(MX_23_Libretto_) Sun Sep 17 02:25:42 /
Thank you, no error so far.
It shows MX19 as I already upgraded from MX19 to MX21 before.
So should I try a reboot without usb?
Re: Error upgrade MX21 - MX23 without reinstall
Posted: Sat Sep 16, 2023 9:03 pm
by Adlermania
I just rebooted, got the same error message like in my first post.
Re: Error upgrade MX21 - MX23 without reinstall
Posted: Sat Sep 16, 2023 9:10 pm
by Adlermania
Tried to install avahi/sysvinit/compat from point 7
demo@mx1:~
$ sudo chroot-rescue-scan
[sudo] password for demo:
===============================================================================
Starting chroot-rescue-scan
===============================================================================
Scanning partitions ...
Scanning directories ...
Only one Linux system was found
Please select a Linux system to visit
Distro Date Dir Device Arch Label
= MX 23 Libretto 2020-12-26 rootMX19 sda2 64-bit rootMX19
> Rescan all partitions for Linux systems
> Quit
Press <Enter> to select the highlighted entry
Use 'r' to redraw, 'q' to quit
Visiting distro MX_23_Libretto_
Directory: /mnt/chroot-rescue-scan/rootMX19 Device: sda2
Use the exit command or <ctrl>-d to return to main menu
===============================================================================
(MX_23_Libretto_) Sun Sep 17 03:06:40 /
chroot> sudo apt install avahi-sysvinit-compat
Code: Select all
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages were automatically installed and are no longer required:
android-libart android-libcrypto-utils android-libetc1 android-libext4-utils
android-libnativebridge android-libnativeloader android-libunwind
bridge-utils cryptsetup-run dalvik-exchange dexdump dh-dkms
firmware-intelwimax ftp g++-10 gir1.2-packagekitglib-1.0 gir1.2-tracker-2.0
gnome-desktop3-data libabsl20200923 libandroid-23-java libappstream-glib8
libatk1.0-data libavdevice58 libavfilter7 libavformat58 libavif9
libavresample4 libbpf0 libcbor0 libcfitsio9 libdns-export1110
libexporter-tiny-perl libextutils-pkgconfig-perl libfam0 libflac8
libfluidsynth2 libfmt7 libgav1-0 libgit2-1.1 libglew2.1 libgs9-common
libgsoap-2.8.104 libgssdp-1.2-0 libgtksourceview-3.0-1
libgtksourceview-3.0-common libgupnp-1.2-0 libhttp-parser2.9 libicu67
libilmbase25 libisc-export1105 libjim0.79 libjsoncpp24
libkdecorations2private7 libkf5kipi-data libkf5kipi32.0.0 libkf5screen7
libkf5sysguard-bin libkf5waylandserver5 libkpimgapi-data
libkpimgapicore5abi1 libkpimsmtp5abi1 libksignalplotter9 libkwaylandserver5
libkwineffects12a libkwinglutils12 libkwinxrenderutils12 libldap-2.4-2
liblibreoffice-java liblist-moreutils-perl liblist-moreutils-xs-perl
libllvm14 libmbedcrypto3 libmbedtls12 libmbedx509-0 libmms0 libmozjs-78-0
libmpdec3 libmujs1 libnetpbm10 libntfs-3g883 libofa0 libopenexr25 libopts25
libperl5.32 libplacebo120 libplacebo72 libpoppler102 libpostproc55
libprocps8 libprotobuf-lite23 libprotobuf23 libpython3.9
libpython3.9-minimal libpython3.9-stdlib libqalculate20 libqalculate20-data
libqpdf28 libquicktime2 librest-0.7-0 libsrt1.4-gnutls libstdc++-10-dev
libstrictures-perl libswscale5 libtepl-5-0 libtiff5 libtracker-control-2.0-0
libtracker-miner-2.0-0 libtracker-sparql-2.0-0 libunbound8 libunoloader-java
libusb-0.1-4 libwmf0.2-7 libwxbase3.0-0v5 libwxgtk3.0-gtk3-0v5
libxkbregistry0 linux-headers-5.10.0-24-amd64 linux-headers-5.10.0-24-common
linux-image-5.10.0-24-amd64 openjdk-11-jdk-headless perl-modules-5.32
python-pip-whl python3-cssutils python3-openssl python3.9 python3.9-minimal
ruby2.7 software-properties-common telnet unbound-anchor ure-java vrms
Use 'sudo apt autoremove' to remove them.
The following NEW packages will be installed:
avahi-sysvinit-compat
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
4 not fully installed or removed.
Need to get 2,308 B of archives.
After this operation, 15.4 kB of additional disk space will be used.
Get:1 http://ftp.halifax.rwth-aachen.de/mxlinux/packages/mx/repo bookworm/main amd64 avahi-sysvinit-compat all 23.07.01 [2,308 B]
Fetched 2,308 B in 0s (18.0 kB/s)
Selecting previously unselected package avahi-sysvinit-compat.
(Reading database ... 457433 files and directories currently installed.)
Preparing to unpack .../avahi-sysvinit-compat_23.07.01_all.deb ...
Unpacking avahi-sysvinit-compat (23.07.01) ...
Setting up linux-image-6.1.0-12-amd64 (6.1.52-1) ...
/etc/kernel/postinst.d/dkms:
dkms: running auto installation service for kernel 6.1.0-12-amd64.
/usr/sbin/dkms.mx autoinstall --kernelver 6.1.0-12-amd64
Sign command: /usr/lib/linux-kbuild-6.1/scripts/sign-file
Signing key: /var/lib/dkms/mok.key
Public certificate (MOK): /var/lib/dkms/mok.pub
Building module:
Cleaning build area...
make -j8 KERNELRELEASE=6.1.0-12-amd64 -C /lib/modules/6.1.0-12-amd64/build M=/va
r/lib/dkms/virtualbox-guest/6.1.22/build...(bad exit status: 2)
Error! Bad return status for module build on kernel: 6.1.0-12-amd64 (x86_64)
Consult /var/lib/dkms/virtualbox-guest/6.1.22/build/make.log for more informatio
n.
Error! One or more modules failed to install during autoinstall.
Refer to previous errors for more information.
dkms: autoinstall for kernel: 6.1.0-12-amd64 failed!
run-parts: /etc/kernel/postinst.d/dkms exited with return code 11
dpkg: error processing package linux-image-6.1.0-12-amd64 (--configure):
installed linux-image-6.1.0-12-amd64 package post-installation script subproces
s returned error exit status 1
Setting up linux-headers-6.1.0-12-amd64 (6.1.52-1) ...
/etc/kernel/header_postinst.d/dkms:
dkms: running auto installation service for kernel 6.1.0-12-amd64.
/usr/sbin/dkms.mx autoinstall --kernelver 6.1.0-12-amd64
Sign command: /usr/lib/linux-kbuild-6.1/scripts/sign-file
Signing key: /var/lib/dkms/mok.key
Public certificate (MOK): /var/lib/dkms/mok.pub
Building module:
Cleaning build area...
make -j8 KERNELRELEASE=6.1.0-12-amd64 -C /lib/modules/6.1.0-12-amd64/build M=/va
r/lib/dkms/virtualbox-guest/6.1.22/build...(bad exit status: 2)
Error! Bad return status for module build on kernel: 6.1.0-12-amd64 (x86_64)
Consult /var/lib/dkms/virtualbox-guest/6.1.22/build/make.log for more informatio
n.
Error! One or more modules failed to install during autoinstall.
Refer to previous errors for more information.
dkms: autoinstall for kernel: 6.1.0-12-amd64 failed!
run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 11
Failed to process /etc/kernel/header_postinst.d at /var/lib/dpkg/info/linux-head
ers-6.1.0-12-amd64.postinst line 11.
dpkg: error processing package linux-headers-6.1.0-12-amd64 (--configure):
installed linux-headers-6.1.0-12-amd64 package post-installation script subproc
ess returned error exit status 1
Setting up avahi-sysvinit-compat (23.07.01) ...
dpkg: dependency problems prevent configuration of linux-headers-amd64:
linux-headers-amd64 depends on linux-headers-6.1.0-12-amd64 (= 6.1.52-1); howev
er:
Package linux-headers-6.1.0-12-amd64 is not configured yet.
dpkg: error processing package linux-headers-amd64 (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of linux-image-amd64:
linux-image-amd64 depends on linux-image-6.1.0-12-amd64 (= 6.1.52-1); however:
Package linux-image-6.1.0-12-amd64 is not configured yet.
dpkg: error processing package linux-image-amd64 (--configure):
dependency problems - leaving unconfigured
Errors were encountered while processing:
linux-image-6.1.0-12-amd64
linux-headers-6.1.0-12-amd64
linux-headers-amd64
linux-image-amd64
E: Sub-process /usr/bin/dpkg returned an error code (1)
Re: Error upgrade MX21 - MX23 without reinstall
Posted: Sun Sep 17, 2023 6:18 am
by Charlie Brown
= MX 23 Libretto 2020-12-26 rootMX19 sda2 64-bit rootMX19
... Or, did you upgrade from 21 which was upgraded from 19 ?
Re: Error upgrade MX21 - MX23 without reinstall
Posted: Sun Sep 17, 2023 7:14 am
by fehlix
Somewhere with you upgrade excersice from MX19
you may have overlooked an install error, indicated by the line
"4 not fully installed or removed."
with the installation attempt:
Adlermania wrote: Sat Sep 16, 2023 9:10 pm
Tried to install avahi/sysvinit/compat from point 7
sudo apt install avahi-sysvinit-compat
Code: Select all
Reading package lists... Done
...
The following NEW packages will be installed:
avahi-sysvinit-compat
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
4 not fully installed or removed.
Maybe you booted into bios/mbr-bootloader of the MX19 install:
Adlermania wrote: Sat Sep 16, 2023 9:03 pm
I just rebooted, got the same error message like in my first post.
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.
Re: Error upgrade MX21 - MX23 without reinstall
Posted: Sun Sep 17, 2023 7:36 am
by Adlermania
Yes I upgraded from MX19 to 21, over one year before, everything worked fine, and now from 21 to 23.
I think I rebooted already with all these errors.
Re: Error upgrade MX21 - MX23 without reinstall
Posted: Sun Sep 17, 2023 7:45 am
by 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.
Re: Error upgrade MX21 - MX23 without reinstall
Posted: Sun Sep 17, 2023 7:51 am
by fehlix
Adlermania wrote: Sun Sep 17, 2023 7:45 am
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.
Re: Error upgrade MX21 - MX23 without reinstall
Posted: Sun Sep 17, 2023 8:15 am
by 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.
Re: Error upgrade MX21 - MX23 without reinstall
Posted: Sun Sep 17, 2023 8:22 am
by 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.
Re: Error upgrade MX21 - MX23 without reinstall
Posted: Sun Sep 17, 2023 8:59 am
by Charlie Brown
Adlermania wrote: Sun Sep 17, 2023 7:36 am
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.
Re: Error upgrade MX21 - MX23 without reinstall
Posted: Sun Sep 17, 2023 9:01 am
by 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.
Re: Error upgrade MX21 - MX23 without reinstall
Posted: Sun Sep 17, 2023 9:12 am
by fehlix
Eadwine Rose wrote: Sun Sep 17, 2023 8:22 am
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:
This may trigger finish the kernel build process.
may be followed by
and
Re: Error upgrade MX21 - MX23 without reinstall
Posted: Sun Sep 17, 2023 12:13 pm
by 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.
Re: Error upgrade MX21 - MX23 without reinstall
Posted: Sun Sep 17, 2023 1:01 pm
by fehlix
Adlermania wrote: Sun Sep 17, 2023 12:13 pm
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
Clear old invalid entries from NVRAM's efi's boot options list:
First check:
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:
Good luck.
Re: Error upgrade MX21 - MX23 without reinstall
Posted: Sun Oct 08, 2023 9:54 am
by 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.
Re: Error upgrade MX21 - MX23 without reinstall
Posted: Sun Oct 08, 2023 10:01 am
by j2mcgreg
@vicco
You should start your own thread and post your QSI.
Re: Error upgrade MX21 - MX23 without reinstall
Posted: Sun Oct 08, 2023 10:47 am
by Eadwine Rose
Indeed. And know that this is NOT supported.