shaunvis

My server has been acting up for a couple weeks and getting worse. Almost like network dropouts, where I can't connect to the UI or watching something on Plex stutters or stops. On top of that about 2-3 times a week it totally loses up and I have to do a hard reboot. So far I can't figure out the cause. I did see errors related to Dynamic file manager but when I remove and reinstall I get this" /boot/config/plugins/dynamix.file.manager/dynamix.file.manager.txz already exists" So how you you totally uninstall a plugin, leaving nothing behind, so you can do a clean reinstall?

I'd thought about that but honestly it scares me. I'm afraid of losing everything.

I'm slowly replacing my 4 & 6TB drives with 22TB drives. I did the parity and one data drive & they each took about 2 days for the rebuild. If I used something like Unbalance to move everything off a driven then remove the old drive from the array first (taking the array down to 10 drives). Then add the new 22TB drive as a new drive (back to 11 in array) will it be any faster? Or will it still do a rebuild adding a new drive like that? Just wondering if there's a way to avoid the 2 day rebuilds every time I replace a drive.

I'm trying to replace my cache drive but can't get my data off of it first. Mover's been running for 12 hours and moved about 60GB with another 430GB to go. I tried "mover stop" and it looks like the command completes but it doesn't stop. How can I stop mover and manually move my data off the cache? Do I just use Dynamix File Manager, browse to the cache, and move things to one of the dives in the array? I know mover splits things between drives so I'm not sure if I can just put it on any drive and be OK

Thanks, that helps. I have always just use Unraid "out of the box" and didn't know that much I guess. That being said, I like the ability to match & match drives and upgrade them as needed. But you can't easily do that in a ZFS pool, correct?

I guess I'm confused by pools then. All of my data is on the array. The only pool I have is my cache drive So if I added a disk shelf, I'd basically set it up like I would my cache drives (pool) and then just use that for storage like I do my array disks? If that's the case, what's the point of the array at all? Why not just have everything be a pool? I guess I don't know the pros/cons of one or the other

So if I have 12 drives in my array and wanted to add a disk shelf with 36 (making 48 total) drives, how would I do that exactly?

Ah, so that's what broke it then. Thanks. I just found SpaceInvaders video on doing exactly this. Running mover now to get everything off cache. You'd think I'd have known better and looked into it first but nah, I'm a "What's this button do" type person and try things first, lol. thanks

I have 1 4tb cache drive formatted xfs. I added a second drive and tried adding it to the pool and ended up with "Unmountable, no file system". After removing the 2nd drive and running a repair I was able to get things back to the original state. Now I'm hesitant to try again, I don't know if I did something wrong. Before attempting again, do I want to stay XFS? Or should I use this as an opportunity to move my cache to ZFS and how do I do that? Does it matter? Using the existing xfs or zfs, how do I properly add a second drive without getting the "Unmountable" error again?

So practically speaking, Unraid Pro is NOT "Unlimited attached storage devices" like it says when you go to buy the license then. Unless for some reason you wanted to plug in dozens of USB drives? So they're just being deceptive and people like me that think they can just add a disk shelf or build a massive array can't actually do it

I"m not sure what you mean by physically connected. Does that mean if I had a SAN or something like that I could use it? My plan was to add a netapp disk shelf (24 bays) to my server (12 bays). Would that not work when connected with a SAS cable but would via network?

I kind of feel duped. I bought the Pro license because it says "Unlimited attached storage devices". The Basic and Pro clearly state the number of drives they support so I assumed unlimited meant unlimited. Now I'm finding out the limit is 28 & 2 parity drives. Is that really true or old info? If it's true, this is really a really deceptive way of selling the licenses.

Sweet! I'll get this set up Monday. Thanks!

Just to add a bit, it seems DNS related. I have issues when I add a server by name, but by IP it doesn't seem to have any trouble. Is there something special in Unraid with setting up DNS? I'm just using my OpnSense firewall for dns and haven't noticed issues with other things

I'll mess with the flash drive, thanks. But yes, on two different servers in 6.12 when I'de get the OOM, the system is totally unresponsive. Even trying to SSH into it, it would take my username, then just hang on the password until I got a timeout error. Eventually the process is killed and things work fine again

I don't know either but I had constant OOM caused by Avahi-daemon on my main server. I eventually made it go away by removing unassigned devices. I reinstalled it and was fine after that. The OOM made 6.12 totally unusable on my main server. After fixing the OOM caused by UD, I was able to finally upgrade to 6.12.4 and have been up over a week without issue. This new server is having the same behavior. Logs attached, let me know if I can do anything else to help. This is just a test system for now so I can mess with it and not care about it breaking. I do plan on making it an active server once this is resolved though hoth-diagnostics-20231010-1614.zip

