Haldanite

Had the same happen to me. Server hung on a line saying that it could not open file /boot/config/plugins/disklocation/disklocation.conf: No such file or directory... - I booted into safe mode - started the array - installed the plugin from the link listed on the first page - I then went into the plugin and to the System tab - under System clicked on Force Update All. It then created the missing conf file. - I rebooted the server and the error was gone and it booted normal.

Thanks. I was just updating while you were typing this. Looks like it is working.

Well, it looks like it is working so I think I'm fine.

After the reboot I saw it downloading like you said. However, when I go into Plex settings now I don't have the ability to select my video card for Hardware Transcoding. It only gives me the option of Auto.

Thanks. No AdBlocker on my network and I'm not running any Unifi network equipment either. I'm in the middle of transferring some files, but I'll give it a reboot and monitor it on my screen. The box is connected directly to my Asus Router. Here's hoping everything works out.

Issue with upgrading to v6.12.8. I received this alert and not really sure what to do about it other than follow the instructions and post the screenshot..

If this is in the wrong place please feel free to move it. I've been using unraid since 2018 and have loved it since day 1 compared to the old Transparent Raid system I used before. I wanted to share a recent experience I've had that may or may not be an issue for someone. I've had 0 issues running my servers with the flash drive in the onboard USB 3 slot for years now. Well either because of the BIOS update or the OS update all of a sudden I was having issues with the flash drive booting up and right away disappearing in unraid. I tried many things including moving it to other USB 3 ports and still the issue persisted. Windows would say that there was an issue with the drive when I plugged it in and so I would allow Windows to "fix it", but the problem would remain and the drive would once again disappear upon booting the system up. I even got to the point that I replaced the drive so my original is now blacklisted, but still the problem would persist. Fast forward to a few days of lost sleep messing with this and going crazy as it would occasionally work and then stop working after a reboot. I realized that all of the ports except for 2 on the front of my PC were USB 3. I moved the flash drive to the USB 2 port in the front and all of a sudden everything worked fine like it had for years. This got me to the point where I remembered seeing something about seeing USB 3 compatibility issues with unraid, but since it was never an issue for me I just eliminated it as the problem. Guess between either the MB firmware update or the OS update or the combo of both it has now become an issue. All is now well with a couple of USB 2.0 ports installed to the USB 2.0 MB header. I ended up having to also move my UPS to the other port because it too had stopped communicating on the same USB 3 port that it has used for years. If you ever run into a problem with the USB after some updates then save yourself a few sleepless nights and make sure you are using a USB 2 port even if the USB 3 had worked before. I just want to say thanks to the community here because if it hadn't been for some similar posts about unraid not liking USB 3 I think I might still be trying to figure out why the server isn't working. This is a great product and an awesome community! Thanks to everyone that spends time trying to help others here.

Been running stable on the rollback to 6.10.3 for almost 3 weeks now. Today just got a Fix Common Problems warning to upgrade to 6.1.1.5; that's not going to happen again.

Been on the latest BIOS and running UNRAID 6.10.3 for almost 2 days now without issue. I'm not really seeing much of difference between version 6.10.3 and 6.11.5 between the two servers. It looks a little different, but I haven't seen anything on the newer version that made me say, "I must upgrade my primary server to have that!". Think I'll just stay on 6.10.3 on my main server for now.

This has me thinking that there might be a common denominator with the MB. The BIOS on my ROG STRIX X470 is version 5220 from 9/12/2019. There have been several updates since this version and nothing specifically noting any issues with the system fans shutting down, but it might be worth trying to update to the latest BIOS version 6042 and upgrading UNRAID back to 6.11.5 and see what happens. Not really a fan of knowing that my system shuts down due to hitting high temps; really don't want to do that to many times.

