@@CaelThunderwing IDESDI is not affected by the health of the drive, it relies on an odd set of heuristics based on information the controller provides about the current drive status. HDmotion is just picking up bad sectors.
It was stuck for just over a minute after 3:48 trying to obtain the parameters. HDMotion doesn't paint a pretty picture either. Barely works well enough for a demo.
@@maxtornogood As I have previously mentioned, IDESDI is not affected at all by the health of a drive. It works purely by a set of unusual heuristics based on data the controller's status register can return. What it's watching for sure write faults and attempting to detect a recalibration. These drives take a long time to recalibrate regardless of whether or not they're working.
Never knew this existed! So, this is an ST-225 technically?
Yup. This is an ST-225 with one platter and two heads removed.
@@MyComputerStudios_ Yes, this is a single platter early model ST-225.
@@leecremeans5446 Yes, but they only exist for 84 and 85, I believe.
I learned way back when that giving a good beating to those drives would make them skip the HDMotion errors.
@@VonAggelby huh? What do you mean
that drive is not happy one bit. how long it took to detect parameters, to the HDMotion Errors. it's just begging for the sweet release of death.
@@CaelThunderwing IDESDI is not affected by the health of the drive, it relies on an odd set of heuristics based on information the controller provides about the current drive status. HDmotion is just picking up bad sectors.
Totally wrong. The drive is fine. Some bad blocks sure.
@@timradde4328This.
It was stuck for just over a minute after 3:48 trying to obtain the parameters. HDMotion doesn't paint a pretty picture either. Barely works well enough for a demo.
@@maxtornogood As I have previously mentioned, IDESDI is not affected at all by the health of a drive. It works purely by a set of unusual heuristics based on data the controller's status register can return. What it's watching for sure write faults and attempting to detect a recalibration. These drives take a long time to recalibrate regardless of whether or not they're working.
You're just wrong.
@@timradde4328I agree, but there's no need to be rude