ANJ_

I'll keep fiddling around, it must be something I'm missing, just strange I can't seem to make a new server work off a fresh install but I'll try at it again soon here. Thanks for the help

I'm not sure if I'm doing something wrong but I haven't been able to get the container working since last uninstalling /reinstalling. The server will show in game but any attempts to join fail. I also get various errors in the logs depending on whether I try reconfiguring fresh, with saved backups, or with just config backups. This may be a more general question to be asking here but is there a way I'm unaware of to totally delete a containers files from unraid? When I reinstall it doesn't take long to boot the server like you mention it should by reinstalling the game. Seems like the game must still be installed. I keep deleting the contrainer and image as well as deleting the appdata folder through console with rm -r "...appdata/longvinter/" but when I reinstall it still seems to remember my settings, drops the container right in the same folder I had it in previously. I'm thinking my issue might be that everything isn't getting deleted but I'm not sure how to wipe it any more cleanly than that.

Not to beat a dead horse but I was just curious if anything ever became of this issue with the Longvinter Server Docker needing it's updates pulled from GitHub instead of SteamCMD. Just deleted the docker again and reinstalled so that it would update and it reminded me of this thread.

That was the ticket, thank you.

Is there a prerequisite to changing the file system of the cache? The File system type is not selectable for me.

Ok, noted, thank you. How about the pool backup method, is what I previously mentioned the way to go about it or is there an easier solution I may be unaware of? If you don't mind some input.

I've read some people also recommending switching to XFS? I think they said specifically if you only have 1 cache drive, which I do. Do you recommend this as well? I'm also not sure of the best practice or best way to go about backing up the pool. I have the Appdata Backup plugin, but wouldn't I still need to rebuild each individual container, I guess through templates, and then run the Appdata Backup restore? I just imagine I'm going to have to be doing a lot of reconfiguring which of course is a pain.

I've admittedly been having a lot of trouble with my server ever since my flash drive died and I rebuilt a new flash, most things I've been able to get passed but it seems like about once a week some container or issue pops up needing a restart. Today however the Fix Common Problems app is saying that my cache drive is read only, out of no where. This did actually happen once before after rebuilding my flash drive but all was resolved when I ran a scrub on the cache drive. This time though unraid doesn't seem to be allowing me to even attempt a scrub. When hitting the scrub button it just shows 'aborted' with no attempt. I tried switching out the sata cable as I read that could be a problem despite not getting any UDMA errors, but that didn't help either. My logs show a handful of concerning looking errors but as I am fairly new to the whole server and networking world I don't know where to go with it. Attached diagnostics as well as logs, some things I'm seeing are: This error seems to be spamming quite often on startup.. Though it doesn't appear to be the cause of my suddenly read-only drive, maybe it's related. Here is where the drive seems to suddenly switch to read-only: I don't know what to make of these logs but it shows where the drive is suddenly "forced readonly". Before that point if I were to run Fix Common Problems it wouldn't show the unable to write error but after that point it will. I've allocated 30GB for Docker and only 17GB of that is being used, so the docker itself doesn't appear to be full. I'm debating rebuilding docker if it's recommended but am also a bit afraid of going that route before trying anything else as it feels a bit nuclear and could be a pain getting everything back up and running again. I'm hoping someone can help point me in the right direction here, I'm at a loss. Having issues with most of my containers because of this. Also, random bonus error I don't really care much about, but fix common problems also lists Write Cache as being disabled on disk1 even though when I check the disk or switch on the write cache with "hdparm -W 1 /dev/(diskID)" it still says it's disable in fix common problems. This I can just ignore though for now as I obviously have bigger fish to fry. anjnas-diagnostics-20240917-1050.zip anjnas-syslog-20240917-1750.zip

Good call, they did email the new file, thanks! Everything seems to be in working order. Appreciate all the help Jonathan!

I'll look through the diagnostics. Though it seems I have created a new problem, which I'm sure has a quick fix if I knew where to look. Upon putting a more recent flash backup onto the flashdrive, it seems the Cache drive is now mountable however I'm being hit with a Invalid Key / GUID Mismatch. Which I just had to replace with this new flashdrive. I'm guessing the old backup must have had a key file in there causing the issue but upon trying the same "replace key" method I'm now getting Error: {"message":"Request failed with status code 403","data":{"error":"KeyFile is not valid"}}