My server just started doing this 2 days ago. I had no idea why the server shutdown until just a few minutes ago. I was in the room and working on a VM and all of a sudden it got quiet. I looked over and the fans had stopped, but the server was still running. I watched as the temps started climbing and just rebooted it from the GUI before it shut itself down. Not sure if it's related, but this is only happening on my main server which was recently upgraded to 6.11.5 and has an Asus ROG STRIX X470-F Gaming board with AMD Ryzen 7 2700X, 32GB DDR4. I've not changed any of the hardware in months. I just rolled back to 6.10.3. I've been running 6.11.3 and recently 6.11.5 on my secondary server without issues. An Asus M5A97 LE R2.0 with AMD FX 6300 and 16GB DDR3 without any issues.

Mine just started doing this 2 days ago. Had no idea what happened until I was sitting in the room and all of a sudden it went quiet. All the fans just stopped. I watched as the temps rose until I decided to just reboot the system instead of letting it get too hot.

Actually, you got me thinking and I went back in to the switch and found that when I setup Jumbo frames I must not have finished the configuration. I set it again and rebooted the switch and I think I'm good to go now. I've mapped a few other shares and so far so good. It seems to be working both directions now. Thanks a ton!

I've tried to configure the servers to do this, but not entirely sure if it is working since it was something I was just trying out. Both servers are setup with the NIC having desired MTU at 9000. Do you think I should drop this back down? Edit: Both are running with Gigabit NIC's and I'm using an old enterprise switch that we retired at work. Catalyst 2960-S

It's really odd though. Both boxes are currently sitting right next to each other while I'm getting the backup box ready. They are both on the same network switch and I've had no issue copying 11.5 TB of data from the primary server over to the backup server over the network. I've also noticed that once I try to connect to one of the mappings and it fails I have a very hard time unmounting the drive. It gets to the point that in some cases the only option is to hard reboot the server since none of the shutdown commands actually work to shut it down.

No, both are currently always on with no power save settings enabled.

homeserver-diagnostics-20191113-2158.zip unraidbackup-diagnostics-20191113-2159.zip

What's odd is that I tried to setup a new test share on one of the servers and created a few test documents there and that seems to work. I was able to click the link on the main tab and it opened right up to show me the test files.

Sorry, still a bit new to this. I've pulled the diagnostics files from both servers, but not sure how to post them. They created zip files with several folders and files inside them.

I've been trying this so many different ways and I'm just not sure what I'm doing wrong. I have 2 unraid servers with one being a backup of the other. What I'm trying to do at this time is mount a SMB share from Server 2 on Server 1. I've selected SMB as the share type when setting it up. I've let the system find the server which it does no problem. I enter a username and password for an account (set the same on both servers). I leave the domain empty. I enter the share name just like it shows under shares. I click Add. Then I click on MOUNT and the first time it looks like it mounts no problem, but when I click the link for the mount point the screen just sits there loading and never shows the files or folders in the share. I've let it sit there trying to load for over an hour as a test and it never does. When I go back to MAIN the mapped share shows SIZE 0 B and USED 0 B. If I try to unmount the share it takes a long time trying and sometimes it does it and sometimes it doesn't. Based on some other posts I've seen from online searches I've even tried going into the Unassigned Devices settings and set Force all SMB remote shares to SMB v1? to Yes on both servers. I even rebooted both servers just to eliminate possible issues there. Nothing seems to work. The issue is the same if I try to do the same from Server 1 to a share on Server 2. Any guidance would be greatly appreciated.

I'm very new to unraid and I was trying to follow this video from Spaceinvader One on setting up virt-manager, but when I get to the part about editing the libvirtd.conf file I find that I don't have the folder etc/libvirt at all. I've tried searching online and I'm just coming up with nothing. Can anyone point me in the right direction? I'd really appreciate the help. Thanks in advance.

Hello, I just switched to unRAID from Transparent RAID and I'm noticing this error blowing up my log. I'm completely new to Linux so I'm at a loss. I've tried searching the forum and I've seen a few people mention the same error inside other posts, but nothing that I can find answering what it is or how to fix it. I'm hoping that maybe a specific post on the error might be able to help get an answer. I'm attaching a pic of the error. Any help would be greatly appreciated.