Balrog

Did you use the VMXNET3 or E1000 as vNIC?

If you mount the "synoboot.img" with OSFMount you can see that there are 3 different boot-settings in the loader: "DS918+ 6.2 Baremetal" "DS918+ 6.2 Baremetal Reinstall" "DS918+ 6.2 VMWare/ESXI" I will play around with the settings and try an update of a running VMware Workstation Test-VM under DSM 6.1.x.

You can exchange the loader 1.02a with 1.02b. You just have to make the same changes of the mac-address and sn in the config file as usal. Have a look into the "how to-threads" here. There will be explained the process.

In the 1.02a-loader is a bug where you have to copy drivers manually after an upgrade of DSM. I would suggest to try the actual loader 1.02b. For debugging purposes it is also good to have access via putty over a serial connection. With this way you be able to see the whole boot process. I made a thread here in the forum with a manual how to do this.

So it's a problem with proxmox and not the H200 itself.I ran for about 2 years DSM with a bare metal installation due to problems with passthrough the H200 under ESXi 6.0. The situation is much better with ESXi 6.5 now.

I use the ds3615xs version. Its working for years now and I see no advantage for me in using the ds3617xs. Before inserting the H200 into the server I flashed it with the newest firmware to 20.00.07. In the early versions of P20-firmware was a bug but version 20.00.04 and after are fine. You can have a deeper look here: https://forums.servethehome.com/index.php?threads/tutorial-updating-ibm-m1015-lsi-9211-8i-firmware-on-uefi-systems.11462/ I dont know if it is the point where it hangs at your site but this is was I have done. Afterwards I put the card into the Server and passed it through the VM with success.

It is possible that the serial port function is only available with a licensed esxi-host but I am not sure about this. Sent from my SM-T810 using Tapatalk

So this is the md5 for the first package of 6.1.4-15217: de53ef411024536dd4c47517a9b8979d This is the md5 for the new release of 6.1.4-15217: 23acaefffb0d01aa9f57870fcfcfb887 It seems that mainly hda1.tgz is different in the pat-files (I decompressed them with 7-zip). I have decompressed hda1.tgz multiple times to be able to compare the files: - a lot of .so-files are different in /usr/lib - a lot of .so-files are different in /usr/syno/synoman/webapi/lib - a lot of "style.css"-files a different in various folders So it seems that the new 6.1.4-15217 is truely a new release with new content.

Nice. I will do it this evening after work. Gladly I even downloaded the original md5 from the first package.

I have downloaded the 6.1.4 package but not installed it. If there is a fresh release I can compare the content of the new package with the abandoned 6.1.4-package.

@4sag: Thank you very much! The tools are working.

I use a Dell H200 flashed to IT-Mode and it works very good with the loader 1.02b (under DSM 6.1.3 Update 4 as a VM under ESXi 6.5 Update 1 as passthrough ). The H200 is similar to the IBM M1015.

If you have installed DMS bare metal on the Gen8 you need to install a software for reading the sensors. Without the sensors values the Gen8 will run in a "save mode" with enhanced fan speed. Search the forum for "AMS". Here is a good start: http://xpenology.com/forum/index.php?/topic/4242-HP-microserver-Gen8-and-hp-ams

In your case I would try an installation via ESXi and fool the DSM to only have one CPU socket. On every installation I see DSM sees every cpu core from the first CPU socket. Only the information page from DSM shows only 2 cpu cores but I think this is hard coded. A proof with "cat /proc/cpuinfo" and an installation of "htop" via qnapware shows easily that every cpu core will be used. What do you want to do with such many cpu cores on a NAS?

As I played around I found that even the 3615xs offers the new "F1 -Format" if it detects 3 SSDs.