So I transferred my flash backup onto a new USB stick and I am now able to boot, however something I previously mentioned happened again. My SSD which functions as my cache drive once again is showing as btrfs and unmountable. I know I can solve it with a format and replace my appdata with backups but does anyone know what might cause this? I guess it's possible that the last time this happened might be right around when the backup I used for this flash drive was made, not sure if there is a correlation or not, but if anyone has any insight? Not sure why my cache drive has randomly become unmountable now for the second time. It's actually possible too that since the flash backup I used was made that I did actually swap out the cache drive for a larger one. Now that my server is up however I can access more recent backups and can once again copy over the flash backup onto the new usb, hopefully this might solve the issue, but again, if anyone has any ideas I would appreciate any information so I'm more informed on what may be going on.

I used the same format, yes. Sounds like I'll probably just reconfigure a new flash drive and give that a shot.

Appreciate that info. And I haven't made any disk changes as far as swapping/adding/removing/formatting any drives if that's what you mean, not from what I can remember at least. I think there may have been one instance where my Cache drive wasn't readable randomly and I had to reformat it, that might have occurred after the backup. Is there something I should be careful about in that case?

I've been having some issues lately with my unraid GUI being a bit unresponsive or slow despite apps working, most the time I've just left it be as I didn't need to access it much but after some time things usually slow down even more and a reboot is needed. A few times trying to reboot I couldn't get unraid to launch, I switched the USB port for my flash drive and then it booted back up. So today my GUI again became unresponsive and I went to boot, however it wouldn't, after switching ports, still not booting. Checking BIOS I made sure Fast Boot was disabled, and I reordered the boot priority to put the flash drive first, since I think when I switched it the first time it must have rearranged it, I also disabled all other drives as bootable drives. Still not having any luck. Just getting "Please select a proper boot device and reboot" I've just now plugged my flash into my Windows PC and the drive does show up in the This PC viewer, though it shows no capacity and in disk management it also shows No Media, as if it hasn't been formatted. So the flash doesn't seem dead, but should anything be showing? I haven't plugged it into my PC before so I wasn't sure if when it's configured as an Unraid bootable it shows any media when plugged in. Help would be appreciated, would love to put these rocky server boots behind me. Also, I do have a flash drive backup.zip from a few months back if needed

Awesome! No worries and glad it brought some insight. Thanks for everything you do!

Just to answer the questions you asked: I haven't inserted my credentials anywhere, shares and paths are configured properly, no ad blocking set up, and I believe I have my network DNS set to 1.1.1.1 and 8.8.8.8 as backup. Also, I've used your other containers (Rust, SonsOfTheForest, Satisfactory, DontStarveTogether, Valheim, PorjectZomboid) And they all haven't had any issues updating. So far just Longvinter doesn't update. Edit: Also here is a small section of the logs when booting the server that seem to show a discrepancy: ---Starting...--- ---Update SteamCMD--- Redirecting stderr to '/serverdata/Steam/logs/stderr.txt' Logging directory: '/serverdata/Steam/logs' Looks like steam didn't shutdown cleanly, scheduling immediate update check [ 0%] Checking for available updates... [----] Verifying installation... UpdateUI: skip show logoSteam Console Client (c) Valve Corporation - version 1716584438 -- type 'quit' to exit -- Loading Steam API...OK Connecting anonymously to Steam Public...OK Waiting for client config...OK Waiting for user info...OK ---Update Server--- ---Nothing to do, game up to date!--- ---Prepare Server--- ---Server ready--- ---Start Server--- seems like it connects to steam ok but fails to notice any need to update. Edit 2: Sure enough deleting the container and the appdata folder and reinstalling the container updated the game. Still not sure why it fails to update on restarts though. The game is a super small indie title so if the problem actually lies on the devs end I made a note of it in their discord. Curious though if anyone has a better idea of what's going on here given the information?

Sorry to bother without a large grasp on what might be happening, but I was trying to setup the Longvinter server yesterday and was struggling to get it working as it kept saying version mismatch in the server browser. In the docker overview it says "Update Notice: Simply restart the container if a newer version of the game is available." However restarting the container never seemed to fix it. I then removed the container (I originally downloaded the template a few months ago) and deleted the appdata folder and reinstalled the container from your template, the game version then was updated and the server worked. Now today the game updated again and once again I have a version mismatch. Restarting the container isn't updating the game files as far as I can tell, I'm probably going to try removing the container and deleting appdata again to see if it fixes it but as the game will probably receive a lot of frequent patches I thought I might ask if maybe the container isn't pinging for steamCMD updates on launch but only initial install? I tried the force update option on the container as well to no avail. Is there perhaps anything I can put in the GAME_PARAMS: to force check steamCMD for updates?

