1
0
mirror of https://github.com/tiyn/wiki.git synced 2025-04-19 06:07:44 +02:00

Compare commits

...

2 Commits

Author SHA1 Message Date
6b94612159 disk-management: add umount 2023-03-21 04:49:45 +01:00
60cfc79a87 disk-management: mount error transport not connected added 2023-03-21 04:39:42 +01:00

View File

@ -42,6 +42,13 @@ The dump flag signals if the file system should be dumped.
The `fsck` order signals if a file system should be checked at boot.
Boot partitions should be flagged with a `1` for this reason, otherwise `0`.
For undoing the mount the `umount` command can be used.
The following is a command to unmount a device from a specified directory.
```sh
umount <path to mount point>
```
## Create Partition
In the following it is assumed that the disk is `/dev/sda`
@ -99,6 +106,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 +120,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 <path to mount point>
```
If this does not work the following command can be used to unmount the device.
```sh
umount -l <path to mount point>
```
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).