I have a whole bunch of hard drives (maybe 10 or so) from a variety of sources that I'd like to test. If they work, I will put them in use and/or give them away. I was going to simply open up one of my machines and plug each one in, one at a time, and troubleshoot from there. Is there a way (or set of tools) that I can use to make this process easier and/or faster?
|
feedback
|
|
I usually put a batch of drives into an Internet-connected spare computer, then go through the steps below. Note that if you have multiple drives hooked up at the same time, it's a lot easier to identify which one you're working with if you just make sure not to hook up two of the same model. Of course, you can also identify the drives based upon the order in which they're hooked up, but it's brain-dead simple if the drives are all different models.
If you want, you can open up a separate terminal for each drive and run the bad block scans in parallel, so you don't have to keep checking on the status of one drive before moving onto the next. Depending on the sizes of your drives, you may need to let the scan run overnight anyway. | ||||
|
feedback
|
|
If they are SATA drives, then they are hotpluggable. So just find a PC where you can insert and remove harddrives from the front cover (without opening it up). This would make the insertion/removal process a lot faster. Other than that, get a thing to check the SMART status and if the SMART says it's not in horrible condition, then do a full format of the drive. If it has any bad sectors afterwards, then it is most likely bad. Modern harddrives' firmware have extra sectors that get mapped to bad sectors when they are first detected as bad. So, if the OS is seeing bad sectors, that means a lot of sectors are already bad, which means, it doesn't have much life left. | |||
|
feedback
|
|
Drive testing takes a while. You could create a script that would prompt you to connect a drive and hit enter, then does a 'badblocks' check (or whatever drive-checking software you want to run) on that drive, then beeps to alert you to disconnect the drive and connect the next drive. You could have the script prompt you for a drive name or number and record all the results. I suppose you could also (if you have the necessary connectors and hubs) connect all the drives at once via USB SATA or PATA adapters and then have a script find and test them all, possibly in parallel. I'm not sure what limit(s) you might hit there. I've never tested more than one drive at a time. | |||||
feedback
|