I'm running Ubuntu on my PC and I've been playing minecraft on it with the game directory set to a network attached storage (NAS). Up until 20w14a, It's been running without any problems; but now whenever I try to open or create a world, it says 'Failed to access level'
This is the error that was outputted in the console:
Failed to read level New World (22) data java.io.IOException: No such file or directory at java.base/sun.nio.ch.FileKey.init(Native Method) at java.base/sun.nio.ch.FileKey.create(FileKey.java:43) at java.base/sun.nio.ch.FileLockTable.<init>(FileLockTable.java:90) at java.base/sun.nio.ch.FileChannelImpl.fileLockTable(FileChannelImpl.java:1089) at java.base/sun.nio.ch.FileChannelImpl.tryLock(FileChannelImpl.java:1153) at java.base/java.nio.channels.FileChannel.tryLock(FileChannel.java:1165) at acr.a(SourceFile:24) at cxp$a.<init>(SourceFile:196) at cxp.c(SourceFile:185) at dit.a(SourceFile:1657) at dqr.n(SourceFile:301) at dqr.b(SourceFile:225) at dkc.ap_(SourceFile:18) at djw.a(SourceFile:15) at dka.a(SourceFile:150) at dkz.a(SourceFile:27) at diu.b(SourceFile:86) at dnj.a(SourceFile:451) at diu.a(SourceFile:86) at diu.c(SourceFile:150) at ald.execute(SourceFile:94) at diu.b(SourceFile:150) at org.lwjgl.glfw.GLFWMouseButtonCallbackI.callback(GLFWMouseButtonCallbackI.java:36) at org.lwjgl.system.JNI.invokeV(Native Method) at org.lwjgl.glfw.GLFW.glfwWaitEventsTimeout(GLFW.java:3174) at com.mojang.blaze3d.systems.RenderSystem.limitDisplayFPS(SourceFile:123) at dit.d(SourceFile:1027) at dit.d(SourceFile:632) at net.minecraft.client.main.Main.main(SourceFile:204)
I don't get this error whenever I use 1.15.2 or previous.
Here is my /ect/fstab:
/etc/fstab: static file system information.
#Use 'blkid' to print the universally unique identifier for a
device; this may be used with UUID= as a more robust way to name devices
that works even if disks are added and removed. See fstab(5).
#<file system> <mount point> <type> <options> <dump> <pass>
/ was on /dev/sda3 during installation
UUID=fd976496-9f6d-45ea-9023-ce4501f97cfb / ext4 errors=remount-ro 0 1
/swapfile none swap sw 0 0
//192.168.1.120/Vault/Storage/Game\040Cache/Steam /media/Vault cifs exec,vers=3.0,rw,credentials=/home/nick/.server,iocharset=utf8,dir_mode=0777,file_mode=0777,uid=1000,gid=1000,auto 0 0
//192.168.1.120/Vault /media/Storage cifs exec,rw,credentials=/home/nick/.server,iocharset=utf8,dir_mode=0777,file_mode=0777,uid=1000,gid=1000,auto 0 0
I really hope this gets patched soon because I really would like to be able to play 1.16 without storing the files locally
Thanks!
Linked issues
is duplicated by 1
Comments 7
This is still an issue for me with server version 20w14a. If I downgrade the server snapshot to 20w13b it does work. Using 20w16a gives me the same error.
[00:20:02] [main/FATAL]: Failed to start the minecraft server
java.io.IOException: No such file or directory
at sun.nio.ch.FileKey.init(Native Method) ~[?:?]
at sun.nio.ch.FileKey.create(FileKey.java:43) ~[?:?]
at sun.nio.ch.FileLockTable.<init>(FileLockTable.java:90) ~[?:?]
at sun.nio.ch.FileChannelImpl.fileLockTable(FileChannelImpl.java:1089) ~[?:?]
at sun.nio.ch.FileChannelImpl.tryLock(FileChannelImpl.java:1153) ~[?:?]
at java.nio.channels.FileChannel.tryLock(FileChannel.java:1165) ~[?:?]
at adc.a(SourceFile:27) ~[server.jar:?]
at czq$a.<init>(SourceFile:200) ~[server.jar:?]
at czq.c(SourceFile:188) ~[server.jar:?]
at net.minecraft.server.MinecraftServer.main(SourceFile:988) [server.jar:?]
I tried a couple versions of java and got the exact same error:
openjdk version "1.8.0_252"
OpenJDK Runtime Environment (build 1.8.0_252-8u252-b09-1~18.04-b09)
OpenJDK 64-Bit Server VM (build 25.252-b09, mixed mode)openjdk version "11.0.7" 2020-04-14
OpenJDK Runtime Environment (build 11.0.7+10-post-Ubuntu-2ubuntu218.04)
OpenJDK 64-Bit Server VM (build 11.0.7+10-post-Ubuntu-2ubuntu218.04, mixed mode, sharing)
Please re-check. While I can't fully reproduce, pre-1 should try harder to make sure that file is there
Apparently still an issue in 1.16-pre2 according to MC-187764.
Newer editions of Java can be very problematic, as noted by the maintainer of the launcher in the Archlinux AUR. Since I'm seeing what looks like more direct Java issues, I'd make sure you're running it in Java8 before going any further. That's the more 'stable' Java version for MC, I'd try that if you're not already using it to launch with.