Custom Query (1415 matches)
Results (292 - 294 of 1415)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #308 | fixed | intel 530 ssd db entry | ||
| Description |
Intel 530 series are not in DB. Here I'm attaching diff, with updated attributes from Intel documentation about the drive |
|||
| #309 | wontfix | Use drive letter of Truecrypt mounted drive in Windows | ||
| Description |
Trying to use smartctl to access a truecrypt mounted drive in Windows using the drive letter. Smartctl says "Function not implemented". When I use the device name (e.g. /dev/sdb) everything works fine. See sample output below. C:\>smartctl --health F: smartctl 6.2 2013-07-26 r3841 [x86_64-w64-mingw32-win7-sp1] (sf-6.2-1) Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org Standard Inquiry (36 bytes) failed [Function not implemented] Retrying with a 64 byte Standard Inquiry Standard Inquiry (64 bytes) failed [Function not implemented] A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options. |
|||
| #310 | fixed | Support staggering of drive tests | ||
| Description |
On the mailing list a best practise thread popped up asking about test cycles which brought us to DEVICESCAN and the staggering of these tests when you have many (4+) drives in a box. A: If a user feeds something like "(O/../../(7|3)/00|S/../.././12|L/../../6/03|C/../../7/03)" to DEVICESCAN it should use best effort to not send that command to every drive at once. It should probably assume something like +30% of a drives reported test runtime before triggering another drive. OR maybe the schedule is in "every X days" and not "sun-sat" calendar weeks per say. B: A sane default (one short test per day, one/two long test per week, one offline per week/month?) to be added commented of course to the default config file. |
|||
