munit85

This just solved a problem I've been having periodically. I was experiencing the 'bad time' from using an IP. thanks

to update. not solved, but I seem to be having mDNS errors. if I connect via IP address it loads fine. If I try to load via my server name plex-pc it takes a few tries and has all the sluggish behavior. I have lots of mdns entries in my log as well as dockers not being able to download their icons. So basically its something wrong with my network.

Agreed. A rollback fixed the problem for me as well. thanks for the hard work Binhex, we appreciate it.

I tried visiting unraid with edge, vs my normal firefox and it seems to load fine. Seems its just a problem on my end.

I pulled any errors or warnings from my system logs. the mdns issue does seem interesting, not sure what to do about it though. Oct 22 17:37:10 Plex-PC kernel: ACPI: Early table checksum verification disabled Oct 22 17:37:10 Plex-PC kernel: pci 0000:01:00.0: BAR 9: failed to assign [mem size 0x00400000 64bit] Oct 22 17:37:10 Plex-PC kernel: pci 0000:01:00.0: BAR 7: failed to assign [mem size 0x00040000 64bit] Oct 22 17:37:10 Plex-PC kernel: floppy0: no floppy controllers found Oct 22 17:37:10 Plex-PC kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.PRT0._GTF.DSSP], AE_NOT_FOUND (20220331/psargs-330) Oct 22 17:37:10 Plex-PC kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.PRT0._GTF due to previous error (AE_NOT_FOUND) (20220331/psparse-529) Oct 22 17:37:10 Plex-PC kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.PRT0._GTF.DSSP], AE_NOT_FOUND (20220331/psargs-330) Oct 22 17:37:10 Plex-PC kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.PRT0._GTF due to previous error (AE_NOT_FOUND) (20220331/psparse-529) Oct 22 17:37:10 Plex-PC kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.PRT2._GTF.DSSP], AE_NOT_FOUND (20220331/psargs-330) Oct 22 17:37:10 Plex-PC kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.PRT2._GTF due to previous error (AE_NOT_FOUND) (20220331/psparse-529) Oct 22 17:37:10 Plex-PC kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.PRT5._GTF.DSSP], AE_NOT_FOUND (20220331/psargs-330) Oct 22 17:37:10 Plex-PC kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.PRT5._GTF due to previous error (AE_NOT_FOUND) (20220331/psparse-529) Oct 22 17:37:10 Plex-PC kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.PRT4._GTF.DSSP], AE_NOT_FOUND (20220331/psargs-330) Oct 22 17:37:10 Plex-PC kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.PRT4._GTF due to previous error (AE_NOT_FOUND) (20220331/psparse-529) Oct 22 17:37:10 Plex-PC kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.PRT2._GTF.DSSP], AE_NOT_FOUND (20220331/psargs-330) Oct 22 17:37:10 Plex-PC kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.PRT2._GTF due to previous error (AE_NOT_FOUND) (20220331/psparse-529) Oct 22 17:37:10 Plex-PC kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.PRT4._GTF.DSSP], AE_NOT_FOUND (20220331/psargs-330) Oct 22 17:37:10 Plex-PC kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.PRT4._GTF due to previous error (AE_NOT_FOUND) (20220331/psparse-529) Oct 22 17:37:10 Plex-PC kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.PRT5._GTF.DSSP], AE_NOT_FOUND (20220331/psargs-330) Oct 22 17:37:10 Plex-PC kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.PRT5._GTF due to previous error (AE_NOT_FOUND) (20220331/psparse-529) Oct 22 17:37:10 Plex-PC kernel: i915 0000:00:02.0: [drm] failed to retrieve link info, disabling eDP Oct 22 17:37:14 Plex-PC mcelog: failed to prefill DIMM database from DMI data Oct 22 17:50:09 Plex-PC root: Fix Common Problems: Other Warning: Background notifications not enabled ** Ignored Oct 23 04:30:07 Plex-PC root: Fix Common Problems: Other Warning: Background notifications not enabled ** Ignored Oct 23 06:56:46 Plex-PC avahi-daemon[820]: *** WARNING: Detected another IPv4 mDNS stack running on this host. This makes mDNS unreliable and is thus not recommended. *** Oct 23 07:15:50 Plex-PC nginx: 2022/10/23 07:15:50 [error] 5348#5348: *501968 connect() to unix:/var/tmp/compose_manager_action.sock failed (111: Connection refused) while connecting to upstream, client: 192.168.1.134, server: , request: "GET /logterminal/compose_manager_action/token HTTP/2.0", upstream: "http://unix:/var/tmp/compose_manager_action.sock:/token", host: "plex-pc:11443", referrer: "https://plex-pc:11443/logterminal/compose_manager_action/"

