https://wiki.preterhuman.net/index.php?title=Jaz-drive_HOWTO_Linux&feed=atom&action=historyJaz-drive HOWTO Linux - Revision history2024-03-28T16:39:49ZRevision history for this page on the wikiMediaWiki 1.35.0https://wiki.preterhuman.net/index.php?title=Jaz-drive_HOWTO_Linux&diff=14576&oldid=prevNetfreak: Created page with "<pre> Jaz-drive HOWTO Herbert S. DaSilva v1.8, 12 January 2000 This HOWTO covers the configuration and use of the 1Gb and 2Gb Iomega Jaz drives under Linux. _____..."2020-07-29T22:48:22Z<p>Created page with "<pre> Jaz-drive HOWTO Herbert S. DaSilva v1.8, 12 January 2000 This HOWTO covers the configuration and use of the 1Gb and 2Gb Iomega Jaz drives under Linux. _____..."</p>
<p><b>New page</b></p><div><pre><br />
Jaz-drive HOWTO<br />
Herbert S. DaSilva<br />
v1.8, 12 January 2000<br />
<br />
This HOWTO covers the configuration and use of the 1Gb and 2Gb Iomega<br />
Jaz drives under Linux.<br />
______________________________________________________________________<br />
<br />
Table of Contents<br />
<br />
<br />
1. Introduction<br />
<br />
1.1 History<br />
1.2 Latest Version<br />
1.2.1 Version History<br />
1.3 Copyrights and Trademarks<br />
1.4 Acknowledgements and Thanks<br />
<br />
2. Jaz Hardware<br />
<br />
2.1 The Jaz Drives<br />
2.2 The Jaz "Disks"<br />
2.3 The Jaz Jet Host Adapter<br />
2.4 Other SCSI Host Adapters<br />
2.5 Kernel Driver Issues<br />
<br />
3. Identifying the Jaz Drive<br />
<br />
3.1 During Power-On Test<br />
3.2 During Boot<br />
3.3 Device Name<br />
<br />
4. Using a Jaz Disk<br />
<br />
4.1 DOS Formatted Disks<br />
4.2 Repartitioned DOS Jaz Disks<br />
4.3 Linux-Native Jaz Disks<br />
4.4 Checking Linux-Native Jaz Disks<br />
4.5 Using the fstab to Make Things Easier<br />
4.5.1 DOS Format Disks<br />
4.5.2 Linux Format Disks<br />
4.5.3 Automatic Mount at Boot Time<br />
4.6 The Jaz "tools" Disk<br />
<br />
5. Linux Utilities for Jaz Drives<br />
<br />
5.1 jaztool<br />
5.1.1 Ejecting a Cartridge<br />
5.1.2 Password Protection<br />
5.2 jaZip<br />
<br />
6. Booting from a Jaz Cartridge<br />
<br />
6.1 BIOS Issues<br />
6.2 Installing Linux on a Jaz Cartridge<br />
<br />
<br />
______________________________________________________________________<br />
<br />
1. Introduction<br />
<br />
The Iomega Jaz drive is a removable-media disk drive whose disks have<br />
a capacity of 1 or 2 Gigabytes. Unlike the Zip drive, the Jaz is only<br />
available as a SCSI device (internal or external), so a SCSI interface<br />
card and driver are required to use these drives.<br />
1.1. History<br />
<br />
Much of this HOWTO evolved from what was created by the previous<br />
author, Bob Willmot, (who can now be reached at bob@willmot.com<br />
<mailto:bob@willmot.com>), who maintained the HOWTO through version<br />
1.6, with contributions and information from the following people:<br />
<br />
<br />
o Grant Gunther, grant@torque.net<br />
<br />
o Tom Poindexter, tpoindex@nyx.net<br />
<br />
o Todd Woods, woods@cs.uiowa.edu<br />
<br />
o Richard B. Melrose, rbm@math.mit.edu<br />
<br />
o Phil Howard, phil@charon.milepost.com<br />
<br />
o Rick Niess, rniess@ocean.st.usm.edu<br />
<br />
1.2. Latest Version<br />
<br />
The latest version of this document can be found on my homepage<br />
http://www.ultranet.com/~hsd/HOWTO/<br />
<http://www.ultranet.com/~hsd/HOWTO/> where you will find the HTML<br />
version, suitable for browsing, a PostScript version, suitable for<br />
printing, and the SGML source. Other versions may be found in<br />
different formats at the LDP homepage http://www.linuxdoc.org/<br />
<http://www.linuxdoc.org/>.<br />
<br />
1.2.1. Version History<br />
<br />
v1.8, 12 January 2000<br />
<br />
o Fixed an incorrect HTTP link<br />
<br />
o Added clarification to jaztool code for 2Gb drives<br />
<br />
v1.7, 18 November 1999<br />
<br />
o Converted to SGML<br />
<br />
o Added info for 2Gb drives<br />
<br />
o Added fstab entry examples<br />
<br />
o General freshening up<br />
<br />
If you have any comments/suggestions/corrections please send them to:<br />
Herb DaSilva at Home <mailto:hsd@ma.ultranet.com> or (if you must have<br />
fast response) at Work <mailto:herb@aoainc.com>.<br />
<br />
1.3. Copyrights and Trademarks<br />
<br />
Copyright (C) 2000,1999 Herbert S. DaSilva<br />
<br />
This manual may be reproduced in whole or in part, without fee,<br />
subject to the following restrictions:<br />
<br />
<br />
o The copyright notice above and this permission notice must be<br />
preserved complete on all complete or partial copies<br />
<br />
o Any translation or derived work must be approved by the author in<br />
writing before distribution.<br />
<br />
o If you distribute this work in part, instructions for obtaining the<br />
complete version of this manual must be included, and a means for<br />
obtaining a complete version provided.<br />
<br />
o Small portions may be reproduced as illustrations for reviews or<br />
quotes in other works without this permission notice if proper<br />
citation is given.<br />
<br />
Exceptions to these rules may be granted for academic purposes: Write<br />
to the author and ask. These restrictions are here to protect us as<br />
authors, not to restrict you as learners and educators. All source<br />
code in this document is placed under the GNU General Public License,<br />
available via anonymous FTP from the GNU archive site<br />
<ftp://prep.ai.mit.edu/pub/GNU/COPYING>.<br />
<br />
1.4. Acknowledgements and Thanks<br />
<br />
Thanks to Stephan Burlot, stephan.burlot@edicom.ch, for pointing out<br />
the error (or lack of clarity) in the 2Gb patch to jaztool that was<br />
fixed in version 1.8.<br />
<br />
My thanks go out to Mark F. Komarinski for his "HOWTO-HOWTO" - This<br />
LDP author was helped Mark, you did your job. ;-)<br />
<br />
2. Jaz Hardware<br />
<br />
2.1. The Jaz Drives<br />
<br />
Jaz drives are SCSI devices and are available as an external drive<br />
with a 50-pin SCSI-2 self-terminating interface or an internal 3-1/2<br />
format drive with a 50-pin header interface.<br />
<br />
Both the internal and external devices are available in either 1 or 2<br />
Gigabyte capacity, so there are four different Jaz drives available.<br />
<br />
2.2. The Jaz "Disks"<br />
<br />
Jaz disks are a cartridge-style removable media containing a stack of<br />
three 3.5" platters. From here out, I'll be using the terms<br />
"cartridge" and "disk" interchangeably to mean the Jaz media.<br />
<br />
The 1Gb and 2Gb cartridges appear similar, but there is actually a<br />
subtle difference in their shape which prevents a 2Gb cartridge from<br />
being fully inserted into a 1Gb drive. Obviously, this means that you<br />
can't use a 2Gb cartridge in a 1Gb drive.<br />
<br />
The 2-Gb capacity Jaz drives can read, write, and format both 2-Gb and<br />
1-Gb Jaz cartridges.<br />
<br />
2.3. The Jaz Jet Host Adapter<br />
<br />
Iomega markets a SCSI host adapter under the name Jaz Jet. However,<br />
there are at least two different SCSI chipsets that are used. For<br />
this reason, the Jaz Jet isn't necessarily the best SCSI adapter to<br />
buy if you need one for your Jaz drive. You're better off getting a<br />
card that you know your Linux distribution will support (see the next<br />
section).<br />
<br />
<br />
One of the Jaz Jet cards is based on the Adaptec 7800 family of<br />
adapters. Linux 2.0 supports this adapter with the aic7xxx driver.<br />
This driver is built into most of the standard 2.x SCSI-capable<br />
kernels supplied with most Linux distributions.<br />
<br />
The other adapter is based on the Advanced Systems chipset. At boot<br />
time the board gives a message like:<br />
Jaz Jet PCI SCSI adapter Copyright Advanced Systems 1996<br />
<br />
Depending on your Linux distribution, you may need to build a custom<br />
kernel (with the CONFIG_SCSI_ADVANSYS variable set) to use this<br />
adapter.<br />
<br />
Personally, I don't like surprises, so if I were going to buy an<br />
adapter card, I would get a name-brand card with a 50-pin connector,<br />
so that I knew that what I was getting was supported.<br />
<br />
2.4. Other SCSI Host Adapters<br />
<br />
If you're using an Ultra-Wide SCSI card with a 68-pin connector,<br />
you'll need to get an adapter or another cable. The adapters do indeed<br />
work just fine with the Jaz drive, but can be rather pricey, so if<br />
you're buying a SCSI card primarily for the purpose of connecting the<br />
Jaz drive, you're better off picking up a card with a 50pin connector<br />
on it.<br />
<br />
If you're looking for a suggestion, I like the Adaptec AHA-2930U -<br />
it's cheap, it's fast, and the Jaz drive just plugs right in using the<br />
supplied cable with no adapter hassles. Unfortunately, support for<br />
this card is fairly new, so unless you have a fairly new Linux<br />
distribution (2.2.x kernel), it probably isn't supported. There are<br />
patches to the aic7xxx driver for 2.0.36 kernels that support this<br />
card, however. The AHA-2940U is an excellent choice as well, and it<br />
has been supported for a lot longer, it's just more expensive.<br />
<br />
2.5. Kernel Driver Issues<br />
<br />
As always, be sure that your Linux distribution supports a particular<br />
card EXPLICITLY before making a purchase. Many manufacturers, like<br />
Adaptec, have cards with numbers and letters similar to each other<br />
that are actually completely different chipsets, and therefore use<br />
completely different drivers.<br />
<br />
Configuring the Linux kernel for a SCSI card is the subject of a<br />
complete document in itself, so I won't go into that here.<br />
<br />
Info on rebuilding the kernel should be found in<br />
/usr/src/linux/README, or in /usr/src/linux/Documentation/ directory<br />
for the 2.x kernels. If these files don't exist, make sure that you<br />
have installed the kernel package source for your distribution.<br />
<br />
You can also check out Brian Ward's Kernel-HOWTO<br />
<http://metalab.unc.edu/mdw/HOWTO/Kernel-HOWTO.html><br />
<br />
3. Identifying the Jaz Drive<br />
<br />
3.1. During Power-On Test<br />
<br />
With a SCSI controller installed, when the machine is powered up or<br />
reset the SCSI controller will scan the SCSI bus looking for attached<br />
devices before booting the operating system.<br />
<br />
If your SCSI card is correctly installed, and your Jaz drive is<br />
attached and powered on, you should see the drive listed as something<br />
like "Iomega Jaz 1GB" or "Iomega Jaz 2GB" during this time.<br />
<br />
If the drive doesn't show up, there's no sense booting Linux. Power<br />
down the PC and Jaz drive, and check everything again. In particular,<br />
unplug the cables and make sure none of the the pins are bent, then<br />
replug them and ensure they are completely seated against the<br />
connector. If you have multiple SCSI devices, make sure they all have<br />
different ID numbers, and that the last device in the SCSI chain is<br />
terminated.<br />
When the drive shows up in the power-on test, you're half way home.<br />
<br />
3.2. During Boot<br />
<br />
When Linux boots the SCSI driver should display information about your<br />
SCSI adapter and what devices are attached to the SCSI bus.<br />
<br />
Boot messages will vary depending on your driver and adapter, and are<br />
logged to the /var/log/messages (or /var/adm/messages) file as well as<br />
appearing on the screen during boot. You can also 'replay' the<br />
messages since your last boot from the command prompt with the dmesg<br />
command.<br />
<br />
Here's the kernel booting output from a 2.0.36 kernel with an Adaptec<br />
2940 controller (using the aic7xxx driver):<br />
<br />
<br />
(scsi0) <Adaptec AHA-2940A Ultra SCSI host adapter> found at PCI 14/0<br />
(scsi0) Narrow Channel, SCSI ID=7, 3/255 SCBs<br />
(scsi0) Warning - detected auto-termination<br />
(scsi0) Please verify driver detected settings are correct.<br />
(scsi0) If not, then please properly set the device termination<br />
(scsi0) in the Adaptec SCSI BIOS by hitting CTRL-A when prompted<br />
(scsi0) during machine bootup.<br />
(scsi0) Cables present (Int-50 NO, Ext-50 YES)<br />
(scsi0) Downloading sequencer code... 419 instructions downloaded<br />
scsi0 : Adaptec AHA274x/284x/294x (EISA/VLB/PCI-Fast SCSI) 5.1.2/3.2.4<br />
<Adaptec AHA-2940A Ultra SCSI host adapter><br />
scsi : 1 host.<br />
Vendor: iomega Model: jaz 2GB Rev: E.17<br />
Type: Direct-Access ANSI SCSI revision: 02<br />
Detected scsi removable disk sda at scsi0, channel 0, id 4, lun 0<br />
scsi : detected 1 SCSI disks total.<br />
(scsi0:0:4:0) Synchronous at 10.0 Mbyte/sec, offset 15.<br />
sda : READ CAPACITY failed.<br />
sda : status = 1, message = 00, host = 0, driver = 28<br />
sda : extended sense code = 2<br />
sda : block size assumed to be 512 bytes, disk size 1GB.<br />
<br />
<br />
<br />
If something resembling these lines doesn't appear, then your kernel<br />
is probably not configured correctly (or you picked the wrong pre-<br />
built kernel).<br />
<br />
If the "scsi0 :" line does not appear, then you have not configured<br />
your driver correctly. Some drivers will give you a hint about what<br />
is wrong. If a drive name is not assigned, you probably forgot to<br />
include SCSI disk support when you built the kernel.<br />
<br />
Note the READ CAPACITY failed. Most SCSI drivers (like this one) will<br />
detect that the drive is a removable media type, and not get all<br />
flustered when it can't read the partition table. However, some SCSI<br />
cards aren't as graceful. If your PC hangs during boot, try booting<br />
with a cartridge in the drive.<br />
<br />
Check the README files in /usr/src/linux/drivers/scsi and the Kernel<br />
HOWTO for other debugging hints.<br />
<br />
3.3. Device Name<br />
<br />
In the log output in the previous section note the raw SCSI device<br />
name, which in this case is "sda", the full name being /dev/sda. If<br />
the Jaz drive is the only SCSI disk on your system, it will typically<br />
be /dev/sda. If your primary hard drive is SCSI, or you have a SCSI<br />
CD-ROM drive, it could be sdb, sdc, etc.<br />
Whatever the drive name is, you will need this name to access the<br />
drive, as explained in later sections.<br />
<br />
4. Using a Jaz Disk<br />
<br />
4.1. DOS Formatted Disks<br />
<br />
Jaz disks come pre-formatted from Iomega with a single partition using<br />
the DOS FAT16 file system. The single partition is usually the 4th<br />
disk partition (for Mac compatibility - the Mac requires data to be on<br />
the 4th partition, but the PC doesn't care which partition data is<br />
on).<br />
<br />
Linux is perfectly happy reading and writing a FAT16 file system, so<br />
you can use the disk as is. In order to use the disk, you need to<br />
mount it, so the first thing you need to do is create a mount point.<br />
For this document, we'll mount all our DOS Jaz drives under /dos_jaz,<br />
so let's create that mount point (you'll need to be root for most of<br />
this stuff). You'll only need to do this once:<br />
<br />
mkdir /dos_jaz<br />
<br />
In a previous section, I mentioned you'd need to remember the Jaz<br />
drive's raw SCSI device name. You need that now. If your drive is<br />
/dev/sda then all these examples will work for you. If not, you'll<br />
need to replace "sda" with the device ID of your Jaz drive. Since you<br />
need to issue these commands as root, you'll want to be sure you have<br />
the correct names.<br />
<br />
If you have a 2.0 kernel, or have added VFAT support, you can mount<br />
the Jaz disk this way, and have long filenames under FAT16:<br />
<br />
<br />
mount -t vfat /dev/sda4 /dos_jaz<br />
<br />
Note that although VFAT allows you to use long filenames, those<br />
filenames are still case in-sensitive, and although 'ls' lists<br />
permissions, you can't actually change permissions on any of the<br />
files.<br />
<br />
If the "vfat" format is not recognized by the mount command, then<br />
you'll use this command to mount the Jaz disk:<br />
<br />
mount -t msdos /dev/sda4 /dos_jaz<br />
<br />
Once you have issued either of the mount commands, files from the disk<br />
will appear under the /dos_jaz directory. While the disk is mounted,<br />
you will not be able to eject it.<br />
<br />
When you are done with the disk, you can unmount it with the command:<br />
<br />
umount /dos_jaz<br />
<br />
Once unmounted, you can press the button on the front of the drive to<br />
eject the cartridge.<br />
<br />
4.2. Repartitioned DOS Jaz Disks<br />
<br />
Since a Jaz disk is simply a disk, it can be repartitioned and<br />
reformatted like a fixed disk. If this is done, you need to know<br />
which partition numbers were used during repartitioning to be able to<br />
mount the disk.<br />
<br />
For instance, if the partition table was wiped, and a single new<br />
partition was created as the first partition, the two mount commands<br />
from the previous section would be:<br />
mount -t vfat /dev/sda1 /dos_jaz<br />
<br />
and<br />
<br />
mount -t msdos /dev/sda1 /dos_jaz<br />
<br />
4.3. Linux-Native Jaz Disks<br />
<br />
Linux-Native Jaz disks allow files to be stored with standard Unix<br />
permissions and case-sensitive filenames. The only drawback to Linux-<br />
Native disks is that they can no longer be used on DOS/Windows<br />
machines.<br />
<br />
A Jaz disk looks the same as a hard drive to Linux, so for those of<br />
you familiar with the Linux disk management tools, none of the<br />
following will be a surprise.<br />
<br />
<br />
If you want to erase a Jaz disk and make a Linux native file system on<br />
it, you use fdisk on the entire disk. Please be very careful using<br />
fdisk, especially if you have a SCSI hard drive - we wouldn't want to<br />
have any "accidents". :-) In particular, make sure you are operating<br />
on the correct device before making changes. In most cases, you'll<br />
use:<br />
<br />
fdisk /dev/sda<br />
<br />
and delete the existing partitions (with the d command). Then create<br />
a new partition with the n command, make it primary partition number 1<br />
(using all the cylinders), use w to write the partition table to disk,<br />
and quit with q.<br />
<br />
Once the partition has been created, format it with:<br />
<br />
mke2fs /dev/sda1<br />
<br />
(The 1 is the number that you gave this partition in fdisk). I prefer<br />
to create a separate mount point for Linux native Jaz disks, and<br />
you'll see why a little later when we talk about the fstab. So let's<br />
create that mount point now, and then mount the disk:<br />
<br />
mkdir /jaz<br />
<br />
mount -t ext2 /dev/sda1 /jaz<br />
<br />
As usual, when the Jaz disk is mounted, it cannot be ejected. When<br />
you're done using the Jaz disk, you unmount it with:<br />
<br />
umount /jaz<br />
<br />
Once unmounted, you can press the button on the front of the drive to<br />
eject the cartridge.<br />
<br />
4.4. Checking Linux-Native Jaz Disks<br />
<br />
Like your other disk drives, once a Linux Jaz disk has been mounted<br />
and unmounted a certain number of times, the system will mark the disk<br />
as "dirty". When this happens, you'll get a message like:<br />
<br />
Mounting unchecked filesystem, /dev/sda1. Recommend running e2fsck.<br />
<br />
Once you see this message, it's a good idea to go ahead and check the<br />
disk. The disk must be unmounted in order to check it.<br />
Unfortunately, you only get the "dirty" message when you mount it, so<br />
you can either check the disk when you're done using it, or unmount<br />
it, check it, then re-mount it. Use the following command to check<br />
the disk (assuming the partition to be checked is the first one):<br />
<br />
e2fsck /dev/sda1<br />
<br />
4.5. Using the fstab to Make Things Easier<br />
<br />
Up to now, we've had to be root to mount and unmount the Jaz disks,<br />
and we've had to type quite a bit to mount the Jaz disks. By adding a<br />
couple of entries to the file /etc/fstab, we can make using the Jaz<br />
drive much easier.<br />
<br />
4.5.1. DOS Format Disks<br />
<br />
If you've got preformatted DOS disks, and you've created the /dos_jaz<br />
mount point, you can add this line to the file /etc/fstab:<br />
<br />
/dev/sda4 /dos_jaz vfat defaults,user,nosuid,noauto 0 0<br />
<br />
With this line in the fstab, any user can mount and unmount a DOS-<br />
format Jaz cartridge with the following commands:<br />
<br />
mount /dos_jaz<br />
<br />
umount /dos_jaz<br />
<br />
This is because we have told Linux what the Jaz device ID and media<br />
type are in the fstab, plus we have given the user option to allow any<br />
user to mount and unmount the disk. Naturally, if your Jaz drive is<br />
other than sda, you'll need to change that, and this won't work for<br />
DOS cartridges that have been repartitioned without another entry in<br />
the fstab that uses a separate mount point (e.g. /dos_jaz2).<br />
<br />
4.5.2. Linux Format Disks<br />
<br />
If you've got Linux formatted disks, and you've created the /jaz mount<br />
point, you can add this line to the fstab:<br />
<br />
/dev/sda1 /jaz ext2 defaults,user,exec,nosuid,noauto 0 0<br />
<br />
With this line in the fstab, any user can mount and unmount a Linux-<br />
format Jaz cartridge with the following commands:<br />
<br />
mount /jaz<br />
<br />
umount /jaz<br />
<br />
Once again, we have told Linux what the Jaz device ID and media type<br />
are in the fstab, plus we have given the user option to allow any user<br />
to mount and unmount the disk. Some system administrators may not<br />
wish to have the exec option present, as there are some security risks<br />
with letting any user run an executable of unknown origin from the<br />
drive, but with the nosuid option present, these risks are minimal.<br />
<br />
4.5.3. Automatic Mount at Boot Time<br />
<br />
Both of the fstab examples above have the option noauto in them to<br />
prevent the disk from being automatically mounted at boot time. In<br />
general, this is a good idea because if there is no disk in the drive<br />
when the computer boots, or the drive is powered off, it can cause<br />
varying amounts of trouble, depending on which SCSI driver you are<br />
using.<br />
<br />
If you're sure you want to mount the jaz drive at boot time, simply<br />
remove the noauto option, and make sure the drive is on, and a<br />
cartridge is inserted before booting. Note that you can only have one<br />
fstab entry for jaz drive that will auto-mount, or you may encounter<br />
the same problems as if there was no cartridge in the drive.<br />
<br />
4.6. The Jaz "tools" Disk<br />
<br />
With some Jaz drives, the software to run the drive is supplied on a<br />
Jaz cartridge instead of on CD-ROM. The "problem" with these disks is<br />
that software-controlled write protection is enabled on the disk, so<br />
that the user can't wipe the disk until after the tools are installed<br />
at least once.<br />
<br />
There are several ways you can reclaim the Jaz tools disk:<br />
<br />
o Install the tools on a DOS/Windows computer.<br />
<br />
o Use a DOS/Windows computer with the Jaz tools already installed to<br />
remove the password protection.<br />
<br />
o Use one of the Linux Utilities mentioned in a later section to<br />
remove the password protection.<br />
<br />
If you have access to one of the password protection removal programs,<br />
all you need is the password that Iomega uses, and it is:<br />
<br />
APlaceForYourStuff<br />
<br />
Note that capitalization is important.<br />
<br />
5. Linux Utilities for Jaz Drives<br />
<br />
5.1. jaztool<br />
<br />
jaztool is a Linux utility written by Bob Willmot to support some of<br />
the Jaz drive's features (including software controlled ejection and<br />
write protection). I like jaztool because its commands can be<br />
embedded in alias commands and scripts. It's also easy to compile and<br />
install.<br />
<br />
The original source code for jaztool can be found at<br />
http://www.willmot.com/jaztool/ <http://www.willmot.com/jaztool/> and<br />
is also mirrored at my site at<br />
http://www.ultranet.com/~hsd/HOWTO/index.shtml#jaztool<br />
<http://www.ultranet.com/~hsd/HOWTO/index.shtml#jaztool><br />
<br />
Note that to use jaztool with a 2Gb Jaz drive, you must change ONE<br />
line of code. Change line 188 from this:<br />
<br />
return(!strncasecmp(id,"IOMEGA JAZ 1GB",15));<br />
<br />
to this:<br />
<br />
return(!strncasecmp(id,"IOMEGA JAZ",11));<br />
<br />
NOTE: There are two spaces between IOMEGA and JAZ in the previous two<br />
lines of code. SGML (or maybe just HTML) apparently removes the extra<br />
whitespace.<br />
<br />
After building jaztool and installing it, it must be suid root, or run<br />
as root, or it won't work.<br />
<br />
I use jaztool regularly, so if you have a question about it, I would<br />
be happy to try and answer it.<br />
<br />
5.1.1. Ejecting a Cartridge<br />
<br />
Use the following command to eject a cartridge:<br />
<br />
jaztool /dev/sda eject<br />
<br />
This might seem like a lot to type, but it's easy to make a slick<br />
alias like this:<br />
<br />
alias jazej 'umount /jaz; jaztool /dev/sda eject'<br />
<br />
5.1.2. Password Protection<br />
<br />
There are two password protection modes on a Jaz, and both are<br />
controlled through software. One is Write Protected and the other is<br />
Read/Write Protected. jaztool will allow you to unlock a Write<br />
Protected disk, but under Linux, a device that cannot be read cannot<br />
be mounted, so Read/Write Protected is not supported.<br />
<br />
If the cartridge is Write Protected (such as a Jaz Tools disk), use<br />
the following command to unlock it (the disk must not be mounted):<br />
<br />
jaztool /dev/sda rw<br />
<br />
jaztool prompts for a password, and if the password is correct, the<br />
disk is unlocked and ejected. This must be done to cause the SCSI<br />
driver to pick up the new mode when the cartridge is re-inserted.<br />
<br />
To make the disk Write Protected again, use the following command:<br />
<br />
jaztool /dev/sda ro<br />
<br />
jaztool again prompts for a password, and the disk is locked and<br />
ejected.<br />
<br />
Note that jaztool doesn't support the "Unprotect until Eject" feature<br />
found in the Windows world. If you remove the password protection, it<br />
is removed until you put it back on.<br />
<br />
5.2. jaZip<br />
<br />
If you'd prefer a nice, slick, graphical user interface to control<br />
your Jaz (and Zip!) drive, there's the jaZip tool. Check it out at:<br />
http://www.scripps.edu/~jsmith/jazip/<br />
<http://www.scripps.edu/~jsmith/jazip/><br />
<br />
I haven't used jaZip myself, so please contact the author directly<br />
with questions on jaZip. Contact information is on the website listed<br />
above.<br />
<br />
6. Booting from a Jaz Cartridge<br />
<br />
6.1. BIOS Issues<br />
<br />
If the Jaz drive co-exists with other SCSI harddrives, most BIOSes<br />
will want to boot the disk that has the lowest SCSI Id. The Jaz drive<br />
can be set to SCSI Ids 0-6, and typically come out of the box set to<br />
SCSI Id 5. Some BIOSes detect and skip removable devices like the<br />
Jaz. If your BIOS will boot from a Jaz, you can set your main SCSI<br />
harddrive to SCSI Id 1, then you can change the Jaz from SCSI Id 5 to<br />
0 when you want to boot from the Jaz.<br />
<br />
More typically, the Jaz drive co-exists with an IDE harddrive. Nearly<br />
every BIOS will want to boot the first IDE harddrive. Some BIOSes<br />
will allow you change a setting in the BIOS setup to boot from a SCSI<br />
device first. Others may require you to disable the IDE drives in the<br />
BIOS setup. Still others may require detaching the IDE drives<br />
physically or disabling the IDE interface.<br />
<br />
<br />
6.2. Installing Linux on a Jaz Cartridge<br />
<br />
Although running Linux from a Jaz cartridge is much slower than<br />
running from a harddrive, the Jaz drive makes an excellent ERD<br />
(Emergency Repair Disk). It's also fun to be able to just pop in some<br />
new Linux system or to try Linux on someone else's Jaz-equipped<br />
machine.<br />
<br />
By far the easiest way to install Linux on the Jaz cartridge is simply<br />
to follow the install procedure for your favorite distribution with<br />
the Jaz drive being the only drive on the system. I've done this with<br />
RedHat 5.2, and it works perfectly. If you're not completely<br />
comfortable with doing weird, wild stuff with LILO, it's the only way<br />
to go.<br />
<br />
If you want to do an "install" from your running system, you can often<br />
succeed in "building" a bootable system on a Jaz cartridge.<br />
<br />
<br />
o Partition the drive and make the filesystems. You probably need to<br />
have a swap partition, too, but if you have lots of RAM then maybe<br />
not. Mount the new root as /jaz and any additional partitions<br />
within that directory as appropriate.<br />
<br />
o Copy all the files into place. Be sure all the /dev files are<br />
copied. Be sure all permissions, ownership and group ids are<br />
retained.<br />
<br />
o Modify the files on the Jaz cartridge to suit the circumstances of<br />
booting from it. In particular be sure to change /jaz/etc/fstab to<br />
mount the Jaz cartridge partition(s) as appropriate. Also change<br />
/jaz/etc/lilo.conf to match as well.<br />
<br />
o There are two alternatives for installing the LILO boot loader:<br />
<br />
o Make a kernel image floppy and use rdev to make it mount the Jaz<br />
cartridge as root. Boot from the floppy when ready the first time<br />
then run LILO to make the Jaz MBR bootable.<br />
<br />
o You can run LILO from your non-Jaz root running system to install<br />
the bootable MBR on the Jaz cartridge. For more information on<br />
this option, check out Alessandro Rubini's LILO mini-HOWTO<br />
<http://metalab.unc.edu/mdw/HOWTO/mini/LILO.html><br />
</pre><br />
<br />
[[Category:How-To]]</div>Netfreak