Running v2.5.1.3062 of Scanner on a fully patched Windows Storage Server 2012 R2 Essentials system.
A couple of weekends ago the system disk in my Thecus W5000 box died without warning. After much fun and games I eventually succeeded in bringing the system back to life with a BMR from the last backup before the failure but once I got around to checking the status of the various components (I run both Drivepool and Scanner on this system) it became apparent that Scanner had apparently not noticed that the system disk had changed from the 500GB Seagate SSHD that Thecus supply in the base system to a 500GB Samsung SSD. It is still showing in the Essentials dashboard SCANNER page as Healthy and last checked on 16th September:
Is this working as designed inasmuch as the BMR has also reapplied some identifier to the disk that makes Scanner think it is the same device?? If not, what further information do you need to assist with troubleshooting this?? (I've captured the current contents of the ErrorReports and Logs directories in a ZIP archive, but that is 8.5 meg so I don't want to waste time and space uploading it somewhere if it isn't useful)
Question
Steve Pitts
Folks,
Running v2.5.1.3062 of Scanner on a fully patched Windows Storage Server 2012 R2 Essentials system.
A couple of weekends ago the system disk in my Thecus W5000 box died without warning. After much fun and games I eventually succeeded in bringing the system back to life with a BMR from the last backup before the failure but once I got around to checking the status of the various components (I run both Drivepool and Scanner on this system) it became apparent that Scanner had apparently not noticed that the system disk had changed from the 500GB Seagate SSHD that Thecus supply in the base system to a 500GB Samsung SSD. It is still showing in the Essentials dashboard SCANNER page as Healthy and last checked on 16th September:
Is this working as designed inasmuch as the BMR has also reapplied some identifier to the disk that makes Scanner think it is the same device?? If not, what further information do you need to assist with troubleshooting this?? (I've captured the current contents of the ErrorReports and Logs directories in a ZIP archive, but that is 8.5 meg so I don't want to waste time and space uploading it somewhere if it isn't useful)
Link to comment
Share on other sites
3 answers to this question
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.