MarshallU

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?

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?

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!

It did just finally update to the newest version now. Thanks for confirming everything and appreciate your work on this docker!!

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.

I will try again to make sure. I have adblocking on my desktop, but no adblocking docker or anything for the network level.

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!!

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

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!

Here you go: usreymedia-diagnostics-20200831-1128.zip

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

Okay so I opened the terminal for Unraid on my system and did the Ifconfig command again and here are the results: Linux 4.18.20-unRAID. root@UsreyMedia:~# ifconfig bond0: flags=5443<UP,BROADCAST,RUNNING,PROMISC,MASTER,MULTICAST> mtu 1500 inet6 fe80::6d4:c4ff:fe57:4e55 prefixlen 64 scopeid 0x20<link> ether 04:d4:c4:57:4e:55 txqueuelen 1000 (Ethernet) RX packets 72344418 bytes 54455395648 (50.7 GiB) RX errors 0 dropped 0 overruns 235 frame 0 TX packets 65535197 bytes 42700854453 (39.7 GiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 br0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.1.8 netmask 255.255.255.0 broadcast 0.0.0.0 inet6 fe80::20de:c2ff:feca:eeb1 prefixlen 64 scopeid 0x20<link> ether 04:d4:c4:57:4e:55 txqueuelen 1000 (Ethernet) RX packets 57499139 bytes 53057311704 (49.4 GiB) RX errors 0 dropped 288 overruns 0 frame 0 TX packets 60361649 bytes 42367326612 (39.4 GiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 docker0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 172.17.0.1 netmask 255.255.0.0 broadcast 172.17.255.255 inet6 fe80::42:bff:fef7:e2bf prefixlen 64 scopeid 0x20<link> ether 02:42:0b:f7:e2:bf txqueuelen 0 (Ethernet) RX packets 52046581 bytes 29530460190 (27.5 GiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 68956108 bytes 53570993784 (49.8 GiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 eth0: flags=6211<UP,BROADCAST,RUNNING,SLAVE,MULTICAST> mtu 1500 ether 04:d4:c4:57:4e:55 txqueuelen 1000 (Ethernet) RX packets 72344422 bytes 54455396220 (50.7 GiB) RX errors 0 dropped 0 overruns 235 frame 0 TX packets 65535203 bytes 42700859352 (39.7 GiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device memory 0xf6500000-f651ffff lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10<host> loop txqueuelen 1000 (Local Loopback) RX packets 4644616 bytes 5287958283 (4.9 GiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 4644616 bytes 5287958283 (4.9 GiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 veth1114cec: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet6 fe80::e4ad:1eff:fefc:1397 prefixlen 64 scopeid 0x20<link> ether e6:ad:1e:fc:13:97 txqueuelen 0 (Ethernet) RX packets 104377 bytes 13762126 (13.1 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 79196 bytes 19082322 (18.1 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 veth24170d5: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet6 fe80::d9:89ff:fe69:6c9 prefixlen 64 scopeid 0x20<link> ether 02:d9:89:69:06:c9 txqueuelen 0 (Ethernet) RX packets 68243 bytes 596845800 (569.1 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 161491 bytes 407691023 (388.8 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 veth8130a5e: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet6 fe80::1487:90ff:fe6f:bb13 prefixlen 64 scopeid 0x20<link> ether 16:87:90:6f:bb:13 txqueuelen 0 (Ethernet) RX packets 188914 bytes 27153799 (25.8 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 217239 bytes 82407082 (78.5 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 veth832a600: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet6 fe80::6830:79ff:fe5b:85a5 prefixlen 64 scopeid 0x20<link> ether 6a:30:79:5b:85:a5 txqueuelen 0 (Ethernet) RX packets 45441742 bytes 27341002496 (25.4 GiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 48489479 bytes 36406310841 (33.9 GiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 veth8680b10: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet6 fe80::5cde:b5ff:fee9:c77f prefixlen 64 scopeid 0x20<link> ether 5e:de:b5:e9:c7:7f txqueuelen 0 (Ethernet) RX packets 996 bytes 1503463 (1.4 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 1365 bytes 715255 (698.4 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 veth91db3b1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet6 fe80::458:d9ff:fece:12b1 prefixlen 64 scopeid 0x20<link> ether 06:58:d9:ce:12:b1 txqueuelen 0 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 2288 bytes 389239 (380.1 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 vethb3876c8: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet6 fe80::546e:86ff:feef:e038 prefixlen 64 scopeid 0x20<link> ether 56:6e:86:ef:e0:38 txqueuelen 0 (Ethernet) RX packets 93193 bytes 20790815 (19.8 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 77287 bytes 50350863 (48.0 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 virbr0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500 inet 192.168.122.1 netmask 255.255.255.0 broadcast 192.168.122.255 ether 52:54:00:46:9e:b9 txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

I opened the console for the docker in Unraid, ran the ifconfig. See attached. Couldn't copy/paste for some reason so took a screenshot of it. It's reporting eth0 inet of 172.17.0.2 Even though when I set it up, I specied LAN network 192.168.1.0/24 as the LAN_NETWORK variable. I'm not sure if this is causing the discrepancy.. Let me know what you think. Thanks!

Here's my supervisord.log file from today after setting debug to "true" and restarting the docker. Very long so uploading instead of copy/pasting. I changed my PIA username and password to "username" and "password" for this version of the log file just in case Thanks in advance! supervisord log 1.8.2020.txt

Okay will do, thank you!