Encountered a new error that I have not seen before working with ESXi 6.5. I was upgrading from the base VMUG ESXi 6.5 image to the latest patched and received the following error
[Errno 28] No space left on device
vibs = VMware_locker_tools-light_6.5.0-1.33.7273056
Please refer to the log file for more details.
The datastore had plenty of space left, over fifty gigabytes. The fix is rather simple, but intuitive, enable Swap on a Datastore. Simply set the Datastore attribute to one of your datastores and try the upgrade again.
Message: The update completed successfully, but the system needs to be reboot ed for the changes to be effective.
Reboot Required: true
Hopefully this saves some people some time and aggravation searching around for answers.
In preparation for working with Boot from SAN and other high network requirement work with my Synology, I looked into getting a 10gbe adapter. Unfortunately, the Synology Branded 10gbe Adapters are extremely expensive.
I was lucky enough to have a Mellanox ConnectX-2 Card kicking around. These single port 10gbe cards can be found on eBay for less than 20$.
After 3D printing a low profile bracket for the card found on ThingiVerse, I was able to power up the Synology with card and connect over 10gbe without issue.
Although I have yet to test the adapter for a normal workload, Synology supports other Mellanox Cards on its other Devices. We can also see by SSHing into the Synology, that the device correctly loaded the mlx4_en drivers.
[Mon Feb 26 11:22:58 2018] IPv6: ADDRCONF(NETDEV_UP): eth4: link is not ready
[Mon Feb 26 11:22:58 2018] mlx4_en: eth4: Link Up
[Mon Feb 26 11:22:58 2018] IPv6: ADDRCONF(NETDEV_CHANGE): eth4: link becomes ready
In the coming weeks I hope to have a series of posts detailing Boot from SAN configurations for ESXi as well as new posts and benchmarks working with Intel’s Xeon Bronze Series of chips.
Setup is rather simple for Storage Spaces on 2016, with clicking on File and Storage Services and then Storage Pools
From there you will see that Primordial Pool and on the bottom right the Physical Disks available for use.
From there click Tasks and New Storage Pool
Name your Pool
Select the drives you wish to use. For us, we chose 4 disk to create a mirrored pool. Selecting five drives or including the NVMe drive cause a failure to create a Virtual Disk.
Go Virtual Disk, Tasks and New Virtual Disk
Name the Virtual Disk and Select “Create storage tiers on this virtual disk” if you have a SSD on the machine. For us we have M.2 Samsung SSD in the system.
This is not an enclosure, we do not select Enclosure Awareness.
We make a decision between storage and speed and redundancy. For us we want the redundancy but can’t because we need a even number of same sized disks. If we were to chose only 4 disks, we would be able to use Mirror, but for just testing a
Since we chose Tiered Storage, we cannot choose thin provisioning.
Once the creation is complete, go and format the disk.
Now we benchmark, where it becomes immediately apparent that Spaces fails terrible on 4K Writes and does really well on Sequential. I would expect better 4K writes from a Single 7200 RPM drive.
Select your XenServer and select Networking
Click Add Network
For me I want to create a Network that can access the internet, so I select External Network
Name the Network
Select the NIC you wish to use.
You will see the new network show up in the Server Networks view
Log into XenServer via XenCenter
Click on your Server and Select Storage
Select New SR…
For me I have a 12G RAID Controller backing my storage, so I select Hardware HBA
XenServer will probe for Storage
XenServer found both my Storage Arrays, and I chose the Array(s) I wish to use.
We format the Storage Repository.
Then we will see the new drive show up.
Download Xen Server 7.2
Write the ISO to a USB Drive or Install with a DVD Drive. I chose to use Rufus
Boot the ISO
Select a Keymap
Accept the warning about your drive being overwritten.
Accept the EULA
Choose a drive to write the OS onto.
Choose a drive for VM Storage. I chose to do this in the Windows Client, and deselect all choices.
Select where your installation source is. For us, it is a local drive.
Choose whether to verify the installation media. I choose to skip it.
Enter a password for the XenServer Host
Select an ethernet adapter that you will use for Management of the Server.
Select and enter the appropriate network information
Name your host and enter an appropriate DNS Server
Select the appropriate geographically area
Select the appropriate time zone
Select the appropriate NTP Settings
Set the appropriate NTP Servers
Choose whether to install an Supplemental Packs. I have none, so I chose No
The installation will finish up
Reboot the server
Upon first boot I received this bug. The host ultimately boots after a minute or two.
Once the host boots navigate to its Management IP Address and Download the Windows Client.
Log into your vSphere Web Client and click Menu – Content Library.
Click the plus sign to add a new Content Library
Add a Name and Location
Select a Local Content Library if you wish to upload ISOs, OVAs, and other templates.
Select your storage location, I use my local Freenas NFS Store.
Click Finish and your new Library will appear.
To add items, click on the Name of the Content Library, then select Actions and Import Item.
Select the item and click OK.
vSphere will then proceed to upload the item.
Once uploaded items like ISOs can be selected on the create VM Screens.