I have been working on my first NAS using UnRaid and everything was going great until the mover stopped working on my cache drive. I have followed other peoples issues and given their solutions a try but nothing has worked for me or more likely I am missing something that's glaring at me in the face.

 

Hope this is the correct log:

Jan 24 15:42:52 NAS01 kernel: BTRFS warning (device sdh1): csum failed root 5 ino 4920 off 631861248 csum 0x44a299d2 expected csum 0xa5313bf1 mirror 1
Jan 24 15:42:52 NAS01 kernel: BTRFS warning (device sdh1): csum failed root 5 ino 4920 off 631861248 csum 0x44a299d2 expected csum 0xa5313bf1 mirror 1
Jan 24 15:42:54 NAS01 kernel: BTRFS warning (device sdh1): csum failed root 5 ino 4958 off 297529344 csum 0x662a9205 expected csum 0x6c43c9a5 mirror 1
Jan 24 15:42:54 NAS01 kernel: BTRFS warning (device sdh1): csum failed root 5 ino 4958 off 297529344 csum 0x662a9205 expected csum 0x6c43c9a5 mirror 1
Jan 24 15:42:55 NAS01 kernel: btrfs_print_data_csum_error: 2 callbacks suppressed
Jan 24 15:42:55 NAS01 kernel: BTRFS warning (device sdh1): csum failed root 5 ino 4961 off 267689984 csum 0x4eda5c1d expected csum 0xee61be5f mirror 1
Jan 24 15:42:55 NAS01 kernel: BTRFS warning (device sdh1): csum failed root 5 ino 4961 off 267689984 csum 0x4eda5c1d expected csum 0xee61be5f mirror 1
Jan 24 15:42:55 NAS01 kernel: BTRFS warning (device sdh1): csum failed root 5 ino 4961 off 267689984 csum 0x4eda5c1d expected csum 0xee61be5f mirror 1
Jan 24 15:42:55 NAS01 kernel: BTRFS warning (device sdh1): csum failed root 5 ino 4961 off 267689984 csum 0x4eda5c1d expected csum 0xee61be5f mirror 1
Jan 24 15:43:00 NAS01 kernel: BTRFS warning (device sdh1): csum failed root 5 ino 4967 off 1201192960 csum 0x932a9376 expected csum 0xead4f9c2 mirror 1
Jan 24 15:43:00 NAS01 kernel: BTRFS warning (device sdh1): csum failed root 5 ino 4967 off 1201192960 csum 0x932a9376 expected csum 0xead4f9c2 mirror 1
Jan 24 15:43:00 NAS01 kernel: BTRFS warning (device sdh1): csum failed root 5 ino 4967 off 1201192960 csum 0x932a9376 expected csum 0xead4f9c2 mirror 1
Jan 24 15:43:00 NAS01 kernel: BTRFS warning (device sdh1): csum failed root 5 ino 4967 off 1201192960 csum 0x932a9376 expected csum 0xead4f9c2 mirror 1
Jan 24 15:43:04 NAS01 kernel: BTRFS warning (device sdh1): csum failed root 5 ino 4975 off 807628800 csum 0x91bcb966 expected csum 0xec79bcf2 mirror 1
Jan 24 15:43:04 NAS01 kernel: BTRFS warning (device sdh1): csum failed root 5 ino 4975 off 807628800 csum 0x91bcb966 expected csum 0xec79bcf2 mirror 1
Jan 24 15:43:04 NAS01 kernel: BTRFS warning (device sdh1): csum failed root 5 ino 4975 off 807628800 csum 0x91bcb966 expected csum 0xec79bcf2 mirror 1
Jan 24 15:43:04 NAS01 kernel: BTRFS warning (device sdh1): csum failed root 5 ino 4975 off 807628800 csum 0x91bcb966 expected csum 0xec79bcf2 mirror 1
Jan 24 15:43:10 NAS01 kernel: BTRFS warning (device sdh1): csum failed root 5 ino 4969 off 1234038784 csum 0xb75a5928 expected csum 0xefb0e465 mirror 1
Jan 24 15:43:10 NAS01 kernel: BTRFS warning (device sdh1): csum failed root 5 ino 4969 off 1234038784 csum 0xb75a5928 expected csum 0xefb0e465 mirror 1
Jan 24 15:43:10 NAS01 kernel: BTRFS warning (device sdh1): csum failed root 5 ino 4969 off 1234038784 csum 0xb75a5928 expected csum 0xefb0e465 mirror 1
Jan 24 15:43:10 NAS01 kernel: BTRFS warning (device sdh1): csum failed root 5 ino 4969 off 1234038784 csum 0xb75a5928 expected csum 0xefb0e465 mirror 1
Jan 24 15:43:11 NAS01 kernel: BTRFS warning (device sdh1): csum failed root 5 ino 272 off 160751616 csum 0x922e7196 expected csum 0x7e99d034 mirror 1
Jan 24 15:43:11 NAS01 kernel: BTRFS warning (device sdh1): csum failed root 5 ino 272 off 160751616 csum 0x922e7196 expected csum 0x7e99d034 mirror 1
Jan 24 15:43:11 NAS01 kernel: BTRFS warning (device sdh1): csum failed root 5 ino 272 off 160751616 csum 0x922e7196 expected csum 0x7e99d034 mirror 1
Jan 24 15:43:11 NAS01 kernel: BTRFS warning (device sdh1): csum failed root 5 ino 272 off 160751616 csum 0x922e7196 expected csum 0x7e99d034 mirror 1
Jan 24 15:43:12 NAS01 kernel: BTRFS warning (device sdh1): csum failed root 5 ino 289 off 248864768 csum 0xfe311b16 expected csum 0xe2780d1f mirror 1
Jan 24 15:43:13 NAS01 kernel: BTRFS warning (device sdh1): csum failed root 5 ino 289 off 248864768 csum 0xfe311b16 expected csum 0xe2780d1f mirror 1
Jan 24 15:43:15 NAS01 kernel: btrfs_print_data_csum_error: 14 callbacks suppressed
Jan 24 15:43:15 NAS01 kernel: BTRFS warning (device sdh1): csum failed root 5 ino 3442 off 82157568 csum 0x186eeb0a expected csum 0x2f951980 mirror 1
Jan 24 15:43:15 NAS01 kernel: BTRFS warning (device sdh1): csum failed root 5 ino 3442 off 82157568 csum 0x186eeb0a expected csum 0x2f951980 mirror 1
Jan 24 15:43:15 NAS01 kernel: BTRFS warning (device sdh1): csum failed root 5 ino 3442 off 82157568 csum 0x186eeb0a expected csum 0x2f951980 mirror 1
Jan 24 15:43:15 NAS01 kernel: BTRFS warning (device sdh1): csum failed root 5 ino 3442 off 82157568 csum 0x186eeb0a expected csum 0x2f951980 mirror 1
Jan 24 15:43:16 NAS01 kernel: BTRFS warning (device sdh1): csum failed root 5 ino 3460 off 177262592 csum 0x8fe11c1e expected csum 0xc2f391cc mirror 1
Jan 24 15:43:16 NAS01 kernel: BTRFS warning (device sdh1): csum failed root 5 ino 3460 off 177262592 csum 0x8fe11c1e expected csum 0xc2f391cc mirror 1
Jan 24 15:43:16 NAS01 kernel: BTRFS warning (device sdh1): csum failed root 5 ino 3460 off 177262592 csum 0x8fe11c1e expected csum 0xc2f391cc mirror 1
Jan 24 15:43:16 NAS01 kernel: BTRFS warning (device sdh1): csum failed root 5 ino 3460 off 177262592 csum 0x8fe11c1e expected csum 0xc2f391cc mirror 1

