Megaman69

The 2nd server didn't show up in the settings because it is not owned by the same account. Adding the IP or the domain to "Custom Servers" also didnt work, until I shared the 2nd server with 1st account and refreshed the token.

I got it to work. The 2 Servers are "Owned" by 2 separate Plex accounts that didn't share with each other, because they're basically twin instances. Once I shared the 2nd server to the 1st account and refreshed the token it works. Id still prefer 2 separate Plugin instances so I know which server is currently streaming, but that's more of personal preference.

OK, maybe I'm dumb, So how do I install the Plex Streams Plugin as a docker container? That's, apparently, what you are recommending I do. I already have 2 Plex Server Dockers. I have 1 Plex Streams Plugin pointed at 1 of those Plex Servers. I would like another Plugin to display the active streams on the dashboard. So from my understanding, you are saying to install the Plugin as a Docker Container.

So how is that done? I've never even heard of that before. I thought Plugins were unraid specific.

Just to be clear, I'm not talking about Plex Server, I'm talking about the Plex Streams Plugin that displays active streams on the unraid dashboard. It can only be pointed at 1 plex server, so it only shows those streams. As far as I'm aware.

Figured I would ask here first to see if this is even possible or not before asking about the specific plugin. Considering I know absolutely zero about unRAID's plugin system, I thought maybe I could just duplicate and rename the files on the USB to get a 2nd Plex Streams Plugin. I have two Plex instances, so it would be cool to have a spot on the dashboard for each. Then I can save a few clicks to see if anyone is watching before I start messing with the server. If not I can figure out another way. Use one of the homepage apps and have a widget for each or something. Thanks

I tried another UPS using SNMP and USB. Same thing, It wouldn't show anything on the settings page but in the UPS section on Dashboard there would be some information. beast-diagnostics-20221106-1751.zip

I saw this too, on 6.11.2 and 6.11.1. I thought I was just seeing stuff or something, but guess not.

Awesome. Thanks.

Hello, I've used this script before and its awesome. Thank you for sharing and helping everyone out. I am trying to get this setup again, I had to wipe my server and start over a few months ago. I am trying to have 4 Rclone remotes, all on the same team drive, just different folders within the drive. I have Rclone setup, I think I have the mount script right based off an example a couple pages back. My questions are for the upload script. 1. Do you just replicate the script for the number of mounts/remotes? basically the same as the mount script example? So for 2 mounts would you have the upload script have 2 sections, specifying the remotes and everything in "Required Settings" in each individual section of the upload script? 2. How do you handle service accounts with multiple uploads? Does Rclone know when it needs to cycle to the next account, even if it has multiple "uploads". I had it working fine before, but that was just 1 remote. Not sure if anything needs to be different for multiple remotes. 3. How does the RcloneMountIP work with multiple remotes? I was gonna set my 4 mounts up with 192.168.1.221 through 192.168.1.225. I see that the Rclone_Mount script has RcloneMountIP="192.168.1.252" and VirtualIPNumber="2", then the Rclone_Upload script has RCloneMountIP="192.168.1.253" and VirtualIPNumber="1". So I'm guessing that each Mount and each Upload needs its own individual RCloneMountIP and VirtualIPNumber? So for 4 remotes you would need 8 different RCloneMountIP= and 8 different VirtualIPNumber=, correct? 4. Is the VirtualIPNumber= similar to how unraid deals with VLANS? Will it interfere if a VLAN has the same number? Like if you have VLAN 3 then you would not want to use VirtualIPNumber="3"? Or are they different and it doesnt matter? Just want to make sure I understand. Thanks again for this awesome solution.