Sure seems like iowait is the culprit based on these right? I'll try updating my bios tonight. I assume some iowait is normal, but not 30% plus? //edit - I take that back. that was while 2 vm's were running and for whatever reason the disk images were on the array, those 2 drives that were being used plus the 2 cache drives. Let me try this again with the domains in my cache pool

Hello everyone, Unraid 6.11.0 rolled back from 6.11.1 no change I'm having trouble in the following ways. main page takes up to a minute for the drive information to populate dashboard page also has this loading lag, as well as a lag in loading the processor usage information When i click to see the log of a docker (any docker) the page pops up, blank, waits maybe 20 seconds and closes. It will work after several tries When I update a docker, the update panel shows up, but no progress is shown. if i esc out after a minute or so it will have updated the docker, just not given me the information attempting to stop the array will either take a very long time or just hang and never stop entirely. This has happened twice. It seems that unassigned devices has the hardest time loading. It shows the loading wave the longest without actually finding anything. These problems happened when i tried to stop the array and it hung on unmounting the drives. since then it has acted oddly. Please advise, thank you plex-pc-diagnostics-20221022-1349.zip

well i did what you said and it worked. no errors to be found. Ordered a different drive as a backup, but either reseating or updating to the beta fixed it. thanks so much

hmm just checked and errors returned. attaching new diagnostics jefflix-diagnostics-20200829-1919.zip

testing now. Flash now reads append nvme_core.default_ps_max_latency_us=0 initrd=/bzroot,/bzroot-gui I'll report back with what happens later today. thanks //edit it's been hours and so far all is well. If it doesn't have issues by tomorrow I'll consider this solved.

Hi all. experiencing some crashing. My dockers died and vm's died. logs show continuous errors. Aug 28 06:48:07 Jefflix kernel: print_req_error: I/O error, dev loop2, sector 180736 Aug 28 06:48:07 Jefflix kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 0, rd 4050, flush 0, corrupt 0, gen 0 The rest of the array seems to be online and fine. and the vm's show "One or more paths do not exist" I also already deleted my docker image and recreated it. that worked for a few hours, but the next day it was in this error state again. log attached. jefflix-diagnostics-20200828-1633.zip

have you tried this:

That seems to have done it. I'm running 3 streams without problem. Sent you some beer money. Thanks for all your work with unraid.

unraid version: 6.7.2 nvidia (problem has occured in vanilla back into 6.6.x days) plugins: dynamix cache, ssd trim, stop shell, system buttons, temp. nerd tools for perl recycle bin unbalance unassigned devices hardware: amd 3600 on asus rog b450 -f board 32GB ram lsi sas9211-8i card going to a super micro backplane 846 24-bay unit This has occured on my old hardware as well which was an intel dual xeon setup. I've also swapped lsi cards with an h200 flashed to IT mode with the same results My cache drive has also changed between 2 SSD's and now an nvme drive 500GB Problem: When I run mover it locks up my system somewhat. cpu usage spikes around 50% and I cannot get files to load/play correctly in plex until moving stops. It is highly repeatable regardless if the files I'm trying to watch are on the cache drive or on the array already. I've not seen any specific errors in the log while mover is running. This diagnostic is from a fresh restart and me moving mover until completion. thank you for the help - Jeff jefflix-diagnostics-20190713-1503.zip

emby blacklisted jell* on their apps so none work with jellyfin. There's an android app and androidtv app. roku is super rough so far. not sure what else is up. reddit.com/r/jellyfin has more info