liynus

my minecraft server doesn't work after an update. tried everything, can anyone help. here is the log. not sure why it can't find my java files. ---Checking for 'server.properties'--- ---'server.properties' found... ---Checking for old logs--- ---Starting Server--- ---Waiting for logs, please stand by...--- Cannot exec '/serverdata/serverfiles/runtime/jre1.8.0_261/bin/java': No such file or directory Terminated ---Checking if UID: 99 matches user--- usermod: no changes ---Checking if GID: 100 matches user--- usermod: no changes ---Setting umask to 000--- ---Checking for optional scripts--- ---No optional script found, continuing--- ---Starting...--- ---Checking for 'runtime' folder--- ---'runtime' folder found--- ---Checking if Runtime is installed--- ---Runtime found--- ---Checking for Minecraft Server executable --- ---Minecraft v1.16.5 is Up-To-Date!--- ---Preparing Server--- ---Checking for 'server.properties'--- ---'server.properties' found... ---Checking for old logs--- ---Starting Server--- ---Waiting for logs, please stand by...---

Thanks so much that was the absolute fix. I'm off and running, What a great community, you guys go above and beyond.

Hi all, Long time (1+ year) bnhex delugeVPN user with PIA VPN. Can't log into the web interface in the last week. It was working fine 2 weeks ago. IP address is the same. Went through the logs, but can't see the problem. Can someone more knowledgeable enlighten me? I also included the startup log with my pass/user stared out. PIA has given me some troubles with the the VPN connection which required replacing the OPENVPN files, but I don't think this browsing through the logs. Thanks all delugelog.txt startuplog.txt

thanks so much. looks like parity is rebuilding now. from the wiki steps 8 and 9 confused me - your clarification on step 8 to go to the main tab to restart the array AND not checking valid parity helped. I didn't know to go to the main tab!!

I tried following instructions on shrinking my array. I wanted to take out a hard drive. Tried following the wiki's "Remove Drives then Rebuild Parity" https://wiki.unraid.net/Shrink_array I moved all the data off the drive - that is disk 2 - see attached picture. I checked it was empty first. Stopped the array, went to Tools -> New Config -> checked off everything in Preserved Current Assignments - see attached pic Check Yes I want this to be Done (disk 2 was then physically taken out of the server) then went back to Main --> Array Devices - but Disk 2 can't be removed? see attached pic I figure it's something simple, but I don't want to mess up. Thanks.

also find it interesting this was a homegrown solution to have 48 drive for backblaze, perhaps they run proprietary software that compensates? any thoughts on what to do the controllers/port multipliers?

thanks. finally got around to it today. I took out the controller cards and plugged all the drives directly into the motherboard. startup errors went away. it's rebuilding parity now. was afraid i was going to lose my data, but your advice and spaceinvader video on xfs corruption saved my butt <https://www.youtube.com/watch?v=JVjB0ROdLBA> wife is SO happy about your unraid hobby. also my docker was hanging my whole system, deleted the docker.img and just reinstalled, nice that the app data is separate, so all my plex data is unchanged!! unraid is so powerful, but also so complicated for average nubes. it's a long learning curve at times for sures. thanks teeteejorge for all the work that you and others do on this forum. unraid's also a pathway to linux learning and learning to program in python for me. what a rabbit hole!!

Thanks. This was a case from BackBlaze 2.0 which they gave out for free. It's sitting in my garage and it's summer, so I'm not surprised about the cooling. I'll probably turn on the fans. I'm a relative unRAID newbie. It's a long rabbit hole. Can I ask how did you work out that it is a controller problem?

Trying to figure out what happened to my Parity drive to disable it, can you guys clarify through the logs: Thanks. Edited attached the logs. tower-diagnostics-20200510-2046.zip