Help for Current Versions of MX
When asking for help, use Quick System Info from MX Tools. It will be properly formatted using the following steps.
1. Click on Quick System Info in MX Tools
2. Right click in your post and paste.
Adlermania
Posts: 43 Joined: Thu Dec 31, 2020 10:32 am
#1
Post
by Adlermania » Sat Sep 16, 2023 1:34 pm
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 =/
Charlie Brown
#2
Post
by Charlie Brown » Sat Sep 16, 2023 1:47 pm
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.
Adlermania
Posts: 43 Joined: Thu Dec 31, 2020 10:32 am
#3
Post
by Adlermania » Sat Sep 16, 2023 2:08 pm
Can I not undo the installation or choose another boot option with the live media? I put MX 23 now on an USB stick.
Charlie Brown
#4
Post
by Charlie Brown » Sat Sep 16, 2023 2:39 pm
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 ..
Adlermania
Posts: 43 Joined: Thu Dec 31, 2020 10:32 am
#6
Post
by Adlermania » Sat Sep 16, 2023 3:21 pm
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
fehlix
Developer
Posts: 12726 Joined: Wed Apr 11, 2018 5:09 pm
#8
Post
by fehlix » Sat Sep 16, 2023 4:04 pm
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.
Adlermania
Posts: 43 Joined: Thu Dec 31, 2020 10:32 am
#9
Post
by Adlermania » Sat Sep 16, 2023 6:23 pm
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
Last edited by
Adlermania on Sat Sep 16, 2023 6:49 pm, edited 2 times in total.
Adlermania
Posts: 43 Joined: Thu Dec 31, 2020 10:32 am
#10
Post
by Adlermania » Sat Sep 16, 2023 6:30 pm
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)