StephenCND

Ok, array reconstruction complete. Rebooted the array and all of my plugins and Dockers are gone. How do I reinstall them? Do I have to reinstall them all individually? I don't even have access to community plugins at this point. A bit lost here...

Thanks itimpi. I am now going through the process of rebuilding the array, but it's going to be a while yet before it's completed. I did notice however when I go to the Docker tab there are no dockers installed. The page says "No Docker containers installed". Is it safe to assume they will appear once the Parity-Sync/Data Rebuild is completed, or is there an issue here? Do I have to do an additional step after the array is rebuilt?

My UPS crapped out on me at a very bad time, and to make a long story short, I had to replace my USB key and get a new registration key (Both of which have been done). Version 6.9.2 has now been installed. (I had made a backup of that USB key and stored on my other PC but it is about one year old). Since then I have added a couple of new drives. Here is where I am at: Unraid array is of course not started. It is asking that I assign drives. I can figure out which 2 drives I used for my cache drive pool, but I am at a loss for what constituted my data drives and my parity drives. Now is there a way to: a). Peek into the drives and see if there is any data stored in there. and or b). I have a old backup of the USB drive. Is there a file in there that could give me a hint as to what drives were used for the parity or data drives? Or, am I missing a much easier solution? I'm very hesitant to start adding drives blindly (I have 6 drives that need to be assigned, either to the data pool, or the parity drives). Any assistance would be greatly appreciated.

Well, the situation has changed a bit. I decided shortly after placing this post to simply reboot (warm boot) the server. It restarted normally, and the cashe pool was recognized and functioning properly. So.. I'm going to assume everything is ok (or until the problem repeats itself). Ps., you mentioned auto start.. at this point do I leave "Enable auto start:" to "Yes" in the "Disk Settings" ?

Oh boy, I seem to have an issue with my cache pool once more. For no apparent reason, the cache pools were no longer recognized. As a result, the system took the array off-line. . To make matters even worse, I rebooted the server and now, I cannot even connect. I have no idea what is going on .. Any assistance would be greatly apppreciated.

Out of the blue, for no reason, I cannot open a WebUI page to Binhex_DelugeVPN. Tried restarting the docker, stopping and reopening, tried rebooting the computer I am trying to connect to Deluge from, but nothing works. The Deluge Docker itself says it's running, but I cannot open a WebUI page to it.. the browser says "This site can’t be reached. 192.168.1.95 refused to connect". I even went over SpaceInvader's tutorial on the installation of the Docker to see if I missed anything. There have been no changes to the settings, or port forwarding. I tried uninstalling and reinstalling but same issue. Don't see anything unusual in the Deluge log file (included) . Any assistance regarding this matter will be greatly appreciated. Deluge_Log.txt

Ports have been forwarded. I put in my IPv4 and added the server from within the game server browser. The game server browser can see my server now (but not the Steam Game Browser, which is file). I think everything is up and running now. Thanks again for all your help ich777 .

But that is an internal LAN IP... if I want to have someone join the server from the internet, that wouldn't work, right? I did add my internal IP to the server list within "favorites" and that worked, but when I refresh, it did not populate within the larger servers list tab. I was able to connect to it from my computer on the same lan, but again, will other computers outside my lan (internet) be able to connect if I only give them my LAN IP address and port? I feel we are very close to getting this to work here..

