@agentx007 I tried to watch through your video with "scan-pass"; however, your version is old and for windows 7. It is not the same as windows 10. I skipped your video and search for the cause. I found the problem. Somehow the new version of BDU downloads and extracts clover into USB then manages to boot from CD/DVD ! NOT from USB. After searching the cause, I found one person suggested to use command from the Shell> fs0:\EFI\boot\bootx64.efi (or fs1:\EFI\boot\bootx64.efi depends on which is your USB installation)

Finally, I have SUCCESSFULLY installed windows 10 into nvme sdd and made nvme 970 evo boot into windows 10.

For now, every time I boot my computer, it goes into clover first. I have to manually choose nvme ssd hd to boot into windows 10. I remembered some member configured plist to auto boot into windows.

Hi, guys!
Very interesting theme and forum. Several times I re-read it. And here the same I did all necessary with Clover and it turned out on my 6th summer computer with Legacy BIOS to make my NVMe SSD as a boot drive.
Thanks to all who took part.
p.s. Sorry for my english.

Good evening and sorry for my English but I use a translator because I do not know him.
After months and months of searching by mistake I found this forum, and this page, I have a 2008 workstation with a UEFI embryonic bios, but following this guide I managed to install NVMe with boot, thanks for your work.
Soon I will take pictures.
I have a problem, my is a PCI-e 2.0 but it is revealed as 1.1, and I have not automate the start yet, but I have no hurry.

Good evening, I have not had time to take pictures and more, but I have to thank you for the opportunity that you shared, the system now seems reborn, travels smooth as oil, made tests disabling in my UEFI (2008) and works great I hope to find the material time to share a positive experience with an old PC of 2008, and that serves others.

PCIE 1.1 is often due to down-clock power-saving like features @by_xfile™ if you didn't already figure that out. Put a load on the graphics card and check it again with GPU-z, I bet it then goes up to 2.0. If not, this can sometimes be fixed by removing the card and plugging back in, or by updating or downgrading drivers sometimes too

I joined this forum to thank OP, this post and all the contributors. Though my questions and inquiries were not addressed by any single post, I was able to piece together enough information to get this working on my HP Z800. I had a summary written here first but lost it. I ended up writing it out on steemit but I'll paste it here.

Load & Boot from Win10 on NVME/PCI-e on HP Z800
https://steemit.com/hp/@fobio/load-win10...ci-e-on-hp-z800

This will be part one of a multi-part series [fingers crossed] covering my attempt to modify a HP Z800 workstation into file, plex and web server housed in a XL-ATX full size tower with 14 drives. I have been dabbling in hardware and software mods for around 20 yrs and I know this is by no means difficult but as a DIY'er this is one of the more daunting yet doable mods at a low price and I believe the bang-for-buck is right up there for an hobbyist looking for something to do over the winter.

A little more background. I have a home lab server running a AMD FX8320 w/ 32GB ram, a M1015 crossflashed to LSI 9211-8i HBA IT mode hosting 13 drives for around 36TB or 24TB usable under Parity mode. This is all managed under Win10 Pro and Windows Storage Spaces. I've spent quite a bit of time reading about it over the past couple of years and despite its slow write speeds, it serves its purpose as a Plex Media Server and NextCloud host. After the recent Win10 1809 update, I started to notice the system starting to hiccup and I noticed a lot of errors within Event Viewer. Some I fixed thru tutorials and regedit, but others just won't go away...namely, IO and write errors to my array which is being updated with Seagate 8TB backup/SMR drives that are cheap TB-per-$ but slow as hell in write performance. Again this is not an issue for my media library mainly for Plex. So I started looking at upgrades.

I always wanted to try server grade equipment but was always put off by their price and footprint; you don't get much room to install racks in a condo. Anyway, I came upon these HP workstations that have server innards but in workstation form factor. The Z600 and Z800 offers dual Xeon's and room for lotsa ram and there's a batch on sale locally. Initially, I only needed a Z600 in its small form factor to play with but I kept reading about the slightly sexier Z800. Being blinded by the prospect of playing with new hardware, I didn't consider some important specifics, like UEFI vs legacy BIOS on these systems. But by this time, my mind was already going a mile a second and I've already plunged into this project.

First off, I was inspired by this post to attempt this.

Hacking the HP Z800 Xeon motherboard into a standard case
http://andybrown.me.uk/2intergrate014/11/01/z800/

Much smarter guys have done this awhile back and I'm just catching up. But not being an IT professional, I don't get access to this level of equipment until they come cheap on the used market. I ended up with a full system with its OEM case for around $600 CDN:

HP Z800
Dual Xeon X5680 @ 3.33 GHz [12 cores/24 threads total, 130w TDP each]
48GB DDR3 ECC 10600 RAM [upgradeable]

