This topic has been marked solved and closed to new posts due to inactivity. We hope you'll join the conversation by posting to an open topic or starting a new one.
After the firmware update to 6.7.3 Beta in the log I find 117 instances op "snapperd[6739]: loading nnn failed" where nnn is a number between 6 and 671 and not in numerical order.
Thiese errors appear with hourly intervals, although not every hour.
Looks like after some snapshots were deleted some empty folders were left behind. Now that those folders have been removed you shouldn't get the snapperd errors anymore.
Please check if this also helps with the spin-down issue.
If you have updated to 6.7.3 and ran into this issue please try USB Boot Recovery (note for those using RAIDiator-x86 systems such as the Pro 6 you'll need to use the RAIDiator-x86 4.2.x USB Boot Recovery tool with the OS6 firmware renamed to RAIDiator-x86-something) with ReadyNAS OS 6.7.4 which is now available!
If you have not yet upgraded please upgrade to 6.7.4 rather than 6.7.3. If your system has already been fixed I would still suggest updating to 6.7.4 the normal way using the web admin GUI.
I performed the update to 6.7.4 through the standard update link as suggested. 20 minutes after the update I fount the same list of errors in the log file. So the newest rerlease does not seem to resolve these errors.
Looks like after some snapshots were deleted some empty folders were left behind. Now that those folders have been removed you shouldn't get the snapperd errors anymore.
Please check if this also helps with the spin-down issue.
The only apps we use are ReadyCloud and Resilio Sync. I updated Sync to the lastest version to correct extensive memory usage. ReadyCloud is only used by my for remote system admin.
Services that are turned on: SMB, AFP, FTP, UPnP, HTTP, HTTPS and Antivirus.
