muzo178

unlikely... it should be writing to flash. but if you enter the tail command you will see the log live on your monitor. i doubt you will get anything though. i never got anything when my box was crashing.. worth a try though..

maybe tail the log on the screen so that if an error is being logged, you can see it on the screen. tail -f /var/log/syslog

Yeah.. used to work with 6.8.3. If we can solve this, we’re golden…

did you try turning off hdr tone mapping? if you are using plex that is… with that off, it works for me.

6.8.3 was fine with hdr tone mapping. I haven’t tried jellyfin yet, I’ll give it a shot in the name of troubleshooting.

Yes, switched to official.

my box seems to be stable now after turning off vt-d. what is your cpu again? Does the hdr tone mapping option in plex work for you? mine is a j3355 (intel hd graphics 500) and it doesn’t.

these diagnostics are from 6.8.3 so MACVLAN it is.. I tried switching to IPVLAN when I upgraded to no avail. The docker fix in the go file was of course removed when I upgraded to 6.11. The modprobe thing in go vs the plugin is something i can try, but I sincerely doubt it will make a difference.. I have been trying to upgrade since 6.9, then 6.10 and finally 6.11 trying all of these permutations that you recommeded and more.. i'm stumped. one thing i still haven't tried is the official plex docker. what i will do for one last time: i will take the box out, connect it to a monitor, see if i can turn off vt-d in the bios @Tristankin upgrade to 6.11.5 switch to plex official container @ich777 switch to IPVLAN @ich777 comment out the modprobe and the docker fix from the go file and switch to using the plugins. @ich777 and pray while i915 hw transcoding anything else i should add to that list you think?

i don't think i have that option

here you go.. i'm using the linuxserver plex container xserve-diagnostics-20230214-1236.zip

unfortunately my server crashed on four separate occasions...all during plex transcodes. same story. nothing in the logs. just fell off a cliff. back to 6.8.3. i now have to accept that this little box is stuck here. it was a pita to downgrade as well since most plugins require >6.9 these days, but i had a good 6.8.3 backup and managed to downgrade properly. normally you can take out the usb and just copy the backup files over, but it is a pita as the usb is inside on the mobo of the little terramaster f5-221 unit. a simple directory fix was was good to be true anyways. oh well..

i can't believe this came down to a simple directory change. will report back in a couple days.

i just physically came back to the location with my 6.8.3 server. I'm gonna try upgrading again tomorrow. Are you still stable @Tristankin?

@ich777 i'm using the linuxserver/plex docker. can't post diagnostics as i am back on 6.8.3.

reading what you have been contributing today, i'd like to say that i am on the exact same boat with you. with all of the same baggage: no vms, ipvlan, plex transcoding i915, 683 stable, etc etc @Tristankin

i did the exact same thing last week. went from 6.8.3 to 6.11.5. started crashing during plex transcodes. reverted back last night. guess i'm stuck on 6.8.3 forever on that box.

you mean Soon™

check this.. if you have the same in your syslog, you have the same problem due to a kernel issue..

