Hello there
I want to reduce the consumption of my server and so, to reduce access to hard drives

But I suspect mdadm to access the drives frequently and wake them up.

Because even when the drives are not mounted, they wake up frequently and I can't find the reason.

Because the are not mounted, it's not due to a process.

I've temporarily disabled smartd so it's not that.

remains the software raid, who can potentially do regular checks, if that's the case how to fix it?
?

ps: I know spin down/up isn't good

all 5 comments

sorted by: hot top controversial new old
[–] 4 points 4 months ago

mdadm --stop /dev/mdX should at least tell you whether or not mdadm is causing the spinning.

  • source
  • [–] 3 points 4 months ago* (last edited 4 months ago)

    You can try and figure out what's accessing the array:

    fatrace | grep /mnt/mountpoint/

    This will show you the process, type of access (read, write, open, etc), and path. If you don't see anything right away just leave it running for a bit.

  • source
  • [–] 2 points 4 months ago

    Never had mdadm causing that. I have a raid5 array that's used only for backup once a day and it is mounted 24/7, and the disks are off for 23hba day more or less ...

  • source
  • [–] 1 point 4 months ago

    Get an anti-hero to protect the data thieves?

  • source
  • [–] 1 point 4 months ago

    I have 2x it hdd's in software raid with mdadm which I use as my backup storage. My server mounts the array, writes the backup, unmounts the array, spins down the disks and puts them to sleep completely automatically every night at 1am. They never wake or spin up at all during the day.

  • source