You are not logged in.
Hi,
I have a small problem for a few weeks now. Since an update my internal harddrives are mounted automatically at boot.
I'm using Gnome 3.
When I try to unmount the drive(s)/partitions in Nautilus (using the eject Symbol) I get following error:
Error ejecting /dev/sdc: Command-line `eject "/dev/sdc"' exited with non-zero exit status 1: eject: unable to eject
How can I solve this problem?
Thanks
EDIT: I want to know, if this problem can cause data corruption because the drive is not unmounted successfully. Or does it unmount the partitions and fails with "ejecting" because these are internal drives?
Last edited by Shino (2016-02-14 11:08:26)
Offline
/dev/sdc is the device, not a partition (like /dev/sdc1 would be), so no wonder ejecting fails.
can you post your /etc/fstab, or at least the part about the drives you have this issue with?
There shouldn't be any risk of data corruption just because the drive fails to eject.
Offline
/dev/sdc is the device, not a partition (like /dev/sdc1 would be), so no wonder ejecting fails.
can you post your /etc/fstab, or at least the part about the drives you have this issue with?There shouldn't be any risk of data corruption just because the drive fails to eject.
/dev/sdc is not in my fstab. It's a drive I use for data storage only and I mount it when necessary. Since an update my PC automatically mounts this drive on boot (which is really annoying).
Is there a way to disable autmount of internal harddrives?
Thanks
Offline
The problem isn't only your, I've the same issue and happens for every partition in every drive, regardless of fstab. gnome-something mounts every devices automatically and cannot unmount them (if I try to un mount a single partition, it unmounts every partition for the same disk).
This is somewhat due to a recent update.
Offline
have you tried to track down which update caused this?
grepping pacman.log reveals that extra/gnome-disk-utility got an update a couple of weeks ago. Maybe it introduced this bug?
I can't test here since I have no "external" filesystems and am not experiencing this issue
Offline
It's caused by the kernel. If you can disable hotplugging in your BIOS, that will work as a temporary fix.
https://bugzilla.kernel.org/show_bug.cgi?id=111651
https://bbs.archlinux.org/viewtopic.php?id=208514
Offline