[[6.8.3] shfs error results in lost /mnt/user]

11 minutes ago, RaidUnnewb said:

Is this an Unraid problem or a Linux problem?

 

 

I don't know.  But at this point I'd be looking for mental problems.

[[6.8.3] shfs error results in lost /mnt/user]

jit-010101, thank you for that background, that does help explain what's going on even if there isn't a fix.

 

What version of unRAID do we have to rollback to in order to not encounter the bug?  I came to unRAID a couple years ago on 6.9 where I encountered the bug.  All of my upgrades became necessary when things (notably plugins) became unsupported.  I always waited as long as I could before upgrading became necessary.

[[6.8.3] shfs error results in lost /mnt/user]

2 hours ago, XiMA4 said:

Or split my setup into two parts, one unRAID just the file server and the other unRAID for add-ons, docker, etc. 

 

 

For things to work on unRAID you need to have an array started.  I suppose you don't need to share any files on it, but some array needs to start because that's how unRAID gets paid.  Honestly if I was considering to go this route, I'd nix unRAID and install some flavor of Ubuntu and do things differently rather than paying unRAID twice because of a problem with unRAID.  Plus increased hardware, electric, and maintenance cost.

 

My problem with this error stopped entirely after I disabled XMP which basically put my BIOS settings back to default.  6.11 was up for 270 days before I upgraded to 6.12.6 just recently.  2 days after installing 6.12 the server randomly and uncleanly rebooted itself, fingers crossed it was just a one-off event.

[[6.8.3] shfs error results in lost /mnt/user]

7 hours ago, evan326 said:

So it looks like this still hasn't been sorted? I'm having this issue occur more and more. 

 

Out of curiosity, are you overclocking and/or have XMP enabled?  Out of desperation for a fix, I reset my BIOS to defaults (no OC or XMP) and currently have an uptime of a little over 3 months, where previously 2 weeks was about the maximum before running into this error.  No clue if it's related, or coincidence, but I'll take it for now.  Still on 6.11.5.

[[6.8.3] shfs error results in lost /mnt/user]

1 hour ago, CS01-HS said:

I've triggered it a few times with SMB file operations from my Mac client where the folder/file structure was stale.

 

Since then I force a refresh by e.g. navigating down a directory then back up before every SMB move or copy. Tedious but so far it hasn't failed.

 

When it happened to me, windows was installing software from the samba share.  The contents of the folder it was installing from was static, nothing to go stale. I've always assumed unRAID was designed to be a NAS as a core competency and it's failing at doing that task and has me questioning my choices.  It's rock solid for the most part, but I can't stand random, unknown, and unpredictable crashes with no explanation or potential fix in the pipeline.  I'm willing to do whatever it takes to make this problem go away, but so far all I get is "?????????" from the community, unraid, and as the directory structure itself says when listing /mnt/user.

[[6.8.3] shfs error results in lost /mnt/user]

Throwing my hat in here too..

 

Don't user Tdarr, and stopped using NFS and I *thought* the problem was fixed by using only samba as I haven't had the issue in a couple weeks.. But, here we go again, it just happened..  Although, the error is different, with NFS it was a kernel crash, with samba I got this:

 

smbd[26612]:   Invalid SMB packet: first request: 0x0001
shfs: shfs: ../lib/fuse.c:1450: unlink_node: Assertion `node->nlookup > 1' failed.
rsyslogd: file '/mnt/user/temp/syslog-192.168.15.21.log'[9] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: Transport endpoint is not connected [v8.2102.0 try https://www.rsyslog.com/e/2027 ]
rsyslogd: file '/mnt/user/temp/syslog-192.168.15.21.log': open error: Transport endpoint is not connected

 

It happened right in the middle of reading from a samba share on a windows VM running on unraid.  Mover was not running and no other shares were active.  The windows share was reading from my cache drive, if that makes a difference.  Apparently an "invalid SMB packet" caused this?  I don't understand how that would happen.