Hey guys, Another question for you all. 

 

My array config : 

 

2x 4TB Parity

5x 4TB Data Drives

1x 250GB Samsung 850 Evo SSD Cache

 

Appdata is set to use cache only

 

In my shares, Appdata, Domains and System are showing with orange triangle. I figured I need to run a parity check so I did and this is the result 

 

Last check completed on Mon 07 Aug 2017 01:32:09 PM EDT (today), finding 955270102 errors.

 

However my drives are still showing as unprotected. 

 

Any advice? Thanks

Any cache only shares will always be unprotected because it's not part of the array

 

Parity errors:  that's an obscene amount of corrections.   Did you do anything strange with the drives Previously? 

I replaced Disk1 slot with the cache SSD, Previously that slot was used by another 4TB. Can I reset disk positions, as currently I have no "Disk1" 

 

 

Would it be best to go through the "New config" Tool?

Edited August 8, 20178 yr by riopgtmn

4 hours ago, riopgtmn said:

Would it be best to go through the "New config" Tool?

Going through New Config would allow you to re-order the drives, but it would also invalidate parity (Parity2 uses disk slot as part of the calculation) so your array would be running unprotected until you had rebuilt parity with the drives in their new positions.

So I did a New Config, and rebuilt the Parity, however my Cache, Domains, and System shares are showing as not protected, I understand why cache is not protected, however any clues on Domains and System?

7 minutes ago, riopgtmn said:

however any clues on Domains and System?

Any cache-only share, cache prefer share, or use cache yes share will show as unprotected in a single cache drive system if files in those shares exist on the cache drive.

9 minutes ago, riopgtmn said:

So I did a New Config, and rebuilt the Parity, however my Cache, Domains, and System shares are showing as not protected, I understand why cache is not protected, however any clues on Domains and System?

Because they are cache:prefer shares, and thus hosted on the cache drive.

I understand now, I switched them to No and rebuilt the parity and everything is showing protected other than appdata, which is set to use cache only