apt full-upgrade - DKMS error - Grub Error

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
@ajaxStardust
Posts: 106
Joined: Thu Sep 23, 2021 2:18 am

Re: apt full-upgrade - DKMS error - Grub Error

#21 Post by @ajaxStardust »

fehlix wrote: Mon Sep 19, 2022 3:30 am In case you have already reinstalled using the lasted MX-21.2.1 ISO, you are probably good.
Also, next time you have been asked to provide QSI-report, please do so and post the report provided by the tool "Quick System Info"
Many thanks!
(haven't taken any action yet, but will provide update thereafter)

FTR, i basically just SSH from windows to MX Linux. So everything (at least in relation to my recent posts here) is command line. I realize there are probably "better" distros for a LAMP stack specific system, but I do also like MX Linux when I'm in the XFCE desktop environment. I'm interested to try the KDE version. Haven't used KDE in 10+ years.

In any case, MX-Linux has become my new vesion of an old-friend.
:D

Y'all are really great here, BTW. Feels like home!
:cat:
Check some old recordings feat me on guitar (acct is dude censored face) at: SoundCloud com /ajaxStardust+
on the Don: vivaldi social /@ajaxStardust

User avatar
@ajaxStardust
Posts: 106
Joined: Thu Sep 23, 2021 2:18 am

Re: apt full-upgrade - DKMS error - Grub Error

#22 Post by @ajaxStardust »

Code: Select all

System:    Kernel: 5.10.0-18-amd64 [5.10.140-1] x86_64 bits: 64 compiler: gcc v: 10.2.1 
           parameters: BOOT_IMAGE=/vmlinuz-5.10.0-18-amd64 
           root=UUID=<filter> ro quiet splash 
           init=/lib/systemd/systemd 
           Desktop: Xfce 4.16.0 tk: Gtk 3.24.24 info: xfce4-panel wm: xfwm 4.16.1 vt: 7 
           dm: LightDM 1.26.0 Distro: MX-21.2.1_x64 Wildflower April 9  2022 
           base: Debian GNU/Linux 11 (bullseye) 
Machine:   Type: Desktop System: LENOVO product: IdeaCentre K330B v: Lenovo Product 
           serial: <filter> 
           Mobo: LENOVO model: N/A serial: <filter> BIOS: LENOVO v: DPKT22A date: 11/08/2011 
CPU:       Info: Dual Core model: Intel Core i3-2120 bits: 64 type: MT MCP arch: Sandy Bridge 
           family: 6 model-id: 2A (42) stepping: 7 microcode: 2F cache: L2: 3 MiB 
           flags: avx lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 26341 
           Speed: 1596 MHz min/max: 1600/3300 MHz Core speeds (MHz): 1: 1596 2: 1596 3: 1597 
           4: 1597 
           Vulnerabilities: Type: itlb_multihit status: KVM: VMX disabled 
           Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable 
           Type: mds mitigation: Clear CPU buffers; SMT vulnerable 
           Type: meltdown mitigation: PTI 
           Type: mmio_stale_data status: Unknown: No mitigations 
           Type: retbleed status: Not affected 
           Type: spec_store_bypass 
           mitigation: Speculative Store Bypass disabled via prctl and seccomp 
           Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization 
           Type: spectre_v2 mitigation: Retpolines, IBPB: conditional, IBRS_FW, STIBP: 
           conditional, RSB filling, PBRSB-eIBRS: Not affected 
           Type: srbds status: Not affected 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: Intel 2nd Generation Core Processor Family Integrated Graphics vendor: Lenovo 
           driver: i915 v: kernel bus-ID: 00:02.0 chip-ID: 8086:0102 class-ID: 0300 
           Display: x11 server: X.Org 1.20.11 compositor: xfwm4 v: 4.16.1 driver: 
           loaded: modesetting unloaded: fbdev,vesa display-ID: :0.0 screens: 1 
           Screen-1: 0 s-res: 1280x1024 s-dpi: 96 s-size: 338x270mm (13.3x10.6") 
           s-diag: 433mm (17") 
           Monitor-1: VGA-1 res: 1280x1024 hz: 60 dpi: 86 size: 376x301mm (14.8x11.9") 
           diag: 482mm (19") 
           OpenGL: renderer: Mesa DRI Intel HD Graphics 2000 (SNB GT1) v: 3.3 Mesa 20.3.5 
           compat-v: 3.0 direct render: Yes 
Audio:     Device-1: Intel 6 Series/C200 Series Family High Definition Audio vendor: Lenovo 
           driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 chip-ID: 8086:1c20 class-ID: 0403 
           Sound Server-1: ALSA v: k5.10.0-18-amd64 running: yes 
           Sound Server-2: PulseAudio v: 14.2 running: yes 
Network:   Device-1: Intel 82579V Gigabit Network vendor: Lenovo driver: e1000e v: kernel 
           port: f080 bus-ID: 00:19.0 chip-ID: 8086:1503 class-ID: 0200 
           IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
           IF-ID-1: br-df74fea0304f state: down mac: <filter> 
           IF-ID-2: docker0 state: down mac: <filter> 
Drives:    Local Storage: total: 231.03 GiB used: 14.46 GiB (6.3%) 
           SMART Message: Unable to run smartctl. Root privileges required. 
           ID-1: /dev/sda maj-min: 8:0 vendor: Kingston model: SA400S37240G size: 223.57 GiB 
           block-size: physical: 512 B logical: 512 B speed: 3.0 Gb/s type: SSD serial: <filter> 
           rev: 0105 scheme: MBR 
           ID-2: /dev/sdb maj-min: 8:16 type: USB vendor: SanDisk model: Cruzer Edge 
           size: 7.45 GiB block-size: physical: 512 B logical: 512 B type: N/A serial: <filter> 
           rev: 1.26 scheme: MBR 
           SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure? 
Partition: ID-1: / raw-size: 217.42 GiB size: 212.95 GiB (97.94%) used: 14.2 GiB (6.7%) fs: ext4 
           dev: /dev/dm-0 maj-min: 253:0 mapped: root.fsm 
           ID-2: /boot raw-size: 512 MiB size: 487.2 MiB (95.16%) used: 262.9 MiB (54.0%) fs: ext4 
           dev: /dev/sda1 maj-min: 8:1 
Swap:      Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default) 
           ID-1: swap-1 type: file size: 1024 MiB used: 0 KiB (0.0%) priority: -2 file: /swapfile 
           ID-2: swap-2 type: partition size: 5.61 GiB used: 0 KiB (0.0%) priority: -3 
           dev: /dev/dm-1 maj-min: 253:1 mapped: swap 
Sensors:   System Temperatures: cpu: 43.0 C mobo: N/A 
           Fan Speeds (RPM): N/A 
Repos:     Packages: note: see --pkg apt: 2388 lib: 1066 flatpak: 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 bullseye-updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/debian.list 
           1: deb http://deb.debian.org/debian bullseye main contrib non-free
           2: deb http://security.debian.org/debian-security bullseye-security main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/docker.list 
           1: deb [arch=amd64 signed-by=/etc/apt/keyrings/docker.gpg] https://download.docker.com/linux/debian bullseye stable
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo/ bullseye main non-free
Info:      Processes: 236 Uptime: 0m wakeups: 0 Memory: 3.69 GiB used: 1.06 GiB (28.8%) 
           Init: systemd v: 247 runlevel: 5 default: 5 tool: systemctl Compilers: gcc: 10.2.1 
           alt: 10 Client: shell wrapper v: 5.1.4-release inxi: 3.3.06 
Boot Mode: BIOS (legacy, CSM, MBR)
from the MX Linux desktop, as advised
Check some old recordings feat me on guitar (acct is dude censored face) at: SoundCloud com /ajaxStardust+
on the Don: vivaldi social /@ajaxStardust

User avatar
dolphin_oracle
Developer
Posts: 22731
Joined: Sun Dec 16, 2007 12:17 pm

Re: apt full-upgrade - DKMS error - Grub Error

#23 Post by dolphin_oracle »

FWIW, you can use

Code: Select all

quick-system-info-mx -g
at the cli to get the same report as the gui.
http://www.youtube.com/runwiththedolphin
lenovo ThinkPad X1 Extreme Gen 4 - MX-23
FYI: mx "test" repo is not the same thing as debian testing repo.
Live system help document: https://mxlinux.org/wiki/help-antix-live-usb-system/

User avatar
@ajaxStardust
Posts: 106
Joined: Thu Sep 23, 2021 2:18 am

Re: apt full-upgrade - DKMS error - Grub Error

#24 Post by @ajaxStardust »

dolphin_oracle wrote: Mon Sep 19, 2022 6:48 am FWIW, you can use

Code: Select all

quick-system-info-mx -g
:rock: Thank you! :D
I appreciate that as I truly only know (aka. only remember) the basic stuff (grep, find, pico, etc.) without referencing and going down some rabbit hole, so such guidance is greatly appreciated. Y'all might empathize with the notion when working on something really advanced. :cool: ;)

Will read the advisories above after some much needed sleep, prior to any operations.

I don't know if it's necessary to report, given what's said here …
asqwerth wrote: Mon Sep 19, 2022 2:41 am No further update/fix is going to help you if you keep your pre-MX21.2 install, since it was not a buggy update. … So either you install afresh the new MX21.2, or you follow fehlix's instructions to sort out the grub on your current MX installation.
… while it probably only reiterates, I'd like to mention that everything about the system is running just fine (outside of needing to have the USB stick to boot). neither `apt update` nor apt `full-upgrade` reports no available package updatesI have every bit of confidence that I can fix the existing installation. I just didn't feel like messing with it that day. :wink:
Check some old recordings feat me on guitar (acct is dude censored face) at: SoundCloud com /ajaxStardust+
on the Don: vivaldi social /@ajaxStardust

User avatar
fehlix
Developer
Posts: 12908
Joined: Wed Apr 11, 2018 5:09 pm

Re: apt full-upgrade - DKMS error - Grub Error

#25 Post by fehlix »

@ajaxStardust wrote: Mon Sep 19, 2022 9:18 am
dolphin_oracle wrote: Mon Sep 19, 2022 6:48 am FWIW, you can use

Code: Select all

quick-system-info-mx -g
:rock: Thank you! :D
I appreciate that as I truly only know (aka. only remember) the basic stuff (grep, find, pico, etc.) without referencing and going down some rabbit hole, so such guidance is greatly appreciated. Y'all might empathize with the notion when working on something really advanced. :cool: ;)

Will read the advisories above after some much needed sleep, prior to any operations.

I don't know if it's necessary to report, given what's said here …
asqwerth wrote: Mon Sep 19, 2022 2:41 am No further update/fix is going to help you if you keep your pre-MX21.2 install, since it was not a buggy update. … So either you install afresh the new MX21.2, or you follow fehlix's instructions to sort out the grub on your current MX installation.
… while it probably only reiterates, I'd like to mention that everything about the system is running just fine (outside of needing to have the USB stick to boot). neither `apt update` nor apt `full-upgrade` reports no available package updatesI have every bit of confidence that I can fix the existing installation. I just didn't feel like messing with it that day. :wink:
OK, as there seem to be nothing hangin anymore, the remaining bit would be to reinstall GRUB's boot loader int MBR and GRUB's modules into /boot/grub/i386_pc.

To be on the safe side before we do this,
do make a backup of the existing grub directory this way:

On the SSHed terminal do

Code: Select all

sudo cp -a /boot/grub  /boot/grub.old
Now, in case something really goes wrong, you could revert to the old back up like this:
When booted into the MX LiveUSB and mount /boot partition
to rename the directory with the mounted directory of the boot partition

grub to grub.bad

and
grub.old to grub

So grub.old is just a fallback to allow you to boot into using LiveUSB Boot Rescue menus.

Let's install the GRUB boot loader to the MBR and modules:

Within the SSH'd-terminal do run:

Code: Select all

sudo grub-install --recheck /dev/sda 
If that was succeful, do also run

Code: Select all

sudo update-grub
Please post the output of the commands, just in case.
If all was 0k, it should now boot into without the need of the MX LiveUSB.

User avatar
@ajaxStardust
Posts: 106
Joined: Thu Sep 23, 2021 2:18 am

Re: apt full-upgrade - DKMS error - Grub Error

#26 Post by @ajaxStardust »

Thank you so much! very thoughtful, and easy to understand. much appreciated. I'll report how things turn out.
:)
Check some old recordings feat me on guitar (acct is dude censored face) at: SoundCloud com /ajaxStardust+
on the Don: vivaldi social /@ajaxStardust

User avatar
@ajaxStardust
Posts: 106
Joined: Thu Sep 23, 2021 2:18 am

Re: apt full-upgrade - DKMS error - Grub Error

#27 Post by @ajaxStardust »

So... this just happened. I haven't done anything in thread #anchor[25] yet. Just a bit anxious: does anyone expect this update to affect what I'd planned to do per @fehlix guidance?

Code: Select all

sudo apt update
[sudo] password for user:
Get:1 http://deb.debian.org/debian bullseye-updates InRelease [44.1 kB]
Get:2 http://security.debian.org/debian-security bullseye-security InRelease [48.4 kB]
Hit:3 http://deb.debian.org/debian bullseye InRelease
Get:4 http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo bullseye InRelease [19.8 kB]
Hit:5 https://download.docker.com/linux/debian bullseye InRelease
Get:6 http://deb.debian.org/debian bullseye-updates/main i386 Packages.diff/Index [10.6 kB]
Get:7 http://deb.debian.org/debian bullseye-updates/main amd64 Packages.diff/Index [10.6 kB]
Get:8 http://deb.debian.org/debian bullseye-updates/main Translation-en.diff/Index [4,995 B]
Get:9 http://deb.debian.org/debian bullseye-updates/main i386 Contents (deb).diff/Index [3,873 B]
Get:10 http://deb.debian.org/debian bullseye-updates/main amd64 Contents (deb).diff/Index [3,873 B]
Get:11 http://deb.debian.org/debian bullseye-updates/main i386 Packages T-2022-09-22-1635.40-F-2022-09-22-1635.40.pdiff [4,637 B]
Get:12 http://deb.debian.org/debian bullseye-updates/main amd64 Packages T-2022-09-22-1635.40-F-2022-09-22-1635.40.pdiff [4,625 B]
Get:13 http://deb.debian.org/debian bullseye-updates/main Translation-en T-2022-09-22-1635.40-F-2022-09-22-1635.40.pdiff [3,855 B]
Get:11 http://deb.debian.org/debian bullseye-updates/main i386 Packages T-2022-09-22-1635.40-F-2022-09-22-1635.40.pdiff [4,637 B]
Get:13 http://deb.debian.org/debian bullseye-updates/main Translation-en T-2022-09-22-1635.40-F-2022-09-22-1635.40.pdiff [3,855 B]
Get:12 http://deb.debian.org/debian bullseye-updates/main amd64 Packages T-2022-09-22-1635.40-F-2022-09-22-1635.40.pdiff [4,625 B]
Preparing to unpack .../2-grub-pc_2.06-3~deb11u2_amd64.deb ...
Unpacking grub-pc (2.06-3~deb11u2) over (2.06-3~deb11u1) ...
Preparing to unpack .../3-grub-pc-bin_2.06-3~deb11u2_amd64.deb ...
Unpacking grub-pc-bin (2.06-3~deb11u2) over (2.06-3~deb11u1) ...
Preparing to unpack .../4-grub-efi-ia32-bin_2.06-3~deb11u2_amd64.deb ...
Unpacking grub-efi-ia32-bin (2.06-3~deb11u2) over (2.06-3~deb11u1) ...
Preparing to unpack .../5-grub-efi-amd64-bin_2.06-3~deb11u2_amd64.deb ...
Unpacking grub-efi-amd64-bin (2.06-3~deb11u2) over (2.06-3~deb11u1) ...
Preparing to unpack .../6-grub-common_2.06-3~deb11u2_amd64.deb ...
Unpacking grub-common (2.06-3~deb11u2) over (2.06-3~deb11u1) ...
Preparing to unpack .../7-libexpat1_2.2.10-2+deb11u4_amd64.deb ...
Unpacking libexpat1:amd64 (2.2.10-2+deb11u4) over (2.2.10-2+deb11u3) ...
Setting up libexpat1:amd64 (2.2.10-2+deb11u4) ...
Setting up grub-common (2.06-3~deb11u2) ...
Setting up grub-efi-amd64-bin (2.06-3~deb11u2) ...
Setting up grub-efi-ia32-bin (2.06-3~deb11u2) ...
Setting up grub2-common (2.06-3~deb11u2) ...
Setting up grub-pc-bin (2.06-3~deb11u2) ...
Setting up grub-pc (2.06-3~deb11u2) ...
Unable to init server: Could not connect: Connection refused

(frontend:88123): Gtk-WARNING **: 19:12:17.698: cannot open display:
debconf: unable to initialize frontend: Gnome
debconf: (DISPLAY problem?)
debconf: falling back to frontend: Dialog
Installing for i386-pc platform.
grub-install: warning: File system `ext2' doesn't support embedding.
grub-install: warning: Embedding is not possible.  GRUB can only be installed in this setup by using blocklists.  However, blocklists are UNRELIABLE and their use is discouraged..
Installation finished. No error reported.
Generating grub configuration file ...
Found theme: /boot/grub/themes/mx_linux/theme.txt
Found linux image: /boot/vmlinuz-5.10.0-18-amd64
Found initrd image: /boot/initrd.img-5.10.0-18-amd64
Found linux image: /boot/vmlinuz-5.10.0-13-amd64
Found initrd image: /boot/initrd.img-5.10.0-13-amd64
Found memtest86+ image: /memtest86+.bin
grub-probe: error: cannot find a GRUB drive for /dev/sdb1.  Check your device.map.
done
Setting up grub2 (2.06-3~deb11u2) ...
Processing triggers for libc-bin (2.31-13+deb11u4) ...
Processing triggers for man-db (2.9.4-2) ...
Processing triggers for install-info (6.7.0.dfsg.2-6) ...
install-info: warning: no info dir entry in `/usr/share/info/gtkdialog.info.gz'
user@mxlinux-21:~
inquiring, per the part:

Code: Select all

grub-install: warning: File system `ext2' doesn't support embedding.
grub-install: warning: Embedding is not possible.  GRUB can only be installed in this setup by using blocklists.  However, blocklists are UNRELIABLE and their use is discouraged..
I already backed up my /var/www/html and did a mysqldump, just in case...
Check some old recordings feat me on guitar (acct is dude censored face) at: SoundCloud com /ajaxStardust+
on the Don: vivaldi social /@ajaxStardust

User avatar
@ajaxStardust
Posts: 106
Joined: Thu Sep 23, 2021 2:18 am

Re: apt full-upgrade - DKMS error - Grub Error

#28 Post by @ajaxStardust »

@fehlix
here it is:
:)

Code: Select all

user@mxlinux-21:~
$ sudo cp -a /boot/grub  /boot/grub.old
[sudo] password for user:
user@mxlinux-21:~
$ sudo grub-install --recheck /dev/sda -s
Installing for i386-pc platform.
Installation finished. No error reported.
user@mxlinux-21:~
$ sudo grub-install --recheck /dev/sda
Installing for i386-pc platform.
Installation finished. No error reported.
user@mxlinux-21:~
$ sudo update-grub
Generating grub configuration file ...
Found theme: /boot/grub/themes/mx_linux/theme.txt
Found linux image: /boot/vmlinuz-5.10.0-18-amd64
Found initrd image: /boot/initrd.img-5.10.0-18-amd64
Found linux image: /boot/vmlinuz-5.10.0-13-amd64
Found initrd image: /boot/initrd.img-5.10.0-13-amd64
Found memtest86+ image: /memtest86+.bin
grub-probe: error: cannot find a GRUB drive for /dev/sdb1.  Check your device.map.
done
user@mxlinux-21:~

Code: Select all

$ ls -laX /boot
total 250248
drwxr-xr-x  6 root root     4096 Sep 22 19:29 grub
drwx------  2 root root    16384 Sep 12 00:30 lost+found
drwxr-xr-x  5 root root     4096 Sep 22 19:28 .
drwxr-xr-x 20 root root     4096 Sep 13 11:47 ..
-rw-r--r--  1 root root   236106 Mar 17  2022 config-5.10.0-13-amd64
-rw-r--r--  1 root root 79439141 Sep 12 00:34 initrd.img-5.10.0-13-amd64
-rw-r--r--  1 root root       83 Mar 17  2022 System.map-5.10.0-13-amd64
-rw-r--r--  1 root root  6840768 Mar 17  2022 vmlinuz-5.10.0-13-amd64
-rw-r--r--  1 root root   236286 Sep  2 09:54 config-5.10.0-18-amd64
-rw-r--r--  1 root root 81058339 Sep 17 00:53 initrd.img-5.10.0-18-amd64
-rw-r--r--  1 root root       83 Sep  2 09:54 System.map-5.10.0-18-amd64
-rw-r--r--  1 root root  6962016 Sep  2 09:54 vmlinuz-5.10.0-18-amd64
-rw-r--r--  1 root root   182704 Aug 15  2019 memtest86+.bin
-rw-r--r--  1 root root   184884 Aug 15  2019 memtest86+_multiboot.bin
drwxr-xr-x  6 root root     4096 Sep 22 19:12 grub.old
-rw-r--r--  1 root root 81052109 Sep 17 00:53 initrd.img-5.10.0-18-amd64.old-dkms
Check some old recordings feat me on guitar (acct is dude censored face) at: SoundCloud com /ajaxStardust+
on the Don: vivaldi social /@ajaxStardust

User avatar
asqwerth
Developer
Posts: 8038
Joined: Sun May 27, 2007 5:37 am

Re: apt full-upgrade - DKMS error - Grub Error

#29 Post by asqwerth »

The embedding by block lists warning comes up every time before you install grub into root partition . As long as it went well thereafter, it's OK.

Since I believe installing grub into root was the first thing you did, it's there now even if you now also install grub on mbr (sda). Thus you will still get this message.
Desktop: Intel i5-4460, 16GB RAM, Intel integrated graphics
Clevo N130WU-based Ultrabook: Intel i7-8550U (Kaby Lake R), 16GB RAM, Intel integrated graphics (UEFI)
ASUS X42D laptop: AMD Phenom II, 6GB RAM, Mobility Radeon HD 5400

User avatar
fehlix
Developer
Posts: 12908
Joined: Wed Apr 11, 2018 5:09 pm

Re: apt full-upgrade - DKMS error - Grub Error

#30 Post by fehlix »

@ajaxStardust wrote: Thu Sep 22, 2022 7:21 pm So... this just happened. I haven't done anything in thread #anchor[25] yet. Just a bit anxious: does anyone expect this update to affect what I'd planned to do per @fehlix guidance?

Code: Select all

sudo apt update
[sudo] password for user:
Get:1 http://deb.debian.org/debian bullseye-updates InRelease [44.1 kB]
...
...
Preparing to unpack .../2-grub-pc_2.06-3~deb11u2_amd64.deb ...
...
...
(frontend:88123): Gtk-WARNING **: 19:12:17.698: cannot open display:
debconf: unable to initialize frontend: Gnome
debconf: (DISPLAY problem?)
debconf: falling back to frontend: Dialog
Installing for i386-pc platform.
grub-install: warning: File system `ext2' doesn't support embedding.
grub-install: warning: Embedding is not possible.  GRUB can only be installed in this setup by using blocklists.  However, blocklists are UNRELIABLE and their use is discouraged..
Installation finished. No error reported.
Generating grub configuration file ...
Found theme: /boot/grub/themes/mx_linux/theme.txt
Found linux image: /boot/vmlinuz-5.10.0-18-amd64
Found initrd image: /boot/initrd.img-5.10.0-18-amd64
Found linux image: /boot/vmlinuz-5.10.0-13-amd64
Found initrd image: /boot/initrd.img-5.10.0-13-amd64
Found memtest86+ image: /memtest86+.bin
grub-probe: error: cannot find a GRUB drive for /dev/sdb1.  Check your device.map.
done
The terminal output posted appears to be to only partial. It's always best to show the full output not fractions of it.
So next, you have shown the out put of this

Code: Select all

sudo grub-install --recheck /dev/sda
sudo update-grub
grub-probe: error: cannot find a GRUB drive for /dev/sdb1.  Check your device.map.
which went both ok, ignoring grub-probe issues to scan the attached USB,
And it looks like you would now be able to boot from the drive without the helping MX LiveUSB,
b/c a working GRUB loader is now placed within the MBR (Master Boot Record) of the drive sda.

But, let's try to understand what was done. Maybe to avoid future issues with a another upgrade of GRUB with the future:
Please post this command output, which will display what "debconf" had registered for the GRUB boot loader installation:

Code: Select all

sudo debconf-show grub-pc

As indicated already installing GRUB boot loader into a partition, would not make BIOS to boot from this bootloader,
so in the case here would not provide anything for the boot process. It's only offered by grub for cases where user want to chainload into this "partition" bootloader at the partition start, but normally not needed. The warning is to let the user know the partition bootloader even if used from a "chainloader" is unreliable.

Post Reply

Return to “MX Help”