IDE ZIP100 Drive
OK, after some searching (while not the best search engine around, Startpage comes up a winner more often than not if there is anything relevant to be found) I've come up (almost) empty handed[0-1]. Everything else I've found so far for IOMEGA ZIP100 drives deals with the external drive (either USB or parallel port). I've not seen anything in dmesg or /var/log/messages that would indicate that the device is being detected by anything on boot aside from the BIOS. I'm not sure of the pin selector on the drive but it is cabled as the secondary master (the primary master being my hard drive, of course). I did try "mount_msdosfs /dev/ad1s4 /mnt/zip" (zip added by me after creating the appropriate directory in /mnt) but came up with "mount_msdosfs: /dev/adls4: No such file or directory" (there is a disk currently loaded). Does anyone else have any experience with these drives? Are there any docs I'm missing (aside from the FreeBSD Handbook, which is silent about this under-appreciated (and unfortunately over-priced) device[2])? [0]: http://www.freebsd.org/doc/en_US.ISO8859-1/articles/zip-drive/ [1]: http://docs.freebsd.org/cgi/getmsg.cgi?fetch=734560+0+archive/1997/freebsd-questions/19970518.freebsd-questions [2]: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/disks.html -- Yours In Christ, PIT Emails are not formal business letters, whatever businesses may want. signature.asc Description: OpenPGP digital signature
[SOLVED] Re: IDE ZIP100 Drive
On 02/23/10 11:42, Tim Judd wrote: > Could be due to that the zip disks have a partition defined. > ls /dev/afd0* > > file -s /dev/afd0 > That did it. I didn't know how to define the partition. Now to format it. -- Yours In Christ, PIT Emails are not formal business letters, whatever businesses may want. signature.asc Description: OpenPGP digital signature
Re: IDE ZIP100 Drive
On Tue, 23 Feb 2010 11:05:20 -0600, Programmer In Training wrote: > OK, upon a second reboot (for something unrelated), the device is > detected (but I think only because I had the disk in the drive at the > time). Now I'm having mount issues. First, it's entry in dmesg: > > afd0: 95MB at ata0-slave PIO0 That look okay. By the way, it shouldn't matter if there's actually a disk in the drive for the detection. The OS will try to identify the media, or report "no media" if there isn't a disk in the drive - but the drive will be present. > I'm issuing the following command with the following results: > > mount_msdosfs /dev/afd0 /mnt/zip > mount_msdosfs: /dev/afd0: Invalid argument For diagnostics, check the output of "fdisk afd0" to see if the MBR partition data can be retrieved. If you have an MS-DOS formatted media, I doubt that /dev/afd0 will be the correct device to access. Are there more /dev/afd0* devices present? Maybe accessing /dev/afd0s1 will work. It depends on the partitioning of the disk. Then, a command like "mount_msdosfs /dev/afd0s1 /mnt/zip" should be working correctly; consider using -noatime and useful masks (-m, -M) because MS-DOS file systems can't deal with file attributes properly. If you're planning to use the ZIP drive with modern OSes only - i. e. such understanding UFS file systems - then you could format the disk with UFS, with a slice containing the partition, or omiting the slice (dedicated)... just an additional idea. > I've tried afd1 through afd4, I just get > no such file or directory errors. Those devices are refering to a second, third, fourth and fifth ZIP drive, which obviously isn't present. > I'd like to use the zip drive to back up my private keys from GnuPG and > other important data. I wouldn't trust important data to a ZIP drive. I still have "hardware virus" in mind, and a fast search revealed this: "I like the fact that the old zip drives were vulnerable to the infamous "click of death". Leave it to Iomega to inadvertantly create what was essentially a hardware virus. We've lost two of our old zip drives in the office to "infected" zip disks. What are the odds of accidentally creating a device that can both damage itself and all other compatible devices it comes in contact with? Basically, it's a broken spring in the sliding aluminum part of the disc that would also damage any drive the disc was used in - those drives often times would end up damaging more discs - thereby spreading the problem. Damaged discs were usually totally unreadable without a little hardware hack that basically involved more or less taking them apart. Doesn't happen to the new drives, but the new discs can still break in the same way." http://www.consolecity.com/forum/archive/index.php/t-12717.html Are you sure your drive isn't affected? I've never owned a ZIP drive, so I can't speak from my own experiences. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: IDE ZIP100 Drive
On 2/23/10, Programmer In Training wrote: > On 02/22/10 14:32, Programmer In Training wrote: >> Second attempt to post this to the list. Please bear with me as I'm >> having issues with my posts to the list not always making it through. >> >> OK, after some searching I've come up (almost) empty handed[0-1]. >> Everything else I've found so far for IOMEGA ZIP100 drives deals with >> the external drive (either USB or parallel port). I've not seen anything >> in dmesg or /var/log/messages that would indicate that the device is >> being detected by anything on boot aside from the BIOS. I'm not sure of > > > OK, upon a second reboot (for something unrelated), the device is > detected (but I think only because I had the disk in the drive at the > time). Now I'm having mount issues. First, it's entry in dmesg: > > afd0: 95MB at ata0-slave PIO0 > > I'm issuing the following command with the following results: > > mount_msdosfs /dev/afd0 /mnt/zip > mount_msdosfs: /dev/afd0: Invalid argument Could be due to that the zip disks have a partition defined. ls /dev/afd0* file -s /dev/afd0 > The man page for mount and mount_msdosfs gives no clue on why that's an > invalid argument. When executed, the drive is accessed, then a moment > later it errors out as above. I've tried afd1 through afd4, I just get > no such file or directory errors. > > I'd like to use the zip drive to back up my private keys from GnuPG and > other important data. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: IDE ZIP100 Drive
On 02/22/10 14:32, Programmer In Training wrote: > Second attempt to post this to the list. Please bear with me as I'm > having issues with my posts to the list not always making it through. > > OK, after some searching I've come up (almost) empty handed[0-1]. > Everything else I've found so far for IOMEGA ZIP100 drives deals with > the external drive (either USB or parallel port). I've not seen anything > in dmesg or /var/log/messages that would indicate that the device is > being detected by anything on boot aside from the BIOS. I'm not sure of OK, upon a second reboot (for something unrelated), the device is detected (but I think only because I had the disk in the drive at the time). Now I'm having mount issues. First, it's entry in dmesg: afd0: 95MB at ata0-slave PIO0 I'm issuing the following command with the following results: mount_msdosfs /dev/afd0 /mnt/zip mount_msdosfs: /dev/afd0: Invalid argument The man page for mount and mount_msdosfs gives no clue on why that's an invalid argument. When executed, the drive is accessed, then a moment later it errors out as above. I've tried afd1 through afd4, I just get no such file or directory errors. I'd like to use the zip drive to back up my private keys from GnuPG and other important data. -- Yours In Christ, PIT Emails are not formal business letters, whatever businesses may want. signature.asc Description: OpenPGP digital signature
Re: IDE ZIP100 Drive
On 22.02.2010 22:32, Programmer In Training wrote: OK, after some searching I've come up (almost) empty handed[0-1]. Everything else I've found so far for IOMEGA ZIP100 drives deals with the external drive (either USB or parallel port). I've not seen anything in dmesg or /var/log/messages that would indicate that the device is being detected by anything on boot aside from the BIOS. I'm not sure of the pin selector on the drive but it is cabled as the secondary master (the primary master being my hard drive, of course). I did try "mount_msdosfs /dev/ad1s4 /mnt/zip" (zip added by me after creating the appropriate directory in /mnt) but came up with "mount_msdosfs: /dev/adls4: No such file or directory" (there is a disk currently loaded). Does anyone else have any experience with these drives? Are there any docs I'm missing (aside from the FreeBSD Handbook, which is silent about this under-appreciated (and unfortunately over-priced) device[2])? I posess one internal with pata interface. Works like a charm though 100Mb is not much. -- Sphinx of black quartz judge my vow. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
IDE ZIP100 Drive
Second attempt to post this to the list. Please bear with me as I'm having issues with my posts to the list not always making it through. OK, after some searching I've come up (almost) empty handed[0-1]. Everything else I've found so far for IOMEGA ZIP100 drives deals with the external drive (either USB or parallel port). I've not seen anything in dmesg or /var/log/messages that would indicate that the device is being detected by anything on boot aside from the BIOS. I'm not sure of the pin selector on the drive but it is cabled as the secondary master (the primary master being my hard drive, of course). I did try "mount_msdosfs /dev/ad1s4 /mnt/zip" (zip added by me after creating the appropriate directory in /mnt) but came up with "mount_msdosfs: /dev/adls4: No such file or directory" (there is a disk currently loaded). Does anyone else have any experience with these drives? Are there any docs I'm missing (aside from the FreeBSD Handbook, which is silent about this under-appreciated (and unfortunately over-priced) device[2])? [0]: http://www.freebsd.org/doc/en_US.ISO8859-1/articles/zip-drive/ [1]: http://docs.freebsd.org/cgi/getmsg.cgi?fetch=734560+0+archive/1997/freebsd-questions/19970518.freebsd-questions [2]: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/disks.html -- Yours In Christ, PIT Emails are not formal business letters, whatever businesses may want. signature.asc Description: OpenPGP digital signature
