kurti500

as far as I have read, the N40L has no controller which can be passed through.... I'll stick with SATA for now, however the LSI Logic SAS did work as well, I recently just had issues with the Paravirtual as often after a reboot 1 disc was lost from the RAID and had to be put in place again with "repair" Cheers.

Thanks for your feedback, I would be interested in reliable SMART data within DSM, which controller/settings are recommended here, or is it really trial and error?

Hi all and merry X-mas. Successfully got my N40L running on ESXI 6.5 upgraded to DSM 6.2.3 with this tutorial, disks using RDM. Thanks a lot! But even after reading tons of posts, I am unclear about what are the best, most performant settings in regards to the RDM disks and the controllers and settings to be used? 1. loader synoboot disk is on SATA 0:0 with disk mode "dependent" -> could this also be "independent non-persistent" to avoid overwrites? 2. data storage disks are on SCSI 0:0 to 0:2 as LSI Logic SAS controller, no BUS sharing. Disk as "independent-persistent" and disk compatibility "physical" -> is the SCSI "VM Paravirtual" controller having any advantages? -> any advantages/disadvantages using a SATA instead of the SCSI controller for the RDM disks? Wondering if any of the options/combinations gives the best disk performance? Is there an easy answer? Thanks for your support!

Quick question, I am running a N40L Microserver ESXI 5.5 and Xpenology DSM 5.2, the physical CPU is an AMD one. Does the restriction that AMD is NOT supported also affect an ESXI installation of Xpenology or will the virtual machine "hide" the AMD and will allow to use bootloader v1.02b with DSM 6.1 , too? Just wondering as under DSM 5.2 Control Panel, Basic information on ESXI the CPU is shown as INTEL Core i3-4130 with 2 cores at 1.5GHz Thanks and sorry for the noob question.