Thanks for the additional information. I’ve replied in bold, @ColtonYYZ
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.
Yes, on the same computer.
Hi
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.
Oh dear, I did suggest only deleting if it works 
The Dell user guide isn’t particularly helpful
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.
HAOS - The system must be 64-bit capable and be able to boot using UEFI.
(Source: Generic x86-64 - Home Assistant)
- You said your setting for UEFI is set to NEVER. → Turn it ON.
- TPM settings are correct
- You said your Secure Boot is: SECURE BOOT NOT ENABLED → ENABLE IT.
Hit Apply after each setting change. Then reboot and see if it finds your drive again.
If this fails, then I’m afraid you will have to troubleshoot your drive by using the suggestions given above by @stevemann
Yup, I screwed the pooch. I did not apply or exit when I deleted, I powered it down. My bad. But, it’s done.
F12 gives options:
UEFI Boot: Merlin Non-Pxe
OOTHER OPTIONS:
Bios Setup
Bios Flash Update
Diagnostics.
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.
Have a look at the source path of the .img file in the error you have posted. It appears it is trying to get the image from a directory with the same as your file name.
I know it was suggested to install Ubuntu, but I’ve never had luck with it personally. Debian was always easy for me to use. Try Debian (KDE) and see if that works better for you…
https://cdimage.debian.org/debian-cd/current-live/amd64/iso-hybrid/debian-live-12.8.0-amd64-kde.iso
This one is a LIVE version so you can simply run it from the USB without having to install.
It wont save any settings you may adjust while using it, as it is a fresh boot up everytime you use it. But at least it gets you going and you’re then able to check your M.2 drive.
And it allows you to install HAOS directly on to your M.2 as well.
Just in case: I have used these instructions (on a Dell Thin Client) to do the job very easy & fast Installing HAOS on a dedicated x86-64 PC - #11 by MichaelSidenius
1 Like
Thank you for all of the suggestions. I have so much on my plate, that I cannot make the time that is needed to do the testing. I’ve got a new M.2 SATA drive coming today. I don’t mind spending the money to save precious time and frustration.
I don’t get why I am getting that error message when I select the image path in belanaEtcher. The 12.4 image that I was trying is the very same path and file I loaded when I initially set up the Wyse 5070. The path and file name has not changed since I downloaded the image. Yesterday, I altered the folder name by removing the dot to the left of img. That helped.
I think belanaEtcher does something to the drive after it flashes the OS. When I view the drive in Disk Manager, it shows 2 partitions, one is active and healthy the other unallocated. I cannot remove the allocated partition with Disk Manager. The only way to remove the partition is through DOS. Or, the drive is not working properly.
My feeling is the M.2 SATA is trashed. I recall seeing multiple partitions on previous attempts at flashing the M.2 SATA. A brief search shows there should be 8 partitions. I only get two.
Hopefully, the new drive will get me back up. I’ll report back when there is something to report.
Thank you again for all of the suggestions.
You can clean the drive using Windows Disk Part in Command Prompt.
Open Command Prompt
Type Disk Part
List Disk
Select the disk (Ex. Select disk 5)
Type: clean
Type: create partition primary
Type: format fs=NTFS quick
Type: assign
And the drive should be back to normal.
Thanks, @ColtonYYZ , I’ll look at that a bit later. I have made progress. I’ve loaded the new drive with HA using Rufus. The drive is recognized in the Bios on the Wyse 5070
I still cannot boot to HA. I get “operating system loader failed signature verification. Warning the file may have been tampered with.”
All bootable devices failed secure boot verification.
That’s because you don’t have secure boot turned on in BIOS
Did you follow this:
A very easy, pure GUI, way to install the x86 OS is by:
- Boot your x86 system with a live Ubuntu USB3 (3 for speed) stick
- Download the x86 OS image to e.g. Downloads folder
- Start the “Disks” program (WIndows key, find the “Disks” program).
- Select your target PC harddisk (not the USB disk), press the “three dots” menu buttom on the right (not the “three lines” menu on the left), and select “Restore disk image…”.
- Now you can simply select the downloaded image and it will be written onto your selected target disk. Dont mind the warning about size difference (unless you installed too small a disk
). - Reboot and follow the onboarding procedure described elsewhere
@ColtonYYZ , I was not going that route. I was going the route of loading HA OS to the M.2 SATA, installing it and booting up the Wyse 5070.
This last issue was caused by secure boot being enabled and UEFI Boot Path Security set to Always… I disabled secure boot and changed UEFI Boot Path Security to Never.
HA is now running on my Wyse.
I think my original M.2 SATA is damaged. I am happy the new drive has fixed my issue. Thank you all for the help it is greatly appreciated 
1 Like
Good you got it solved Brian!
Please mark the post with the answer that helped you as the solution so anyone who’s searching for this can benefit from it.
You do that by selecting the three dots under the post:
Then select the check box:
Also, by doing so this prevents that someone else steps in for trying to help.
I am happy to do that, Nick. When I click on the three dots under @stevemann’s post, it just bookmarks it.
Is that all I need to do?
Apparently it’s marked as solved!