wildfire305 Posted March 30 Share Posted March 30 (edited) After updating to 6.12.9 on all three of my servers, their drives will not spin down automatically. These servers previously spun down as expected after the time-out. Two of them are used once a day and only need to spin up at that time. No configuration changes were made besides updating all plugins before upgrading. Considering downgrading one as part of the diagnosis. Is there a bug in 6.12.9 for disk sleep? Â Getting diagnostics soon... Edited March 30 by wildfire305 title more detail Quote Link to comment
wildfire305 Posted March 30 Author Share Posted March 30 cvg02 and cvg05 have been power cycled since upgrade, tonyserver has not. cvg02-diagnostics-20240329-2344.zip cvg05-diagnostics-20240329-2343.zip tony-diagnostics-20240329-2344.zip Quote Link to comment
JorgeB Posted March 30 Share Posted March 30 6 hours ago, wildfire305 said: Is there a bug in 6.12.9 for disk sleep? Not AFAIK, does downgrading resolve the issue? Quote Link to comment
wildfire305 Posted March 30 Author Share Posted March 30 The one server I was considering downgrading (cvg05) has now started sleeping on its own. That server only has an rsnapshot container running and a speed test container. The other containers are not used unless the primary server is down and they are started manually. It has no external shares and it pulls backups through ssh from other servers on the network once a day and has no external shares enabled. Nothing is able to write to it by design because it is a backup server, therefore the disks sleep after the backups complete and they stay asleep until the next daily backup. It uses a small SSD cache for appdata, domains, system. It has one VM that boots debian and displays a webpage on a monitor.  The other two servers disks remain awake and the drives are not being commanded to sleep according to the disk logs. I can usually see if I have a thing that is keeping the disks awake in the disk logs by seeing them spin up and down, but that isn't showing up. I had previously moved all highly active file activity to a always on zfs pool and the array is now just WORM policy type stuff. My array disks on both servers are only supposed to wake up during Media Streaming activity. This has been a working design for me for the six months prior to the 6.12.9 upgrade. Quote Link to comment
wildfire305 Posted March 30 Author Share Posted March 30 This is what I mean when the command to sleep the disks isn't showing up. Usually if I have something keeping the disks awake, I see a lot of "spinning down" followed by "read SMART" when the disks are awoken by the process reading files. I'm not seeing the spinning down and the reads/writes are not increasing in count. Â Â Â Quote Link to comment
Solution JorgeB Posted March 31 Solution Share Posted March 31 Try disabling and re-enabling spin down, if it doesn't do anything it suggests something is keeping the drives up, so it never tries to spin them down. Quote Link to comment
wildfire305 Posted April 4 Author Share Posted April 4 (edited) This worked on two of the three servers. I added a reboot in between disable/enable. Quote Try disabling and re-enabling spin down, if it doesn't do anything it suggests something is keeping the drives up, so it never tries to spin them down. Â The third one was resolved by watching the disks that woke up from manual spin down command with find . -mmin -30 This showed that some metadata on existing old files was being modified by an hourly rclone process. Not sure why OneDrive has started modifying metadata on files, but since it gets modified, rclone syncs the changes. If there are no changes the disks don't wake up. Edited April 4 by wildfire305 1 Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.