I got a barebones system and needed to add my own GPU and drives. I added a GTX 1060 3GB and a WD 256 NVME SSD on a PCI-e adapter. This is where it gets ...interesting. As the updated BIOS doesn't support NVME storage, I had to get creative with my kiddy-scripting, read: combining best practices and trial and error them into a workable solution. The following is after around 10 to 12 hrs of research:

Step 1:

Just to say Thanks, my old system is now booting off NVME, life in the old dog yet! (HP Compaq 8200 elite CMT).
Its not all cream cakes and coffee though but I guess its not bad considering its i7 2600, Sandy Bridge, 24Gb RAM.
I had thought that I should be able to leave win10 on my SataSSD (leaving the EFI partition there) and do a fresh install of win10 on the NVME. I did that and it will set up no problem but I never got it to boot to the NVME from Win10 dual boot screen.

I am going to upgrade at some point soon anyway but thanks for exercising my brain!

Surely I can put the clover boot thing onto one of my SATA drives instead of having the USB key in?

Maybe that is possible, make a bootable NTFS partition on your drive instead of USB, copy USB Contents there, and then point to that instead of USB?

Could someone help?

Short Description ox my Problem Case:

1. OS W10 PRO 64 bit installed on SATA-SSD (Samsung EVO 850, SATA 6GB/Interface, AHCI Protocol. Huge Software-Installation, everything works 100% reliable. W10 new Installation from Scratch to much work/effort.

2. HP Z420 WS, AMI BIOS, Intel C600/X79 Chipset, 4 Core Xeon Processor E5-1603 @ 2.80GHZ

3. BIOS Flashing regularly procedure OK, latest BIOS: J61_0394 flashed. Mods BIOS Flashing (NVMe Insert) not possible for sure, because of HP/AMI integrated Checksum protection.

4. Bought an EVO 970 M.2 NVMe SSD, installed it on a DeLOCK M.2 NVMe PCIe x4 Apatper. Build in a free PCIe Slot x4. EVO 970 recognised at W10 OS level as a data storage device. Automatically Microsoft NVMe Driver installation, in addition manual installation of Samsung EVO NVMe Driver. Benchmark at Samsung MAGICIAN Controller-Software, seq. read speed EVO 850 app. 500 MB/sec., EVO 970 3.500 MB/sec. (!).

5. 1:1 Clone EVO 850 to EVO 970 NVMe OK via Samsung Data Migration Tool, or Acronis 2019 Clone option.

6. Using an W10 USB installation Media (Setup via Microsoft Creation tool), new W!0 Installation works without any trouble.

7. Using the in the forum mentioned great Clover methodology to boot an NVMe storage device without a mod BIOS Version, even the booting of the fresh installed W10 environment is functionally working, without any problems!

8. As described at “5.”, unfortunately I´m not able to come to the wished stage, to boot the NVMe EVO 970, after cloning the existing W10 on my 850 EVO to the EVO 970 NVMe. The Device is recognised in the Clover Shell, the booting starts with a Microsoft circle symbol, but it then stops, with a blue screen error and the message “can´t find a booting device”.

Although I tried to find a solution description for this case, I´m at the point now, of personally having no ideas know anymore what to do further to cover this final boot problem issue.
Why not to stay at the EVO 850 as the working boot device? If I think about to renew my HP Z420 let`s say in two or three years, my W10 software platform won’t be smaller then. The hardware at that time will be changed to M.” NVMe interfaces and SSD Gadgets in regularly use. Norma HDD`s/NAS will only be used as mass data storage devices. So, I have to solve this case anyway in advance, to be prepared using an OS on a NVMe device.
I´m sure that there is a solution procedure, on an expert level, so I ask you, does Somebody of you has an Idea, knowing a solution to fix my problem case, I would be glad about.

Thank you in advance, Heinz

Hi Fernando (Dieter), as i wrote: "3. BIOS Flashing regularly procedure OK, latest BIOS: J61_0394 flashed. Mods BIOS Flashing (NVMe Insert) not possible for sure, because of HP/AMI integrated Checksum protection."
As i know now fore sure (HP Solution Forum), a modded BIOS can´t be flashed on a HP WS (These are Enterprise machines). They have strong protection integrated because of security reasons in Enterprise use. I tried AFUDOS an other FreeDOS based flasing programs, no chance. A senior expert explained it in detail to me, why its not possible. Their included hidden checksum protection hasn´t been "cracked" so far. So i gave it up and was glad to find the Clover based solution here.

Regards
Heinz

Zitat von Smudgedog im Beitrag #218

---

Surely I can put the clover boot thing onto one of my SATA drives instead of having the USB key in?

---

@htruempl

Clover is a UEFI bootloader, thus, the NVME you're trying to boot off of must be formatted in GPT.
See my post above.

It's likely you cloned a MBR disk over. In my post there's a set of command to convert NVME to GPT.
If this is in fact your issue, you'll be up and running once you convert the new boot drive to GPT. Try it out.