Re: why is my local user (/dev/sda5) drive not being displayed by df?
On 07/03/2020 08:44, Albretch Mueller wrote:
> $ sudo blkid
> /dev/mapper/sda5_crypt: UUID="HA3h3P-GUUe-brth-12Jb-VYcF-sE7h-l7Ep7Q"
> TYPE="LVM2_member"
> /dev/mapper/lbrtchx--vg-root:
> UUID="d2f3c65d-063b-441e-878e-e283e9ab39a2" TYPE="ext4"
> /dev/sda1: UUID="22e7b834-11f9-4f29-84d2-8757aa9f721d" TYPE="ext2"
> PARTUUID="c67530bc-01"
> /dev/sda5: UUID="27928fd6-a5a9-47a7-8e84-c65c2e2ed1df"
> TYPE="crypto_LUKS" PARTUUID="c67530bc-05"
> /dev/mapper/lbrtchx--vg-swap_1:
> UUID="0e990461-59f0-470c-9e07-c2942e683d2a" TYPE="swap"
>
> $ sudo df --human-readable --all
> Dateisystem Größe Benutzt Verf. Verw% Eingehängt auf
> sysfs 0 0 0 - /sys
> proc 0 0 0 - /proc
> udev 1,8G 0 1,8G 0% /dev
> devpts 0 0 0 - /dev/pts
> tmpfs 356M 11M 346M 3% /run
> /dev/mapper/lbrtchx--vg-root 289G 131G 144G 48% /
> securityfs 0 0 0 - /sys/kernel/security
> tmpfs 1,8G 105M 1,7G 6% /dev/shm
> tmpfs 5,0M 4,0K 5,0M 1% /run/lock
> tmpfs 1,8G 0 1,8G 0% /sys/fs/cgroup
> cgroup 0 0 0 - /sys/fs/cgroup/systemd
> pstore 0 0 0 - /sys/fs/pstore
> cgroup 0 0 0 -
> /sys/fs/cgroup/cpu,cpuacct
> cgroup 0 0 0 - /sys/fs/cgroup/freezer
> cgroup 0 0 0 -
> /sys/fs/cgroup/net_cls,net_prio
> cgroup 0 0 0 - /sys/fs/cgroup/cpuset
> cgroup 0 0 0 - /sys/fs/cgroup/memory
> cgroup 0 0 0 - /sys/fs/cgroup/pids
> cgroup 0 0 0 - /sys/fs/cgroup/devices
> cgroup 0 0 0 - /sys/fs/cgroup/perf_event
> cgroup 0 0 0 - /sys/fs/cgroup/blkio
> systemd-1 - - - - /proc/sys/fs/binfmt_misc
> hugetlbfs 0 0 0 - /dev/hugepages
> debugfs 0 0 0 - /sys/kernel/debug
> mqueue 0 0 0 - /dev/mqueue
> /dev/sda1 236M 66M 159M 30% /boot
> tmpfs 356M 20K 356M 1% /run/user/1000
> binfmt_misc 0 0 0 - /proc/sys/fs/binfmt_misc
> $
> ~
> lbrtchx
>
Please include your question in the body as well. The subject should be
a summary of the email, not part of it.
df shows mounted filesystems. So your sda5 is not mounted.
Since it seems to be a LUKS encrypted volume, it cannot be mounted, but
rather it's contents can be decrypted and mounted (sda5_crypt).
... Except that sda5_crypt seems to be a LVM physical volume, so you
don't mount that directly either, you mount the logical volumes.
/dev/mapper/lbrtchx--vg-root seems to be one of those volumes.
Try running lsblk, it should show the device tree.
--
We don't know who it was that discovered water, but we're pretty sure
that it wasn't a fish.
-- Marshall McLuhan
Eduardo M KALINOWSKI
eduardo@kalinowski.com.br
Reply to: