Grub installation failed mx linux

Grub installation failed

I had a good running installation of Debian Jessie, but then I ran apt-get update && apt-get upgrade && apt-get dist-upgrade . And then after rebooting, it came directly to the BIOS. I realized that Grub was missing, so I ran a live cd and entered Rescue mode , mounted my root partition, + the boot partition and ran these commands: Grub finds the linux image:

root@debian:~# update-grub Generating grub configuration file . Found background image: /usr/share/images/desktop-base/desktop-grub.png Found linux image: /boot/vmlinuz-4.9.0-3-amd64 Found initrd image: /boot/initrd.img-4.9.0-3-amd64 Found linux image: /boot/vmlinuz-4.9.0-0.bpo.3-amd64 Found initrd image: /boot/initrd.img-4.9.0-0.bpo.3-amd64 Found linux image: /boot/vmlinuz-3.16.0-4-amd64 Found initrd image: /boot/initrd.img-3.16.0-4-amd64 Found Ubuntu 16.10 (16.10) on /dev/sdb2 Adding boot menu entry for EFI firmware configuration done 

root@debian:~# grub-install /dev/sda Installing for x86_64-efi platform. Could not prepare Boot variable: No such file or directory grub-install: error: efibootmgr failed to register the boot entry: Input/output error. 

root@debian:~# lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 223.6G 0 disk ├─sda1 8:1 0 92.6G 0 part / ├─sda2 8:2 0 130.4G 0 part └─sda3 8:3 0 573M 0 part /boot/efi 

root@debian:~# ls -l /boot/efi/EFI/debian/ total 120 -rwx------ 1 root root 121856 Jul 20 20:29 grubx64.efi 

root@debian:~# efibootmgr --verbose | grep debian 

grub-install: info: executing efibootmgr -c -d /dev/sda -p 3 -w -L grub -l \EFI\grub\grubx64.efi. Could not prepare Boot variable: No such file or directory grub-install: error: efibootmgr failed to register the boot entry: Input/output error. 

Источник

MX Linux Forum

Important information
—If in starting your system it boots to an unwanted Desktop, right click desktop, then select leave and logout. At the
login screen there is a session chooser at the top of the screen.

News
— MX Linux on social media: here
— New Forum Features, Marking Solved and Referencing a User: here

[Solved] Grub won’t install: Dual boot MX-21 March KDE & Win 10

Help with the version of MX KDE officially released by the Development Team.
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.

[Solved] Grub won’t install: Dual boot MX-21 March KDE & Win 10

#1 Post by serviteur » Mon Apr 11, 2022 6:51 am

I have an issue with the Grub installation. it’s similar to this post/topic I created last year:https://forum.mxlinux.org/viewtopic.php . book+8760w
When I launched »MX Boot Repair», I had an error pop text below.

Installing for x86_64-efi platform. grub-install: warning: Cannot set EFI variable Boot0000. grub-install: warning: efivarfs_set_variable: writing to fd 6 failed: No space left on device. grub-install: warning: _efi_set_variable_mode: ops->set_variable() failed: No space left on device. grub-install: error: failed to register the EFI boot entry: No space left on device 

