February 5, 20242 yr 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 Edited February 5, 20242 yr by derek_zoolander
February 5, 20242 yr Community Expert There are a few drives spinning up: Jan 30 21:50:05 Media-Server emhttpd: read SMART /dev/sdi Jan 30 21:50:15 Media-Server emhttpd: read SMART /dev/sdh Jan 30 21:50:21 Media-Server emhttpd: read SMART /dev/sdj Jan 30 21:50:24 Media-Server emhttpd: read SMART /dev/sdk Jan 30 21:50:32 Media-Server emhttpd: read SMART /dev/sde Jan 30 21:50:40 Media-Server emhttpd: read SMART /dev/sdf Depending on the controller it can block all reads until they all spin up, so from 21:50:05 until approximately 20:50:45
February 5, 20242 yr Author 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. Edited February 5, 20242 yr by derek_zoolander
February 5, 20242 yr Community Expert Addon controllers are usually more prone to this, onboard not as common, so could be the SAS card, try disabling spin down to test, for all or just the disks on the SAS controller.
February 5, 20242 yr Author 1 minute ago, JorgeB said: Addon controllers are usually more prone to this, onboard not as common, so could be the SAS card, try disabling spin down to test, for all or just the disks on the SAS controller. 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!
February 19, 20242 yr Author 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.
July 17, 20241 yr Author bumping this back up because it appears the issue has returned. Fresh diagnostics from two occurrences right after the issue presented. Not sure what is happening, but its really frustrating. media-server-diagnostics-20240709-2251.zipmedia-server-diagnostics-20240716-2149.zip
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.