TimV

I have a problem with binhex_plex not recognizing all my music files. I'm running 2 Unraid systems and this appears to be only happening on system #2, but I'm afraid to remove and re-add for fear of them not coming back. Both systems running the latest version of Unraid (6.12) and binhex_plex docker. System #1 - Music was loaded over a year ago and seems to have no problems. This would imply there is nothing wrong with the mp3 files themselves or the naming format. It could be possible, Plex changed since I added the files, but I use the same naming convention for all my music so I wonder how it could be fine for some and not others. System #2 - I noticed earlier this year some of my music was not listed in Plex. I did the folder listing and the folder was present from within Plex. No issues accessing the files from the OS. Here is a list of debugging steps I took, all of which did not work. - I copied the files out of directory and then back in. - I checked and updated the mp3 metadata. - Renamed Directory and mp3 files. - Various shut-downs of Plex docker and Unraid itself. - Created new Library with different path and copied files into it. - Installed the binhex plexpass docker and it wouldn't show up there. - Removed all plex dockers, did a rm -rf in the appdata directories and re-installed binhex-plex. - note: this made it worse. Now, only 5% of my music is showing up. The scan files operation finishes really quickly. I'm at a loss as I've used Plex and these files (as is) for the last 6-7 years with no issues at all. I thought nuking them and starting over would remove any corruption problems that might be occurring. The scan files operation seems to be passing right over them.

Unassigned Disks (UD) shares are no longer showing up on MacOS (10.15.7) or WIndows 10. This started before I upgraded from 6.11.1 to 6.11.5 so I think it's related to UD. For the last year, I've had no problem with UD shares (I have no problems seeing actual share directories) and then one day they magically disappeared. I've rebooted both my mac and unraid server multiple times. I've gone in and unshared them, hit apply and then re-did the share. My /etc/exports directory has them listed. I think it's something related to UD because Windows can no longer see them , either so it's not just a Mac thing. I have the latest version of UD which is dated for 3/3/23. Note: I have no problems accessing these disks from the Unraid server, so it looks like the mount is good, but the network component is hosed. SOLVED: I guess 'enable SMB Security' got changed in the UD settings or functionality changed. I set if from 'off' to 'Public' and my shares showed up again.

This may sound stupid, but how do I use this? I don't see any instructions in the project other than how to get your GitHub token, which I got. I start the docker, get into the console and have no idea what to run to make this work. I went thru the posts hoping I'd see a similar post, but to no avail. Any guidance on getting started would be appreciated. Thanks.

That was the problem. I saw it earlier when I was fiddling with my settings, but wasn't sure. It works like a champ now. THanks.

I had a VM (Windows 10) I could connect to via RDP with no problems and when I upgraded my motherboard, I'm no longer able to do so. After reconfiguring the VM to start, I can only connect thru VNC. The VM still has network and internet access. but has a strange IP address. Instead of having a 192.168.0.x IP, it has a 192.168.122.x address. If I try to use that IP address, it will not connect to RDP. When I view RDP settings in the VM, they are are unchanged from before. It says I should be able to connect by its name (Proteus). Any suggestions as to why this is no longer working? I went into device mangler and updated the network drivers, no dice. I can mount devices that host on my unraid server, but am unable to mount any non-unraid network storage to the VM. Any suggestions?

Thanks. I was trying to use a ASUS Z590-A and was not able to boot. The suggestions in this thread helped me to get it to boot, however, it wants to do an Intel network boot first despite the USB being first in the chain.

Yes, that is what it was. I have no idea why it turned on because I wasn't using in 6.10. Everything works now.

I'm thinking it might've turned Wireguard on and set it to autostart. I went back to 6.10.3 and everything worked again. I'm trying upgrade again.

Upgrade to 6.11.1 breaks DNS. I cannot change anything in the networking section of settings. Attached is my diag output. neptune-diagnostics-20221016-1030.zip

Everything was working fine, but after upgrade, my box cannot access the internet. I can login locally via network, but it can't communicate. OpenVPN reports DNS error, my Fix Common Problems pops up saying i have DNS problem, but I can't find it. Unraid itself cannot communicate back to GitHub. i'm good on intranet activity, but not internet. Attached is the output of my diagnostics run. I'm about to restore back to 6.10.3. I ran the pre-upgrade check and it passed on everything. neptune-diagnostics-20221016-1030.zip

