Mx-23.2 boot failure

[Charlie Brown]

... used "Chroot Rescue Scan" ... then used "MX Boot Options" tool to ... then rebooted. No change,..

Cause you needed to open those applications (no matter gui or cli) within that chroot terminal , not using the Whisker menu or App. Finder. Those you directly open (using menu etc) will not affect the chrooted system (target), but will be done on the running (live in this case) system itself.

Shortly when you see the prompt

chroot>

issue:

Code: Select all

mx-boot-options

( same for ddm etc ...)

[Charlie Brown]

... a blinking cursor in the upper left of a black screen...

When you boot with the live usb access your MX partition using the left pane on Thunar (even "root Thunar") then delete if there is such a file:

/etc/X11/xorg.conf

(Not the others or directories with similar names, just and exactly this file "if there is")


P.S. Probably the same file is on live usb (you can check that /etc/X11/ too and that's why you had to use the failsafe parameter)

[DukeComposed]

... no partition information found in this QSI ...

Normal. Live session.

This is what I was hoping. OP still needs to find all the right partitions to mount and, I'm guessing, rebuild initramfs and/or reinstall GRUB.

[james]

Thank you for the assistance. I will be here all day able to work on this as needed.

[j2mcgreg: What utility did you use to write the snapshot ISO to your USB drive?] Per fehlix, I used the MX Linux "Live USB Maker" tool.

[DukeComposed: I see four storage devices: two 1 TB drives, 1 500-ish GB drive, and the USB flash drive.] Yes, the two 1 TB drives and the 500 GB drives are all nvme drives installed on the mother board. One 1 TB drive has Mx Linux installed, using a vfat boot partition and an ext4 root partition. The other two nvme's are used to store data. There is no other OS on the machine. The USB flash drive has the Live USB Snapshot. Thank you very much for the explanation of how to know when I am looking at files on the Live USB versus those on the hard drive of the machine. The info you requested on the drives is:

Code: Select all

$ sudo fdisk -l /dev/nvme0n1p1
Disk /dev/nvme0n1p1: 465.76 GiB, 500103643136 bytes, 976764928 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
[~]
$ sudo fdisk -l /dev/nvme1n1p1
Disk /dev/nvme1n1p1: 931.51 GiB, 1000203091968 bytes, 1953521664 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
[~]
$ sudo fdisk -l /dev/nvme2n1p1
Disk /dev/nvme2n1p1: 256 MiB, 268435456 bytes, 524288 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x00000000
[~]
$ sudo fdisk -l /dev/nvme2n1p2
Disk /dev/nvme2n1p2: 931.26 GiB, 999933607936 bytes, 1952995328 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

I am going to paste current QSI since I have been wrestling with this problem and have experimented with various changes, particularly BIOS and boot parameters. I will stop doing so now unless instructed:

Code: Select all

Snapshot created on: 20240310_1128
System:
  Kernel: 6.7.8-1-liquorix-amd64 [6.7-12~mx23ahs] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0 parameters: audit=0
    intel_pstate=disable rcupdate.rcu_expedited=1 BOOT_IMAGE=/antiX/vmlinuz quiet splash splash
    failsafe
  Desktop: Xfce v: 4.18.1 tk: Gtk v: 3.24.36 info: xfce4-panel wm: xfwm v: 4.18.0 vt: 7
    dm: LightDM v: 1.26.0 Distro: MX-23.2_ahs_x64 Libretto January 21  2024 base: Debian GNU/Linux
    12 (bookworm)
Machine:
  Type: Desktop System: Gigabyte product: Z690 AERO G DDR4 v: -CF serial: <superuser required>
  Mobo: Gigabyte model: Z690 AERO G DDR4 v: x.x serial: <superuser required> UEFI: American
    Megatrends LLC. v: F8a date: 03/28/2022
Battery:
  Device-1: hidpp_battery_2 model: Logitech Wireless Mouse M215 2nd Gen serial: <filter>
    charge: 100% (should be ignored) rechargeable: yes status: discharging
  Device-2: hidpp_battery_3 model: Logitech Wireless Keyboard K330 serial: <filter> charge: 100%
    (should be ignored) rechargeable: yes status: discharging
CPU:
  Info: model: 12th Gen Intel Core i9-12900K bits: 64 type: MST AMCP arch: Alder Lake gen: core 12
    level: v3 note: check built: 2021+ process: Intel 7 (10nm ESF) family: 6 model-id: 0x97 (151)
    stepping: 2 microcode: 0x1E
  Topology: cpus: 1x cores: 16 mt: 8 tpc: 2 st: 8 threads: 24 smt: enabled cache: L1: 1.4 MiB
    desc: d-8x32 KiB, 8x48 KiB; i-8x32 KiB, 8x64 KiB L2: 14 MiB desc: 8x1.2 MiB, 2x2 MiB L3: 30 MiB
    desc: 1x30 MiB
  Speed (MHz): avg: 902 high: 2127 min/max: 800/3201 boost: enabled scaling: driver: acpi-cpufreq
    governor: ondemand cores: 1: 993 2: 800 3: 990 4: 800 5: 1004 6: 800 7: 800 8: 800 9: 1000
    10: 800 11: 1005 12: 800 13: 948 14: 800 15: 2127 16: 800 17: 800 18: 800 19: 800 20: 800
    21: 800 22: 800 23: 800 24: 800 bogomips: 152985
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities:
  Type: gather_data_sampling status: Not affected
  Type: itlb_multihit status: Not affected
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: mmio_stale_data status: Not affected
  Type: retbleed status: Not affected
  Type: spec_rstack_overflow status: Not affected
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
  Type: spectre_v2 mitigation: Enhanced / Automatic IBRS, IBPB: conditional, RSB filling,
    PBRSB-eIBRS: SW sequence
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: Intel AlderLake-S GT1 vendor: Gigabyte driver: N/A alternate: i915 bus-ID: 00:02.0
    chip-ID: 8086:4680 class-ID: 0300
  Device-2: NVIDIA GA104 [GeForce RTX 3070 Ti] vendor: eVga.com. driver: nvidia v: 525.147.05
    non-free: 530.xx+ status: current (as of 2023-03) arch: Ampere code: GAxxx process: TSMC n7 (7nm)
    built: 2020-22 pcie: gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 01:00.0 chip-ID: 10de:2482
    class-ID: 0300
  Display: x11 server: X.Org v: 1.21.1.7 compositor: xfwm v: 4.18.0 driver: X: loaded: N/A
    unloaded: fbdev dri: swrast gpu: nvidia note: X driver n/a display-ID: :0 screens: 1
  Screen-1: 0 s-res: 1280x1024 s-dpi: 96 s-size: 339x271mm (13.35x10.67") s-diag: 434mm (17.09")
  Monitor-1: default res: 1280x1024 hz: 77 size: N/A modes: N/A
  API: OpenGL v: 4.5 Mesa 23.1.2-1~mx23ahs renderer: llvmpipe (LLVM 15.0.6 256 bits)
    direct-render: Yes
Audio:
  Device-1: Intel Alder Lake-S HD Audio vendor: Gigabyte driver: N/A bus-ID: 1-11:4
    alternate: snd_hda_intel, snd_sof_pci_intel_tgl bus-ID: 00:1f.3 chip-ID: 0414:a012 class-ID: 0300
    chip-ID: 8086:7ad0 class-ID: 0403
  Device-2: NVIDIA GA104 High Definition Audio vendor: eVga.com. driver: snd_hda_intel v: kernel
    pcie: gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 01:00.1 chip-ID: 10de:228b class-ID: 0403
  Device-3: Giga-Byte USB Audio type: USB driver: hid-generic,snd-usb-audio,usbhid
  API: ALSA v: k6.7.8-1-liquorix-amd64 status: kernel-api tools: alsamixer,amixer
  Server-1: PipeWire v: 1.0.0 status: off with: 1: pipewire-pulse status: off 2: wireplumber
    status: off 3: pw-jack type: plugin tools: pw-cat,pw-cli,wpctl
  Server-2: PulseAudio v: 16.1 status: active tools: pacat,pactl,pavucontrol
Network:
  Device-1: Intel Alder Lake-S PCH CNVi WiFi driver: iwlwifi v: kernel modules: wl bus-ID: 00:14.3
    chip-ID: 8086:7af0 class-ID: 0280
  IF: wlan0 state: down mac: <filter>
  Device-2: Intel Ethernet I225-V vendor: Gigabyte driver: igc v: kernel pcie: gen: 2
    speed: 5 GT/s lanes: 1 port: N/A bus-ID: 05:00.0 chip-ID: 8086:15f3 class-ID: 0200
  IF: eth0 state: down mac: <filter>
  Device-3: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver: r8169 v: kernel pcie:
    gen: 1 speed: 2.5 GT/s lanes: 1 port: 3000 bus-ID: 06:00.0 chip-ID: 10ec:8161 class-ID: 0200
  IF: eth1 state: up speed: 100 Mbps duplex: full mac: <filter>
Bluetooth:
  Device-1: Intel AX201 Bluetooth type: USB driver: btusb v: 0.8 bus-ID: 1-14:8 chip-ID: 8087:0026
    class-ID: e001
  Report: hciconfig ID: hci0 rfk-id: 1 state: up address: <filter> bt-v: 3.0 lmp-v: 5.2
    sub-v: 3462 hci-v: 5.2 rev: 3462
  Info: acl-mtu: 1021:4 sco-mtu: 96:6 link-policy: rswitch sniff link-mode: peripheral accept
Drives:
  Local Storage: total: 2.39 TiB used: 62.17 GiB (2.5%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:1 vendor: Western Digital model: WDS500G1X0E-00AFY0
    size: 465.76 GiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s lanes: 4 type: SSD
    serial: <filter> rev: 614600WD temp: 41.9 C scheme: GPT
  ID-2: /dev/nvme1n1 maj-min: 259:2 vendor: Western Digital model: WDS100T1X0E-00AFY0
    size: 931.51 GiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s lanes: 4 type: SSD
    serial: <filter> rev: 614600WD temp: 40.9 C scheme: GPT
  ID-3: /dev/nvme2n1 maj-min: 259:0 vendor: Western Digital model: WDS100T1X0E-00AFY0
    size: 931.51 GiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s lanes: 4 type: SSD
    serial: <filter> rev: 614600WD temp: 41.9 C scheme: GPT
  ID-4: /dev/sda maj-min: 8:0 type: USB vendor: SanDisk model: USB 3.2Gen1 size: 114.6 GiB
    block-size: physical: 512 B logical: 512 B type: N/A serial: <filter> rev: 1.00 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: 26.0 C mobo: N/A
  Fan Speeds (RPM): N/A
Repos:
  Packages: pm: dpkg pkgs: 2697 libs: 1447 tools: apt,apt-get,aptitude,nala,synaptic pm: rpm
    pkgs: 0
  No active apt repos in: /etc/apt/sources.list
  Active apt repos in: /etc/apt/sources.list.d/brave-browser-release.list
    1: deb [arch=amd64] https://brave-browser-apt-release.s3.brave.com/ stable main
  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 https://mxrepo.com/mx/repo/ bookworm main non-free
    2: deb https://mxrepo.com/mx/repo/ bookworm ahs
  Active apt repos in: /etc/apt/sources.list.d/protonvpn-stable.list
    1: deb [arch="all", signed-by=/usr/share/keyrings/protonvpn-stable-archive-keyring.gpg] https://repo.protonvpn.com/debian stable main
  Active apt repos in: /etc/apt/sources.list.d/vivaldi.list
    1: deb [arch=amd64] https://repo.vivaldi.com/stable/deb/ stable main
Info:
  Processes: 523 Uptime: 4h 38m wakeups: 20 Memory: 62.57 GiB used: 2.69 GiB (4.3%) Init: SysVinit
  v: 3.06 runlevel: 5 default: graphical tool: systemctl Compilers: gcc: 12.2.0 alt: 12
  Client: shell wrapper v: 5.2.15-release inxi: 3.3.26
Boot Mode: UEFI
Video Tweaks:
Detected possible Hybrid Graphics
No kernel video driver

Best,
James

[james]

Sorry: I seem to have pasted my previous response in here twice. Perhaps the moderator could remove one? Thank you Charlie Brown...

[Charlie Brown: ...you needed to open those applications (no matter gui or cli) within that chroot terminal ... issue: mx-boot-options] OK, this did not seem to work either:

Code: Select all

chroot> mx-boot-options
Invalid MIT-MAGIC-COOKIE-1 key
qt.qpa.xcb: could not connect to display :0.0
qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.

Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, xcb.

Aborted

[Charlie Brown: delete if there is such a file: /etc/X11/xorg.conf] Done successfully from Chroot terminal.

[james]

Charlie Brown, could you recommend which plugin I should install to get the boot options to work, and the chroot commands to use to do so?

Thanks again,
James

[xaol]

the disk info still looks a bit incomplete. it may help to run just sudo fdisk -l which should hopefully show info on all disks or possibly run it like you did without adding the partition (p1 and p2) to the disk. for example:

Code: Select all

sudo fdisk -l /dev/nvme0n1

my disk is a little different from yours because it isn't an nvme, but this is what it looks like after running sudo fdisk -l

Code: Select all

sudo fdisk -l
Disk /dev/sda: 931.51 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: Samsung SSD 870 
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: AB5404A8-0A85-4706-942F-44D87C9CCD83

Device          Start        End    Sectors  Size Type
/dev/sda1        2048    1026047    1024000  500M EFI System
/dev/sda2  1945137152 1953523711    8386560    4G Linux root (x86)
/dev/sda4  1882222592 1945137151   62914560   30G Linux filesystem
/dev/sda5     1026048 1882222591 1881196544  897G Linux root (x86)

[DukeComposed]

Thank you for the assistance. I will be here all day able to work on this as needed.

[j2mcgreg: What utility did you use to write the snapshot ISO to your USB drive?] Per fehlix, I used the MX Linux "Live USB Maker" tool.

[DukeComposed: I see four storage devices: two 1 TB drives, 1 500-ish GB drive, and the USB flash drive.] Yes, the two 1 TB drives and the 500 GB drives are all nvme drives installed on the mother board. One 1 TB drive has Mx Linux installed, using a vfat boot partition and an ext4 root partition.

Whichever device contains the boot and root partitions is the one you need to worry about. Please post correct fdisk information for the device as xoal has demonstrated.

[james]

xoal and DukeComposed: Thank you for the help, and here is the info you requested:

Code: Select all

chroot> fdisk -l /dev/nvme2n1
Disk /dev/nvme2n1: 931.51 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: WDS100T1X0E-00AFY0                      
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 3C78339C-D42B-4DAC-AF88-7B5FA5E40CCA

Device          Start        End    Sectors   Size Type
/dev/nvme2n1p1   2048     526335     524288   256M EFI System
/dev/nvme2n1p2 526336 1953521663 1952995328 931.3G Linux filesystem

Best,
James

[DukeComposed]

xoal and DukeComposed: Thank you for the help, and here is the info you requested:

Code: Select all

chroot> fdisk -l /dev/nvme2n1
Disk /dev/nvme2n1: 931.51 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: WDS100T1X0E-00AFY0                      
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 3C78339C-D42B-4DAC-AF88-7B5FA5E40CCA

Device          Start        End    Sectors   Size Type
/dev/nvme2n1p1   2048     526335     524288   256M EFI System
/dev/nvme2n1p2 526336 1953521663 1952995328 931.3G Linux filesystem

OK, based on this, /dev/nvme2n1 is, or should be, your boot device. First things first go into your system BIOS if you haven't already and make sure this exact drive is in the boot menu order. If you only see one 1 TB Western Digital drive, it may accidentally be the other drive if you recently updated the BIOS or made changes to it.

If this drive is listed as a bootable device option in your BIOS, then start your MX USB live session and in Thunar confirm that you can see the drive and, when you click on the "1TB Drive" entry in Devices in the sidebar you see the files in nvme2n1p2. This means there will be a "boot" directory, a "var" directory, an "etc" directory, and a dozen-ish more.

This will all be under /media. It should look almost exactly like what is under /. It should look exactly like what you get running "ls -la" at the chroot prompt. If it's not identical, you're in the wrong place.