Date: Wed, 6 Feb 2002 15:13:17 -0600 From: Dan Nelson <dnelson@allantgroup.com> To: Joseph Lewis <sharktooth@innocent.com> Cc: questions@FreeBSD.ORG Subject: Re: Iomega Zip Drive is ad, not afd Message-ID: <20020206211316.GG1066@dan.emsphone.com> In-Reply-To: <20020206201252.5104.qmail@iname.com> References: <20020206201252.5104.qmail@iname.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In the last episode (Feb 07), Joseph Lewis said: > Mounting the ATA (Indeed, the BIOS boot up reports it as a removable > Hard Disk), works fine, the first time I boot into FreeBSD. When I > umount it, and then re-mount a zip disk, either the same one or a new > one, the drive's access light turns on, and I get some IO errors at > the console. I cannot umount it, nor get any response out of the > eject button (I guess a not-so-important observation on my part). I > have to shut down in order to get the zip disk back, or to use the > drive a second time. When I used the afd device, it functioned > perfectly. Is there a mount procedure or special step that is not > synonymous with regular floppies or hard disks? What kind of > /etc/fstab entry should I have? It currently reads: > > /dev/ad4s4 /mnt/zip msdos rw,noauto,noexec,nodev 0 0 > > dmesg out put reads: > ad4: 96MB <IOMEGA ZIP 100> [512/12/32] at ata-master PIO0 > > The error recieved on the second mounting of the device reads: > ad4s4c: hard error reading fsbn 1 (ad4s4 bn 1; cn 0 tn 0 sn 1) status=59 error=20 > ad4s4c: hard error reading fsbn 32 of 0-3 (ad4s4 bn 32; cn 0 tn 1 sn 0) status=51 error=00 I seem to remember a coworker having a similar problem with his ATA zip. I think he just replaced it with an ATAPI one. -- Dan Nelson dnelson@allantgroup.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020206211316.GG1066>