{"id":27410,"date":"2020-03-29T20:26:37","date_gmt":"2020-03-29T19:26:37","guid":{"rendered":"https:\/\/home.apeconsulting.co.uk\/adrian\/?p=27410"},"modified":"2020-03-29T20:27:53","modified_gmt":"2020-03-29T19:27:53","slug":"resize-virtual-disks","status":"publish","type":"post","link":"https:\/\/home.apeconsulting.co.uk\/adrian\/resize-virtual-disks\/","title":{"rendered":"Resize Virtual Disks"},"content":{"rendered":"\n

This is as much a reference for me as it is anything else, but I needed to resize a couple of virtual disks over the weekend, and these are the pretty simple steps to do it, at least for my FreeNAS configuration.<\/p>\n\n\n\n\n\n\n\n

It started because my UPS decided to shut down for some strange reason, and so far I have no idea why. That will require some further investigation and possibly another blog, but it’s not great to find everything switched off when the power to the house is just fine.<\/p>\n\n\n\n

Anyway, that was the why, this is supposed to be about how! I was actually quite happy as pretty much everything (jails and VMs) came back online within about 15-20 minutes of rebooting. The only things I thought hadn’t restarted were my iSCSI service (which I use infrequently on FreeNAS0 with BerryBoot, again for another blog) and my TrueCommander container on my Docker VM. I fixed both of these to auto-start so they shouldn’t be a problem moving forward.<\/p>\n\n\n\n

Everything else appears to have worked perfectly, but around 24 hours later I noticed that some adverts weren’t been blocked by Pi-hole. It was allowing internet traffic, and from the homepage, it appeared to be running, although I could see nothing was being blocked. On further investigation, the virtual disk on the Pi-hole VM was completely full, as I’d only assigned it 10GB when it was created. I could have probably tried to free up some space, but given I’ve still got over 20TB of free space on FreeNAS0, I thought the easier solution was to increase the size of the virtual disk. This works something like the diagram below (which I found on the internet and the blue legend really should be green!)<\/p>\n\n\n\n

\"resize<\/figure>\n\n\n\n

I’ve done this before on FreeNAS1, and had even blogged about it a little here<\/a>, but I needed to Google a few other things so thought a more detailed blog might avoid that in the future. I didn’t document things when I increased the virtual disk for Pi-hole from 5GB to 50GB, but I decided to check the other VMs and noticed the Docker one was around the 85% mark (that had 50GB assigned) so I thought I’d bump that to 200GB and document the steps below:<\/p>\n\n\n\n

Increase the zvol size<\/h3>\n\n\n\n

The first step is to shut down the VM as I’m not sure messing around with the zvol size when it’s running is a great idea. After that, it’s just a case of going into the Storage > Pool > Iohyve dataset and editing the appropriate zvol. I’d let FreeNAS name them when I created them, so I needed to check in the VM settings to identify which was which! Also, beware! Increasing the size isn’t a problem, but bad things will happen if you try to go the other way.<\/p>\n\n\n\n

Restart the VM<\/h3>\n\n\n\n

Next, restart the VM and SSH into a terminal window. <\/p>\n\n\n\n