search
top

How To Read an IOMEGA ZIP 100 Drive on Ubuntu Linux 12.04

As with most things computer there are times when old media formats appear and a need to retrieve the data. One such occurrence happened recently when several ZIP  disks arrived. The IOMEGA ZIP  drives were parallel port connected SCSI drives that were popular back in the late 90’s early 2000’s. They were great for backups and had more capacity that floppy disks. They are before USB attached drives came into being. So the question is how do I read these drives?

Installation of IOMEGA

Installation with Ubuntu 9.10 and higher only require a single module to be loaded. Editing the /etc/module file and adding ppa is all that is required. This is the Parallel port driver. After editing /etc/modules reboot the system. Make sure to have the drive plugged in and powered on.

Once the system has rebooted we can check to see what was detected. We can run the following command.

$ sudo cat /proc/scsi/scsi

Here we see the IOMEGA drive.

IOMEGA zip100_2

Attached devices:

Host: scsi0 Channel: 00 Id: 00 Lun: 00
Vendor: ATA Model: ST2000DM001-1ER1 Rev: CC26
Type: Direct-Access ANSI SCSI revision: 05

Host: scsi1 Channel: 00 Id: 00 Lun: 00
Vendor: TSSTcorp Model: DVD+-RW TS-L633C Rev: DW40
Type: CD-ROM ANSI SCSI revision: 05

Host: scsi6 Channel: 00 Id: 06 Lun: 00
Vendor: IOMEGA Model: ZIP 100 Rev: K.0
Type: Direct-Access ANSI SCSI revision: 02

At this point all you need to do is insert a disk and Linux will auto-mount and you can now access the files.

IOMEGA zip100

 

