Page 1 of 1

[SOLVED] Can't boot MX-23 after clean install on SSD

Posted: Sat Sep 02, 2023 2:20 pm
by jsluk
Hi all,
I am typing from my MX21 USB flash drive with snapshot dated late Aug. 2023. Using Gparted, all the partitions looked fine but just no boot. Don't know enough about the GRUB thing but could the update / fresh install messed up GRUB. Here is my system info:

Code: Select all

[CODE]Snapshot created on: 20230826_1255
System:    Kernel: 5.10.0-23-amd64 [5.10.179-3] x86_64 bits: 64 compiler: gcc v: 10.2.1 
           parameters: BOOT_IMAGE=/antiX/vmlinuz quiet splash 
           Desktop: Xfce 4.18.1 tk: Gtk 3.24.24 info: xfce4-panel wm: xfwm 4.18.0 vt: 7 
           dm: LightDM 1.26.0 Distro: MX-21.3_x64 Wildflower August 26  2023 
           base: Debian GNU/Linux 11 (bullseye) 
Machine:   Type: Desktop Mobo: ASUSTeK model: P8Z77-V DELUXE v: Rev 1.xx serial: <filter> 
           UEFI: American Megatrends v: 2104 date: 08/13/2013 
Battery:   Device-1: hidpp_battery_0 model: Logitech Marathon Mouse/Performance Plus M705 
           serial: <filter> charge: 100% (should be ignored) rechargeable: yes status: Discharging 
CPU:       Info: Quad Core model: Intel Core i5-3570K bits: 64 type: MCP arch: Ivy Bridge 
           family: 6 model-id: 3A (58) stepping: 9 microcode: 17 cache: L2: 6 MiB 
           flags: avx lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 bogomips: 27281 
           Speed: 1731 MHz min/max: 1600/3800 MHz Core speeds (MHz): 1: 1731 2: 1714 3: 1745 
           4: 1775 
           Vulnerabilities: Type: itlb_multihit status: KVM: VMX unsupported 
           Type: l1tf mitigation: PTE Inversion 
           Type: mds status: Vulnerable: Clear CPU buffers attempted, no microcode; SMT disabled 
           Type: meltdown mitigation: PTI 
           Type: mmio_stale_data status: Unknown: No mitigations 
           Type: retbleed status: Not affected 
           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: Not affected 
