Cfrtjryk

I have a about 100-150 HDD and SSD's that I need to run some tests on. My servers can host up to 16 drives at a time, possibly 8-16 more if I add some more RAID cards, but either way what I need to do is find a way to test all these "older" hard drives (mechanical) or SSD's from top to bottom and in the process I need to get a detailed log of all the information from the tests so I can save it with each drive tested.

I remember being able to run a test on each hard drive (/deb/sdX) from the command line, so I could test all the drives at one time. The problem is that I can't seem to find how to get the output of these tests (short, extended, conveyance, etc).

When I run GSmartControl, I can select a drive, select "Run Tests" and then run each individually, then I save the output with a unique filename to the drive. I think there is some info missing from what is available from the command line tests. I also get the test to stall at about 85-95% for some reason (short tests so far, and a couple conveyance - haven't run extended as waiting to run them all at once if possible).

I'm currently working on my desktop with 7 drives connected -all SATA.

I would like to be able to save the results for each test, maybe identified by the drive name (like Intel 240GB SSD) and then the name of each test (short, long, conveyance, etc), they can all be in one folder and I can move them to individual ones (for each drive) later. The problem is when I run the test in the CL, it says "test will be done in 1-2 mins (for short test) and then I never see results. Is there a way I can save them to log files, or any way of saving all the tests (I know you can run all 3 at once).

If I have multiple drives, should I run tests for each drive in it's own separate command line (Bash) tab (single window, many tabs)? Or can I do it under one tab?

Another test is Badblock that I haven't used, IDK if I can run multiple tests on many drives as well with this.

badblocks is a utility for scanning bad blocks or bad sectors in hard disks. Assuming you detect any bad blocks on your hard disk, you can use it together with fsck or e2fsck to instruct the kernel not to use the bad blocks. I haven't' used these in any drives yet, I have plenty with active partitions with lots of data, so suggestions here would be appreciated.

I'd like to do a complex write up on this after I get things sorted out so if other people like me are in this situation, it is easier to find what I did and copy it, instead of searching 15-20 different locations.

Any help is GREATLY appreciated. I got started on this when a 4TB drive (99% full) stopped showing up on my system and I don't know how to salvage it (disconnected now and isolated), so I want to check all my drives and verify any that may be going bad.

Finally as far as working with hard drives and setting up partitions, I'm used to standard command line Fdisk, but have also used Gparted, KDE Partition Manger and have found the GUI's usefull in some cases where the command line is acting up for some reason. IDK if there are better tools or if any combine tools like GSmartControl & a partition/fdisk utility in one - that would seem like a nice package if it were available. Any other suggestions when it comes to these programs or GUI's?