I periodically get access errors for a specific spinning
disk that I have done these things to diagnose:
Changed Sata Cable
Switched Sata bus on MB
Run E2fsck on the 3 formatted ext4 partitions w/ no errors found
Run smartctl -a: all results within norms
Run smartctl -t short: No errors found
Di
jbk wrote:
> I periodically get access errors for a specific spinning disk that I have
> done these things to diagnose:
> Changed Sata Cable
> Switched Sata bus on MB
> Run E2fsck on the 3 formatted ext4 partitions w/ no errors found
> Run smartctl -a: all results within norms
> Run smartctl -t sh
Assuming that the drives are good, you might be hitting the standby
problem. So-called "green drives" park their heads and go into standby
mode very quickly (a set of Western Digital Green series drives I have
park after 8 seconds idle). It can take a long time (tens of seconds)
for them to spin up
On 12/17/23 13:44, Dan Ritter wrote:
jbk wrote:
I periodically get access errors for a specific spinning disk that I have
done these things to diagnose:
Changed Sata Cable
Switched Sata bus on MB
Run E2fsck on the 3 formatted ext4 partitions w/ no errors found
Run smartctl -a: all results within
jbk said on Sun, 17 Dec 2023 10:13:36 -0500
>I periodically get access errors for a specific spinning
>disk that I have done these things to diagnose:
>Changed Sata Cable
>Switched Sata bus on MB
>Run E2fsck on the 3 formatted ext4 partitions w/ no errors found
>Run smartctl -a: all results withi
