NOTE: This problem is consistently manifested when running Jun's loader on a virtual machine with 6.2.3, but some also have problems on baremetal, and under certain conditions, other 6.2.x versions. The fix can be implemented safely on all Jun loader installs. You can verify if you have the issue by launching SSH and issuing the following command:
$ ls /dev/synoboot*
/dev/synoboot /dev/synoboot1 /dev/synoboot2
If these files are not present, your Synoboot devices are not being configur
As I continue to parse your issue report, I think you are confusing disk "suppression" with disks actually being present.
You said you set your loader to position 0:1 but if it is ESXi, it enumerates starting with position 0:0.
SataPortMap=1 says there is only one device attached to the first controller, but your drive is in the second position so it is never mapped to a /dev/sdx device.
SataPortMap=2 says there are two devices attached to the first controller, so th