It’s been awhile since this site was active. It’s not really active now, but it does have a new name and a new domain.

This site has been dormant nearly two years, with the most recent post made in June 2015. This post doesn’t really qualify as re-activating the site. But I did make some changes and it’s likely I’ll be posting here a bit more.

I moved this site to WordPress.com hosting when I shut down my Linode VPS in 2014. I’m back on a Linode VPS server and I’ve moved this site back to being a self-hosted WordPress site. I kept the same theme and didn’t make any cosmetic changes so it shouldn’t be noticeable.

The migration went remarkably well. There’s a lot of graphics and images missing from older posts, but these went missing when I imported them into the WordPress.com site three years ago. I never got around to fixing them at that time. This time I went through and removed the broken/missing images and broken links from the posts. I did indicate in the affected post that old images and links were removed. Most were of old and obsolete software. Missing images were fairly easy to find so I think I got all of them, there are probably broken links remaining since I didn’t really dig in to find them. Cleanup will continue.

I also changed the domain name. When I started the site back in 2006 the domain osquest.com wasn’t available (not at a price I wanted to pay), so I used theosquest.com. After ignoring solicitations to sell me the domain, osquest.com was dropped and I was able to register it a few years ago. I finally got up the nerve to make the change and now use this as the URL. All the redirects seem to be working.

I haven’t been able to test the RSS feed to verify that it redirects successfully. This post will let me know. But the site has been inactive so long I doubt anyone will notice. If you do subscribe via RSS I suggest you switch to the new feed to avoid future issues.

If nothing else, the site may see some activity as I write about the site move and WordPress setup.

Synology has released Cloud Sync version 1.0-0378, In addition to several fixes it adds support for Amazon Cloud Drive and improves WebDAV compatibility.

The complete set of changes is:

What’s New

Added support for Amazon Cloud Drive.

Improvements

Improved WebDAV compatibility.

Fixed issues

Fixed an issue where S3 subfolders might not be correctly displayed.

Fixed an issue where token expiration is not duly notified in certain conditions.

Fixed an issue where an expired access token might lead to a syncing loop.

Updated Yandex Disk icon.

I applied the update to both my test NAS, a DS212+, and my production NAS, a DS1815+, without a problem. But I don’t use any of the affected services such as S3. Microsoft OneDrive, Google Drive, and Dropbox all seem unaffected.

Synology has released Disk Station Manager 5.2 Update 2 and is calling it DSM 5.2-5565 Update 2. While there are some security fixes there’s nothing major. Unless, of course, you’re impacted by one of the bugs that have been fixed.

Synology has also stated that they reviewed DSM and their implementation of OpenSSL is not vulnerable to the LogJam vulnerability.

The complete list of documented fixes is:

Improved the stability of SHR expansion.

Improved the stability of SMB transfer when the system is being accessed by an excessive number of clients.

Share this:

Synology has released a minor update to Cloud Station with 8 documented fixes.

Synology released Cloud Station 3.2-3479 for DSM 5.2. I installed the update on my DS1815+ without any problems. It automatically and silently updated the client software running on my Macs. (I don’t have any Windows machines currently running Cloud Station but it should automatically update those too.)

Documented fixes include:

Fixed an issue that might caused high CPU usage using QuickConnect connection.

Fixed an issue where SSD cache volume information may not be displayed correctly in Resource Monitor.

Fixed an issue where users with guest accounts would be unable to create new files or folders via SMB protocol.

I haven’t encountered any of these issues in the short time I’ve been using DSM 5.2. I will be setting up a SSD cache in a week or so and the security fixes are always welcome so I immediately applied the update.

I applied the update to a DS1815+, DS415+ and DS212+ Synology NAS without having a problem. The update only took a couple of minutes but it did require a NAS reboot.

Share this:

Synology updated both Photo Station and Video Station. No new funtionality but they are needed for security and compatibility.

Synology has released updates to Photo Station and Video Station.

Photo Station is up to version 6.2-2945. The changes are covered in one line:

Security Enhancements

Video Station is up to version 1.5-0754. Again, the changes are covered in one line:

Upgraded to be compatible with DSM 5.2-5565 update 1

I applied both updates to my Synology DSM 5.2-5565 NAS (the base DSM 5.2 installation) without an issue. I applied the update before DSM 5.2 Update 1 since the Video Station update was needed for compatibility.

Share this:

Synology has released DSM 5.2. My upgrade from the 5.2 beta had some hiccups but the upgrade from DSM 5.1 was problem free.

Today Synology Released DiskStation Manager 5.2 (a.k.a. DSM 5.2). I’ve been running the beta version since it was released and I’ve liked it. The beta has been problem free, at least for me, although the upgrade from the beta wasn’t. My problems appear beta related as a second Synology NAS, that was running the latest DSM 5.1, not the beta, didn’t have any problems.

The process I follow for upgrades is fairly straight-forward:

Update all installed packages to the latest version available.

Download and update DSM through the Control Panel.

The only beta upgrade issue I consider serious is that CloudSync no longer starts because of some version confusion1. After updating to DSM 5.2 the CloudStation package won;t start because it says it’s incompatible with the installed DSM version. The package won’t update because it’s a higher version number than what’s available for installation. The installed version is 1.0-0327 while the version available for install is 1.0-0263 and dates back to December 2014. I’m hoping Synology is just slow in updating the repository or can quickly update the version check and the package actually works. I’m going to give them a few days before I uninstall and then re-install the package. I’m concerned that the re-install will force a new sync which I’d prefer to avoid. [Updated 5/13 – Sure enough, the CloudSync package had an update waiting this morning and it’s fine after the update.]

The beta upgrade did not re-start any of the packages. Some started manually but some did not so I rebooted the NAS and they all started.

Neither of these problems occurred when I updated from DSM 5.1 to DSM 5.2.