dp64

Ah ok, maybe in that case I'll consider leaving it alone then, its more of a cosmetic thing really. Regarding hiding the 50MB drive, after some extensive testing, I noticed that if you hide the 50MB drive by moving the SATA port in the VM settings to a higher number before installing DSM fresh, the installation fails with I think a code 13 stating that the file is probably corrupt. However, if it is set to a lower port number, the initial installation goes through smoothly no problems. This got me thinking perhaps during future security updates, if the 50MB drive is set back to a higher port number in the VM settings to where it is hidden, could subsequent DSM updates/security patches fail installing? Meaning I'd have to "reveal" the 50MB drive before an update then hide it again?

Thanks for the reply, I will look into it. Will modifying synoinfo.conf for the disk slots affect functionality with packages and/or DSM updates?

Hello, I just got a 1.04b DS918+ running on a VM in ESXi for testing. I was able to hide the 50mb disk (set the sata port/slot number to a higher number) but in the storage manager in DSM, I see a total of 16 disk slots. The loader has the sata port map set to 4. Is there anyway to have it only show 4 slots like an actual DS918+?

Ah, ok. I was wondering if that was the case though hoped it could all be done on its own. Oh well, time to look into an XMPP solution. Thanks!

Hello, I seem to be having trouble with the Chat push notifications to mobile devices (Android). It doesn't seem to be working. Trying to enable push services gives an error in the control panel in DSM. Is this a Synology hosted service or am I doing something wrong on my configuration? Thanks!

Hello, I'm trying to see what the correct way is to add CPU/Memory/NIC after an installation of DSM 6.1 in ESXi 6.5 with Jun's 1.02b loader. I noticed that when I change the CPU core count or memory in the VM settings, after boot up, DSM goes into recovery mode. Clicking recover goes successfully and all appears ok but just want to make sure that this is normal behavior and the "proper" way to do it. Not sure exactly on how the loader handles such changes. Thoughts?

+1 I am quite interested in DSM 6 for Hyper-V as well.

Not working. The loader needs the Hyper-V integration drivers. Mostly for the network part. Sent from my iPhone using Tapatalk I did get it to work with generation 1 hyper-v and with a tool from http://xpenology.com/forum/viewtopic.php?f=2&t=16114&hilit=DSM_DS3615xs_7393 [spoiler=](it seems the download link is gone but i have them if anyone needs them) DS3615xs_7393.iso i was able to install using the install option iso and then updating use the DS3615xs_7393.pat you have to use the install option for every boot and the nics only the show 100mbps I would like to try this out on hyperv too, if you could direct me to the files needed it be much appreciated. Also, Does it run gigabit even though it says 100mbps like the older DSM5 loader? How has it been running for you?

Hello I am trying to deploy nanoboot/Synology on Hyper-V in a Windows Server 2012 R2 virtual machine. I have found out that when using pass-through disks using Hyper-V, hard drive SMART data is not passed along to Synology. This does not seem good as I don't know if I will be alerted if one of the drives has a problem or begins to fail. I thought alternatively I could configure my drives in RAID using the onboard Intel Raid utility of my motherboard then pass the disks through to the VM so the onboard controller can monitor the drives but this does not seem ideal. Any suggestions? Thanks!