Sep 27 11:12:09 Xserve kernel: i915 0000:00:02.0: [drm] Resetting rcs0 for CS error Sep 27 11:12:09 Xserve kernel: i915 0000:00:02.0: [drm] Plex Transcoder[28979] context reset due to GPU hang Sep 27 11:12:09 Xserve kernel: i915 0000:00:02.0: [drm] GPU HANG: ecode 9:1:6978ba13, in Plex Transcoder [28979] Sep 27 11:12:16 Xserve kernel: i915 0000:00:02.0: [drm] Resetting rcs0 for preemption time out Sep 27 11:12:16 Xserve kernel: i915 0000:00:02.0: [drm] Plex Transcoder[28979] context reset due to GPU hang Sep 27 11:12:16 Xserve kernel: i915 0000:00:02.0: [drm] GPU HANG: ecode 9:1:8fd8ffff, in Plex Transcoder [28979] Sep 27 11:12:23 Xserve kernel: i915 0000:00:02.0: [drm] Resetting rcs0 for preemption time out Sep 27 11:12:23 Xserve kernel: i915 0000:00:02.0: [drm] Plex Transcoder[28979] context reset due to GPU hang Sep 27 11:12:23 Xserve kernel: i915 0000:00:02.0: [drm] GPU HANG: ecode 9:1:8fd8ffff, in Plex Transcoder [28979] Sep 27 11:12:30 Xserve kernel: i915 0000:00:02.0: [drm] Resetting vcs0 for preemption time out Sep 27 11:12:30 Xserve kernel: i915 0000:00:02.0: [drm] Plex Transcoder[28979] context reset due to GPU hang Sep 27 11:12:30 Xserve kernel: i915 0000:00:02.0: [drm] GPU HANG: ecode 9:4:cab6fff5, in Plex Transcoder [28979] Sep 27 11:12:37 Xserve kernel: i915 0000:00:02.0: [drm] Resetting vecs0 for preemption time out Sep 27 11:12:37 Xserve kernel: i915 0000:00:02.0: [drm] Plex Transcoder[28979] context reset due to GPU hang Sep 27 11:12:37 Xserve kernel: i915 0000:00:02.0: [drm] GPU HANG: ecode 9:8:cffbffff, in Plex Transcoder [28979] Sep 27 11:14:10 Xserve kernel: i915 0000:00:02.0: [drm] Resetting rcs0 for CS error Sep 27 11:14:10 Xserve kernel: i915 0000:00:02.0: [drm] Resetting rcs0 for CS error Sep 27 11:14:17 Xserve kernel: i915 0000:00:02.0: [drm] Resetting rcs0 for preemption time out got the same thing on my J3355 CPU.

I added another satellite device to my UNRAID box and now I am getting this message in the logs constantly.. Any ideas? Aug 12 14:00:16 UNRAID kernel: vhci_hcd: unlink->seqnum 108674182 Aug 12 14:00:16 UNRAID kernel: vhci_hcd: urb->status -104 Aug 12 14:00:22 UNRAID kernel: vhci_hcd: unlink->seqnum 108700222 Aug 12 14:00:22 UNRAID kernel: vhci_hcd: urb->status -104 Aug 12 14:00:28 UNRAID kernel: vhci_hcd: unlink->seqnum 108727607 Aug 12 14:00:28 UNRAID kernel: vhci_hcd: urb->status -104 Aug 12 14:00:34 UNRAID kernel: vhci_hcd: unlink->seqnum 108755739 Aug 12 14:00:34 UNRAID kernel: vhci_hcd: urb->status -104 Aug 12 14:00:40 UNRAID kernel: vhci_hcd: unlink->seqnum 108782401 Aug 12 14:00:40 UNRAID kernel: vhci_hcd: urb->status -104 Aug 12 14:00:46 UNRAID kernel: vhci_hcd: unlink->seqnum 108810661 Aug 12 14:00:46 UNRAID kernel: vhci_hcd: urb->status -104 Aug 12 14:00:52 UNRAID kernel: vhci_hcd: unlink->seqnum 108838662 Aug 12 14:00:52 UNRAID kernel: vhci_hcd: urb->status -104 Aug 12 14:00:58 UNRAID kernel: vhci_hcd: unlink->seqnum 108866563 Aug 12 14:00:58 UNRAID kernel: vhci_hcd: urb->status -104

yup, fixed. now my zigbee and rtl sdr dongle that is upstairs connected to a pi are happily and automatically humming along passed through to my hasssio VM in the basement server. thanks for this.

this is fantastic in initial testing. I am getting this in my syslog every minute though.. UNRAID usb_manager: Info: rc.usb_manager USBIP Host Check attached failed Array

+1 for this. It would be great if USB Manager could mount remote USBIP devices automatically if they are discovered. I have a couple of them set to attach automatically to the VM when they are available, but if I restart the remote host that has the USB devices plugged in, I have to manually attach them so that they then attach to the local VM. Amazing plugin btw. Keep up the good work..

Same here with a J3355 CPU.. Been following this thread for a while, but it has become very Alder Lakey

synology dsm users seem to have the same problem: https://community.synology.com/enu/forum/1/post/150054?page=3&sort=oldest