Suse 10.2 Iomega Zip Drive - Ha1.device.volume Doesn't Exist

I've been using SuSE for quite awhile for a number of releases with Iomega Zip Drives. Mine is currently a USB 250MB, but I believe this is probably applicable to other Iomega Zip Drives. I certainly don't claim to be an expert with Iomega Zip Drives, I am just listing what worked for me and has been very stable.

I started getting the following error on one of my systems. Method "Mount" with signature "ssas" on interface "org.freedesktop.Hal1.Device.Volume" doesn't exist

Surfing, I found others had same problem. A long story short; One group was saying it is necessary with SuSE 10.2 to have an Iomega Zip Disk in the drive when booting, otherwise it is not recognized. Looking in my logs, I confirmed this was happening. So, if I boot my system with the Zip disk in the drive, from then on the Zip drive works fine. The Icons appear on the desktop, I can mount, unmount, remove the disk, and this is repeatable. The only catch is, I have to have the disk in the drive just during the boot process. This just started happening with SuSE 10.2 on my systems.

On another system, I had a defective Iomega drive, so it was not recognized, of course, during the installation process and setup.

Here is what worked for me.

In etc/fstab I added the line:

/dev/sda4 /media/zip auto noauto,user 0 0

In /media, I added the directory /media/zip from then on the other system worked fine with the Iomega Zip Drive. Of course, I still had to do the boot procedure I already discussed.

I hope this might possibly help someone else having similar problems.

Duane

I've been using SuSE for quite awhile for a number of releases with Iomega Zip Drives. Mine is currently a USB 250MB, but I believe this is probably applicable to other Iomega Zip Drives. I certainly don't claim to be an expert with Iomega Zip Drives, I am just listing what worked for me and has been very stable.

I started getting the following error on one of my systems. Method "Mount" with signature "ssas" on interface "org.freedesktop.Hal1.Device.Volume" doesn't exist

Surfing, I found others had same problem. A long story short; One group was saying it is necessary with SuSE 10.2 to have an Iomega Zip Disk in the drive when booting, otherwise it is not recognized. Looking in my logs, I confirmed this was happening. So, if I boot my system with the Zip disk in the drive, from then on the Zip drive works fine. The Icons appear on the desktop, I can mount, unmount, remove the disk, and this is repeatable. The only catch is, I have to have the disk in the drive just during the boot process. This just started happening with SuSE 10.2 on my systems.

On another system, I had a defective Iomega drive, so it was not recognized, of course, during the installation process and setup.

Here is what worked for me.

In etc/fstab I added the line:

/dev/sda4 /media/zip auto noauto,user 0 0

In /media, I added the directory /media/zip from then on the other system worked fine with the Iomega Zip Drive. Of course, I still had to do the boot procedure I already discussed.

I hope this might possibly help someone else having similar problems.

Duane
[/b]

I need to add an update to my original post. I use Iomega disks between several systems here for a quick copy of some data, very handy here for our needs. I found an additional item to add to my original posting.

If after making sure fstab is as above, and media/zip exists as above, the error [Method "Mount" with signature "ssas" on interface "org.freedesktop.Hal1.Device.Volume" doesn't exist] returns, it is not necessary to have a zip disk in the drive when booting. I've found all I need to do is issue a manual mount just as user in a shell tool. mount /dev/sda4

After that, the zip drive icon indicates mounted, and unmount can be done just from the Iomega Icon. I'm using this approach on several systems and I never had any difficulties, now, using an Iomega zip drive on SuSE 10.2.

yup, same as here, although I auto-load the imm module for ZIP drives at boot time