Exo7

Hi, Thanks for the ovf template, it made deploying DSM 6.1 a breeze. Tested on ESXi 6.5 U1, updated DSM via config panel to 6.1.3-15152 Update 3 without any issue. Please verify you have set MAC to 00:11:32:2C:A7:85 if having DHCP issue. However, I noticed SMART status was not working as expected. I first though it was due to disk being in physical RDM mode and incorrect SMART handling in VMware stack, which I expected. I installed an IBM 1015 (flashed to 9211-8i IT mode) and setup passthrough to the virtual machine, but still had problem with SMART. My disks are 6TB Ironwolf, but ironwolf health monitoring was not working either. symptoms : - health info show as "unavailable" in storage manager UI for every disk, be it physical RDM or connected via a passthrough HBA in IT mode. - /var/log/messages complain a lot about /dev/sda & /dev/sdb while in the storage manager UI resolution : - add a SATA controler to the virtual machine - attach disk 1 as SATA 0:0 (this disk is 50MB, independant / non-persistant, provided with the ovf) - attach disk 2 as SATA 0:1 (this disk is 8GB, independant / persistant, provided with the ovf). Both disk must be attached to the SATA controler or DSM won't boot. caveat : the paravirtual SCSI adapter is not used anymore (except if you have added disk to it on your own). notice that the volume and raid group hosted on the 2nd disk won't be available anymore. You will have to reinstall some package (such as open-vm-tools-bromolow) to another volume. As I am new to xpenology, that might not be a best practice ? I have not yet figured it out. As a side note, I also have an horror story to share about the 9211-8i : symptoms : - disk and RAID group are recognized, but soon after it is pure chaos as one or more disk are faulted. - /var/log/messages show hundreds of SCSI sense code error - RAID group and volume eventually become bricked as all error are randomized against all disk connected to the SAS HBA. - rebooting or reconstructing the RAID is a no go as disk error will again show up very soon after. - disk manager show system partition of one or more disk as faulted - after erasing the faulty partition (use "benchmark" for a quick erase", disk is available again and SMART status show disk as healthy resolution : - figure if you have an overheat issue. The SAS 2008 chip can be very hot in small enclosure and do bad thing to your RAID group. - do not use firmware 20.00.00.00. Flash it to 20.00.07.00 !