hpk

As I'm using the VM DSM to replace an older physical Synology with Logitech Media Server, I did a backup of the settings on the physical machine and restored it on the VM ... and now, Terminal with PuTTY works ... Need to check, what settings might have caused the behaviour described above ...

Thanks Balrog, didn't know that one ... so I needed to try it out, and it worked not as expected. I use PuTTY on the WIndows 10 client and can see the start of the boot process: COM1 - PuTTY GNU GRUB version 2.02~beta2-36ubuntu3.7 +----------------------------------------------------------------------------+ | DS3615xs 6.1 Baremetal with Jun's Mod v1.02-alpha | | DS3615xs 6.1 Baremetal with Jun's Mod v1.02-alpha Reinstall | | DS3615xs 6.1 Baremetal with Jun's Mod v1.02-alpha Force Install | |*DS3615xs 6.1 VMWare/ESXI with Jun's Mod v1.02-alpha | | | +----------------------------------------------------------------------------+ Use the ^ and v keys to select which entry is highlighted. Press enter to boot the selected OS, `e' to edit the commands before booting or `c' for a command-line. The highlighted entry will be executed automatically in 0s. [ 3.341029] sd 1:0:0:0: [sda] Assuming drive cache: write through [ 3.344508] sd 1:0:0:0: [sda] Assuming drive cache: write through [ 3.352841] sd 1:0:0:0: [sda] Assuming drive cache: write through [ 3.355359] sd 1:0:1:0: [sdb] Assuming drive cache: write through [ 3.359576] sd 1:0:1:0: [sdb] Assuming drive cache: write through [ 3.375711] sd 1:0:1:0: [sdb] Assuming drive cache: write through [ 3.662064] ata2: Read current link speed fail, retry 1 [ 3.669056] ata2: Read current link speed fail, retry 2 [ 3.676078] ata2: Read current link speed fail, retry 3 [ 3.696104] ata3: Read current link speed fail, retry 1 [ 3.703105] ata3: Read current link speed fail, retry 2 [ 3.710126] ata3: Read current link speed fail, retry 3 [ 3.812263] md: invalid raid superblock magic on sdb3 [ 34.775265] BTRFS: has skinny extents Hide But there it stops and I don't go to the prompt. Any idea what I'm doing wrong?

6.1.2-15132 Update from 6.1.1-15101 failed on ESXi Server as several discovered already. Therefore, I did the following to bring it up & running: I did a fresh install in a new directory on the ESXi server with an 8GB virtual disk. 6.1.2-15132 installs without any issues. I shut down the virual machine and moved the second virtual disk (4TB) from the 6.1.1-15101 installation to the new 6.1.2 installation directory. Then in VM settings I added this existing virtual disk with all my data to the newly created virtual machine. After restart, DSM reported an error on the new volume and offered to repair it (my guess, it copied the 200MB DSM files from the 8GB virtual disk one to the 4TB virtual disk two, as they were not the same). I started the repair routine wich ended up with an okay. After a reboot, everything was up and running, all data on my big virtual disk were there. So, for me it worked, hovewer: Don't forget, Jun's 1.02a loader is in alpha status. If you are testing things as I explained above, make shure you have a good backup concept. That it worked for me on my ESXi server does not mean, it works at your's as well. So be cautious and backup your valuable data before experimentig ... Good luck

Es läuft wie bei einer physischen Synology. Die DSM Software wird auf eine Harddisk geladen. Auf meinem ESXi Server habe ich 2 virtuelle Harddisks erstellt. EIne 8GB grosse, auf der ich die 3615xs mit DSM 6.1.1 installiert habe und eine 4 TB grosse für die Daten. Im DSM habe ich dann nur die 4TB grosse Platte als Volume eingebunden, die 8GB Platte wird nur für das System genutzt.

Jun's loader contains 4 files. I did the following steps: 1) modified ds3615.vmx ( virtualHW.version = "11" ) 2) uploaded all 4 files to a new directory on the ESXi server 3) added ds3615.vmx to the list of Virtual Machines. 4) in the VM settings: deleted the network adapter and added a new one 5) in the VM settings: created and added 8GB virtual drive 6) started the vm an connected to it in the browser 7) installed DSM 6.1.1 on DS3615xs 8) upgraded within DSM to 6.1.1-15101 Update 4 9) configured DS3615xs to my likes and shut it down 10) in the VM settings: created and added 4TB virtual drive 11) started VM 12) on DSM: added new Raid Group (basic, btrfs) 13) on DSM: added a new volume 14) installed Hyper Backup and Hyper Backup Vault from the Package Center 15) tested my backup concept after a few hours all data were restored ...

That's what I did today. Copied Jun's loader 1.02a to the ESXi Server and then a fresh install and update of DS3615xs ... Now the VM is running with 6.1.1-15101 Update 4 like the physical Synologies I have here.

Vielen Dank für diese Anleitung. Die Installation auf meinem ESXi Server hat keine 20 Minuten gedauert. Habe heute eine 5TB HD für meinen DL360p Server bestellt und werde die XPEnology DS3615xs als Backup einsetzen.