In my home lab, I use Synology for my shared storage solution. In this post, I would like to talk about what Synology devices I use and how I have them configured.
From time-to-time, I find myself needing to hot add a virtual disk to a VM and expand capacity. While the process has improved over time, I still occasionally run into issues on Linux. In the post, I will cover potential issues and provide a workaround.
I recently attempted to extend a filesystem on my Ubuntu system and ran into an interesting problem I figured would be worth sharing.
I was recently asked to explain a discrepancy between the reported live storage size reported by Log Insight versus the actual disk size listed on the Log Insight virtual appliance:
As you can see in the above screen shot, the delta is rather significant (almost 40 GB!). So what is going on?
While I do not frequently have the need to create or extend logical volumes, I find that every time I do I need to lookup the commands. To make it easier for myself and others, I have decided to put together the commands I frequently run.
I ran into a frustrating issue the other day when attempting to add multiple new virtual disks to an existing VM. Upon doing so, I received the dreaded “Operating System not found” message when the VM was started. While the underlying issue was easy to discover, the way to fix the problem became tedious due to issues with the vSphere web client. This post contains some tips and tricks to make the process easier.
I recently was doing some performance tests and wanted to try out the VMware paravirtual SCSI controller (PVSCSI). The VM I was testing was running SUSE, had the LSI controller configured, and was running VMware tools on a vSphere 5.5 environment. Every time I tried to change to the PVSCSI controller the VM stopped working. For those of you thinking about using the PVSCSI, below are some tips that should assist.