TBG_Killer

Members
  • Posts

    10
  • Joined

  • Last visited

Recent Profile Visitors

261 profile views

TBG_Killer's Achievements

Noob

Noob (1/14)

1

Reputation

  1. That seemed to work! The container is staying up now. Thank you very much!
  2. Hello, my ASA server was working (I also run a 12 map cluster of ASE that has been running for months). Shortly after adding 2 ASA servers, my main box/server has been crashing. I had to re-create my zpool to get the ASE cluster working again. However, I can't seem to get ASA working. I have tried an entirely new container with default settings and still get the following error. Does ASA now need a path for a "Windows" directory? Or, perhaps I need to re-create my shares? Sorry, this may not be an ich777 issue. Just thought I'd ask. text error warn system array login ---Ensuring UID: 99 matches user--- ---Ensuring GID: 100 matches user--- ---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' Logging directory: '/serverdata/Steam/logs' [ 0%] Checking for available updates... [----] Verifying installation... Steam Console Client (c) Valve Corporation - version 1702079268 -- type 'quit' to exit -- Loading Steam API...dlmopen steamservice.so failed: steamservice.so: cannot open shared object file: No such file or directory OK Connecting anonymously to Steam Public...OK Waiting for client config...OK Waiting for user info...OK ---Update Server--- Redirecting stderr to '/serverdata/Steam/logs/stderr.txt' Logging directory: '/serverdata/Steam/logs' [ 0%] Checking for available updates... [----] Verifying installation... Steam Console Client (c) Valve Corporation - version 1702079268 -- type 'quit' to exit -- Loading Steam API...dlmopen steamservice.so failed: steamservice.so: cannot open shared object file: No such file or directory OK "@sSteamCmdForcePlatformType" = "windows" Connecting anonymously to Steam Public...OK Waiting for client config...OK Waiting for user info...OK Success! App '2430930' already up to date. ---Checking the maximum map count per process...--- ---Maximum map count per process OK...--- ---Current map count per process: 265000--- ---Checking if WINE workdirectory is present--- ---WINE workdirectory found--- ---Checking if WINE is properly installed--- ---WINE properly set up--- ---Prepare Server--- ---Server ready--- ---Start Server--- Waiting for logs... wine: could not open working directory L"C:\\windows\\system32\\", starting in the Windows directory. wine: could not open working directory L"C:\\windows\\system32\\", starting in the Windows directory. wine: could not load kernel32.dll, status c0000135 Waiting for logs... Waiting for logs... Waiting for logs... Waiting for logs... Waiting for logs... Waiting for logs... Waiting for logs... Waiting for logs... Waiting for logs... No log files found after 20 seconds, putting container into sleep mode!
  3. Following, as I have the same issue. newperms fixes the issue temporarily. However, some folders loose their permissions over time. I mostly see this in my steam library. Steam is able to find a game but doesn't have permission to update it. I run newperms on the game folder and then steam can update that game. Later, steam tries to update the same game and no longer has permission. Also, my files/folders were copied from a windows machine. Please tell me there is a fix for this (other than deleting and starting over on the unraid server).
  4. That worked! Man, this unRAID is sweet. Thanks so much for the help and quick responses!
  5. Now that I think about it. How would you remove a drive from the array without destroying it? I'm sure 1 at a time. However, if I could force the array to act like it only had 6 drives in the array, I think it might work. I just don't know how to modify the array that way.
  6. Thanks for that. However, won't that wipe the remaining drives in the array? I forgot to mention that these are the last 4 drives of 12 total (2 parity and 10 for the array). I have data on the first two drives in the array that I wish to keep. Is there a way to start the array without the failed drives and get the data off? I could then rebuild the array and move the data back.
  7. I just fried 4 drives at once (my fault, used a molex PSU cable from the wrong PSU). All of the drives that failed were empty on the array. I have 2 parity drives. Is there a way to sneak 4 new/blank drives back into the array?