zip drive won't work

[Chess007]

I've googled and tried to get this thing working, but eh... no success.

root@locomotive:/home/stewie00right # mnt /dev/hdd4
bash: mnt: command not found
root@locomotive:/home/stewie00right # mnt hdd4
bash: mnt: command not found
root@locomotive:/home/stewie00right # mount hdd4
mount: can't find hdd4 in /etc/fstab or /etc/mtab
root@locomotive:/home/stewie00right # mkdir /mnt/zip
root@locomotive:/home/stewie00right # insmod parport
insmod: can't read 'parport': No such file or directory
root@locomotive:/home/stewie00right # mount -t msdos /dev/hdd4 /mnt/zip
mount: special device /dev/hdd4 does not exist
root@locomotive:/home/stewie00right # cd /mnt/zip
root@locomotive:/mnt/zip # ls -a
. ..
root@locomotive:/mnt/zip # ls -a
. ..
root@locomotive:/mnt/zip #

That is after I installed a program called "jazip." It was saposed to make the zip drive work. No such luck.

In the Ubuntu 'Device Manager' it reads:

IDE device (slave)
IOMEGA ZIP 100 ATAPI

Under the advanced tab it reads:
block.device string /dev/hdd4

The specs i've read seem to indicate that this drive is an IOMEGA ZIP 250, not 100.

Edit 1:
The error in Konquerer is

"Could not mount device.

The reported error was:

mount: can't find /dev/hdd4 in /etc/fstab or /etc/mtab"

So, maybe I have to edit fstab...what line should I add for a 100mb zip disk thats been formated with a fat file system?


Edit 2:

Here's the contents of my fstab file.

# /etc/fstab: static file system information.
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
/dev/hda1 / ext3 defaults,errors=remount-ro 0 1
/dev/hda5 none swap sw 0 0
/dev/hdc /media/cdrom0 udf,iso9660 ro,user,noauto 0 0
/dev/fd0 /media/floppy0 auto rw,user,noauto 0 0

In any event, I just want to make it work. Thanks in advance. :)

[je_fro]

/dev/hdd4 /mnt/zip auto rw,users,noauto 0 0

but that makes no sense to me...try:

/dev/hdd1 /mnt/zip auto rw,users,noauto 0 0

[banzaikai]

je_fro
/dev/hdd4
but that makes no sense to me...try:
Doesn't make sense to me, either, but all my Zips have mounted as /dev/blahblah4.

Chess007
/dev/hdc /media/cdrom0 udf,iso9660 ro,user,noauto 0 0
Looks like you're using HAL (hald). This can be a pain, as it uses "fstab-sync" to auto-update the fstab, and if you don't have a disk in the Zip, it sometimes deletes that line from it, thinking that the drive is no longer there. My fstab looks like:
/dev/hdb4 /media/zip auto pamconsole,exec,noauto,managed 0 0
/dev/hdc /media/cdrecorder auto pamconsole,exec,noauto,managed 0 0
Oh, I'm using FC4, so YMMV...

To mount manually, I'd try:
mount -t auto /dev/hdd4 /media/zip
(or)
mount -t vfat /dev/hdd4 /media/zip

It shouldn't matter that you've got the Zip250 drive with a Zip100 disk - it'll work. It will matter if the disk is a 250 and the drive is a 100, though.

banzai "Zip codes" kai

[Chess007]

"Doesn't make sense to me, either, but all my Zips have mounted as /dev/blahblah4."

for some reason hdd4 seems to be how iomega zip drives show up.

tried adding

/dev/hdd4 /mnt/zip auto rw,users,noauto 0 0


Do I need to space the words the same way that they are in the fstab?

And i had the zip disk in during boot... The error:

root@locomotive:/home/stewie00right # mount -t auto /dev/hdd4 /mnt/zip
mount: special device /dev/hdd4 does not exist
root@locomotive:/home/stewie00right #

i'll try the other lines now.

if i try anything other than the first line recommend by Jefro, i get "This device does not exsist." If I use his line, i get an error:

special device /dev/hdd4 does not exist


So, it lives in the device manager, but it can't be accessed or used.

root@locomotive:/home/stewie00right # mount -t auto /dev/hdd4 /mnt/zip
mount: special device /dev/hdd4 does not exist
root@locomotive:/home/stewie00right # mount /mnt/zip
mount: special device /dev/hdd4 does not exist

(gedit:7004): GnomeUI-WARNING **: While connecting to session manager:
Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed.
root@locomotive:/home/stewie00right # mount /dev/hdd1 /mnt/zip
mount: special device /dev/hdd1 does not exist
root@locomotive:/home/stewie00right # sudo gedit /etc/fstab

