Oort

Hi Lovely/Cleverer peeps than me, My server started warning me that I had an invalid folder in .mnt called 'download' a few days ago; so Ive checked every single docker containers shares and I cant find one called download. Everything thats needs it is configured for the 'downloads' folder. Ive had a look at the help files and it says to post the full FCP error and the diagnostics in here. So this is what Im doing. Any ideas? I did try creating a download folder but the error still remains. unraid-diagnostics-20260502-1415.zip

Awesome. Im using direct paths. Renamed it just to be safe, all good. Deleted it all. Thanks for your help!

Thanks for the reply, to be honest Ive redone the majority of the metadata now and checking 160gb of file dates doesnt seem like a lot of fun. I assume, as everything seems to be working fine, I can just delete the files on the array?

Anybody?

As the title says, I have appdata files in three different places on my server. Its totally my fault I wasnt paying attention when doing some configuring and for some reason I cant now fathom I had the bright idea to move my appdata folder location around. At the moment I have appdata files in these location. Appdata_cache (where they should be) Array cache_VM (another cache drive) Ive sorted the cache_vm as it only had files from a redundent container in them so I deleted the folder with MC. The biggest problem I had was I lost all my my plex metadata trying to put the files back or so I thought... So, I got plex to rebuild the database from scratch and spent a few days redoing most of the custom metadata and tentatively breathed a sigh of relief. I checked the server again today and as far as I can tell the entire appdata folder is still on the array platter drives. All my dockers work fine and have checked them thoroughly so I know the current appdata folder is OK. ACTUAL PROBLEM How do I sort this? If I just tell mover to move the files back to the appdata_cache drive will it bork the new plex database? or should I just delete the appdata folder on the array completely, chalk it up to experience and never mess with the appdata share again? Thanks

Just wanted to say thanks for this thread and for anyone else that lands here. Removed the nvidia drivers, reset gpu statistics, deleted the device line from the plex config, set hardware decoding back to auto in plex app and installed Intel-TOP. Shutdown server, installed A380. Rebooted, selected A380 in gpu statistics, added the new device /dev/dri/ to plex config and selected A80 for hardware decoding in plex app. Nothing. Plex refused to use the card. What fixed it was deleting the /dev/dri/ device from plex config and adding --device=/dev/dri to the extra parameters line. No idea why that made it work as If I understand it correctly adding a new device does exactly the same thing as putting the line in extra parameters, anyway, no matter its all working beautifully now.

Hi, Yes Im aware if you put http in a file explorer window it just opens up a browser and then obviously still wont connect. \\unraid does work in a file window thats the problem. http://unraid doesnt work either in a browser it has to have the .local extension same as file explorer. Unfortunately I have already implemented the hack around for getting PC's talking to other PCs on a network I was hoping that it might of been fixed by now and obviously Microsoft dont give a proverbial...

Thanks for letting me know. One machine lets me click it but no IP the other one nothing. Guess its my hardware then.

As the title suggests it would stand to reason that theres a problem with the PC's not playing ball but thats where it gets a bit odd. I have two Unraid servers one called unraid and one called dropbox, 2 x managed network switches and three Win11 client PC's All set to DHCP and auto DNS. All network shares are set to secure and all three client PC's have users set up specifically for SMB sharing between each other and the servers. The two servers are set up with static IP's (at the moment) It doesnt make any difference if they are static or DHCP as Ive tried. SMB1 and NETBIOS are all disabled in the Clients. My router sees both servers with the correct names in DHCP config. ACTUAL PROBLEM. I can see dropbox server listed as dropbox in network section of file manager but I can only connect to the unraid server via unraid.local. If I try to connect to just http://unraid it cant find the network path. I tried renewing and flushing dns for the clients but no joy. Odd thing is all bonjour/mac settings in unraid are turned off, the network/SMB settings for both servers are identical (other than NIC brand) Ive completely killed all the network settings on the clients just in case I borked some settings but even with a clean install of NIC's with default settings the problem persists. And thats where my networking knowledge kinda peters out. Can anyone suggest anything new I can try to get this working? I have included both servers diagnostics in case there's something there that might be causing issues. Thanks dropbox-diagnostics-20250828-1448.zip unraid-diagnostics-20250828-1447.zip

Not the most time critical problem but before upgrading to 7(.1.4) my servers IP was always shown in the Dashboard header. After upgrading to 7 it disappeared and I dont know if its been removed or moved or theres a plugin I need in install to get it back? Any ideas?

I guess I spoke to soon... Removing the reserved address worked for about 7 hours and then it started acting up and producing spurious MAC addresses again. After doing a lot of googling I came across a thread about unraid producing random mac addresses and according to that it was something to do with SHIM networks. So, I checked the docker settings and sure enough for some reason 'Host access to custom networks' in the docker settings was enabled. Once I turned this off, all my problems disappeared and no more ghost MAC's or IP's for nearly 2 days now. Im fairly confident that this really is fixed now.

Have you ever spoken to virginmedia customer support? They are less than useless. As a last attempt before I give in a waste an hour phoning a tech that doesnt know what theyre talking about. I tried removing the reserved address for the server in the router and changed all the links to my dockers to unraid.local instead of the direct IP address and its bloody worked! No more ghost IP's and connecting through file manager in windows happens immediately instead of it always taking 10 seconds. So I think the issue is now fixed. Thanks for your help I doubt I would of thought to remove the reserved address without your advice.

Thanks for the reply. Only thing on the network that I wasnt able to configure was the cloudkey so Ive removed it completely. I then shut down everything, clients, server, router and switches. Waited ten mins and then restarted the router and the switches. Then booted up a client PC and ran the ip scanner again. It still lists Unraid on 192.168.0.250 with the incorrect MAC address and shows up an unknown connection on 192.168.0.237 which has the correct MAC address for the server. The unraid server is set to be the browser master so could that be an issue with it fighting with the router? Theres nothing else on the network that deals with DNS or IP's . I have 3 desktops connected, a mobile phone, a CCTV box and occasionally connect a couple of laptops,. All set to auto DHCP and IP. Its also impossible to change the IP address or DNS of the router.

Hi all, I seem to be having a rather strange problem since Ive upgraded to Virgin Media fibre where the virgin router thinks the unraid server has a different MAC address than it actually does. I also upgraded my plex server from 6.9.2 to 7.1.4 and while everything seems to be in working order I dont get the IP address of the server listed in the top right of the dashboard header menu. A quick google says that this means theres a networking issue but I cant find where and am assuming that these are caused by the same issue? The whole network is set to DHCP for IP and DNS. Everything shows up OK except the unraid server which fluctuates between the correct address and a different one. The only other things I run on the network are two managed switches which also use DHCP from the server so everything should just work yet unraid or the router is doing something odd. I have set reserved DHCP rules via MAC address (Virgin Router) for unraid and both switches. Ive also noticed that the DNS the router gives to any network attached devices in the same DNS that the router uses for the internet instead of defaulting to the gateway address (usually the ip of the router) like every other router Ive ever used for the last 20 years. Ive looked into the virgin hub 5x and they are not the best router in the world but since theyve disabled modem only mode I have to use it. I have attached the server diagnostics zip file. Any ideas? Thanks in advance. unraid-diagnostics-20250819-1247.zip