I have removed my Steam credential (user name and password) from the docker's template in the "Show more settings" section . You are correct, I was talking about the in game (server) list. It doesn't show up there (even after removing my Steam User name and Password as mentioned above. I did access the Steam Server Browser, (didn't know that it existed) but my server isn't lisited there either. Appart from the Docker Set-up and the server.cfg, is there another file or setting i needed to set up?

Doesn't loop. Smooth start and stop for that matter. I've included two screen captures of the Docker template (top portion & bottom portion) to make it easier to read. (note, I blacked-out the Steam Username). The appdata folder is set to "Prefer:Cache" I'm also including a screen capture of my Array devices and Pool (cache) devises if that can be of assistance. I've also included my server.cfg file. I really appreciate the time and effort you've put into my problem. Thanks again. server.cfg

I've removed and re-installed the docker (again). Seems all the required files got downloaded and installed. Can get the docker to run... but same issue.. When I start the game through Steam, it doesn't show up in the games server list. I've included the Docker's log file. logfile.txt

Well, I'm at a bit of a loss: Uninstalled and re-Installed. Seems to have installed correctly, however there is only have a "steamapps" folder inside the "insurgency" folder. I also installed the docker for Killingfloor game server (to see how it would install) . Same issue.. just one folder installed inside the killingfloor folder (steamapps) .

I have a an array of 1TB on an SSD drive. The appdata folder is set to Prefer : Cache . I'm going to start over as you suggested and see what happens. Will keep you posted once done.

It's Insurgency (not Insurgency Sandstorm). I am on Unraid version 6.10.3 No changes were made during the setup. I can start the docker and it shows as started. Could it be an issue with the server.cfg file? (Please find attached) server.cfg

I am having issues running the Insurgency Game Server Docker. It seems to have installed correctly. I can get it to run. I have created a "server.cfg" file in which I have named the server, password, etc, and placed it in the appropriate folder ( ..appdata/insurgency/insurgency/cfg/), however, when i start the game in Steam and go looking for the server I created, it does not show up anywhere. The log file seems there might be an issue with running Steam: "[S_API FAIL] SteamAPI_Init() failed; SteamAPI_IsSteamRunning() failed. [S_API FAIL] SteamAPI_Init() failed; unable to locate a running instance of Steam, or a local steamclient.so." I have included the entire log as an attachment. Am I missing a step? Any assistance would be greatly appreciated. Insurgency_Log.txt

Anyone have any suggestions ?

EDIT: Seems I have got it to run. Server says it's up and running, but how do I configure the server (ie., name it, set the parameters, etc..?) I was able to do it in 7 Days to Die by editing a server config file, but not sure for this game Docker. Any assistance would be greatly appreciated. I've also included the log file (attachment), which tends to make me believe it's NOT running correctly Insurgency_Log.txt

That seems to have done it. Much appreciated JorgeB !

O K..., and when you say "unassign", you mean I set the both caches to "no device". Sorry ... still learning here....

Here you go. nasterminal1-diagnostics-20220812-1115.zip

I recently upgraded my cache pool from two 256GB SSD's to two 1TB SSD's (Followed SpaceInvaders video tutorial to do so.) Everything seems to have worked just fine, however, upon rebooting the server today, the Dashboard tab is saying the cache array is stopped . On the Main tab under the "Device" column, the Caches have a red "x" next to them and the word "Wrong". In the "Array Operation" the array is indicated as "Stopped. Configuation valid". On both the Dashboard and Main tab, at the very bottom, it is marked "Array Stopped Autostart disabled (device configuration change). Nothing really changes once I start the array, both the Main and Dashboard tabs have the same error messages, although the array seems to be working fine. To tell you the truth, I'm not sure where to look to troubleshoot this issue. I suspect it's perhaps just a setting that has to be changed somewhere. Any assistance would be greatly appreciated.

Not sure why this is happening. It happened on occasion before, but that was when too many Dockers happen to be running at the same time. And it's not like I am streaming anything .... it's just open with no clients. I should add, that the CPU usage goes to 100% on all cores when I open a WebUI page from the Docker tab from a computer in my home network, but it will remain normal if I run Plex from my TV's Amazon Firestick. Below is the Plex log. ps., sorry if I put this in General forum, and not the Docker forum. It's greyed-out for me and I do not have access. -=-=-=-=-=-=-=-=-= text error warn system array login kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec] kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec] kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec] kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec] [s6-finish] sending all processes the TERM signal. [s6-finish] sending all processes the KILL signal and exiting. [s6-init] making user provided files available at /var/run/s6/etc...exited 0. [s6-init] ensuring user provided files have correct perms...exited 0. [fix-attrs.d] applying ownership & permissions fixes... [fix-attrs.d] done. [cont-init.d] executing container initialization scripts... [cont-init.d] 40-plex-first-run: executing... [cont-init.d] 40-plex-first-run: exited 0. [cont-init.d] 45-plex-hw-transcode-and-connected-tuner: executing... [cont-init.d] 45-plex-hw-transcode-and-connected-tuner: exited 0. [cont-init.d] 50-plex-update: executing... [cont-init.d] 50-plex-update: exited 0. [cont-init.d] done. [services.d] starting services Starting Plex Media Server. [services.d] done. Stopping Plex Media Server. [cont-finish.d] executing container finish scripts... [cont-finish.d] done. [s6-finish] waiting for services. [s6-finish] sending all processes the TERM signal. [s6-finish] sending all processes the KILL signal and exiting. [s6-init] making user provided files available at /var/run/s6/etc...exited 0. [s6-init] ensuring user provided files have correct perms...exited 0. [fix-attrs.d] applying ownership & permissions fixes... [fix-attrs.d] done. [cont-init.d] executing container initialization scripts... [cont-init.d] 40-plex-first-run: executing... [cont-init.d] 40-plex-first-run: exited 0. [cont-init.d] 45-plex-hw-transcode-and-connected-tuner: executing... [cont-init.d] 45-plex-hw-transcode-and-connected-tuner: exited 0. [cont-init.d] 50-plex-update: executing... [cont-init.d] 50-plex-update: exited 0. [cont-init.d] done. [services.d] starting services Starting Plex Media Server. [services.d] done. Stopping Plex Media Server. [cont-finish.d] executing container finish scripts... [cont-finish.d] done. [s6-finish] waiting for services. [s6-finish] sending all processes the TERM signal. [s6-finish] sending all processes the KILL signal and exiting. [s6-init] making user provided files available at /var/run/s6/etc...exited 0. [s6-init] ensuring user provided files have correct perms...exited 0. [fix-attrs.d] applying ownership & permissions fixes... [fix-attrs.d] done. [cont-init.d] executing container initialization scripts... [cont-init.d] 40-plex-first-run: executing... [cont-init.d] 40-plex-first-run: exited 0. [cont-init.d] 45-plex-hw-transcode-and-connected-tuner: executing... [cont-init.d] 45-plex-hw-transcode-and-connected-tuner: exited 0. [cont-init.d] 50-plex-update: executing... [cont-init.d] 50-plex-update: exited 0. [cont-init.d] done. [services.d] starting services Starting Plex Media Server. [services.d] done. Stopping Plex Media Server. [cont-finish.d] executing container finish scripts... [cont-finish.d] done. [s6-finish] waiting for services. [s6-finish] sending all processes the TERM signal. [s6-finish] sending all processes the KILL signal and exiting. [s6-init] making user provided files available at /var/run/s6/etc...exited 0. [s6-init] ensuring user provided files have correct perms...exited 0. [fix-attrs.d] applying ownership & permissions fixes... [fix-attrs.d] done. [cont-init.d] executing container initialization scripts... [cont-init.d] 40-plex-first-run: executing... [cont-init.d] 40-plex-first-run: exited 0. [cont-init.d] 45-plex-hw-transcode-and-connected-tuner: executing... [cont-init.d] 45-plex-hw-transcode-and-connected-tuner: exited 0. [cont-init.d] 50-plex-update: executing... [cont-init.d] 50-plex-update: exited 0. [cont-init.d] done. [services.d] starting services Starting Plex Media Server. [services.d] done. Stopping Plex Media Server. [cont-finish.d] executing container finish scripts... [cont-finish.d] done. [s6-finish] waiting for services. [s6-finish] sending all processes the TERM signal. [s6-finish] sending all processes the KILL signal and exiting. -=-=-=-=-=-=

I Believe I was able to get it up and running. Not sure why it worked this time around .. but let's not look a gift horse in the mouth as they say.

Ya... I went to the Docker tab, then the 7Days to Die docker, and went to "Support" . Got to the place you linked, but I was unsure if I should select "Reply to this Topic" or "Start New Topic" (in the upper right hand corner of the page). I figured I'm not replying to a topic, I'm creating one so I went there. Once in there, I had to select from a pull down menu and select a forum. The "Docker Container" forum is greyed-out and not selectable for me (I'm guessing it's reserved for Devs?), so I was forced to select the next closest thing (Docker Engine). Sorry if I messed things up for a simple post .... but I hate to say it's not that intuitive to post in here!

? ... because, you told me to do it through the Web UI and clicking Support