Solved Life experience by using sysutils/parkverbot: is it worth it?

Drives that are designed for 24/7 operation usually have long enough timeouts to not park their head ecxessively (or at all) under normal operation. Even most desktop/consumer drives usually won't park their heads when used in a ZFS pool due to the periodic commits.
The only drive that comes to mind that is problematic in this regard is the pesky WD green (at least specific generations/firmware variants). But those are total crap anyways, so just let them die...
 
Ah, I was reading the website of the port, and they mentioned the WD green. So it's really for those specific drives. It's not a general thing that could help or at least not harm on other disks as well. I see what you mean, interesting.
 
The ports says that by preventing parking the disk will last longer, parking reduces the lifetime it seems. I was not aware of this, so I thought maybe some people here already used it and had a good experience. But like sko was saying, it seems that port is indeed focusing on hard disk that do parking more then others, or that are known for it. At the end of the day, I think: why do they build hard disk that park i mean ...

The port is really specific for certain drives, I thought it was maybe beneficial for others as well...

I found this on internet:
This is fine for operating systems like Microsoft Windows, which have been tuned to leave disk drives in the idle state for as long as possible. But on Linux and RAID devices, this can have serious consequences.


intellipark



On many of these systems, disk I/O operations occur more frequently, often every 10 to 20 seconds. This means that data get read, then 8 seconds later the head gets parked, and then another 2 to 12 seconds later the actuator arm is activated again to read more data. Continually parking and activating the heads causes wear and tear, potentially leading to early drive failure.
Click to expand...
 
Ah yes, I found such behaviour in a 2017 Seagate barracuda. It would indeed unload every few seconds. I got the piece as used, no idea if that is factory default or elsewise, and it is indeed killing the drive.
It was fixed by setting camcontrol -l 192 or such in rc.local
 
You must log in or register to reply here.
Back
Top