Create a Synology VM with XPEnology

 

I’m a huge fan of Synology NAS systems, but I must say, they do often put a gaping hole in your wallet.  Well, fortunately the folks over at XPEnology have created an alternative way for us to create your own Synology devices, whether it be deployed on a bare-metal system or as a virtual machine.  I currently own a few Synology NAS devices, but I love having the ability to spin up a working VM version quickly and with ease, for use in my nested lab environments.

 

In this post, I am going to show you how to create your very own Synology VM on VMware ESXi, Workstation, and Fusion hypervisors.  As I mentioned previously, you can also deploy this onto a bare-metal system, but since I do not have a spare system to test this with, I will not cover that deployment.  So without any further hesitation, let’s get to it!

Prerequisites:

• VMware ESXi
• VMware Workstation
• VMware Fusion
• XPEnology files
  • DSM 5.x PAT file – (please note that DSM 6.0 remains unsupported with XPEnology at this time)
  • XPEnoboot 5.x VMDK file
  • Synology Assistant (optional but recommended)
  • NFS Plug-in for VMware VAAI (optional but recommended)
  • Open-VM-tools (optional but recommended)

The type of Synology system that XPEnology emulates is a DS3615xs 12-bay unit.  Let’s begin by heading over to the XPEnology website and grabbing what we need.  At the time of this writing, the current version of DSM is the newly released DSM 5.2-5967, but the XPEnology team has not yet created an updated bootloader (XPEnoboot) that supports this version.  The current stable version is DSM 5.2.-5644 Update 5 (and can be manually updated to Update 8 at a later time).  The current stable version of XPEnoboot is 5.2-5644.5 so I’ve downloaded the following files…

Now the fun begins, and I will start with the VMware ESXi deployment.  I will be deploying on the newest version of ESXi 6.0 Update 2 via the vSphere Web Client.  For those of you using the vSphere C# client, the directions are the same just the interface is different.

 

ESXi 6.0 Update 2

Part 1:

Create a new virtual machine

Give it a name and select a folder to place the VM in

Select a compute resource

Select a storage location

Select the proper Compatibility version

Select the following Guest OS settings

Customize the VM with the following settings, remove the floppy, and select the appropriate network 

Finish and let it build the “Shell” VM 

 

Part 2:

Now that the VM has been built, we need to add the XPEnboot VMDK that we downloaded earlier to the VM

Browse to the datastore where you created the VM and upload the XPEnoboot VMDK 

Once uploaded, we need to add the disk to the VM 

At this point, I also like to add an additional SCSI disk which will be used as an NFS volume, or iSCSI LUN.  You can make this any size you like but for the purposes of this post, I’m just going to add a simple 50GB Thin Provisioned disk. The 16GB disk we created with the VM will be used to install application packages (i.e. – VMware Tools, etc.)

Keep in mind that this is a 12-bay device, so you can technically add 10 more disks to fill all the drive bays

Now power-on the VM and open the console window.  Keep an eye on the window for the IP address assigned to the VM.  You can connect to this IP using a web browser instead of using the Synology Assistant to detect and connect to it.

Open you favorite web browser and type in the IP address of the VM, and hit enter.  This will connect you to the VM’s Synology Web UI

Click the Set up button, then click the Manual Install link and browse for the DSM .pat file we downloaded earlier. Then click the Install Now button

This will prompt you that it will erase all data on all disks, including the XPEnoboot disk we uploaded and attached earlier.  Note, I have experienced failures at this point and received a message that the .pat file may be corrupt.  In the even this also happens to you, please use this alternative XPEnology download link.

Once complete, the VM will be rebooted.  But since we erased all of the disks during installation, the VM will fail to boot properly and this is expected

Power off the VM and access the datastore that the VM is stored on.  Delete the XPEnoboot VMDK then re-upload the VMDK that we originally downloaded

Power on the VM and select the Install/Upgrade option

When it finishes it boot, this time you will notice that it will not display the IP address we saw the last time.  The IP should have remained the same but I’m going to use the Synology Assistant to detect it and help me connect since my web browser was not connecting to the same address

Now we are presented with the Web UI screen and we can login with admin and a blank password

Click next and give the Synology VM a name and change the admin user password or enter a new username and password then click Next

In order to prevent updates from installing automatically and possibly breaking the boot up of the Synology VM, I chose “Download DSM updates but let me choose whether to install them” and clicked next

I also chose to skip the “Set up QuickConnect”

And….You’re Done!  You now have a fully functional Synology virtual machine.  You can feel free to add additional disks or what have you.

At this point, I like to go ahead and install the Open-VM-Tools package so that I can use the VMware tools to gracefully power off the VM as needed.  To do so, you will need to have downloaded the package from the XPEnology website.

Open Package Center, then click the Settings button.

On the General tab, set the Trust Level to Any Publisher and click OK

Back in the Package Center, click Manual Install.  Browse to the package and click Next

Since we have yet to create a volume, it will prompt you to click OK to launch Storage Manager and create a volume to install the package on.

In Storage Manager, click Volume the click Create.  Keep the default of “Quick”, Next, select Disk 3, Next, OK to the warning message, Yes for disk check, Next, Apply….Done!

    

Now, repeat step 3 above, click Apply, and you will have VMware tools installed.

Wow, that seemed like an awful lot of steps, but it really wasn’t all that much.  In the next sections, I will just go over the deployment of the “Shell VMs”  and the steps to add the XPEnoboot VMDK to the VMs in VMware Workstation and VMware Fusion as the rest of the post-boot setup steps are the same.

 

VMware Workstation Pro 12.1.1

Part 1:

Create the Shell VM…

Part 2: 

