So, I'm fresh to Drivepool and Drive Scanner, and I run into a few things that I don't understand. I hope someone can explain them to me.
Background: I recently build an AM4 home server, using 8x 4 TB drives (all leftovers, of which some of very questionable heritage, and some are even SMR's, brrr).
Software: Windows 11 / Drivepool / Drivescanner / HDD Sentinel
Other software on the same machine: SqueezeBox (Lyrion) Server / Plex
I noticed a few things, and perhaps I don't understand how it exactly works.
1. In the Drivescanner window, it shows how many days ago the last scan took place. I have different periods set for filesystem scans and sector scans. What is exactly shown on that page? The last sector scan, or just any scan activity?
2. When I set in settings 'only perform within this window' it doesn't seem to matter whatever I set as 'unless disk scans are past due by xxx days'. It just never starts scanning, unless I use 'perform work at any time'.
A bug, or something I don't understand? (Probably the latter 🙂 )
3. Under throttling I use 'do not interfere' with 'high sensitivity' which is ok. I was just wondering why 'scan using background' would never trigger a scan, even when there's nto a single user or other application (but the generic services) actively accessing any of the drives.
Again, I'm a newby with Drivepool and Drivescanner...
Question
BluezNL
So, I'm fresh to Drivepool and Drive Scanner, and I run into a few things that I don't understand. I hope someone can explain them to me.
Background: I recently build an AM4 home server, using 8x 4 TB drives (all leftovers, of which some of very questionable heritage, and some are even SMR's, brrr).
I noticed a few things, and perhaps I don't understand how it exactly works.
1. In the Drivescanner window, it shows how many days ago the last scan took place. I have different periods set for filesystem scans and sector scans. What is exactly shown on that page? The last sector scan, or just any scan activity?
2. When I set in settings 'only perform within this window' it doesn't seem to matter whatever I set as 'unless disk scans are past due by xxx days'. It just never starts scanning, unless I use 'perform work at any time'.
A bug, or something I don't understand? (Probably the latter 🙂 )
3. Under throttling I use 'do not interfere' with 'high sensitivity' which is ok. I was just wondering why 'scan using background' would never trigger a scan, even when there's nto a single user or other application (but the generic services) actively accessing any of the drives.
Again, I'm a newby with Drivepool and Drivescanner...
1 answer 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.