k2trf

Thank you so much -- I still never figured out where I went wrong with that, but you've saved me a ton of headache either way! ^_^

Could you push an update for SkyFactory One? For whatever reason, the 1.0.4 client is crashing for me, while the 1.0.5 client runs just fine, but says the server is mismatched on modlist (I believe the server is 1.0.4, though I don't know if the modlist actually differs from the versions). I tried upgrading the docker enviornment manually, according to the UPDATE-GUIDE.txt file, * didn't bother making backups, because this was a fresh install & there's nothing to backup * downloaded the server file for 1.0.5 from curseforge (https://www.curseforge.com/minecraft/modpacks/skyfactory-one/files/3652066) * merged the structure on the server, so I could run the install script on the desktop * ran the install script, told it for a server, in that directory, it ran fine according to the output * uploaded everything back to the server, including the libraries, and tried running the server At first, it had a permission error on the forge-1.16.5-36.2.28.jar file (I guess either the installer didn't give it perms or filezilla stripped them, but just them apparently), but after fixing that, the output log still shows like it can't access the file. + cd /data + [[ true = \f\a\l\s\e ]] + echo eula=true + [[ -f SkyFactory_One_Server_1_0_4.zip ]] + [[ -n SkyFactoryOne, now with RFC2321! ]] + sed -i '/motd\s*=/ c motd=SkyFactoryOne, now with RFC2321!' /data/server.properties + [[ -n world ]] + sed -i '/level-name\s*=/ c level-name=world' /data/server.properties + [[ -n mesmerus ]] + echo mesmerus + awk -v RS=, '{print}' + . ./settings.sh ++ export $'INSTALL_JAR=forge-1.16.5-36.2.28-installer.jar\r' ++ INSTALL_JAR=$'forge-1.16.5-36.2.28-installer.jar\r' ++ export $'SERVER_JAR=forge-1.16.5-36.2.28.jar\r' ++ SERVER_JAR=$'forge-1.16.5-36.2.28.jar\r' ++ export $'JAVA_JAR=\r' ++ JAVA_JAR=$'\r' ++ $'\r' ./settings.sh: line 6: $'\r': command not found ++ export $'MIN_RAM=1024M\r' ++ MIN_RAM=$'1024M\r' ++ export $'MAX_RAM=4096M\r' ++ MAX_RAM=$'4096M\r' ++ export 'JAVA_PARAMETERS=-XX:+UseG1GC -Dsun.rmi.dgc.server.gcInterval=2147483646 -XX:+UnlockExperimentalVMOptions -XX:G1NewSizePercent=20 -XX:G1ReservePercent=20 -XX:MaxGCPauseMillis=50 -XX:G1HeapRegionSize=32M -Dfml.readTimeout=180' ++ JAVA_PARAMETERS='-XX:+UseG1GC -Dsun.rmi.dgc.server.gcInterval=2147483646 -XX:+UnlockExperimentalVMOptions -XX:G1NewSizePercent=20 -XX:G1ReservePercent=20 -XX:MaxGCPauseMillis=50 -XX:G1HeapRegionSize=32M -Dfml.readTimeout=180' + curl -o log4j2_112-116.xml https://launcher.mojang.com/v1/objects/02937d122c86ce73319ef9975b58896fc1b491d1/log4j2_112-116.xml % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed + java -Xms2048m -Xmx8096m -XX:MaxPermSize=256M -Dlog4j.configurationFile=log4j2_112-116.xml -jar $'forge-1.16.5-36.2.28.jar\r' nogui Error: Unable to access jarfile forge-1.16.5-36.2.28.jar I don't know why it can't access it, because it is present, and as far as I know the permissions are fine. I've also tried setting the owner as nobody:nobody and nobody:users, just to make sure that wasn't the case, but no dice. total 158M drwxrwxrwx 1 1000 1000 264 May 8 05:57 ./ drwxrwxrwx 1 nobody users 4.0K May 8 04:02 ../ -rw-r--r-- 1 1000 1000 180 May 8 05:46 Install.bat -rwxr-xr-x 1 1000 1000 212 May 8 05:46 Install.sh* -rw-r--r-- 1 1000 1000 608 May 8 05:46 NOTES.txt -rw-r--r-- 1 1000 1000 2.8K May 8 05:46 README.txt -rw-r--r-- 1 1000 1000 1.6K May 8 05:46 README_ISLANDS.txt -rw-r--r-- 1 1000 1000 775 May 8 05:46 ServerStart.bat -rwxr-xr-x 1 1000 1000 1.5K May 8 05:46 ServerStart.sh* -rw-r--r-- 1 1000 1000 930 May 8 05:46 ServerStartJava14.bat -rw-r--r-- 1 1000 1000 103M May 8 04:07 SkyFactory_One_Server_1_0_4.zip -rw-r--r-- 1 1000 1000 1.3K May 8 05:46 UPDATE-GUIDE.txt -rw-r--r-- 1 1000 1000 2 May 8 04:57 banned-ips.json -rw-r--r-- 1 1000 1000 2 May 8 04:57 banned-players.json drwxrwxrwx 1 1000 1000 4.0K May 8 05:13 config/ drwxrwxrwx 1 1000 1000 4.0K May 8 05:13 defaultconfigs/ -rw-r--r-- 1 1000 1000 10 May 8 05:57 eula.txt -rwxr-xr-x 1 1000 1000 7.1M Dec 10 12:18 forge-1.16.5-36.2.20-installer.jar* -rw-r--r-- 1 1000 1000 1.8M May 8 04:16 forge-1.16.5-36.2.20-installer.jar.log -rwxr-xr-x 1 1000 1000 208K May 8 04:07 forge-1.16.5-36.2.20.jar* -rwxr-xr-x 1 1000 1000 7.6M May 8 05:46 forge-1.16.5-36.2.28-installer.jar* -rwxrwxrwx 1 1000 1000 208K May 8 05:46 forge-1.16.5-36.2.28.jar* drwxrwxrwx 1 1000 1000 40 May 8 05:13 global_data_packs/ drwxrwxrwx 1 1000 1000 27 May 8 05:13 global_resource_packs/ -rw-rw-rw- 1 1000 1000 1.8M May 8 05:46 installer.log drwxr-xr-x 1 1000 1000 46 May 8 04:21 journeymap/ drwxr-xr-x 1 1000 1000 50 May 8 04:07 libraries/ -rw-r--r-- 1 1000 1000 1.2K May 8 05:57 log4j2_112-116.xml drwxr-xr-x 1 1000 1000 78 May 8 04:53 logs/ -rwxr-xr-x 1 1000 1000 37M May 8 05:46 minecraft_server.1.16.5.jar* drwxrwxrwx 1 1000 1000 81 May 8 05:13 mods/ -rw-r--r-- 1 1000 1000 136 May 8 04:57 ops.json -rw-r--r-- 1 1000 1000 70 May 8 05:57 ops.txt -rw-r--r-- 1 1000 1000 10 May 8 04:53 ops.txt.converted drwxrwxrwx 1 1000 1000 23 May 8 05:13 packmenu/ drwxr-xr-x 1 1000 1000 6 May 8 04:18 patchouli_books/ -rw-r--r-- 1 1000 1000 14K May 8 05:46 server-icon.png -rw-r--r-- 1 1000 1000 1.2K May 8 05:57 server.properties -rw-r--r-- 1 1000 1000 484 May 8 05:46 settings.bat -rwxr-xr-x 1 1000 1000 568 May 8 05:46 settings.sh* -rw-r--r-- 1 1000 1000 107 May 8 04:57 usercache.json -rw-r--r-- 1 1000 1000 137 May 8 04:31 whitelist.json drwxr-xr-x 1 1000 1000 98 May 8 05:07 world/ Clearly, I'm doing something wrong, but I don't know what, but if you can just push an update for 1.0.5 on SkyFactory One, it'd save me the headache & update the server, since the update is available. Thanks for help in either direction!

