# Grub impossible à lancer. Boot avec menu Intel **URL:** \ **Category:** Support Debian\ **Tags:** boot, grub\ **Created:** [Mai 22, 2021, 4:13 UTC](https://www.debian-fr.org/t/grub-impossible-a-lancer-boot-avec-menu-intel/84663 "2021-05-22T16:13:25Z")\ **Posts on this page:** 13\ **Page:** 1
**Author:** ![Laurent001](https://www.debian-fr.org/letter_avatar_proxy/v4/letter/l/ce73a5/32.png) [@Laurent001](https://www.debian-fr.org/u/Laurent001)\ **Post date:** [Mai 22, 2021, 4:13 UTC](https://www.debian-fr.org/t/grub-impossible-a-lancer-boot-avec-menu-intel/84663/1 "2021-05-22T16:13:25Z")
Bonjour, J’ai un problème de boot. J’y ai passé un bon paquet d’heures. Tout est arrivé quand j’ai voulu mettre un nouveau kernel qui m’empêchait d’arrêter le PC. J’ai mis l’ancien et désormais, au démarrage, j’ai un boot menu d’Intel qui apparaît. Impossible d’avoir grub. Je vois même, dans ce menu, les entrées que j’ai créé via, par exemple rescatux, et impossible de lancer ces entrées. J’ai fait plusieurs essais via un live usb (ventoy) qui contient plein d’iso pour lancer supergrub2, ubuntu live, rescatux et boot-repair live. Je mets un rapport boot-info à la fin. J’ai bcp changé des choses dans le bios pour passer en UEFI ou Legacy ou les 2 (« both »). J’ai aussi fait pas mal de gparted en créant/supprimant mon sda1 pour y mettre le flag boot et esp. J’ai fini par activer une partition de 1mo pour le drapeau bios\_flag (unformatted) [en faisant ceci](https://doc.ubuntu-fr.org/gpt#creer_une_partition_bios-boot) J’ai aussi bcp chrooter via les live-cd. Et j’ai fini par installer debian dans une nouvelle partition pour espérer qu’il fixe le problème pendant l’installation mais nada. Voilà le boot-info qui ne contient pas la dernière install de debian: ``` boot-repair-4ppa125 [20210522_0815] ============================= Boot Repair Summary ============================== No sda3/etc/default/grub /usr/share/boot-sav/bs-cmd_terminal.sh: line 177: warning: command substitution: ignored null byte in input ping: google.com: Temporary failure in name resolution Recommended repair: ____________________________________________________________ The default repair of the Boot-Repair utility will reinstall the grub-efi-amd64-signed of sda2, using the following options: sda1/boot/efi, Additional repair will be performed: unhide-bootmenu-10s use-standard-efi-file /boot/efi added in sda2/fstab rm /mnt/boot-sav/sda1/efi/Boot/bootx64.efi /mnt/boot-sav/sda1/efi/Boot/bootx64.efi.grb Mount sda1 on /mnt/boot-sav/sda2/boot/efi No sda2/boot/efi/efi/ ubuntu/mint folder ================= Reinstall the grub-efi-amd64-signed of sda2 ================== grub-install --version grub-install (GRUB) 2.02+dfsg1-20+deb10u4 efibootmgr -v from chroot before grub install BootCurrent: 001B Timeout: 2 seconds BootOrder: 001B,0000,0001,0002,0005,0010,0011,0012,0013,0014,0015,0016,0006,0017,0018,0019,001A,001C,001D,001E,001F,0020 Boot0000* debian HD(1,GPT,53bf3e64-9298-4ca6-9856-7137c8bb9e1c,0x800,0x82000)/File(EFIdebianshimx64.efi) Boot0001* (Rescapp) shimx64.efi HD(1,GPT,53bf3e64-9298-4ca6-9856-7137c8bb9e1c,0x800,0x82000)/File(EFIdebianshimx64.efi) Boot0002* (Rescapp) grubx64.efi HD(1,GPT,53bf3e64-9298-4ca6-9856-7137c8bb9e1c,0x800,0x82000)/File(EFIdebiangrubx64.efi) Boot0005* (Rescapp) mmx64.efi HD(1,GPT,53bf3e64-9298-4ca6-9856-7137c8bb9e1c,0x800,0x82000)/File(EFIdebianmmx64.efi) Boot0006* (Rescapp) fbx64.efi HD(1,GPT,53bf3e64-9298-4ca6-9856-7137c8bb9e1c,0x800,0x82000)/File(EFIdebianfbx64.efi) Boot0010 Setup FvFile(721c8b66-426c-4e86-8e99-3457c46ab0b9) Boot0011 Boot Menu FvFile(126a762d-5758-4fca-8531-201a7f57f850) Boot0012 Diagnostic Splash Screen FvFile(a7d8d9a6-6ab0-4aeb-ad9d-163e59a7a380) Boot0013 Lenovo Diagnostics FvFile(3f7e615b-0d45-4f80-88dc-26b234958560) Boot0014 Startup Interrupt Menu FvFile(f46ee6f4-4785-43a3-923d-7f786c3c8479) Boot0015 Rescue and Recovery FvFile(665d3f60-ad3e-4cad-8e26-db46eee9f1b5) Boot0016 MEBx Hot Key FvFile(ac6fd56a-3d41-4efd-a1b9-870293811a28) Boot0017* USB CD VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,86701296aa5a7848b66cd49dd3ba6a55) Boot0018* USB FDD VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,6ff015a28830b543a8b8641009461e49) Boot0019* NVMe0 VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,001c199932d94c4eae9aa0b6e98eb8a400) Boot001A* ATA HDD0 VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,91af625956449f41a7b91f4f892ab0f600) Boot001B* USB HDD VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,33e821aaaf33bc4789bd419f88c50803) Boot001C PCI LAN VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,78a84aaf2b2afc4ea79cf5cc8f3d3803) Boot001D* IDER BOOT CDROM PciRoot(0x0)/Pci(0x16,0x2)/Ata(0,1,0) Boot001E* IDER BOOT Floppy PciRoot(0x0)/Pci(0x16,0x2)/Ata(0,0,0) Boot001F* ATA HDD VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,91af625956449f41a7b91f4f892ab0f6) Boot0020* ATAPI CD VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,aea2090adfde214e8b3a5e471856a354) uname -r 5.3.0-28-generic grub-install --efi-directory=/boot/efi --target=x86_64-efi --uefi-secure-boot Installing for x86_64-efi platform. Installation finished. No error reported. df /dev/sda1 touch /mnt/boot-sav/sda2/boot/efi/EFI/Boot/bootx64.efi.grb cp /mnt/boot-sav/sda2/boot/efi/EFI/debian/shimx64.efi /mnt/boot-sav/sda2/boot/efi/EFI/Boot/bootx64.efi efibootmgr -v from chroot after grub install BootCurrent: 001B Timeout: 2 seconds BootOrder: 0000,001B,0001,0002,0005,0010,0011,0012,0013,0014,0015,0016,0006,0017,0018,0019,001A,001C,001D,001E,001F,0020 Boot0000* debian HD(1,GPT,53bf3e64-9298-4ca6-9856-7137c8bb9e1c,0x800,0x82000)/File(EFIdebianshimx64.efi) Boot0001* (Rescapp) shimx64.efi HD(1,GPT,53bf3e64-9298-4ca6-9856-7137c8bb9e1c,0x800,0x82000)/File(EFIdebianshimx64.efi) Boot0002* (Rescapp) grubx64.efi HD(1,GPT,53bf3e64-9298-4ca6-9856-7137c8bb9e1c,0x800,0x82000)/File(EFIdebiangrubx64.efi) Boot0005* (Rescapp) mmx64.efi HD(1,GPT,53bf3e64-9298-4ca6-9856-7137c8bb9e1c,0x800,0x82000)/File(EFIdebianmmx64.efi) Boot0006* (Rescapp) fbx64.efi HD(1,GPT,53bf3e64-9298-4ca6-9856-7137c8bb9e1c,0x800,0x82000)/File(EFIdebianfbx64.efi) Boot0010 Setup FvFile(721c8b66-426c-4e86-8e99-3457c46ab0b9) Boot0011 Boot Menu FvFile(126a762d-5758-4fca-8531-201a7f57f850) Boot0012 Diagnostic Splash Screen FvFile(a7d8d9a6-6ab0-4aeb-ad9d-163e59a7a380) Boot0013 Lenovo Diagnostics FvFile(3f7e615b-0d45-4f80-88dc-26b234958560) Boot0014 Startup Interrupt Menu FvFile(f46ee6f4-4785-43a3-923d-7f786c3c8479) Boot0015 Rescue and Recovery FvFile(665d3f60-ad3e-4cad-8e26-db46eee9f1b5) Boot0016 MEBx Hot Key FvFile(ac6fd56a-3d41-4efd-a1b9-870293811a28) Boot0017* USB CD VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,86701296aa5a7848b66cd49dd3ba6a55) Boot0018* USB FDD VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,6ff015a28830b543a8b8641009461e49) Boot0019* NVMe0 VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,001c199932d94c4eae9aa0b6e98eb8a400) Boot001A* ATA HDD0 VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,91af625956449f41a7b91f4f892ab0f600) Boot001B* USB HDD VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,33e821aaaf33bc4789bd419f88c50803) Boot001C PCI LAN VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,78a84aaf2b2afc4ea79cf5cc8f3d3803) Boot001D* IDER BOOT CDROM PciRoot(0x0)/Pci(0x16,0x2)/Ata(0,1,0) Boot001E* IDER BOOT Floppy PciRoot(0x0)/Pci(0x16,0x2)/Ata(0,0,0) Boot001F* ATA HDD VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,91af625956449f41a7b91f4f892ab0f6) Boot0020* ATAPI CD VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,aea2090adfde214e8b3a5e471856a354) chroot /mnt/boot-sav/sda2 update-grub Generating grub configuration file ... using custom appearance settings Found linux image: /boot/vmlinuz-4.19.0-16-amd64 Found initrd image: /boot/initrd.img-4.19.0-16-amd64 Found linux image: /boot/vmlinuz-4.19.0-8-amd64 Found initrd image: /boot/initrd.img-4.19.0-8-amd64 grub-probe: error: cannot find a GRUB drive for /dev/sdb2. Check your device.map. Found unknown Linux distribution on /dev/sda3 Found Ubuntu 20.04.1 LTS (20.04) on /dev/sdb5 Adding boot menu entry for EFI firmware configuration Unhide GRUB boot menu in sda2/boot/grub/grub.cfg An error occurred during the repair. You can now reboot your computer. Please do not forget to make your UEFI firmware boot on the Debian GNU/Linux 10 (buster) entry (sda1/EFI/debian/shimx64.efi file) ! ============================ Boot Info After Repair ============================ => Grub2 (v2.00) is installed in the MBR of /dev/sda and looks at sector 34 of the same hard drive for core.img. core.img is at this location and looks for (,gpt2)/boot/grub. It also embeds following components: modules --------------------------------------------------------------------------- fshelp ext2 part_gpt biosdisk --------------------------------------------------------------------------- => Grub2 (v2.00) is installed in the MBR of /dev/sdb and looks at sector 1 of the same hard drive for core.img. core.img is at this location and looks for /boot/grub. It also embeds following components: modules --------------------------------------------------------------------------- fshelp ext2 part_gpt biosdisk search_fs_uuid --------------------------------------------------------------------------- config script --------------------------------------------------------------------------- search.fs_uuid f06b156c-05e5-43f9-90fe-7ac7e294e218 root hd0,gpt6 set prefix=($root)'/boot/grub' --------------------------------------------------------------------------- sda1: __________________________________________________________________________ File system: vfat Boot sector type: Unknown Boot sector info: No errors found in the Boot Parameter Block. Operating System: Boot files: /efi/Boot/bootx64.efi /efi/Boot/grubx64.efi /efi/debian/fbx64.efi /efi/debian/grubx64.efi /efi/debian/mmx64.efi /efi/debian/shimx64.efi /efi/debian/grub.cfg sda2: __________________________________________________________________________ File system: ext4 Boot sector type: - Boot sector info: Operating System: Debian GNU/Linux 10 (buster) Boot files: /boot/grub/grub.cfg /etc/fstab /etc/default/grub /boot/grub/i386-pc/core.img sda3: __________________________________________________________________________ File system: ext4 Boot sector type: - Boot sector info: Operating System: Boot files: sda4: __________________________________________________________________________ File system: swap Boot sector type: - Boot sector info: sda5: __________________________________________________________________________ File system: BIOS Boot partition Boot sector type: Grub2's core.img Boot sector info: sdb1: __________________________________________________________________________ File system: ntfs Boot sector type: Windows 8/2012: NTFS Boot sector info: No errors found in the Boot Parameter Block. Mounting failed: ntfs-3g-mount: mount failed: Device or resource busy ntfs-3g-mount: mount failed: Device or resource busy sdb2: __________________________________________________________________________ File system: iso9660 Boot sector type: Unknown Boot sector info: Operating System: Boot files: /boot/grub/grub.cfg sdb3: __________________________________________________________________________ File system: vfat Boot sector type: FAT32 Boot sector info: No errors found in the Boot Parameter Block. Operating System: Boot files: /efi/Boot/bkpbootx64.efi /efi/Boot/bootx64.efi /efi/Boot/fbx64.efi /efi/Boot/grubx64.efi /efi/Boot/mmx64.efi /efi/debian/fbx64.efi /efi/debian/grubx64.efi /efi/debian/mmx64.efi /efi/debian/shimx64.efi /efi/grub/fbx64.efi /efi/grub/grubx64.efi /efi/grub/mmx64.efi /efi/grub/shimx64.efi /efi/ubuntu/grubx64.efi /efi/ubuntu/mmx64.efi /efi/ubuntu/shimx64.efi /efi/debian/grub.cfg /efi/grub/grub.cfg /efi/ubuntu/grub.cfg sdb4: __________________________________________________________________________ File system: Extended Partition Boot sector type: - Boot sector info: sdb5: __________________________________________________________________________ File system: ext4 Boot sector type: - Boot sector info: Operating System: Ubuntu 20.04.1 LTS Boot files: /boot/grub/grub.cfg /etc/fstab /etc/default/grub ================================ 3 OS detected ================================= OS#1: Debian GNU/Linux 10 (buster) on sda2 OS#2: unknown Linux distribution on sda3 OS#3: Ubuntu 20.04.1 LTS on sdb5 ============================ Architecture/Host Info ============================ CPU architecture: 64-bit Live-session OS is Ubuntu 64-bit (Boot-Repair-Disk 64bit 20200604, bionic, x86_64) ===================================== UEFI ===================================== BIOS is EFI-compatible, and is setup in EFI-mode for this live-session. SecureBoot disabled. efibootmgr -v BootCurrent: 001B Timeout: 2 seconds BootOrder: 001B,0000,0001,0002,0005,0010,0011,0012,0013,0014,0015,0016,0006,0017,0018,0019,001A,001C,001D,001E,001F,0020 Boot0000* debian HD(1,GPT,53bf3e64-9298-4ca6-9856-7137c8bb9e1c,0x800,0x82000)/File(\EFI\debian\shimx64.efi) Boot0001* (Rescapp) shimx64.efi HD(1,GPT,53bf3e64-9298-4ca6-9856-7137c8bb9e1c,0x800,0x82000)/File(\EFI\debian\shimx64.efi) Boot0002* (Rescapp) grubx64.efi HD(1,GPT,53bf3e64-9298-4ca6-9856-7137c8bb9e1c,0x800,0x82000)/File(\EFI\debian\grubx64.efi) Boot0005* (Rescapp) mmx64.efi HD(1,GPT,53bf3e64-9298-4ca6-9856-7137c8bb9e1c,0x800,0x82000)/File(\EFI\debian\mmx64.efi) Boot0006* (Rescapp) fbx64.efi HD(1,GPT,53bf3e64-9298-4ca6-9856-7137c8bb9e1c,0x800,0x82000)/File(\EFI\debian\fbx64.efi) Boot0010 Setup FvFile(721c8b66-426c-4e86-8e99-3457c46ab0b9) Boot0011 Boot Menu FvFile(126a762d-5758-4fca-8531-201a7f57f850) Boot0012 Diagnostic Splash Screen FvFile(a7d8d9a6-6ab0-4aeb-ad9d-163e59a7a380) Boot0013 Lenovo Diagnostics FvFile(3f7e615b-0d45-4f80-88dc-26b234958560) Boot0014 Startup Interrupt Menu FvFile(f46ee6f4-4785-43a3-923d-7f786c3c8479) Boot0015 Rescue and Recovery FvFile(665d3f60-ad3e-4cad-8e26-db46eee9f1b5) Boot0016 MEBx Hot Key FvFile(ac6fd56a-3d41-4efd-a1b9-870293811a28) Boot0017* USB CD VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,86701296aa5a7848b66cd49dd3ba6a55) Boot0018* USB FDD VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,6ff015a28830b543a8b8641009461e49) Boot0019* NVMe0 VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,001c199932d94c4eae9aa0b6e98eb8a400) Boot001A* ATA HDD0 VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,91af625956449f41a7b91f4f892ab0f600) Boot001B* USB HDD VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,33e821aaaf33bc4789bd419f88c50803) Boot001C PCI LAN VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,78a84aaf2b2afc4ea79cf5cc8f3d3803) Boot001D* IDER BOOT CDROM PciRoot(0x0)/Pci(0x16,0x2)/Ata(0,1,0) Boot001E* IDER BOOT Floppy PciRoot(0x0)/Pci(0x16,0x2)/Ata(0,0,0) Boot001F* ATA HDD VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,91af625956449f41a7b91f4f892ab0f6) Boot0020* ATAPI CD VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,aea2090adfde214e8b3a5e471856a354) 8273287f52ffff4624121d2926ef9df4 sda1/Boot/bootx64.efi 2aec8d06a813f6b2fd1d6e9e774b470f sda1/Boot/grubx64.efi 1305dac4d07ae01b4b45438e18ff4c9b sda1/debian/fbx64.efi 2aec8d06a813f6b2fd1d6e9e774b470f sda1/debian/grubx64.efi 6a71919b8c1f3a6d277fa10b875010dc sda1/debian/mmx64.efi 8273287f52ffff4624121d2926ef9df4 sda1/debian/shimx64.efi ============================= Drive/Partition Info ============================= Disks info: ____________________________________________________________________ sda : is-GPT, hasBIOSboot, has---ESP, not-usb, not-mmc, has-os, 34 sectors * 512 bytes Partitions info (1/3): _________________________________________________________ sda1 : no-os, 32, nopakmgr, no-docgrub, nogrub, nogrubinstall, no-grubenv, noupdategrub, not-far sda2 : is-os, 64, apt-get, signed grub-pc grub-efi , grub2, grub-install, grubenv-ok, update-grub, farbios sda3 : is-os, 64, nopakmgr, no-docgrub, grub1, grub-install, no-grubenv, grub-mkconfig -o /boot/grub, farbios Partitions info (2/3): _________________________________________________________ sda1 : is---ESP, part-has-no-fstab, no-nt, no-winload, no-recov-nor-hid, no-bmgr, notwinboot sda2 : isnotESP, fstab-has-goodEFI, no-nt, no-winload, no-recov-nor-hid, no-bmgr, notwinboot sda3 : isnotESP, part-has-no-fstab, no-nt, no-winload, no-recov-nor-hid, no-bmgr, notwinboot Partitions info (3/3): _________________________________________________________ sda1 : not-sepboot, no-boot, part-has-no-fstab, not-sep-usr, no---usr, part-has-no-fstab, std-grub.d, sda sda2 : not-sepboot, with-boot, fstab-without-boot, not-sep-usr, with--usr, fstab-without-usr, std-grub.d, sda sda3 : not-sepboot, no-boot, part-has-no-fstab, not-sep-usr, with--usr, part-has-no-fstab, std-grub.d, sda fdisk -l (filtered): ___________________________________________________________ Disk sda: 238.5 GiB, 256060514304 bytes, 500118192 sectors Disk identifier: 53D5A9B7-8E4F-4D4A-A065-257892478C5D Start End Sectors Size Type sda1 2048 534527 532480 260M EFI System sda2 534528 426717183 426182656 203.2G Linux filesystem sda3 426717184 489631743 62914560 30G Linux filesystem sda4 489631744 500117487 10485744 5G Linux swap sda5 34 2047 2014 1007K BIOS boot Partition table entries are not in disk order. Disk sdb: 114.6 GiB, 123060879360 bytes, 240353280 sectors Disk identifier: 0x24be7684 Boot Start End Sectors Size Id Type sdb1 2048 154719055 154717008 73.8G 7 HPFS/NTFS/exFAT sdb2 239708160 240349183 641024 313M ef EFI (FAT-12/16/32) sdb3 * 154720256 155768831 1048576 512M ef EFI (FAT-12/16/32) sdb4 155770878 239708159 83937282 40G 5 Extended sdb5 155770880 239708159 83937280 40G 83 Linux Partition table entries are not in disk order. Disk dm-0: 880 MiB, 922746880 bytes, 1802240 sectors Disk identifier: 0x2c534026 Boot Start End Sectors Size Id Type dm-0p1 * 0 1802239 1802240 880M 0 Empty dm-0p2 964 5891 4928 2.4M ef EFI (FAT-12/16/32) Disk zram0: 1.5 GiB, 1553711104 bytes, 379324 sectors Disk zram1: 1.5 GiB, 1553711104 bytes, 379324 sectors Disk zram2: 1.5 GiB, 1553711104 bytes, 379324 sectors Disk zram3: 1.5 GiB, 1553711104 bytes, 379324 sectors parted -lm (filtered): _________________________________________________________ sda:256GB:scsi:512:512:gpt:ATA SanDisk SD8TN8U2:pmbr_boot; 5:17.4kB:1049kB:1031kB:::bios_grub; 1:1049kB:274MB:273MB:fat32::boot, esp; 2:274MB:218GB:218GB:ext4::; 3:218GB:251GB:32.2GB:ext4::; 4:251GB:256GB:5369MB:linux-swap(v1)::; sdb:123GB:scsi:512:512:msdos: USB SanDisk 3.2Gen1:; 1:1049kB:79.2GB:79.2GB:ntfs::; 3:79.2GB:79.8GB:537MB:fat32::boot, esp; 4:79.8GB:123GB:43.0GB:::; 5:79.8GB:123GB:43.0GB:ext4::; 2:123GB:123GB:328MB:fat16::esp; zram3:1554MB:unknown:4096:4096:loop:Unknown:; 1:0.00B:1554MB:1554MB:linux-swap(v1)::; zram1:1554MB:unknown:4096:4096:loop:Unknown:; 1:0.00B:1554MB:1554MB:linux-swap(v1)::; zram2:1554MB:unknown:4096:4096:loop:Unknown:; 1:0.00B:1554MB:1554MB:linux-swap(v1)::; zram0:1554MB:unknown:4096:4096:loop:Unknown:; 1:0.00B:1554MB:1554MB:linux-swap(v1)::; blkid (filtered): ______________________________________________________________ NAME FSTYPE UUID PARTUUID LABEL PARTLABEL sda ├─sda1 vfat DB89-E4D7 53bf3e64-9298-4ca6-9856-7137c8bb9e1c ├─sda2 ext4 f06b156c-05e5-43f9-90fe-7ac7e294e218 6c156bf0-e505-f943-90fe-7ac7e294e218 ├─sda3 ext4 55a47317-dfb0-404d-a833-47fa1ff6c4c5 1773a455-b0df-4d40-a833-47fa1ff6c4c5 ├─sda4 swap de3cfc4b-bf50-4fd0-83e4-95b21193e0b6 28118e2f-44a5-d94e-9544-56cb3eb5c80a └─sda5 72bc70eb-67fb-4932-bab5-cf70222d4cd1 sdb ├─sdb1 ntfs 9AFA9B98FA9B6EEF 24be7684-01 Ventoy ├─sdb2 iso9660 2020-06-13-00-42-55-00 Boot-Repair-Disk 64bit ├─sdb3 vfat FB72-0CC1 24be7684-03 ├─sdb4 24be7684-04 └─sdb5 ext4 f149e002-58e4-48b4-a23b-7bba31825f45 24be7684-05 zram0 zram1 zram2 zram3 df (filtered): _________________________________________________________________ Avail Use% Mounted on mapper/ventoy 0 100% /cdrom sda1 248.2M 3% /mnt/boot-sav/sda1 sda2 55.7G 68% /mnt/boot-sav/sda2 sda3 25.8G 7% /mnt/boot-sav/sda3 sdb2 0 100% /media/lubuntu/Boot-Repair-Disk 64bit sdb5 29.8G 19% /media/lubuntu/f149e002-58e4-48b4-a23b-7bba31825f45 Mount options: __________________________________________________________________ mapper/ventoy ro,noatime,nojoliet,check=s,map=n,blocksize=2048 sda1 rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro sda2 rw,relatime sda3 rw,relatime sdb2 ro,nosuid,nodev,relatime,nojoliet,check=s,map=n,blocksize=2048 sdb5 rw,nosuid,nodev,relatime ===================== sda1/efi/debian/grub.cfg (filtered) ====================== search.fs_uuid f06b156c-05e5-43f9-90fe-7ac7e294e218 root hd1,gpt2 hd0,gpt2 set prefix=($root)'/boot/grub' configfile $prefix/grub.cfg ====================== sda2/boot/grub/grub.cfg (filtered) ====================== Debian GNU/Linux f06b156c-05e5-43f9-90fe-7ac7e294e218 Debian GNU/Linux, with Linux 4.19.0-16-amd64 f06b156c-05e5-43f9-90fe-7ac7e294e218 Debian GNU/Linux, with Linux 4.19.0-8-amd64 f06b156c-05e5-43f9-90fe-7ac7e294e218 Ubuntu 20.04.1 LTS (20.04) (on sdb5) f149e002-58e4-48b4-a23b-7bba31825f45 Ubuntu (on sdb5) f149e002-58e4-48b4-a23b-7bba31825f45 Ubuntu, with Linux 5.8.0-50-generic (on sdb5) f149e002-58e4-48b4-a23b-7bba31825f45 Ubuntu, with Linux 5.4.0-42-generic (on sdb5) f149e002-58e4-48b4-a23b-7bba31825f45 ### END /etc/grub.d/30_os-prober ### System setup uefi-firmware ### END /etc/grub.d/30_uefi-firmware ### ========================== sda2/etc/fstab (filtered) =========================== # UUID=f06b156c-05e5-43f9-90fe-7ac7e294e218 / ext4 errors=remount-ro 0 1 UUID=f06b156c-05e5-43f9-90fe-7ac7e294e218 /mnt/lfs ext4 defaults 1 1 UUID=de3cfc4b-bf50-4fd0-83e4-95b21193e0b6 none swap sw 0 0 UUID=DB89-E4D7 /boot/efi vfat defaults 0 1 ======================= sda2/etc/default/grub (filtered) ======================= GRUB_DEFAULT="0" GRUB_TIMEOUT=10 GRUB_DISTRIBUTOR="`lsb_release -i -s 2> /dev/null || echo Debian`" GRUB_CMDLINE_LINUX_DEFAULT="quiet" GRUB_CMDLINE_LINUX="" GRUB_TERMINAL="console" export GRUB_MENU_PICTURE="/root/Images/the_legend_of_zelda-11.jpg" ==================== sda2: Location of files loaded by Grub ==================== GiB - GB File Fragment(s) 0.254890442 = 0.273686528 boot/grub/grub.cfg 1 20.503208160 = 22.015152128 boot/grub/i386-pc/core.img 1 94.556678772 = 101.529460736 boot/vmlinuz-4.19.0-16-amd64 2 120.646511078 = 129.543204864 boot/vmlinuz-4.19.0-8-amd64 1 120.646511078 = 129.543204864 vmlinuz 1 94.556678772 = 101.529460736 vmlinuz.old 2 92.017276764 = 98.802798592 boot/initrd.img-4.19.0-16-amd64 5 122.019794464 = 131.017756672 boot/initrd.img-4.19.0-8-amd64 3 122.019794464 = 131.017756672 initrd.img 3 92.017276764 = 98.802798592 initrd.img.old 5 ===================== sda2: ls -l /etc/grub.d/ (filtered) ====================== -rwxr-xr-x 1 root root 12444 Mar 1 22:50 10_linux -rwxr-xr-x 1 root root 11497 Mar 1 22:50 20_linux_xen -rwxr-xr-x 1 root root 12059 Mar 1 22:50 30_os-prober -rwxr-xr-x 1 root root 1418 Mar 1 22:50 30_uefi-firmware -rwxr-xr-x 1 root root 214 Mar 1 22:50 40_custom -rwxr-xr-x 1 root root 216 Mar 1 22:50 41_custom drwxr-xr-x 4 root root 4096 May 21 09:50 backup ===================== sda3: ls -l /etc/grub.d/ (filtered) ====================== -rwxr-xr-x 1 root root 10575 May 2 2020 10_linux -rwxr-xr-x 1 root root 12051 May 2 2020 20_linux_xen -rwxr-xr-x 1 root root 11301 May 2 2020 30_os-prober -rwxr-xr-x 1 root root 214 May 2 2020 40_custom -rwxr-xr-x 1 root root 216 May 2 2020 41_custom ====================== sdb2/boot/grub/grub.cfg (filtered) ====================== ==================== sdb2: Location of files loaded by Grub ==================== GiB - GB File Fragment(s) ?? = ?? boot/grub/grub.cfg 1 ===================== sdb3/efi/debian/grub.cfg (filtered) ====================== search.fs_uuid f06b156c-05e5-43f9-90fe-7ac7e294e218 root hd0,gpt2 hd0,gpt2 set prefix=($root)'/boot/grub' configfile $prefix/grub.cfg ====================== sdb3/efi/grub/grub.cfg (filtered) ======================= search.fs_uuid f06b156c-05e5-43f9-90fe-7ac7e294e218 root hd0,gpt2 set prefix=($root)'/boot/grub' configfile $prefix/grub.cfg ===================== sdb3/efi/ubuntu/grub.cfg (filtered) ====================== search.fs_uuid f149e002-58e4-48b4-a23b-7bba31825f45 root hd1,msdos5 set prefix=($root)'/boot/grub' configfile $prefix/grub.cfg ====================== sdb5/boot/grub/grub.cfg (filtered) ====================== Ubuntu f149e002-58e4-48b4-a23b-7bba31825f45 Ubuntu, with Linux 5.8.0-50-generic f149e002-58e4-48b4-a23b-7bba31825f45 Ubuntu, with Linux 5.4.0-42-generic f149e002-58e4-48b4-a23b-7bba31825f45 Debian GNU/Linux 10 (buster) (on sda2) f06b156c-05e5-43f9-90fe-7ac7e294e218 GNU/Linux (on sda2) f06b156c-05e5-43f9-90fe-7ac7e294e218 GNU/Linux, with Linux 4.19.0-16-amd64 (on sda2) f06b156c-05e5-43f9-90fe-7ac7e294e218 GNU/Linux, with Linux 4.19.0-8-amd64 (on sda2) f06b156c-05e5-43f9-90fe-7ac7e294e218 ### END /etc/grub.d/30_os-prober ### UEFI Firmware Settings uefi-firmware ### END /etc/grub.d/30_uefi-firmware ### ========================== sdb5/etc/fstab (filtered) =========================== # # / was on /dev/sda5 during installation UUID=f149e002-58e4-48b4-a23b-7bba31825f45 / ext4 errors=remount-ro 0 1 # /boot/efi was on /dev/nvme0n1p1 during installation /swapfile none swap sw 0 0 UUID=FB72-0CC1 /boot/efi vfat defaults 0 1 ======================= sdb5/etc/default/grub (filtered) ======================= GRUB_DEFAULT=0 GRUB_TIMEOUT_STYLE=hidden GRUB_TIMEOUT=10 GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian` GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" GRUB_CMDLINE_LINUX="" ==================== sdb5: Location of files loaded by Grub ==================== GiB - GB File Fragment(s) 98.403133392 = 105.659559936 boot/grub/grub.cfg 1 80.833332062 = 86.794129408 boot/vmlinuz 1 77.921016693 = 83.667054592 boot/vmlinuz-5.4.0-42-generic 2 80.833332062 = 86.794129408 boot/vmlinuz-5.8.0-50-generic 1 77.921016693 = 83.667054592 boot/vmlinuz.old 2 81.594074249 = 87.610970112 boot/initrd.img 3 81.550029755 = 87.563677696 boot/initrd.img-5.4.0-42-generic 3 81.594074249 = 87.610970112 boot/initrd.img-5.8.0-50-generic 3 81.550029755 = 87.563677696 boot/initrd.img.old 3 ===================== sdb5: ls -l /etc/grub.d/ (filtered) ====================== -rwxr-xr-x 1 root root 17622 Feb 24 19:33 10_linux -rwxr-xr-x 1 root root 42359 Feb 24 19:33 10_linux_zfs -rwxr-xr-x 1 root root 12894 Jul 31 2020 20_linux_xen -rwxr-xr-x 1 root root 12059 Jul 31 2020 30_os-prober -rwxr-xr-x 1 root root 1424 Jul 31 2020 30_uefi-firmware -rwxr-xr-x 1 root root 214 Jul 31 2020 40_custom -rwxr-xr-x 1 root root 216 Jul 31 2020 41_custom =============================== StdErr Messages ================================ sed: can't read /media/lubuntu/Boot-Repair-Disk: No such file or directory sed: can't read 64bit/boot/grub/grub.cfg: No such file or directory File descriptor 63 (pipe:[45365]) leaked on lvs invocation. Parent PID 1915: /bin/bash ``` ---
**Author:** ![Laurent001](https://www.debian-fr.org/letter_avatar_proxy/v4/letter/l/ce73a5/32.png) [@Laurent001](https://www.debian-fr.org/u/Laurent001)\ **Post date:** [Mai 22, 2021, 8:01 UTC](https://www.debian-fr.org/t/grub-impossible-a-lancer-boot-avec-menu-intel/84663/2 "2021-05-22T20:01:18Z")
C’est vraiment bizarre. Grâce à `sudo bootctl` je vois qu’aucun bootloader est actif mais j’en ai en magasin. ``` sudo bootctl System: Firmware: n/a (n/a) Secure Boot: disabled Setup Mode: user Boot into FW: supported Current Boot Loader: Product: n/a Features: ✗ Boot counting ✗ Menu timeout control ✗ One-shot menu timeout control ✗ Default entry control ✗ One-shot entry control ✗ Support for XBOOTLDR partition ✗ Support for passing random seed to OS ✗ Boot loader sets ESP partition information ESP: n/a File: └─n/a Random Seed: Passed to OS: no System Token: set Exists: yes Available Boot Loaders on ESP: ESP: /boot/efi (/dev/disk/by-partuuid/53bf3e64-9298-4ca6-9856-7137c8bb9e1c) File: └─/EFI/systemd/systemd-bootx64.efi (systemd-boot 247.3-5~bpo10+1) File: └─/EFI/BOOT/bootx64.efi (systemd-boot 247.3-5~bpo10+1) Boot Loaders Listed in EFI Variables: Title: ubuntu ID: 0x0002 Status: active, boot-order Partition: /dev/disk/by-partuuid/53bf3e64-9298-4ca6-9856-7137c8bb9e1c File: └─/EFI/ubuntu/shimx64.efi Title: Linux Boot Manager ID: 0x0001 Status: active, boot-order Partition: /dev/disk/by-partuuid/6c156bf0-e505-f943-90fe-7ac7e294e218 File: └─/EFI/systemd/systemd-bootx64.efi Title: Linux Boot Manager ID: 0x0000 Status: active, boot-order Partition: /dev/disk/by-partuuid/53bf3e64-9298-4ca6-9856-7137c8bb9e1c File: └─/EFI/systemd/systemd-bootx64.efi Boot Loader Entries: $BOOT: /boot/efi (/dev/disk/by-partuuid/53bf3e64-9298-4ca6-9856-7137c8bb9e1c) ``` ---
**Author:** ![Laurent001](https://www.debian-fr.org/letter_avatar_proxy/v4/letter/l/ce73a5/32.png) [@Laurent001](https://www.debian-fr.org/u/Laurent001)\ **Post date:** [Mai 23, 2021, 3:14 UTC](https://www.debian-fr.org/t/grub-impossible-a-lancer-boot-avec-menu-intel/84663/3 "2021-05-23T15:14:48Z")
Punaise j’en ai ch… mais j’ai trouvé. En faisant quelques commandes de cette [très belle page](https://www.rodsbooks.com/efi-bootloaders/installation.html) j’ai remarqué le flag **pmbr\_boot** que je n’avais jamais vu ailleurs via la commande **parted /dev/sda print** (disk flag:) Je l’ai enlevé avec [disk\_set](https://www.gnu.org/software/parted/manual/html_node/disk_005fset.html). ---
**Author:** ![PascalHambourg](https://www.debian-fr.org/user_avatar/www.debian-fr.org/pascalhambourg/32/5837_2.png) [@PascalHambourg](https://www.debian-fr.org/u/PascalHambourg)\ **Post date:** [Mai 23, 2021, 4:14 UTC](https://www.debian-fr.org/t/grub-impossible-a-lancer-boot-avec-menu-intel/84663/4 "2021-05-23T16:14:24Z")
On voyait que le flag pmbr\_boot (flag boot sur la partition de protection GPT du MBR) était activé dans le rapport posté plus haut. Il peut être nécessaire de l’activer avec certains ordinateurs pour pouvoir booter en mode BIOS/legacy sur un disque au format GPT. Par contre il peut empêcher le boot en mode EFI avec certains ordinateurs (parfois les mêmes) car c’est contraire au standard GPT (la partition de protection GPT ne doit pas avoir le flag boot activé). ---
**Author:** ![Laurent001](https://www.debian-fr.org/letter_avatar_proxy/v4/letter/l/ce73a5/32.png) [@Laurent001](https://www.debian-fr.org/u/Laurent001)\ **Post date:** [Mai 23, 2021, 4:29 UTC](https://www.debian-fr.org/t/grub-impossible-a-lancer-boot-avec-menu-intel/84663/5 "2021-05-23T16:29:53Z")
Oui et j’ai bien laissé ce flag sur cette partition. D’ailleurs gparted l’associe obligatoirement au flag esp. Mais là, c’est un flag sur le disque dur. Pas sur une partition. ---
**Author:** ![PascalHambourg](https://www.debian-fr.org/user_avatar/www.debian-fr.org/pascalhambourg/32/5837_2.png) [@PascalHambourg](https://www.debian-fr.org/u/PascalHambourg)\ **Post date:** [Mai 24, 2021, 7:13 UTC](https://www.debian-fr.org/t/grub-impossible-a-lancer-boot-avec-menu-intel/84663/6 "2021-05-24T07:13:49Z")
Je ne parle pas du « flag » esp/boot de la partition système EFI (qui est en fait la façon de parted de représenter le type GUID « EFI system partition ») mais du flag boot de la partition de protection GPT (type hexa EE) de la table de partition du MBR protecteur, qu’on peut visualiser avec ``` fdisk -l -t dos /dev/sda ``` Là encore, la façon de parted de représenter ce flag de partition comme un flag de disque est trompeuse. ---
**Author:** ![Laurent001](https://www.debian-fr.org/letter_avatar_proxy/v4/letter/l/ce73a5/32.png) [@Laurent001](https://www.debian-fr.org/u/Laurent001)\ **Post date:** [Mai 24, 2021, 3:50 UTC](https://www.debian-fr.org/t/grub-impossible-a-lancer-boot-avec-menu-intel/84663/7 "2021-05-24T15:50:31Z")
Merci pour ces précisions. Etant débutant, je me suis dit que c’était un flag sur disque. Je viens de comparer les différences avec fdisk et je trouve vraiment pas à évident sur fdisk aussi. On voit " \* " sur la colonne amorçage. Jamais je me serais dis qu’il aurait fallu virer ce flag de cette partition. Et je suis étonné que tous les outils utilisés pour fixer le boot efi n’est pas viré ce flag. J’en ai utilisé des tonnes. Certes, au final, ils faisaient un peu tous la même chose. Mais aucun n’a visiblement cherché à le virer avec parted et son `disk_set`. ---
**Author:** ![PascalHambourg](https://www.debian-fr.org/user_avatar/www.debian-fr.org/pascalhambourg/32/5837_2.png) [@PascalHambourg](https://www.debian-fr.org/u/PascalHambourg)\ **Post date:** [Mai 24, 2021, 4:15 UTC](https://www.debian-fr.org/t/grub-impossible-a-lancer-boot-avec-menu-intel/84663/8 "2021-05-24T16:15:28Z")
Encore heureux. J’active ce flag sur certaines machine car j’en ai besoin (BIOS buggé) et je n’apprécierais pas qu’un programme de partitionnement le désactive en douce sans que je lui demande. Par contre une chose est sûre : il ne s’est pas activé tout seul, c’est forcément toi qui l’a fait lors de tes tentatives, peut-être pour booter en mode BIOS/legacy. ---
**Author:** ![Laurent001](https://www.debian-fr.org/letter_avatar_proxy/v4/letter/l/ce73a5/32.png) [@Laurent001](https://www.debian-fr.org/u/Laurent001)\ **Post date:** [Mai 24, 2021, 7:49 UTC](https://www.debian-fr.org/t/grub-impossible-a-lancer-boot-avec-menu-intel/84663/9 "2021-05-24T19:49:47Z")
Je trouverai normal que les outils pour fixer les bios legacy remettent ce flag et ceux pour l’uefi le vire, non? Ou alors il y a un truc qui m’échappe… Pour la petite histoire: Après ma maj du kernel foireuse, je me rappelle que j’avais originalement un flag bios\_grub (vu sous gparted). J’avais aussi resetté le CMOS (pile retirée). J’avais tenté de repartir sur le bios legacy sans succès donc je me suis orienté vers l’uefi. ---
**Author:** ![PascalHambourg](https://www.debian-fr.org/user_avatar/www.debian-fr.org/pascalhambourg/32/5837_2.png) [@PascalHambourg](https://www.debian-fr.org/u/PascalHambourg)\ **Post date:** [Mai 25, 2021, 5:46 UTC](https://www.debian-fr.org/t/grub-impossible-a-lancer-boot-avec-menu-intel/84663/10 "2021-05-25T17:46:28Z")
> [@Laurent001](#): > > Je trouverai normal que les outils pour fixer les bios legacy remettent ce flag et ceux pour l’uefi le vire, non? De quels outils parles-tu exactement, et qu’entends-tu par « fixer les bios legacy » ? ---
**Author:** ![Laurent001](https://www.debian-fr.org/letter_avatar_proxy/v4/letter/l/ce73a5/32.png) [@Laurent001](https://www.debian-fr.org/u/Laurent001)\ **Post date:** [Mai 26, 2021, 1:03 UTC](https://www.debian-fr.org/t/grub-impossible-a-lancer-boot-avec-menu-intel/84663/11 "2021-05-26T13:03:36Z")
J’ai utilisé Gparted, rescatux, boot-repair et j’ai chrooté pour updater le grub et le réinstaller aussi. Par ex, dans rescatux je demande de fixer le boot pour l’UEFI et jamais ce flag n’a été enlevé. Dans Gparted, je ne vois pas ce flag. Seulement « boot » et « esp ». Et boot-repair aussi détectait bien que j’avais booté en UEFI + partition boot/esp et pourtant il n’a jamais enlevé ce flag. Bref, y’a un truc qui m’échappe. ---
**Author:** ![PascalHambourg](https://www.debian-fr.org/user_avatar/www.debian-fr.org/pascalhambourg/32/5837_2.png) [@PascalHambourg](https://www.debian-fr.org/u/PascalHambourg)\ **Post date:** [Mai 27, 2021, 6:28 UTC](https://www.debian-fr.org/t/grub-impossible-a-lancer-boot-avec-menu-intel/84663/12 "2021-05-27T18:28:49Z")
> [@Laurent001](#): > > Par ex, dans rescatux je demande de fixer le boot pour l’UEFI Ça ne me dit pas ce que signifie « fixer le boot pour l’UEFI » ni « fixer les bios legacy » . ---
**Author:** ![Laurent001](https://www.debian-fr.org/letter_avatar_proxy/v4/letter/l/ce73a5/32.png) [@Laurent001](https://www.debian-fr.org/u/Laurent001)\ **Post date:** [Mai 30, 2021, 8:10 UTC](https://www.debian-fr.org/t/grub-impossible-a-lancer-boot-avec-menu-intel/84663/13 "2021-05-30T20:10:08Z")
Je comprends pas trop la question/remarque. =\> fixer le boot pour l’UEFI/Legacy: permettre de booter en UEFI/Legacy si on a choisi cette option dans le bios.