Part 2 – This page
Following on from part one of this blog series, where we unboxed the DS1621xs+ and applied some basic configuration to the NAS, I wanted to delve a little deeper into the disk RAID setup and carry some basic performance testing with and without the SSD disk cache feature. Out of the box, the RAID config is set up using RAID 5. I wanted to switch this to RAID 10 in an attempt to maximise performance, albeit at the cost of capacity.
Change of RAID type
As I mentioned above, the default RAID config on the NAS is RAID 5, I want to change this to RAID 10. First, we need to remove the existing storage pool, which is managed by the Storage Manager app.
Once that is gone, we can move onto creating a new storage pool.
I opted to stick with a single storage pool as I wanted all the drives to participate in the storage.
Choose the RAID type from the next screen.
Choose which disks will participate in the RAID group. I chose all of them.
Warning all data will be erased, ok.
Once the storage pool is created, we have a note stating we need to create a volume before we can use the space.
Moving on to create a new volume.
The new volume will be created on the new storage pool.
Then you can choose a file system. I opted for Btrfs.
Give the volume a name.
Now we have a shiny new volume for consumption.
Virtual Machine Deployment
Synology offers the ability to run virtual machines directly on the NAS device through an app called Virtual Machine Manager. The underlying hypervisor appears to be KVM based but I need to confirm. I must say I am impressed with the functionality available with VMM. For some of the higher end Synology devices with a bit of RAM in them, they could quite easily host a highly available cluster for VM workloads, although cluster services do incur additional licensing costs. A compelling all in one device for SMB to SME type customers or even for ROBO (Remote Office, Branch Office) use case. For a single NAS device running virtual machines though, this is out of the box functionality with no additional cost.
We can see the status of our host (NAS) and storage are looking good. The first step to deploying a VM is to have an image to deploy from. I will be using a Windows 10 ISO file.
Browse the computer for the ISO.
Choose where the ISO will live. This is the storage volume we created earlier.
Wait for the ISO to upload and Voilà.
No to create a new virtual machine.
Choose the operating system type. One interesting thing here is the ability to spin up a virtual DSM (DiskStation Manager). This could be good for testing nested NAS functionality, or replication testing etc.
Choose the storage where the VM will live, this is the same volume we created earlier.
Give the VM a name and define what resources it should have made available to it.
Define the drive size for the virtual machine.
Configure the network. I need to look into this further but the NAS creates a default virtual network to connect to. It would seem you can create multiple networks though.
The additional ISO file is to install the in guest tools so they can make use of the virtual hardware the Synology NAS provides to the guest operating system. Much like VMware tools or Hyper-V integration services.
You can also define who can manage the virtual machine from a host level. It would make sense to create a dedicated role for this if granting access to multiple people in a none lab environment.
And then click apply to create the VM.
And then we have a new VM.
I won’t run through how to configure WIndows 10, there is plenty of articles out there to cover that element off.
In this article, we covered changing the disk RAID type to RAID 10 and detailed how to deploy a Windows 10 VM. In Part 3 I will show the difference the SSD cache can make to in guest disk performance on Windows 10.