EDIT: I forgot this was happening before I think. I rolled back to 6.9.0 and everything was fine again. Ill try 6.9.2 and see what happens. 6.9.10 rc-2 Supermicro X10DRi-T4+ mobo, 2X Xeon E5-2699V4, 384G of ram Over the last week or so my server has started crashing. No network, no GUI, monitor output doesn't even work. I have to shut down and reboot. Last night it happened right before I was going to bed, so I just reset it and went to sleep. Next time it happens I will grab the diagnostics if I can. Because this started happening I turned on the Syslog and this is what was going on right before it crashed. I did run a memtest on this recently, over 24 hours and it didn't find anything. Is there any useful information in this? Also attached the txt file if that's easier to read. Thanks. Mar 1 22:45:38 Beast kernel: vethc4234dc: renamed from eth0 Mar 1 23:08:42 Beast kernel: DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Mar 1 23:08:42 Beast kernel: general protection fault, probably for non-canonical address 0x8aee055cbb66ac79: 0000 [#1] SMP PTI Mar 1 23:08:42 Beast kernel: CPU: 50 PID: 35661 Comm: node Tainted: P W O 5.14.15-Unraid #1 Mar 1 23:08:42 Beast kernel: Call Trace: Mar 1 23:08:42 Beast kernel: Hardware name: Supermicro PIO-648R-E1CR36L+-ST031/X10DRi-T4+, BIOS 3.1c 04/27/2019 Mar 1 23:08:42 Beast kernel: RIP: 0010:nf_nat_setup_info+0x247/0x710 [nf_nat] Mar 1 23:08:42 Beast kernel: <IRQ> Mar 1 23:08:42 Beast kernel: Code: 80 00 00 00 41 bc 01 00 00 00 48 8b 84 24 98 00 00 00 65 48 2b 04 25 28 00 00 00 0f 84 bd 04 00 00 e8 b1 29 55 e1 8a 44 24 46 <38> 42 46 74 65 48 8b 92 98 00 00 00 48 85 d2 74 0c 48 81 ea 98 00 Mar 1 23:08:42 Beast kernel: RSP: 0018:ffffc9000d0b07c8 EFLAGS: 00010286 Mar 1 23:08:42 Beast kernel: RAX: ffff88820b5f2511 RBX: ffff88b3fa995680 RCX: 000000002ffc71ff Mar 1 23:08:42 Beast kernel: ? fib_rules_lookup+0x133/0x1b6 Mar 1 23:08:42 Beast kernel: RDX: 8aee055cbb66ac33 RSI: 00000000f522ea0d RDI: ffffc9000d0b07e8 Mar 1 23:08:42 Beast kernel: RBP: ffffc9000d0b0890 R08: 0000000000000000 R09: ffff88820697fba0 Mar 1 23:08:42 Beast kernel: R10: ffff88b08f3ac388 R11: ffff8881211cd000 R12: 0000000000000000 Mar 1 23:08:42 Beast kernel: R13: ffffc9000d0b07e8 R14: ffffc9000d0b08a4 R15: ffffffff8216b040 Mar 1 23:08:42 Beast kernel: ? krealloc+0x31/0x89 Mar 1 23:08:42 Beast kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 Mar 1 23:08:42 Beast kernel: nf_nat_masquerade_ipv4+0x111/0x137 [nf_nat] Mar 1 23:08:42 Beast kernel: masquerade_tg+0x48/0x62 [xt_MASQUERADE] Mar 1 23:08:42 Beast kernel: ? fib4_rule_action+0x6c/0x74 Mar 1 23:08:42 Beast kernel: ipt_do_table+0x50d/0x5b0 [ip_tables] Mar 1 23:08:42 Beast kernel: ? mark_tg+0x20/0x20 [xt_mark] Mar 1 23:08:42 Beast kernel: ? ipt_do_table+0x563/0x5b0 [ip_tables] Mar 1 23:08:42 Beast kernel: nf_nat_inet_fn+0x101/0x1cb [nf_nat] Mar 1 23:08:42 Beast kernel: nf_nat_ipv4_out+0x15/0x8b [nf_nat] Mar 1 23:08:42 Beast kernel: nf_hook_slow+0x3e/0x93 Mar 1 23:08:42 Beast kernel: nf_hook+0xaf/0xd6 Mar 1 23:08:42 Beast kernel: ? __ip_finish_output+0x14e/0x14e Mar 1 23:08:42 Beast kernel: ip_output+0x82/0x8f Mar 1 23:08:42 Beast kernel: ? __ip_finish_output+0x14e/0x14e Mar 1 23:08:42 Beast kernel: ip_sabotage_in+0x4c/0x59 [br_netfilter] Mar 1 23:08:42 Beast kernel: nf_hook_slow+0x3e/0x93 Mar 1 23:08:42 Beast kernel: ? ip_rcv_finish_core.constprop.0+0x358/0x358 Mar 1 23:08:42 Beast kernel: NF_HOOK.constprop.0+0x72/0xcd Mar 1 23:08:42 Beast kernel: ? ip_rcv_finish_core.constprop.0+0x358/0x358 Mar 1 23:08:42 Beast kernel: __netif_receive_skb_one_core+0x79/0x9a Mar 1 23:08:42 Beast kernel: netif_receive_skb+0xa3/0xf7 Mar 1 23:08:42 Beast kernel: br_handle_frame_finish+0x35c/0x3a0 Mar 1 23:08:42 Beast kernel: ? __br_multicast_querier_exists+0x41/0x41 Mar 1 23:08:42 Beast kernel: br_nf_hook_thresh+0xc7/0xf8 [br_netfilter] Mar 1 23:08:42 Beast kernel: ? __br_multicast_querier_exists+0x41/0x41 Mar 1 23:08:42 Beast kernel: br_nf_pre_routing_finish+0x23d/0x264 [br_netfilter] Mar 1 23:08:42 Beast kernel: ? __br_multicast_querier_exists+0x41/0x41 Mar 1 23:08:42 Beast kernel: ? NF_HOOK.isra.0+0xc4/0x118 [br_netfilter] Mar 1 23:08:42 Beast kernel: ? br_handle_frame_finish+0x3a0/0x3a0 Mar 1 23:08:42 Beast kernel: br_nf_pre_routing+0x226/0x236 [br_netfilter] Mar 1 23:08:42 Beast kernel: ? br_nf_forward_finish+0xdc/0xdc [br_netfilter] Mar 1 23:08:42 Beast kernel: br_handle_frame+0x29d/0x2e5 Mar 1 23:08:42 Beast kernel: ? __br_multicast_querier_exists+0x41/0x41 Mar 1 23:08:42 Beast kernel: __netif_receive_skb_core.constprop.0+0x363/0x524 Mar 1 23:08:42 Beast kernel: __netif_receive_skb_one_core+0x42/0x9a Mar 1 23:08:42 Beast kernel: process_backlog+0xab/0x143 Mar 1 23:08:42 Beast kernel: __napi_poll.constprop.0+0x2a/0x114 Mar 1 23:08:42 Beast kernel: net_rx_action+0xe8/0x1f2 Mar 1 23:08:42 Beast kernel: __do_softirq+0xef/0x218 Mar 1 23:08:42 Beast kernel: do_softirq+0x50/0x68 Mar 1 23:08:42 Beast kernel: </IRQ> Mar 1 23:08:42 Beast kernel: __local_bh_enable_ip+0x40/0x48 Mar 1 23:08:42 Beast kernel: ip_finish_output2+0x2f0/0x341 Mar 1 23:08:42 Beast kernel: ip_send_skb+0x15/0x37 Mar 1 23:08:42 Beast kernel: udp_send_skb+0x25c/0x2be Mar 1 23:08:42 Beast kernel: udp_sendmsg+0x617/0x830 Mar 1 23:08:42 Beast kernel: ? asm_sysvec_apic_timer_interrupt+0x12/0x20 Mar 1 23:08:42 Beast kernel: ? ip_mc_finish_output+0x69/0x69 Mar 1 23:08:42 Beast kernel: ? xfrm_lookup_with_ifid+0x3e3/0x4e5 Mar 1 23:08:42 Beast kernel: ? sock_sendmsg_nosec+0x2b/0x3c Mar 1 23:08:42 Beast kernel: sock_sendmsg_nosec+0x2b/0x3c Mar 1 23:08:42 Beast kernel: __sys_sendto+0xd3/0x10e Mar 1 23:08:42 Beast kernel: ? __sys_connect+0x78/0xa2 Mar 1 23:08:42 Beast kernel: __x64_sys_sendto+0x20/0x23 Mar 1 23:08:42 Beast kernel: do_syscall_64+0x83/0xa5 Mar 1 23:08:42 Beast kernel: entry_SYSCALL_64_after_hwframe+0x44/0xae Mar 1 23:08:42 Beast kernel: RIP: 0033:0x1466a34f663f Mar 1 23:08:42 Beast kernel: RDX: 0000000000000018 RSI: 00001466a213c2f0 RDI: 0000000000000013 Mar 1 23:08:42 Beast kernel: RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000 Mar 1 23:08:42 Beast kernel: R10: 0000000000004000 R11: 0000000000000246 R12: 0000000000004000 Mar 1 23:08:42 Beast kernel: R13: 0000000000000018 R14: 00001466a213c2f0 R15: 00001466a213edb8 Mar 1 23:08:42 Beast kernel: Modules linked in: veth nvidia_modeset(PO) nvidia_uvm(PO) xt_mark xt_nat xt_tcpudp xt_comment tun macvlan xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xt_addrtype iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 br_netfilter xfs nfsd auth_rpcgss oid_registry lockd grace sunrpc md_mod nvidia(PO) ipmi_devintf ip6table_filter ip6_tables iptable_filter ip_tables x_tables bonding ixgbe mdio x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel ipmi_ssif kvm ast drm_vram_helper crct10dif_pclmul i2c_algo_bit crc32_pclmul crc32c_intel drm_ttm_helper ghash_clmulni_intel ttm aesni_intel crypto_simd cryptd drm_kms_helper rapl intel_cstate drm mpt3sas intel_uncore backlight i2c_i801 nvme agpgart tpm_tis i2c_smbus syscopyarea nvme_core raid_class tpm_tis_core sysfillrect ahci input_leds sysimgblt scsi_transport_sas i2c_core fb_sys_fops led_class tpm wmi libahci acpi_ipmi ipmi_si acpi_power_meter acpi_pad button [last unloaded: mdio] Mar 1 23:08:42 Beast kernel: ---[ end trace dc808e42f43fb756 ]--- Mar 1 23:08:42 Beast kernel: RIP: 0010:nf_nat_setup_info+0x247/0x710 [nf_nat] Mar 1 23:08:42 Beast kernel: Code: 80 00 00 00 41 bc 01 00 00 00 48 8b 84 24 98 00 00 00 65 48 2b 04 25 28 00 00 00 0f 84 bd 04 00 00 e8 b1 29 55 e1 8a 44 24 46 <38> 42 46 74 65 48 8b 92 98 00 00 00 48 85 d2 74 0c 48 81 ea 98 00 Mar 1 23:08:42 Beast kernel: RSP: 0018:ffffc9000d0b07c8 EFLAGS: 00010286 Mar 1 23:08:42 Beast kernel: RAX: ffff88820b5f2511 RBX: ffff88b3fa995680 RCX: 000000002ffc71ff Mar 1 23:08:42 Beast kernel: RDX: 8aee055cbb66ac33 RSI: 00000000f522ea0d RDI: ffffc9000d0b07e8 Mar 1 23:08:42 Beast kernel: RBP: ffffc9000d0b0890 R08: 0000000000000000 R09: ffff88820697fba0 Mar 1 23:08:42 Beast kernel: R10: ffff88b08f3ac388 R11: ffff8881211cd000 R12: 0000000000000000 Mar 1 23:08:42 Beast kernel: R13: ffffc9000d0b07e8 R14: ffffc9000d0b08a4 R15: ffffffff8216b040 Mar 1 23:08:42 Beast kernel: FS: 00001466a213e700(0000) GS:ffff88afbf900000(0000) knlGS:0000000000000000 Mar 1 23:08:42 Beast kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Mar 1 23:08:42 Beast kernel: CR2: 000014936dc15e38 CR3: 00000030cb61c004 CR4: 00000000003706e0 Mar 1 23:08:42 Beast kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 Mar 1 23:08:42 Beast kernel: DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 crash.txt

