Lidde

It was 5,27 GB I am trying to figure out if there are files lost or if everything is in the lost+found. Both by moving files from lost+found to the original folders and restoring an crashplan backup.

[SOLVED, found it myself] First of all, thanks for a great plugin. I just had a disk crash and some of the files where lost. My plan was to restore to a separate folder and then manually compare and copy the restored files to the original location. But regardless how I do it, I get the same error creating directory, Read only file system. What am I missing, how do I allow the Crashplan write access to my unraid server? Thx!

It does, thank you so much! Both JorgeB, Trurl and Itimpi! I am using Crashplan for the important files, but there was a lot of files not backed up that is saved now. Really appreciate your support!

There is no bay free, but I could replace one of the cache disks with the original disk if needed. I needed to use the -L, see attached file. xfs_repair status -L disk 4 2022-09-03.txt

I believe that I did it from both the webgui and the terminal in the webgui. But I did it again now from the webgui and got another result, see attached file. BTW, thanks for the support everyone! xfs_repair status disk 4 2022-09-02.txt

Thanks for the reply JorgeB, I just did a reboot and created a diagnostics file. I have the same behavior as when i discovered this the first time with the original crashed disk, it boots and gets online but many files are missing when I access the share via samba. store-diagnostics-20220902-2141.zip

Thanks, I ran the "Check Filesystem Status" on the disk and got the follwing result, which do not looks good: Phase 1 - find and verify superblock... superblock read failed, offset 0, size 524288, ag 0, rval -1 fatal error -- Input/output error I get the same result if i remove the -n, it immediately reply as above.

Hi When i logged in to my unraid server yesterday did I notice that one of the disks had collapsed (disk 4, sdc), many errors. So I turned of the server, replaced the disk with a new one and restarted and assigned the new disk the same place as the old one and started the array. Unraid started to read on the discs and write to the new one, ie restoring the data. But when I logged in a day later when the restoring should be done, I get an error message from the disk saying: "Unmountable: Wrong or no file system" It is true that I did not format the new disk before starting to rebuild the array, I thought that this would be done automatically. It also seems like the monthly parity check started during the rebuild, finding zero errors. What do I do now? Is the data lost forever, or can I assign a file system to the new disk? Thanks! store-diagnostics-20220901-2018.zip

Thanks, I did not see it yesterday but a restart of the container and now it shown in the WebUI as well as the console. Now everything is working again!

I logged in to WebUI today and noticed that it was working on backup the whole share and not only the intended folders. In the container setting is Storage: set to "/mnt/user/Lagring" and from my earlier memories was i expected to see this folder with is sub folder when i log in to Manage Files in the WebUI and there set the folders I want to backup. But I just get to Root and cant find my share, the mnt folder is empty. Anyone who could help? Btw, thanks for the docker, have been using it for many years now.