From 60cfc79a87721233a71f308df7e231d591313e11 Mon Sep 17 00:00:00 2001 From: tiyn Date: Tue, 21 Mar 2023 04:39:42 +0100 Subject: [PATCH] disk-management: mount error transport not connected added --- wiki/linux/disk-management.md | 23 +++++++++++++++++++++++ 1 file changed, 23 insertions(+) diff --git a/wiki/linux/disk-management.md b/wiki/linux/disk-management.md index 24b23ee..3213d40 100644 --- a/wiki/linux/disk-management.md +++ b/wiki/linux/disk-management.md @@ -99,6 +99,9 @@ Especially for large file systems this might take a while. ## Error solving +This section addresses various problems that can occur and are related to +disk-management. + ### sudo: unable to open ... Read-only file system Ususally the filesystem will go into read-only mode whe the system is running @@ -110,3 +113,23 @@ To fix it run: `fsck from util-linux 2.20.1` you may want to try using the ext4-specific fsck: - `fsck.ext4 -f /dev/sda1` + +### cannot access: Transport endpoint is not connected + +This error message can occur if a mounted directory is left mounted due to a +crash of the filesystem but not accessible anymore. +This error can be fixed and the directory made accessible again by running the +following command. + +```sh +fusermount -u +``` + +If this does not work the following command can be used to unmount the device. + +```sh +umount -l +``` + +This section is based on a reply by +[Jonathan Brown on Stack Overflow](https://stackoverflow.com/questions/16002539/fuse-error-transport-endpoint-is-not-connected).