I don't have 'lots of splitters', but I do have a couple of drives connected with an old style power connector adaptor to a new style SATA power connector. I honestly can't remember if this drive is connected with such an adaptor, and will have to take the server apart to find out for sure. The server has 8 120mm fans connected to the power supply (5 to one power connector, and 3 connected to another). if that matters. The server runs very cool, so I can disconnect at least 3 of the fans without issue, i'm sure.
I stopped SABnzbd from running while I ran the preclear on only on drive, so preclear should have been the only thing running on this server all night. Below are the results, which show sectors still needing re-allocation. this drive is a few years old, and had served as my cache drive for the last couple of years. It is out of warranty so there is no RMA available.
so, do I throw the drive away, even though is hasn't actually failed, or preclear again, or put it into the array, and be aware that it's likely to fail in the near future, and get a replacement ordered and precleared to be ready the day it does fail on me???
== invoked as: ./preclear_disk.sh /dev/sdk
== SAMSUNG HD103UJ S13PJDWS337885
== Disk /dev/sdk has been successfully precleared
== with a starting sector of 64
== Ran 1 cycle
==
== Using :Read block size = 8225280 Bytes
== Last Cycle's Pre Read Time : 3:13:07 (86 MB/s)
== Last Cycle's Zeroing time : 2:58:54 (93 MB/s)
== Last Cycle's Post Read Time : 7:15:07 (38 MB/s)
== Last Cycle's Total Time : 13:28:07
==
== Total Elapsed Time 13:28:07
==
== Disk Start Temperature: 26C
==
== Current Disk Temperature: 25C,
==
============================================================================
** Changed attributes in files: /tmp/smart_start_sdk /tmp/smart_finish_sdk
ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE
Airflow_Temperature_Cel = 75 74 0 ok 25
Temperature_Celsius = 76 74 0 ok 24
No SMART attributes are FAILING_NOW
[b]10 sectors were pending re-allocation before the start of the preclear.[/b]
11 sectors were pending re-allocation after pre-read in cycle 1 of 1.
0 sectors were pending re-allocation after zero of disk in cycle 1 of 1.
[b]9 sectors are pending re-allocation at the end of the preclear,
a change of -1 in the number of sectors pending re-allocation.[/b]
0 sectors had been re-allocated before the start of the preclear.
0 sectors are re-allocated at the end of the preclear,
the number of sectors re-allocated did not change.