[SOLVED] Repeated spindowns

 

Hi,

 

when copying large files to my Unraid shares, I always get repeated spindows on disk1:

 

May 7 12:32:24 Tower kernel: mdcmd (5275): spindown 1

May 7 12:33:25 Tower kernel: mdcmd (5282): spindown 1

May 7 12:34:26 Tower kernel: mdcmd (5289): spindown 1

May 7 12:35:07 Tower kernel: mdcmd (5294): spindown 1

May 7 12:35:21 Tower kernel: mdcmd (5296): spindown 1

May 7 12:35:32 Tower kernel: mdcmd (5298): spindown 1

May 7 12:36:23 Tower kernel: mdcmd (5304): spindown 1

May 7 12:37:24 Tower kernel: mdcmd (5311): spindown 1

May 7 12:38:25 Tower kernel: mdcmd (5318): spindown 1

May 7 12:39:27 Tower kernel: mdcmd (5325): spindown 1

May 7 12:40:08 Tower kernel: mdcmd (5330): spindown 1

May 7 12:40:21 Tower kernel: mdcmd (5332): spindown 1

May 7 12:40:32 Tower kernel: mdcmd (5334): spindown 1

May 7 12:41:23 Tower kernel: mdcmd (5340): spindown 1

May 7 12:42:25 Tower kernel: mdcmd (5347): spindown 1

May 7 12:43:26 Tower kernel: mdcmd (5354): spindown 1

May 7 12:44:27 Tower kernel: mdcmd (5361): spindown 1

May 7 12:45:08 Tower kernel: mdcmd (5366): spindown 1

May 7 12:45:22 Tower kernel: mdcmd (5368): spindown 1

May 7 12:45:33 Tower kernel: mdcmd (5370): spindown 1

May 7 12:46:24 Tower kernel: mdcmd (5376): spindown 1

May 7 12:47:25 Tower kernel: mdcmd (5383): spindown 1

May 7 12:48:26 Tower kernel: mdcmd (5390): spindown 1

May 7 12:49:28 Tower kernel: mdcmd (5397): spindown 1

May 7 12:50:09 Tower kernel: mdcmd (5402): spindown 1

May 7 12:50:22 Tower kernel: mdcmd (5404): spindown 1

May 7 12:50:27 Tower kernel: mdcmd (5406): spindown 1

May 7 12:50:33 Tower kernel: mdcmd (5408): spindown 1

May 7 12:51:25 Tower kernel: mdcmd (5430): spindown 1

 

 

 

Harddrves in the server are:

 

OK   parity      /dev/sda   00J_WD-WCAYY0078132

OK   /dev/md1   /mnt/disk1   /dev/hdc   SAMSUNG_HD502HI_S1VZJ1NQB06007484.74G

OK   /dev/md2   /mnt/disk2   /dev/sdb   00J_WD-WCAYY0003607

 

 

Spin up group for disk 1 is defined as 'ide1', and spinup group for disk2 is defined as 'host2'

 

 

Is that behaviour normal?