Hey, i could use some help troubleshooting this so i don't fudge something up and end up losing my data.

 

I had a power outage which took down my Unraid server uncleanly. Server booted up normally, i started the array and the parity check completed (fixing 1000+ errors, normal?), but my User Shares are now all missing. All of my disks are present and i can access them directly and verify that data is still on the disks and accessible. I checked that User Shares are enabled and all disks included in Global Share Settings. I enabled Disk Shares temporarily and they show up and are browseable that way.

 

Just now while writing this post and collecting diagnostics, i just noticed these entries in the log. Full diagnostics attached.

Mar 28 10:48:32 UNRAID emhttpd: shcmd (63): mkdir /mnt/user
Mar 28 10:48:32 UNRAID emhttpd: shcmd (64): /usr/local/bin/shfs /mnt/user -disks 15 -o default_permissions,allow_other,noatime -o remember=28 800 
Mar 28 10:48:32 UNRAID shfs: fuse: invalid argument `800'
Mar 28 10:48:32 UNRAID shfs: fuse_main exit: 1
Mar 28 10:48:32 UNRAID emhttpd: shcmd (64): exit status: 1

 

I'm not at all familiar with FUSE, but it almost seems like there is an extra space between 28 and 800 in the remember-argument? 28800 seconds / 8 hours sounds reasonable, i guess. I have no idea how an argument value in a command run automatically by the system would gain a space due to a power outage though, but i can't think of anything i might have done either.

unraid-diagnostics-20250328-1052.zip

Go to Settings - NFS and set "Fuse_remeber) to default (330) and apply.

1 minute ago, JorgeB said:

Go to Settings - NFS and set "Fuse_remeber) to default (330) and apply.

Thanks! That's exactly where the extra space was. Setting it to 330 and starting the array brought everything back to normal. 

 

It's a true mystery why this issue popped up only now though. I haven't used NFS in years, but i think i'm starting to recall i had issues with stale file handles when i started out with Unraid and that's probably why some gremlin (me) has messed with that value...