You are not authorized to mount this device [External HDD]

cat /etc/fstab
lsblk
sudo blkid
3 Likes

sdb Transcend is my usb hdd.

cat /etc/fstab
File: /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a device; this may
# be used with UUID= as a more robust way to name devices that works even if
# disks are added and removed. See fstab(5).
#
# <file system>             <mount point>  <type>  <options>  <dump>  <pass>
UUID=7DF3-82DA                            /boot/efi      vfat    umask=0077 0 2
UUID=22d356d9-8602-4ffa-af8f-150a79ea6337 /              btrfs   subvol=/@,defaults,noatime,autodefrag,compres
s=zstd,discard=async,ssd 0 0
UUID=22d356d9-8602-4ffa-af8f-150a79ea6337 /home          btrfs   subvol=/@home,defaults,noatime,autodefrag,com
press=zstd,discard=async,ssd 0 0
UUID=22d356d9-8602-4ffa-af8f-150a79ea6337 /root          btrfs   subvol=/@root,defaults,noatime,autodefrag,com
press=zstd,discard=async,ssd 0 0
UUID=22d356d9-8602-4ffa-af8f-150a79ea6337 /srv           btrfs   subvol=/@srv,defaults,noatime,autodefrag,comp
ress=zstd,discard=async,ssd 0 0
UUID=22d356d9-8602-4ffa-af8f-150a79ea6337 /var/cache     btrfs   subvol=/@cache,defaults,noatime,autodefrag,co
mpress=zstd,discard=async,ssd 0 0
UUID=22d356d9-8602-4ffa-af8f-150a79ea6337 /var/log       btrfs   subvol=/@log,defaults,noatime,autodefrag,comp
ress=zstd,discard=async,ssd 0 0
UUID=22d356d9-8602-4ffa-af8f-150a79ea6337 /var/tmp       btrfs   subvol=/@tmp,defaults,noatime,autodefrag,comp
ress=zstd,discard=async,ssd 0 0
tmpfs                                     /tmp           tmpfs   defaults,noatime,mode=1777 0 0
lsblk
NAME   MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
sda      8:0    0 223.6G  0 disk
├─sda1   8:1    0   300M  0 part /boot/efi
└─sda2   8:2    0 223.3G  0 part /var/tmp
/var/log
/var/cache
/srv
/root
/home
/
sdb      8:16   0 931.5G  0 disk
└─sdb1   8:17   0 931.5G  0 part /run/media/antik/Transcend
zram0  254:0    0  15.6G  0 disk [SWAP]
sudo blkid

/dev/sda2: UUID="22d356d9-8602-4ffa-af8f-150a79ea6337" UUID_SUB="6a5f30dd-bc7e-4ca1-b162-7f7faf327630" BLOCK_S
IZE="4096" TYPE="btrfs" PARTLABEL="root" PARTUUID="ab4710eb-8f79-4647-9438-c9bae4cd4240"
/dev/sdb1: LABEL="Transcend" BLOCK_SIZE="512" UUID="3656C74656C70619" TYPE="ntfs" PARTUUID="f1d12b96-01"
/dev/sda1: LABEL_FATBOOT="NO_LABEL" LABEL="NO_LABEL" UUID="7DF3-82DA" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="5
4cc2719-16a0-cf4b-8d65-f4ccfcfab85d"
/dev/zram0: LABEL="zram0" UUID="19f47e6f-e169-42ea-848c-a5b6bae5aaf4" TYPE="swap"

NTFS filesystems need to be mounted a specific way. Often people are successful adding a special entry for it in /etc/fstab, but be mindful that often times you need to be specific about permissions while writing the entry.

Here is an example of an entry from Arch Wiki:

/dev/*NTFS-partition* /mnt/windows ntfs-3g uid=username,gid=username,dmask=022,fmask=133 0 0

Here is where you can learn more about this: NTFS-3G - ArchWiki

Here is an example of another thread where a similar solution was discussed: Write on file's SSD NTFS not working - #11 by dalto

3 Likes

I do not understand where to write this line. Can you please specify what and where to write? Because I am pretty much a new user in linux and it is not clear to me.

sudo micro /etc/fstab

It is important you have the entry exactly right before you save.

2 Likes

Maybe use kate, it's a little easier than micro, but micro is the best cli, for me.
kate ask about root password if you try to save the file, do not start with sudo!

1 Like

So I put this line

/dev/*NTFS-partition* /mnt/windows ntfs-3g uid=username,gid=username,dmask=022,fmask=133 0 0

just below this?
tmpfs /tmp tmpfs defaults,noatime,mode=1777 0 0

Dos not matter, use last line :slight_smile:

1 Like

So I pasted

/dev/*NTFS-partition* /mnt/windows ntfs-3g uid=username,gid=username,dmask=022,fmask=133 0 0

at the last line by replacing "username" to my os username, saved and reboot, my system broke and went to maintenance mode. I removed the line and then reboot and got back to the os.
It showed something like failed dependency /mnt/windows

You do not change to the path?
Or UUID.

1 Like

No. My bad :grin:. So, I put lsblk above. Now, do I put /run/media/antik/Transcend or I put /dev/sdb or /dev/sdb1 ?

Try :slight_smile: :slight_smile:

2 Likes

I put

/dev/sdb1 /mnt/windows ntfs-3g uid=username,gid=username,dmask=022,fmask=133 0 0

Again breaks the system. I did put the real username of my os account.

setfont: KDFONTOP: Function not implemented
[FAILED] Failed to mount /mnt/windows.
[DEPEND] Dependency failed for Local File Systems.
[ OK ] Finished Create Volatile Files and Directories.
................

And again goes into the maintenance mode.

Did you make that directory first?

sudo mkdir /mnt/windows

1 Like

It already exists.

Can you post lsblk -f?

Maybe try without dmask and fmask too.

/dev/sdb1 /mnt/windows ntfs-3g uid=username,gid=username 0 0
lsblk -f
NAME   FSTYPE FSVER LABEL     UUID                                 FSAVAIL FSUSE% MOUNTPOINTS
sda
├─sda1 vfat   FAT32 NO_LABEL  7DF3-82DA                             298.8M     0% /boot/efi
└─sda2 btrfs                  22d356d9-8602-4ffa-af8f-150a79ea6337  191.4G    14% /var/tmp
/root
/var/log
/srv
/home
/var/cache
/
sdb
└─sdb1 ntfs3        Transcend 3656C74656C70619
zram0                                                                             [SWAP]

Oh you may need to give yourself (user) access rights to the mount point.

sudo chown -R uid:gid /mnt/windows

uid and gid are the same user and group you've been using (username:username).

1 Like

any specific reason (maybe i missed it) that you aren't using ext3/4/btrfs for the file system on the external? first thing i did to my wd passport backup drive was repartition it to ext4, as I don't need to use it in windows.

1 Like

When I reboot, it says,

[39.861000] watchdog: watchdog0: watchdog did not stop!
[39.876031] sd-umount[639]: Failed to unmount /oldroot: Device or resource busy
[39.876367] sd-umount[640]: Failed to unmount /oldroot/dev: Device or resource busy
[39.876815] shutdown[1]: Failed to finalize file systems, ignoring.

then it stucks. Then when I unplug the usb hdd then it reboots.
I do not understand. I was using garuda dragonized gaming edition iso of January 2022 and it never cause me problem. But this March 2022 iso whenever I tried to start install using nvidia driver it always stuck at Plymount. Now it is causing this. I am tired of uninstall and reinstalling os for one week. Anyways, trying sudo chown -R and let you know. However, the forum says that I'll be able to post after 21 hours. Man!!! I tried chown but did not work.