Actually, to be honest, the DrivePool should circumvent any drive size limitation. The driver shows up as a 2TB disk. However, everywhere else in Windows, it shows up as the actual size of the pool. This should prevent running into the limit.
As for the disks in the pool, there are a couple of ways to identify them.
- By the number (as it appears in disk management)
- By the disk labels (even with a letter, they can still have labels, and DrivePool sees that)
- DrivePool has an "Identify" option when a disk is missing to ping the disks, so you can see which are connected and where. (if the case has LEDs for the individual disks)
- StableBit Scanner. If it's installed, then DrivePool will pull information from StableBit Scanner. This includes the model number and serial number of the disks. As well as the customized "case" location (in Scanner, under "Disk settings", you can specify this information).
This option has a "Case" and "location" setting. It allows for a lot of flexibility here. And it shows up in the tool tips in DrivePool.
- By mounting the drives to a folder path (they won't show up in "My Computer" but in a path like C:\DrivePool\[case]\[drive])
Additionally, if you have both StableBit Scanner and StableBit DrivePool installed on the same system, if Scanner detects damage on the disk, DrivePool will automatically move data off of the disk to help prevent data loss due to corruption/damage.
By default, this is only for "damage" (bad sectors), but you can enable it for SMART data as well.
Also, there is the option to do either for unduplicated data or duplicated data.
Additionally, if you have Scanner installed, and you have notifications enabled, it will include the case and location information information in the notification.
Microsoft MVP for Windows Home Server 2009-2012
Lead Moderator for We Got Served
Moderator for Home Server Show
This is my server
Lots of "Other" data on your pool? Read about what it is here.