Custom Query (1365 matches)
Results (28 - 30 of 1365)
| Ticket | Owner | Reporter | Resolution | Summary |
|---|---|---|---|---|
| #502 | fixed | Missing variable quoting in update-smart-drivedb | ||
| Description |
The update-smart-drivedb script (using version 6.3) does not quote the $SMARTCTL variable correctly in line 125 so when the path to smartctl contains whitespace execution will fail. Currently line 125 reads: if $SMARTCTL -B "$DEST.new" -P showall >/dev/null; then :; else |
|||
| #517 | fixed | Two new USB Drives (drivedb.h entries) | ||
| Description |
{ "USB: Seagate Slim Portable Drive; ", // tested with External USB Drive model SRD00F1
"0x0bc2:0xab00",
"",
"",
"-d sat"
},
{ "USB: Dynex 2.5\" USB 3.0 Exclosure; ", // tested with Model DX-HD302513
"0x1f75:0x0621",
"",
"",
"-d sat"
},
|
|||
| #518 | invalid | Is following "FIRMWARE IMPENDING FAILURE*" errors critical ? | ||
| Description |
Is following errors critical:? FIRMWARE IMPENDING FAILURE GENERAL HARD DRIVE FAILURE FIRMWARE IMPENDING FAILURE DRIVE ERROR RATE TOO HIGH FIRMWARE IMPENDING FAILURE DATA ERROR RATE TOO HIGH FIRMWARE IMPENDING FAILURE SEEK ERROR RATE TOO HIGH FIRMWARE IMPENDING FAILURE TOO MANY BLOCK REASSIGNS FIRMWARE IMPENDING FAILURE ACCESS TIMES TOO HIGH FIRMWARE IMPENDING FAILURE START UNIT TIMES TOO HIGH FIRMWARE IMPENDING FAILURE CHANNEL PARAMETRICS FIRMWARE IMPENDING FAILURE CONTROLLER DETECTED FIRMWARE IMPENDING FAILURE THROUGHPUT PERFORMANCE FIRMWARE IMPENDING FAILURE SEEK TIME PERFORMANCE FIRMWARE IMPENDING FAILURE SPIN-UP RETRY COUNT FIRMWARE IMPENDING FAILURE DRIVE CALIBRATION RETRY COUNT If an error above occurs(smartd reports it) should I replace HDD ? Or it is not possible to say it exactly and need to analyze more with special tools. I have OS Linux x86_64-linux-3.0.101(SUSE). Vendor HDD: TOSHIBA |
|||
