February 17, 201610 yr I am debugging an issue with my setup at the moment which is only affecting my Main Server and not my Backup Server. I THOUGHT I had resolved the issue with a switch replacement (which seemed to have everything solved for 48 hours - see here: http://lime-technology.com/forum/index.php?topic=46668.msg445940#msg445940) BUT when I get home tonight the stability issue is there again! I have combed the syslog of previous days and todays and spotted something that I have not seen before relating to the drives I have as my Cache Pool: Feb 17 05:42:03 main emhttp: shcmd (84): /usr/sbin/hdparm -y /dev/sdb &> /dev/null Feb 17 05:42:03 main emhttp: shcmd (85): /usr/sbin/hdparm -y /dev/sdc &> /dev/null Feb 17 07:00:48 main kernel: mdcmd (82): spindown 1 Feb 17 07:09:16 main kernel: mdcmd (83): spindown 2 Feb 17 07:10:37 main kernel: mdcmd (84): spindown 4 Feb 17 07:11:33 main emhttp: shcmd (86): /usr/sbin/hdparm -y /dev/sdb &> /dev/null Feb 17 07:11:33 main emhttp: shcmd (87): /usr/sbin/hdparm -y /dev/sdc &> /dev/null Feb 17 07:12:18 main kernel: mdcmd (85): spindown 6 Feb 17 08:51:38 main emhttp: shcmd (88): /usr/sbin/hdparm -y /dev/sdb &> /dev/null Feb 17 08:51:38 main emhttp: shcmd (89): /usr/sbin/hdparm -y /dev/sdc &> /dev/null Feb 17 09:17:49 main kernel: mdcmd (86): spindown 4 Feb 17 10:31:44 main emhttp: shcmd (90): /usr/sbin/hdparm -y /dev/sdb &> /dev/null Feb 17 10:31:44 main emhttp: shcmd (91): /usr/sbin/hdparm -y /dev/sdc &> /dev/null Feb 17 11:42:51 main kernel: mdcmd (87): spindown 3 Feb 17 11:43:22 main kernel: mdcmd (88): spindown 0 Feb 17 11:43:23 main kernel: mdcmd (89): spindown 6 Feb 17 11:53:49 main kernel: mdcmd (90): spindown 5 Feb 17 12:00:07 main kernel: mdcmd (91): spindown 2 Feb 17 12:00:08 main kernel: mdcmd (92): spindown 4 Feb 17 12:00:44 main emhttp: shcmd (92): /usr/sbin/hdparm -y /dev/sdb &> /dev/null Feb 17 12:00:44 main emhttp: shcmd (93): /usr/sbin/hdparm -y /dev/sdc &> /dev/null Feb 17 13:41:54 main emhttp: shcmd (94): /usr/sbin/hdparm -y /dev/sdb &> /dev/null Feb 17 13:41:54 main emhttp: shcmd (95): /usr/sbin/hdparm -y /dev/sdc &> /dev/null It seems that emhttp is executing something that is not user driven. It seems to happen when I am at work or asleep and it is happening repeatedly? There is literally nothing else in the logs that would be of any concern at all AFAIAC. My question is two fold and concerns the :emhttp: shcmd (95): /usr/sbin/hdparm -y /dev/sdc &> /dev/null command .... 1) Could this be causing my GUI to be unstable and or unresponsive (emhttp is doing something when I am not looking) AND if so 2) What is this command doing? Any insight would be gratefully received.
February 17, 201610 yr That command is trying to "spin down" or get the device to enter low power mode.
February 17, 201610 yr Author That command is trying to "spin down" or get the device to enter low power mode. Thanks. Can't be that then. Sigh. Issue has to be my network then. Server seems absolutely fine. I think I am getting close to testing / replacing cables.
February 17, 201610 yr Author That command is trying to "spin down" or get the device to enter low power mode. Actually when you say "trying" is it being successful. I am noting that when the other drives "spin down" noting of course these are SSD's the log entry is ... spindown x But with these drives in the log is the hdparam code? Is that significant?
February 17, 201610 yr I'm not sure on why this is different to the other drives, I just looked at the man page for hdparm.
February 21, 201610 yr Author Well. This is definitely a case of No Fault Found. There has been no issue since I posted last. No required reboots. No instability. No actable log entries. No clue.
Archived
This topic is now archived and is closed to further replies.