12 minutes ago, dejammey said:

Hope this is the correct log

No it's not. Syslog snippets are seldom sufficient

 

Go to Tools - Diagnostics and attach the complete diagnostics zip file to your next post.

Thank you so much for responding so fast and pointing me to the correct log.

 

nas01-diagnostics-20190124-1600.zip

Looks like your cache is corrupt, probably because you overfilled it. If there is anything on there you need you can try to copy it off manually. You will have to format it, preferably as XFS unless you intend to create a pool.

 

Looks like you currently have all your shares set to move from cache to array, including appdata and system. Those 2 shares are normally cache-prefer and you should set them back to cache-prefer after you get this cleaned up. I am guessing you changed those to try to get some room. Currently only system and Video Editing have anything still on cache as can be seen in your screenshot.

 

But it makes me wonder if you had some of the others set incorrectly and that is why you filled cache. Was your Video Editing share always set to cache-yes or did you change it after you began having problems?

 

27 minutes ago, trurl said:

Looks like your cache is corrupt, probably because you overfilled it. If there is anything on there you need you can try to copy it off manually. You will have to format it, preferably as XFS unless you intend to create a pool.

 

Looks like you currently have all your shares set to move from cache to array, including appdata and system. Those 2 shares are normally cache-prefer and you should set them back to cache-prefer after you get this cleaned up. I am guessing you changed those to try to get some room. Currently only system and Video Editing have anything still on cache as can be seen in your screenshot.

 

But it makes me wonder if you had some of the others set incorrectly and that is why you filled cache. Was your Video Editing share always set to cache-yes or did you change it after you began having problems?

 

I changed it after I was having problems. I will try to move everything back then format the drive correctly as you instructed.

12 minutes ago, dejammey said:

I changed it after I was having problems.

What exactly did you change? I already mentioned appdata and system as being changed.

 

What I am wondering about specifically is whether you had Video Editing previously set to cache-prefer.

I only remember changing it from Yes to No and Back to Yes after trying out steps from another post.

56 minutes ago, trurl said:

Looks like your cache is corrupt, probably because you overfilled it. If there is anything on there you need you can try to copy it off manually. You will have to format it, preferably as XFS unless you intend to create a pool.

 

Looks like you currently have all your shares set to move from cache to array, including appdata and system. Those 2 shares are normally cache-prefer and you should set them back to cache-prefer after you get this cleaned up. I am guessing you changed those to try to get some room. Currently only system and Video Editing have anything still on cache as can be seen in your screenshot.

 

But it makes me wonder if you had some of the others set incorrectly and that is why you filled cache. Was your Video Editing share always set to cache-yes or did you change it after you began having problems?

 

"If there is anything on there you need you can try to copy it off manually"

 

What is the best way of doing this?

Where do you want to try to copy it to? There is a good chance that some of it won't copy. What is on there that you need?

You have corrupt files, i.e., files failing checksums, btrfs will detect those and won't allow you to copy them, so you know there's a problem, you can run a scrub to find which files are corrupt, and need to investigate how they became corrupt, it could be bad RAM, controller, board, etc.

14 hours ago, johnnie.black said:

You have corrupt files, i.e., files failing checksums, btrfs will detect those and won't allow you to copy them, so you know there's a problem, you can run a scrub to find which files are corrupt, and need to investigate how they became corrupt, it could be bad RAM, controller, board, etc.

So when I started this build I only had one stick of DDR 3 ram. I did add another stick and just realized that the problem started after I added the second stick. Thank you for pointing this out for me.