You guys had it! Somehow, 0 and 1 must be my parity drives, because 2 and 3 immediately mounted with their xfs partitions, and I seem to have the bulk of my stuff! Definate *doh* moment! Thanks guys

The sdX I'm referencing is when I pop them into my workstation -- I know which drives are which in unRAID before they are mounted, not paying attention to the sdX, but rather the drive assignment (Parity 1, Parity 2, Array 1, etc.), and that hasn't ever changed on me through reboots, shutdowns, etc. My workstation seems to just sort by UUID, alphabetically. Which makes my boot ssd sda, my two extracted drives from unRAID sdb and sdc, and my /home hdd sdd. Kinda funny in a way! EDIT: I'll be able to try throwing the other drives in when I have time later this evening. They're not very difficult to mount to the sleds, though it isn't toolless for 2.5" drives. Once I do that, regardless of the outcome, I'll come back, so we can hopefully start to get a bigger picture, because johnnie and you have made good points; I may be trying to look at two parity drives. Just because I'm pretty sure of what I'm doing doesn't mean I'm right!

In the case of the tail, I only attempted to mount sdb, since both drives produce the same output it seemed redundant. I'm fairly sure its not the parity -- I set the disks in unRAID to follow the numbering on the R610 face; 0, 1, 2, 3 were my four data drives (1-4 respectively), with 4 and 5 being parity one and two. Can always try the others when I have time later today, but I simultaneously don't think that likely, but also hear your logic, since even gparted shows them as unknown fs types. :\

