Tip: drive refuses to be imaged when connected internally
April 10th, 2009, 3:34
I had a few drives that didn't like to be imaged when connected directly to the controller. To make this more fun, I have an assortment of controllers. The drives would start imaging, hit a bad block, and stop the process.
When troubleshooting, that manifests itself as drive starts to scan OK in MHDD, hits a block, and then goes offline. A powercycle is then necessary to bring it back online. Skipping past that point scans the drive with no problems.
What I found is that I can often bypass that particular problem by connecting the patient drive through a USB adapter that is dumb enough to ignore the instruction to power down the drive. Several drives got imaged this way with no issues. Sometimes ignorance is pure bliss.
One such adapter is the Coolmax CD-350.
When troubleshooting, that manifests itself as drive starts to scan OK in MHDD, hits a block, and then goes offline. A powercycle is then necessary to bring it back online. Skipping past that point scans the drive with no problems.
What I found is that I can often bypass that particular problem by connecting the patient drive through a USB adapter that is dumb enough to ignore the instruction to power down the drive. Several drives got imaged this way with no issues. Sometimes ignorance is pure bliss.
One such adapter is the Coolmax CD-350.
Powered by phpBB © phpBB Group.