Ok, this used to work a few weeks ago… (I know, not very useful)
When I plug my USB drive in, the kernel sees it and I can mount it manually. However, it won’t automount. Can someone point me the way to dig deeper into this? I’ve done plenty of google searches but nothing I’ve tried has worked for ‘GNOME, SUSE 11.3.’ I am not sure if it is a permissions problem, configuration problem, a kernel automount, HID, or USB problem.
As DaaX has suggested, not unmounting correctly (Windows or Linux) can cause problems. The best method is to mount within Windows and let it check/reset/repair the partition.
However, you could try the ntfsfix utility from a console:
Yes, but if you used it improperly in windows, you’ll have to go back in windows, plug the drive and disconnect it properly. It doesn’t cost a lot to try it.
After that, try mounting and unmounting it in openSUSE.
Sorry, I missed that. Your using Gnome right? Maybe check media mounting with ‘gconf-editor’ utility. If the media mounting settings look ok, then we may have to look at policykit settings…
mark3397 wrote:
> It mounts fine. However, automount doesn’t work. Same log as before.
FWIW, I have a (possibly) similar problem. Gnome, 11.3 and an external
USB drive that used to automount and now doesn’t (see below).
I’ll check through this topic when I’m in front of the machine and
report whether it seems to really be the same or not. FWIW, the details
of my disk are:
Device Boot Start End Blocks Id System
/dev/sdb1 1 262 2104483+ c W95 FAT32 (LBA)
/dev/sdb2 263 1306 8385930 c W95 FAT32 (LBA)
/dev/sdb3 1307 120296 955787175 8e Linux LVM
/dev/sdb4 120297 121601 10482412+ c W95 FAT32 (LBA)
It used to automount the three fat32 partitions and now it just
automounts /dev/sdb4.
More of a nuisance, it used to be that I could plug it in and then just
mount an LV in the LVM partition.
mount /dev/backup_vg/backup_home_lv
Now, the LV is not detected and has to be manually discovered and
activated. The following were executed after the drive was plugged in
and had settled down for a while:
piglet:~ # lvscan
ACTIVE ‘/dev/pooh_vg/home’ [150.00 GiB] inherit
ACTIVE ‘/dev/pooh_vg/usr’ [50.00 GiB] inherit
piglet:~ # pvscan
PV /dev/sdb3 VG backup_vg lvm2 [911.51 GiB / 661.51 GiB free]
PV /dev/sda3 VG pooh_vg lvm2 [268.10 GiB / 68.10 GiB free]
Total: 2 [1.15 TiB] / in use: 2 [1.15 TiB] / in no VG: 0 [0 ]
piglet:~ # lvscan
inactive ‘/dev/backup_vg/backup_home_lv’ [250.00 GiB] inherit
ACTIVE ‘/dev/pooh_vg/home’ [150.00 GiB] inherit
ACTIVE ‘/dev/pooh_vg/usr’ [50.00 GiB] inherit
piglet:~ # lvchange -ay /dev/backup_vg/backup_home_lv
piglet:~ # lvscan
ACTIVE ‘/dev/backup_vg/backup_home_lv’ [250.00 GiB] inherit
ACTIVE ‘/dev/pooh_vg/home’ [150.00 GiB] inherit
ACTIVE ‘/dev/pooh_vg/usr’ [50.00 GiB] inherit
There is a Gnome GUI tool that can be used to check/configure policy settings.
Start the Authorizations tool either via the GNOME main menu by selecting More Applications+Tools+Authorizations or by pressing Alt+F2 and entering polkit-gnome-authorization.
In particular, the XML file /usr/share/PolicyKit/policy/org.freedesktop.hal.storage.policy contains a section that should look like this:
<action id="org.freedesktop.hal.storage.mount-removable">
<description>Mount file systems from removable drives.</description>
<message>System policy prevents mounting removable media</message>
<defaults>
<allow_inactive>no</allow_inactive>
<allow_active>yes</allow_active>
</defaults>
</action>
The ‘<allow active>’ (active console) part should be set to ‘yes’. It can be edited directly (with root privileges) if preferred.