Due to moving, I can't run my unRAID server for the near future. Most of my data is on two of the drives in my array though, and my workstation has two "hot swap tray" bays (not really hot swap, but means no side panels have to be messed with). Figured this was lucky, as I know all my drives in the pool are just xfs, and I know exactly which of my drives is which physically and in unraid. Threw them into the workstation, Ubuntu 16.04 LTS, and found that it won't mount the damn things. Running `syslog | tail` after trying shows the following, for both sdb, sdb1, sdc and sdc1 (the two drives in question, with one partition each). ┌─[ $ ]─[ k2trf@desktop ]───[ Wed Dec 27 | 23:43:58 ]───[ ~ ] └─> dmesg | tail [ 41.296933] userif-3: sent link up event. [ 43.913444] userif-3: sent link down event. [ 43.913451] userif-3: sent link up event. [ 79.096560] sdb: sdb1 [ 79.098099] sdc: sdc1 [ 372.615530] SGI XFS with ACLs, security attributes, realtime, no debug enabled [ 381.557248] sdb: sdb1 [ 381.559387] sdc: sdc1 [ 667.199182] XFS (sdb1): Invalid superblock magic number [ 681.848472] XFS (sdb): Invalid superblock magic number I am running (or I suppose was since it isn't currently up...) a 6.4 prerelease. I'd just updated as much as I could before the final shutdown, I want to say 6.4_rc17? That may not be right, but it's a close ballpark. I know for fact all the array drives were xfs (the system was initialized well back, sometime just prior to 6.2 IIRC), and all my drives have a relatively low pwron hours, with no SMART issues, nominal health, etc. before the final shutdown. They're both 1TB HGST 2.5" drives (R610 only slots 2.5" sadly), so I'm not entirely sure what to make of it. Installed xfsdump and xfsprogs, as I realized I didn't have them, and rebooted, but the tail shows the same. I've not tried reading the disks directly like this prior, but was aware that it was a fairly simple matter, especially with ubuntu on the workstation. The ACL/security flag has me a bit concerned, as I didn't recall setting up anything of the sort under unraid. Hoping I'm just missing something, possibly related to being in a 6.4 pre-release! If anyone has any insight into what might be tripping me up, I'm happily all ears!