Hi, Ive been chasing this error in radarr and lidarr for a while. It started a few months ago, around september, after an update. If I run a version from last summer it works. On anything newer it starts showing this error in the logs after a couple days and refuses to start. If I delete radarr and delete its appdata, reinstall, it will work for a couple days then the error happens again. Ive asked the linuxserver guys and they have no clue. I thought that maybe I screwed up my unraid installation somehow, so I installed radarr on another machine that has unraid and completely wiped my main server to start fresh. Today I was gonna start reinstalling all my dockers on my main unraid. Went to open up radarr on the 2nd machine to take a backup to move to 1st machine. Webui wouldnt open so I open the logs and it shows the error again. Failed to create CoreCLR, HRESULT: 0x80004005. So thats 2 different unraids, 2 different machines. The 2nd machine has hardly anything on it and I just set it up recently, so its basically fresh. This is really irritating and Ive reinstalled radarr many, many times trying to figure out why it keeps doing this. Like I said, I asked in the Linuxserver forum and they dont have any idea. It looks to be a Dotnet issue, something to do with dotnet not being able to access a temp filesystem or something. This error can happen with anything that uses dotnet I guess. I am going to try the Linuxserver Alpine tag just to see what happens. I find it odd that this would happen on 2 different machines, but that its not a common widespread issue with unraid. That seems really odd to me. Im wondering if there may be some dependency Im missing or something, but I thought dockers were self contained and had everything they needed wrapped up? I really want to figure this out. It worked fine for 2 years and thenrandomly started in september after an update to Radarr. It happens with all the repositories, Linuxserver, Binhex, Hotio. Ive tried unraid version 6.9.0, 6.9.2, 6.10-rc2. I will also ask the Radarr team and see what they say, but if we can eliminate some issue with my unraid setup that works too. Like I said, its weird that it has happened on 2 unraid installs but its not all over the forums with people having this problem. I am putting this in general support intentionally because its happened across multiple unraid versions and 2 machines but I cant find anyone else using unraid that has the same issue so Im trying to figure out if Im doing something wrong in unraid that is making this happen, and I asked the linuxserver guys and they dont know. I really, really dont want to have to run radarr in windows. Ive also ran a memory test for over 24 hours without getting any errors. Thought that may be good to mention. Like I said, Ive been chasing this gremlin for a while. Thanks

