Transport endpoint is not connected

Question

FUSE is constantly every 2 - 3 days  giving me this Transport endpoint is not connected error on my mount point and the only thing that seems to fix it is rebooting    I currently have my mount points setup like this  I m not sure what other details I should add here so let me know if I missed anything     dev sdc1  mnt hdd2 ext4 defaults 0 0  dev sdb1  mnt hdd1 ext4 defaults 0 0 mhddfs  mnt hdd1  mnt hdd2  data fuse defaults allow other 0 0

User · Answer

I had this problem when using X2Go  The problem happened in a folder that was shared between the remote computer and my local PC    Solution  cd out of that folder and in again  That fixed it

User · Answer

So interestingly enough this error  Transport endpoint is not connected  was caused by my having more than one Veracrypt device mounted  I closed the extra device and suddenly I had access to the drive  Hmm

User · Answer

I have exactly the same problem  I haven t found a solution anywhere  but I have been able to fix it without rebooting by simply unmounting and remounting the mountpoint   For your system the commands would be   fusermount -uz  data mount  data   The -z forces the unmount  which solved the need to reboot for me  You may need to do this as sudo depending on your setup  You may encounter the below error if the command does not have the required elevated permissions      fusermount  entry for  data not found in  etc mtab   I m using Ubuntu 14 04 LTS  with the current version of mhddfs

User · Answer

This typically is caused by the mount directory being left mounted due to a crash of your filesystem  Go to the parent directory of the mount point and enter fusermount -u YOUR MNT DIR   If this doesn t do the trick  do sudo umount -l YOUR MNT DIR

User · Answer

I get this error from the sshfs command from Fedora 17 linux to debian linux on the Mindstorms EV3 brick over the LAN and through a wireless connection   Bash command   el defiant  mnt   sshfs root 192 168 13 102  root -p 22  mnt ev3 fuse  bad mount point   mnt ev3   Transport endpoint is not connected   This is remedied with the following command and trying again   fusermount -u  mnt ev3   These additional sshfs options prevent the above error from concurring   sudo sshfs -d -o allow other -o reconnect -o ServerAliveInterval 15 root myremoteserver com  var lib redmine plugins  mnt -p 12345 -C   In order to use allow other above  you need to uncomment the last line in  etc fuse conf     Set the maximum number of FUSE mounts allowed to non-root users    The default is 1000     mount max   1000    Allow non-root users to specify the  allow other  or  allow root    mount options    user allow other   Source  http   slopjong de 2013 04 26 sshfs-transport-endpoint-is-not-connected

User · Answer

Now this answer is for those lost souls that got here with this problem because they force-unmounted the drive  but their hard drive is NTFS Formatted  Assuming you have ntfs-3g installed  sudo apt-get install ntfs-3g    sudo ntfs-3g  dev hdd  mnt mount point -o force   Where hdd is the hard drive in question and the   mnt mount point  directory exists   NOTES  This fixed the issue on an Ubuntu 18 04 machine using NTFS drives that had their journal files reset through sudo ntfsfix  dev hdd and unmounted by force using sudo umount -l  mnt mount point  Leaving my answer here in case this fix can aid anyone

User · Answer

There is a segmentation fault problem which was introduced in 0 1 39  You may check my repository that fixed this one in meanwhile  https   github com vdudouyt mhddfs-nosegfault

[mount] Transport endpoint is not connected

Examples related to mount

Examples related to fuse