I had an issue with one disk going off line with no SMART errors it just became disabled, in trying to fix that and swapping cables around I ended up with two disabled disks.

 

I started a parity rebuild of those two disk, apparently there is no way to just add them back into the array once they are disabled.

 

Then this afternoon my docker service crashed, when all my shares disappeared.

My docker service has been crashing fairly regularly since installing 6.9.0

Browsing the disks the folders are there with data in but the shares are missing

But because the shares are missing all access to these files has stopped.

 

I don't want to reboot the server as this will interrupt the parity rebuild.

 

Any help would be appreciated, diagnostics attached.

35highfield-diagnostics-20210415-1618.zip

3 minutes ago, doma_2345 said:

apparently there is no way to just add them back into the array once they are disabled.

If the disks are known to be good you can do a new config instead.

 

As for the shares, this was the problem:

 

Apr 15 16:05:20 35Highfield shfs: shfs: ../lib/fuse.c:1451: unlink_node: Assertion `node->nlookup > 1' failed.

 

AFAIK only solution is rebooting.

good to know, but also FFS.

 

if I reboot how does that affect the parity rebuild will it start from where it left off or will it start again?

5 minutes ago, doma_2345 said:

will it start again?

This.

So i have rebooted and my shares are still missing

35highfield-diagnostics-20210415-1648.zip

It already happened again, the error you seeing is this issue, though when it happens it usually only happens after hours or days.

this error still shows

 

Apr 15 16:45:12 35Highfield shfs: shfs: ../lib/fuse.c:1451: unlink_node: Assertion `node->nlookup > 1' failed.

 

what do i do now?

Try rebooting again, if it keeps happening post on the linked thread, it might help LT get to the bottom of the problem if it's easily repeatable.

so i rebooted again and disabled a docker container that had an error in the first set of diagnostics and has been installed for about the same amount of time as i have been having docker issues which may have been caused by this all along and it is now working.

 

but it does seem to be docker containers causing this issue. 

1 hour ago, doma_2345 said:

but it does seem to be docker containers causing this issue.

Yep, dockers directly manipulating files seems to be one of the reasons for this.

I have this issue where my shares disappear every now and then and rebooting is a problem when i run my NVR on a VM.  Really cant find a solution on these forums.