I had this going pretty well before a power outage a few weeks ago. I don’t think it was a lightening strike. It could have been a power surge, I just don’t know.
On my Dell Wyse, I am able to get into Bios without issue. When I try to change the boot sequence, the M.2 Sata does not show as an option. I have used Etcher to load up the drive. Etch goes through the installation and then runs it’s check to make sure all is well. I can see the M.2 drive under Disk Management on my Windows PC. But, the Wyse just doesn’t seem to see it. When the Wyse starts up, it stops at “No bootable devices found”. I get options F1, F2 and F5. I have run the diagnostics and it passes.
I am not sure what the issue is with the way I post, @stevemann. Everything in my first post was written as complete sentences. The title of my post is clear and concise.
On the first screen you posted it gave the option to add a boot option, the one you have now looks as if it points to the windows boot manager that you have presumably over written? You could try adding another boot option with the filename as
\EFI\BOOT\bootx64.efi
Presumably the file system list option stays the same or it gives you the option of selecting from your disc once you add a new. If it works you could deselect the Windows Boot Manager as a boot option, or delete it altogether. Personally I’d hit the ‘Add Boot Option’ button see what it offers and post back here if unsure.
Thanks, @EBME2. When I click Add Boot Option, I get “File System Not Found!” as a response. I selected Delete Boot Option, but cannot Add a Boot Option. So, now I only have Merlin Non-Pxe. When I click View, nothing happens.
But it does say below, have you tried the F12 key?
Boot Sequence
Boot Sequence allows you to bypass the System Setup–defined boot device order and boot directly to a specific device. During the Power-on Self Test (POST), when the Dell logo appears you can:
Access System Setup by pressing the F2 key
Bring up the one-time boot menu by pressing the F12 key
It might be worth re-writing your HAOS image with Etcher after doing a complete wipe of the disc.
Question did you have it running on the Dell Wyse before or are you now moving it to this? Seems strange to have changed unless BIOS has set itself back to default.
You should avoid putting important details only in the title. When scrolling through the thread, some devices will scroll the title off the page.
So, finally the pieces come together. You had Home Assistant running on this computer using this M.2, then it failed with an error: “No bootable devices…”. Do I have that correct so far?
Steps I would take if this were my computer.
Boot Ubuntu (only because it’s easy) from a thumbdrive.
If it boots from a thumbdrive then your BIOS is probably OK.
Flash Ubuntu to the M.2 and boot it.
If you get the “No bootable devices…” error, then I would suspect the SSD. In this case, use a partition editor to delete all partitions. Partition the whole volume as a New Simple Volume and format it to NTFS. Flash a fresh copy of HAOS (your copy may have an error) and try booting again.
If the computer still does not see a bootable device, then the easy fix is to use another M.2 SSD.
You could attempt to fix the bad boot sector. The following is from my notebook- I HAVE NOT NEEDED THIS, so I can’t vouch for its accuracy.
No bootable devices…
After flashing a boot disk from an image, a drive might not be recognized as bootable if the new boot sector is not correctly written due to a hardware issue.
Fix the MBR of a boot device
Create a Bootable USB
Download the Windows Installation Media Creation Tool from the Microsoft website. Download Windows 10
Follow the instructions to create a bootable USB drive.
Boot from the USB
Insert the bootable USB into your computer and restart it.
Enter the BIOS/UEFI settings and change the boot order to boot from the USB drive.
Save and exit BIOS/UEFI settings.
Repair the Boot Sector
When the Windows setup screen appears, select your language and click Next.
Click on Repair your computer.
Choose Troubleshoot > Advanced options > Command Prompt.
In the Command Prompt, run the following commands one by one:
bootrec /fixmbr
bootrec /fixboot
bootrec /scanos
bootrec /rebuildbcd
Remove the thumbdrive and reboot your computer.
If the repairs worked your repaired drive should be bootable. Flash the disk image again.
So before you go through all the effort of installing Ubuntu, Using Windows 10 etc… try changing some of your settings in your BIOS. You won’t harm the system by doing this.
I prefer the path of least resistance to start with. I partitioned the M.2 as a whole volume and formatted to NTFS. Then, I used balenaEtcher to get a fresh copy of HA loaded up. I got errors when selecting either of the two images of HA I have. one, I downloaded today. I rebooted and was able to load haos_generic-x86-64-13.2.img on the M.2
There is no change on the Wyse. I still have no choices to boot from on the Wyse. I am now trying to load Ubuntu onto a thumb drive and am getting the same error with balenaEtcher. This is turning into an incredible rabbit hole.
it’s a 5070
When I click View, nothing happens.
