Hi Jordi, Thanks for the quick response. On further investigation it seems the 'smartctl -a' command does wake up the drives. It pauses to wake up just before the output
SMART Error Log Version: 1 No Errors Logged So perhaps my drive does something stupid like keep the log on the disk! I changed the command to 'smartctl -A' in the application and now all is fine. Possibly not suitable for everyone though as I am not sure what section the '^Current Drive Temperature:' comes from. I have come across at least one other person with this problem so maybe you could change the command to just include the relevant sections? Now for the next step I think I will write a script to restart monitorix at night with a different configuration file that doesn't check disk space and then doesn't revert to the normal config until the drives wake up again... Regards, Mike. On 06/03/2012 10:15, Jordi Sanfeliu wrote: > Hi Mike, > > As far as I know the only part where Monitorix could wake up the disk > drives is when collecting their temperatures in the Disk graph. > > It uses the command 'hddtemp -wqn<disk_drive>' where the '-w' parameter > forces indeed the disk to wake up. Note also that this command is _only_ > used if the 'smartctl' previous command failed to get the temperature > information. > > Please, make sure if your hard drives are SMART capable, otherwise they > are probably wake up by the 'hddtemp' command line. > > So, it shouldn't have any relationship with disabling the filesystem > usage monitor. Just disable the Disk graph in /etc/monitorix.conf and > your hard drives shouldn't be wake up anymore. > > Also, Monitorix _only_ reads its configuration file when it is started. > > Please, let me know if that helped you. > Best regards. > > > > On 03/06/2012 12:27 AM, Michael Perry wrote: >> Hi, >> >> Just wondering if you can suggest a way to stop monitorix from waking up >> hard drives when they are in standby mode? I am aiming for a low power >> server and having two drives spun down saves me about 16 watts. >> >> Of course the most simple solution is to disable the filesystem usage >> monitor completely, but that would be a shame. >> >> The only idea I have come up with so far is that (assuming I remember >> correctly that the config file is parsed on every run) I could make a >> little script to change the config file depending on drive status/time >> of day. >> >> Thanks for the great software, >> >> Mike. >> ------------------------------------------------------------------------------ Keep Your Developer Skills Current with LearnDevNow! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-d2d _______________________________________________ Monitorix-general mailing list Monitorix-general@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/monitorix-general
