Falloutman

Everything across each share, including the Recycle Bin, is being backed up by my backup software. While I could exclude the folder, doing so for every new share would get tiresome. If I could relocate these files to an other share, let's say a Recycling Bin share, it would make maintenance simpler.

This might be a feature request. Is it possible to have deleted files moved to a different folder/share?

More or less just trying to figure out why these errors would occur. I have these errors corrected automatically while the Parity check is running but it keeps coming back. Took a quick screenshot to help with the formatting.

Below is the history from my monthly parity checks. Ever since I replaced my Parity Drive with a 14tb, this is a monthly issue whenever the scan runs. Where do I start? Date Duration Speed Status Errors Elapsed Time Increments Type 2021-02-03, 10:41:17 1 day, 12 hr, 13 min, 33 sec 107.4 MB/s OK 967841513 Unknown Unavailable 2020-12-28, 09:46:17 1 min, 28 sec Unavailable Canceled 0 Unknown Unavailable 2020-12-26, 02:10:08 1 day, 6 hr, 33 min, 15 sec 127.3 MB/s OK 967841513 Unknown Unavailable 2 day, 13 hr, 29 min, 28 sec 1 OK Unknown Unavailable 2020-12-06, 02:16:18 2 day, 13 hr, 29 min, 28 sec 63.2 MB/s OK 967841513 Unknown Unavailable 13 min, 34 sec 1 OK Unknown Unavailable 2020-12-04, 12:12:47 13 min, 34 sec 17.2 GB/s Canceled 8485997 Unknown Unavailable 2020-12-04, 12:02:37 25 sec Unavailable Canceled 383899 Unknown Unavailable 2020-12-03, 22:28:24 1 day, 22 hr, 19 min, 24 sec 84.0 MB/s OK 0 1 day, 22 hr, 19 min, 24 sec 1 Correcting 2020-12-02, 17:35:19 2 day, 8 hr, 23 min, 52 sec 69.0 MB/s OK 0 2 day, 8 hr, 23 min, 52 sec 1 Non-Correcting 2020-12-01, 10:11:24 20 hr, 22 min, 46 sec 54.5 MB/s OK 0 20 hr, 22 min, 46 sec 1 Correcting 2020-11-01, 09:12:41 20 hr, 25 min, 18 sec 54.4 MB/s OK 0 20 hr, 25 min, 18 sec 1 Non-Correcting 2020-10-01, 10:12:25 10 hr, 12 min, 24 sec 108.9 MB/s OK 0 10 hr, 12 min, 24 sec 1 Correcting 11 hr, 18 min, 39 sec 1 OK 2020-09-01, 11:18:40 11 hr, 18 min, 39 sec 98.3 MB/s OK 11 2020-08-14, 08:46:05 10 hr, 33 min, 28 sec 105.3 MB/s OK 11 2020-08-07, 21:51:01 10 hr, 59 min, 14 sec 101.1 MB/s OK 11 2020-08-04, 21:41:34 10 hr, 36 min, 58 sec 104.7 MB/s OK 11 2020-08-04, 00:40:40 11 hr, 46 min, 33 sec 94.4 MB/s OK 19 tower-diagnostics-20210209-0938.zip

HI All, Woke up this morning to my cache drive showing an error in the log. Can someone help me what this means? Tower kernel: BTRFS error (device loop2): bad tree block start tower-diagnostics-20200223-0932.zip

Did both of these and the rebuild is happening now.

I cannot remove this darn error from UNRAID. It's occurring on my Parity Drive and it continues to stay disabled. No where in the webgui does it give me the option to acknowledge the error. Is there a different way to to this?

Gotcha. I have deleted and recreated docker.img to my cache drive.

I looked over the faq but didn't see much. There might be a docker I could remove but nothing lines up with the crashes.

tower-diagnostics-20180417-0518.zipLately, my server has been crashing out of the blue. Everything comes to a halt and the only information available to me is a picture from my phone. After the first error, I did some research and decided to install Fix Common Problems plugin and ran it in troubleshooting mode. This is the last string from logs in my latest dump. "Apr 17 05:18:24 Tower kernel: BTRFS warning (device loop2): csum failed root 650 ino 19396 off 1064960 csum 0x8bc30ca1 expected csum 0x62f0379a mirror 1" I have currently pulled the flash drive and will not reboot the server for now. Thanks for anyone's help! tower-diagnostics-20180417-0518.zip FCPsyslog_tail.txt