• Posts

  • Joined

  • Last visited

Everything posted by evakq8r

  1. Machine has been restarted since the anomaly, so current diagnostics are now meaningless, and I'm not rolling back then upgrading to get them again, but appreciate the input.
  2. Just adding my 2c/experience with the upgrade process. Went from 6.9.2 to 6.10.2, no LAN NICs on next boot. Found adapters I have in my Dell Poweredge appear to be the affected ones mentioned here (Broadcom NetXtreme II for reference, running in bond0). Ended up adding the blank tg3.conf file to the USB boot drive, LAN adapters now functional. Strange side effect however; the upgrade appeared to completely remove my NVIDIA and DVB drivers? Only realised this when trying to run the docker container for Plex and having it return 'Error: Unable to find runtime nvidia'. Is this expected behaviour? Or just an unexpected anomoly? (reinstalling the respective drivers from the CA App store has fixed the issue FWIW).
  3. Yes using an external DB and also imported the schema. For whatever reason though, I just reinstalled it from scratch and made no changes to config, and 'it just works'. NFI why, but I'm not questioning it.
  4. Have tried setting this up today, and can't get the web UI to load the login prompt without throwing this: There's no errors in the Apache Guacamole docker, nor MariaDB. The user and password work for the database I setup for this container, so I'm at a loss. Have tried both Unraid templates (with and without mariadb), Docker has 'host access to custom networks' enabled, and have also tried different networks (br0 to give the container it's own IP, as well as my reverse proxy network). Probably something simple, but any help would be appreciated. Thanks.
  5. Fixed the issue; ended up being an ID10T error. The Dell drive caddies have a SAS and SATA hole layout, and I figured 'hey, I should use the SATA holes!'.... nope; the drives were not connected to the backplane as I didn't screw the drives into the correct holes in the caddy. Now using the SAS holes, and lo and behold everything works!
  6. Hi all. I've been using Unraid for quite a while now and had the means to migrate my server from a makeshift server to a Poweredge unit I've acquired. It comes with a PERC H700 mini flashed to LSI 2308 in IT mode and had come with 4x SAS drives. Installed a test environment of Unraid, worked fine. Started migrating my hard drives into it (7x Seagate Ironwolf NAS SATA 10TB drives), turned the server on and... nothing. No SATA drives. Turned off the server, plugged the SAS drives back in, nada. The only drives being detected are my NVMe cache drives. Tried plugging in a mix of SATA and SAS drives, same outcome. I have no idea what's caused Unraid to no longer find any SAS or SATA drives. To my knowledge, this controller should support both SATA and SAS drives. Tried checking whether the BIOS or iDRAC would show the drives, but neither did (even when functioning previously) as the LSI has been flashed into IT mode. Diagnostics attached. The syslog shows the LSI SAS 2308 controller still showing up and enabled, so I'm at a loss. Any help would be appreciated. Thanks. tower-diagnostics-20220106-2316.zip
  7. Client is 100% on Experimental (game version confirms that). I'll rebuild the container at some point and see how we go. Thanks anyways @ich777- great work as always
  8. /facepalm... no idea why I didn't pick that up myself; forgot that the dedicated server defaults to EA(also just rechecked the patch notes and somehow missed (EXPERIMENTAL) against the latest version...). I've added -beta experimental to the game parameters and validated the files. It appeared to download an update, but the game still complains of a mismatch (server doesn't match the client). Tried -beta -experimental, same deal. I suspect I might need to rebuild the docker container completely as it still thinks EA is Experimental.
  9. Has anyone encountered any issues with the Satisfactory container not pulling the latest game version? (even though the logs suggest the latest has been pulled). Is there a way to interact with steamcmd from within the Satisfactory docker to try and force an update? I also installed the same container on a completely different server and no difference. Satisfactory is throwing a 'game version mismatch' error: From the different server (new install): Update state (0x5) verifying install, progress: 2.67 (120586243 / 4522427563) Update state (0x5) verifying install, progress: 6.94 (314071968 / 4522427563) Update state (0x5) verifying install, progress: 10.79 (487774880 / 4522427563) Update state (0x5) verifying install, progress: 15.19 (686813465 / 4522427563) Update state (0x5) verifying install, progress: 19.87 (898567076 / 4522427563) Update state (0x5) verifying install, progress: 25.74 (1163915780 / 4522427563) Update state (0x5) verifying install, progress: 29.96 (1354779631 / 4522427563) Update state (0x5) verifying install, progress: 34.42 (1556748166 / 4522427563) Update state (0x5) verifying install, progress: 39.39 (1781451636 / 4522427563) Update state (0x5) verifying install, progress: 44.03 (1991436565 / 4522427563) Update state (0x5) verifying install, progress: 47.12 (2131001286 / 4522427563) Warning: failed to init SDL thread priority manager: SDL not found Update state (0x5) verifying install, progress: 51.67 (2336568147 / 4522427563) Update state (0x5) verifying install, progress: 55.57 (2513281039 / 4522427563) Update state (0x5) verifying install, progress: 60.30 (2726960366 / 4522427563) Update state (0x5) verifying install, progress: 65.98 (2984071282 / 4522427563) Update state (0x5) verifying install, progress: 71.34 (3226146982 / 4522427563) Update state (0x5) verifying install, progress: 76.97 (3480813547 / 4522427563) Update state (0x5) verifying install, progress: 82.25 (3719792347 / 4522427563) Update state (0x5) verifying install, progress: 88.28 (3992280189 / 4522427563) Update state (0x5) verifying install, progress: 93.53 (4229697601 / 4522427563) Update state (0x5) verifying install, progress: 98.72 (4464500652 / 4522427563) Success! App '1690800' fully installed. ---Prepare Server--- ---Server ready--- ---Start Server--- From the game: EDIT: Hmm, might be a Steam issue; loaded a new version of the dedicated server from Steam directly and it's also not up to date... but would be good if someone else can confirm so I can at least verify it's not just me.
  10. Ahh, Game Parameters and Extra Parameters aren't the same thing (that's where I was getting confused): vs: As the error suggests, 'ultihome' is because '-m is another abbreviation for --memory in unRAID, and it's in the wrong format. Just tried again under Game Parameters only, and (after a few restarts) it seems to have registered. Thanks @DazedAndConfused.
  11. @DazedAndConfused Are you adding the -multihome part to the Extra Parameters template under Advanced View? Or somewhere else? If I add as you've pasted above, I get: invalid argument "ultihome=" for "-m, --memory" flag: invalid size: 'ultihome=' If I add a double-dash ( -- ) : unknown flag: --multihome Adding to Game Parameters starts the container, but throws the error listed on the QA website:
  12. The wiki is your friend @ra1k_0. There are suggestions for improving multiplayer under 'temporary lag solution', but I've implemented them anyway to prevent that kind of issue happening. Not sure if @ich777 wanted to consider doing the same for this template? Others that have spun up the dedicated server as a Docker container appear to have.
  13. Right, my bad. I'm used to manually spinning up docker files in non-Unraid environments and added the Variable path to substitute for -v. As for raising it under Satisfactory Steam Community/their own QA website, they have announced plans to spin up Satisfactory Server as a docker hub container, but no ETA on when that will actually come to fruition. Not a big issue, I just like things to represent actual time zones of where I am. Thanks @ich777.
  14. I might have missed it somewhere in the documentation, but is it possible to get the times in the logs to match your local timezone rather than UTC? I've tried adding the TZ variable: -e TZ="America/New_York" \ (example) to the container as well as: -v /etc/localtime:/etc/localtime:ro \ But the logs seem to revert back to UTC (I'm +9.5): [2021.10.30-05.42.44:871][602]LogGame: Write Backup to Disk and Cleanup time: 0.003 seconds [2021.10.30-05.42.44:874][602]LogGame: Total Save Time took 0.428 seconds [2021.10.30-05.47.44:648][574]LogGame: World Serialization (save): 0.166 seconds [2021.10.30-05.47.44:913][574]LogGame: Compression: 0.262 seconds [2021.10.30-05.47.44:913][574]LogGame: Write To Disk: 0.002 seconds [2021.10.30-05.47.44:913][574]LogGame: Write Backup to Disk and Cleanup time: 0.003 seconds EDIT: Actual Unraid Template screenshots would probably help:
  15. True, but people have been asking for dedicated servers for quite a while now, so I figured a lot of people would be trying to set this up
  16. Thank you for the Satisfactory template @ich777! I was literally in the midst of spinning up a dedicated server on a VM and stumbled across this. I do however seem to have some weird anomaly with trying to connect (it is likely a me problem as I can't find any reports of the same issues happening with someone else). This happens with both Windows Server (via Steam app) and Linux (via steamcmd). When I try and connect to the game server, my logs are spammed with the following (the IP is from my Steam client on my gaming PC): None of the server info loads in Game on my client (game thinks the server is offline). I understand this is all still experimental, but has anyone else had this same issue as yet? EDIT: Fixed my own issue; turns out I made an unnecessary port change (tried connecting to 7777 instead of 15777). Swapped to 15777 and now it loads.
  17. I've had 3 DNS servers on 2 different bits of hardware fail on me in the last 24 hours (power blackouts really aren't fun), so yes I have; it's now set to a known public DNS provider and everything "just works".
  18. Both plugins remain once booted. Here you go. syslog
  19. I did notice an update earlier (for both nvidia and DVB). Installed both and rebooted.... The boot time is significantly faster now! I'll keep an eye on this for a few days but suffice to say it no longer takes my server 90 mins to boot!
  20. Ah yes of course! Forgot about that handy feature. Thanks again!
  21. I see, that would make sense. Australia No problems, I'll take that under advisement. Trying to limit myself to services like unbound or other recursive servers, but I will set that as a last resort. Great, thanks! Thanks for your help thus far @ich777
  22. That said, here's the current syslog file attached (without rebooting). syslog
  23. There were Plugin errors listed for the Nvidia and DVB drivers, which have since been removed. Server does have an active internet connection, yes. I do run PiHole on the server as well as the Unifi Controller. Not sure whether not having the controller accessible would prevent internet access? (haven't had the issue before). I would, but after I made the last edit earlier (the server did finally boot with a working GUI), I'm now reluctant to reboot it again and have to wait over an hour and a half for it to become responsive. Well when I took the USB boot drive and plugged it into an alternative computer, I deleted all plugins listed in the folder and tested, which worked fine. I then added JUST the NVIDIA plugin and tested, and the boot hanging began. Putting 2 + 2 together made me think that was the case, but maybe it was coincidence, I'm not sure. That's correct; I plugged a 5" RPI screen I had spare into the 1st port of the P2000 so I could get an idea on what was happening when the server didn't respond after the power blackout.
  24. Hi there, My Unraid server seems to no longer be booting with the NVIDIA plugin installed. Need to explain a little. We had a power blackout today (the server is on a UPS, but due to the length of the blackout the UPS shut the server down, which was fine). Since power was restored, Unraid has been hanging after starting Samba services during the bootup sequence (normal boot time takes ~5 minutes, I left the server at this state for over an hour and no GUI). I took the USB to another computer, set the syslinux.cfg to boot into Safe Mode, and I am now able to get to the GUI, which made me think one of the plugins went bad. I had an old USB backup from 12 days ago that I flashed using the Unraid Creator and tried to boot that, which didn't work. Thinking that was odd, I removed all addons from the config folder on the boot USB, and attempted to boot in normal mode. Successful. I then went to reinstall the NVIDIA plugin (460.67 driver), disabled and re-enabled Docker as suggested, and tested Plex transcoding. Successful. I then went to reboot Unraid, and it once again stuck at the Samba login screen. I did however notice the server was pingable and can be SSH'd from another device (not directly, oddly enough), so the server is 'alive' but with no GUI. I rolled the change back with the NVIDIA plugin not installed, and the server fired up no problem (albeit with no plugins). I've gone back to the last backup I was able to grab before the UPS' power went out, and pulled a diagnostics via SSH. TL;DR: What would potentially cause the NVIDIA plugin to prevent GUI bootup? Pic attached is as far as the boot sequence will go. Server specs are in my sig. EDIT: Well, after waiting an hour and a half... the bloody thing boots with a GUI. I have no idea why it took so long to boot, but it's up and that's all that matters. I will do some more investigation over the coming days, but if anyone has any insight as to the lengthy lead times on boot up, I'm all ears. tower-diagnostics-20210322-2110.zip