Seagate/Irwin Minicartridge (mc) Floppy Tape Driver v4.0.0s for SCO Open Server Release 5.0.0 and 5.0.2 =========================================================== There are two files used install the driver. mc400s_s.txt: (this file) contains a procedure to install a minicartridge tape driver on an SCO Open Server Release 5 system. mc400s_s.Z: (a separate file) contains the corresponding tape driver and supporting utilities. Contents -------- History Controller Support Drive Support Cartridge Support Creating an Installation Floppy Diskette Using custom(ADM) to Install the Minicartridge Driver Update Using '/etc/mkdev mc' to Configure the Minicartridge Driver Update Rebooting After Minicartridge Driver Installation Creating an Emergency Boot/Root Floppy In the Event of a System Crash Using custom(ADM) to Remove the Minicartridge Driver Update The "mcart" Utility No-rewind Device: /dev/nrctmini (For Advanced Users) Notes Alternate Tape Controllers Error Messages Files History ------- v2.x.x -- Irwin only support v3.0.0 -- Added Irwin Filemark/End-of-data support v3.1.0 -- Added Divergent track pattern and read-after-write verify v3.2.0 -- Added Conner SLC drive support but only for Irwin AccuTrak (not QIC) cartridges. v3.3.0 -- Added AIX-PS2 Irwin read only support. v4.0.0 -- Added Conner/Archive QIC support. Version 4.0.0a changes (relative to 3.3.0): o Conner/Archive QIC support added (including formatting). This includes the Hornet, Super Hornet, SLC, and Roadrunner. o Two choices for QIC write management: - SCO Xenix/Unix ft driver compatible (no filemark support), or - NT Posix compatible (filemarks allowed). o Starting of /etc/mcdaemon is no longer a requirement unless read-after-write byte-for-byte verification is used. o Read-after-write verify is NOT functional for QIC formats (if enabled, a console message is printed on first write to QIC tape after open()). o Alternate controller port/irq/dma is configured in "space.c". o The direct access device interface, used by previous versions, is no longer supported. However, tapes created by previous versions, can still be read and written. Version 4.0.0b: o During verification of the claim "compatibility with NT driver", it was discovered that ECC, for QIC tapes, was encoded for the all sectors of all segments rather than excluding any bad (mapped out) sectors. 4.0.0b fixes this. Note: 4.0.0b will report "ECC verification error" when reading a tape created by 4.0.0a and a segment with excluded sectors is read. o Fixed write mgmt_qic_xenix to mgmt_qic_ntmark conversion error. Procedure for replication on v4.0.0a: # mcart mgmt_qic_xenix (default after boot) # tar cfv /dev/rctmini . # mcart mgmt_qic_ntmark # tar cfv /dev/rctmini . tar: write error 4.0.0b fixes this. o Support has been restricted to only Irwin, Archive, Conner, and IBM tape drives. Other drives report "Drive not found" on system initialization. Version 4.0.0c: o Added ioctl support for the following (from sys/tape.h) MT_STATUS -- read tape status MT_RESET -- reset tape hardware MT_RETEN -- retention tape MT_REWIND -- rewind tape MT_ERASE -- erase tape MT_AMOUNT -- report on amount of data xfered MT_RFM -- read n filemarks MT_WFM -- write filemark MT_FORMAT -- format a tape MT_EOD -- position at EOD MT_REPORT -- report device type o Included the Rc (run-command) file. This file, which was required by v3.x.x, is obsolete for v4.x.x. Its purpose is to start /etc/mcdaemon at system startup. /etc/mcdaemon now need only be started if the byte-for-byte read-after-write data verification feature (for AccuTrak) is to be used. (/etc/mcdaemon can also be started manually.) Version 4.0.0e: o Renamed /etc/conf/pack.d/mc/Rc to /etc/conf/pack.d/rc to prevent "link kit not installed" errors. o Modified mc_link_most(), mc_link_least(), mc_move_most(), mc_move_least() to prevent kernel PANIC. Version 4.0.0n: o Created custom installable version of driver (see install procedure below) o Modified read ahead code to ignore read data errors on close. This prevents incorrect "ECC verification error" on close. o Changed driver reported error on end-of-medium on writes from "Error 0" to "Tape full". o For tape management schemes which support filemarks, added automatic skip past filemark on open and write filemark if data written on close. o Changed QIC write error recovery to decrement end-of-medium rather than end-of-data. This fixes incorrect reporting of "Not at beginning-of-tape or end-of-data" when data is being displaced by write error recovery. o Added 10 sector write error limit. Version 4.0.0o: o Fixed cause of system corruption and/or process hang during close after a write error. o After a write error, subsequent write attempts will now produce the message "NOTICE: mc: Write error 107 on tape unit 0: Write error limit reached" until the cartridge is reinserted or replaced. o Fixed incorrect reporting of "Error 0" rather than "ECC verification error" on read ECC verification error. o Added 'mkdev mc' script Version 4.0.0p: o Added Device Query Interface (DQI) support. This allows Backup Manager to find "Minicartridge Floppy Tape Drive 0" as a backup device. o Added support for QIC 1000 foot cartridges. o Fixed "System hang during kernel initialization (at boot)" when certain SMC controllers are present (e.g, 37C932). The hang is caused by a failure to exit SMC configuration mode when, after entering, the part id is not recognized. o Added optional "Retension tape on first write after open". This feature is configured by mc_reten_write in space.c Version 4.0.0q: o Bug fix for position maintenance which caused the message "Not at beginning-of-tape or end-of-data" when appending Irwin or mgmt_qic_ntmark tapes using the no-rewind device. o Bug fix for inaccessibility of second tape backup when 'mcart rfm' is used to skip the first backup on Irwin or mgmt_qic_ntmark tapes accessed via the no-rewind device. o Changed ssoId strings in 'mkdev mc'. Version 4.0.0s: o Modified 'mkdev mc' script on to prevent the following error on Open Server v5.0.2: "/usr/lib/mkdev/mc: Error: /var/opt/K/SCO/mcDriver/4.0.0q/etc/conf/pack.d/space.c: Not found" o Changed Conner references to Seagate o Increased FDC fifo threshold from 4 to 11 to reduce DMA overruns. o On the first tape access, previous driver versions cause a tape application process to hang when the interrupt (IRQ) is incorrectly configured. This version exits and reports "92: Interrupt timeout". o Previous versions report "Block 0 medium defect" when the DMA channel is incorrectly configured. This version reports "17: DMA overrun". o Modified to prevent 'kernel panic' when used with alternate tape settings of DMA 2 and and an IRQ other than 6. Controller Support ------------------ In addition to the system floppy controller, the minicartridge (mc) driver v4.0.0 supports the following alternate floppy tape controllers: Seagate CTC-2Mb 2-Mbit (ISA) Conner CTC-2Mb 2-Mbit (ISA) Maynard 4100M 1-Mbit (ISA) Irwin 4100, 4100A, 4100C 1-Mbit (ISA) Irwin 4100MC 1-Mbit (MCA) Drive Support ------------- The minicartridge (mc) driver v4.0.0 supports the following floppy interface floppy tape drives: Seagate CTM420 (QIC-80, 8mm) Seagate CTT800 (QIC-80, 8mm, TR1) Seagate CTM700 (QIC-3010, 8mm) Seagate CTM1360 (QIC-3020, 8mm) Seagate CTT3200 (QIC-3020, 8mm, TR3) Seagate TapeStor 420 (QIC-80, 8mm) Seagate TapeStor 800 (QIC-80, 8mm, TR1) Seagate TapeStor 700/850 (QIC-3010, 8mm) Seagate TapeStor 1360/1700 (QIC-3020, 8mm) Seagate TapeStor 3200 (QIC-3020, 8mm, TR3) Conner 11250N/51250N (QIC-80) Conner CTM420 (QIC-80, 8mm) Conner CTT800 (QIC-80, 8mm, TR1) Conner CTM700 (QIC-3010, 8mm) Conner CTM1360 (QIC-3020, 8mm) Conner CTT3200 (QIC-3020, 8mm, TR3) Conner TapeStor 420 (QIC-80, 8mm) Conner TapeStor 800 (QIC-80, 8mm, TR1) Conner TapeStor 700/850 (QIC-3010, 8mm) Conner TapeStor 1360/1700 (QIC-3020, 8mm) Conner TapeStor 3200 (QIC-3020, 8mm, TR3) Archive Hornet 5540 (QIC-40) Archive Hornet 5580 (QIC-80) Archive SuperHornet 11250Q(1"), 31250Q(3.5"), 51250Q(5.25") (QIC-80) IBM Internal Tape Backup Unit (Similar to Irwin 285) IBM DualStor 250 Internal Tape Backup Unit (QIC-80) IBM DualStor 450 Internal Tape Backup Unit (QIC-80, 8mm) IBM DualStor 800 Internal Tape Backup Unit (QIC-80, 8mm, TR1) Irwin 110, 310, 410 (10 MB servo 0.15" DC1000) Irwin 120, 220, 320, 420, 720, 2020 (20/30 MB servo DC2080/DC2120) Irwin 125, 225, 325, 425, 725 (20 MB servo 0.15" DC1000) Irwin 145, 245, 345, 445, 745, 2040, A120 (40/60 MB servo DC2080/DC2120) Irwin 165, 265, 465, 765 (64 MB servo DC2080) Irwin 285, 485, 785, 2080, 287, 487, 787, 2120, A250 (80/120 MB servo DC2080/DC2120) Cartridge Support ----------------- The minicartridge (mc) driver v4.0.0 supports the following tape cartridges: mcart Capa- Format city Burst FRPI Tk*Blk Data+ECC Wide*Len Cartridge I10 10MB Irwin 6400 8*158 8+0 0.15"*185' DC1000 I20 20MB Irwin 6400 14*85 16+2 1/4"*205' DC2080 I20XL 30MB Irwin 6400 14*128 16+2 1/4"*307' DC2120 I25 20MB Irwin 10000 12*110 16+2 0.15"*185' DC1000 I45 40MB Irwin 10000 20*124 16+2 1/4"*205' DC2080 I45XL 60MB Irwin 10000 20*186 16+2 1/4"*307' DC2120 I65 64MB Irwin 13200 24*164 16+2 1/4"*205' DC2080 I85 80MB Irwin 11600 32*86 29+3 1/4"*205' DC2080 I85XL 120MB Irwin 11600 32*130 29+3 1/4"*307' DC2120 Q40 40MB QIC 10000 20*68 29+3 1/4"*205' DC2080 Q40XL 60MB QIC 10000 20*102 29+3 1/4"*307' DC2120 Q40PL 210MB QIC 10000 20*365 29+3 1/4"*1100' QDE2430 Q80 80MB QIC 14700 28*100 29+3 1/4"*205' DC2080 Q80XL 120MB QIC 14700 28*150 29+3 1/4"*307' DC2120 Q80 170MB QIC 14700 28*207 29+3 1/4"*425' DC2120XL or 400MB QIC 14700 28*~487 29+3 1/4"*1000' DC2120EX Q80PL 440MB QIC 14700 28*537 29+3 1/4"*1100' QDE2430 Q80W 220MB QIC 14700 36*~204 29+3 8mm *420' QW5122XLF or 400MB QIC 14700 36*~365 29+3 8mm *750' TR1 or 500MB QIC 14700 36*~487 29+3 8mm *1000' TR1EX Q3010 250MB QIC 22125 40*~215 29+3 1/4"*295' DC2500 or 340MB QIC 22125 40*~292 29+3 1/4"*400' MC3000XL Q3010W 430MB QIC 22125 50*~292 29+3 8mm *400' QW3010XLF or 800MB QIC 22125 50*~547 29+3 8mm *750' TR2 Q3020 500MB QIC 44250 40*~422 29+3 1/4"*295' DC2500 or 675MB QIC 44250 40*~572 29+3 1/4"*400' MC3000XL or 1600MB QIC 44250 40*~1431 29+3 1/4"*1000' MC3020EX Q3020W 850MB QIC 44250 50*~572 29+3 8mm *400' QW3020XLF or 1600MB QIC 44250 50*~1073 29+3 8mm *750' TR3 Note: ~ means approximate (Flexible format) Creating an Installation Floppy Diskette ---------------------------------------- Installation of the driver is accomplished by transferring the data image, contained in mc400s_s.Z, to an installation floppy diskette. 'custom' is then used to install the driver from floppy. The installation floppy diskette is a 3-1/2 inch, 135 tracks per inch, double sided, 18 sector per track (1.44MB) format. uncompress mc400s_s.Z - uncompress 'mc400s_s.Z' and convert it to a file named 'mc400s_s' . format /dev/rfd0135ds18 - format a 1.44 MB 3-1/2" floppy diskette. cp mc400s_s /dev/rfd0135ds18 - Copy the image file to the floppy. An installation floppy diskette is now prepared for use by 'custom'. You may want to write protect the floppy. Using custom(ADM) to Install the Minicartridge Driver Update ------------------------------------------------------------ To install the minicartridge driver update from an installation floppy diskette, and relink the kernel, follow these steps: Insert the installation floppy diskette in the drive. Double click the Software Manager icon or type /etc/custom From the menu bar, select: Software -> Install New... From the dialogue: "Begin installation on " "What host (machine) name do you want to install from?", select: From -> Continue From the dialogue: "Select media" "Insert media and select media device.", select: Floppy Disk Drive 0 -> Continue From the dialogue: "Install preference on " installing: "Seagate/Irwin Minicartridge Floppy Tape Driver (ver 4.0.0s)" "Do you want a FULL or PARTIAL installation?", select: Full At this point, custom - displays the dialogue: "Installation Progress on ", - installs the minicartridge driver files, and - relinks the kernel. From the dialogue: "Information" "During this installation, the kernel was relinked. You must reboot" "your system to make this kernel effective.", select: OK From the dialogue: "Message" "Installation complete", select: OK From the menu bar, select: Host -> Exit Remove the installation floppy diskette from the drive. The Minicartridge Driver update is now installed, linked in the kernel, and configured for default settings. Normally, at this point, go to the section "Rebooting After Minicartridge Driver Installation" below. If you are using an alternate tape controller, such as the Seagate CTC-2Mb or those listed in the "Controller Support" section above, and it has been jumpered for other than the default settings: Port 370 (hex), IRQ 6, DMA 2, then go to the section "Using '/etc/mkdev mc' to Configure the Minicartridge Driver Update" below. If your system has (a) an Adaptec 1542c with floppy drives attached, and (b) an alternate tape controller (such as those listed in the "Controller Support" section above), with the DMA channel set to 2 then, the DMA settings need to be changed. The new settings should be either DMA 1 or DMA 3. Both the alternate controller's DMA jumpers (or switches) and the driver's "Alternate controller DMA" parameter must be altered. See both sections "Alternate Tape Controllers" and "Using '/etc/mkdev mc' to Configure the Minicartridge Driver Update" below. Using '/etc/mkdev mc' to Configure the Minicartridge Driver Update ------------------------------------------------------------------ /etc/mkdev runs device configuration scripts kept in the directory /usr/lib/mkdev/. The script /usr/lib/mkdev/mc installs or removes the Minicartridge Driver from the system configuration and rebuilds the kernel. In addition, certain Minicartridge driver parameters, such as Alternate controller Port, IRQ, and DMA, can be adjusted. There is also a means by which this driver can be named as the default device used by the /usr/bin/tape program. The procedure to install, or reinstall the Minicartridge Driver in the system configuration is: Start '/etc/mkdev mc' from either the desktop or a Unix root user prompt. To start '/etc/mkdev mc' from the desktop: From the desktop, double click "System Administration". From "System Administration", double click "Hardware/Kernel Manager". In the "Hardware/Kernel Manager", select "mc" in the "Drivers" list box, then click "Configure Drivers". To start '/etc/mkdev mc' from a Unix root user prompt: At the root prompt, enter '/etc/mkdev mc' (or /usr/lib/mkdev/mc). The mkdev mc menu appears: Seagate/Irwin Minicartridge Floppy Tape Driver Installation 1. Install or reinstall tape driver in system configuration 2. Remove tape driver from system configuration 3. Make this the default tape driver Select an option or enter q to quit Enter '1'. The driver configuration menu appears: Seagate/Irwin Minicartridge Floppy Tape Driver Configuration 1. Display parameters 2. Edit proposed parameter values 3. Set all proposed parameter values to default values 4. Configure tape driver with proposed parameter values Select an option, or 'q' to quit, or to continue installation: Normally this menu can be skipped with . (If skipping go to -- Relinking the Kernel -- below.) The menu must be used, however, if you are using an alternate tape controller configured for other than the default settings: Port 370 (hex) IRQ 6 DMA 2 Note: If your system has (a) an Adaptec 1542c with floppy drives attached, and (b) an alternate tape controller (such as those listed in the "Controller Support" section above), with the DMA channel set to 2 then, the DMA settings need to be changed. The new settings should be either DMA 1 or DMA 3. Both the alternate controller's DMA jumpers (or switches) and the driver's "Alternate controller DMA" parameter must be altered. See the section "Alternate Tape Controllers" below. For example, to change the DMA channel from the default of 2 to 1, the Configuration menu is used to - Edit the "Proposed" DMA channel parameter, and - Make "Proposed" values "Current" by configuring the driver To perform these steps start by entering 2 (for: 2. Edit proposed parameter values) and you will see: Minicartridge Driver Parameter Current Proposed Default ------------------------------ ------- -------- ------- 1. Alternate controller I/O port 0x370 0x370 0x370 2. Alternate controller IRQ 6 6 6 3. Alternate controller DMA channel 2 2 2 At boot time, the driver scans for tape drives. First an alternate controller is scanned and then the system controller. A zero for "Alternate controller I/O port", disables the alternate scan. Enter parameter to edit or for previous menu: 3 Entering 3 selects the DMA channel parameter. Enter decimal value for DMA channel, or for existing value: 1 Entering 1 sets the proposed DMA channel to 1. Minicartridge Driver Parameter Current Proposed Default ------------------------------ ------- -------- ------- 1. Alternate controller I/O port 0x370 0x370 0x370 2. Alternate controller IRQ 6 6 6 3. Alternate controller DMA channel 2 1 2 At boot time, the driver scans for tape drives. First an alternate controller is scanned and then the system controller. A zero for "Alternate controller I/O port", disables the alternate scan. Enter parameter to edit or for previous menu: Entering returns to the configuration menu. Seagate/Irwin Minicartridge Floppy Tape Driver Configuration 1. Display parameters 2. Edit proposed parameter values 3. Set all proposed parameter values to default values 4. Configure tape driver with proposed parameter values Select an option, or 'q' to quit, or to continue installation: 4 Entering 4 reconfigures the driver and makes the "Proposed" values "Current". Minicartridge Driver Parameter Current Proposed Default ------------------------------ ------- -------- ------- 1. Alternate controller I/O port 0x370 0x370 0x370 2. Alternate controller IRQ 6 6 6 3. Alternate controller DMA channel 1 1 2 At boot time, the driver scans for tape drives. First an alternate controller is scanned and then the system controller. A zero for "Alternate controller I/O port", disables the alternate scan. Seagate/Irwin Minicartridge Floppy Tape Driver Configuration 1. Display parameters 2. Edit proposed parameter values 3. Set all proposed parameter values to default values 4. Configure tape driver with proposed parameter values Select an option, or 'q' to quit, or to continue installation: At this point DMA channel 1 is "Current". Enter to continue installation. -- Relinking the Kernel -- If you see the message: Another tape drive is currently linked to the default device /dev/xctmini. Do you wish to remove this link and have the Seagate/Irwin Minicartridge Floppy Tape Drive linked to the default devices? (y/n) Answer 'y'. You will then see: The following special devices have been created: /dev/rmc0 /dev/nrmc0 Press to Continue. Press . If you see the message: Another Tape Drive is currently listed as the default in /etc/default/tape. Do you wish to change this to the current Seagate/Irwin Minicartridge Floppy Tape Drive? (y/n) Answer 'y'. You will then see: Default special devices have been created with the following links: /dev/rctmini linked to /dev/rmc0 /dev/nrctmini linked to /dev/nrmc0 /dev/xctmini linked to /dev/nrmc0 In /etc/default/boot: No current boot string. -or- Current boot string is Enter new string, "rm" to remove string, or enter 'q' to leave current string as is: Answer 'q'. Note: See boot(HW) for more about the DEFBOOTSTR kept in /etc/default/boot. Then you will see: Updating system configuration ... System files have been successfully updated. You must create a new kernel to effect the driver change you specified. Do you wish to create a new kernel now? (y/n) Answer 'y'. The next message is: The UNIX Operating System will now be rebuilt. This will take a few minutes. Please wait. Root for this system build is / The UNIX Kernel has been rebuilt. Do you want this kernel to boot by default? (y/n) Answer 'y'. Backing up unix to unix.old Installing new unix on the boot file system. The kernel environment includes device node files and /etc/inittab. The new kernel may require changes to /etc/inittab or device nodes. Do you want the kernel environment rebuilt? (y/n) Answer 'y'. The kernel has been successfully linked and installed. To activate it, reboot your system. Setting up new kernel environment You have successfully re-linked a new kernel. In order for the changes to be reflected on your emergency boot floppy set, it is recommended that you run the command '/etc/mkdev fd' and re-create the emergency boot floppy set with the newly linked kernel. Reboot the system using 'shutdown -g0 -y' or 'reboot'. Rebooting After Minicartridge Driver Installation ------------------------------------------------- After minicartridge driver installation, reboot the computer using the command: shutdown -g0 -y or reboot 1) If rebooting with the new driver fails and hangs the system, then seek technical support. - In the meantime, the previous state of the system can be restored as follows: - Reset or re-power the computer and, at the "boot:" prompt, enter: boot: unix.old - Then, after the system boots, remove the driver with the procedure "Using custom(ADM) to Remove the Minicartridge Driver Update" below. 2) Normally, during the boot process, the minicartridge driver displays the following entry in the device list: %mc - - - version=4.0.0s type=mc - Immediately after displaying its entry, the driver searches for a tape drive. 3) If the following message is seen (after the above device list entry) -- mc: initialization error: 23: Drive not found - Wait for the message: Type CONTROL-d to proceed with normal startup, (or give root password for System Maintenance): - Enter the root password and press . Wait until the "#" prompt appears. - Execute the command: haltsys - Wait for the message ** Safe to Power Off ** -or- ** Press Any Key to Reboot ** - Turn the power switch off. - Check that tape drive's data and power cables are properly connected and correctly oriented. "Correctly oriented" for the data cable means the, usually red, marked edge of ribbon cable corresponds to the pin 1 end of tape drive connector. When the power cable is correctly connected, Seagate, Conner, Irwin, and IBM tape drives will blink the LED (in the bezel) once shortly after power is applied. NOTE: It is recommended that a Seagate or Conner drive be configured for 'soft select' (This is the normally shipped configuration). - Power up the system and go to step 1 4) On successful boot, you may want to verify that the driver is functional by inserting a cartridge and using the following commands: mcart h Shows mcart command list mcart drive Shows driver information mcart info Shows tape cartridge information cd /usr/bin; tar cvbf 20 /dev/rctmini . Backup /usr/bin tar tvbf 20 /dev/rctmini Lists content of backup If you are using an alternate tape controller and, during tape access, one of the following messages is seen: "Drive not found", "Interrupt timeout", or "DMA overrun", go to the section "Alternate Tape Controllers" below. Creating an Emergency Boot/Root Floppy -------------------------------------- You should now create emergency Boot and Root floppy(s) with the newly installed tape device on it. This is vital in the case of a system crash where you need to boot from your emergency Boot/Root floppy(s) and restore data from your backup tape. From a unix prompt, type: mkdev fd At the main menu: -------------------------------------------------------------- FLOPPY FILESYSTEM CREATION AND EMERGENCY BOOT/ROOT SET PROGRAM -------------------------------------------------------------- Choices for contents of the floppy filesystem. 1. Filesystem 2. Emergency Boot and Root floppy filesystems Enter an option or q to quit: Choose: 2. Emergency Boot and Root floppy filesystems At the sub menu: Emergency Boot and Root floppy filesystems option ------------------------------------------------- Choices for type of floppy filesystem. 1. 96tpi, double sided, 15 sectors per track (1.2Mb 5.25 inch) 2. 135tpi, double sided, 18 sectors per track (1.44Mb 3.5 inch) 3. 135tpi, double sided, 36 sectors per track (2.88Mb 3.5 inch) Enter an option or q to quit: Choose: 1, 2, or 3 as appropriate for the floppy device At the prompt: Do you want to use floppy drive 0 or floppy drive 1? Choose: 0 or 1 as appropriate for the floppy device At the sub menu: Emergency Boot and Root Filesystems ----------------------------------- Please choose the type of filesystem. 1. Root filesystem 2. Boot filesystem 3. Single floppy Boot and Root filesystem (2.88Mb only) If you have high density (1.44M) disks, you must create separate root and boot filesystem floppies. The root floppy must be prepared first. If you have extra density (2.88Mb) disks, you can choose to have both the root and boot filesystems on the same floppy disk. Enter an option or q to quit: Choose: 1 (or 3 if you have a 2.88Mb drive) At the prompt: Insert a floppy into drive N Press to continue or q to quit: Insert the requested diskette and press: At the prompt: Would you like to format the floppy first? (y/n) Choose: y or n as appropriate for the condition of the diskette. At this juncture, mkdev fd will create a Root filesystem diskette (or in the case of a 2.88 diskette a Root/Boot diskette). Essential files are copied to the diskette, then ... At the prompt: Do you want a shell escape to place extra files on the root filesystem? (y/n) Choose: y At the prompt: You can copy files into /mnt to customize your root filesystem floppy. After you finish, type "exit 0" to continue. You have free blocks (512 bytes each) available on the floppy. Enter: cp /usr/bin/mcart /mnt/usr/bin/mcart At the prompt: Enter: exit 0 mkdev fd will continue copying files, as space permits, to the floppy and complete the creation of a Root filesystem diskette. At the prompt: created and checked successfully. Press to continue Press: At the sub menu: Emergency Boot and Root Filesystems ----------------------------------- Please choose the type of filesystem. 1. Root filesystem 2. Boot filesystem 3. Single floppy Boot and Root filesystem (2.88Mb only) If you have high density (1.44M) disks, you must create separate root and boot filesystem floppies. The root floppy must be prepared first. If you have extra density (2.88Mb) disks, you can choose to have both the root and boot filesystems on the same floppy disk. Enter an option or q to quit: Choose: 2 (or q if you have made a 2.88Mb Root/Boot floppy) At the sub menu: Boot filesystem creation ------------------------ Please choose the boot floppy style. 1. System specific boot 2. Generic boot (builds a special kernel) The System specific boot floppy can only boot the machine it was created on. The Generic boot floppy can be used to boot any machine. Enter an option or q to quit: Choose: 1 (as the minicartridge driver is not yet a Boot Time Loadable Driver) At the prompt: Insert a floppy into drive Press to continue or q to quit: Insert the requested diskette and press: At the prompt: Would you like to format the floppy first? (y/n) Choose: y or n as appropriate for the condition of the diskette. At this point, mkdev fd will create a Boot filesystem diskette. At the prompt: created and checked successfully. Press to continue Press: At the sub menu: Emergency Boot and Root Filesystems ----------------------------------- Please choose the type of filesystem. 1. Root filesystem 2. Boot filesystem 3. Single floppy Boot and Root filesystem (2.88Mb only) If you have high density (1.44M) disks, you must create separate root and boot filesystem floppies. The root floppy must be prepared first. If you have extra density (2.88Mb) disks, you can choose to have both the root and boot filesystems on the same floppy disk. Enter an option or q to quit: Choose: q Creation of the Boot/Root floppy(s) is complete. You may want to reboot using with the Boot/Root floppy(s) to verify functionality of both the Boot/Root and the operation of the tape driver. Be sure to store the floppy(s) in a safe place. In the Event of a System Crash ------------------------------ The emergency Boot/Root floppy(s) that have been prepared by you contains all you will need to boot up and issue a restore command after a system crash. When you boot up using your emergency floppy, you will be put in System Maintenance mode at a root prompt. You can then restore your backup using the following command: /bin/restore rf /dev/rctmini /dev/hd0root The restore command itself restores a root filesystem backup from the tape device. This command is to be used for tape backups made using the "backup", or "sysadmin" utilities. Using custom(ADM) to Remove the Minicartridge Driver Update ----------------------------------------------------------- To remove the minicartridge driver update from the system, and relink the kernel, follow these steps: Double click the Software Manager icon or type /etc/custom In the window: "All software on ", highlight: "Seagate/Irwin Minicartridge Floppy Tape Driver (ver 4.0.0s)" From the menu bar, select: Software -> Remove Software... From the dialogue "Confirm Selected Software on ", "Are you sure you want to remove this software?" "Seagate/Irwin Minicartridge Floppy Tape Driver (ver 4.0.0s)", select: Remove From the dialogue "Select media", select: Floppy Disk Drive 0 -> Continue From the dialogue "Install preference on ", select: Full At this point, custom - displays the dialogue: "Remove Software Progress on ", - removes the minicartridge driver update files, - restores the original system version, and configuration state of the minicartridge driver and, - relinks the kernel. From the dialogue: "Information" "During this removal, the kernel was relinked. You must reboot your" "system to make this kernel effective.", select: OK From the dialogue "Message" "Removal complete", select: OK From the menu bar, select: Host -> Exit The minicartridge driver update is now removed. Reboot the computer using the command: shutdown -g0 -y or reboot The "mcart" Utility ------------------- The minicartridge driver specific utility "/usr/bin/mcart" has also been added to your system. It enables you to perform a number a useful functions on your tape drive. They are summarized below: h This is a help command which allows you to view a list of available "mcart" commands. drive This command provides information about drive type, controller type and unit select. info This command provides information about cartridge state, format and write protect slider position. capacity This command shows the total cartridge capacity in 512 byte blocks after formatting. kapacity This command shows the total cartridge capacity in 1024 byte blocks after formatting. format This command enables you to prepare unformatted tape cartridges for use with your tape drive. If you are using AccuTrak pre-formatted tape cartridges, you will not need to use this command. (SEE NOTE BELOW) To use the "format" command, you need to make sure you are using either brand new, unformatted tapes, or bulk (magnetically) erased tapes. rewind This command is used to rewind a tape after a backup or restore has been interrupted. Normally, the tape is rewound automatically. reten This command is used to align a tape that has not been used for a long time, or has been exposed to temperature extremes. The command syntax is: mcart command For example, using the "rewind" option, the command would be: mcart rewind No-rewind Device: /dev/nrctmini (For Advanced Users) ---------------------------------------------------- The no-rewind device, /dev/nrctmini, was added to v4.x.x of the minicartridge driver. Using /dev/rctmini (rewind device), allows a single archive to be written to a given tape. Each time /dev/rctmini written, the previous archive is overwritten. Using /dev/nrctmini (no-rewind device), allows multiple archives to be saved to a single tape. Each archive is separated by a filemark. A filemark is a special (non-data) tape block automatically written on device close. *** WARNING: IN ORDER TO USE FILEMARKS ON QIC TAPES, THE DRIVER *** MUST BE CONFIGURED TO USE NT STYLE DEFECT/FILEMARK MANAGEMENT. For QIC tapes there are two choices for cartridge management either mgmt_qic_xenix or mgmt_qic_ntmark. mgmt_qic_xenix is compatible with the SCO Xenix-Unix ft driver and Interactive Unix xl driver. mgmt_qic_xenix has NO filemark support. mgmt_qic_ntmark uses Windows NT(tm) style filemark support. When reading tapes, the driver automatically recognizes either management style. When writing tapes, conversion from one defect/filemark management style to another takes place on the first tape write when tape is positioned at beginning-of-medium. A tape is at beginning-of-medium after cartridge insertion, after using the command "mcart rewind", or after using the rewind device /dev/rctmini. The management style written can be selected at run time using the "mcart" utility. For example, use "mcart mgmt_qic_xenix" to select Xenix/Unix ft/xl driver compatible (no-filemarks) QIC management, or "mcart mgmt_qic_ntmark" to select NT (filemark support) QIC style management. Better yet, the initial management selection may be changed by editing the value in mc_mgmt_qic in /etc/conf/pack.d/mc/space.c and re-linking the kernel. Current management values (applied when writing tape from beginning- of-medium) are displayed by the command "mcart mgmt". The minicartridge tape driver will only allow writing tape positioned to beginning-of-medium or end-of-data. When using /dev/nrctmini, the following mcart commands are useful: mcart rewind Positions read/write pointer to beginning-of-medium. mcart eod Positions read/write pointer to end-of-data. mcart rfm Positions read/write pointer just past next filemark If no more filemarks present, positions to end-of-data. Notes ----- (1) Due to problems arising while formatting tapes and for data integrity reasons, it is highly recommended that pre-formatted tapes be used. The format option is provided for use at your own risk! (2) If you choose to format your own tapes, remember that you MUST BULK ERASE the tape to be formatted. If you do not bulk erase your tape, you will not be able to format it. Please remember that the format option is *not* fully supported. It is provided for use at your own risk! (3) Normally, the device you write to should be "/dev/rctmini". This device needs to be specified regardless of whether you are writing to the drive with "tar", "backup", "cpio", or some other utility. (4) Also, regardless of which utility you use to write to the drive, you MUST specify a blocking factor. The recommended blocking factor is "20". (5) While installing your hardware, please refer to the hardware guide shipped with your tape backup unit. If you have questions regarding the installation of your hardware, contact Seagate Technical Support. (6) The minicartridge driver sends error messages to a system service called cmn_err(), which in turn, prints errors on the system console screen and also appends the error messages to the file /usr/adm/messages. (7) Once the driver is installed, avoid using 'mkdev tape' to add or remove the Minicartridge driver. Use 'mkdev mc' instead. If you suspect the installation has been corrupted, re-install v4.0.0s with custom. (8) After installation, additional documentation is present in the file /usr/lib/mc/mc.txt Alternate Tape Controllers -------------------------- At boot time, the driver scans for tape drives. First an alternate controller is scanned and then the system controller. See "Controller Support" section above for a list of alternate tape controllers. The system floppy controller uses these fixed settings: System Floppy Controller (SYSFDC) Settings Base I/O Port: 3F0 (hexadecimal) Interrupt Request (IRQ): 6 DMA Channel: 2 The driver default parameters for an alternate tape controller are: Alternate Tape Controller (ALTFDC) Default Settings Base I/O Port: 370 (hexadecimal) Interrupt Request (IRQ): 6 DMA Channel: 2 The driver's default parameters correspond to the standard settings of the Irwin 4100, Maynard 4100M, and Seagate/Conner CTC-2Mb controllers. Thus, in the default configuration, the alternate controller shares IRQ 6, and DMA 2, with the system floppy controller. When, IRQ and/or DMA settings are shared, the driver manages IRQ/DMA switching and diskette/tape contention. If the following message is seen on the first tape access when an alternate tape controller is used, "DMA overrun", possible causes are: 1) The DMA channel jumpers on the controller may not match the DMA channel settings in the driver's configuration. The solution is to reconfigure the alternate tape controller board and/or driver DMA setting to match. 2) There may be a DMA conflict with another board in the system. If DMA 2 is configured, the system floppy controller may be failing to disconnect from the bus. This condition is typical in a system which uses the Adaptec 1542c SCSI/Floppy controller for the floppy drives. The resolution is to reconfigure both the board jumpers and driver setting for another DMA channel (usually DMA 1 or 3). 3) The alternate tape controller may be defective or not well seated in its slot. Try re-inserting the controller or moving it to another slot. Most alternate tape controllers have 2 DMA jumpers or 2 switches that need to be set to the "on" position. Switches, in particular, can become corroded. If they are supposed to be in the "on" position, try cycling them "off" then back "on" a couple of times. 4) The system DMA controller (on the system board), may be defective. If the following message is seen on the first tape access when an alternate tape controller is used, "Interrupt timeout", possible causes are: 1) The IRQ setting of the alternate tape controller may not match the configuration of the driver. The solution is to reconfigure the alternate tape controller board IRQ jumper and/or driver IRQ setting to match. 2) The IRQ setting of the alternate tape controller may conflict with another controller. The resolution is to reconfigure both the board IRQ jumper and driver IRQ setting for a different interrupt request. 3) The alternate tape controller may be defective or not well seated in its slot. Try re-inserting the controller or moving it to another slot. Most alternate tape controllers have an IRQ jumper or a switch that needs to be set to the "on" position. Switches, in particular, can become corroded. If it is supposed to be in the "on" position, try cycling it "off" then back "on" a couple of times. If the following message is seen on system boot or when attempting to use the tape drive: "Drive not found", possible causes are: 1) The tape drive may be defective or may not be receiving power from the red-black-black-yellow power cable. For Seagate, Conner, Irwin, and IBM tape drives the LED should light briefly when the system is first powered. Check for a secure power cable connection. Power cycle the system and see if the LED flashes. 3) The tape drive's "select" jumper, if any, may be improperly set. Consult hardware manual for the jumper setting. Typically, if a drive supports it, "soft select" is recommended. 2) The ribbon cable may defective or may be misaligned at either the controller or tape drive connectors (pin 1 on the connectors must match), or the ribbon connectors may not be fully inserted. Check ribbon cable installation. 3) The I/O port and/or IRQ settings of the alternate tape controller may not match the configuration of the driver. The solution is to reconfigure the alternate tape controller board I/O port and IRQ jumpers and/or driver I/O port and IRQ settings to match. 4) The I/O port and/or IRQ settings of the alternate tape controller may conflict with another controller. The resolution is to reconfigure both the board jumpers and driver settings for a different I/O port and/or IRQ. 5) The alternate tape controller may be defective or not well seated in its slot. Try re-inserting the controller or moving it to another slot. Most alternate tape controllers have an jumper or switches to select the I/O port. Switches, in particular, can become corroded. If they are set to the "on" position, try cycling them "off" then back "on" a couple of times. The driver's "Alternate controller" settings may be configured either by using '/etc/mkdev mc' or directly editing /etc/conf/pack.d/mc/space.c. To configure using '/etc/mkdev mc', go to "Using '/etc/mkdev mc' to Configure the Minicartridge Driver Update" above. To configure directly, use a text editor such as vi (for example, vi /etc/conf/pack.d/mc/space.c) and adjust the values for: int mc_altfdc_port = 0x370; int mc_altfdc_irq = 6; int mc_altfdc_dmachan = 2; Notes: In "int mc_altfdc_port = 0x370;", the '0x' means that 370 is hexadecimal (omitting 0x makes it decimal). If "int mc_altfdc_port = 0;" the alternate controller drive search is disabled. After editing space.c, the kernel must be relinked and the system rebooted for changes to take effect. To relink the kernel use /etc/conf/cf.d/link_unix and answer 'y' to both questions asked. To reboot the system use shutdown -g0 -y or /etc/reboot Error Messages -------------- Below is a list of the most common error messages included in the minicartridge (mc) tape driver. Block not found IE_BLKNOTFND(5) --------------- A block not found error occurs when the driver cannot locate a physical tape block during a read or write operation. Insure the tape head is clean (see the tape drive hardware manual for cleaning instructions). When this message is displayed during a data restore operation, try retensioning the tape, then repeat the restore operation. If this fails, try restoring the data using a different tape drive. When this message is displayed during data backup operation, try another tape. If your backup is successful on another tape, discard or bulk erase and reformat the original tape. Data CRC error IE_CRC(12) ID CRC error IE_IDCRC(13) -------------- An "ID CRC error", or "Data CRC error" message is displayed during a tape read operation when a tape block cannot be recovered by ECC. If this message appears, retension the tape and try again. If this fails, the data might be recovered by using a different tape drive. Causes of persistent CRC errors are: poor quality tapes, worn tape head, a defect in the drive's record circuitry, or an incompatible or otherwise defective data separator circuit on the controller. CRC errors might be stopped by using new tapes, or installing a data compensator circuit on the drive. Record not found IE_RECNOTFND(14) ---------------- A "Record not found" error occurs when some sector within a tape block cannot be located. This error typically occurs on a during a tape read operation when there are too many erroneous sectors to recover data using ECC. (See Data CRC Error) Drive not found IE_DRVNOTFND(23) --------------- During system boot, a drive searching algorithm is executed by the driver. If this algorithm fails to detect the presence of a tape drive, "mc: initialization error: 23: Drive not found" is displayed. Subsequently, a similar message is displayed on any read or write access to an opened MC device file for which no drive is present. When this message appears, hardware should be checked. Make sure that data and power cables are connected and correctly oriented. "Correctly oriented" for the data cable means the, usually red, marked edge of ribbon cable corresponds to the pin 1 end of tape drive connector. When the power cable is correctly connected, Seagate, Conner, Irwin, and IBM tape drives will blink the LED (in the bezel) once shortly after power is applied. Servo failure IE_SERVO(24) ------------- "Servo failure" is a tape formatting error message. The servo writing function is a part of the tape drive's firmware. The driver commands the tape drive to servo write and awaits tape drive completion status. Usually the drive's LED will be flashing on servo writing failure. Try bulk erasing the cartridge and restart the format. If this fails, try another cartridge. Insufficient memory IE_NOMEM(42) ------------------- "Insufficient memory" messages are given when the driver fails to allocate at least three tape block buffers. Sufficient memory may be available when single user mode is entered immediately after system boot. Usually adding memory to the system will stop this message. Block 0 missing servo header IE_SERVOBLK0(43) Too many sequential missing servo headers IE_SERVOSEQ(44) Too many missing servo headers on track IE_SERVOTRK(45) Too many missing servo headers IE_SERVOTOT(46) Too many sequential bad blocks IE_CYLSEQ(47) Too many bad blocks on a track IE_CYLTRK(48) Too many bad blocks IE_CYLTOT(49) ----------------------------------------- These messages occur during formatting. When formatting fails for one of these reasons, try bulk erasing the cartridge and re- formatting. If this fails, try another cartridge. Block 0 medium error IE_BLK0DEFECT(52) -------------------- A "Block 0 medium error" results when, during tape state determination, the first tape block has a medium error which is not recoverable by either redundant correction or ECC. Normally the cartridge should be reformatted or discarded. If the cartridge has a backup on it, try using a different drive to read the tape. If this message persists for multiple cartridges, the tape drive's read circuitry may be out of adjustment, or there may be an incompatibility between the floppy controller's data separator circuit and the tape drive. Defect list has unrecoverable error IE_DLISTDEFECT(54) ----------------------------------- This message is displayed when both copies of the relocation table (kept in the second and third good tape blocks) have unrecoverable medium errors or are otherwise corrupt. Defect list corrupt IE_DLISTCORRUPT(55) ------------------- This message is displayed if an error is found in the primary defect list kept in block 0. Reformat the tape. Interrupt timeout IE_INTRTMO(92) ------------------- An "Interrupt timeout" occurs when an interrupt is not received from the floppy tape controller. If this error is seen during initialization or the first access of the tape drive, it may be caused by: 1) incorrect driver interrupt (IRQ) configuration, 2) incorrect floppy tape controller interrupt (IRQ) configuration (usually set by jumper on the controller board), or 3) another board configured for the same interrupt (IRQ) as the floppy tape controller (a hardware interrupt conflict). See "Alternate Tape Controllers" above. Files ----- /etc/conf/pack.d/mc/Driver.o Driver object /etc/conf/pack.d/mc/device.dat DQI data for /etc/conf/cf.d/sysRegistry /etc/conf/pack.d/mc/space.c Driver configuration source /etc/conf/node.d/mc Node definitions for /dev directory /etc/conf/sdevice.d/mc System device configuration /etc/conf/cf.d/mdevice Master device list /usr/lib/mc/mc.txt Documentation /usr/bin/mcart Driver specific command utility /etc/mcdaemon Daemon startup program (obsolete) /dev/rmc0 Rewind tape device (minor=0) /dev/nrmc0 No-rewind device (minor=4) /dev/rctmini Rewind device (minor=0) /dev/nrctmini No-rewind device (minor=4) /dev/xctmini Control device (minor=4) /opt/K/SCO/mcDriver/* Custom install directory /opt/P/SCO/mcDriver/* Custom install product directory /var/opt/K/SCO/mcDriver/* Custom install directory