Jump to content
XPEnology Community

Ambifacient

Rookie
  • Posts

    1
  • Joined

  • Last visited

Ambifacient's Achievements

Newbie

Newbie (1/7)

0

Reputation

  1. Hello all, just wanted to add to this discussion I have a DS216j which is a 32-bit ARM NAS. I wanted to migrate to my own XPEnology install, and used some old Ivy Bridge based hardware to do this. My DS216j was running 6.2.4 Update 2. Being on the wrong arch and a newer version, I wasn't hopeful to directly "migrate" without reformatting my disks. Each of my drives were in their own storage pool with one volume per pool (i.e. I did not use RAID). Please note that I did a backup of my files to other storage that's not part of my XPEnology setup. You should do this too. I also recommend backing up DSM configuration and applications if you plan on using those later. My setup and process: ESXi 6.7 was installed on to a USB. I grabbed the XPEnology OVF and VMDK files from here: https://xpenology.com/forum/topic/13019-tuto-configs-toute-prête-pour-vmware/ ds3617xs with Loader 1.03b I have an SSD that I plan to use for application install and some docker containers, so I created a virtual 32GB disk and attached it to the VM. I booted up DSM and set it up without any of my hard disks attached or mapped. Then, I applied the Synoboot fix to upgrade to 6.2.3 Update 3: https://xpenology.com/forum/topic/28183-running-623-on-esxi-synoboot-is-broken-fix-available/ My two disks were attached to the Z77 chipset's SATA ports. I passed these disks to the XPEnology VM using Raw Device Mapping: https://kb.vmware.com/s/article/1017530 They were attached to SATA Controller 1 After a reboot, DSM was able to detect my drives, identify the storage pools, volumes and my shares, set them up, and make them available. Storage Manager indicated that there was some error with my drive, and I had to Repair them. After clicking Repair my volumes were no longer degraded. Now I can access my files without having to reformat my disks. I did however lose all my installed Synology applications and previous configuration files, but that didn't matter to me. They still remain on the drives in @appstore and other residual folders, which I'll manually clean up.
×
×
  • Create New...