DriveBackupV2 icon indicating copy to clipboard operation
DriveBackupV2 copied to clipboard

Can not backup world_nether

Open SimonKlemp opened this issue 3 years ago • 4 comments

Hey, I frequently have problems with backuping my files. I backup the world, plugins, nether and the end. It always backups the end first, which works fine. Then, it tries to backup the nether. Sometimes it runs into errors which makes the whole filesystem (/directory) read only. I attached some screenshots with the error. I also cannot send the log itself, because the file system is read only and does not write into the log. The last thing that gets saved in the logs is also attached. I hope you can help me. I have not yet figured out how to properly reproduce it. Sometimes it works just fine, sometimes not. Annotation 2021-06-05 214352 Annotation 2021-06-05 214341 Annotation 2021-06-05 214326 Annotation 2021-06-05 220131

SimonKlemp avatar Jun 05 '21 20:06 SimonKlemp

Does this issue still occur? If so what is your server version and plugin version?

rhld16 avatar Jun 13 '21 01:06 rhld16

Hey, thanks for the answer. Sorry, I forgot to include that. The issue occurs occasionally. It has not happened since I opened the issue, but I also only have played one time. My Plugin version is the latest, I think this is 1.4.0. I am currently running on this Spigot version: " This server is running CraftBukkit version 3086-Spigot-9fb885e-5912843 (MC: 1.16.5) (Implementing API version 1.16.5-R0.1-SNAPSHOT) " (I hope this is what you meant.)

SimonKlemp avatar Jun 15 '21 12:06 SimonKlemp

Sorry about the delay we've been working hard on the new update so I've haven't been able to pay much attention to this issue. This usually occurs due to linux file permissions. Could you post the output of running 'ls -l' in your server directory

rhld16 avatar Aug 13 '21 09:08 rhld16

This issue is way more likely to be due to hardware failure than this plugin. When the filesystem goes read-only, there should be some information about it in your kernel logs ( dmesg ).

Something like a corrupted filesystem or a bad connection to the disk in question could cause this to happen.

Worn out SD card or SSD could also cause this, but then the filesystem is likely to stay read-only for the rest of eternity.

oddstr13 avatar Jan 23 '22 18:01 oddstr13