demo@mx1:~ $ sudo update-grub 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 demo: /usr/sbin/grub-probe: error: failed to get canonical path of `overlay'. demo@mx1:~ $ 

Snapshot created on: 20220315_1055 System: Kernel: 5.10.0-12-amd64 x86_64 bits: 64 compiler: gcc v: 10.2.1 parameters: BOOT_IMAGE=/antiX/vmlinuz quiet Desktop: KDE Plasma 5.20.5 wm: kwin_x11 vt: 7 dm: SDDM Distro: MX-21_KDE_x64 Wildflower October 20 2021 base: Debian GNU/Linux 11 (bullseye) Machine: Type: Laptop System: Hewlett-Packard product: HP EliteBook 8760w v: A0001D02 serial: Chassis: type: 10 serial: Mobo: Hewlett-Packard model: 1630 v: KBC Version 01.3D serial: UEFI: Hewlett-Packard v: 68SAD Ver. F.66 date: 02/13/2018 Battery: ID-1: BAT0 charge: 56.5 Wh (97.4%) condition: 58.0/58.0 Wh (100.0%) volts: 16.3 min: 14.4 model: Hewlett-Packard Primary type: Li-ion serial: status: Unknown CPU: Info: Quad Core model: Intel Core i7-2760QM bits: 64 type: MT MCP arch: Sandy Bridge family: 6 model-id: 2A (42) stepping: 7 microcode: 2F cache: L2: 6 MiB flags: avx lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 bogomips: 38315 Speed: 1113 MHz min/max: 800/3500 MHz Core speeds (MHz): 1: 1139 2: 1299 3: 1240 4: 1187 5: 1081 6: 1094 7: 1788 8: 1359 Vulnerabilities: Type: itlb_multihit status: KVM: VMX unsupported Type: l1tf mitigation: PTE Inversion Type: mds status: Vulnerable: Clear CPU buffers attempted, no microcode; SMT vulnerable Type: meltdown mitigation: PTI Type: spec_store_bypass status: Vulnerable Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization Type: spectre_v2 mitigation: Retpolines, IBPB: conditional, IBRS_FW, STIBP: conditional, RSB filling Type: srbds status: Not affected Type: tsx_async_abort status: Not affected Graphics: Device-1: NVIDIA GF104GLM [Quadro 4000M] vendor: Hewlett-Packard driver: nouveau v: kernel bus-ID: 01:00.0 chip-ID: 10de:0e3b class-ID: 0300 Device-2: Sunplus Innovation HP Universal Camera type: USB driver: uvcvideo bus-ID: 4-1.4:4 chip-ID: 1bcf:2888 class-ID: 0e02 Display: x11 server: X.Org 1.20.13 compositor: kwin_x11 driver: loaded: modesetting unloaded: fbdev,vesa display-ID: :0 screens: 1 Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.0x11.2") s-diag: 582mm (22.9") Monitor-1: LVDS-1 res: 1920x1080 hz: 60 dpi: 128 size: 381x214mm (15.0x8.4") diag: 437mm (17.2") OpenGL: renderer: NVC4 v: 4.3 Mesa 21.2.5 direct render: Yes Audio: Device-1: Intel 6 Series/C200 Series Family High Definition Audio vendor: Hewlett-Packard driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 chip-ID: 8086:1c20 class-ID: 0403 Device-2: NVIDIA GF104 High Definition Audio vendor: Hewlett-Packard driver: snd_hda_intel v: kernel bus-ID: 01:00.1 chip-ID: 10de:0beb class-ID: 0403 Sound Server-1: ALSA v: k5.10.0-12-amd64 running: yes Sound Server-2: PulseAudio v: 14.2 running: yes Network: Device-1: Intel 82579LM Gigabit Network vendor: Hewlett-Packard driver: e1000e v: kernel port: 5020 bus-ID: 00:19.0 chip-ID: 8086:1502 class-ID: 0200 IF: eth0 state: up speed: 1000 Mbps duplex: full mac: Device-2: Intel Centrino Ultimate-N 6300 driver: iwlwifi v: kernel modules: wl port: 4000 bus-ID: 25:00.0 chip-ID: 8086:4238 class-ID: 0280 IF: wlan0 state: down mac: Drives: Local Storage: total: 494.67 GiB used: 0 KiB (0.0%) SMART Message: Unable to run smartctl. Root privileges required. ID-1: /dev/sda maj-min: 8:0 vendor: Smart Modular Tech. model: SHGS31-500GS-2 size: 465.76 GiB block-size: physical: 4096 B logical: 512 B speed: 3.0 Gb/s type: SSD serial: rev: 0Q00 scheme: GPT ID-2: /dev/sdb maj-min: 8:16 type: USB model: USB DISK 3.0 size: 28.91 GiB block-size: physical: 512 B logical: 512 B type: N/A serial: rev: PMAP scheme: GPT SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure? Swap: Alert: No swap data was found. Sensors: System Temperatures: cpu: 59.0 C mobo: 52.0 C gpu: nouveau temp: 54.0 C Fan Speeds (RPM): N/A Repos: Packages: note: see --pkg apt: 2336 lib: 1296 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/mx.list 1: deb http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo/ bullseye main non-free 2: deb http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo/ bullseye ahs Info: Processes: 251 Uptime: 1m wakeups: 2 Memory: 31.31 GiB used: 1.05 GiB (3.4%) Init: SysVinit v: 2.96 runlevel: 5 default: 5 tool: systemctl Compilers: gcc: 10.2.1 alt: 10 Shell: quick-system-in default: Bash v: 5.1.4 running-in: quick-system-in inxi: 3.3.06 

Command: sudo efibootmgr -v

demo@mx1:~ $ sudo efibootmgr -v 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 demo: No BootOrder is set; firmware will attempt recovery Boot0001* Notebook Hard Drive BBS(HD, ,0x0). Boot0004* Notebook Hard Drive BBS(HD, ,0x0). Boot0005* USB Hard Drive 1 - USB DISK 3.0 BBS(HD, ,0x900). demo@mx1:~

demo@mx1:~ $ grep efivarfs /proc/self/mounts efivarfs /sys/firmware/efi/efivars efivarfs rw,relatime 0 0 demo@mx1:~

demo@mx1:~ $ ls -1 /sys/firmware/efi/efivars/dump* | wc -l ls: cannot access '/sys/firmware/efi/efivars/dump*': Invalid argument 0 demo@mx1:~

$ sudo sudo parted -l Model: ATA SHGS31-500GS-2 (scsi) Disk /dev/sda: 500GB Sector size (logical/physical): 512B/4096B Partition Table: gpt Disk Flags: Number Start End Size File system Name Flags 1 1049kB 106MB 105MB fat32 EFI system partition boot, esp 2 106MB 123MB 16.8MB Microsoft reserved partition msftres 3 123MB 393GB 393GB ntfs Basic data partition msftdata 4 393GB 479GB 85.9GB ext4 6 479GB 495GB 16.6GB ntfs Basic data partition msftdata 7 495GB 500GB 4295MB fat32 Basic data partition msftdata 8 500GB 500GB 533MB ntfs hidden, diag Model: USB DISK 3.0 (scsi) Disk /dev/sdb: 31.0GB Sector size (logical/physical): 512B/512B Partition Table: gpt Disk Flags: Number Start End Size File system Name Flags 1 1049kB 31.0GB 31.0GB Ventoy msftdata 2 31.0GB 31.0GB 33.6MB fat16 VTOYEFI hidden, msftdata Model: Linux device-mapper (linear) (dm) Disk /dev/mapper/ventoy: 2473MB Sector size (logical/physical): 512B/512B Partition Table: msdos Disk Flags: Number Start End Size Type File system Flags 2 287kB 4555kB 4268kB primary esp

lsblk -f -o +PARTUUID

demo@mx1:~ $ lsblk -f -o +PARTUUID NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINT PARTUUID loop0 squash 4.0 0 100% /live/linu sda ├─sda1 │ vfat FAT32 SYSTEM │ F4E7-D4D4 4922128c-7ad2-4433-bbce-d4977dcf683a ├─sda2 │ 0353ee48-3287-4807-adf2-1ee8b25b5cd6 ├─sda3 │ ntfs F6E8692EE868EDF5 750f3191-d131-4db4-bdf5-56409efcdbbb ├─sda4 │ ext4 1.0 rootMX21 │ 13899b6b-09ff-4beb-a1a0-82126ab80181 de0c1036-f1ee-0a4b-96b0-b20602908052 ├─sda6 │ ntfs Recovery Image │ 362E44572E4411F3 94041314-7b8c-4796-b3d3-91f24a05ac16 ├─sda7 │ vfat FAT32 HP_TOOLS │ 3A12-BAF5 c6b41dfd-552b-4f6a-9c4e-644addd49384 └─sda8 ntfs 563ADFF73ADFD1DB 97bad949-2853-4d8b-8db9-13954acfd6c7 sdb ├─sdb1 │ exfat 1.0 Ventoy │ 4E21-0000 19a12269-1c91-42a0-87a4-4270705736bf │ └─ventoy │ 0 100% /live/boot └─sdb2 vfat FAT16 VTOYEFI B336-78FD f9157df3-eb96-4ec6-b526-b779f06af017 sr0 demo@mx1:~ $ 

Источник

MX Linux Forum

Important information
—If in starting your system it boots to an unwanted Desktop, right click desktop, then select leave and logout. At the
login screen there is a session chooser at the top of the screen.

News
— MX Linux on social media: here
— New Forum Features, Marking Solved and Referencing a User: here

New installation failed at grub

New installation failed at grub

#1 Post by Ycd83 » Sun May 02, 2021 10:12 pm

Hey,
I’m try to install mx on entire ssd, but the installation stop at end with grub.
Now I have tried mx boot repair, I boot in grub command, the problem is I can’t type any command, like my keyboard don’t work.
Dunno what wrong.

Re: New installation failed at grub

#2 Post by Huckleberry Finn » Sun May 02, 2021 10:39 pm

For SSDs Ahci is recommended as sata mode in Bios settings.

Also have you checked the sum of the downloaded iso ?

• On Windows Rufus is recommended (but not multiboot tools, Balena Etcher etc. ).

• On any Linux distro dd (or) cp commands in a terminal.

• On MX / antiX : «Live Usb Maker» from Menu.

Re: New installation failed at grub

#3 Post by JayM » Sun May 02, 2021 10:46 pm

Please boot your MX live USB, run Quick System Info and post your system information whenever asking for help as per the forum rules (which please read.) Just run it then right-click paste in a reply, don’t copy/paste. Instructions are here if you need them. Thanks.

Please read the Forum Rules, How To Ask For Help, How to Break Your System and Don’t Break Debian. Always include your full Quick System Info (QSI) with each and every new help request.

Re: New installation failed at grub

#4 Post by Ycd83 » Sun May 02, 2021 11:43 pm

Источник