(gedit:7059): GnomeUI-WARNING **: While connecting to session manager:
Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed.
root@locomotive:/home/stewie00right # mount -t auto /dev/hdd4 /media/zip
mount: mount point /media/zip does not exist
root@locomotive:/home/stewie00right # mount -t vfat /dev/hdd4 /media/zip
mount: mount point /media/zip does not exist
root@locomotive:/home/stewie00right # cd media
bash: cd: media: No such file or directory
root@locomotive:/home/stewie00right # cd /media/
root@locomotive:/media # cd zip
bash: cd: zip: No such file or directory
root@locomotive:/media # mkdir zip
root@locomotive:/media # cd zip
root@locomotive:/media/zip # mount
/dev/hda1 on / type ext3 (rw,errors=remount-ro)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
devpts on /dev/pts type devpts (rw,gid=5,mode=620)
tmpfs on /dev/shm type tmpfs (rw)
/dev on /.dev type unknown (rw,bind)
none on /dev type tmpfs (rw,size=5M,mode=0755)
usbfs on /proc/bus/usb type usbfs (rw)
root@locomotive:/media/zip # mount /zip/
mount: can't find /zip/ in /etc/fstab or /etc/mtab
root@locomotive:/media/zip #

[banzaikai]

for some reason hdd4 seems to be how iomega zip drives show up.
Yes, I was just letting je_fro know that. I think it has something to do with Iomega setting the Zip to an internal LUN of 4, but how that translates to IDE/USB is what's got me confused.

Do I need to space the words the same way that they are in the fstab?
Nope. It's just for readability. As long as there's one space between entries, you're okay.

mount: special device /dev/hdd4 does not exist
Okay, then. Have you tried /dev/hdb4? It should go like this:
hda4 = Pri Mstr
hdb4 = Pri Slv
hdc4 = Sec Mstr
hdd4 = Sec Slv # <-- Iomega default config/recommendation
Now, if you just type in the mount command without anything else, it'll show you what's there:
[banzai@blossom ~]$ mount
/dev/hda3 on / type ext3 (rw)
/dev/hda1 on /boot type ext3 (rw)
blah...blah
So if you see /dev/hdb# already in there, then it's either hdc or hdd. Also, try using hdd1 anyway, just to see what happens.

Oh, and for "Mounting Things 101": the first half of the command mounts the hardware and filesystem (the "mount -t auto /dev/hdd4" part), and the second sets the filesystem directory that the files get sent to (the "/mnt/zip" part). On FC, it now goes to the /media directory for all removable devices. Your distro may still use /mnt (but your output says the CD and Floppy are using /media). You may still be using hotplug, which is a different config altogether. If you're getting an error that flags the "/dev/hdd4", then it's not finding the device. If you get an error about the "/mnt/zip", then it's either permissions or directory not there. Based on the last output, I'd try (cut and paste):
mkdir /media/zip
mount -t auto /dev/hdb4 /media/zip
mount -t auto /dev/hdc4 /media/zip
mount -t auto /dev/hdd4 /media/zip
mount -t auto /dev/hdd1 /media/zip
If none of these work, then see if you need to have the HAL daemon running (hald). HAL has replaced hotplug and udev on many distros. If one of these lines do work, then just copy that info over to your fstab (assuming that, like mine, your zip is at hdb4):
/dev/hdb4 /media/zip auto rw,users,noauto 0 0
and then restart the machine to have it pick up the changes.

banzai "Zip zapped" kai

[je_fro]

<an_aside>You know, I've lost more data because of those damn zip disks. I'm glad they are finally going away...</an_aside>

[Chess007]

None of that worked. *sigh* So, how do I make the HAL daemon run?

[pyavitz]

my zip(s) have always fallen under /dev/sda4
i've never seen one fall under /dev/hd*?

[banzaikai]

Chess007:
None of that worked. *sigh* So, how do I make the HAL daemon run?
Check this (https://launchpad.net/distros/ubuntu/+source/dbus/+bug/31517) out. It may be a bug between HAL and D-Bus.
If this fails, you may want to try a shutdown, unplug the drive, startup, shutdown, re-plug the drive, and startup again. Hopefully, this will reset HAL back to normal (although this may be Kudzu at work on my FC - but it couldn't hurt).
And one last thing: Is the disk you're using formatted? Double-check it in another drive, if you can. As je_fro pointed out, Zips are notorious for failing due to full moons, bad burritos, or loneliness. I've had to re-prep about half my stock of Zips over the years.

pyavitz:
my zip(s) have always fallen under /dev/sda4
i've never seen one fall under /dev/hd*?
If you have a SCSI or USB Zip drive, then you'll see it as sdX4 (my dual-boot box has an external SCSI that I share with my Amigas). The parallel port version should show up as "pp0" or somesuch (never had one, so I don't know for sure). For the rest of us, it'll most likely be the internal ATA/IDE version, which pops up as hdX4, depending on where in the IDE map it's sitting (I have these installed in my other boxes for quick file transfers between PC/Amigas - I use flash drives for PC/PC).
Tip: Use the utility (Iomega Tools) to format the disks. For some reason, the format seems to "hold" longer. I'm guessing the extra time it takes for it to complete the format has something to do with it (writing extra info or verifying the tracks).

banzai "Open the fscking Zip disk, HAL..." kai