I just updated to Unraid 6.12.5 and am now unable to start or stop services from the docker dashboard. Is this a known issue? I can still open logs, info, the web ui, etc, but the start and stop functions don't work. EDIT/SOLVED! : Found the issue, the plugin Docker-Folder was causing this as it seems to no longer be supported.

I couldn't say with 100% confidence that my networking is configured entirely professionally, but only because I'm not super savvy on networking. Everything does seem to be working fine currently and maybe I'm speaking too soon but I think my issue has resolved. I'm about to hit 3 days uptime on the server without any issues, it's been getting used quite frequently this whole time, and typically by now, or by 24-48 hours the server would have crashed and I would have needed to hard reboot. I think what happened is this: Initially I missed a C state setting in Bios (C1E) which needed to be disabled. The gigabyte bios on my board unfortunately doesn't have any global c-state toggle and I happened to miss the C1E setting. I toggled it off but then thought it didn't resolve anything because at that same time is when I had flashed bios and the LAN drivers seemed to fail. So then I updated BIOS not realizing it essentially flashed bios again and booted it with all C states on, of course, with no success, making me think the C1E disable didn't change anything. Once I realized though that BIOS was back at default, and I never actually got a boot with C1E disabled, I reconfigured BIOS once again, this time with ALL C states off (as far as I can tell), and now the server is up for 3 days with no issues. I'll give it a week before I call it good but I feel confident right now that this was the issue and everything is now configured as it should be.

Alright, so still at the drawing board here. Server went unresponsive again today. I had the server booted into GUI mode with peripherals plugged in at the tower and the GUI was totally frozen. Completely inaccessible through LAN, but frozen at the tower itself. I rebooted and went to BIOS and noticed that none of my BIOS settings had saved. After flashing BIOS I'm sure I reconfigured but it may have been after the fact that I then updated BIOS, not sure if that essentially flashed it again to default values, so I'm once again making the BIOS changes and letting it run another 24-48hours or until crash. I re-enabled syslogs mirrored to flash, then, again if it fails this time I will try reseating CPU and RAM while I'm at it. I'm still so lost though I haven't the faintest clue what is causing this. Is it possible the MOBO is bad? The BIOS changes being unsaved is suspicious to me but because of the recent BIOS shenanigans I'm not sure if I can confirm whether or not it just completely failed to acknowledge changes. I've never received a bad MOBO so I'm not really sure what the tell tale signs are of a faulty one that seemingly works fine for up to at least 48 hours before just going ghost on you.

Yeah I'm not too sure what happened, I'm guessing flashing bios just messed up the LAN drivers since a BIOS upgrade solved it. I tried switching the rules but it just made it so the problem was reversed based off of which port I had my cable plugged into (scenario 1 became scenario 2 and vice versa). It's working as expected again and currently my network settings read eth0 1000 Mbps, full duplex, mtu 1500, eth1 interface down / [ shutdown (inactive) ] I have the server back up and am testing to see if it goes offline at or around 2days. I did have one server crash this morning and the RAM log% was at 100% so I rebooted, going to consider it a fluke for now and see what happens in the next coming days as its up and running at the moment. I think the logs were getting spammed with an error possibly related to my intel igpu being used as a transcoding device. The logs were spammed with: " kernel: get_swap_device: Bad swap file entry ############# " where # = a seemingly random string of letters and numbers

