NVME boot drive not found after image capture .. doh !
So I was trying to image our UEFI HP Z240 with an NVMe (SamsungMZVP128HDGM-000H1), and after editing the DHCP policies it seemed to image fine. It did, in fact, save an image on my storage node, but upon coming back in the morning, no hard drive found.
This is unnerving, as I was trying to backup the exceedingly expensive calibration job on some scientific equipment this machine runs. I’m going to try a live distro to try and pull the most expensive data, but I’d really like to get this thing to work.
I found this link
As this issue didn’t seem to hose the OS, I started a new topic.
@geardog I thought you might just want to start from scratch, install a fresh clean windows 7 in UEFI mode. But seems like you could even convert form legacy BIOS to UEFI if you are keen: https://social.technet.microsoft.com/wiki/contents/articles/14286.converting-windows-bios-installation-to-uefi.aspx
This post is deleted!
It appears any time I boot the machine in legacy mode.
Well sure. As I keep saying - switching between UEFI and legacy BIOS is NOT a good idea. It will not work.
It happens even with spinning platters, as win7 is not compatible with UEFI.
Though I am not a windows guy I am fairly sure this can be done. A quick search engine foo got me this post in MS technet from 2011. So I am fairly sure it is possible!
I don’t bother much about looking into getting iPXE to work in legacy BIOS mode as I reckon it should be way easier to install in UEFI properly.
The error is a windows boot error, or it is perhaps generated by the UEFI. It is shown in the string of 6 photos. It appears any time I boot the machine in legacy mode. It happens even with spinning platters, as win7 is not compatible with UEFI. I don’t know of a way around this switching until I upgrade to win10. Not sure it will ever happen as this is a Zeiss CMM control box.
I haven’t had any luck getting any of the UEFI boxes to come up as legacy, but I know diddly. That might work.
but upon coming back in the morning, no hard drive found.
Can you post a picture of that error? Is that in FOG? I am still kind of confident that we can figure out a way to make this work without switching. Going from UEFI to legacy BIOS and back is not a good idea anyway.
So the trouble I’ve had with this box is that it falls in the middle of the bios/UEFI game. I’m dealing with Win7 (doesn’t play UEFI) and an i210 NIC (doesn’t seem to play Legacy). Upping to Win10, and booting fully UEFI would be the fix for this last quibble with this box.
@sebastian-roth Honestly just happy I didn’t hose my boot files. I’ve sorted a number of complications that made this seem a bigger deal than it was.
The only settings that seem to have any impact are UEFI secure boot options. It amounts to a toggle between:
[Legacy on; secure boot off] which allows NVMe drive to be found and boot, but gives a fog failure “no cofiguration methods succeeded.”
[UEFI on; secure boot off] which prevents a windows boot, but gives way to UEFI policies picking up the DHCP/PXE request.
Thoughts on how to get both sides to work would be great. I’m tempted to shift HDD mode to SATA, perhaps allowing it to work with UEFI, but I’m not excited about hosing my HDD in the process. I have a few more NVMe computers to go, and so far it hasn’t been as awesome as the bios boxes.
Boot option “BOOT as UEFI” (which allowed the i210 NIC to be configured by fog properly) prevented the hard drive from being seen.
Well that’s really unfortunate. Mind taking pictures of the settings and errors you see and posting those here? Possibly we can still give some advice on this.
The error was poor notes on my part. Boot option “BOOT as UEFI” (which allowed the i210 NIC to be configured by fog properly) prevented the hard drive from being seen. Looks like I’ll have to adjust bios any time I boot from FOG.