Graphics:  Device-1: AMD Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] 
           vendor: Sapphire Limited driver: amdgpu v: kernel bus-ID: 01:00.0 chip-ID: 1002:67df 
           class-ID: 0300 
           Display: x11 server: X.Org 1.20.11 compositor: xfwm4 v: 4.18.0 driver: 
           loaded: amdgpu,ati unloaded: fbdev,modesetting,vesa display-ID: :0.0 screens: 1 
           Screen-1: 0 s-res: 2560x1440 s-dpi: 96 s-size: 677x381mm (26.7x15.0") 
           s-diag: 777mm (30.6") 
           Monitor-1: DisplayPort-1 res: 2560x1440 hz: 60 dpi: 93 size: 698x393mm (27.5x15.5") 
           diag: 801mm (31.5") 
           OpenGL: 
           renderer: Radeon RX 570 Series (POLARIS10 DRM 3.40.0 5.10.0-23-amd64 LLVM 11.0.1) 
           v: 4.6 Mesa 20.3.5 direct render: Yes 
Audio:     Device-1: Intel 7 Series/C216 Family High Definition Audio vendor: ASUSTeK 
           driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 chip-ID: 8086:1e20 class-ID: 0403 
           Device-2: AMD Ellesmere HDMI Audio [Radeon RX 470/480 / 570/580/590] 
           vendor: Sapphire Limited driver: snd_hda_intel v: kernel bus-ID: 01:00.1 
           chip-ID: 1002:aaf0 class-ID: 0403 
           Sound Server-1: ALSA v: k5.10.0-23-amd64 running: yes 
           Sound Server-2: PulseAudio v: 14.2 running: yes 
Network:   Device-1: Intel 82579V Gigabit Network vendor: ASUSTeK P8P67 Deluxe driver: e1000e 
           v: kernel port: f040 bus-ID: 00:19.0 chip-ID: 8086:1503 class-ID: 0200 
           IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
           Device-2: Intel Wireless 7265 driver: iwlwifi v: kernel modules: wl port: e000 
           bus-ID: 07:00.0 chip-ID: 8086:095a class-ID: 0280 
           IF: wlan0 state: up mac: <filter> 
           Device-3: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
           vendor: ASUSTeK P8 series driver: r8169 v: kernel port: b000 bus-ID: 0c:00.0 
           chip-ID: 10ec:8168 class-ID: 0200 
           IF: eth1 state: down mac: <filter> 
Bluetooth: Device-1: ASUSTek BCM20702A0 type: USB driver: btusb v: 0.8 bus-ID: 7-1.1:3 
           chip-ID: 0b05:17b5 class-ID: fe01 serial: <filter> 
           Report: hciconfig ID: hci0 rfk-id: 1 state: up address: <filter> bt-v: 2.1 lmp-v: 4.0 
           sub-v: 220e hci-v: 4.0 rev: 15bc 
           Info: acl-mtu: 1021:8 sco-mtu: 64:1 link-policy: rswitch sniff link-mode: slave accept 
           service-classes: rendering, capturing, object transfer, audio 
Drives:    Local Storage: total: 3.35 TiB used: 15.33 GiB (0.4%) 
           SMART Message: Unable to run smartctl. Root privileges required. 
           ID-1: /dev/sda maj-min: 8:0 vendor: Samsung model: SSD 860 EVO 500GB size: 465.76 GiB 
           block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> 
           rev: 2B6Q scheme: GPT 
           ID-2: /dev/sdb maj-min: 8:16 vendor: Western Digital model: WD740GD-00FLC0 
           size: 69.25 GiB block-size: physical: 512 B logical: 512 B speed: 1.5 Gb/s type: N/A 
           serial: <filter> rev: 8F33 scheme: GPT 
           ID-3: /dev/sdc maj-min: 8:32 vendor: Western Digital model: WD740GD-00FLC0 
           size: 69.25 GiB block-size: physical: 512 B logical: 512 B speed: 1.5 Gb/s type: N/A 
           serial: <filter> rev: 8F33 scheme: GPT 
           ID-4: /dev/sdd maj-min: 8:48 vendor: Western Digital model: WD30EFRX-68AX9N0 
           size: 2.73 TiB block-size: physical: 4096 B logical: 512 B speed: 3.0 Gb/s type: N/A 
           serial: <filter> rev: 0A80 scheme: GPT 
           ID-5: /dev/sde maj-min: 8:64 type: USB vendor: SanDisk model: Cruzer Glide 
           size: 29.25 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? 
Swap:      Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default) 
           ID-1: swap-1 type: partition size: 4 GiB used: 0 KiB (0.0%) priority: -2 dev: /dev/sdb4 
           maj-min: 8:20 
           ID-2: swap-2 type: partition size: 6.89 GiB used: 0 KiB (0.0%) priority: -3 
           dev: /dev/sdc3 maj-min: 8:35 
Sensors:   System Temperatures: cpu: 29.8 C mobo: 27.8 C gpu: amdgpu temp: 36.0 C 
           Fan Speeds (RPM): N/A gpu: amdgpu fan: 798 
Repos:     Packages: 1953 note: see --pkg apt: 1944 lib: 932 flatpak: 9 
           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://mirror.steadfast.net/debian bullseye-updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/debian.list 
           1: deb http://mirror.steadfast.net/debian bullseye main contrib non-free
           2: deb http://security.debian.org/debian-security bullseye-security main contrib non-free
           3: deb-src http://mirror.steadfast.net/debian bullseye main contrib non-free
           4: deb http://mirror.steadfast.net/debian bullseye-backports main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/google-chrome.list 
           1: deb [arch=amd64] https://dl.google.com/linux/chrome/deb/ stable main
           Active apt repos in: /etc/apt/sources.list.d/librewolf.list 
           1: deb [arch=amd64] http://deb.librewolf.net bullseye main
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb https://mirror.us.oneandone.net/linux/distributions/mx/packages/mx/repo/ bullseye main non-free
           Active apt repos in: /etc/apt/sources.list.d/onlyoffice.list 
           1: deb https://download.onlyoffice.com/repo/debian squeeze main
Info:      Processes: 277 Uptime: 20m wakeups: 4 Memory: 15.56 GiB used: 2.34 GiB (15.0%) 
           Init: SysVinit v: 2.96 runlevel: 5 default: 5 tool: systemctl Compilers: gcc: N/A 
           alt: 10 Client: shell wrapper v: 5.1.4-release inxi: 3.3.06 
Boot Mode: UEFI
[/code]

Appreciate all the help from the experts. Best regards.

Re: Can't boot MX-23 after clean install on SSD

Posted: Sat Sep 02, 2023 2:23 pm
by Charlie Brown
jsluk wrote: Sat Sep 02, 2023 2:20 pm... but could the update / fresh install messed up GRUB...
It just reinstalls a fresh grub (unless you uncheck grub installation)

What happens when you start pc? No grub? Just a blank screen or a blinking cursor on a blank screen etc..?

Re: Can't boot MX-23 after clean install on SSD

Posted: Sat Sep 02, 2023 2:33 pm
by jsluk
I think that I copied the wrong system information. I believed that the one posted originally is the info for the USB Snap Shot. I am able to use the file manager and point to the MX23 boot folder. I use terminal and here is the info from the command inxi -Fxxxmprz:

Code: Select all

jsluk@MX-22:/media/jsluk/rootMX23/boot
$ inxi -Fxxxmprz
System:    Kernel: 5.10.0-23-amd64 x86_64 bits: 64 compiler: gcc v: 10.2.1 Desktop: Xfce 4.18.1 
           tk: Gtk 3.24.24 info: xfce4-panel wm: xfwm 4.18.0 vt: 7 dm: LightDM 1.26.0 
           Distro: MX-21.3_x64 Wildflower August 26  2023 base: Debian GNU/Linux 11 (bullseye) 
Machine:   Type: Desktop Mobo: ASUSTeK model: P8Z77-V DELUXE v: Rev 1.xx serial: <filter> 
           UEFI: American Megatrends v: 2104 date: 08/13/2013 
Battery:   Device-1: hidpp_battery_0 model: Logitech Marathon Mouse/Performance Plus M705 
           serial: <filter> charge: 100% (should be ignored) rechargeable: yes 
           status: Discharging 
Memory:    RAM: total: 15.56 GiB used: 2.77 GiB (17.8%) 
           RAM Report: permissions: Unable to run dmidecode. Root privileges required. 
CPU:       Info: Quad Core model: Intel Core i5-3570K bits: 64 type: MCP arch: Ivy Bridge rev: 9 
           cache: L2: 6 MiB 
           flags: avx lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 bogomips: 27281 
           Speed: 1669 MHz min/max: 1600/3800 MHz Core speeds (MHz): 1: 1669 2: 1691 3: 1784 
           4: 1806 
Graphics:  Device-1: AMD Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] 
           vendor: Sapphire Limited driver: amdgpu v: kernel bus-ID: 01:00.0 chip-ID: 1002:67df 
           class-ID: 0300 
           Display: x11 server: X.Org 1.20.11 compositor: xfwm4 v: 4.18.0 driver: 
           loaded: amdgpu,ati unloaded: fbdev,modesetting,vesa resolution: 2560x1440~60Hz 
           s-dpi: 96 
           OpenGL: 
           renderer: Radeon RX 570 Series (POLARIS10 DRM 3.40.0 5.10.0-23-amd64 LLVM 11.0.1) 
           v: 4.6 Mesa 20.3.5 direct render: Yes 
Audio:     Device-1: Intel 7 Series/C216 Family High Definition Audio vendor: ASUSTeK 
           driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 chip-ID: 8086:1e20 class-ID: 0403 
           Device-2: AMD Ellesmere HDMI Audio [Radeon RX 470/480 / 570/580/590] 
           vendor: Sapphire Limited driver: snd_hda_intel v: kernel bus-ID: 01:00.1 
           chip-ID: 1002:aaf0 class-ID: 0403 
           Sound Server-1: ALSA v: k5.10.0-23-amd64 running: yes 
           Sound Server-2: PulseAudio v: 14.2 running: yes 
Network:   Device-1: Intel 82579V Gigabit Network vendor: ASUSTeK P8P67 Deluxe driver: e1000e 
           v: kernel port: f040 bus-ID: 00:19.0 chip-ID: 8086:1503 class-ID: 0200 
           IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
           Device-2: Intel Wireless 7265 driver: iwlwifi v: kernel port: e000 bus-ID: 07:00.0 
           chip-ID: 8086:095a class-ID: 0280 
           IF: wlan0 state: up mac: <filter> 
           Device-3: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
           vendor: ASUSTeK P8 series driver: r8169 v: kernel port: b000 bus-ID: 0c:00.0 
           chip-ID: 10ec:8168 class-ID: 0200 
           IF: eth1 state: down mac: <filter> 
Bluetooth: Device-1: ASUSTek BCM20702A0 type: USB driver: btusb v: 0.8 bus-ID: 7-1.1:3 
           chip-ID: 0b05:17b5 class-ID: fe01 serial: <filter> 
           Report: hciconfig ID: hci0 rfk-id: 1 state: up address: <filter> bt-v: 2.1 lmp-v: 4.0 
           sub-v: 220e hci-v: 4.0 rev: 15bc 
Drives:    Local Storage: total: 3.35 TiB used: 45.94 GiB (1.3%) 
           ID-1: /dev/sda vendor: Samsung model: SSD 860 EVO 500GB size: 465.76 GiB 
           speed: 6.0 Gb/s type: SSD serial: <filter> rev: 2B6Q scheme: GPT 
           ID-2: /dev/sdb vendor: Western Digital model: WD740GD-00FLC0 size: 69.25 GiB 
           speed: 1.5 Gb/s type: N/A serial: <filter> rev: 8F33 scheme: GPT 
           ID-3: /dev/sdc vendor: Western Digital model: WD740GD-00FLC0 size: 69.25 GiB 
           speed: 1.5 Gb/s type: N/A serial: <filter> rev: 8F33 scheme: GPT 
           ID-4: /dev/sdd vendor: Western Digital model: WD30EFRX-68AX9N0 size: 2.73 TiB 
           speed: 3.0 Gb/s type: N/A serial: <filter> rev: 0A80 scheme: GPT 
           ID-5: /dev/sde type: USB vendor: SanDisk model: Cruzer Glide size: 29.25 GiB 
           type: N/A serial: <filter> rev: 1.00 scheme: MBR 
Partition: ID-1: /live/boot-dev size: 28.67 GiB used: 15.33 GiB (53.5%) fs: ext4 dev: /dev/sde1 
           ID-2: /media/jsluk/rootMX23 size: 457.13 GiB used: 30.61 GiB (6.7%) fs: ext4 
           dev: /dev/sda2 
Swap:      ID-1: swap-1 type: partition size: 4 GiB used: 0 KiB (0.0%) priority: -2 
           dev: /dev/sdb4 
           ID-2: swap-2 type: partition size: 6.89 GiB used: 0 KiB (0.0%) priority: -3 
           dev: /dev/sdc3 
Sensors:   System Temperatures: cpu: 29.8 C mobo: 27.8 C gpu: amdgpu temp: 35.0 C 
           Fan Speeds (RPM): N/A gpu: amdgpu fan: 799 
Repos:     Packages: 1953 note: see --pkg apt: 1944 flatpak: 9 
           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://mirror.steadfast.net/debian bullseye-updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/debian.list 
           1: deb http://mirror.steadfast.net/debian bullseye main contrib non-free
           2: deb http://security.debian.org/debian-security bullseye-security main contrib non-free
           3: deb-src http://mirror.steadfast.net/debian bullseye main contrib non-free
           4: deb http://mirror.steadfast.net/debian bullseye-backports main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/google-chrome.list 
           1: deb [arch=amd64] https://dl.google.com/linux/chrome/deb/ stable main
           Active apt repos in: /etc/apt/sources.list.d/librewolf.list 
           1: deb [arch=amd64] http://deb.librewolf.net bullseye main
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb https://mirror.us.oneandone.net/linux/distributions/mx/packages/mx/repo/ bullseye main non-free
           Active apt repos in: /etc/apt/sources.list.d/onlyoffice.list 
           1: deb https://download.onlyoffice.com/repo/debian squeeze main
Info:      Processes: 283 Uptime: 34m wakeups: 4 Init: SysVinit v: 2.96 runlevel: 5 default: 5 
           Compilers: gcc: N/A alt: 10 Shell: Bash v: 5.1.4 running-in: xfce4-terminal 
           inxi: 3.3.06 
Hope this is the proper sys info to start getting help. Thanks

Re: Can't boot MX-23 after clean install on SSD

Posted: Sat Sep 02, 2023 2:37 pm
by Charlie Brown
:)

Thank you but this still (and normally) shows:

Distro: MX-21.3
... mx/packages/mx/repo/ bullseye main ...

That qsi is ok, enough in the meantime...


Just, did you uncheck the grub installation and what happens when booting?


Sometimes one can forget to take the usb stick out and it keeps booting the live usb instead of the disk.

Re: Can't boot MX-23 after clean install on SSD

Posted: Sat Sep 02, 2023 2:44 pm
by jsluk
I see what you mean. I guess that I don't know how to get the MX23 system info. When I look at the SSD where it is installed, it is labeled MX23 with folders root, boot, home, ...
Any ideas how I should proceed?

Re: Can't boot MX-23 after clean install on SSD

Posted: Sat Sep 02, 2023 2:47 pm
by Charlie Brown
Ok, at least you can post the outputs of:

Code: Select all

lsblk -f

Code: Select all

sudo parted -l
And tell us what happens after you press the power button.

Re: Can't boot MX-23 after clean install on SSD

Posted: Sat Sep 02, 2023 2:50 pm
by j2mcgreg
Is this a dual boot situation?

Re: Can't boot MX-23 after clean install on SSD

Posted: Sat Sep 02, 2023 3:38 pm
by jsluk
j2mcgreg wrote: Sat Sep 02, 2023 2:50 pm Is this a dual boot situation?
More than dual, I have Windows 10 Pro, and 3 other Linux distributions on separate SSD.

Re: Can't boot MX-23 after clean install on SSD

Posted: Sat Sep 02, 2023 3:46 pm
by jsluk
Charlie Brown wrote: Sat Sep 02, 2023 2:47 pm Ok, at least you can post the outputs of:

Code: Select all

lsblk -f

Code: Select all

sudo parted -l
And tell us what happens after you press the power button.
Before I post the requested codes, I don't know how to insure that I am posting the correct information from the SSD and not the flash drive USB. When I hit the power button, I hit F8 to bring up the boot loader. It sees the drive that has MX23 but when I select it, I get the dreaded "grub> prompt" as described previously. Then I am stuck because I don't know what to do next,

Re: Can't boot MX-23 after clean install on SSD

Posted: Sat Sep 02, 2023 3:51 pm
by jsluk
Charlie Brown wrote: Sat Sep 02, 2023 2:47 pm Ok, at least you can post the outputs of:

Code: Select all

lsblk -f

Code: Select all

sudo parted -l
And tell us what happens after you press the power button.
Charlie Brown, here it is.

Code: Select all

jsluk@MX-22:/media/jsluk/rootMX23/mnt
$ lsblk -f
NAME   FSTYPE   FSVER LABEL      UUID                                 FSAVAIL FSUSE% MOUNTPOINT
loop0  squashfs 4.0                                                         0   100% /live/linux
sda                                                                                  
├─sda1 vfat     FAT32 EFI-SYSTEM 2E29-3F8C                                           
└─sda2 ext4     1.0   rootMX23   928801df-ad49-4baa-86c1-9d01a1e7de58  403.2G     7% /media/jsluk/ro
sdb                                                                                  
├─sdb1 vfat     FAT32            3513-69F0                                           
├─sdb2 vfat     FAT32            3513-6A94                                           
├─sdb3 ext4     1.0              070686b7-dc3b-4139-9687-0131eeb4856b                
└─sdb4 swap     1                336108cd-71a7-4a49-8535-58876f6e7836                [SWAP]
sdc                                                                                  
├─sdc1 vfat     FAT32            9C74-1D38                                           
├─sdc2 ext4     1.0              bb32dc27-d63b-4050-93b6-810a56bb14d3                
└─sdc3 swap     1                a22479fa-f43b-48c3-a31f-46499a0051ee                [SWAP]
sdd                                                                                  
├─sdd1                                                                               
└─sdd2 ntfs           WD Red 3TB 96C0E142C0E128E7                                    
sde                                                                                  
├─sde1 ext4     1.0   Live-usb   f62ba6dc-04e6-4216-9569-0c47ca0ca408   13.3G    53% /live/boot-dev
└─sde2 vfat     FAT32 LIVE-UEFI  0BA3-7C2B         

Code: Select all

jsluk@MX-22:/media/jsluk/rootMX23/mnt
$ sudo parted -l

We trust you have received the usual lecture from the local System
Administrator. It usually boils down to these three things:

    #1) Respect the privacy of others.
    #2) Think before you type.
    #3) With great power comes great responsibility.

[sudo] password for jsluk: 
Model: ATA Samsung SSD 860 (scsi)
Disk /dev/sda: 500GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags: 

Number  Start   End    Size   File system  Name     Flags
 1      1049kB  269MB  268MB  fat32        primary  boot, esp
 2      269MB   500GB  500GB  ext4         primary


Model: ATA WDC WD740GD-00FL (scsi)
Disk /dev/sdb: 74.4GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags: 

Number  Start   End     Size    File system     Name      Flags
 1      2097kB  1074MB  1072MB  fat32                     boot, esp
 2      1074MB  5369MB  4295MB  fat32           recovery  msftdata
 3      5369MB  70.1GB  64.7GB  ext4
 4      70.1GB  74.4GB  4295MB  linux-swap(v1)            swap


Model: ATA WDC WD740GD-00FL (scsi)
Disk /dev/sdc: 74.4GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags: 

Number  Start   End     Size    File system     Name  Flags
 1      2097kB  317MB   315MB   fat32                 boot, esp
 2      317MB   66.9GB  66.6GB  ext4            root
 3      66.9GB  74.3GB  7403MB  linux-swap(v1)        swap


Model: ATA WDC WD30EFRX-68A (scsi)
Disk /dev/sdd: 3001GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt
Disk Flags: 

Number  Start   End     Size    File system  Name                          Flags
 1      17.4kB  134MB   134MB                Microsoft reserved partition  msftres
 2      135MB   3001GB  3000GB  ntfs         Basic data partition          msftdata


Model: SanDisk Cruzer Glide (scsi)
Disk /dev/sde: 31.4GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags: 

Number  Start   End     Size    Type     File system  Flags
 1      1049kB  31.4GB  31.4GB  primary  ext4         boot
 2      31.4GB  31.4GB  51.4MB  primary  fat32        esp


jsluk@MX-22:/media/jsluk/rootMX23/mnt
$ 

Re: Can't boot MX-23 after clean install on SSD

Posted: Sat Sep 02, 2023 5:54 pm
by fehlix
jsluk wrote: Sat Sep 02, 2023 2:20 pm Hi all,
I am typing from my MX21 USB flash drive with snapshot dated late Aug. 2023. Using Gparted, all the partitions looked fine but just no boot.
What does "can't boot" or "just no boot" mean? Any error messages?
Have you selected from the UEFI boot menu (on ASUS maybe F8 during POST)?
Or is the MX Linux efiGRUB loader not listed?
Can you boot with help of the MX-23 LiveUSB -> LiveBoot Menu -> Boot Rescue -> Select: efi GRUB loader | GRUB menu?

Re: Can't boot MX-23 after clean install on SSD

Posted: Sat Sep 02, 2023 10:10 pm
by jsluk
fehlix wrote: Sat Sep 02, 2023 5:54 pm
jsluk wrote: Sat Sep 02, 2023 2:20 pm Hi all,
What does "can't boot" or "just no boot" mean? Any error messages?
Have you selected from the UEFI boot menu (on ASUS maybe F8 during POST)?
Or is the MX Linux efiGRUB loader not listed?
Can you boot with help of the MX-23 LiveUSB -> LiveBoot Menu -> Boot Rescue -> Select: efi GRUB loader | GRUB menu?
Hi fehlix, I can hit F8 to access the UEFI boot menu. I select the SSD where MX23 is installed. And I get this error message with a black screen for GNU GRUB version 2.06:
"Minimal BASH-like line editing is supported. For the first word. TAB lists possible command completions. Anywhere else TAB lists possible device or file completions.

grub> _"

After this prompt, I have no idea what to do. When I hit TAB, I get a list of commands and I hit reboot to get out of this situation. Do you have any ideas what I should do next? When I first installed MX23, it booted but somehow the rest of my Linux distributions in the other SSD's got all mess up and I could not boot any of them except for the Windows 10 Pro SSD. I was able to repair a couple of them with the suggestions from the other forums. Now, I cannot boot in MX23. Hope that is what you are referring to and thanks.

Re: Can't boot MX-23 after clean install on SSD

Posted: Sat Sep 02, 2023 10:16 pm
by jsluk
fehlix wrote: Sat Sep 02, 2023 5:54 pm
jsluk wrote: Sat Sep 02, 2023 2:20 pm
Can you boot with help of the MX-23 LiveUSB -> LiveBoot Menu -> Boot Rescue -> Select: efi GRUB loader | GRUB menu?
Yes, I can boot with the MX-23 LiveUSB and any of the other Linux LiveUSB's. I have not tried Boot Rescue. Not sure I understand the rest of your questions for I am not familiar to the workings of GRUB. Are you suggesting that I boot in this LiveUSB and go to MX tools and start Boot Rescue?

Re: Can't boot MX-23 after clean install on SSD

Posted: Sun Sep 03, 2023 7:12 am
by fehlix
jsluk wrote: Sat Sep 02, 2023 10:16 pm
fehlix wrote: Sat Sep 02, 2023 5:54 pm
Can you boot with help of the MX-23 LiveUSB -> LiveBoot Menu -> Boot Rescue -> Select: efi GRUB loader | GRUB menu?
Yes, I can boot with the MX-23 LiveUSB and any of the other Linux LiveUSB's. I have not tried Boot Rescue. Not sure I understand the rest of your questions for I am not familiar to the workings of GRUB. Are you suggesting that I boot in this LiveUSB and go to MX tools and start Boot Rescue?
On the LiveUSB GRUB Menu you have a last menu entry "Boot Rescue".
Here you will find two entries for searching efi GRUB loader and a 2nd one for searching GRUB menu's.
The system will scan the attached drive an displays a list of found items.
It may find for MX23 /MX Linux at least two efi-GRUB loader (bootx64.ef and grubx64.efi) for efi loader,
and it also may find a grub.cfg .
Please try all found. and whether it shows you a GRUB menu of the installed system and you can boot into the system.
Also it should work with the MX-21 Live USB, suggest to try it also with the fresh MX-23 LiveUSB.

Re: Can't boot MX-23 after clean install on SSD

Posted: Sun Sep 03, 2023 11:23 am
by jsluk
fehilix, before I do the above precedures, should I disconnect the other SSD's so that they would not be affected by this change. I asked because after I upgraded to MX23, all the other linux distributions on the other SSD's stop booting up when the pc is powered up? Thanks.

Re: Can't boot MX-23 after clean install on SSD

Posted: Sun Sep 03, 2023 12:37 pm
by fehlix
jsluk wrote: Sun Sep 03, 2023 11:23 am fehilix, before I do the above precedures, should I disconnect the other SSD's so that they would not be affected by this change. I asked because after I upgraded to MX23, all the other linux distributions on the other SSD's stop booting up when the pc is powered up? Thanks.
Probably an issue with your UEFI firmeware system. Also you mentioned only F8 and selecting the drive.
Normally the UEFI boot menu would list all entries added to the UEFI-NVRAM, e.g. like "MX Linux" or MX23
The "test" with the LiveBoot-Rescue menu is just a check whether you have bootable GRUB with either a working efi-loader or a GRUB menu.
The test when verified with either of efi-loader and/or GRUB menu searching would you give a GRUB menu which boot into the system. If that works, something with the UEFI-system on the motherboard need to be adjusted.
E.g when you go into UEFI System Setup you may find and entry like "Add efi file" or "trust EFI file",
b/c no all UEFI system accept adding entry from Linux with help of efibootmgr. If that's the case,
you may need first to enabled secureboot, reboot again int o the UEFI system and select a trusted efi-File
from the ESP ( e.g. naviagte to .../EFI/mx23/grubx64.efi) - don't choose the falback loader /EFI/BOOT/bootx64.efi), b/c the fallback loader is meant to get loaded when select the drive with F8.
When done disable secureboot again.

Other Linux system like Ubuntu etc do have a bit more "logic" added with the ESP entries, where you may find something like BOOT.CSV, fbx64.efi and shim64.efi. If thos are presend the EFI system dynamical tries to add this system into the NVRAM and folowed by booting those entries, which may fail b/c the triggered logic to add an entry is not bullet proof. So you might also look on the ESP of the other installs and tidy up unused sub-directorires, to avoid such hanger.
Further to you question of disconnecting a drive : UEFI System is dynamical one: If you disconnect drives with ESP, any valid entry from those ESPs within NVRAM may be get deleted by the UEFI system at next boot b/c the system "assumes" those are invalid.

Re: Can't boot MX-23 after clean install on SSD

Posted: Sun Sep 03, 2023 4:21 pm
by jsluk
Wow, thanks fehlix. A lot of good stuff to digest. Many terms I am not familiar with such as NVRAM, and when I go into UEFI System Setup, etc. Will study this some before proceeding. Will report back once I get started. Best regards.

Re: Can't boot MX-23 after clean install on SSD

Posted: Sun Sep 03, 2023 8:31 pm
by jsluk
Thought that I would share with you all that I was successful in downgrading GRUB to a previous stable version. The guy over at Xerolinux had a very detailed you tube version showing step by step instructions. Once GRUB is reinstalled, all my other distributions came back. I will closed this topic and thanks to all who pitch in was suggestions. Best regards.

Re: [SOLVED] Can't boot MX-23 after clean install on SSD

Posted: Sun Sep 03, 2023 8:56 pm
by FullScale4Me
I've watched a few videos where he (Steve) was on by himself or a part of a panel of speakers (TheLinuxCast).

Well worth time spent watching.