derek_zoolander

just posting to update with the solution in case anyone ends up here. It appears changing the spindown time to 30m was causing my issues. I completely disabled spindown, then moved to the default hour period and have since not had the problem anymore.

Disabled everywhere for now. I figure I can disable just for the SAS card if the problem is resolved after some testing. Now that I am thinking about it in the context of spindown, I also made some changes that my ARR stack now updates my Kodi SQL database vs. triggering an automated full library scan in Kodi itself via an addon. I made these changes b/c I noticed drives were rarely spinning down before. I can't recall if this issue started occurring around then. Anyway, got some troubleshooting to do. Will revisit the thread once I have some results to report back. Thanks for your help JorgeB!

Hmm interesting, these are split across 2 controllers (i think), the default mobo sata ports and an SAS card w/ sata breakout. What do you think, can cross controller drives cause issues like this ie (movie on the drive on the main mobo and there is a spinup request for the SAS card)? I'll try disabling spin-down for a few days and see if that resolves it.

I've been having an issue recently that I was hoping someone knowledgable could take a look at my diagnostics and help me troubleshoot. When watching a movie on a RPi 4 running kodi/osmc, every about 45m or so of playback, the movie freezes and requires hitting stop/play again to restart playback. I will get an error upon resuming the movie that says "Source too slow for continuous playback" which disappears after 5s or so and playback continues normally. However, these are 1080p files over wired gigabit ethernet which should not be a problem, also the problem only started recently. I never used to have this issue in the same ecosystem network/equipment/etc wise, and am wondering if something is up with the server itself. I may have lowered the time before a disk spins down, but I dont think this should cause it as the disk would need to be inactive in order to spin down correct? Anyway, the attached logs were grabbed the other night when watching a movie immediately after the problem occurred. Appreciate any insight the community may be able to provide. media-server-diagnostics-20240130-2149.zip

Thanks! Inadvertently, I think i may have found a container that caused this as it was spamming the log every 1s. Looks like it may have been a bad update. Ill monitor and bump the thread if the issue resurfaces.

oh, I've always left the GUI open in a browser... assuming thats bad? Server uptime at the time of issue was only 5d, ive gotten into the 50s before with no issues like this.

Hi all, Hoping someone can take a look at my diagnostics and help me understand what may have gone wrong or what happened with my server. Server was functioning properly, although a bit laggy. However, when trying to open any of the built in log viewers/consoles etc. they'd immediately crash and close. I was able to grab a screenshot of the system log before it closed out and stumbled on this thread from reddit, which running the nginx restart command from an ssh session resolved the issue. However, I am not sure what went wrong in the first place and if there is anything going on that will cause future hangups/problems. Appreciate any help from the pros who know more about this stuff. media-server-diagnostics-20231026-1041.zip

bump, anyone got any ideas?

Hello - Quick question, cant seem to find anything about this. I am trying to get my VM on unraid to put the monitor/display to sleep after 1m of inactivity. It doesn't seem to work despite the guest additions being installed. I have noticed it will sleep on the login screen, but not the main desktop. I am not talking about full VM sleep that needs to be woken up via WOL, just simple display sleep. Am I missing something?!

anyone successfully passing thru a RTX 4070 and playing on a local monitor too? I used to have my iGPU passed through and could use the locally attached monitor. Now I just get a blank screen when starting the container on the monitor. VNC works fine.

@Josh.5, I figured out the solution to this. Are you able to add /dev/snd/* to this line in your 10-setup_user.sh? device_nodes=( /dev/uinput /dev/input/event* /dev/dri/* /dev/snd/*) Adding this line enables me to use my onboard audio card

video works fine, there is just no audio

has anyone been able to get audio out to a monitor via hdmi?

Updating this - turns out the ASRock z690 pro rs mobo I am using required a BIOS update to support the additional memory past 64GB. Strange since there was no documentation of this on ASRock's site, nor anything in the BIOS update release notes indicating this functionality was added in an update.

Hmm - yeah you are right - BIOS seems to be reporting only 64gb max. Marked as solved since appears to be a mobo issue.