Add the XPEnoboot VMDK to the VM…

Power on the VM and continue with same process outlined above for ESXi deployment.  Use the Synology Assistant to find and connect as the VM may not display the IP address right away.

 

VMware Fusion Pro 8.1.1

Part 1:

Create the Shell VM…

Part 2:

Add the XPEnoboot VMDK to the VM…

Power on the VM and continue with same process outlined above for ESXi deployment.  Use the Synology Assistant to find and connect as the VM may not display the IP address right away.

 

Now you should all feel confident in creating your own Synology VM systems for whatever your use case may be and hopefully you will all love using Synology products as much as I do.  If you would like the true experience, I’d recommend purchasing a real system.  But in the interim, this will give you a way to create your own and play around with it.

Keep in mind that when updates are released, it is always wise to first check on the XPEnology site and/or forum to see if the updates break anything as sometimes they will cause the boot process to break since the XPEnoboot cannot support it yet.  Usually you are safe to update as long as the update is within the same DSM version, but consult the site/forum first as I am not responsible for any upgrade impacts.

Well, I hope that you all have enjoyed this read/guide and come back for more!

And giving credit where it is due, I’d like to give a shout out to Erik Bussink as his guide is what inspired me to write this updated guide for all of you!  

Cheers!

-virtualex-

Home Lab 2016 – Part 3

 

Hello all!  My sincere apologies for the brief hiatus, but I am back to continue my Home Lab 2016 series.  In my previous posts, I covered the components that make up my new Home Lab.  In this post I will quickly cover my Storage and Network solutions that connect my lab.  Let’s get to it!

I will begin by covering my networking components used in my home LAN and LAB.  

• ISP Modem
• Ubiquiti EdgeRouter Lite – ERLite-3
• ASUS RT-AC68U Router – AC68U
• Cisco SG300-10 SMB Managed Switch – Core1
• Cisco SG300-52 SMB Managed Switch – Core2

 

My WAN connects to my ISP modem, which then connects to my amazing Ubiquiti EdgeRouter Lite (ERLite-3) via eth0.  My hardwired LAN connects from eth1 on the ERLite-3 to port 1 on the SG300-10 (core1).   Lastly, I changed my ASUS router to Access Point mode and connected my Wifi LAN from port 1 of the ASUS to eth2 on my ERLite-3.

EdgeRouter Connections:

• eth0 – WAN
• eth1 – LAN (configured as a 192.x.x.x network)
• eth2 – WLAN (configured as a 172.x.x.x network)

On to the Cisco SG300-10 (core1), 10-port managed switch, this is configured in Layer 3 (L3) mode and is where I created all of my VLANs and DHCP scopes, etc….

• port 1 – connects to ERLite-3
• ports 2-5 configured in an LACP/EtherChannel trunk to Cisco SG300-52 (core 2)
• ports 6-10 connect to different rooms in my home LAN

 

I created the following VLANs on core 1 and allowed them to traverse the trunk to core 2.  

• VLAN10 – IPMI
• VLAN20 – ESXi Management
• VLAN30 – vMotion
• VLAN40 – VM Traffic
• VLAN50 – NFS Traffic
• VLAN55 – VSAN Traffic
• VLAN60 – DEV-VM Traffic
• VLAN65 – DEMO-VM Traffic
• VLAN99 – UPS/ATS/DPU

The Cisco SG300-52 is configured in its default Layer 2 (L2) mode and I set up the proper settings, trunk ports, and access ports for each VLAN.  I understand that I could’ve also configured this in L3-mode and reduce the extra hop to core 1, but I didn’t feel the need to do so for my use case. I may change my mind at some point, but it works for me…for now.  

Due to the way the ethernet cables connected from the switch to each ESXi host, I started configuring the switch ports at the end of the switch and worked my way towards to the beginning of the switch ports.

 

• ports 49-52 (LAG 8): LACP/EtherChannel trunk from SG300-10 (core 1)
• ports 23-24, 47-48: IMPI
• ports 1, 19-22, 43-47: ESXi Management Traffic
• ports 15-18, 25, 39-42: vMotion Traffic
• ports 11-14, 26: NFS Traffic
• ports 26, 35-38: VSAN/iSCSI Traffic
• ports 2, 7-10, 31-34: VM Traffic
• ports 6, 30 (LAG 7): Synology
• ports 5, 29: UPS/ATS/DPU
• ports 3-4, 27-28: Unassigned

 

Next, let’s take a look at Shared Storage.  I run my shared storage infrastructure on Synology DiskStation hardware, because…they’re flat out awesome, and give you a ton of bang for your buck!

• Synology DS415+
• Synology DX213
• 2 x 800GB Micron 500DC SSD’s
• 2x 480GB Micron 510DC SSD’s
• 2 x 6TB HGST Deskstar HDD’s

I have to say I absolutely love the Synology products, and my DS415+ rocks!  I have this running 4 SSD’s and a DX213 expansion unit attached with 2 HDD’s in in.  It runs DSM 6.0-* update *. The interface is slick and setting up the device is a breeze.  I am currently using NFS only in my lab, and plan to incorporate VSAN soon, as well as testing out iSCSI vs NFS performance.  For my disk setup, I decided to use the Micron 500DC SSD drives as my first Disk Group (Disk Group 1) for my performance volume (Volume 1), the Micron 510DC drives for SSD Cache, and the HGST drives as my 2nd Disk Group (Disk Group 2) for all other storage volumes (Volume 2-x; ISOs, Backups, etc.)

Well, there you have it.  In my next posts, I will go over the basic setup and configurations of my Home Lab.  

I hope you enjoyed the read!  

Don’t forget to comment and subscribe!