Heh, you have one of those older "weird" Zip drives that did not conform to the EIDE specs.
 
I know because I have one too!  Hence the /dev/hda problem.
 
Newer drives I've tried work as everyone says they do here. As /dev/hda4. Those older drives were a little weird with the partitioning and access.
 
Anyways...
 
In spite of the fact that you are running all scsi, linux is trying to access the ZIP drive as a hard drive, which is why you see the error messages.
 
This happens because Linux is probing the IDE bus for devices and traditionally ID 0 /dev/hda is used for hard drives.
 
You could jumper the ZIP drive and make it a slave or move it to your secondary IDE chain, while disabling the first. Either will cure the problem.
 
-JMS
 
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of John and Marcie Alexander
Sent: Tuesday, December 19, 2000 10:52 AM
To: [EMAIL PROTECTED]
Subject: [newbie] atapi zip drive

I am running LM7.2 and I have an all scsi system (hd and cd-rw).  However, I am using an internal zip atapi drive plugged into the primary ide controller.
Under windows, this drive comes up as rive b:
Under linux, I keep getting "drive reports both xxxxx and 0 bytes" or something similiar (I don't have my notes right now)
I found that if I mount the zip under /hda (not /hda4 as some have suggested) then I can read and write to the drive, but I still get this error message popping up occasionally.
 
Any ideas?

Reply via email to