In a previous post , I was trying to understand why my FS was regurlary corrupted. It was said that I could be caused by an unsupported sleep mode, but I didn't look further.
Now, I noticed another issue : the hard-drive correctly go to sleep mode after a 10 minutes or by issuing the command 'hdparm -y /dev/sda', but it awakes by itself, without any reason (no access to the hard drive at that time).
I couldn't find the reason of that... It seems to occur event if the system is totally disconnected from the network.
For information, I'm running OMV3 (yeah, I know, it's beta, but I want to run on Debian 8 ) on an Odroid XU4 installed with DietPi (based on Debian 8). I'm not sure that this issue is directly linked to OpenMediaVault, but I think that there are a lot of experts out there that could help me. The OS is running from an SD card, and the hard-drive is a Lacie external hard drive connected on USB 2.
I've read the Guide to debugging disks spin up with no success : hdparm -C /dev/sda always return the state "standby" (even if it is actually running), so, this script cannot detect the drive spinning up.
I've monitoried dmesg when the drive restarted, but I didn't see any messages about sda, only READ/WRITE blocks on mmcblk0p2.
In the man page of hdparm, I found the param '-Z', that is supposed to disable automatic power saving modes for some Seagate hard-drive. The reference "ST3xxx models" is mentionned. When I saw that, I thought it should solve the issue, as my hard drive is a Seagate ST3500820AS. I ran hdparm -Z /dev/sda but it still spins up automatically.
Here are some more information about the hard drive:
I don't know how to diagnose further this issue. I'm looking for new ideas