Why would a share show 'some or all files unprotected'? I recently copied files to this share and I don't recall it reporting this status before.

I suspect that you have a single cache drive and the share in question is configured to use the cache drive.

 

As you have recently copied some files to the share they are currently residing on the cache drive which is not protected.    When 'mover' runs (usually configured to run automatically overnight, or you run it manually) then the files will be moved to the protected data disks.

I do have a single cache drive and the share is configured to use the cache drive, however the cache drive is showing 0 bytes indicating there is nothing on it.

Ok thats weird, I just ran mover again and although the log indicated it didn't move anything, the share is now reporting protected.

 

 

Thanks.

 

AM

All of my shares are reporting as unprotected. I have no cache drive, and all sharing options are set to private.

 

I am building my server right now, so the parity is being generated right now.

 

This seems like a bug to me. Unless I am missing something?

Its normal for the shares to show as unprotected until the parity build is complete, not a bug.

Ah -- I was confused due to the semantics. I read unprotected as shares having open read[/write] access. Sorry, working in the security industry makes you very paranoid.

"Protected" in this context means fault-tolerant.    If you don't have valid parity; or if some of the content is on a non-fault-tolerant cache (i.e. not a btrfs pool), then it will show that some of the data is not protected.

 

Hello! I have the same issue: one of my shares shows 'some or all files unprotected'. I have a single cache drive, but the share in question configured to not use cache. Running mover didn't make a difference. Parity check comes clean. I'm very new to unRAID, please help troubleshoot.

Hello! I have the same issue: one of my shares shows 'some or all files unprotected'. I have a single cache drive, but the share in question configured to not use cache. Running mover didn't make a difference. Parity check comes clean. I'm very new to unRAID, please help troubleshoot.

I would still check to the cache drive to see if there are files corresponding to the share in question.  Although unRAID itself will not put files there for a share that is configured to not use cache, that does not mean that you do not have an docker application placing files there (or you manually copying files directly to the cache drive bypassing user shares).

Checked cache. There is nothing there except docker image file. Any other ideas for troubleshooting? Thanks!

Checked cache. There is nothing there except docker image file. Any other ideas for troubleshooting? Thanks!

Do you have valid parity?

Yes, I do