Reboot And Select Proper Boot Device Linux

[Lacy Tortelli]

ThisUbuntu boot-repair tool can repair frequent boot issues you may encounter in Ubuntu like when you can't boot Ubuntu after installing Ubuntu. Or you can't boot Windows after installing a Linux distribution, or when you can't boot Ubuntu after installing Windows, or when GRUB is not displayed anymore, or some software update or hardware upgrade breaks GRUB, etc.

Four options. Either boot into the LiveCD and download the program and apply it to your boot loader, or create a Ubuntu OS install boot disk with boot-repair, or boot into a barebones boot-repair liveCD, or a boot repair USB stick.

So either pitch in and help the developers figure out why that version of Ubuntu isn't working with your hardware, or troubleshoot what is wrong by learning about how the boot process works, or try a different version of Ubuntu on a different hardware.

I had this issue today. For me the fix was to hit a different function key than the normal bios menu. This made a menu pop up that allowed me to select a device to boot from (this is also in BIOS, but this menu was a different thing that only allowed you to do that one thing). Then I selected the device "uefi: Ubuntu." This device was already selected as the first boot priority in my BIOS, but for some reason it didn't work until I used this second menu. I had used this menu before to boot from USB to install Ubuntu, so I'm thinking maybe this menu overrides what's in BIOS and it's persistent? I have no idea, but problem solved.

Hello everyone, I'm facing an issue after updating the BIOS. I have two SSDs: one with Windows 11 (the system from which I'm currently writing) and another with Arch Linux. The primary boot option has always been set to Windows. When I needed to use Arch, I would manually select the SSD with Arch during boot, and systemd-boot would load the operating system. However, after the BIOS update, attempting to boot from the SSD with Arch results in the BIOS displaying "Reboot and select proper boot device."

Additional details: There is a third SSD in the PC, which used to have Linux Mint installed with a partition containing Grub. Although I have wiped this SSD partition, now, if I try to select any SSD (except for the one with Windows 11), Grub starts in rescue mode. I attempted to reinstall Grub using the Arch Linux installation USB key and chroot, but I was unsuccessful. I apologize if the story is a bit confusing.

When I attempt to boot the newly built computer from a USB flash drive in order to install windows 10, I get the error "Reboot and select proper boot device." I think that somehow my settings in the UEFI are not correct so that it is not attempting to boot from the USB flash drive as I'd like.

It doesn't make sense to dd a Windows ISO to a USB drive. It's simply not supposed to be bootable this way. For the PC to boot a USB drive, the drive needs to have either a MBR with proper boot code for hard disks, but not ISO9660/UDF, for BIOS/CSM, or a proper FAT-formatted ESP for UEFI.

The simplest way to make a bootable Windows installation USB for UEFI, is to format the drive with FAT32, and then mount the ISO and copy the content to it. UEFI simply looks for EFI binaries on proper location.

However, since the offical ISO from Microsoft have been consisting of file (well the "core" file, namely install.wim) that exceeds the 4G file limit of FAT32, meaning that you'll need to use NTFS or exFAT instead.

But then by standard UEFI firmwares are only required to support the FAT-family filesystems (not including exFAT), therefore solutions like Rufus ships an NTFS/exFAT UEFI driver and a program that loads it before executing the boot file on the "main" NTFS/exFAT partition. (Binary build of the driver is also available separately, which can be loaded with EDK2 shell instead.) Another alternative would be to have a FAT(32) ESP with grub, which can chainload the boot file on the main partition as well.

For the record, the Media Creation Tool from Microsoft seems to work around the problem by using the more compressed ESD format instead of WIM for the install image, which is why it allows you to continue using FAT32 only. (I have no idea whether Microsoft has trim down some content of the image or it really purely relies on compression though.)

While I have figured out how to do this on a one-time basis, the issue happened again. So the question remains - why, whenever I unplug the SSD from the SATA port on the AAEON EMB-BT1 itx board, does it then refuse to boot and give this error?My operating system is Debian Linux and I cannot be reinstalling grub-efi every time I swap SSDs.

Apparently your system firmware will automatically delete any UEFI NVRAM boot entries that refer to disks that are no longer accessible. That helps avoid the possibility of the UEFI NVRAM becoming full, but can be a pain if you swap boot disks often. Unfortunately there is probably nothing you can do to change this firmware behavior.

