Hi all

Just wondered if anyone can explain this...

I have got a new Proliant ML30 G10 server and wanted to replace my aging ML310e G8 server which I have been using at home for many years.

So swapped everything over and spent 2 hours trying to get it to boot into UnRAID. Out of desperation I made a new USB key with the UnRAID USB Creation app and tried that and the new server booted immediately into UnRAID. So I knew it had to be something about the key. I spotted on the original key the EFI directory was called "EFI-" on the new demo UnRAID key it was called "EFI"... so as I have a backup of my key (thanks UnRAID Connect*)... I just renamed the directory from "EFI-" to "EFI"... immediately it worked fine

I was just wondering what the significance of the "-" in the directory name is? My understanding is that Legacy to UEFI is controlled with a "~" prefix?

Also thought I would post this in case anyone else has a similar problem and this might help them.

Thanks

I have just found that my VMs wont boot on the new server and shows this error;

I think this is because the old CPU (E3-1210 v3) was 4 physical cores and a total of 8 threads, while the new CPU is E-2224 which is only 4 physical cores and doesn't support hyperthreading... but am not sure how to correct the fact the VMs are (maybe) trying to use cores which no longer exist?!?

If anyone can assist in how to diagnose and fix this I would be very grateful

Thanks

Edited April 26Apr 26 by SliMat

Edit the VM, select cores/count again?

18 hours ago, SliMat said:

I was just wondering what the significance of the "-" in the directory name is? My understanding is that Legacy to UEFI is controlled with a "~" prefix?

-EFI prevents UEFI boot, this was the old default. EFI allows UEFI boot (and does not prevent legacy boot), and it's been the default for some years now.