So today morning when i woke up i realized that plex wasn't working properly so restated the plex docker but  after that it is showing this read only file system error.

so i restarted my unraid array and now fix common problem plugin in showing these errors.

Just forget about the filebotui error part, cause i did it on my own and it was working fine.

here goes the diagnostics. I really need some help cause now im starting to feel that unraid might not work out for me cause after every 3-4 days im here, crying out for help or could it be all because of BTRFS.

unraid-diagnostics-20170501-1127.zip

There are corrupt files on disk1:

 

Apr 24 16:43:05 Unraid kernel: BTRFS warning (device md1): csum failed ino 428 off 8089600 csum 4151497176 expected csum 1559119275
Apr 24 16:43:06 Unraid kernel: BTRFS warning (device md1): csum failed ino 428 off 8257536 csum 1854616921 expected csum 3195413001
Apr 24 16:43:06 Unraid kernel: BTRFS warning (device md1): csum failed ino 428 off 8089600 csum 4151497176 expected csum 1559119275
Apr 24 16:43:07 Unraid kernel: BTRFS warning (device md1): csum failed ino 428 off 8257536 csum 1854616921 expected csum 3195413001
Apr 24 16:43:07 Unraid kernel: BTRFS warning (device md1): csum failed ino 428 off 9281536 csum 2251577804 expected csum 2021076594
Apr 24 16:43:08 Unraid kernel: BTRFS warning (device md1): csum failed ino 428 off 9281536 csum 2251577804 expected csum 2021076594
Apr 24 16:43:08 Unraid kernel: BTRFS warning (device md1): csum failed ino 428 off 9486336 csum 3583183900 expected csum 2002863738

 

Run a scrub to find out which file(s) are affected.

1 minute ago, johnnie.black said:

There are corrupt files on disk1:

 

Apr 24 16:43:05 Unraid kernel: BTRFS warning (device md1): csum failed ino 428 off 8089600 csum 4151497176 expected csum 1559119275
Apr 24 16:43:06 Unraid kernel: BTRFS warning (device md1): csum failed ino 428 off 8257536 csum 1854616921 expected csum 3195413001
Apr 24 16:43:06 Unraid kernel: BTRFS warning (device md1): csum failed ino 428 off 8089600 csum 4151497176 expected csum 1559119275
Apr 24 16:43:07 Unraid kernel: BTRFS warning (device md1): csum failed ino 428 off 8257536 csum 1854616921 expected csum 3195413001
Apr 24 16:43:07 Unraid kernel: BTRFS warning (device md1): csum failed ino 428 off 9281536 csum 2251577804 expected csum 2021076594
Apr 24 16:43:08 Unraid kernel: BTRFS warning (device md1): csum failed ino 428 off 9281536 csum 2251577804 expected csum 2021076594
Apr 24 16:43:08 Unraid kernel: BTRFS warning (device md1): csum failed ino 428 off 9486336 csum 3583183900 expected csum 2002863738

 

Run a scrub to find out which file(s) are affected.

Okay i already tried running scrub but it aborts on its own after 3 secs.

scrub status for 3a966616-a38f-43fc-992b-b99d7ae0b686
	scrub started at Mon May  1 08:43:22 2017 and was aborted after 00:00:03
	total bytes scrubbed: 291.64MiB with 0 errors

And now just to be sure i just tried it again and now whenever i click on scub button it just reloads the page.

Reboot and try again

6 minutes ago, johnnie.black said:

Reboot and try again

So when i tried to stop the unraid array it was stuck at unmounting disks, so i hard rebooted the system but still everything is same.

 

scrub status for 3a966616-a38f-43fc-992b-b99d7ae0b686
	scrub started at Mon May  1 13:56:25 2017 and was aborted after 00:00:00
	total bytes scrubbed: 0.00B with 0 errors

 

It just aborts itself on its won.

Maybe docker image is the only corrupt file, delete the image and recreate it.

 

If there are still checksum errors after that move all files from disk1 to other disk(s), all files that can't be moved due to a read error are corrupt.

Edited May 1, 20179 yr by johnnie.black

11 minutes ago, johnnie.black said:

Maybe docker image is the only corrupt file, delete the image and recreate it.

 

If there are still checksum errors after that move all files from disk1 to other disk(s), all files that can't be moved due to a read error are corrupt.

that was the very first thing that i did so already copied all that data that was important to me.

So basically u mean i have to reformat my drives and start all over again, so if that's what u meant then in that case would u recommend me to switch to xfs cause this will be the third time i will be starting all over in 15 days of trial period.

XFS is more stable and it's probably the best choice for most users, but those btrfs errors are probably the result of other problems.

 

On the main GUI page, click on disk1, change filesystem to xfs, start the array, format the disk.

16 minutes ago, johnnie.black said:

XFS is more stable and it's probably the best choice for most users, but those btrfs errors are probably the result of other problems.

 

On the main GUI page, click on disk1, change filesystem to xfs, start the array, format the disk.

Do have any idea what could be those other problems might be.

Cause as i said this will be the third time i will be strting all over again but this time i would love to not face these problems again

Logs are erased every time there's a reboot, if there are any more issues in the future grab the logs as soon as you notice them and before rebooting.

3 minutes ago, johnnie.black said:

Logs are erased every time there's a reboot, if there are any more issues in the future grab the logs as soon as you notice them and before rebooting.

okay but even this time i grabbed them before rebooting, infact i didn't rebooted my unraid server until you told me to.

It was too late, it only shows the checksum errors but not what caused them

okay that means i took too long before grabbing diagnostics.

ohh okay will be careful next time

i guess i will give BTRFS one last chance, lets hope their will be no next time.

If you're not using ECC it's also a good idea to run Memtest for 24 hours to rule out any memory issues.

5 minutes ago, johnnie.black said:

If you're not using ECC it's also a good idea to run Memtest for 24 hours to rule out any memory issues.

Okay will do that, thanks for suggestions and everything.