TheIlluminate

ive seen the reason being heat and that shouldnt be concerned for this on as the usb 3.1 internal spot on a r360 is right in front of the pcie slots so it gets PLENTY of airflow. on a side note samsung doesn't even sell usb 2.0 drives anymore and the usb 2.0 slot on the server is technically for idrac access. I "could" plug it in there but i would like to put it on the internal slot if i can. appreciate the response im just looking for more information on why 3.x seems to fail more often.

I was afraid of that. Is there any indication of whether it's the flash drive failing? Even still Im about to pick up a Samsung FIT 64gb (they don't make any smaller anymore) and run it on the internal 3.1 usb port and see if that helps. Thanks as always I appreciate it.

And here's the syslogs. I also updated to 7.1.2 hoping that would help. syslog-Waz-Server.log

I'm back sorry it took so long. Got that docker taken care of and let it run for a few days. Still crashing roughly every 24 hours. waz-server-diagnostics-20250513-2030.zip

That would probably be Pelican-Wings. That should be unrelated to this as I just started messing with that today/yesterday. Its giving me trouble so and Im messing with its config file so I have to restart it every time i make a change.

just happened again and i had the syslog on for a bit before that. should have posted that as well. Sorry syslog-Waz-Server.log

Been a while since I last had a problem so here goes. Recently the server started becoming non responsive to connecting to the GUI but all the dockers kept working for at least a couple hours. After that even the dockers stop working and I can't connect to anything. Here's the diagnostics and i'll be on all day to try and figure this out. Only thing I changed recently was having to redo my network for a move but I simply gave it the same static IP address as before and set it up in unraid to have that IP address. Only weird thing I'm running on that end is that its in a link aggregation. Thank you ahead of time. Diag.zip

Sorry for posting in the UnRaid 6.0 section but it doesn't appear a 7.0 is up. Nor do I believe this is related to 7.0. My system keeps crashing due to a specific docker. Specifically Pterodactyl and is whats weird is it only crashes for a single game server i'm trying to run. If I could just get a pointer to go in the right direction that would be great. Specifically its the UbiSoft Foundry game server. I can run it for awhile and then it will crash the whole system not just the individual server. I also run a Palworld and satisfactory server just fine for long periods of time. Thanks Ahead of time waz-server-diagnostics-20240810-1143.zip

Seriously thank you for the reply. And double thank you for pointing me to someone who may help. Hope you have a good day.

Hello and good morning. I hope this is the right place to ask this and forgive me if its not but would it be possible for you to do a Foundry game server docker? It just came out last week on steam and they have a Foundry dedicated server for it. If it is possible thank you very much. If you are too busy then thank you for all you do otherwise and I guess i'll start to learn how to build a docker.

I don't think i can do that...its a dell r360 1u server. My question then would be why only the cache drives? the other 4 ssd drives are on the same backplane.

And the errors are back. New diags are posted. waz-server-diagnostics-20240416-1158.zip

So far so good. Just finished the scrub and balance and no errors and nothing in the log other then the balance and scrub. Guess I'll let it run for the day and then if its good figure out why that slot is giving me trouble as its a brand new server. Figures its something basic. Much appreciated and I'll mark as solution for now. Thanks

just swapped the drive to a different slot. can't really do another controller as its all an 8 device backplane on a dell 1u server. I'll let you know if the problem continues. im running a scrub and a balance just to get the drive going.

Keep getting this error every day and ive deleted the docker img file and rebuilt it already. Checked out the SSD that the cache is on and i keep getting write errors on the primary SSD Cache Drive. I pulled it and reseat it as well. I have it in Raid 1 so if i have to swap it out thats fine even more so as i have spares available. Just wanna make sure im not missing something but Im wondering if i have a bad drive. Thanks Diags.zip

Thanks for the reply. Sorry for taking so long to get back.

Got this error code from the fix common problems plugin and just making sure its all good. I'm pretty sure its the one in the syslog at Feb 21 15:39:43 so its just ECC RAM catching something and fixing it but do i need to be checking for ram errors or should I be good? Appreciate the help as always guys. waz-server-diagnostics-20240222-0824.zip

Personally I'm just waiting for 6.13. If you need it now then yeah id run it through a vm. I don't think it matters what VM but someone else could answer that better then me. I'd do what OS you are more comfortable with. Windows has ARC drivers and Linux has them built in now. So what ever is easiest for you.

Unless you are running and can confirm unraid 6.13 has linux kernel 6.2 or higher OR using Thors little kernel hack to run linux 6.2 or higher on unraid 6.12 then no it doesn't work natively. You would still need to pass it on through a VM.

Just kinda curious and I know this isn't going to be an easy answer if it is possible. But with AMD releasing a new media accelerator card that supports AV1 and is stupid fast. How would one go about loading the drivers into unraid? Is it even possible or is this gonna have to be something like whats been happening to load the Intel ARC drivers into unraid? Specifically i'm looking at an Alveo MA35D media accel card. It would be running on a Dell r730xd. But I have absolutely no idea how the software and driver side of things would work.

Honestly didn't even think to check for that...well crap. Sorry for the stupid question and thanks. You wouldn't happen to know a PCI to USB card that actually works would you?

I think its that one. On a side note how do i translate info from that in to figuring out what goes here: /dev/ttyS1

I'm running 6.12.4. I can try real quick. Give me a minute

if you mean ls -l /dev/usb/by-id. same thing.