27

I have an internal HDD that gives this error when I try to mount either of its two partitions in Nautilus, while my main HDD works fine.

When I use Disks to mount it works but unmounting in Nautilus gives the same error. mount works too.

dmesg and syslog shows nothing special, so I don't know where to look for the relevant log. I hope someone can provide me some hints on this issue.

  • 4
    I solved this by going to GParted, choose the the partition, right click it and choose New UUID. Apply and done. Sorry for late reply but this question appears on Google. – dat tutbrus Jun 23 '16 at 11:50
  • 1
    @dattutbrus You should really post that as an answer, because it fixed it for me. – DanMan Jul 15 '16 at 18:13
  • @DanMan This post was last year... – dat tutbrus Jul 18 '16 at 3:41
  • 2
    @dattutbrus Yes, and? It's an answer, so it ought to be posted like one, so that people can upvote it. – DanMan Jul 18 '16 at 22:37
  • 1
    @dattutbrus please add it as an answer. It's still great today. I mean, nobody prefer temporary solutions. – Rodrigo Dec 8 '16 at 2:16
19

Apparently this question appeared on Google and many people are asking me to post an answer, so here it is.

  1. First, go to Dash (for Ubuntu) or run gparted using superuser, preferrably gparted-pkexec.
  2. Right click the partition, choose New UUID.
  3. Click the Apply button.

This solution should be permanent until you mess something up, so no worries.

Update: Some people claimed that just by having gparted refreshing information, the problems are solved. You should try that first, as refreshing UUID screws up fstab.

  • 3
    For me starting sudo gparted and just look at the partition was enough, I didn't have to change UUIDs or anything else. – ohno Apr 19 '18 at 11:43
8

I managed to workaround this issue online by simply restarting the gvfs-udisks2-volume-monitor user service:

systemctl --user restart gvfs-udisks2-volume-monitor

After that, mounting disks in Nautilus worked fine.

  • 2
    While the other methods haven't helped, this one has. You're a lifesaver! – Szymon Marczak Apr 8 '19 at 11:30
3

I have temporary solution, try mounting with

sudo mount /dev/... /mnt/tothisdir

Or use "Disk" to mount or any other but not nautilus

2

Maybe you should have a look at my Question & Solution for a detailed analysis ...

In short the GNOME Virtual File System or gvfs is not working at all.

However Do Not unmount & remove the /run/user/[USER ID]/gvfs folder as suggested by other posters here (default User ID is 1000).

Find your gvfs folder and [USER ID]

$ mount | grep gvfs
gvfsd-fuse on /run/user/[USER ID]/gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,user=jean)
$

List mount points used by gvfs. [NOTE: Since gvfs is not working it should be empty]

$ ls -als /run/user/[USER ID]/gvfs
total 0
0 dr-x------  2 jean jean   0 Dec 22 17:42 .
0 drwx------ 10 jean jean 260 Dec 22 17:42 ..
$

Check whether the gvfsd daemon process is active

$ ps axu | grep gvfsd
jean      5993  0.0  0.0 680372  6356 ?        Sl   17:42   0:00 /usr/lib/gvfs/gvfsd

Kill it with the following cmd.

$ sudo killall -9 gvfsd

Then relaunch the daemon (process)

$ sudo /usr/lib/gvfs/gvfsd-fuse /run/user/[USER ID]/gvfs

Well, that's it. It didn't show up straight as I needed to completely shutdown and restart the system (restarting the system without a complete shutdown will not work for me). But right after the system restart, gvfs worked fine and I had access to all partitions / drives within Nemo / Nautilus.

Previously, restarting the system would not solve anything.

0

Unmounting gvfs solved the problem for me:

umount -fl /home/user/.gvfs
rm -rf /home/user/.gvfs

I found that solution here

0

If botchniaque's fix doesn't work for you, first check the gvfs mountpoint on your system:

mount | grep gvfs

On Ubuntu 15.10 it was mounted under /run/user/[USER ID]/gvfs, so the following commands worked for me:

sudo umount -fl /run/user/[USER ID]/gvfs
sudo rm -rf /run/user/[USER ID]/gvfs
0

For me none of the mentioned solutions worked out. Or at least they did not work immediately.

However, after I rebooted the machine, the drive worked.

So I don't know, whether a simple reboot fixed it or the umount/rm -method and a reboot after those.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.