Thu, 25 Jan 2024 21:35:27 +0100 "Carlos E. R." <robin.listas@telefonica.net> :
On 2024-01-25 15:05, Ben T. Fender wrote:
Thu, 25 Jan 2024 08:53:39 +0100 "Carlos E. R." <robin.listas@telefonica.net> :
On 2024-01-25 03:53, Ben T. Fender wrote:
After "fdisk -l" to validate that my booting drive is in fact /dev/sda
mount /dev/sda8 /0/sa08
because I want to work in partition 8
What I get in response is ========================================================== # 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. ==========================================================
Why is TW not letting me mount by confirmed device-name?
Why do you say it doesn't?
Because dolphin showed nothing under /0/sa07 :-)
What evidence have you shown?
The error message says /dev/sda7 is already mounted OR mountpoint is busy
Your original question implies that it does not allow you to mount by device name but allows you to mount by using some other method. You have not shown proof of this, in this message at least.
Maybe the error message should say WHERE it is mounted? The already-mounted bit couldn't be the reason because it's a path of my own making. I use canned mountpoints for often used mounts, this way my stuff never gets stepped on @ /mnt nor vice versa (below)
You have not shown that you can mount by another method.
Not sure I understand what more I can do If I do # mount UUID=4960ac17-a377-4007-84fd-45ee43713a57 /0/sa07 then it gets mounted there but tha's NOT what I want (not interested in copy-pasting uuids!) DMESG: [ 1072.223450] EXT4-fs (dm-7): mounted filesystem 4960ac17-a377-4007-84fd-45ee43713a57 r/w with ordered data mode. Quota mode: none. [ 1072.229397] audit: type=1400 audit(1706219199.152:130): apparmor="DENIED" operation="open" class="file" profile="nscd" name="/0/adat/u3/0DirectLink/hosts-nosnoop" pid=1341 comm="nscd" requested_mask="r" denied_mask="r" fsuid=473 ouid=1003
I could mount by using uuid but that wasn't what I commanded
AND, you have not shown that you read the error message and done what it told you to do.
the error message is incomplete and dmesg is in chinese:
Nonononono. ... Or, better still, you open a terminal, write "dmesg --follow", hit enter a few times, then on the original terminal issue the command. A few lines should print in the demsg terminal.
Just read those lines, and post them here.
cool, thanks for reminding me that I look like the lumberjack who struggled with a chainsaw without starting it :-) Ok, so I done that and it ended up looking like this: # mount /dev/sda7 /0/sa07 ERROR MESSAGE: mount: /0/sa07: /dev/sda7 already mounted or mount point busy. dmesg(1) may have more information after failed mount system call. DMESG: [ 434.252860] /dev/sda7: Can't open blockdev # mount /dev/sdc1 /0/sc01 NO ERROR DMESG: [ 457.306647] EXT4-fs (sdc1): warning: mounting fs with errors, running e2fsck is recommended [ 457.348560] EXT4-fs (sdc1): mounted filesystem 21655adc-bb12-4709-aaa7-faf4abdc8618 r/w with ordered data mode. Quota mode: none. [ 457.357989] audit: type=1400 audit(1706218584.296:113): apparmor="DENIED" operation="open" class="file" profile="nscd" name="/0/adat/u3/0DirectLink/hosts-nosnoop" pid=1341 comm="nscd" requested_mask="r" denied_mask="r" fsuid=473 ouid=1003 ...repeats last line a few times, then [ 765.151101] EXT4-fs (sdc1): error count since last fsck: 1166 [ 765.151137] EXT4-fs (sdc1): initial error at time 1681240940: ext4_lookup:1785: inode 231380078 [ 765.151161] EXT4-fs (sdc1): last error at time 1700089692: ext4_mb_generate_buddy:1215 this partition dies get mounted and am already dd-ing a slowroll backup to it # dd if=/dev/sda7 of=/0/sc01/OSes/m7-sR-2024-01-24.dd bs=16M status=progress