MarshallU

Members
  • Posts

    25
  • Joined

  • Last visited

MarshallU's Achievements

Noob

Noob (1/14)

3

Reputation

  1. Yeah I got that bit, but I will also have to give up one of my 4 TB drives for a 12 TB, would it be best to just copy the data off that 4 to the 12?
  2. Okay that’s at least a start. If I go down to a single parity drive, I’ll have room for 5 data drives. So I could have the other two 12 TB + three of the 4 TB. That would be my preferred setup. So my two 4 TB parity drives will be no more, then the one 4 TB drive in the data array, do I just need to hard copy all the files off it to one of the 12 TB drives?
  3. Hey y’all, wanted to get some opinions on best route to take for some upgrades. I currently have 2 x 4 TB parity drives and 4 x 4 TB data drives. I have reached 100% utilization finally. I bought 3 x 12 TB drives last Black Friday but haven’t put them in. I would like to move the parity drives to a single 12 TB drive and also upgrade 2 of the data drives to 12 TB as well. What would be the best way to go about this upgrade? This will be my first hardware upgrade since starting up my server so I want to do it right. thanks all!
  4. It did just finally update to the newest version now. Thanks for confirming everything and appreciate your work on this docker!!
  5. Here's the log after restart if helpful. I deleted the majority of parts with progress status for brevity. The last line showed up as a warning. ---Ensuring UID: 99 matches user--- usermod: no changes ---Ensuring GID: 100 matches user--- usermod: no changes ---Setting umask to 000--- ---Checking for optional scripts--- ---No optional script found, continuing--- ---Taking ownership of data...--- ---Starting...--- ---Update SteamCMD--- Redirecting stderr to '/serverdata/Steam/logs/stderr.txt' [ 0%] Checking for available updates... [----] Verifying installation... Steam Console Client (c) Valve Corporation - version 1654574676 -- 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--- ---Validating installation--- Redirecting stderr to '/serverdata/Steam/logs/stderr.txt' [ 0%] Checking for available updates... [----] Verifying installation... Steam Console Client (c) Valve Corporation - version 1654574676 -- 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 state (0x3) reconfiguring, progress: 0.00 (0 / 0) Update state (0x5) verifying install, progress: 0.22 (41912944 / 18788585748) ... Update state (0x61) downloading, progress: 100.00 (806 / 806) Success! App '376030' fully installed. Update state (0x5) verifying install, progress: 98.68 (18541218256 / 18788585748) Update state (0x61) downloading, progress: 100.00 (806 / 806) Success! App '376030' fully installed. ---Prepare Server--- ---Server ready--- ---Start Server--- [S_API FAIL] SteamAPI_Init() failed; SteamAPI_IsSteamRunning() failed.
  6. I will try again to make sure. I have adblocking on my desktop, but no adblocking docker or anything for the network level.
  7. Hi all, Brand new with running gameserver dockers here so bit of a newb question. I am running ArkSE server container and it was doing just fine for the last 2 weeks, but now Steam has pushed out a new patch version. When I go to log in to my server, it is not showing up, because it is still running the old patch. I restarted the container but this did not fix the issue. How can I force the container to be running the new patch version to match steam? Thanks!!
  8. Saiba, I'm having the same issue. I backed up my world and reset all the non-relevant chunks using the MCA editor program. Now I'm trying to move my server to 1.17 in MineOS and it will not start. I have seen other instances of this happening - looks like it could be some incompatibility with the old version of java.. Need some help to get this resolved though - just wanted to let you know you are not alone
  9. Hey all, I have an issue with my cache drives - they are showing up as read only which is causing all dockers to act up. I have tried a few common fixes seen on the forums like rebalancing the cache but haven't seen any success yet. Wondering if someone can look at the diagnostics file and see if there are any other thing I can try. I also got this error that I've never seen when I tried to write the diagnostic file. Thanks! usreymedia-diagnostics-20210306-1330.zip
  10. Hey Jorge - wanted to let you know it looks like this solution worked. I changed the RAM speed to 2400 MHz in the BIOS (updated BIOS while I was at it) Then ran 2 back to back parity checks. The first still found and corrected about 1000 errors, the second was completely clean. Thanks so much for your help!
  11. Thanks, Jorge, appreciate the tip. Just to make sure - I am running a 2nd gen Ryzen with 2 of 4 DIMS (dual channel) populated, so I should set my mem frequency to 2400 MHz in BIOS? Would you suggest running any more tests other memtest if that doesn't help?
  12. Small numbers of parity sync errors were corrected starting about a month ago - now I have ran a few within the last week with several thousand errors being "corrected". If they're being corrected, shouldn't they not appear on the next scan? Unless there is a hardware issue that is causing this. Posted my diagnostic file if anyone wants to take a look and can figure out what might be causing this. I'm having trouble starting VMs and wondering if the drive space for them might be corrupted? Thanks in advance! usreymedia-diagnostics-20210224-1050.zip
  13. Thank you, I will try that! The disk has a three year warranty of which only 1 year is used - so if worse comes to worse I am covered for a replacement. Thanks for looking over the data!
  14. I had this same issue happen to me today - one drive shows up as disabled - contents emulated. I'm attaching the SMART report here so someone can review it. It shows "Passed" on the overall health assessment. Parity check was performed 3 days ago with 0 errors. Any help would be appreciated! This is the first time I have come across this situation in Unraid. ST4000VN008-2DR166_ZDH7GQYQ-20200830-1326.txt