Especially useful for enclosure-based systems (which are getting cheaper):
-
Simultaneously scan multiple drives
With SAS enclosures, the total bandwidth of the enclosure can be used if multiple drives are scanned at the same time. For example, 6Gbps (SFF-8087/8088) can probably do 4 simultaneous scans and still maintain peak drive output, a 12Gbps can go even higher. Even limiting it to 2 (to allow for other storage traffic) would improve scan rates. Having the setting be configurable would allow admins to control how much bandwidth they want to use. -
Save reports to the documents directory rather than the application directory
The tool currently saves the report with a static name and in the application directory. This means that old reports are lost on each scan, and that the reports are written to a drive that could potentially be under pressure already. Having it saved to the documents folder (or even better, a user-selected location) would mean the application directory doesn’t have to be touched. Even better, if the report name could contain the serial number of the drive and the date of the scan, it would make it easier for the admin to figure out what and when the scan was. -
Queuing of scans
Tying in to #1, admins could add a batch of new drives into an enclosure, and then queue up the entire batch for scanning. Combined with #2, this would allow an efficient scanning of the drives with the admin only having to deal with the results at the end of the scans.
The tool probably started as a simple single drive solution, but with the popularity of multiple bay enclosures, it would be nice to give the tool a bit of a refresh. Most of the internal diagnostics code can probably be reused, and a new UX could be provided relatively quickly (there are many examples of similar types of tools - even download managers could be used as an UX example).
If the original tool has no proprietary source code, it could be open sourced and others can extend it.