I have about 3000 lines of this stuff.

 

I'm doing a parity check, which is currently running. 

 

From MyMenu / SysLog - The parity check is showing no errors in the error column.  It is showing 14.6 GB total, 1.5 GB complete, 10.7% complete, 22.3 mB / sec, 0 sync errors corrected.

 

I assume that it had an issue trying to get control of the drives to do the parity or something?  It seems that it is now functioning correctly and is not finding errors.

 

Oct 25 19:41:55 Tower kernel: mdcmd (95304): spindown 9

Oct 25 19:41:55 Tower kernel: md: disk9: ATA_OP_STANDBYNOW1 ioctl error: -22

Oct 25 19:41:55 Tower kernel: mdcmd (95305): spindown 10

Oct 25 19:41:55 Tower kernel: md: disk10: ATA_OP_STANDBYNOW1 ioctl error: -22

Oct 25 19:41:55 Tower kernel: mdcmd (95306): spindown 11

Oct 25 19:41:55 Tower kernel: md: disk11: ATA_OP_STANDBYNOW1 ioctl error: -22

Oct 25 19:41:55 Tower kernel: mdcmd (95307): spindown 12

Oct 25 19:41:55 Tower kernel: md: disk12: ATA_OP_STANDBYNOW1 ioctl error: -22

Oct 25 19:41:55 Tower kernel: mdcmd (95308): spindown 15

Oct 25 19:41:55 Tower kernel: md: disk15: ATA_OP_STANDBYNOW1 ioctl error: -22

Oct 25 19:42:05 Tower kernel: mdcmd (95310): spindown 6

Oct 25 19:42:05 Tower kernel: md: disk6: ATA_OP_STANDBYNOW1 ioctl error: -22

 

I have about 3000 lines of this stuff.

 

I'm doing a parity check, which is currently running. 

 

From MyMenu / SysLog - The parity check is showing no errors in the error column.  It is showing 14.6 GB total, 1.5 GB complete, 10.7% complete, 22.3 mB / sec, 0 sync errors corrected.

 

I assume that it had an issue trying to get control of the drives to do the parity or something?  It seems that it is now functioning correctly and is not finding errors.

 

Oct 25 19:41:55 Tower kernel: mdcmd (95304): spindown 9

Oct 25 19:41:55 Tower kernel: md: disk9: ATA_OP_STANDBYNOW1 ioctl error: -22

Oct 25 19:41:55 Tower kernel: mdcmd (95305): spindown 10

Oct 25 19:41:55 Tower kernel: md: disk10: ATA_OP_STANDBYNOW1 ioctl error: -22

Oct 25 19:41:55 Tower kernel: mdcmd (95306): spindown 11

Oct 25 19:41:55 Tower kernel: md: disk11: ATA_OP_STANDBYNOW1 ioctl error: -22

Oct 25 19:41:55 Tower kernel: mdcmd (95307): spindown 12

Oct 25 19:41:55 Tower kernel: md: disk12: ATA_OP_STANDBYNOW1 ioctl error: -22

Oct 25 19:41:55 Tower kernel: mdcmd (95308): spindown 15

Oct 25 19:41:55 Tower kernel: md: disk15: ATA_OP_STANDBYNOW1 ioctl error: -22

Oct 25 19:42:05 Tower kernel: mdcmd (95310): spindown 6

Oct 25 19:42:05 Tower kernel: md: disk6: ATA_OP_STANDBYNOW1 ioctl error: -22

 

Learn to live with it.  Your disk controller driver apparently is having errors when attempting to spin down your disks. (it might not support that operation)

Does it write a new log each day or something?  This AM I see only three lines in the log.

 

jwcolby

Does it write a new log each day or something?  This AM I see only three lines in the log.

 

jwcolby

Yes the log is rotated out in the middle of the night if it is over a given size. 

The older log is re-named to syslog.1 or syslog.2 (if needed)

Where is it stored?  I would look to look at past logs.

 

jwcolby

Where is it stored?  I would look to look at past logs.

 

jwcolby

They are in /var/log

(if you have not rebooted.  It you've rebooted, they are gone)

I'm not finding a /Var under tower/flash

 

jwcolby

I'm not finding a /Var under tower/flash

 

jwcolby

That is because it is not under \\tower\flash

 

You cannot get to it via the "flash" share.

 

You can see it on recent versions of unRAID by using the following URLs:

//tower/log/syslog

or

//tower/log/syslog.1

or

//tower/log/syslog.2

 

Other than that, you must log in via telnet or on the system console and you'll find the files under

/var/log