That was me that posted that and it is definitely the Unassigned Devices plugin causing it, in my case anyway. I built a second server with 6.12.4 and twice now caused my system to become totally unresponsive when using this plugin. The first time I was at work so I left it for a few hours, when I tried again I was able to get back on. There was a OOM error in the logs caused by the avahi-daemon that the system finally killed and I was able to use the system again. The same process that was giving me an OOM on my main server in 6.11.5 Just a few minutes ago I caused the new server to go unresponsive again. I realized I was doing the same thing this morning. - Setting up a remote mounted SMB share. I follow the wizard, pick the server, enter username and password, I get the the "shares" section and click load shares. It looks like it's working but doesn't actually load the shares. Then the server becomes totally unresponsive. That's where I am right now on the new server, waiting for it to start working again. If I force a reboot, I'll lose the logs so I'll let it go. I fully expect to find another OOM caused by Asahi-daemon but I'll let you know for sure

Just a followup, I duplicated this on a second server. - Built a new server with 6.12.4 - It ran fine for almost a day, then hung up for hours. - When I was finally able to access it again, I had an OOM error related to "Avahi-Daemon" The only difference between this one and my main server is that this new one also had the "Unassigned Devices Plus" plugin in addition to the regular one. I'd forgotten I removed that one from my main server as well as the regular one. I reinstalled the regular one but never installed the Plus one again on my main server So I can confirm one od the Unassigned Devices plugins (regular or plus) is causing an OOM. The OOM is causing 6.12 to become totally unresponsive

TLDR: I think 6.12 is not properly handling OOM errors, causing hard locks I've had zero luck with 6.12. It always would just hang up and require a hard reboot. Then I'd downgrade back to 6.11.5 and wait for the next 6.12.x and try again, same result. The longest I'd make it is maybe an hour or two before it would lock up. I also have been having issues with OOM errors on 6.11.5 that I could never fix. I finally figured out it was the Unassigned Devices plugin causing that. I removed and reinstalled that and the OOM went away in 6.11.5. After a day of no OOM errors (I always got them within 30 minutes of a reboot and then occasionally after that) I decided to try 6.12.4 again. I've been up and running with no issues or lockups on 6.12.4 for a few days now. Before that the longest I got on 6.12 with no lockups was maybe 2 hours. So the only thing I changed was fixing the cause of the OOM error and now 6.12 runs fine it seems. It looks like 6.12 is not handeling things like OOM issues correctly (killing the offending process) and instead is letting the system go until it totally locks up. It's possible there are similar issues other people are having that are causing their lockups and system freezes. Issues that 6.11 would handle before crashing, 6.12 does not

I didn't get the swap file set up, I was reading other people that set up a swap file & the OOM just filled that up too. But your post sent me down a rabbit hole that I think FINALLY fixed my OOM errors. It looks like the "Unassigned Devices" plugin was causing avahi-daemon to eat up all my RAM until it was killed. I reinstalled it had it's been OK since. Now I'm wondering of your experience of .12 locking up from issues like that instead of showing an OOM errors in the log is what I was seeing. I might tempt 6.12 again to see if it works now.

I've actually had OOM issues on 6.11 with no apparent fix. Mine is "avahi-daemon" causing it. I hadn't found the swapfile solution or any help at all for my OOM. I'll give that a shot. If that stops the OOM in 6.11, maybe I can get 6.12 to run longer than a few hours. Thanks! I'll give that a shot

Try downgrading to 6.11.5. It's the last version that runs fine for many people

You'd think if you had to do all that just to install an update, there'd be a flashing sign, warnings, message you have to acknowledge, or maybe something to guide you through the process instead of a simple "Click to update" and then have your server crash constantly. Especially when the release notes for 6.12.4 say most of these things are no longer an issue

I'm assuming you're on 6.12, correct? If so, try 6.11.5. Lots of people, myself included can't go a day on 6.12 without it doing this exact sort of thing. Have to do a hard reboot, then it works for a little while again. I've tried each version of 6.12 and always end up back on 6.11.5 where I have no issues.

I keep searching for answers to the 6.12 issues and this is a new one. I have yet to get 6.12 run longer than a day on any version, including 6.12.4. I do tend to leave a browser open on some device or another conencted to my server. If leaving a browser open causes a server to lock up, the problem is the OS, not the browser, lol. I guess I'll stick to 6.11.5 where I don't have to worry about my server crashing if I forget to close a browser tab (which I do all the time).