Thanks for the awesome script man!! I used it yesterday to dump a Gigabyte GTX 1650 OC LP. I tried to upload it to github but it said I didn't have permission. How should I go about that or should I just PM it to you?

Don't know if you guys can help but I'm stuck at creating the service accounts. when I run python3 gen_sa_accounts.py --quick-setup 1 I get request had insufficient authentication scopes. I've enabled the drive api and have the credentials.json so not sure what's wrong. EDIT: OK, got it working with manually created service accounts. Everything worked first try and I uploaded a 4k movie. Plex playback is fine, but for movies with Atmos I use MRMC (KODI) on my shield because the plex app stutters. Within MRMC I tried to add gdrive_media_vfs/4kmovies. MRMC cannot see anything below gdrive_media_vfs if trying to add as an NFS share. It sees it with SMB and playback is fine so far, but I prefer NFS because its faster. Ill keep playing with it but if anyone has any insight please let me know. Ive gotta upload 4k Lord Of The Rings and see how the Atmos works. Also I assume it is storing the streaming movies in ram? EDIT: Thought up a couple more questions. Im not very smart so these may be dumb questions and assumptions. Is there a reason not to change RcloneCacheShare="/mnt/user0/mount_rclone" to RcloneCacheShare="/mnt/disks/cache/mount_rclone" My thinking is then it would stay completely on my 4 TB ssd cache drive. After I got it working I created a folder with midnight commander in /mnt/user/mount_mergerfs/gdrive_media_vfs/ called 4kmovies. Would it be better to change MountFolders=\{"downloads/complete,downloads/intermediate,downloads/seeds,movies,tv"\} to include other directories I want such as "4kmovies" and "4ktvshows? This wont overwrite anything each time the mount script runs? I want to start uploading 73TB this weekend so I just want to get everything right and understand how it works.