Another workaround, which allows to automount the HDD and make it appear in
media managers like the one in KDE. It seems that the main problem with the
drive is caused by the fact that the "storage" and "volume" devices do not
appear in HAL when the disk is remounted without disconnecting the power. So,
the workaround is to add the devices manually using hal-device --add. The best
solution is to first mount the disk "properly" for the first time after
reconnecting the power and look into the output of hal-device for
"/org/freedesktop/Hal/devices/volume_uuid_<here_uuid_of_the_volume>" and its
parent e.g.
"/org/freedesktop/Hal/devices/storage_serial_Seagate_FreeAgentDesktop_6QG220EL_0_0".
Copy the parameter list into files e.g. volume.txt and storage.txt and then,
when the device is reconnected, use:
cat storage.txt | hal-device --add
"/org/freedesktop/Hal/devices/storage_serial_Seagate_FreeAgentDesktop_6QG220EL_0_0"
cat volume.txt | hal-device --add
"/org/freedesktop/Hal/devices/volume_uuid_<here_uuid_of_the_volume>"
This will make the drive appear in the media managers.
I wrote a script, which is run by udev and does that automatically. In udev
rules I added a file "99-usb-hd-fix.rules" (most of the Freeagent users have
that file anyway to solve the spin-down problem), which contains:
BUS=="scsi", ATTRS{vendor}=="Seagate*", ATTRS{model}=="FreeAgent*",
PROGRAM="vol_id --uuid %N", RUN+="/bin/usbhdfix %k %P"
Then, I created a script /bin/usbhdfix (attached), which solves the
spin-down problem as suggested in several places, and then creates the
hal devices. As I said, the property list is copied from hal-device, it
just needs to be checked that the property volume.is_mounted = false,
otherwise the mount managers will think that the disk is already mounted
and will not try to mount it themselves.
Hope this helps someone.
** Attachment added: "usbhdfix"
http://launchpadlibrarian.net/12162250/usbhdfix
--
external Seagate FreeAgent disk doesn't auto mount
https://bugs.launchpad.net/bugs/126825
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-volume-manager in ubuntu.
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
