rick9814911

This would be a very welcomed feature! Especially after a power outage. If I can schedule the parity check it's not a huge deal. But even a small blip in power makes the server slow for hours because of the parity check.

+1 for iSCSI support! Being able to run VMs from the cache drives would be amazing. I have a 10Gb fibre connection to my Windows Server 2016 machine. iSCSI would be a big help!

Thank you so much! You've been a huge help.

Excellent!! That's great news. Will it tell you which file is corrupt so I can restore it from the previous backup?

Thank you for clarifying! My only concern is that if I backup a file not knowing it's been corrupted, my backup will also be corrupt. That is the case right? Is there a recommended way to protect against bitrot on unRAID? I really love unRAID, but bitrot does worry me.

Hi, I recently started my unRAID trial and setup my array using BTRFS. From what I've read it should be stable enough, and I do make backups of course! One of the big reasons I went with BTRFS over XFS is to protect against bitrot. However, I was talking with a user on Reddit that said the following: "BTRFS can identify errors in a RAID0 or 'no raid' scenario, but only RAID1 can correct. (and 5 and 6, but they're not ready)" Is this true? Does BTRFS protect against bitrot when used on the array? Or does it only detect the errors but isn't able to correct them? Sorry if this has been documented before! I searched the forums but didn't find an answer to this. Any input would be much appreciated! Without the ability to fix bitrot errors I would probably choose XFS over BTRFS since it's been around much longer and seems to be very stable.

I'm having issues with this as well. I can't seem to find the support thread for this Docker. Can anyone chime in?