lordbob75

Hello, I've started getting a machine check error on my server. Instructions say to post it to support, so my diagnostics are attached. Based on the post in the more information, it looks like it's happening well after the startup, so I think it's an actual issue. Hopefully it's a cheap/easy fix if so. Thanks for the help. skynet-diagnostics-20241027-0839.zip

Oh, duh, I see now. I totally assumed that was something else. Looks like this has worked perfectly and I'm back up and running again. Thanks very much, that was an easy fix in the end.

Ok, I set both cache pool devices to "no device", but it won't let me start the array because cache drives are missing. Did you mean something else by "unassign all pool devices"?

Ok great, that sounds like an easy fix then. I'll give that a shot this evening after work and report back.

That won't delete or erase the cache drive? I'd guess not since you're recommending it, but I want to make sure I understand first. It would be a nice easy fix though, so I hope it'll work. I won't be able to try until after work today anyways so I've got some time.

Ah, well it says the cache drive is emulated and when I mounted the array it started containers. Uh, it's been a while and I don't remember exactly. I followed directions from the documentation on changing the cache drives. I believe it was these instructions: https://wiki.unraid.net/Replace_A_Cache_Drive Everything had been working for quite a while and the server had rebooted multiple times. Attached. skynet-diagnostics-20230607-0543.zip

I just replaced my unraid USB drive. The array itself is good, but my cache drive isn't. For some reason the config thinks that I'm still using an old cache configuration with 2 drives, whereas I have moved to using just 1 drive well over a year ago. However, the new USB config is looking for my 2 old cache drives not my single new one. The cache drive is successfully emulated by the array. How can I fix this? Can I just correct the cachepool.cfg file? Do I need do something else? Let me know what, if any, information you need. Thanks

I'm using NUT with my Xtreme power p80 series UPS. NUT seems to detect it, though I have to manually set the battery size. As far as I can tell everything is working correctly, except that it seems to shut my server and client down immediately upon AC power loss instead of depleting the battery. I believe I have it setup correctly, it's set to power the server down at 10 minutes on the battery.

All of a sudden this container won't load. When trying to bring up the WebGUI all I get is "Cannot Connect". There are no errors in the logs and I haven't even logged into the GUI in months because everything worked. Tried reinstalling it, changing branches, changing to bridge/host/br0, deleted all appdata and copied it back over. What's going on? How do I fix this?

Great, just wanted to double check. Thanks!

Ok cool, easy fix then. This won't delete the world right?

@ich777 thanks for the great containers. I'm running 2 Valheim containers and both are working just fine except for one issue. Almost every time that the CA Appdata backup runs, the first server doesn't come back up because the original ports are added back to the 2nd server and it won't let the other one start. I deleted the original port and game port on the 2nd server, but it's coming back. Any idea how to stop it from doing this?

Yes you have to delete it. I tried force update first but it doesn't do anything.

Since the GitHub post didn't specify anything for UnRAID specifically, I'll post it here to confirm it for anyone who's unsure. Simply delete your current container (and image). Reinstall the container, and choose the Default (or Latest). I just did this in less than 15 minutes and it was extremely painless and saved all my settings. You can search for the container easily enough but if you're unsure which one you had installed you can always check Previous Apps in the left menu.

Oh I'm sure it's my fault somehow, I just dunno how. Screenshot of settings: @ich777 Alrighty I think I have it figured out. I believe the server was continually rebooting itself (taking about a minute to do so) and throwing an error when it tried to start, causing the reboot. Error seems to have been caused by an out-dated map-settings file, which has now been corrected. Server is stable, and the log is no longer being spammed. Problem solved! Confirmed I can connect to it as well. Not sure what exactly happened with the map file, but I'm sure it was because of updates.