Boot hang after move partitions left in gparted  [Solved]

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.
Message
Author
User avatar
mxismythang
Posts: 40
Joined: Tue Nov 07, 2023 4:05 pm

Boot hang after move partitions left in gparted

#1 Post by mxismythang »

My NVME was dual boot Win10/MX23, and I tired of the Win10 partition, so I booted to MXLive and deleted it and the other superfluous partitions. Afterward, I updated the grubcfg and booted successfully into MX23.

Then I rebooted to MXLive and moved the EFI partition left and rebooted. All was well, MX23 booted fine.

I booted to MXLive again and moved the remaining partitions (/boot, /, /home) left, acknowledging the warning about moving /boot, thinking that a grub update or reinstall would be all that was needed.

After reboot, grub loads MX23 and I am prompted for my luks PW, after which, It successfully opens, but no further.

Is there a chroot or other method to get this sorted out?

(I was going to include a QSI, but it refused to show any partition info, which I suspect is the most important bit.)

Code: Select all

System:
  Kernel: 6.10.10-1-liquorix-amd64 [6.10-12~mx23ahs] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0 parameters: audit=0
    intel_pstate=disable BOOT_IMAGE=/antiX/vmlinuz quiet splasht nosplash
  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.4_ahs_x64 Libretto September 15  2024 base: Debian GNU/Linux
    12 (bookworm)
Machine:
  Type: Desktop Mobo: ASUSTeK model: ROG STRIX Z390-H GAMING v: Rev X.0x
    serial: <superuser required> UEFI: American Megatrends v: 2417 date: 06/03/2019
CPU:
  Info: model: Intel Core i7-8700 bits: 64 type: MT MCP arch: Coffee Lake gen: core 8 level: v3
    note: check built: 2018 process: Intel 14nm family: 6 model-id: 0x9E (158) stepping: 0xA (10)
    microcode: 0xB4
  Topology: cpus: 1x cores: 6 tpc: 2 threads: 12 smt: enabled cache: L1: 384 KiB
    desc: d-6x32 KiB; i-6x32 KiB L2: 1.5 MiB desc: 6x256 KiB L3: 12 MiB desc: 1x12 MiB
  Speed (MHz): avg: 1156 high: 1900 min/max: 800/3201 boost: enabled scaling:
    driver: acpi-cpufreq governor: ondemand cores: 1: 1000 2: 1900 3: 800 4: 1381 5: 1900 6: 1900
    7: 1000 8: 800 9: 800 10: 800 11: 800 12: 800 bogomips: 76799
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3
  Vulnerabilities:
  Type: gather_data_sampling status: Vulnerable: No microcode
  Type: itlb_multihit status: KVM: VMX unsupported
  Type: l1tf mitigation: PTE Inversion
  Type: mds mitigation: Clear CPU buffers; SMT vulnerable
  Type: meltdown mitigation: PTI
  Type: mmio_stale_data mitigation: Clear CPU buffers; SMT vulnerable
  Type: reg_file_data_sampling status: Not affected
  Type: retbleed mitigation: IBRS
  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: IBRS; IBPB: conditional; STIBP: conditional; RSB filling;
    PBRSB-eIBRS: Not affected; BHI: Not affected
  Type: srbds status: Vulnerable: No microcode
  Type: tsx_async_abort mitigation: Clear CPU buffers; SMT vulnerable
Graphics:
  Device-1: AMD Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] vendor: Gigabyte driver: amdgpu
    v: kernel arch: GCN-4 code: Arctic Islands process: GF 14nm built: 2016-20 pcie: gen: 3
    speed: 8 GT/s lanes: 16 ports: active: DP-3 empty: DP-1, DP-2, DVI-D-1, HDMI-A-1
    bus-ID: 01:00.0 chip-ID: 1002:67df class-ID: 0300 temp: 36.0 C
  Display: x11 server: X.Org v: 1.21.1.7 compositor: xfwm v: 4.18.0 driver: X: loaded: amdgpu
    unloaded: fbdev,modesetting,vesa dri: radeonsi gpu: amdgpu display-ID: :0.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: DP-3 mapped: DisplayPort-2 model: Acer XF250Q serial: <filter> built: 2018
    res: 1920x1080 hz: 60 dpi: 90 gamma: 1.2 size: 544x303mm (21.42x11.93") diag: 623mm (24.5")
    ratio: 16:9 modes: max: 1920x1080 min: 720x400
  API: OpenGL v: 4.6 Mesa 23.1.2-1~mx23ahs renderer: AMD Radeon RX 580 Series (polaris10 LLVM
    15.0.6 DRM 3.57 6.10.10-1-liquorix-amd64) direct-render: Yes
