It's still not even close to being a concise article. The only real metric there being discussed is simply age?

Maybe the SSDs moved 100x the data in their much shorter age so far? That would mean a lot and change the outcome significantly.

@StorageNinja said in RAID rebuild times 16TB drive:

@scottalanmiller said in RAID rebuild times 16TB drive:

Its a system, not an IO, bottleneck typically. Especially with RAID 6. Its math that runs on a single thread.

Distributed storage systems with per object raid FTW here. If I have every VMDK running it's own rebuild process (vSAN) or every individual LUN/CPG (how Compellent or 3PAR do it) then a given drive failing is a giant party across all of the drives in the cluster/system. (Also how the fancy erasure code array systems run this).

Yeah, that's RAIN and that basically solves everything 🙂

Looking at this as a replacement.

https://www.amazon.com/Sabrent-External-Lay-Flat-Docking-EC-DFLT/dp/B00LS5NFQ2/ref=sr_1_3?ie=UTF8&qid=1483744282&sr=8-3&keywords=sata+drive+dock&refinements=p_72%3A2661618011

0_1483744609542_716LhfU8+VL.SL1500.jpg

ahhhhhhhhh there we go - thank you guys

@Katie said:

I knew a guy who used to pull the clicking drive and pop it in a freezer for 30 minutes. Sometimes it worked.

3 years ago I had to do this for a client. I was able to retrieve 30%. And had to freeze multiple times.

For testing I'd go with the manufacture tools, but to exercise the drive and possibly help it help itself.. I'd run a level 4 scan with Spinrite.