Sorry, I wasn't super clear, the card I'm talking about that the HDDs are plugged into isn't a PCI card or anything, it's built into the case and it just has slotted HDD connections that connect to the same amount of sata outputs on the other end, it's only purpose is to serve as cable management allowing you to connect your sata cables from a different position in the chassis . Speaking of network errors though, I have now ran into a whole new issue I might need to make a new thread for. I'm not very well versed with network configuring but after doing some memtests and toggling a setting in bios which seemed to be a mistake as I could no longer boot to BIOS, I flashed BIOS, reconfigured and relaunched into Unraid. However, my server now no longer has internet functionality. My mobo has two LAN ports and when I'm plugged into the same Ethernet port I was plugged into up to today I can't access the unraid GUI via LAN and have no internet access on the server, when I switch the Ethernet cable to the other (previously unused) LAN port I can access the unraid GUI via LAN but I still don't have internet access. I don't understand why this is, in my network settings it shows eth1 as inactive/shutdown but eth0 seems fine. I have no bridging or bonding between the ports as I am not savvy enough to understand it's function but on my first install of unraid I did disable bridging and bonding because with them enabled my network speeds on all devices in the network were terrible, once I turned off bridging and bonding devices were usable again. Anyway. Once again I'm at a loss. Another oddity of it all is that only when plugged into the second (previously unused) Ethernet port will I be able to see the tower listed as connected to the router, but even then it doesn't show up as an attached device, it only shows up in the list of attached devices when I hit the Access Control button in my router, then it is on a list of connected devices. to reiterate: Scenario 1: Connected to - LAN port 1 (previously used port) Unraid results - eth0 Interface Down, eth1 Interface Down (No internet access/no LAN GUI access) Scenario 2: Connected to - LAN port 2 (previously unused port) Unraid results - eth0 (1000mbs out, #mbs in) eth1 Interface Down (No internet access/Yes LAN GUI access) Before this my setup looked like: Connected to - LAN port 1 Unraid results - eth0 (1000mbs out, #mbs in), eth1 (I honestly don't remember if any information was displayed) (Yes internet access/Yes LAN GUI access) Edit: Updated to most current bios and networking started working again. *shrugs* I found a possible C state setting in BIOS I hadn't disabled (I think it was C1E) so that is disabled now and I'm going to see if the server stays up, I'll update if it works and if not I'll continue with testing CPU and reseating.

Ok I guess I'll reseat the cpu next, I never really thought that would be an issue, and I suppose I would still find it pretty surprising, I would think the only issue resulting in reseating a cpu would be from a bent pin or something of the sort but it's definitely worth a shot. I'll look into those two test, I suppose I'll reseat and see if the server stays online and if it goes offline I'll try a windows install and run some tests. The usb stick by the way I'm sure is 2.0 it's just that my motherboard only has 3.0 slots. Someone suggested buying a usb 2.0 cable/header that plugs into an open usb header on the mobo so I could probably do that I just wasn't sure how important it really was. And I did format the flash drives before trying to install unraid. They fell within the specs they just werent being recognized by the usb boot img creator tool for unraid. If the Rams good and the CPUs good I feel like I'm sort of running out of hardware to be suspect of. I have no gpu in the server, the hard drives all passed smart and I haven't got anything more than a few random udma crc errors which seem to just pop up and then instantly be resolved when running a test on the drives, so I've started to ignore those. ( loose sata connections I believe is the error, but the sata cables aren't loose). I imagine these maybe happen because the drives are plugged into a board within the case which then have sata connectors out for each drive, so sort of a third wheel at the party. These are far and few between but periodically one will pop up in the notifier for a random drive.

If it were anything hardware related I would have to put the odds on it being the cpu being that I did pick it up used, so I will definitely check this next though whats the best way to put the cpu to the test? Most I did before dropping it into the rig was boot it on a test bench into BIOS. Also I can do a windows install to test it if thats the best way, but theres no good way to test on linux? I actually thought Memtest also tested cpu. And I haven't had any warnings on thermals within unraid but I won't rule it out entirely. My HDD thermals have all been fine after some reconfiguring from the start when I did get 1 temp warning, the CPU I would think is doing fine on thermals being that it's almost always running at pretty low usage and I did drop a noctua cooler on the thing. Some additional information in case someone finds it may be pertinent to the problem: My mobo does not have usb 2.0 so the flash drive is plugged into usb 3.0 Also the flash drive is a cheapo 1 GB throwaway that came from a conference. I tried multiple other larger and what I would have considered more quality flash drives and they kept not having Unique Identifiers and whatnot so I just went with the one I had that it accepted.

So I ran memtest but it's limiting me to only 4 passes, I don't know how to run it longer than that/24 hours. 4 passes only took about 5 hours but it passed with 0 errors. I'll run it again, is running it multiple times at all equivalent to just running it for an extended amount of time? since I'm limited to 4 passes that's all I can really see to do. 4/4 passes 0 errors 8/8 passes 0 errors 12/12 passes 0 errors 16/16 passes 0 errors