evakq8r

Members
  • Posts

    34
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

evakq8r's Achievements

Newbie

Newbie (1/14)

12

Reputation

1

Community Answers

  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=0.0.0.0" for "-m, --memory" flag: invalid size: 'ultihome=0.0.0.0' 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