I just found this thread dealing with the same thing. I noticed that all 8 of my disks were spun up all the time. If I manually spun them down, they'd all spin back up a few seconds later. Checking the log I'd see something like this:
Mar 22 14:28:21 Jasmine emhttpd: spinning down /dev/sdh
Mar 22 14:28:21 Jasmine emhttpd: spinning down /dev/sdg
Mar 22 14:28:21 Jasmine emhttpd: spinning down /dev/sdd
Mar 22 14:28:21 Jasmine emhttpd: spinning down /dev/sde
Mar 22 14:28:21 Jasmine emhttpd: spinning down /dev/sdb
Mar 22 14:28:21 Jasmine emhttpd: spinning down /dev/sdf
Mar 22 14:28:21 Jasmine emhttpd: spinning down /dev/sdc
Mar 22 14:28:21 Jasmine emhttpd: spinning down /dev/sdi
Mar 22 14:28:30 Jasmine emhttpd: read SMART /dev/sdb
Mar 22 14:28:34 Jasmine emhttpd: read SMART /dev/sdf
Mar 22 14:28:35 Jasmine emhttpd: read SMART /dev/sdg
Mar 22 14:28:39 Jasmine emhttpd: read SMART /dev/sde
Mar 22 14:28:39 Jasmine emhttpd: read SMART /dev/sdc
Mar 22 14:28:55 Jasmine emhttpd: read SMART /dev/sdh
Mar 22 14:28:55 Jasmine emhttpd: read SMART /dev/sdd
Mar 22 14:28:55 Jasmine emhttpd: read SMART /dev/sdi
I don't think it's related to Mover. Mover was on an hourly schedule but this happens consistently after I spin down the drives. I switched mover to a daily schedule and the same thing happens.
I don't have any active streams or file handles to some of these drives, some of them are completely empty yet they're still spinning up.
Some of these drives are plugged right into the motherboard's SATA ports, others are plugged into a cheapo Marvell 88SE9215 card.
It definitely used to spin drives down, so something has changed likely on my end that I've done but I can't see anything that would cause drives to be kept "awake". My spin down idle time is 30mins and even an hour after the SMART reads the drives are still spinning and nothing new is in the syslog. I suspect the SMART reads are a red herring and that's just happening when the drive spins up but what is causing them to spin up I simply don't know.
EDIT: As soon as I posted this, I think I figured out the issue on my end was Turbowrite. It seems determined to spin up all my drives no matter how many are actually active so I've disabled it for now and it seems to have calmed down. I'll monitor on my end.
6.9.2 RC2 "Read SMART" spins up the same 2 disks throughout the day
-
-
-
-
-
in Prereleases
Posted · Edited by Kushan
I just found this thread dealing with the same thing. I noticed that all 8 of my disks were spun up all the time. If I manually spun them down, they'd all spin back up a few seconds later. Checking the log I'd see something like this:
Mar 22 14:28:21 Jasmine emhttpd: spinning down /dev/sdh Mar 22 14:28:21 Jasmine emhttpd: spinning down /dev/sdg Mar 22 14:28:21 Jasmine emhttpd: spinning down /dev/sdd Mar 22 14:28:21 Jasmine emhttpd: spinning down /dev/sde Mar 22 14:28:21 Jasmine emhttpd: spinning down /dev/sdb Mar 22 14:28:21 Jasmine emhttpd: spinning down /dev/sdf Mar 22 14:28:21 Jasmine emhttpd: spinning down /dev/sdc Mar 22 14:28:21 Jasmine emhttpd: spinning down /dev/sdi Mar 22 14:28:30 Jasmine emhttpd: read SMART /dev/sdb Mar 22 14:28:34 Jasmine emhttpd: read SMART /dev/sdf Mar 22 14:28:35 Jasmine emhttpd: read SMART /dev/sdg Mar 22 14:28:39 Jasmine emhttpd: read SMART /dev/sde Mar 22 14:28:39 Jasmine emhttpd: read SMART /dev/sdc Mar 22 14:28:55 Jasmine emhttpd: read SMART /dev/sdh Mar 22 14:28:55 Jasmine emhttpd: read SMART /dev/sdd Mar 22 14:28:55 Jasmine emhttpd: read SMART /dev/sdiI don't think it's related to Mover. Mover was on an hourly schedule but this happens consistently after I spin down the drives. I switched mover to a daily schedule and the same thing happens.
I don't have any active streams or file handles to some of these drives, some of them are completely empty yet they're still spinning up.
Some of these drives are plugged right into the motherboard's SATA ports, others are plugged into a cheapo Marvell 88SE9215 card.
It definitely used to spin drives down, so something has changed likely on my end that I've done but I can't see anything that would cause drives to be kept "awake". My spin down idle time is 30mins and even an hour after the SMART reads the drives are still spinning and nothing new is in the syslog. I suspect the SMART reads are a red herring and that's just happening when the drive spins up but what is causing them to spin up I simply don't know.
EDIT: As soon as I posted this, I think I figured out the issue on my end was Turbowrite. It seems determined to spin up all my drives no matter how many are actually active so I've disabled it for now and it seems to have calmed down. I'll monitor on my end.
jasmine-diagnostics-20210322-1538.zip