One of my hard drives reaches 120,000 hours of operation in about a month:
$ ~/src/blkleaderboard/blkleaderboard.sh sdd 119195 hours (13.59 years) 0.29TiB ST3320620AS sdb 114560 hours (13.06 years) 0.29TiB ST3320620AS sda 113030 hours (12.89 years) 0.29TiB ST3320620AS sdk 76904 hours ( 8.77 years) 2.73TiB WDC WD30EZRX-00D sdh 66018 hours ( 7.53 years) 0.91TiB Hitachi HUA72201 sde 45746 hours ( 5.21 years) 0.91TiB SanDisk SDSSDH31 sdc 39179 hours ( 4.46 years) 0.29TiB ST3320418AS sdf 28758 hours ( 3.28 years) 1.82TiB Samsung SSD 860 sdj 28637 hours ( 3.26 years) 1.75TiB KINGSTON SUV5001 sdg 23067 hours ( 2.63 years) 1.75TiB KINGSTON SUV5001 sdi 9596 hours ( 1.09 years) 0.45TiB ST500DM002-1BD14
It’s a 320GB Seagate Barracuda 7200.10.
The machine these are in is a fileserver at my home. The four 320GB HDDs are what the operating system is installed on, whereas the hodge podge assortment of differently-sized HDDs and SSDs are the main storage for files.
That is not the most performant way to do things, but it’s only at home and doesn’t need best performance. It mostly just uses up discarded storage from other machines as they get replaced.
sdd has seen every release of Debian since 4.0 (etch) and several iterations of hardware, but this can’t go on much longer. The machine that the four 320GB HDDs are in now is very underpowered but any replacement I can think of won’t be needing four 3.5″ SATA devices inside it. More like 2x 2.5″ NVMe or M.2.
Then again, I’ve been saying that it must be replaced for about 5 years now, so who knows how long it will take me. sdd will definitely reach 120,000 hours barring hardware failure in the next month.
blkleaderboard.sh is on GitHub, by the way.