this post was submitted on 26 Apr 2024
27 points (90.9% liked)

Linux

8066 readers
58 users here now

Welcome to c/linux!

Welcome to our thriving Linux community! Whether you're a seasoned Linux enthusiast or just starting your journey, we're excited to have you here. Explore, learn, and collaborate with like-minded individuals who share a passion for open-source software and the endless possibilities it offers. Together, let's dive into the world of Linux and embrace the power of freedom, customization, and innovation. Enjoy your stay and feel free to join the vibrant discussions that await you!

Rules:

  1. Stay on topic: Posts and discussions should be related to Linux, open source software, and related technologies.

  2. Be respectful: Treat fellow community members with respect and courtesy.

  3. Quality over quantity: Share informative and thought-provoking content.

  4. No spam or self-promotion: Avoid excessive self-promotion or spamming.

  5. No NSFW adult content

  6. Follow general lemmy guidelines.

founded 1 year ago
MODERATORS
 

~~System is Arch Linux. NTFS-3G is installed. I have had this problem on Gnome (Nautilus) and KDE (Dolphin). I already tried fixing it with Testdisk. No success. Any help is appreciated.~~

UPDATE: I have re-formatted the disk and it is working now. Thank you for all your suggestions and tips.

top 10 comments
sorted by: hot top controversial new old
[–] BestBouclettes@jlai.lu 6 points 6 months ago* (last edited 6 months ago) (1 children)

Disks mounted via your user are mounted differently than when you sudo or with root. The driver needs FUSE support to allow you to mount it via your user.

You can find more info here: https://wiki.archlinux.org/title/NTFS-3G#Allowing_user_to_mount

[–] nebulaone@lemmy.world 2 points 6 months ago

I ran Nautilus with root privileges, same error message. I will read about FUSE support, though, thanks.

[–] Kerb@discuss.tchncs.de 6 points 6 months ago* (last edited 6 months ago) (2 children)

thats probably ~~part~~ par of the course for the arch experience

id check if Udisks is installed and running.

[–] CameronDev@programming.dev 8 points 6 months ago

Off topic, but the phrase you are looking for is "Par for the course" :)

[–] nebulaone@lemmy.world 3 points 6 months ago

Thanks, I will do that. Currently reading the ArchWiki entry on udisks.

[–] tal@lemmy.today 5 points 6 months ago (1 children)

I have no idea what that GUI thing is you're using to do the mount, but I note that the CLI and the GUI are not using the same mountpoint. Is it possibly the case that the directory /mnt/storage2 exists but /run/media/void/2TB does not?

[–] nebulaone@lemmy.world 1 points 6 months ago (1 children)

When I create 2TB It tries to mount at 2TB1.

[–] nebulaone@lemmy.world 1 points 6 months ago

GUI is the default Gnome file manager (Nautilus).

[–] palordrolap@kbin.social 2 points 6 months ago (1 children)

If you're using GNOME or a derivative, you should probably be using gio mount to do the same mounting as the file manager would. Then again, you say that the file manager isn't working, so gio mount probably won't work either.

I admit I had no idea about the guts of this - and maybe still don't - but the user who suggested looking at udisks is probably right. It's always been there in the background as long as I remember (Mint/Cinnamon, many years), and has hooks into something I mounted with gio after the last reboot.

Another search term that might help is "gvfs", or GNOME virtual file system, which I've definitely poked around with before.

Importantly, Nautilus and gio don't need sudo because they call into what's already running. They (or the subsystem) automatically create the mount point directory (and remove it on unmount). If the directory already exists, they use the "append a 1" technique you experienced, presumably so they don't clobber or hide something that might be important.

[–] nebulaone@lemmy.world 1 points 6 months ago

At this point I will probably just back up all the files and re-format the disk, as I can mount usb flash drives without any issue, so I am assuming there is something wrong with the external hard drive.