Monday, August 24, 2020

Fixing Steam 0 bytes available disk space issue when removing a drive from the system





 Ran into an issue this weekend, so I'm memorializing it here. 

I had two drives in my system, one SSD for the OS and one high capacity spinning drive for secondary, slower storage. The second drive is where I put my Steam Library.

I pulled the drive this weekend to put into another machine I'm using for temporary file storage while I migrate Synology servers (longer story). This 1TB drive was holding my Steam Library.


I went into Steam, and Steam recognized that the SteamLibrary folder was no longer present and set the default back to the C:\ drive. I thought I was all good.

Fast forward a week and I have picked up a used NVidia card, and wanted to test it out. Went to download/reinstall the game and Steam says there's "0 bytes available" even though there's no other Steam folder, and the DEFAULT is set to the C:\ drive.


Here's what I did, that wasn't covered by other posts and threads I found: 


1) Go to Steam Settings

2) then Downloads

3) then click Steam Library Folders


4) then right-click on the directory shown and click on Make Default Folder. (yes, yes, even though it says it's already the default)

5) then right-click on the directory again and click on Repair Library Folder. Steam will restart.

You're done. Try installing games again.



Sunday, January 26, 2020

Synology, Mac OS X, OpenVPN and Tunnelblick

I'm putting this here so it shows up in your chosen search engine more easily.

If you have a Synology NAS, have the VPN Server installed, configured OpenVPN and use an Apple Macbook with OSX with Tunnelblick as your VPN client, you've probably seen this message:
Warning: This VPN may not connect in the future. The OpenVPN configuration file for 'Undercity OpenVPN' contains these OpenVPN options: 'comp-lzo' was deprecated in OpenVPN 2.4 and removed in OpenVPN 2.5 You should update the configuration so it can be used with modern versions of OpenVPN. Tunnelblick will use OpenVPN 2.4.4 - OpenSSL v1.0.2n to connect this configuration. However, you will not be able to connect to this VPN with future versions of Tunnelblick that do not include a version of OpenVPN that accepts the options.
All you have to do to ensure compression is enabled, through the config file is to replace one line in the ovpn config file you're using. Replace the line with
comp-lzo
with 
compress lzo
You won't have the warning message show up in the Log window after that.

Chris