Audio:
  Device-1: Intel Cannon Lake PCH cAVS vendor: ASUSTeK driver: snd_hda_intel v: kernel
    bus-ID: 1-12:5 chip-ID: 0951:16c4 alternate: snd_soc_avs,snd_sof_pci_intel_cnl class-ID: 0300
    bus-ID: 00:1f.3 chip-ID: 8086:a348 class-ID: 0403
  Device-2: AMD Ellesmere HDMI Audio [Radeon RX 470/480 / 570/580/590] vendor: Gigabyte
    driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16 bus-ID: 01:00.1
    chip-ID: 1002:aaf0 class-ID: 0403
  Device-3: Kingston HyperX Cloud Flight Wireless Headset type: USB
    driver: hid-generic,snd-usb-audio,usbhid
  API: ALSA v: k6.10.10-1-liquorix-amd64 status: kernel-api tools: alsamixer,amixer
  Server-1: PipeWire v: 1.0.0 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:15bc class-ID: 0200
  IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Drives:
  Local Storage: total: 1.37 TiB used: 390.59 GiB (27.8%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:1 vendor: Samsung model: SSD 970 EVO Plus 1TB size: 931.51 GiB
    block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 type: SSD serial: <filter>
    rev: 2B2QEXM7 temp: 37.9 C scheme: GPT
  ID-2: /dev/nvme1n1 maj-min: 259:0 vendor: Samsung model: SSD 970 EVO Plus 500GB
    size: 465.76 GiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 type: SSD
    serial: <filter> rev: 2B2QEXM7 temp: 40.9 C scheme: GPT
  ID-3: /dev/sda maj-min: 8:0 type: USB model: USB DISK 2.0 size: 7.46 GiB block-size:
    physical: 512 B logical: 512 B type: N/A serial: <filter> rev: PMAP scheme: GPT
  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: 31.0 C mobo: N/A gpu: amdgpu temp: 36.0 C
  Fan Speeds (RPM): N/A gpu: amdgpu fan: 2090
Repos:
  Packages: pm: dpkg pkgs: 2119 libs: 1052 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 https://mxrepo.com/mx/repo/ bookworm main non-free
    2: deb https://mxrepo.com/mx/repo/ bookworm ahs
Info:
  Processes: 356 Uptime: 0m wakeups: 1 Memory: 31.27 GiB used: 1.28 GiB (4.1%) 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

User avatar
mxismythang
Posts: 40
Joined: Tue Nov 07, 2023 4:05 pm

Re: Boot hang after move partitions left in gparted  [Solved]

#2 Post by mxismythang »

I was able to fix this using the boot-repair tool in a live environment. https://sourceforge.net/p/boot-repair/home/Home/
I don't know if the problem should have been fixed by the MX Boot Repair, or if something was encountered that it couldn't detect as a problem. It completed with no errors, but never booted past decryption. I do see the boot-repair tool did not detect fstab entries for the / and /boot partitions:

Code: Select all

nvme0n1p1	: is---ESP,	part-has-no-fstab,	no-nt,	no-winload,	no-recov-nor-hid,	no-bmgr,	notwinboot, vfat
nvme0n1p5	: isnotESP,	part-has-no-fstab,	no-nt,	no-winload,	no-recov-nor-hid,	no-bmgr,	notwinboot, ext4
Here is the detail/info of that repair operation:

Code: Select all

The default repair of the Boot-Repair utility would reinstall the grub-efi of
mapper/luks-[filtered],
using the following options:  nvme0n1p5/boot nvme0n1p1/boot/efi

/boot detected. Please check the options.
The settings chosen by the user will reinstall the grub-efi of
mapper/luks-[filtered],
using the following options:  disable-internet-check nvme0n1p5/boot nvme0n1p1/boot/efi
Additional repair will be performed:  unhide-bootmenu-5s use-standard-efi-file


/boot added in mapper/luks-[filtered]/fstab
/boot/efi added in mapper/luks-[filtered]/fstab
Mount /dev/nvme0n1p5 on /media/demo/rootMX23/boot
Mount /dev/nvme0n1p1 on /media/demo/rootMX23/boot/efi
No mapper/luks-[filtered]/boot/efi/efi/ ubuntu/mint folder

Unhide GRUB boot menu in mapper/luks-[filtered]/etc/default/grub

= Reinstall the grub-efi of /dev/mapper/luks-[filtered] ==

chroot /media/demo/rootMX23 grub-install --version
grub-install (GRUB) 2.06-13+deb12u1
modprobe: FATAL: Module efivars not found in directory /lib/modules/6.10.10-1-liquorix-amd64
chroot /media/demo/rootMX23 modprobe efivars

chroot /media/demo/rootMX23 efibootmgr -v (filtered) before grub install
EFI variables are not supported on this system.


chroot /media/demo/rootMX23 uname -r
6.10.10-1-liquorix-amd64

chroot /media/demo/rootMX23 grub-install --efi-directory=/boot/efi --target=x86_64-efi
Installing for x86_64-efi platform.
grub-install: warning: EFI variables are not supported on this system..
Installation finished. No error reported.
Error: no grub*.efi generated for Debian GNU/Linux 12 (bookworm). Please report this message to boot.repair@gmail.com

chroot /media/demo/rootMX23 efibootmgr -v (filtered) after grub install
EFI variables are not supported on this system.

Warning: NVram is locked (Debian not found in efibootmgr).

chroot /media/demo/rootMX23 update-grub
Found theme: /boot/grub/themes/mx_linux/theme.txt
Found linux image: /boot/vmlinuz-6.12.7-2-liquorix-amd64
Found initrd image: /boot/initrd.img-6.12.7-2-liquorix-amd64
Found linux image: /boot/vmlinuz-6.11.10-1-liquorix-amd64
Found initrd image: /boot/initrd.img-6.11.10-1-liquorix-amd64
Found linux image: /boot/vmlinuz-6.11.9-1-liquorix-amd64
Found initrd image: /boot/initrd.img-6.11.9-1-liquorix-amd64
Found linux image: /boot/vmlinuz-6.6.12-1-liquorix-amd64
Found initrd image: /boot/initrd.img-6.6.12-1-liquorix-amd64
Found mtest-64.efi image: /uefi-mt/mtest-64.efi
Found Windows Boot Manager on /dev/nvme1n1p2@/efi/Microsoft/Boot/bootmgfw.efi
Adding boot menu entry for EFI firmware configuration

An error occurred during the repair.
Error: no grub*.efi generated for Debian GNU/Linux 12 (bookworm). Please report this message to boot.repair@gmail.com

Locked-NVram detected. Please do not forget to make your UEFI firmware boot on the Debian GNU/Linux 12 (bookworm) entry (nvme0n1p1 file) !
Not the error about not generating the grub*.efi, which seems to have had no effect on my system.

Below is the missing Partition info I couldn't access in MXLive:

Code: Select all

Partition:
  ID-1: / raw-size: 36.77 GiB size: 35.9 GiB (97.62%) used: 19.64 GiB (54.7%) fs: ext4
    dev: /dev/dm-0 maj-min: 253:0 mapped: luks-<filter>
  ID-2: /boot raw-size: 1.05 GiB size: 1022.5 MiB (95.20%) used: 410.1 MiB (40.1%) fs: ext4
    dev: /dev/nvme1n1p5 maj-min: 259:7
  ID-3: /boot/efi raw-size: 100 MiB size: 98.4 MiB (98.45%) used: 411 KiB (0.4%) fs: vfat
    dev: /dev/nvme1n1p1 maj-min: 259:6
  ID-4: /home raw-size: 893.56 GiB size: 878.46 GiB (98.31%) used: 546.96 GiB (62.3%) fs: ext4
    dev: /dev/dm-1 maj-min: 253:1 mapped: luks-<filter>
Swap:
  Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: file size: 4 GiB used: 0 KiB (0.0%) priority: -2 file: /swapfile

Post Reply

Return to “MX Help”