Looks like they are already at 7sec?
$ sudo smartctl -l scterc /dev/sdb
smartctl 7.2 2020-12-30 r5155 [x86_64-linux-5.13.4-1-MANJARO] (local build)
Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org
SCT Error Recovery Control:
Read: 70 (7.0 seconds)
Write: 70 (7.0 seconds)
$ sudo smartctl -l scterc /dev/sdc
smartctl 7.2 2020-12-30 r5155 [x86_64-linux-5.13.4-1-MANJARO] (local build)
Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org
SCT Error Recovery Control:
Read: 70 (7.0 seconds)
Write: 70 (7.0 seconds)
And this brings up 2 more other HD thoughts:
- how would I check for and change write caching on the drives… I’m assuming having write caching disabled would be a better option in case of crash (preserving data integrity at the cost of speed)… or maybe this is an old idea that might not be as relevant in GNU/Linux as it was in Windows?
EDIT: Well look at that… it’s anotherhdparm
command/parameter…
$ sudo hdparm -W /dev/sdb
/dev/sdb:
write-caching = 1 (on)
$ sudo hdparm -W /dev/sdc
/dev/sdc:
write-caching = 1 (on)
- In one of my other posts the discussion evolved to adjusting APM settings on the mechanical drives to
254
(or255
if they support it) but I thought I would reserve looking into that for this discussion (deciding how the drives would be attached first; SATA versus HBA)… would you have a recommendation for APM settings?
$ sudo hdparm -B /dev/sdb
/dev/sdb:
APM_level = 164
$ sudo hdparm -B /dev/sdc
/dev/sdc:
APM_level = 164