24 Responses to “How To Read an IOMEGA ZIP 100 Drive on Ubuntu Linux 12.04”

  1. Edwin Barton says:

    Actually the IOMEGA Zip 100 drive came in a variety of interfaces. As you know there was a parallel port version (I used to own an Epson branded parallel port version that had a sort of greyish-beige case), and a SCSI version (both internal and external SCSI, I used to own one of the external SCSI (with a solid blue case, there were some external Zip 100’s that sold with a translucent blue case as well) ones which connected to a SCSI adapter card that you installed in the PC, it also could be daisy-chained with other SCSI devices by connecting them to the second 25 pin connector on the back of the drive), there was also an ATAPI version and an IDE version (ATAPI is not the same as IDE in this instance), I actually have 3 of the IDE ones still sitting in a box in my garage currently (none of which are suffering the dreaded “click of death” fortunately). The IDE version can even be connected to a USB2IDE adapter and functions great this way without the need to install any additional packages in Linux, or the need for any special software in Windows even. I haven’t yet tested it with a SATA2IDE adapter though to see if it works alright when connected to an internal SATA port. And there was actually a USB 1.1 version of the Zip 100 drive as well, though it was produced at about the time the Zip 250 was introduced as a successor to the Zip 100.

    • newlife007 says:

      You are correct, there were several varieties of the ZIP drives, besides the parallel version I have the internal ZIP 100 and in the past have used many other SCSI attached and there is also the ZIP 250, thanks for the history on the ZIP.

  2. arthur perkins says:

    Hi,

    I am trying to read a syquest syjet 1.5 external scsi drive that is connected to the parallel port. Will these instructions allow me to read this drive or are there different instructions that I can use to access the syquest drive?

    Thanks in advance for any help you can give me.

    • newlife007 says:

      I do not see why it wouldn’t work. Doesn’t hurt to try it.

    • Edwin Barton says:

      If you’re sure it’s a scsi drive and not a parallel port drive it will only work when connected to a scsi controller card. The 25 pin scsi connector may look the same as a parallel port connector but it does NOT support the same functionality. SCSI devices equipped with a 25 pin connector that looks like the 25 pin parallel port cannot simply be connected to the parallel port willy nilly. The pin configurations as well as the communication protocols used by the two ports are significantly different from one another to prevent them from working. Iomega sold a 25 pin ISA bus SCSI controller card specifically for use with their SCSI based devices. And while you may not be able to install an ISA bus card in today’s computers SCSI cards are still available to fit today’s computers and in addition to one of those you should only need to purchase a pin adapter to go from the D68/D50 pin external connector currently in use down to the D25 SCSI connector Iomega devices used. There are also USB to SCSI adapters available though they don’t seem to be very easy to locate (or very affordable either).

      • arthur perkins says:

        The Iomega drive I have is scsi but it came with a Iomega-designed cable to enable use of the scsi drive and the parallel port at the same time.

        Thanks,

  3. arthur perkins says:

    I tried the instructions and the syquest drive does not show up when I run the ‘cat /proc/scsi/scsi’ command.

    Is there anything I can try? The syquest drive was purchased as new from ebay and came still wrapped in plastic.

    Thanks,

  4. arthur perkins says:

    I am using v14.04 lts. I first tried to mount the syquest drive using those instructions first before searching the web and coming across your site.

    I’m going to try those instructions again and will let you know where I am running into problems which I will list below:

    I created the text file as instructed but when I type the following command: chmod +x paride’, I get the following error message: ‘chmod: cannot access ‘paride’, no such file or directory’. The text file paride is currently on the desktop.

    Should it be somewhere else or can the command be modified to point to file on the desktop?

    Thanks,

    • newlife007 says:

      when you are in the terminal prompt type cd ~/Desktop then type the command chmod +x paride after that you should be able to run the command while in the terminal.

  5. arthur perkins says:

    I was able to get to the desktop but when i type the command ‘chmod +x paride’ I get the same error message ‘chmod: cannot access ‘paride’, no such file or directory.

    The file is named paride.txt. I tried the command with and without the ‘.txt’ extension.

    Thanks,

  6. arthur perkins says:

    I renamed the file to paride.sh but am getting the same error message: ‘chmod: cannot access ‘paride.sh’, no such file or directory’.

    Thanks,

  7. arthur perkins says:

    Is there a command to list the contents of the desktop?

  8. arthur perkins says:

    I renamed the file paride.txt to paride.sh. Using the ls command, 3 files are listed:

    paride.sh
    paride.txt~
    unknown document

    The file paride.sh is the only document on the desktop. I tried the ‘chmod’ command again on both listed files with the same result.

    Is it possible to send the paride file to you to review and test?

    Thanks,

  9. newlife007 says:

    The paride.txt~ is a backup file created by your text editor. From what you are showing for the ls output the file is there. A screen shot or copy and paste of the whole terminal text. open a terminal session and type in the following commands. Press enter after each line.

    Open Terminal
    cd ~\Desktop
    ls
    chmod 755 paride.sh

  10. arthur perkins says:

    Hi,

    As requested, I have run the commands that you have asked me to run. The results of the commands as copied from a terminal session is pasted below:

    arthur@arthur-T5082:~/Desktop$ cd ~\Desktop
    bash: cd: ~Desktop: No such file or directory
    arthur@arthur-T5082:~/Desktop$ cd ~/Desktop
    arthur@arthur-T5082:~/Desktop$ ls
    Paride.sh Paride.txt~ Untitled Document~
    arthur@arthur-T5082:~/Desktop$ chmod 755 paride.sh
    chmod: cannot access ‘paride.sh’: No such file or directory
    arthur@arthur-T5082:~/Desktop$

    Please let me know what’s going on.

    Thanks,

    • newlife007 says:

      Found your issue. Linux is case sensitive. You named the file Paride.sh so when you type the command and the file is in lowercase it is correct with its error. Type chmod +x Paride.sh

  11. arthur perkins says:

    I ran the command successfully after picking up on the case-sensitivity comment you made, then ran the script. I got the following errors below:

    arthur@arthur-T5082:~/Desktop$ sudo ./Paride.sh
    : not found: 2: ./Paride.sh:
    : not found: 5: ./Paride.sh:
    not found.ATAL: Module paride
    : not found: 7: ./Paride.sh:
    : not found: 12: ./Paride.sh:
    Inserting the necessary modules…
    modprobe: ERROR: could not insert ‘pd’: No such device
    : not found: 16: ./Paride.sh:
    : not found: 19: ./Paride.sh:
    : not found: 29: ./Paride.sh:
    : not found: 31: ./Paride.sh:
    Running commandsmou…
    ./Paride.sh: 72: ./Paride.sh: Syntax error: end of file unexpected (expecting “then”)
    arthur@arthur-T5082:~/Desktop$

    Thanks for your help so far. We’re making progress slowly but surely.

    • newlife007 says:

      It is complaining about various errors in the script. Looks like it is pointing at various lines, the number by not found. Also looks like you have an open if statement since it is looking for then. The error about no such device means the syquest drive connected with a different device name. you can look at the output of the dmesg command and look for references to syquest and should have the information.

  12. arthur perkins says:

    Ok, I’ll play around with it and get back to you as soon as I have some results of my testing.

    Thanks,

  13. arthur perkins says:

    Hi,

    When I run the dmesg command, I get the following info: “paride: epat registered as protocol 0″.

    When I run the command ‘modprobe epat # Syquest Protocol from a terminal line I get no errors.

    When I run the command ‘modprobe pd # Syquest Driver from a terminal line I get the following error message below:

    ‘ERROR: could not insert ‘pd’: Operation not permitted’.

    Any blank or non-execcutable line is the cause of the ‘not found: 2: ./Paride.sh:
    ‘not found: 5: ./Paride.sh:

    errors. I got rid of them by deleting the blank lines.

    The line ‘not found.ATAL: Module paride’ I’m not sure where it is coming from but I am guessing that it’s because there is no module called Paride.

    When I type in just ‘dmesg’, I get a lot of info about the system. I’m pasting the results of scanning for ‘pd’ and ‘syquest’ below:

    ‘PD’
    [ 13.296218] systemd-udevd[322]: starting version 204
    [ 13.655352] ppa: Version 2.07 (for Linux 2.4.x)
    [ 13.702289] lp: driver loaded but no devices found
    [ 13.760479] ppdev: user-space parallel port driver
    [ 13.783234] parport_pc 00:03: reported by Plug and Play ACPI
    [ 13.783402] parport0: PC-style at 0x378, irq 7 [PCSPP,TRISTATE,EPP]
    [ 13.800888] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
    [ 13.814818] piix4_smbus 0000:00:14.0: SMBus Host Controller at 0x3010, revision 0
    [ 13.826047] lp0: using parport0 (interrupt-driven).
    [ 1017.365256] paride: epat registered as protocol 0
    [ 1017.384993] pd: pd version 1.05, major 45, cluster 64, nice 0
    [ 1017.522425] pda: Autoprobe failed
    [ 1017.522436] pd: no valid drive found
    [ 1282.714177] pd: pd version 1.05, major 45, cluster 64, nice 0
    [ 1282.847682] pda: Autoprobe failed
    [ 1282.847694] pd: no valid drive found
    [ 1636.201655] perf interrupt took too long (2504 > 2500), lowering kernel.perf_event_max_sample_rate to 50000
    [ 1701.308984] pd: pd version 1.05, major 45, cluster 64, nice 0
    [ 1701.444420] pda: Autoprobe failed
    [ 1701.444431] pd: no valid drive found
    [ 1751.773982] audit: type=1400 audit(1547667624.107:71): apparmor=”STATUS” operation=”profile_replace” profile=”unconfined” name=”/usr/lib/cups/backend/cups-pdf” pid=2831 comm=”apparmor_parser”
    [ 1751.774008] audit: type=1400 audit(1547667624.107:72): apparmor=”STATUS” operation=”profile_replace” profile=”unconfined” name=”/usr/sbin/cupsd” pid=2831 comm=”apparmor_parser”
    [ 1751.775218] audit: type=1400 audit(1547667624.107:73): apparmor=”STATUS” operation=”profile_replace” profile=”unconfined” name=”/usr/sbin/cupsd” pid=2831 comm=”apparmor_parser”
    [ 3455.005755] ath5k: ath5k_hw_get_isr: ISR: 0x00000080 IMR: 0x00000000
    [ 4535.005520] ath5k: ath5k_hw_get_isr: ISR: 0x00000400 IMR: 0x00000000
    [ 8135.005558] ath5k: ath5k_hw_get_isr: ISR: 0x00000080 IMR: 0x00000000
    [ 8735.005599] ath5k: ath5k_hw_get_isr: ISR: 0x00000080 IMR: 0x00000000
    [20257.304073] ath5k: ath5k_hw_get_isr: ISR: 0x00000001 IMR: 0x00000000
    [21575.005696] ath5k: ath5k_hw_get_isr: ISR: 0x00000080 IMR: 0x00000000
    [22775.005835] ath5k: ath5k_hw_get_isr: ISR: 0x00000400 IMR: 0x00000000
    [24575.424073] ath5k: ath5k_hw_get_isr: ISR: 0x00000001 IMR: 0x00000000
    [24786.750947] pd: pd version 1.05, major 45, cluster 64, nice 0
    [24786.883924] pda: Autoprobe failed
    [24786.883937] pd: no valid drive found
    [24818.739096] systemd-hostnamed[3222]: Warning: nss-myhostname is not installed. Changing the local hostname might make it unresolveable. Please install nss-myhostname!
    [24938.756067] ath5k: ath5k_hw_get_isr: ISR: 0x00000001 IMR: 0x00000000
    [26452.779632] pd: pd version 1.05, major 45, cluster 64, nice 0
    [26452.911351] pda: Autoprobe failed
    [26452.911362] pd: no valid drive found
    arthur@arthur-T5082:~/Desktop$ [ 1017.365256] paride: epat registered as protocol 0
    bash: [: missing `]’
    arthur@arthur-T5082:~/Desktop$ [ 1017.384993] pd: pd version 1.05, major 45, cluster 64, nice 0
    bash: [: missing `]’
    arthur@arthur-T5082:~/Desktop$ [ 1017.522425] pda: Autoprobe failed
    bash: [: missing `]’
    arthur@arthur-T5082:~/Desktop$ [ 1017.522436] pd: no valid drive found
    bash: [: missing `]’
    arthur@arthur-T5082:~/Desktop$ [ 1282.714177] pd: pd version 1.05, major 45, cluster 64, nice 0
    bash: [: missing `]’
    arthur@arthur-T5082:~/Desktop$ [ 1282.847682] pda: Autoprobe failed
    bash: [: missing `]’
    arthur@arthur-T5082:~/Desktop$ [ 1282.847694] pd: no valid drive found
    bash: [: missing `]’
    arthur@arthur-T5082:~/Desktop$ [ 1636.201655] perf interrupt took too long (2504 > 2500), lowering kernel.perf_event_max_sample_rate to 50000
    bash: syntax error near unexpected token `(‘
    arthur@arthur-T5082:~/Desktop$ [ 1701.308984] pd: pd version 1.05, major 45, cluster 64, nice 0
    bash: [: missing `]’
    arthur@arthur-T5082:~/Desktop$ [ 1701.444420] pda: Autoprobe failed
    bash: [: missing `]’
    arthur@arthur-T5082:~/Desktop$ [ 1701.444431] pd: no valid drive found
    bash: [: missing `]’
    arthur@arthur-T5082:~/Desktop$ [ 1751.773982] audit: type=1400 audit(1547667624.107:71): apparmor=”STATUS” operation=”profile_replace” profile=”unconfined” name=”/usr/lib/cups/backend/cups-pdf” pid=2831 comm=”apparmor_parser”
    bash: syntax error near unexpected token `(‘
    arthur@arthur-T5082:~/Desktop$ [ 1751.774008] audit: type=1400 audit(1547667624.107:72): apparmor=”STATUS” operation=”profile_replace” profile=”unconfined” name=”/usr/sbin/cupsd” pid=2831 comm=”apparmor_parser”
    bash: syntax error near unexpected token `(‘
    arthur@arthur-T5082:~/Desktop$ [ 1751.775218] audit: type=1400 audit(1547667624.107:73): apparmor=”STATUS” operation=”profile_replace” profile=”unconfined” name=”/usr/sbin/cupsd” pid=2831 comm=”apparmor_parser”
    bash: syntax error near unexpected token `(‘
    arthur@arthur-T5082:~/Desktop$ [ 3455.005755] ath5k: ath5k_hw_get_isr: ISR: 0x00000080 IMR: 0x00000000
    bash: [: missing `]’
    arthur@arthur-T5082:~/Desktop$ [ 4535.005520] ath5k: ath5k_hw_get_isr: ISR: 0x00000400 IMR: 0x00000000
    bash: [: missing `]’
    arthur@arthur-T5082:~/Desktop$ [ 8135.005558] ath5k: ath5k_hw_get_isr: ISR: 0x00000080 IMR: 0x00000000
    bash: [: missing `]’
    arthur@arthur-T5082:~/Desktop$ [ 8735.005599] ath5k: ath5k_hw_get_isr: ISR: 0x00000080 IMR: 0x00000000
    bash: [: missing `]’
    arthur@arthur-T5082:~/Desktop$ [20257.304073] ath5k: ath5k_hw_get_isr: ISR: 0x00000001 IMR: 0x00000000
    [20257.304073]: command not found
    arthur@arthur-T5082:~/Desktop$ [21575.005696] ath5k: ath5k_hw_get_isr: ISR: 0x00000080 IMR: 0x00000000
    [21575.005696]: command not found
    arthur@arthur-T5082:~/Desktop$ [22775.005835] ath5k: ath5k_hw_get_isr: ISR: 0x00000400 IMR: 0x00000000
    [22775.005835]: command not found
    arthur@arthur-T5082:~/Desktop$ [24575.424073] ath5k: ath5k_hw_get_isr: ISR: 0x00000001 IMR: 0x00000000
    [24575.424073]: command not found
    arthur@arthur-T5082:~/Desktop$ [24786.750947] pd: pd version 1.05, major 45, cluster 64, nice 0
    [24786.750947]: command not found
    arthur@arthur-T5082:~/Desktop$ [24786.883924] pda: Autoprobe failed
    [24786.883924]: command not found
    arthur@arthur-T5082:~/Desktop$ [24786.883937] pd: no valid drive found
    [24786.883937]: command not found
    arthur@arthur-T5082:~/Desktop$ [24818.739096] systemd-hostnamed[3222]: Warning: nss-myhostname is not installed. Changing the local hostname might make it unresolveable. Please install nss-myhostname!
    [24818.739096]: command not found
    arthur@arthur-T5082:~/Desktop$ [24938.756067] ath5k: ath5k_hw_get_isr: ISR: 0x00000001 IMR: 0x00000000
    [24938.756067]: command not found
    arthur@arthur-T5082:~/Desktop$ [26452.779632] pd: pd version 1.05, major 45, cluster 64, nice 0
    [26452.779632]: command not found
    arthur@arthur-T5082:~/Desktop$ [26452.911351] pda: Autoprobe failed
    [26452.911351]: command not found
    arthur@arthur-T5082:~/Desktop$ [26452.911362] pd: no valid drive found
    [26452.911362]: command not found
    arthur@arthur-T5082:~/Desktop$ “paride: epat registered as protocol 0”

    The scan for ‘syquest’ turned up nothing.

    As far as the if/then/fi issue, it looks like all of the if lines have a then and fi at the if condition.

    My next test was to comment out all of the conditional ‘if’ statements in the script, then add back each ‘if’ statement to see what happens.

    The results are below:

    arthur@arthur-T5082:~/Desktop$ sudo ./Paride.sh
    not found.ATAL: Module paride
    Inserting the necessary modules…
    modprobe: ERROR: could not insert ‘pd’: No such device
    Running commandsmou…
    mkdir: cannot create directory ‘/media/Syquest\r’: File exists
    mount: special device /dev/pda1 does not exist
    ls: cannot access /media/Syquest: No such file or directory
    arthur@arthur-T5082:~/Desktop$

    So far this is the results of my testing.

    Thanks,

  14. harry says:

    set the port to bi-directional not ecp,
    then it works fine

Trackbacks/Pingbacks

  1. Подключаем привод Iomega zip 100 | Уголок быдлокодера - […] Источники: раз, два. […]

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.

top