February 13, 201016 yr I'm running the initial release of 4.5 with 6 drives and have this really strange issue with my single 1T Seagate drive. I often get sets of spindown messages for that drive (and can hear it do so) My default spin down delay is set to 30 minutes but I have log entries like this: Feb 13 14:54:47 NAS2 kernel: mdcmd (364374): spindown 3 Feb 13 14:55:17 NAS2 kernel: mdcmd (364379): spindown 3 Feb 13 14:55:31 NAS2 kernel: mdcmd (364383): spindown 3 Feb 13 14:56:02 NAS2 kernel: mdcmd (364388): spindown 3 Feb 13 14:56:15 NAS2 kernel: mdcmd (364392): spindown 3 What the heck could be causing this? (syslog attached as I know that nothing happens without a syslog) Thanks for your thoughts! syslog-2010-02-13.txt
February 13, 201016 yr Author Followup Information: I just noticed that it seems to be most common after I use the myMain page in unmenu. The link I'm using is: http://tower:8080/myMain?sort=num&view=default I find that doing a refresh seems to wake up the drives and try to put them back to sleep or something. I do not know if this is intended behavior of unmenu. It is trying to get temperatures, which I thought some people said that the drives had to spin up to do that. Just wondering out loud until a more knowledgeable guy comes by.
Archived
This topic is now archived and is closed to further replies.