I'm trying to use AzireVPN. I downloaded the config file, uploaded it to Wireguard. When I switch to advanced mode, I see their server name in there. VPN tunneled access is the type I'm trying to setup. I can ping their server from the config screen. When I activate it, the "last handshake" line shows inactive connection. When I leave the screen and go back in, it's inactive. I must be forgetting something fairly basic, yet I'm seeing anything in this thread, It might be there and I just don't recognize it.

I've got an old LG-NAS (L2B2 or similar) that works fine with Windows and MacOS but I cannot mount on unRAID 6.8.3. When going thru the GUI, it just does nothing when I try to mount it. No logs, nothing so I opened up a shell window. When I try to mount from the command line, I get: root@Neptune:/mnt/remotes# mount -t nfs LG-NAS:/volume1_public /mnt/remotes/LG-NAS mount.nfs: requested NFS version or transport protocol is not supported So, I tried nfs version 3... same thing. root@Neptune:/mnt/remotes# mount -vvvv -t nfs -o vers=3 LG-NAS:/volume1_public /mnt/remotes/LG-NAS mount.nfs: timeout set for Thu Mar 4 09:15:53 2021 mount.nfs: trying text-based options 'vers=3,addr=10.0.0.13' mount.nfs: prog 100003, trying vers=3, prot=6 mount.nfs: portmap query retrying: RPC: Program not registered mount.nfs: prog 100003, trying vers=3, prot=17 mount.nfs: portmap query failed: RPC: Program not registered mount.nfs: trying text-based options 'vers=3,addr=10.0.0.13' mount.nfs: prog 100003, trying vers=3, prot=6 mount.nfs: portmap query retrying: RPC: Program not registered mount.nfs: prog 100003, trying vers=3, prot=17 mount.nfs: portmap query failed: RPC: Program not registered mount.nfs: trying text-based options 'vers=3,addr=10.0.0.13' mount.nfs: prog 100003, trying vers=3, prot=6 mount.nfs: portmap query retrying: RPC: Program not registered mount.nfs: prog 100003, trying vers=3, prot=17 mount.nfs: portmap query failed: RPC: Program not registered mount.nfs: requested NFS version or transport protocol is not supported root@Neptune:/# rpcinfo 10.0.0.13 program version netid address service owner 100000 2 tcp 0.0.0.0.0.111 portmapper unknown 100000 2 udp 0.0.0.0.0.111 portmapper unknown I tried to mount with nfs version 2... root@Neptune:/# mount -vvvv -t nfs -o nfsvers=2 LG-NAS:/volume1_public /mnt/remotes/LG-NAS mount.nfs: timeout set for Thu Mar 4 09:33:32 2021 mount.nfs: trying text-based options 'nfsvers=2,addr=10.0.0.13' mount.nfs: prog 100003, trying vers=2, prot=6 mount.nfs: portmap query retrying: RPC: Program not registered mount.nfs: prog 100003, trying vers=2, prot=17 mount.nfs: portmap query failed: RPC: Program not registered mount.nfs: trying text-based options 'nfsvers=2,addr=10.0.0.13' mount.nfs: prog 100003, trying vers=2, prot=6 mount.nfs: portmap query retrying: RPC: Program not registered mount.nfs: prog 100003, trying vers=2, prot=17 mount.nfs: portmap query failed: RPC: Program not registered mount.nfs: trying text-based options 'nfsvers=2,addr=10.0.0.13' mount.nfs: prog 100003, trying vers=2, prot=6 mount.nfs: portmap query retrying: RPC: Program not registered mount.nfs: prog 100003, trying vers=2, prot=17 mount.nfs: portmap query failed: RPC: Program not registered mount.nfs: requested NFS version or transport protocol is not supported No dice. Anything left for me to try?

You got this working? I have same MOBO but with B460 chipset and i had to use 6.9.rc2 for it to recognize my onboard NIC.

Is there some kind of roadmap that shows where unRAID wants to go at a high level? We used to get those once a year from IBM when dealing with Netezza.

ST8000VN004-2M2101_WKD32TB8-20210212-2308.txt