KptnKMan

Members
  • Posts

    197
  • Joined

  • Last visited

Everything posted by KptnKMan

  1. Oh shit yo, I didn't even know that 6.10 went gold! I have some reading to do! I haven't decided when to upgrade, but I may wait a little bit and figure out some stuff or upgrade 1 of my systems and see. As always, stability is my top priority for my particular setup.
  2. I wish I was happy with that, I'm basically in the same position, I've just left it alone and not touched it. But it means I cannot setup any complex networking until it is solved, because I want to setup interface failover on my servers, but I can't because of this instability. I've documented trying to make this work in my other threads on getting to 10Gbit and the thread linked earlier here as well. I just try not to think about how bummed I am about that, but stability is my priority.
  3. This is definitely an issue I'd love to see an answer for, or in the least a sustainable workaround. Alas, every time I see this issue raised, I see the response "Update your firmware". I've documented my issues quite well on this forum (As linked above), and how I've tried to workaround it, but it seems to be hoops that I have to jump through after each reboot. Not a great solution for an automated headless remote server. I'd also appreciate to see what the results of the Debian server test are, if you got around to it.
  4. Thanks, I appreciate you responding with an explanation and I appreciate your following advice but I have looked through the template trying to find a solution, and I have to say that your reasoning here contradicts just a couple things (This is just my opinion, I'm not the supporter of this template so it doesn't matter in that regard). You say that this overcomplicates things, but I would argue that a separate variable is arguably more simple. There are variables similar to this throughout your base template, that are unused, such as "GAME_PARAMS". I'm just saying, it's a little inconsistent with your implementation that there are variables unused, that can be enabled by what I would call "advanced users", which I assume would be "at your own risk". Again, just my opinion, but a separate variable is arguably a lot simpler and consistent. I couldn't agree more, I'm not arguing against best practice, this was just me trying to get the functionality to work. That's fair enough, I completely understand you don't want to support something that could potentially lock someone's account. In my opinion, a disclaimer that "This is unsupported" would be clear that this is functional but most definitely "Unsupported and at your own risk. Don't ask me for help if you lock your account". It would also help to answer questions about Steam Guard that I have already seen people asking here without doing any research (I tried to do research before asking). I couldn't agree more! 😁 Thanks, I'll check this out. Definitely good advice for an alternative. I've already been looking into setting up a second account for this purpose. Lastly, once again this is all just my opinion, so I'm just trying to test and ask questions. I appreciate you working hard on this template, and my request and offer for a PR is meant to be constructive not to indicate that there is something wrong with your template. I don't think that functionality that is "unsupported" is a bad thing, as long as that is clearly stated, because it may give a better understanding to other people. Saying that, I understand why you want to stay clear of it because of the potential hassle. I just wish that it was there because I am someone who genuinely wants to use it. Anyhow, thanks anyway. 👍
  5. Hi @ich777 I've been trying to get the Assetto Corsa image to work, but of course I have Steam Guard enabled and it fails no matter what I've tried. So I have a few questions that maybe you might be able to enlighten me with your experience? I saw that (within the image) in the `/opt/scripts/start-server.sh` file contains everything for running steamcmd and the various steps including `---Update SteamCMD---` and `---Update Server---` and I've been trying to add `+set_steam_guard_code ${STEAM_GUARD_CODE} \` in there so that I could add a `STEAM_GUARD_CODE` variable in the Unraid template and make that work. I couldn't get this to work, mostly because restarting the docker container refreshes the files in `/opt/scripts/`. I tried adding the Path to the template, so that I could manually edit the scripts persistently (To add a couple lines in): But alas, this did not work, and presents an "Execution error" that I cannot solve, but works again when I remove the Path: I would like to test further but this has me stuck. Do you know how I can make that Path work? I also looked up the Valve Developer wiki and saw that the SteamCMD section specifies the `set_steam_guard_code` is available, but also specifies to check the latest version and commands on the GitHub repo, which specifies there that the `set_steam_guard_code` is also present, but isn't in practice. In practice, the syntax for `steamcmd login` specifies `login : <username> [<password>] [<Steam guard code>]` so this line worked for me in the command console: `/serverdata/steamcmd/steamcmd.sh +login MYSTEAMUSER MYPASSWD GUARDCODE +quit` I found that I could make this work by using the Steam Android app authenticator, I could wait for the Steam Guard code to reset then in the template IMMEDIATELY AND QUICKLY specify my `PASSWRD` (Steam-Password) variable as `MYPASSWD GUARDCODE` to authenticate with Steam Guard still enabled. This is time sensitive because the Steam Guard code resets within 30 SECONDS. Within this 30 seconds, both the `---Update SteamCMD---` and `---Update Server---` steps need to authenticate (login) in time before the Steam Guard code changes. Within `/opt/scripts/start-server.sh` the step `---Update SteamCMD---` doesn't require authentication and should be faster to run with `/serverdata/steamcmd/steamcmd.sh +login anonymous +quit` (At least in my testing), but the second step `---Update Server---` seems to require authentication and work with the command: ```/serverdata/steamcmd/steamcmd.sh +@sSteamCmdForcePlatformType windows \ +force_install_dir /serverdata/serverfiles \ +login MYSTEAMUSER MYPASSWD GUARDCODE +app_update 302550 \ +quit``` With all that in mind, could the variable STEAM_GUARD_CODE be added to the template as a variable immediately after the actual password? Here is an example of what I mean: ```${STEAMCMD_DIR}/steamcmd.sh \ +login ${USERNAME} ${PASSWRD} ${STEAM_GUARD_CODE}\ +quit``` I could put together a PR reflecting this, if you would consider this for advanced users? I would DEFINITELY consider using Steam Guard or such a variable advanced. I'm just trying to get this to work.
  6. Hey man, I haven't solved this issue, I've just sort of been ignoring it for a little while because everything "works" well enough in its current state. My plan to have failover working is not possible with this issue present though, so that's a blocker. Every time I come back and see if anyone has gotten further, I see that the best advice is to upgrade the firmware and see if it fixes it. So far from what I've seen, reports show that the latest firmwares don't fix the issue. Bummer.
  7. I've been on a mission to get UEFI and rBar working this last few weeks. I did everything above before reading all of this, and confirmed everything in a bare-metal install (Also so I could use NVFlash to backup the old and new BIOS). After all of this, I still get a black screen when booting the VM that works perfectly fine with CSM enabled. Interestingly, I also find that I am unable to boot into "Unraid GUI mode" when booting Unraid UEFI enabled. When I boot the "Unraid GUI mode", everthing appears to boot correctly, and at the last moment when the screen goes black to show the GUI all I see is a flashing terminal cursor in the top left corner of the screen. Normally the GUI would boot and display the graphical login prompt. Has anyone else experienced this or understand why this is? This happens before booting any VM, and VMs boot to a black screen also, when they would normally boot ok. I'm also seeing this in my logs with CSM disabled. I was going to start a new thread about this summarising my experience, but I don't know if maybe I/we should try to work together about it here?
  8. @LexBergif you're interested in doing a lot of reading around 10Gb cards, I'd recommend checking out the thread I started about this. Lots of info in there, details, links and recommendations of what I did and eventually purchased. I'm still happy with my 10Gb setup to this day.
  9. Please, I'm trying to seek some help. I have got this container running, but after setup when I got back to the login page it flashes up for a second then disappears. I've reinstalled multiple times, cleared postgres and redis, reinstalled all dependencies. I can login initially and setup Photonix, then next login the login screen flashes up for a second then disappears again. This happens from then on each time the login is accessed. The logs don't seem to show any errors, shows postgres connected. I've tried accessing from different browsers, InPrivate mode, different client workstations, same login prompt flashes up for a second then is gone. Its quite irritating and I cannot find what is the matter. Can anyone help?
  10. Sorry no, I strongly disagree with the assertion of "going bleeding edge hurt nothing". We all know clearly enough, that updating can break thing just as much as fix things... and often does introduce issues. If you need your unraid for anything more than a test/play box, then it's something we all consider when upgrading especially to dev/RC releases. The prospect of encountering issues on a working server that you need for daily functions, for the sake of "bleeding edge" is (to put it lightly) discouraging. This thread is about temperature monitors in kernel versions of unraid, so that being said, the idea of upgrading to an unraid version to maybe get a feature that you know is not in the kernel version of that release is risking a lot and frankly a bit stupid.
  11. Thanks, I appreciate you clarifying some of the key points here. I'm going to think a bit more about exactly my use case and figure out how this can be better worked into my backup plan process. I may use another tool together with this, to get 2-way syncing for some selective workflows.
  12. Hi, using the settings RCLONE_OPERATION=copy and RCLONE_DIRECTION=both I can see traffic in both directions like so: 1) new local file, copied to remote, yes. renamed file produces duplicate. 2) new remote file, copied to local, yes. renamed file produces duplicate. 3) change local file (edit txt), changes are reflected on remote, yes. 4) change remote file (edit txt), changes are NOT reflected on local, no. Changes are overwritten. This is single changes, single change at a time.
  13. Ok, I understand the risks of what you've described, but I think maybe I'm not communicating this well enough. I think I'm using the word/term "sync" loosely, so maybe I can clarify. My bad. I set the variables to RCLONE_OPERATION=copy and RCLONE_DIRECTION=both, and made 2 changes on the remote cloud side; I created a new file "dont_delete_me_please.txt" and renamed a file "rclone_test2.txt" to "rclone_test_2.txt" (added the 2nd underscore to the filename). With that logic, I expected the operation to delete the local copy of "rclone_test2.txt", then copy down "rclone_test_2.txt" and "dont_delete_me_please.txt". But I had the duplicate behaviour as shown in the screenshot. It duplicated the renamed file, and copied down the new file. But I take it that the RCLONE_OPERATION=copy behaviour will never delete anything, but only copy, which is fair enough (Is that correct?). The original issue however, was that when setting RCLONE_OPERATION=sync, it would only sync in 1 direction. So am I correct in thinking that (Assuming RCLONE_DIRECTION=both) an RCLONE_OPERATION=sync operation will copy everything in 1 direction, then copy everything (including the previous copy) in the other direction (including new duplicates)? Am I missing something?
  14. Ok, so I changed the variable RCLONE_OPERATION=sync to RCLONE_OPERATION=copy and now files are copied, but and changes are not recognised. As a result a changed file is duplicated, where the "old" (un-renamed) file is replaced and the "new" (renamed) file is synced. Any ideas?
  15. Hi, After some messing around I've got docker to connect to my OneDrive, and I'm testing syncing. However, I can only seem to sync files UP, but not DOWN, and if I add files to the folder from the OneDrive side, they are deleted. If I change something on the OneDrive side, the "new" (changed) file gets deleted, and the "old" (unchanged) file is synced back up in its place. Seems like a working 1-way sync, I'm trying to get 2-way. I've resolved all errors in the logs/reports, and the link seems to be working. Anyone know why this is happening? I have the variables set as following: RCLONE_OPERATION=sync RCLONE_DIRECTION=both
  16. Yeah that's fair enough, I didn't know if there was something else behind your comment. I suppose it is fair enough, I often think out loud as well. The script error does seem to have gone after the recreation, so I think there was a script with an "assumption" somewhere that didn't check if the bridge device existed first. it is a bit strange though. I'm not sure if I'll get to the bottom of that one, but hopefully someone can find this and it might help them in the future. I usually use notepad++ from another machine, which allows for whitespace and non-printable character detection, as I've had that annoyance before. Its a good thing to keep vigilant for, and I will do a deeper look to see if something is occurring. For now, it seems to have confirmed my suspicions that the files were created when the network configuration was modified in the GUI, but that caused a bunch of things to go wrong at the same time. It's quite sad that this doesn't want to behave with a relatively simple configuration.
  17. If the temp improvements are confirmed to be in kernel 5.16, in my opinion it doesn't seem like a good idea to upgrade just to see if it will work if 6.10rc2 is confirmed to have kernel 5.14.15. Seems like a good way to possibly create more issues (Like the share configuration being disabled/modified) where there might not be right now. I've been waiting and considering 6.10rc2 for a while, especially with the first inclusion of swTPM for Windows 11, but still I wouldn't advise upgrade without solid reasoning. Right now, I've been watching and reading to see what the reported experiences are. I know I can potentially roll back, but that's not a great plan for me personally. I need my servers, and I'm still struggling with some other unraid issues around 10Gbit networking and bonding. Honestly, I wish that kernel 5.16 would be used if that includes temp monitor updates for X570 motherboards, but that will come later for other reasons I suppose. Also, my X570-PLUS seems to work quite well. Saying that, I'm not keen to change anything, as I've done that before and lost all of my sensors. ¯\_(ツ)_/¯
  18. These are the sensors I see on the X570-PLUS: These are the sensors I see on the X570-PRO:
  19. Hi, I upgrade both my systems last week to BIOS version 4021 and I've been having the same issues. I still have working temps on the X570-PLUS and not on the X570-PRO. Seeing as they are both using the same chipset, I've been trying to copy the temp configuration from Unraid1 over to Unraid2, but I've not managed to make it work yet. I did this by copying the file /boot/config/plugins/dynamix.system.temp.plg and the contents from /boot/config/plugins/dynamix.system.temp/ to the other server. After a reboot, that didn't seem to work. If anyone has any idea how I can copy a working temp config to another server, I would be grateful.
  20. You mean beside the netboot bios? I haven't seen any delays other than that with the cards coming up, they seem to be recognised and active when Unraid boots on both servers. Yep, I'm using the dual-port SFP+ cards, and only using a single SFP+ on each card, just as you say. I'm not sure why more "ghost" ports would be registered, as I can see all 3 (Including the onboard 1Gb) listed when the system comes online. Is a ghost port something that has been observed in other uses of the Mellanox X-3 cards? Is this known behaviour with dual-port cards? The BIOS on these cards is the latest installed from the Mellanox site, installed using the Mellanox Tools for Unraid, exactly as instructed for the tools (As detailed in the GUI). Also, I have this issue on both servers where there is seemingly a skipped interface. I noticed in the network.cfg that initially there is the line for 'BONDNICS[0]'. Originally, this read as 'BONDNICS[0]="eth0 eth1 eth2 eth3"' But now it reads as 'BONDNICS[0]="eth0 eth1 eth3"' on Unraid1, and 'BONDNICS[0]="eth0 eth2 eth3"' on Unraid2. Unraid1 is where I'm having the issue where it seems to not be able to decide which interface id is being used, and lists 4 in the network-rules.cfg file. Unraid2 has not shown this particular issue. Also, this bootup error seems to have disappeared after I jumped through hoops to remove-then-re-add the br0 interface, that I mentioned above. I suspected that was related to the bridge getting messed up somehow, and that seems to have reset it. I understand that the bridge itself is also listed as a device, as basically everything is in linux. So with it being broken the startup scripts were probably either looking for it or assuming it was there? to setup the bridge and/or bond? Interestingly, this s***show began after I simply set the Interface Description. Changed nothing else. Before that I had wiped the network.cfg and network-rules.cfg files, all settings were running default, and I noted that the network.cfg file was not recreated until I set the Interface Description. As soon as I did that, everything seemed to get weird. Happened on both Unraid systems. ¯\_(ツ)_/¯
  21. So I got the br0 network interface back to a "working" state by essentially: - in settings, disabling Docker - in settings, disabling VMManager - network settings, disable bonding and bridging - reboot - fix "interface rules" duplicates manually again - confirm that everything is in correct order - reboot - fix "interface rules" again, and confirm - network settings, enable bonding and bridging - reboot - confirm settings stuck, fix "interface rules" again - confirm br0 is present and working - enable docker - enable VMManager - verify VMs work again Really not sure why that got broken. Also on Unraid1, the physical interfaces now seem to show up as eth0, eth1 and eth3. I still need to manually modify the network-rules.cfg file after each bootup, otherwise 4 interfaces show up in the "interface rules" GUI. I just encountered the same br0 missing issue on Unraid2, and resolved it following the same process above, but the interfaces are labelled the same afterward. Would really appreciate if anyone has any idea what might be happening?
  22. I started a new thread to investigate some issues I encountered today regarding more networking trouble. I can troubleshoot networking issues well enough, but Unraid configuration I'm not an expert at. Something strange is going on, and I'm really not sure why. I'd really just like to get the bond networking working stable and well so I can not have to mess with it.
  23. Hi all, I've been getting very strange behaviour on both my Unraid systems since upgrading my NICs to 10Gb Mellanox ConnectX-3 cards. I've chronicled my journey to using 10Gb in a separate thread over here. Started this thread to try and figure out if there is a way to resolve the issues I'm encountering. My intention is to have the bonded network (active backup mode 1) working with the first port of the Mellanox 10Gb card as primary, and the onboard 1Gb as secondary failover. My understanding of how this should work is that the "primary" interface should be prioritised and fail-over to the secondary, then further interfaces (if configured) if primary interface is interrupted. I understand the bond should also fail-over back to the primary interface, should it reconnect. That doesn't seem to be happening, or I'm misunderstood. So far I've not been able to make that work as expected, and I'm struggling to determine why. When either system boots up, the onboard 1Gb is set as primary bonding interface until I manually unplug the 1Gb and it fails-over to the 10Gb. It does not seem to fail-over back to the 1Gb, unless I unplug the 10Gb. I'm quite sure its not the cards themselves that are the issue, as they seem to operate within expectations, but some software configuration or settings in Unraid. At this point I'm running everything pretty standard, and still experiencing issues. Is there some way to manually set the bonding I'm also seeing some other strange behaviours that I can't determine the reason for, and I continue to troubleshoot: On both servers, I have (and are using) the 10Gb Mellanox card, and the 1Gb onboard for the respective motherboard. On both servers, I have tried wiping the network.cfg and network-rules.cfg but the same issues return. On both servers, bonding (active-backup mode 1) and bridging is enabled by default. If anyone has any advice or can help troubleshoot I'd be thankful. A few issues are present, being: - network interface assignments changed. On Unraid1 I have eth0, eth1, eth2 and also eth3(?) yet I only should have 3 physical interfaces. On Unraid2 I'm getting eth0, eth2, and eth3. I'm not sure where eth1 has been skipped. - duplicate entries in the network-rules.cfg file. On Unraid1, I'm seeing 4 entries in config for the rules (eth0 to eth3) but still show 3 physical interfaces. This causes an apparently known issue where I am unable to edit the "interface rules" in the network setting GUI. I have to go back to the network-rules.cfg file, delete one of the entries and back to the GUI. This reoccurs after each reboot. On Unraid2, this occured once but has not seemed to be an issue since, the system has apparently settled on eth0, eth2 and eth3. - br0 has disappeared. On Unraid1, as of today, the br0 interface apparently seems to have disappeared. I'm not sure why this is, I haven't modified anything in networking as yet, apart from modifying the "interface rules" order and setting an interface description. I can access the webgui but I now get an error when trying to start any VMs: - boot up log errors (I think) related to interface assignments. On Unraid1, I have started seeing errors in the bootup log stating: 'Not enough information "dev argument is required. Error: Argument "down" is wrong: Device does not exist' There doesn't seem to show an IP on the main bootup screen either, not sure if this is related:
  24. Yeah, this is what I'm wondering about as well. I'm going to have to do some tests and see if there is a timeout I'm missing. I remember seeing in the CRS309 that there were a few timeout settings, so I assumed there would be something similar for unraid. That's something I could do. I imagine the passive side would just be regular links? I guess that would that mean disabling the bond0, then configuring the separate switch interfaces as a bond interface as before? Would that mess with the DHCP or do I need to spoof both nics as the same MAC? 🤔 I need to read the mikrotik wiki to find out their recommendations, or try their forum as you advised. 🤔 I need to go find some answers, I appreciate you taking the time to run through this with me.
  25. Ah gotcha. Thanks, that makes total sense. Absolutely, this seems to match what I read and understand. I'm not sure how to set the priority in unraid apart from the NIC order in the "interface rules". Is there a config I can set where I can assign some kind of weight to the ethX interfaces? I made sure to rearrange the interfaces to prioritise both the 10Gb links (1 being disconnected of course, but ok) and then the 1Gb link. This way I figured it would just go down the totem until it reaches the 1Gb link, and refer back to the 10Gb when it returns. Doesn't seem to follow that behaviour, unless there is a timeout I'm not aware of? I figured that 30 seconds was the norm, even though it failed-over immediately, didn't seem to skip a beat. Hmm, I assumed this was the order in the network-rules.cfg file or the interface order in the "bonding members of bond0". Interestingly, there is no network.cfg file since I deleted it to reset the config. I assumed this is because I have not modified anything, and the active-backup bond0 was configured by default. If I set an interface description or something, I expect it to return. I initially set the "interface rules" in the order I want, but I should look further into configuring linux UDEV rules, if there is something else I can set for weight or timeout. I think there's something I'm missing, but I can't see anything else obvious.