Crunchable

The problem has not occurred again since. I just uninstalled the containers for Krusader and we're good now.

Thanks, will do.

Sure thing. totus-diagnostics-20221218-1502.zip

Hello, My friend and I made an unraid box recently. It worked fine for a week and my friend used binhex-krusader to copy the contents of various hard drives to the array and use it normally. These details might be relevant: I came over, shut it down, and installed an extender for a case fan (wasn't long enough in the initial build). I brought it back up and changed a setting in the UPS menu (Turn off UPS after shutdown) to yes because it seemed safer to keep it off until whatever was causing outages passed. I then fired up binhex-krusader again and transferred 2 Tb of data to the array (8 hours), leaving when it finished. Everything seemed normal. Overnight the PC shut down. When my friend logged into the webUI it showed an error: "unRAID API Error: Relay returned a 500 error". Krusader, the only docker container we have installed, will not come up. Any insight into how this happened or what can be done to fix ti?

Hello, I built a new server on Thursday. I put in 6 shucked 14 Tb easystore drives, installed the preclear software, and began the preclear with pre- and post-read. That is now wrapping up and I wanted to get a sanity check on what I'm doing next and input on how long creating the array will take. I plan to use two drives as parity and the rest for data. How long will it take to create this array? SpaceInvader One indicated that building parity will take a while. I'm just going to be dumping terabytes of data on it for the foreseeable future, should I just create the data array and add the parity drives when I'm done with the initial dump? I'd rather have protection from the beginning but it would be very inconvenient tonight to have to wait another dozen hours before I could start adding files