evilmoonkey

Well found root cause I believe, bad power cable fried the whole array. Process of troubleshooting one bank of drives to see if the drives or cables are the problem, ended up taking good drives and putting them on the bad power fried the control boards on everything so off to replacement I go. Thanks for the assist!

yep, same power supply, cables etc. Nothing else was swapped but the case

Hoping anyone has had a similar issue as I'm running to a dead end. Moved my Unraid server from one case to another, no hardware swap outs etc. at all just moving things from point A to point B, now all the drives are "missing". BIOS etc. has not changed at all, tried troubleshooting drives one by one, but no luck, nothing shows anymore and it just doesn't make sense as to why. Resize BAR enabled, SR-IOV enabled, Hot swap disabled...all the usual suspects check out. Anyone else have a similar issue they've been able to work through?

Did the force update on the container, working as expected. Thanks much!

Rust server with the Carbon Mod set to true starts up okay on initial start up. If the container is shutdown for any reason and started again, it says the following. and sits idle. I can confirm carbon is still installed on the server as well in my appdata folder at minimum so not sure what's missiing and why its stating its not found etc.

Froze up this morning. Been happening pretty frequently so I swapped out USB sticks hoping that was the issue. Worked great for a few days then boom right back to waking up to frozen system with the same log output of hex code. syslog-172.16.0.150.log

Thanks much. Ill report back when/if it happens again with a new syslog.

First real issue I've had with Unraid since purchasing over a year ago so that's a plus for the product, but I've been having serious issues the past two plus weeks. It started with the server essentially being resource locked (or what appeared to be). UI wasn't responding and CLI showed a rather long hex code error. Okay no big issue, quick restart should fix it. Restarted seemed fine until the next day...boom same issue. Went through the system to make sure I didn't have any kind of hardware issues (loose plugs etc.) causing the issue and restarted the device. Few days later, system rebooted randomly at 11:30 at night...most VM's and Dockers failed to start upon reboot. Looked through the logs and I see a couple of corrupt video files from Frigate, but nothing that 'should' crash a system, however, the a long hex error code was present there as well. This morning I woke up to email errors saying my FlightAware and a few other systems were offline for most of the night, logged in and see the error message that docker service failed to start. At this point the only other thing I can think is a USB drive going bad perhaps? Attached the syslog file from Feb. through today to assist, but any insight would be greatly appreciated. syslog-Feb_Current.zip

Yes and no. They put their site up https://carbonmod.gg/ which contains the needed linux/windows files to run the oxide replacement. Oxide itself needs to be removed from the equation and carbon dropped at the RustDedicated file level and is supposed to just go. Ive heard of developers and others stating there needs to be some additions to the Docker variables so things load in a certain order and a specific file is loaded prior to the SteamCMD process kicking off. Built a standalone linux rust server to test and the resource consumption is non-existent compared against Oxide, defiantly going to be the new way to go in the future.

So Codefling just released Carbon for Rust as a more efficient replacement for Oxide. Is there an elegant way to get that running on the Rust Docker App?