Sorry, me again. Just updated my docker setup to the latest Jellyfin but am now facing the issue that ever since I updated several days ago, my hdd is not going to sleep as it did before.
I use hd-idle to spin down my external harddrive which has everything Jellyin on it, media and configs. Worked perfectly fine before upgrading to 10.11, for several years.
After updating to 10.11 this does not work anymore, my hdd is running without any sleep and with no activity on the server. Nothing changed in how the server is used. There are no scheduled tasks running continuously. When I go to the logs in the dashboard it doesn’t record anything happening either during the times it normally would have put the hdd to sleep.
Anyone got any idea what it is or how I could narrow down what it could be that seems to keep writing on my hdd? Or is this intended behaviour of the new version?
Sorry, I have nothing to contribute to help diagnose, but I thought it was interesting I basically do the opposite. I had heard a long time ago that the hardest moments for a hard drive are the initial spin up, so I used some software I can’t remember anymore to keep the drives spinning 24/7 and never go to sleep. Might have been hd-idle, I can’t remember.
While that is still true, unless you spin them up many times a day, it’s a non-issue. Set your timeout to at least 30 minutes. Most jellyfin servers are not gonna be used fir many hours at night, for example. Or when everyone is at work/school.
These days, power is expensive for have people. If I keep my drives spinning 24/7, it’ll cost me around 150€ per year. If they spin when needed, it’ll cost me whatever percentage they are spinning, so in practice they are on for like 1-3 hours a day. So let’s say 20€ per year.
Good to know, but in my case the drives are used as a NAS, so they absolutely will be spun up multiple times a day, as i’m not the only one accessing files on them.
Multiple times a day and many times a day isn’t necessarily the same thing. Also just having a 1-2 hours long timeout might still be a viable option preventing repeated spin ups, but still allowing spin down during longer unused periods.
While probably not worth it for your particular case, it might will be for others reading this. Ideally, one could observe the access patterns for a while a find a suitable timeout setting.
That is exactly my usecase. Especially during the week the server is used only in the morning and in the evening. It is not accessible outside my home wifi either. So the drive is sleeping like 20 hours a day instead of running needlessly.
My first thought behind this was also wear of the drive but seems like that is a small issue. Cost of electricity is however another one, but to be fair I never calculated that. Might be less than in your case but still money spent on something not being used.