partition appears to be mounted, but not according to umount or lsblk
Hello lovely debianizers,
My Debian 10 machine has two physical disks, sda and sdb. The
(encrypted) root filesystem is on sdb, meanwhile I’ve used
fstab/crypttab to mount an (encrypted) partition on sda to
/mnt/data01-hdd, where I’ve stored some stuff:
user@hostname:/$ ls -gh /mnt/data01-hdd/
total 4.0K
drwxr-xr-x 5 1007 4.0K Jan 1 23:02 backups
However, when i do
user@hostname:/$ sudo umount /mnt/data01-hdd
umount complains thus:
umount: /mnt/data01-hdd: not mounted.
How can I unmount the partition?
lsblk -f doesn’t show the partition as mounted, which is something that
I don’t understand:
user@hostname:~$ sudo lsblk -f
NAME FSTYPE LABEL UUID
FSAVAIL FSUSE% MOUNTPOINT
sda
└─sda1 crypto_LUKS
400a161c-0654-4596-9b1c-3900ef504cb5
└─sda1_crypt LVM2_member
6I1ePw-7IuN-DQqN-02rs-vDgM-e3Nh-DUkfK0
└─1Terabyte01--vg-data01 ext4
900e8322-5af6-4ecd-827d-fae54f21e4f3
sdb
├─sdb1 ext2
0791c90e-8567-48c9-90a8-67c7c6619359 359.1M 18% /boot
├─sdb2
└─sdb5 crypto_LUKS
2b5a5240-9d34-42af-958a-a2a4509382d8
└─sdb5_crypt LVM2_member
q9xOdL-yo0s-CDK9-eYiV-0uya-sX7o-WIvPZH
├─debian--vg-root ext4
4248fdef-e86c-456a-8fc7-2a4ec5b1b0df 195.7G 52% /
└─debian--vg-swap_1 swap
5cc35d37-c746-4bc5-9d00-f437061f6cc8 [SWAP]
The configuration files:
user@hostname:/$ cat /etc/fstab
# /etc/fstab: static file system information.
# <file system> <mount point> <type>
<options> <dump> <pass>
/dev/mapper/debian--vg-root / ext4
errors=remount-ro 0 1
# /boot was on /dev/sdb1 during installation
UUID=0791c90e-8567-48c9-90a8-67c7c6619359 /boot ext2
defaults 0 2
/dev/mapper/debian--vg-swap_1 none swap sw
0 0
# 1000gb hdd via its LVM, cf. also /etc/crypttab
#/dev/mapper/1Terabyte01--vg-data01 /mnt/data01-hdd ext4
default
user@hostname:/$ cat /etc/crypttab
# sdb5 - debian 10 / yunohost on 500Gb HDD
# Tell cryptsetup to create the volume sdb5_crypt from /dev/sdb5
(identified
# by its UUID). Don't use a key file. Since this is the root device, it
will
# automatically be processed during the initramfs stage of boot (making
it
# accessible to dropbear).
#
sdb5_crypt UUID=2b5a5240-9d34-42af-958a-a2a4509382d8 none luks,discard
# sda1 - data on 1000Gb HDD
# Tell cryptsetup to create the volume sda1_crypt from /dev/sda1
(identified
# by its UUID) using the sda1.luks key. Since this is not a root device,
we
# explicitly require that the device be processed during the initramfs
stage.
#
sda1_crypt UUID=400a161c-0654-4596-9b1c-3900ef504cb5 /etc/keys/sda1.luks
luks,initramfs
I’d much apreciate your guidance!
Thyme Harp
Reply to: