Fri, 26 Jan 2024 20:50:00 +0100 "Carlos E. R." <robin.listas@telefonica.net> :
On 2024-01-26 20:43, Ben T. Fender wrote:
It's possible, but now I'm definitely on part-8 and
# mount /dev/sda7 /0/sa07 mount: /0/sa07: /dev/sda7 already mounted or mount point busy. dmesg(1) may have more information after failed mount system call.
DMESG: [ 3623.707590] audit: type=1400 audit(1706298089.239:537): apparmor="DENIED" operation="open" class="file" profile="nscd" name="/0/adat/u3/0DirectLink/hosts-nosnoop" pid=1388 comm="nscd" requested_mask="r" denied_mask="r" fsuid=473 ouid=1003 [ 3628.696970] /dev/sda7: Can't open blockdev
Andrei told you the reason. They are in exclusive use by device-mapper. So "Can't open blockdev".
Ok, they're locked out but not mounted, then that's what the error message should say. So how can I find out WHY they are locked out by device-manager? They have nothing to do with the booted system but they do make it impossible to do anything in them from the booted system, is this something from redhat too?