This will result a second copy of the bootloader at /boot/efi/EFI/BOOT/BOOTx64.efi, which is the path the firmware looks for when booting on removable media (on the x64 hardware architecture), or when the applicable UEFI NVRAM boot entry for the installed OS has been lost.

If you do this to all your system SSDs, it should minimize the effort involved in swapping SSDs. Windows 10 and 11 will automatically set up a copy of their UEFI bootmanager to this path by default, so if one of your boot SSDs contains Windows, you should not need to do anything special for it.

The fact that your EFI System Partition starts at block #2048 is normal - unlike the old MBR partition table that was just 64 bytes in size, the GPT partition table will occupy at least 33 512-byte sectors, and the modern standard is to set up partition limits at exact multiples of 1 MiB for data alignment reasons - this avoids performance degradation on SSDs and some SANs that internally use much larger disk blocks.

Additionally, SATA only partially supports hot unplugging devices.If the device is in a hot swap slot with physical rails, it likely is safe. But if it just has a cable connected to it without any guides, then every time you unplug or plug in the drive while power is on, there is a chance of damaging the drive electronics.

Additionally, if you plug a drive in after BIOS has initialized, it may not detect the drive as bootable and will not have it in its boot list; rebooting or power cycling may fix this. Also, if you are using EFI mode, when the bootloader is installed, an entry is added to the bios EFI boot list, and if the drive is not online when bios inititalizes, it may delete boot entries associated with the drive.

Some of them work at the first shot, some (the most important, of course) display "Boot failure. Reboot and Select proper Boot device or Insert Boot Media in selected Boot device" message. The VM settings are identical as in working units. All VHDs show the same results of inspection (from Hyper-V Manager).

I'd had a new computer and a laptop since my old laptop is running slow im trying to install linuxmint on it (not sponsored or anything) but it require some kind of efi partitions to run on it, im pretty sure that im selecting legacy not UEFI so im thinking that it just some kind of Peripheral that needed for it tu run, then i created the EFI partitions expecting it to be running normally instead after install it showed "reboot and select boot device" screen

i've guess this is because im dualbooting W7 that maybe on legacy mode with linuxmint that maybe installed on UEFI thinking the laptop can handled it, now the bios also dont showed the boot only on UEFI options so im thinking, can zorin os legacy mode overide the linuxmint installations and posibbly fix the problem?

When you install Linux Mint You should have the Option to install Linux beneath Windows because the Installer should detect Windows. When you choose that it makes the Stuff automatically. It is on Zorin, too.

Hi everyone, i joined this forum because i found a lot of interesting information here regarding Windows installations and unattended setups. I've been in I.T. for 15 years installing windows since 3.

When You install Zorin You should get the Option to install Zorin beneath Windows, too I would think. Because You are on Windows 7 ... I don't know that but on Windows 10 the Installer detect the System and give that Option.

I don't use Virtual Machines to test Linux Distros. I use every Time Dual Boot to have it on the Machine so I can see how it runs. I can tell you my Steps how I delete a Linux Partition from my Dual Boot System. I could make a little pictured Guide for You if you want that.

can you do that for me? after i check these are partition that i had, this picture is taken from linux mint livecd, i can't boot to windows because reboot and select proper dev screen. i can't even filter the bios to boot on UEFI only because somehow theres no options for it?

Screenshot827563 77.5 KB

Linuxmint is installed on the extended partitions except sda5, im very sure that this is installed on legacy mode because i select "KingstonDataTravel" not "UEFI: KingstonDataTravel" but it still ask for EFI partitions.

(sda6 the EFI, sda7 swap, sda 8 root, sda 9 home)

So, You can't even start into Windows from the BIOS? Because my Description is for Windows. Theoretically You should go into BIOS and look there for something like a ''Boot''-Menu and there You should adjust the Start. Completely turn off Your PC, then push the Power-Button and directly after that permanently push the Button to come to BIOS. then You should arrive it.

So, can You first try if You can get boot into Windows? Because from Windows I can describe it. Form Your GParted Picture I would say You could theoretically delete sda7, 8 and 9. But when You do that You could have Problems with starting Your PC because You could get an Error-Message. And then You must go into BIOS too to start from there into Windows.

While I'm waiting your response, I'm trying to override the broken installations with zorin os 17 and found something weird. I'm 100% sure that I'm booting my stick on Legacy Mode, I deleted a EFI partitioning mistake that turns out Legacy and UEFI don't like together and it saying no EFI was found on Legacy mode?

3a8082e126