View previous topic :: View next topic |
Author |
Message |
Spargeltarzan Guru
Joined: 23 Jul 2017 Posts: 317
|
Posted: Tue Aug 14, 2018 8:42 pm Post subject: [SOLVED] Default Boot Device Missing - No Operating System |
|
|
Dear Community,
I installed Qubes OS for testing beside my Gentoo on an own partition on my notebook and crashed my booting completely. UEFI doesn't find any booting option beside an plugged USB Stick. To install Qubes OS I switched to legacy mode for its install-routine and switched back to EFI mode afterwards.
Default Boot Device Missing - for UEFI and Legacy mode "No OS found".
I have configured back to EFI, bootet the Gentoo rescue stick, mounted Gentooroot, boot- & efi-partition, changed root, re-mounted EFI variables, re-installed grub to /dev/sda and created the grub-config with success. After a reboot the issue "Default Boot Device Missing" persists. (Grub-mkconfig shows Gentoo, Qubes, but not Windows)
Additionally I checked efibootmgr -v and Gentoo wasn't shown. With efibootmgr -c Gentoo appears, but this setting is not persistent accross a new boot try. It's lost again and still no boot option found. I have secureboot, fastboot, Intel Trusted Platform disabled.
I tried to install my Grub around 20 times, I re-formated my /boot/efi partition and installed Grub again, without success. Flags boot, esp are set.
My Partition layout (fedoraroot is now Qubes root), lvm its home partition.
Code: |
Number Start End Size File system Name Flags
1 1049kB 274MB 273MB fat32 EFI System Partition boot, esp
2 274MB 290MB 16.8MB Microsoft reserved partition msftres
3 290MB 69.0GB 68.7GB ntfs Basic data partition msftdata
8 69.0GB 142GB 73.4GB ext4 gentooroot
11 142GB 143GB 537MB ext4 boot
9 143GB 194GB 51.3GB fedoraroot
12 194GB 203GB 8858MB linux-swap(v1) swap
13 203GB 214GB 10.5GB lvm
10 214GB 466GB 252GB ext4 fedorahome
4 466GB 493GB 26.8GB ntfs Basic data partition msftdata
5 493GB 494GB 1049MB ntfs Basic data partition hidden, diag
6 494GB 511GB 17.5GB ntfs Basic data partition diag
7 511GB 512GB 1049MB fat32 hidden
|
I tried also to install Grub in legacy mode with boot partition bios_grub flag, without success.
Something seems to be broken deeply.
Help is very much appreciated, I tried to fix my boot issue together with a Gentoo friend and we both run out of ideas. _________________ ___________________
Regards
Spargeltarzan
Notebook: Lenovo YOGA 900-13ISK: Gentoo stable amd64, GNOME systemd, KVM/QEMU
Desktop-PC: Intel Core i7-4770K, 8GB Ram, AMD Radeon R9 280X, ZFS Storage, GNOME openrc, Dantrell, Xen
Last edited by Spargeltarzan on Wed Aug 15, 2018 6:23 pm; edited 1 time in total |
|
Back to top |
|
|
Keruskerfuerst Advocate
Joined: 01 Feb 2006 Posts: 2289 Location: near Augsburg, Germany
|
Posted: Wed Aug 15, 2018 6:43 am Post subject: |
|
|
Please post grub.cfg! |
|
Back to top |
|
|
Spargeltarzan Guru
Joined: 23 Jul 2017 Posts: 317
|
Posted: Wed Aug 15, 2018 7:36 am Post subject: |
|
|
Thanks for fast reply! https://paste.pound-python.org/show/Jt8brq5i85ZKCKaGGcJf/
I realize in grub.cfg for Gentoo "set root='hd0,gpt11'", but my root partition is /dev/sda8. But I do not get to Grub... _________________ ___________________
Regards
Spargeltarzan
Notebook: Lenovo YOGA 900-13ISK: Gentoo stable amd64, GNOME systemd, KVM/QEMU
Desktop-PC: Intel Core i7-4770K, 8GB Ram, AMD Radeon R9 280X, ZFS Storage, GNOME openrc, Dantrell, Xen |
|
Back to top |
|
|
oreo n00b
Joined: 14 Aug 2018 Posts: 31
|
Posted: Wed Aug 15, 2018 8:09 am Post subject: |
|
|
So just to make sure, your bios is not detecting your internal hard drive as a boot device?
If this is the case, you may try installing grub with --removable flag. Some bioses only support (auto-detect) the /efi/boot/ location for grub. For my first install, I had to manually tell my bios where grubx64.efi was. If your bios supports the creation of boot options, try adding one with the exact location of grubx64.efi. (With your esp partition as root.) Next install, I used the --removable flag and my bios detected it no problem.
Hope this helps! _________________ "One does not simply, install gentoo." |
|
Back to top |
|
|
Keruskerfuerst Advocate
Joined: 01 Feb 2006 Posts: 2289 Location: near Augsburg, Germany
|
Posted: Wed Aug 15, 2018 8:56 am Post subject: |
|
|
Then check the UEFI Bios settings for booting. (in the Bios) |
|
Back to top |
|
|
Spargeltarzan Guru
Joined: 23 Jul 2017 Posts: 317
|
Posted: Wed Aug 15, 2018 10:09 am Post subject: |
|
|
oreo wrote: | So just to make sure, your bios is not detecting your internal hard drive as a boot device? |
My Lenovo Bios shows in the tab "Information" the Liteon Hard Disk. In the Bios/UEFI Boot Options no hard disk is shown
oreo wrote: |
If this is the case, you may try installing grub with --removable flag. |
I tried the grub-install in the chroot with --removable flag, still the same error message appears when I turn on my notebook. My boot partition was mounted in /boot and my efi partition in /boot/efi. I didn't specify any target or efi directory, the grub-install finishes fine with its autodetection.
"Default Boot Device Missing or Boot Failed.
Insert Recover Media and Hit any key
Then Select "Boot Manager" to choose a new Boot Device or to Boot Recovery Media"
oreo wrote: |
Some bioses only support (auto-detect) the /efi/boot/ location for grub. For my first install, I had to manually tell my bios where grubx64.efi was.
|
Should I try any directory or target in the grub-install for another location?
I have no option to specify a *.efi location in the bios. Previously I never installed grub with --removable flag before or any other options and my computer justed worked.
Keruskerfuerst wrote: |
Then check the UEFI Bios settings for booting. (in the Bios)
|
-) Secure Boot is off
-) I didn't touch the "Reset to Setup Mode" option regarding Secure Boot
-) Intel Trusted Platform off
-) Mode UEFI
-) "OS Optimized Default" I tried with enabled and disabled
-) Tried also "Mode Legacy".
PS: My Windows partition is also not found, neither by bios nor by grub-mkconfig in the chroot.
-- No idea -- _________________ ___________________
Regards
Spargeltarzan
Notebook: Lenovo YOGA 900-13ISK: Gentoo stable amd64, GNOME systemd, KVM/QEMU
Desktop-PC: Intel Core i7-4770K, 8GB Ram, AMD Radeon R9 280X, ZFS Storage, GNOME openrc, Dantrell, Xen |
|
Back to top |
|
|
P.Kosunen Guru
Joined: 21 Nov 2005 Posts: 309 Location: Finland
|
Posted: Wed Aug 15, 2018 10:17 am Post subject: |
|
|
What does "efibootmgr -v" say?
You might need to fix Windows boot first and then install grub. You can install and config Grub from any installed linux, but use only that one for updating config, from others you can uninstall grub completely. |
|
Back to top |
|
|
Spargeltarzan Guru
Joined: 23 Jul 2017 Posts: 317
|
Posted: Wed Aug 15, 2018 10:24 am Post subject: |
|
|
Code: |
sysresccd /boot/efi/EFI # efibootmgr -v
BootCurrent: 0000
Timeout: 0 seconds
BootOrder: 0002,0001,2001,2002,2003
Boot0000* EFI USB Device (SanDisk) PciRoot(0x0)/Pci(0x14,0x0)/USB(13,0)/HD(1,MBR,0x0,0x20,0x1cf7fe0)RC
Boot0001* Linux HD(1,GPT,cc078c9c-1d55-4a72-b1c3-1d4ff3245504,0x800,0x82000)/File(\EFI\Gentoo\grub.efi)
Boot0002* gentoo HD(1,GPT,cc078c9c-1d55-4a72-b1c3-1d4ff3245504,0x800,0x82000)/File(\EFI\gentoo\grubx64.efi)
Boot2001* EFI USB Device RC
Boot2002* EFI DVD/CDROM RC
Boot2003* EFI Network RC
|
This is the output directly after I installed grub in the chroot. After a boot try without success and I boot my rescue-stick again, the efibootmgr -v forgets the "Linux" and "gentoo" entry again. _________________ ___________________
Regards
Spargeltarzan
Notebook: Lenovo YOGA 900-13ISK: Gentoo stable amd64, GNOME systemd, KVM/QEMU
Desktop-PC: Intel Core i7-4770K, 8GB Ram, AMD Radeon R9 280X, ZFS Storage, GNOME openrc, Dantrell, Xen |
|
Back to top |
|
|
Spargeltarzan Guru
Joined: 23 Jul 2017 Posts: 317
|
Posted: Wed Aug 15, 2018 10:31 am Post subject: |
|
|
How could I fix my Windows boot with help of my SystemRescueCD if efibootmgr -c doesn't work? _________________ ___________________
Regards
Spargeltarzan
Notebook: Lenovo YOGA 900-13ISK: Gentoo stable amd64, GNOME systemd, KVM/QEMU
Desktop-PC: Intel Core i7-4770K, 8GB Ram, AMD Radeon R9 280X, ZFS Storage, GNOME openrc, Dantrell, Xen |
|
Back to top |
|
|
Spargeltarzan Guru
Joined: 23 Jul 2017 Posts: 317
|
Posted: Wed Aug 15, 2018 11:04 am Post subject: |
|
|
Code: |
sysresccd / # tree -L 3 /boot/efi/
/boot/efi/
└── EFI
├── BOOT
│ └── BOOTX64.EFI
├── bootx64.efi
└── gentoo
└── grubx64.efi
|
_________________ ___________________
Regards
Spargeltarzan
Notebook: Lenovo YOGA 900-13ISK: Gentoo stable amd64, GNOME systemd, KVM/QEMU
Desktop-PC: Intel Core i7-4770K, 8GB Ram, AMD Radeon R9 280X, ZFS Storage, GNOME openrc, Dantrell, Xen |
|
Back to top |
|
|
P.Kosunen Guru
Joined: 21 Nov 2005 Posts: 309 Location: Finland
|
|
Back to top |
|
|
Keruskerfuerst Advocate
Joined: 01 Feb 2006 Posts: 2289 Location: near Augsburg, Germany
|
Posted: Wed Aug 15, 2018 11:11 am Post subject: |
|
|
I would check the boot order in the UEFI Bios first. |
|
Back to top |
|
|
P.Kosunen Guru
Joined: 21 Nov 2005 Posts: 309 Location: Finland
|
Posted: Wed Aug 15, 2018 11:14 am Post subject: |
|
|
Keruskerfuerst wrote: | I would check the boot order in the UEFI Bios first. |
"EFI/Microsoft/Boot" is missing, those are needed for Windows to boot and fixing it will destroy Grub.
If Windows entry /boot/bootx64.efi is working, you could try to copy grubx64.efi over it and then chainload Windows from Grub.
https://wiki.gentoo.org/wiki/GRUB2/Chainloading#Dual-booting_Windows_on_UEFI_with_GPT |
|
Back to top |
|
|
Keruskerfuerst Advocate
Joined: 01 Feb 2006 Posts: 2289 Location: near Augsburg, Germany
|
Posted: Wed Aug 15, 2018 12:12 pm Post subject: |
|
|
It is possible to repair the Windows Bootloader from the repair console of Windows media. |
|
Back to top |
|
|
Spargeltarzan Guru
Joined: 23 Jul 2017 Posts: 317
|
Posted: Wed Aug 15, 2018 2:45 pm Post subject: |
|
|
P.Kosunen wrote: |
Try automatic repair first from Windows install media.
Does Windows entry survive reboots and what efibootmgr shows? |
-) Efibootmgr never showed Windows. Not directly after creating grub.cfg, nor after a failed boot when it forgets the gentoo entry.
-) When pressing the Novo button of my Lenovo Yoga and go to "System Recovery", the same "Default Boot Device Missing" error appears.
-) Tried to identify the Windows partition with os-prober. Therefore I mounted the Windows partition, cleaned the hibernation file, performed a fsck, but os-prober doesn't find Windows wether the partition is mounted or not.
-) I did with "dd" a Windows-8.1.iso to another USB-stick, but this stick is not identified by UEFI/Bios and it can't boot. But I can normally mount the Windows stick on my rescue-linux-stick.
Any other idea how to get a recovery media?
Keruskerfuerst wrote: |
I would check the boot order in the UEFI Bios first.
|
I do not have any boot devices in my UEFI/Bios beside my plugged linux-rescue-stick.
P.Kosunen wrote: |
"EFI/Microsoft/Boot" is missing, those are needed for Windows to boot and fixing it will destroy Grub.
|
My mounted Win-8.1 stick has got an:
Code: |
root@sysresccd /mnt/windows/efi/boot % ls
bootx64.efi
|
bootx64.efi file. I try to copy it to EFI partition and chainload it as described in the wiki.
Code: |
sysresccd /boot/efi/EFI/microsoft # tree -L 4 /boot/efi/
/boot/efi/
└── EFI
├── BOOT
│ └── BOOTX64.EFI
├── bootx64.efi
├── gentoo
│ └── grubx64.efi
└── microsoft
├── Boot
│ └── bootx64.efi
└── bootx64.efi
|
I copied the bootx64.efi from the Win-8.1 stick to EF/microsoft/Boot and created the chainload in 40_custom:
Code: |
menuentry "Windows 7 UEFI/GPT" {
insmod part_gpt
insmod search_fs_uuid
insmod chain
search --fs-uuid --no-floppy --set=root 96CECAC7CECA9EBD
chainloader ($root)/EFI/microsoft/boot/bootx64.efi
}
|
with --set=root the UUID of the Win partition and the previously copied .efi from the stick (/EFI/microsoft/boot/bootx64.efi)
--- No success _________________ ___________________
Regards
Spargeltarzan
Notebook: Lenovo YOGA 900-13ISK: Gentoo stable amd64, GNOME systemd, KVM/QEMU
Desktop-PC: Intel Core i7-4770K, 8GB Ram, AMD Radeon R9 280X, ZFS Storage, GNOME openrc, Dantrell, Xen |
|
Back to top |
|
|
Tony0945 Watchman
Joined: 25 Jul 2006 Posts: 5127 Location: Illinois, USA
|
Posted: Wed Aug 15, 2018 3:41 pm Post subject: |
|
|
Spargeltarzan wrote: | I do not have any boot devices in my UEFI/Bios beside my plugged linux-rescue-stick. |
If your BIOS doesn't see the device you have no hope of booting. It's not (necessarily) that Linux or grub that can't read your hard drive, your hardware doesn't recognize that a hard drive exists! I don't know how your usb stick can see the drive but your BIOS can't. Or possibly it's a case where your BIOS doesn't see a bootable drive.
They all have different formats so explore your BIOS menu and give a small sigh of relief if somewhere it acknowledges that a drive exists. Then the problem is that the drive isn't recognized as bootable. That might be a partitioning issue. |
|
Back to top |
|
|
Spargeltarzan Guru
Joined: 23 Jul 2017 Posts: 317
|
Posted: Wed Aug 15, 2018 5:46 pm Post subject: |
|
|
Tony0945 wrote: |
If your BIOS doesn't see the device you have no hope of booting. It's not (necessarily) that Linux or grub that can't read your hard drive, your hardware doesn't recognize that a hard drive exists! I don't know how your usb stick can see the drive but your BIOS can't. Or possibly it's a case where your BIOS doesn't see a bootable drive. |
My BIOS sees a LITEON hard drive in the very first register "Information". It is a read only field where no action can be taken. If I force my computer to list bootable devices by pressing F12 after turning on, the list is empty. Previously I can remember that OS are listed; I am very unsure if a hard driver was ever listed in here. It even showed Systems I uninstalled already, but EFI still had informations about it. (my former Ubuntu install...)
When exploring the register "Boot" in BIOS, it shows the above mentioned settings like Boot Mode UEFI or Legacy, OS, .... But I will twisted & dance with my BIOS again to find something.
Tony0945 wrote: |
Then the problem is that the drive isn't recognized as bootable. That might be a partitioning issue.
|
I fully deleted the /dev/sda1 EFI partition and re-created it with formatted fat32 and boot,esp flat. Then I rsynced my EFI files back. Gdisk shows correct EF00 code. After re-creation of the partition I of course installed grub again.
What could I do more to check my partitioning?
Code: |
root@sysresccd /root % gdisk -l /dev/sda
GPT fdisk (gdisk) version 1.0.1
Partition table scan:
MBR: protective
BSD: not present
APM: not present
GPT: present
Found valid GPT with protective MBR; using GPT.
Disk /dev/sda: 1000215216 sectors, 476.9 GiB
Logical sector size: 512 bytes
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 1000215182
Partitions will be aligned on 2048-sector boundaries
Total free space is 2669 sectors (1.3 MiB)
Number Start (sector) End (sector) Size Code Name
1 2048 534527 260.0 MiB EF00 EFI System Partition
2 534528 567295 16.0 MiB 0C01 Microsoft reserved ...
3 567296 134754303 64.0 GiB 0700 Basic data partition
4 909520896 961949695 25.0 GiB 0700 Basic data partition
5 961949696 963997695 1000.0 MiB 2700 Basic data partition
6 963997696 998166527 16.3 GiB 2700 Basic data partition
7 998166528 1000214527 1000.0 MiB ED01 Basic data partition
8 134754304 278114303 68.4 GiB 8300 gentooroot
9 279162880 379416575 47.8 GiB 8300 fedoraroot
10 417230848 909520895 234.7 GiB 8300 fedorahome
11 278114304 279162879 512.0 MiB 8300 boot
12 379416576 396718079 8.3 GiB 8200 swap
13 396718080 417230847 9.8 GiB 8E00
|
Gdisk shows "Found valid GPT with protective MBR; using GPT."
DONE!! gdisk -v showed a warning for the MBR and that some UEFIs might not find a boot option and writing a new MBR with gdisk fixed the issue. Afterwards -v showed "No Problems"!!!
https://unix.stackexchange.com/questions/323677/qubes-clobbered-my-boot-how-can-i-re-enable-efi-booting _________________ ___________________
Regards
Spargeltarzan
Notebook: Lenovo YOGA 900-13ISK: Gentoo stable amd64, GNOME systemd, KVM/QEMU
Desktop-PC: Intel Core i7-4770K, 8GB Ram, AMD Radeon R9 280X, ZFS Storage, GNOME openrc, Dantrell, Xen |
|
Back to top |
|
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|