stanitzd

Hi! I am rocking Unraid 7 and so far it's great. I am running two pools, zfs only. One Cache (two names mirrored) and an raidz1 with 3 hdds. I come to notice, when I stream via infuse, the hdds spin down although I am still watching. So let's say an episode is about an hour, hdd spin down is set to default, the intelligent caching of zfs puts the file into ram, infuse gets the file and with no other activity, hdds spin down within the length of the episode, so that when you are about to watch the next episode (which is not in the ram cache), the spin up takes so much time, that infuse runs into a timeout and I've got to trigger the playback twice. Two possible solutions so far: - Increase timeout for spin down, which should then be at least the length of a feature film, otherwise you run into the same problem there - a script that check the log of Jellyfin for user activity and prevent spin down. Both not really ideal and I did not yet tested the second one. Does anybody experience the same problem? Are there other solutions? Is there something planned on the Unraid side to tackle this? Would love to hear your thoughts! Cheers Dan

Sorry for not testing this myself. Removing the plugin did the job. Thank you for your help and time!

Hi trurl, done! tower-diagnostics-20241204-1220.zip

Hi! I am new to Unraid and startet with the Beta 4 of Unraid 7 and just updated to rc1. Everything works as expected except the mover. I have two zfs pools, one as cache (two mirrored nvmes) and one raidz1 pool with 4 hdds. I configured a handful of shares, e.g download with cache as primary and the zfs pool as secondary. When I try to trigger the mover, the log only says "mover: cache not present, or only cache present". I can't find anymore settings to configure the mover. What am I doing wrong? As far as I understood the release notes, moving between pools without an Unraid array should be possible. Thank you in advance! Cheers, Daniel