Hey guys, loving the software so far. Just got some issues that I was hoping to get an answer on.
So last night, one of my pools randomly ejected a disk and I thought that maybe something was going wrong with a drive in my pool. So I decided to have scanner re-scan all drives in the pool and it is taking a REALLY LONG TIME to finish the scans. The scan has been running for close to 12 hours on a 1TB drive and it is still at 50% as of writing this post. The issue I am seeing is the scanner seems to be scanning in bursts - reading a few sectors and then stopping for like 5 minutes or so to start the next sector scan. At this rate, my scan will finish by my calculations in 4 months (over exaggeration warning) which is just a little bit too slow for my liking.
My USB drives in another pool seem to scan continuously unlike my internal drives (which are the ones being scanned currently).
Hope someone can help me resolve why this is happening before my drives die.
Thanks!
EDIT: So I started scanning another drive in the same pool and it seems like only one drive (the first drive in the pool / the second drive on the controller / drive 1 not drive 0) has this long scanning time issue. Could it be that the drive is failing?
Question
Arman
Hey guys, loving the software so far. Just got some issues that I was hoping to get an answer on.
So last night, one of my pools randomly ejected a disk and I thought that maybe something was going wrong with a drive in my pool. So I decided to have scanner re-scan all drives in the pool and it is taking a REALLY LONG TIME to finish the scans. The scan has been running for close to 12 hours on a 1TB drive and it is still at 50% as of writing this post. The issue I am seeing is the scanner seems to be scanning in bursts - reading a few sectors and then stopping for like 5 minutes or so to start the next sector scan. At this rate, my scan will finish by my calculations in 4 months (over exaggeration warning) which is just a little bit too slow for my liking.
My USB drives in another pool seem to scan continuously unlike my internal drives (which are the ones being scanned currently).
Hope someone can help me resolve why this is happening before my drives die.
Thanks!
EDIT: So I started scanning another drive in the same pool and it seems like only one drive (the first drive in the pool / the second drive on the controller / drive 1 not drive 0) has this long scanning time issue. Could it be that the drive is failing?
Link to comment
Share on other sites
4 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.