hawihoney Posted October 30, 2018 Share Posted October 30, 2018 Whenever a disk spins down, this activity is written to syslog. E.g. Oct 30 15:29:13 Tower2 kernel: mdcmd (101): spindown 1 Whenever a disk spins up, this activity is not written to syslog. Please add this activity too. Thanks. Quote Link to comment
itimpi Posted October 30, 2018 Share Posted October 30, 2018 5 minutes ago, hawihoney said: Whenever a disk spins down, this activity is written to syslog. E.g. Oct 30 15:29:13 Tower2 kernel: mdcmd (101): spindown 1 Whenever a disk spins up, this activity is not written to syslog. Please add this activity too. Thanks. Spindowns are easy to handle when they are software triggered. I do not think they are logged when the spindown happens at the drive level without being initiated from software. I am not sure that spin-ups generate events that can be logged. It may even be handled at the hardware level and not even visible at the software level. I would love to be proved wrong, though, as having spinups logged would be useful for investigating certain issues. Quote Link to comment
hawihoney Posted October 30, 2018 Author Share Posted October 30, 2018 I do have those issues since 6.6.3. All drives spin up together many times a day. I did remove all plugins to test, without success. I did remove all Dockers to test, without success. I do see the system and/or emhttp to hang for a minute or so. After that all disks are spun up. Usually my systems run for months. Since 6.6.3 I'm rebooting daily. Perhapsa spinup log entry would help. 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.