• Content Count

  • Joined

  • Last visited

  • Days Won


jadehawk last won the day on February 9 2019

jadehawk had the most liked content!

Community Reputation

10 Good

1 Follower

About jadehawk

  • Rank
    Junior Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Correct. The DS918 requires a new generation CPU. Which means we (HP Gen 8) are stuck on DS3615xs.
  2. I go manual install. however this time I tried it both ways and both worked. Also I am on SATA with my 3 drives in RDM..
  3. As of right now. my VM is running DSM 6.2.1-23824 Update 4. As Always you should ALWAYS verify this on your own (I made another Test VM to see if it worked) BEFORE making any changes (Updates) to your "Production" Xpenology install. My hardware is an HP Microserver Gen 8. If you have something different it may not work out the same.. VM or NOT. Best Practice is always to test on a disposable copy of your XPenology install, for us running VM's is simple to just add another VM and see. You are ultimately responsible for your data.
  4. Looking At your screenshot. I think you are trying to install the incorrect .PAT file. You need to install the one found here : https://global.download.synology.com/download/DSM/release/6.2.1/23824/DSM_DS3615xs_23824.pat I just tested that again on a new VM and it get's you up to Latest Version as of today 01/02/2019 Hope this helps.
  5. I don't have any idea how to go about installing the older driver. As far as I understand it, the acceptable latency for a VM datastore is 20ms or less. (Saw it somewhere, just cant remember where). Am also running a Surveillance Station on the XPEnology VM with 1 camera connected (forgot to mention that!)
  6. Mine is even Higher. But I really only use this copy of XPEnology as backup for the Main Synology box, and it also runs my VPN.
  7. In my case. with the HP Gen 8. I was unable to use pass-through of the drives and still be able to use the SSD drive on SATA5. (I may be doing something wrong, but I got it working using RDM) YMMV. As for the vid , pid. I didn't change them. I just made sure that the MAC address was correct. and I have two Ethernet ports. one is to connect to the VM Host and the other is for the XPEnology Virtual Machine.
  8. Are you re-using the synoboot.img? I had the same issues before, after I try to update to the latest DSM. the only way to get the VM working again was to delete and re-upload the synoboot.img to the datastore..
  9. Are you re-using the synoboot.img? I had the same issues before, after I try to update to the latest DSM. the only way to get the VM working again was to delete and re-upload the synoboot.img to the datastore..
  10. @MooseMan123 Try the following. Create fresh VM install and name the new server the exact same name as the original. once you are up and running do not create a new volume. shutdown VM and add your drives to the new VM. restart VM. and log back in to DSM , open up "Storage Manager", it should pick up the original array "Volume" and ask you to repair . I just migrated an array from a VM DS3617xs running 6.2, to a VM DS3615xs running 6.2.1. And all worked great. My drives however are RDM's which makes them easy to add to VM's (When I made them RDM's, they were part an array Volume already and I did not loose any data) Good luck This is how I made them RDM's : Video
  11. jadehawk

    DSM 6.2 Loader

    I have a similar setup as simoareva , so I'll share my results and await @simoareva to compare as well, my drives however are OLD WD Green drives in an SHR setup. Transfer is from a Windows 10 to the VM Virtual machine. on 1gbe Network connected to my router Hope this helps.. For comparison, Same test but from the Windows 10 to a Synology DS1817+ Via SFP+ DAC 10Gbe Cable (No Switch):
  12. - Outcome of the installation/update: SUCCESSFUL - DSM version prior update: Fresh Install - Loader version and model: JUN'S LOADER v1.03b - DS3615xs - Using custom extra.lzma: NO - Installation type: VM - HP Microserver GEN 8 - ESXi 6.7 + 1 VMDK on SSD + 3 RDM Drives (Network vnic set to E1000e) - Additional comments: See below ======================================================================================== RDM Drives where loaded on DSM 6.2 Update #2 DS3617xs. Migrating to new VM DS3615xs was as simple as assigning the drives to the new VM (after DSM 6.2.1 U1 was setup) and letting DSM repair the partitions. Didn't make changes to SataPortMap or DiskIdxMap (Interested in knowing why would I need to do so? @simoareva). HP Microserver Specs - 16GB ECC RAM, Xeon E3-1265L V2, 3x 2T Drives, 1x 500GB SSD(ESXi Datastore).