I've finally added a 12TB Parity drive to by 7TB unRAID server. It's doing a parity-sync as expected, but what I didn't expect was my proxmox server unable to connect to NFS during this time. "requested NFS version or transport protocol is not supported". Yet my Windows machines can still browse over SMB without any issues.

 

Is this normal behavior during a parity-sync?

Edited October 6, 20196 yr by ShiroiKuma

No.    The only impact of a parity sync should be degraded file access performance.

 

if you want more informed feedback you should provide system diagnostics zip file (obtained via Tools>>Diagnostics) taken while the problem is occurring to see if anyone can spot something.

That's what I expected, but wasn't too sure if that was intended or not.

 

A few more hours of parity-sync to go. I've attached the diagnostics zip.

 

I have tried disabling nfs, waiting and then re-enabling it to no affect. Until the parity-sync started NFS has been working fine for several weeks.

titan-diagnostics-20191006-0718.zip

That's what I expected, but wasn't too sure if that was intended or not.

 

A few more hours of parity-sync to go. I've attached the diagnostics zip.

 

I have tried disabling nfs, waiting and then re-enabling it to no affect. Until the parity-sync started NFS has been working fine for several weeks.

 

EDIT: Had a very random idea, and somehow it worked. I went into a share itself and switched export from yes -> no, saved it, and then no -> yes and saved it. And now I can mount the share okay. Hopefully the diagnostics can explain why this happened