benflux

Thank you for saving my bacon!

I haven't rebooted, here are my diagnostics... nas-diagnostics-20250417-1948.zip

I was downsizing my array, I stopped it, removed the drive, clicked new config and then attempted to start the array and it's now lost the config and doesn't know which drive was in which disk. I assume I need to know which was parity (I think I can guess that it was one of the 8TB drives)? I went looking for a flash backup but found this: Which is after the problem occurred. Help! :-)

You’re a genius. How did that folder become renamed?

I just replaced the motherboard, cpu and memory with like for like to make sure my failing setup was going to come back from the scenario where I couldn’t get to the bios or even any video output. I’m booting from a usb stick that has worked for years and this is where I end up. I don’t know if the usb is corrupt or I need to do something in the sas controller or bios to make it see the drives to allow it to boot. This was is a 10 year old lime tech box. Where to start?

same deal...

I recently lost my config for the UPS i've been using. Yesterday I had a power outtage and Unraid all went down uncleanly. Fortunately I think all is OK but I now need the settings for the UPS and i've been struggling to re-find the information. I'm connected by USB. Any tips? Tried many options and i'm currently here:

It hasn't happenned again for me since that time so I haven't researched more.

ah, daily increments! Genius.

When my NAS is doing a scheduled parity check (which can take 48hrs+), Plex (as a Docker image) becomes unusable and streaming anything over the LAN suffers from very frequent buffering. As soon as the parity check is over, all is good. Any tips?

it completed in 5 mins this time, i'll run with this and live without Plex 🙂

it could have been that the backup hadn't finished, I had a panic and restarted them. I've just kicked it off again without plex to see if that was the issue

Recently, my docker containers have not restarted after the backup has finished, any tips?

I've fixed this by switching away from br0 but keen to know how to make that work.

I've got Node-RED installed as a docker and it can see states on devices I share with it from my Hubitat hub at the time of deploying a change but if a state changes in Hubitat, the state doesn't update in Node-RED because the POST isn't getting through. This prevents my flows from starting because they don't know a state has changed. I've been told to look at whether the ports are open on my node-red docker to allow posts from the hub, the hub sends it's posts to: http://192.168.1.2:1880/hubitat/webhook__ How do I ensure 1880 is 'open'? I'm running the docker with its own IP on br0. Or am I missing something?