While using the Sonarr UI recently I have noticed that when navigating to the system tab the diskspace section tends to hang with the loading icon for sometime before being populated by my storage locations. Initially I thought this was a problem with my Apache 2.4 reverse proxy setup, but I manually tested the request in a web browser via localhost.
http://localhost:8989/api/diskspace?apikey=APIKEY
I also tested the https:// and reverse proxy URL’s with same results.
The diskspace api request in a browser took on average around 57 seconds. Which is not normal. Other than this issue the functionality of Sonarr doesn’t appear to be affected.
My storage consists of a Windows Server 2012 R2 Storage Space Mirror as well as Windows UNC path. I’m thinking the UNC path may be causing the long latency on the request, but as far as I was aware, Sonarr supports UNC paths for storage. I am able to create series entries with the UNC path without any issues.
C:/ (OS)
D:/ Virtual Disk (Network Drive for backups)
E:/ Storage Space Mirror
UNC Path to a NAS
After going into the box itself via Remote Desktop it looks like the Virtual Disk was causing the hanging. Overall the I/O on that disk was hanging even Windows Explorer. A reboot was needed to clear it in the end.
So it was a network drive, but not the UNC path at fault as I originally thought.
While not the fault of Sonarr, is it likely there would be an option to ignore certain disk drives in the future? I only use two of those drives for Sonarr use.
It would appear the API stalled because of some massive I/O performance degradation that occurred, so like I said not actually Sonarr’s fault, but good to know why it happened.