Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

get_filesystem_status: statfs: /mnt/user/ Transport endpoint is not connected

Featured Replies

Did u get anything out of this information?

What I'm seeing is that the system wide limit of 1024 open files is far too small.

(and most likely, so is the max_user_watches for people with marge media and file collections)

 

Is 100000 too small for max_user_watches ? Do you mind reviewing my settings since I have a problem also?

Did u get anything out of this information?

What I'm seeing is that the system wide limit of 1024 open files is far too small.

(and most likely, so is the max_user_watches for people with marge media and file collections)

 

Is 100000 too small for max_user_watches ? Do you mind reviewing my settings since I have a problem also?

That would entirely depend upon how many files and folders you have.  (Most of us have fewer than 100,000 files, but you might have a very large collection)

When starting inotifywait, it will usually warn if the max user-watches is too low.

 

Joe L.

Did u get anything out of this information?

What I'm seeing is that the system wide limit of 1024 open files is far too small.

(and most likely, so is the max_user_watches for people with marge media and file collections)

 

Is 100000 too small for max_user_watches ? Do you mind reviewing my settings since I have a problem also?

That would entirely depend upon how many files and folders you have.  (Most of us have fewer than 100,000 files, but you might have a very large collection)

When starting inotifywait, it will usually warn if the max user-watches is too low.

 

Joe L.

 

Thanks. Do you have a solution for max open files? I can do 'ulimit -n 5000' as root, and it'll set that -- but I read that only works for current login, and obviously would have to be added to the go file. It doesn't allow me to do that as a normal user -- username I use to connect to my shares remotely.

 

I can't seem to find the limits file that is typical of a linux OS. Does unRAID have a file to set these limits?

 

Thanks

Did u get anything out of this information?

What I'm seeing is that the system wide limit of 1024 open files is far too small.

(and most likely, so is the max_user_watches for people with marge media and file collections)

 

Is 100000 too small for max_user_watches ? Do you mind reviewing my settings since I have a problem also?

That would entirely depend upon how many files and folders you have.  (Most of us have fewer than 100,000 files, but you might have a very large collection)

When starting inotifywait, it will usually warn if the max user-watches is too low.

 

Joe L.

 

Thanks. Do you have a solution for max open files? I can do 'ulimit -n 5000' as root, and it'll set that -- but I read that only works for current login, and obviously would have to be added to the go file. It doesn't allow me to do that as a normal user -- username I use to connect to my shares remotely.

 

I can't seem to find the limits file that is typical of a linux OS. Does unRAID have a file to set these limits?

 

Thanks

See here:

http://www.cyberciti.biz/faq/linux-increase-the-maximum-number-of-open-files/

And how do we set it for Unraid?, and where?

I'd be curious on how to correct this too, as it happens everytime I upgrade past rc8a.

I only had SMB shares, just recently added NFS to work with PXE booting.

 

With rc12a I can run for about half an hour before my user share poops the bed and goes all ?????????? in ls -l.

I have tried the ulimit fix in the "go" script, but it didn't help.

 

I'm not getting any OOM errors.

I'd also like to know how to permanently change the open file limit via 'ulimit'. It seems that the 'ulimit -n 20000' command in the Go script is being ignored, since issuing 'ulimit -Hn' on the command line results in an answer of 4096. I'm pretty sure that the whole number-of-open-file limit has something to do with many of the problems that people are having. The current setting for the soft limit on my system seems to be 1024, just like for everybody else. Rsync seems to want to open more files than the system allows, and hence causes Unraid to crash; the computer doesn't crash, but the service goes away.

 

I'd love to have this problem resolved soon, so I can go back to using my server the way I was under Unraid 4.x and won't be forced migrating to a commercial NAS, which would be a pain in the neck.

 

Thanks,

Carsten

I've read that link and tried the changes, doesn't help.

 

I also am not using PLEX, that's another difference.

 

Very confusing!

 

As you might have seen, I've tried the 'ulimit' setting in the Go script already and it didn't have any effect. I'll next try the

 

sysctl fs.inotify.max_user_watches=20000

 

idea from Tom to see if I can get rsync to back up my music directory. Will report back.

/I think you need both an increased number of open files possible, and an increased number of user-watches.  I've got my max_user_watches set to 100000

 

Joe L.

 

As you might have seen, I've tried the 'ulimit' setting in the Go script already and it didn't have any effect. I'll next try the

 

sysctl fs.inotify.max_user_watches=20000

 

idea from Tom to see if I can get rsync to back up my music directory. Will report back.

/I think you need both an increased number of open files possible, and an increased number of user-watches.

 

Joe L.

 

I have both mods in my Go script and am booting as we speak. In case it matters, both mods are called before start of the management utility via emhttp.

 

As you might have seen, I've tried the 'ulimit' setting in the Go script already and it didn't have any effect. I'll next try the

 

sysctl fs.inotify.max_user_watches=20000

 

idea from Tom to see if I can get rsync to back up my music directory. Will report back.

/I think you need both an increased number of open files possible, and an increased number of user-watches.  I've got my max_user_watches set to 100000

 

Joe L.

 

Didn't make a lick of a difference to have both the ulimit and fs.inotify.max_user_watches changed in the Go script. Rsync throws an

 

Transport endpoint is not connected (107)

 

error message pretty early on when trying to create the sync list and this causes the shares to disappear. No other service was running at the time, and the system had gone through a fresh reboot. I'd like to help out here, since I can easily reproduce this error. Let me know what other information or log file I could provide to trouble shoot this issue.

 

Thanks,

Carsten

  • 3 weeks later...

This just started happening for me yesterday out of the clear blue.  Is there anything I can do other than have to reboot my server every half hour or so?  I am also running plex and turning plex off has no difference.  I have never had this issue before today and I am running RC11.

 

Thanks,

 

Bill

Thought this was just an AFP issue, but it occurred while SSH'd in. Ran the 'find' command which accessed all my FLAC directories (the problem directory), and received the 'Transport endpoint is not connected' error.

  • 4 weeks later...

Just upgraded to 15a and tried rsync on my music directory to back it up to an external drive. Same problem still persists. Early during the rsync process, the endpoint is disconnected error message gets thrown and only a reboot of the system can make the directories appear again. Not sure what else to do here. Being able to use rsync and Crashplan was essential to how I used to use unRAID under version 4.7.

  • 2 weeks later...

This issue seems to be resolved, as I was able to browse large-file-listing directories without fail.

 

I did receive this while downloading a file over SFTP, however:

 

Fetching /home/<user>/Torrents/Completed/TV/Ray Donovan/Ray.Donovan.S01E03.720p.HDTV.x264-IMMERSE.mkv to Ray.Donovan.S01E03.720p.HDTV.x264-IMMERSE.mkv

/home/<user>/Torrents/Completed/TV/Ray Donovan/Ray.Donovan.S01E03.720p.HDTV.x264-IMMERSE.mkv                                                                          90%  963MB 221.7KB/s  07:50 ETA

Couldn't write to "Ray.Donovan.S01E03.720p.HDTV.x264-IMMERSE.mkv": Transport endpoint is not connected

 

Which crashed my shares. I'm rebooting now, and will check the syslog.

 

Edit: Doesn't look like anything too exciting or verbose in the log, but I've attached it. Crash happened after 00:00.

 

syslog-20130715-001224.txt.zip

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.