glave

Could a breaking change happen recently? I can no longer access via reverse proxy. If I try the web page comes up slowly, and when you try logging in a generic 'Something went wrong' error happens. Access through the WebGUI link is working flawless, but using NPM seems broken somehow. I don't really see anything in the container logs so I'm not sure where to begin.

LSI 9300-16i in IT mode? That's in containerUnraid and is what the drives will attach to. Would that be ok?

That's not really what I'm doing here. I'm taking the drives out of an existing Unraid server and attaching to a different existing Unraid server. This existing server has a lot of containers already running on it.

Would it? I'm not moving the flash drive at all. The existing disks in dockerUnraid's array are not a priority at all. They are just two 300gb 2.5" disks with no data. This is purely about getting diskUnraid's drives reconnected without losing data from the original array on diskUnraid.

I have two Unraid servers, one is filled with storage and the other mostly doing container things. For ease of reference, I'll call them diskUnraid and dockerUnraid. dockerUnraid only has 2 drives in it's array, and they are empty. The primary stuff happening there are pool devices and containers. I'm converting diskUnraid to be a DAS, and dockerUnraid will be using those drives now. I know I will need to first destroy the array on dockerUnraid but I'm wondering on how I bring in the drives from diskUnraid and keep the data intact. Do I just populate them all inside dockerUnraid in the exact same drive assignments they had in diskUnraid? Will parity (I have dual) be destroyed?

I have a Norco 4220 case and an old i7, but I also have a HP DL380 Gen10. What options do I have to to use the HP as compute but attach the 20 HDDs to it? I'm currently running unraid on both and using fileshares to access the HDDs but I feel this is a bit less than ideal.

Between my two servers I have one that isn't behaving the same with display. I'm trying to set both of them to 'small' but on one server it reverts back to 'normal' every time I hit Apply. Once upon a time I had the theme engine plugin, but that has been removed from both servers. Is there something I can reset or check that could be keeping the font size setting from sticking?

Unfortunately they don't work in some situations, although I haven't tracked down the specifics yet. I have a 50GB minimum set on each share, yet I still have a few disks than continue to fill up past that without triggering warnings.

Has anyone created a script that can parse the log file looking for a string and then send a notification using unraid's notification system? I'd like to search for "No space left on device" in the log file, just wondering if something similar may already exist before I reinvent the wheel.

Rebuilding both parity at the same time makes sense, but wouldn't replacing both data disks at the same time cause data loss? I thought if I lose/remove more than 1 data drive at once then I lose data?

My current parity drives are 12TB and I've got two 14TB on the way. I'll be swapping the 14TB drives in as parity, removing two 4TB drives and replacing them with the 12TB drives that are currently parity. What is the easiest/fastest order of operations that I can achieve this? Right now I'm thinking it will take 4 parity rebuilds to pull this off, which will take a very long time.

I recreated the USB with stable release, copied over the config directory and restored the key. I was able to use the 64gb drive that I bought, but I'm not sure if there will be some consequence (?) later since the maximum is stated at 32gb.

Also just noticed on the download page that a 32gb drive is the max? The replacement I got was 64gb. Is it possible to use this at all?

What is the workflow to move over? I used the USB creator tool and then copied over all the files from the old drive, but when it attempts to boot I keep getting Failed to load COM32 file menu.c32 boot: A few more details- My drive died last night right after upgrading to 6.10rc2 and it was doing it's reboot. I tried to use the USB creator tool and told it to use 6.10rc2 but it appears that something is broken with that option, as the tool erases the drive, pauses, then closes the program without warning. No files are put on the drive. I knew this wasn't correct, so I tried again and this time chose stable. This worked as I expected and downloaded the zip at the end and extracted it. I then copied my old flash drive contents on to the new drive. Should I have done that? Should I just move the config folder only?