Writing zeros takes the same amount of time as reading the drive but is much more comprehensive. It's a bad technique if you're trying to validate a drive as fully functional. This is a good technique if you are trying to recover data and there's a bad sector interfering. All the software does is to read the whole disk and write zeros to any bad sector it finds. Just write a sector and the firmware does the rest. The firmware on the drive is where the magic happens and no special software is required to make it work. Error correction is not magic performed by the software. There's no reason the software can't run on other brand drives other than to annoy the user. Since there are only 8760 hours in a year isn't that 171 years? ![]() I still trust SCSI, median average failure time 1.5 million hours! What's your longevity record for consumer grade IDE and SATA drives. There were three or four newish drives with the "click of death", the heads refusing to park properly.įortunately there was a 750GB with less than 1000 hours, two 250GB drives with no faults, one Seagate 250GB with one error that I corrected, a working 160GB laptop SATA drive, and surprisingly a couple of those skinny Maxtor IDEs which had big hours but no faults. There were several newish drives with I guess bad logic boards as the drive was not detected at all. Some of the drives with unfixable media faults had hours as low as 1800. Most of the drives had POH hours between 500. ![]() Since WD and Samsung only evaluate defects, which Seatools does already, why bother?Īt any rate the POH (powered on hours) was very interesting to me. It evaluates any manufacturers drives, and allows error correction on Seagate (and Maxtors made by Seagate) drives. The best tool by far was Seagate's Seatools for DOS. I downloaded all the Drive Tools I could find from Seagate, Western Digital, Samsung, Hitachi and Maxtor. Two posts in two days - must be losing my mojo.I recently bought a box of 20 plus hard drives, a mixture of IDE and SATA. Before you ask me, "Why didn't you wipe it in the old computer, idiot?", it's because the optical drive had been harvested from the old clunker. I'm going to put the drive back in the old computer and see what the status is. There was NEVER a password needed for booting when the hard drive was in the old PC. Is it the act of changing the computer the drive was in causing the locking? I'm pretty confused. I don't know if I have two different things going on here (Boot & Nuke failure) AND the freeze locking or both the same. Rebooted again and still can't wipe it with Boot & Nuke from UBCD. Ran SEATools and it's NOT locked this time. One time, I let the PC start up and got to the Boot Options Menu, unplugged the power from the Seagate drive, plugged it back in and chose to boot from the UBCD in the optical drive. I tried turning off the PC and restating - same situation. However, once it is frozen, it remains locked until a power cycle or hardware reset." I read this article and specifically this line: "The drive can be frozen by the BIOS, the OS, or possibly a software application. Running all these tools from the UBCD 5.1.1 ![]() SEATools tells me that the drive is Security Freeze Locked. Boot & Nuke kept erroring out when I tried to wipe the drive. ![]() I put it into my utility computer (HP a1310n) on which I do this kind of thing. So, all I wanted to do was take this drive out of an old computer and wipe it using Darik's Boot & Nuke.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |