Why is my HDD waking up?

    • This happened again but this time "smbd" was present among the processes in iosnoop.

      Source Code

      1. smbd 2911 RM 8,16 5033242544 4096 6922.81
      2. kworker/0:1H 383 WS 8,16 3905925968 28672 0.33
      3. jbd2/sdb1-62 622 FWS 8,16 18446744073709551615 0 70.79
      4. <idle> 0 WS 8,16 3905926024 4096 0.22
      5. <idle> 0 FWS 8,16 18446744073709551615 0 24.96


      I wasn't using using smb at the moment and the only other device that has access to the share is my nvidia shield tv so it must be it.
      "find /sharedfolders -amin -1" showed a bunch of random directories.


      Source Code

      1. /sharedfolders/WD-RED-Media/Serie TV/Big Mouth (2017)
      2. /sharedfolders/WD-RED-Media/Serie TV/Mr. Robot (2015)
      3. /sharedfolders/WD-RED-Media/Serie TV/Bates Motel (2013)
      4. /sharedfolders/WD-RED-Media/Serie TV/Bates Motel (2013)/Season 02
      5. /sharedfolders/WD-RED-Media/Serie TV/Bates Motel (2013)/Season 05
      6. /sharedfolders/WD-RED-Media/Serie TV/Bates Motel (2013)/Season 03
      7. /sharedfolders/WD-RED-Media/Serie TV/Brickleberry (2012)
      8. /sharedfolders/WD-RED-Media/Immagini foto video
      9. /sharedfolders/WD-RED-Media/Immagini foto video/Cellulare Ionel
      10. /sharedfolders/WD-RED-Media/Immagini foto video/Cellulare Ionel/gennaio - febbraio 2016
      11. /sharedfolders/WD-RED-Media/Immagini foto video/Cellulare Ionel/montagna marzo 2016
      12. /sharedfolders/WD-RED-Media/Immagini foto video/Cellulare Ionel/romania marzo 2016
      13. /sharedfolders/WD-RED-Media/Immagini foto video/Fotocamera Gheorghe
      14. /sharedfolders/WD-RED-Media/Immagini foto video/Fotocamera Gheorghe/capodanno 2017
      15. /sharedfolders/WD-RED-Media/Immagini foto video/Cellulare Alex
      16. /sharedfolders/WD-RED-Media/Immagini foto video/Cellulare Alex/Dicembre 2015
      Display All

      I think the reason "smbd" didn't show up ealier is because I run the iosnoop command after the drive woke up. I forgot to mention that, my bad.
      However, I'm pretty sure I have seen the drive woke up without any activity shown in iosnoop in the past, so I'm not excluding SMART yet.
    • It seems like you have some software somewhere that is indexing your media files or at least checking for updates. It could be another client on the network or some local media app. Or even a intruder hacker. ;) So it seems that your system is working just fine. If some software tries to access files on the HDD, it spins up.


      Perhaps the nvidia shield TV checks for new media. Or Emby/Plex checks for updated or new media. Check the settings...
      OMV 4, 7 x ODROID HC2, 1 x ODROID HC1, 5 x 12TB, 1 x 8TB, 1 x 2TB SSHD, 1 x 500GB SSD, GbE, WiFi mesh

      The post was edited 1 time, last by Adoby ().

    • Sorry for bothering you guys again but I'm still having this issue :( . This time with smb deactivated. iosnoop shows that this caused by "sync". Any idea what could it be?

      Source Code

      1. mmcqd/0 170 WFS 179,0 163968 4096 0.85
      2. mmcqd/0 170 WS 179,0 294912 4096 0.69
      3. mmcqd/0 170 FWS 179,0 18446744073709551615 0 0.16
      4. sync 18922 FWS 8,0 18446744073709551615 0 6970.21
      5. mmcqd/0 170 WS 179,0 3827584 32768 1.31
      6. mmcqd/0 170 WS 179,0 4351872 32768 2.00
    • Again, are there some files accessed in /sharedfolders, that may cause the drive to spin up?

      If there are, them some plugin/script/setting is causing that. Check crontab, anything strange there?

      The program sync is commonly used in timed scripts and background processes to ensure that data in caches and buffers are written to disk.

      You might even (unlikely) have been infected by a worm that tries to propagate and spread.

      What happens if you do a fresh install? Just install and update, don't add anything at all. Does the drive still spin up?

      Then add one thing after another, until you get where you are now, and check after every single step to see if that caused the random spin ups.

      And please, please report here if you find the culprit!
      OMV 4, 7 x ODROID HC2, 1 x ODROID HC1, 5 x 12TB, 1 x 8TB, 1 x 2TB SSHD, 1 x 500GB SSD, GbE, WiFi mesh
    • Hi! Update. This is what happened. First thing I noticed that the issue had a pattern: the HD was being waken up every 15 minutes. Then I noticed that even with all the components active (smb, docker, SMART, ecc.), a simple reboot was fixing the issue... for a day. The next day the issue was coming back again. I then deactivated every component one by one with a reboot and a day of waiting in between. And I finally found the culprit: the transmission docker. I simply reinstalled it and now it looks like it's all working fine. Thanks for the help!
    • FabrizioMaurizio wrote:

      I need to test this more but I think SMART was causing the disk to spin up. Anyway, I need to change the default spindown time for the hd622 (which currently is 10 minutes) to something higher like 60 minutes. I tried hdparm and hd-idle but neither of them work. Can anyone suggest a solution (changing the hd622 for something else is also an accepted solution)?
      On this matter, I bought this cheap adapter with the jms578 chipset. I flashed the firmware for the odroid HC2 and everything seems to be working perfectly!


      Source Code

      1. root@rock64:~# hdparm -C /dev/sda
      2. /dev/sda:
      3. drive state is: active/idle
      4. root@rock64:~# lsusb -t
      5. /: Bus 05.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 5000M
      6. |__ Port 1: Dev 2, If 0, Class=Mass Storage, Driver=uas, 5000M
      7. /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 480M
      8. /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=ohci-platform/1p, 12M
      9. /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci-platform/1p, 480M
      10. |__ Port 1: Dev 2, If 0, Class=Mass Storage, Driver=usb-storage, 480M
      11. /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=dwc2/1p, 480M
      12. root@rock64:~#
      Display All

      Source Code

      1. root@rock64:~/JMS578FwUpdater# ./JMS578FwUpdate -d /dev/sda -v
      2. Bridge Firmware Version: v173.1.0.2
      3. root@rock64:~/JMS578FwUpdater#
      Changing the drive spindown time using the GUI also works but a full power cycle is needed for changes to be applied. I'm very pleased with this thing.
      Images
      • s-l1600.jpg

        39.24 kB, 800×800, viewed 15 times
    • FabrizioMaurizio wrote:

      I need to test this more but I think SMART was causing the disk to spin up. Anyway, I need to change the default spindown time for the hd622 (which currently is 10 minutes) to something higher like 60 minutes. I tried hdparm and hd-idle but neither of them work. Can anyone suggest a solution (changing the hd622 for something else is also an accepted solution)?
      Again on this matter, I tried flashing the firmware for the cloudshell2 on the hd622 and as expected it didn't work since the cloudshell2 has the JMS561 chip and the hd622 has the JMS561u chip. However, changing the spindown timer using the jms561fwupdater worked just fine.


      Source Code

      1. ./JMS561FwUpdate -d /dev/sda -t 30

      "hdparm -C /dev/sda" still doesn't work: it returns "drive state is: standby" even if the drive is active. Can anyone tell me what are the implications of this?
    • Users Online 1

      1 Guest