2023-11-21, 08:52 PM
(This post was last modified: 2023-11-21, 09:30 PM by Henkow. Edited 3 times in total.)
(2023-11-21, 08:29 PM)TheDreadPirate Wrote:(2023-11-21, 08:24 PM)Henkow Wrote: I did try to transcode to ramdisk instead and while I couldn't get quite far enough in the movie where it would usually freeze (before running out of ram), a new tab did load. So there must be something with the access to the SSD. I tried upgrading my SMB share to v3 and connected my PC straight to the same switch as the server, bypassing the router, to see if something would change but got the same behaviour. I have other docker containers that occasionally want to access the SSD like HA, but surely that shouldn't be noticeable?
Just to be clear, the SSD is local, right? The SSD containing your docker directory is NOT an SSD over SMB?
Oh, no. it's in the server. The SSD is only accessed by the jellyfin webclient over SMB. Btw, did these messages not indicate any sort of issue? Seemed to happen around the time the video froze.
[16:27:57] [INF] [58] Emby.Server.Implementations.Session.SessionWebSocketListener: Lost 1 WebSockets.
[16:27:45] [INF] [82] Emby.Server.Implementations.Session.SessionWebSocketListener: Sending ForceKeepAlive message to 1 inactive WebSockets.
Finally, I looked in the syslog and while everything crawls to a halt, home assistant started spitting out some warning messages so it seems like the SSD may not be able to keep up despite what the tests said.
homeassistant[3892534]: #033[33m2023-11-21 16:30:21.208 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.adguard_home_dns_queries_blocked is taking over 10 seconds#033[0m