|
This was a real suggestion but either you don't want to hear it or simply don't know how to use it :
if SMART triggered or something happened there must be a reason , so a COMPLETE DIAGNOSE must be done.
Example : one head is physically damaged during drive activity due to bump or structural failure, in the time before the drive becomes unstable there is time to try reallocation of "bads" (not really bads, only the head could not read it) and maybe trigger SMART, but the drive is unstable.
Would you reset SMART in this case with a non completely working head ? No wonder you get an error because the drive was unable to init SMART data with other damage too.
Of course the question would have been pointless if you know how to get data regardless of SMART status, overcoming the problem. But don't pretend to repair a car with only a screwdriver = to do miracles with terminal commands only. So the answer is NOT to fiddle with commands on unstable drive UNLESS YOU ARE 10000000000% SURE about the drive condition and what the problem is.
|