Re: IOMEGA ZIP-100 / ZIP-250 -- banging my head against the wall

[Sean Quinlan <smq@gmx.co.uk>]

* Phil Edwards <pedwards@disaster.jaj.com> (2001-08-18 01:00):
> On Sat, Aug 18, 2001 at 12:12:03AM +0100, Sean Quinlan wrote:
> > * Phil Edwards <pedwards@disaster.jaj.com> (2001-08-17 23:50):
> > mount -t vfat -o blocksize=1024 /dev/hdd4 /mnt/point
> 
> I tried this just now, still no joy.  I am seeing something with hdd4 that
> I don't see with any other device name, however, regardless of mount options:
> 
>     [~]# mount .... /dev/hdd4 /mnt/point
>     mount: wrong fs type, bad option, bad superblock on /dev/hdd4,
>            or too many mounted file systems
> ->         (could this be the IDE device where you in fact use
> ->         ide-scsi so that sr0 or sda or so is needed?)
>     [~]#
> 
> There's nothing special about this IDE controller, it's just an onboard
> controller from a plain Dell mobo.  I tried sr0 and sda, they failed
> (not surprisingly).

I had a look at the Zip-Drive mini howto, and it seems horribly out of
date (they're still talking about 2.0.x kernels), so it probably
won't be much help :)

After looking at the kernel config, it seems that IDE-floppy support
may be needed to access the zip250 drive.  Check your .config file for
CONFIG_BLK_DEV_IDEFLOPPY, if its compiled as a module, try "modprobe
ide-floppy" before the mount command.  If its built in (=y) then check
dmesg for any signs of it picking up your drive.
 
> > > That can't be the right conclusion -- I was running the same 2.2.19 kernel
> > > under RH7 that I'm running now under Debian, built from stock sources.
> > 
> > Are you using the exact same kernel (ie. copied the kernel from the
> > Redhat /boot to the Debian /boot), or are you using the same kernel
> > revision, but you went through the menuconfig or xconfig seperately.
> 
> No but no.  :-)  I kept the .config file resulting from the kernel build
> with me, to seed the configuration.  So it's not the same image file,
> but it is the same configuration.

OK, well that's good, although it means that its something to do with
the configuration in Debian :(  Hopefully its the module above, but if
not, then I should be able to get access to a Redhat 7.1 machine at
work, and I can have a look at their kernel config and such on Monday.

Cheers,
Sean

-- 
Sean Quinlan (smq@gmx.co.uk)