Hi there

 

These erros are appearing on my syslog every minute or so, with the disks sleeping, on my unraid 5.0beta6a:

 

May 11 10:47:08 Tower emhttp: mdcmd: write: Invalid argument
May 11 10:47:08 Tower emhttp: mdcmd: write: Invalid argument
May 11 10:47:08 Tower kernel: mdcmd (6877): spindown 1
May 11 10:47:08 Tower kernel: md: disk1: ATA_OP_STANDBYNOW1 ioctl error: -22
May 11 10:47:08 Tower kernel: mdcmd (6878): spindown 2
May 11 10:47:08 Tower kernel: md: disk2: ATA_OP_STANDBYNOW1 ioctl error: -22
May 11 10:47:18 Tower emhttp: mdcmd: write: Invalid argument
May 11 10:47:18 Tower emhttp: mdcmd: write: Invalid argument
May 11 10:47:18 Tower kernel: mdcmd (6879): spindown 1
May 11 10:47:18 Tower kernel: md: disk1: ATA_OP_STANDBYNOW1 ioctl error: -22
May 11 10:47:18 Tower kernel: mdcmd (6880): spindown 2
May 11 10:47:18 Tower kernel: md: disk2: ATA_OP_STANDBYNOW1 ioctl error: -22
May 11 10:47:28 Tower emhttp: mdcmd: write: Invalid argument
May 11 10:47:28 Tower emhttp: mdcmd: write: Invalid argument
May 11 10:47:28 Tower kernel: mdcmd (6881): spindown 1
May 11 10:47:28 Tower kernel: md: disk1: ATA_OP_STANDBYNOW1 ioctl error: -22
May 11 10:47:28 Tower kernel: mdcmd (6882): spindown 2
May 11 10:47:28 Tower kernel: md: disk2: ATA_OP_STANDBYNOW1 ioctl error: -22

 

These disks are connected to a LSI 3081E-R controller, and uses the mptsas kernel module

 

when the disks are awake, this error doesn't appear

 

is this error something serious? is there anything I can do to stop it?

 

thanks

syslog-2011-05-11.zip

It indicates your disk/disk controller does not support the IO command to spin down the drives.  (errno = 22 = invalid argument)

 

ATA_OP_STANDBYNOW1 is not supported with your specific hardware with the drivers in 5.0beta6a.

 

You can do nothing to prevent the errors other than turn off the spin-down feature built into unRAID and instead use hdparm commands to set the disk's internal hardware spin-down timers.

I see. thanks