Anyone know how to install an IBM LTO 3 Ultrium tape drive?

What works, and doesn't, for you. Be specific, and please include Puppy version.
Message
Author
PappyPuppy
Posts: 409
Joined: Sat 01 Oct 2016, 00:27

And it's NOT 0 or 7 or 15

#16 Post by PappyPuppy »

The ID it finds the IBM LTO Ultrium 3 23R4762/95P2012 drive on IS ID 7.

The Adaptec card is a PCI device. And I would guess that it picks up the IBM drive. I would like to shut the BIOS from running each time. Is it not saving this information ID 7? That's why it runs each boot?


PappyPuppy
Posts: 409
Joined: Sat 01 Oct 2016, 00:27

Their Fix Central says to start by typing your product name

#18 Post by PappyPuppy »

It says that for device names of IBM Ultrium-TD3 that I MUST use the IBM drivers.

Now I have to analyze 3 things!
1) Is my device really IBM Ultrium-TD3. I guess that's a yes.
2) Do I really MUST have those drivers!
3) What is the product name that corresponds to the device that's named IBM Ultrium-TD3.

Why can't I just put in IBM LTO Ultrium 3 23R4762? I can't get the product name to match!

I need to find drivers under this (GNU drivers):
Tape drivers and software, Tape device drivers (Linux 64-bit,x86_64)

I think I'm this:
IBM Ultrium Gen-3 and IBM 400/800GB LTO Gen 3
Drive ID : IBM ULTRIUM-TD3
Firmware : 4C17

I would guess that if they say I need their drivers and the Linux Kernel won't drive it, then I might need source code to recompile, although sometimes drivers will work - like for .deb or something. A lot of unknowns right now.

Under /proc/scsi, I've got a directory aic7xxx, which has 7 and 8, and is what dmesg | grep 'Adaptec' gives the scsi host7 and host 8 params and it lists the ID as 7 iin the files 7 and 8. So the Adaptec is set up. I'm not yet quite sure why there is 25.340029 AND 44.480029

PappyPuppy
Posts: 409
Joined: Sat 01 Oct 2016, 00:27

I'm justchecking some stuff

#19 Post by PappyPuppy »

dmesg | grep 'Adaptec'

[ 25.340029] scsi host7: Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 7.0
<Adaptec 3960D Ultra160 SCSI adapter>
[ 44.480029] scsi host8: Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 7.0
<Adaptec 3960D Ultra160 SCSI adapter>


cat /proc/scsi/aic7xxx/7

Adaptec AIC7xxx driver version: 7.0
Adaptec 3960D Ultra160 SCSI adapter
aic7899: Ultra160 Wide Channel A, SCSI Id=7, 32/253 SCBs
Allocated SCBs: 4, SG List Length: 128

Serial EEPROM:
0xc33a 0xc33a 0xc33a 0xc33a 0xc33a 0xc33a 0xc33a 0xc33a
0xc33a 0xc33a 0xc33a 0xc33a 0xc33a 0xc33a 0xc33a 0xc33a
0xb8f4 0x7c5d 0x2807 0x0110 0x0300 0xffff 0xffff 0xffff
0xffff 0xffff 0xffff 0xffff 0xffff 0xffff 0x0250 0x974f

Target 0 Negotiation Settings
User: 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)
Target 1 Negotiation Settings
User: 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)
Target 2 Negotiation Settings
User: 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)
Target 3 Negotiation Settings
User: 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)
Target 4 Negotiation Settings
User: 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)
Target 5 Negotiation Settings
User: 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)
Target 6 Negotiation Settings
User: 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)
Target 7 Negotiation Settings
User: 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)
Target 8 Negotiation Settings
User: 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)
Target 9 Negotiation Settings
User: 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)
Target 10 Negotiation Settings
User: 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)
Target 11 Negotiation Settings
User: 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)
Target 12 Negotiation Settings
User: 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)
Target 13 Negotiation Settings
User: 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)
Target 14 Negotiation Settings
User: 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)
Target 15 Negotiation Settings
User: 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)


cat /proc/scsi/aic7xxx/8

Adaptec AIC7xxx driver version: 7.0
Adaptec 3960D Ultra160 SCSI adapter
aic7899: Ultra160 Wide Channel B, SCSI Id=7, 32/253 SCBs
Allocated SCBs: 4, SG List Length: 128

Serial EEPROM:
0xc33a 0xc33a 0xc33a 0xc33a 0xc33a 0xc33a 0xc33a 0xc33a
0xc33a 0xc33a 0xc33a 0xc33a 0xc33a 0xc33a 0xc33a 0xc33a
0xb8f4 0x7c5d 0x2807 0x0110 0x0300 0xffff 0xffff 0xffff
0xffff 0xffff 0xffff 0xffff 0xffff 0xffff 0x0250 0x974f

Target 0 Negotiation Settings
User: 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)
Target 1 Negotiation Settings
User: 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)
Target 2 Negotiation Settings
User: 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)
Target 3 Negotiation Settings
User: 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)
Target 4 Negotiation Settings
User: 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)
Target 5 Negotiation Settings
User: 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)
Target 6 Negotiation Settings
User: 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)
Target 7 Negotiation Settings
User: 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)
Target 8 Negotiation Settings
User: 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)
Target 9 Negotiation Settings
User: 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)
Target 10 Negotiation Settings
User: 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)
Target 11 Negotiation Settings
User: 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)
Target 12 Negotiation Settings
User: 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)
Target 13 Negotiation Settings
User: 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)
Target 14 Negotiation Settings
User: 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)
Target 15 Negotiation Settings
User: 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)

These show that the ID is 7

PappyPuppy
Posts: 409
Joined: Sat 01 Oct 2016, 00:27

I have NOT yet tried SCSI Select's 2nd option

#20 Post by PappyPuppy »

I guess I thought that this was mostly only for Hard-drives, not tape drives, but perhaps I should see if it gives me an ID of the tape drive?

I don't know.

PappyPuppy
Posts: 409
Joined: Sat 01 Oct 2016, 00:27

I think I need to reboot

#21 Post by PappyPuppy »

How can the BIOS on the Adaptec SCSI Controller be disabled?
Answer ID 2353 | Published 05/21/2001 06:06 PM | Updated 08/12/2010 08:58 AM
The Adaptec SCSI Controller becomes the priority boot card when installed.

How can the BIOS on the Adaptec SCSI Controller be disabled so it won't attempt to boot over the existing boot controller or onboard chipset?


This information applies to the following Operating System(s):
- This information is not Operating System specific
The SCSI Controller BIOS can be disabled within the SCSI BIOS, via the SCSISelect feature on the SCSI controller.

During the system boot process, you will see the Adaptec BIOS and a prompt to press Ctrl-A to go inside SCSISelect.

Once inside the SCSISelect utility:

Choose the SCSI controller you want to disable the BIOS on and press enter.

Choose Configure / View SCSI Controller Settings and press enter.

Choose Advanced Configuration inside Additional Options area below.

Select SCSI Controller Int 13 Support. This option controls the state of the BIOS at POST time. The following settings are available:

Enabled - Supports INT 13 for booting from a SCSI hard disk drive connected to the SCSI card. If you use this option, the following options are available:
- Extended INT 13 Translation for DOS Drives > 1 GB
- Support Removable Disks Under INT 13 as Fixed Disks
- BIOS Support for Bootable CD-ROM

Disabled:NOT Scan - select this option if all the devices on the SCSI bus are controlled by software drivers and do not need the BIOS, and you do not want the BIOS to scan the SCSI bus. SCSISelect remains available if needed.

Disabled:Scan Bus - select this option if all the devices on the SCSI bus are controlled by software drivers and you need the BIOS to scan the SCSI bus. Allows devices to spin up according to the setting of the Send Start Unit Command. SCSISelect remains available if needed.

Note: Once you have changed the BIOS settings, press "Esc" twice and it will prompt you to save the changes. Press "Esc" again to exit and then restart the system.
Was this answer helpful?

PappyPuppy
Posts: 409
Joined: Sat 01 Oct 2016, 00:27

I've changed the Adaptec under Advanced on boot

#22 Post by PappyPuppy »

from running SCSISelect each time. I hope this streamlines things a little at least.

When I ran the Drive Configurator it gave me the message "Not a disk drive" which is correct and it gives me the ID 0 for the IBM ULTRIUM-TD3 and 7 for the Adaptec card.

Firmware of the Tape drive is 6B20

So at least I'm learning.

The computer is booting now without the SCSISelect screen for the first time.

PappyPuppy
Posts: 409
Joined: Sat 01 Oct 2016, 00:27

Suppose I wanted to reenable the SCSISelect and using card

#23 Post by PappyPuppy »

Just curious how I would reenable that stuff.

I'm not planning to need that anytime soon. Perhaps I can just run SCSISelect from the command line somehow.??

The computer is rebooted but still no tape drive.

So no kernel drivers are loading.

PappyPuppy
Posts: 409
Joined: Sat 01 Oct 2016, 00:27

I may need the source code for the -TD3 drives

#24 Post by PappyPuppy »

I wonder if I can get that source code and recompile?

I have sent a message to someone who had the same problem as me and asked him for the names of the drivers.

PappyPuppy
Posts: 409
Joined: Sat 01 Oct 2016, 00:27

I've rebooted into Windows XP

#25 Post by PappyPuppy »

My computer can be booted into Windows XP. I'll work with that for a while while I await any feedback from those who've read my posts and messages - maybe there is a tape tool or driver source that I can compile for Fatdog.

So I will start now to get this to run on Windows. But in the end, I need it to run on Linux.

PappyPuppy
Posts: 409
Joined: Sat 01 Oct 2016, 00:27

I am trying to find the IBM manuals from a long list

#26 Post by PappyPuppy »

IBM says that they obsolete their manuals - not sure what that means.

I am still looking for a manual so I can install in windows now while I wait for help with Fatdog Linux.

IBM Ultrium Device Drivers Installation and User’s Guide, GC32-0430-13

I need the above manual. I cannot find it.

PappyPuppy
Posts: 409
Joined: Sat 01 Oct 2016, 00:27

Under device manager, I see a yellow question mark

#27 Post by PappyPuppy »

So I wonder if I can update the drivers for this and get it to recognize it?

It says that this device is working properly.

I have no program to use in windows yet. So that's another job. I wonder if it is really working properly. Why doesn't it list it as a tape drive? Apparently it doesn't know that it's a tape drive but it says it's working properly. I guess I need to check for drivers. If it really has a driver? It says Driver Provider: Unknown, I don't think it's really working.

PappyPuppy
Posts: 409
Joined: Sat 01 Oct 2016, 00:27

I can't get it to work on Windows XP either

#28 Post by PappyPuppy »

But I will be busy for the day, so I'm not on this for a bit. I'm not making any progress. I wonder though, did another company develop stuff that will work on IBM's tape system. Like firmware/software, or even hardware. Am I looking in the wrong place for drivers for the IBM tape drive.

PappyPuppy
Posts: 409
Joined: Sat 01 Oct 2016, 00:27

Implementing IBM Tape in Linux and Windows

#29 Post by PappyPuppy »

I hope that this document was written soon enough for the release of my tape drive. My tape drive was manufactured in 2007 although I think that model was available as early as late 2005 or 2006. These are details that may be important. This (October 2005) is the Fourth edition of the above manual, started in 2002. I am trying to point my helper(s) in the direction I'm going as I was hoping to finish this by Friday and it's now Sunday. Such is life.

Windows XP came out in late 2001 I believe? A little later than Windows 2000 but before Windows 2003. The reason I mention this is just that the overall hardware/software platforms they supported can sometimes come into play. I will make a call tomorrow to a "helper" I spoke with once already and see what "platform(s)" he uses. This might help also.

But page 183 of that manual describes what to do for Linux. I will start reading that now.

There is an issue of which manual to read or should I just read what I can find, so I will at least take a look at that and see if I can follow it and get it to work.

Thanks for any help. And this is my only thread for this forum. The others are locked so please if you have some smarts or whatever, post it here, thanks. :D

PappyPuppy
Posts: 409
Joined: Sat 01 Oct 2016, 00:27

Narrowing down which set of documents are for my reader

#30 Post by PappyPuppy »

SLES12, SLES11, RHEL7, RHEL6, Archives
Update: The above refer to Enterprise Linux Server, and Redhat, so I would guess I'll be in Archives or possibly one of the other. I don't know yet.

I am trying to see which set of Fixit Central archives to go through. In the previous post I mention page 183. On page 184, they suggest reading over some documents - if I navigate to IBM's ftp site, and drill down to storage/devdrvr/Doc, the Doc has been replaced with a link to an http site FixIt Central. I'm going through that now.

So two mysteries:
1) Which document is for my reader?
2) Why is my Ultrium reader, a 23R4762 never, ever mentioned anywhere but the IBM 3580 series ARE mentioned. This is what I'm trying to figure out - where is my reader mentioned - that would help.

PappyPuppy
Posts: 409
Joined: Sat 01 Oct 2016, 00:27

I need to search for kernel support in the form of st driver

#31 Post by PappyPuppy »

I may have to simply walk the system through creating the st drive. Perhaps I have support and something is just not there that automatically detects something. Perhaps even a parameter in the Adaptec, like 16 eg. for bus, should that be 32. I doubt it but it's not impossible that some LUN feature or whatever isn't there but maybe I can mknod and get a device up that way. I don't know yet until I try to look for the tape drive support. If it's there, I can start trying stuff.

PappyPuppy
Posts: 409
Joined: Sat 01 Oct 2016, 00:27

Output of modinfo command

#32 Post by PappyPuppy »

When I run the command modinfo st, it DOES list tape drive support:

filename: /lib/modules/4.4.35/kernel/drivers/scsi/st.ko
alias: ...
alias: ...
license: ...
description: SCSI tape (st) driver

So I have support for tape drives in my Fatdog 710 kernel.

So I should create a device /dev/st0

User avatar
Flash
Official Dog Handler
Posts: 13071
Joined: Wed 04 May 2005, 16:04
Location: Arizona USA

#33 Post by Flash »

I don't know if this is any help, but I believe that Linux only mounts filesystems, not devices. If there is no tape in the drive, there can be no filesystem to mount. Same as a DVD drive without a DVD in it.

PappyPuppy
Posts: 409
Joined: Sat 01 Oct 2016, 00:27

Thanks for the info - I've tried mounting a tape

#34 Post by PappyPuppy »

When I insert a CD, an icon for SR0 appears on the Fatdog desktop.

When I insert a tape, nothing appears. But perhaps I need to tell the boot-up process something - this is over my head but I need to begin to try things.

This causes me concern, as I would expect it to show the icon when I insert a tape. So I need to debug and/or work around this problem.

I just have to keep understanding it. Trying stuff might have to wait until I read more - like, what parameters will I give the mknod command, anyway? I am about to mknod --help or whatever now.

User avatar
rockedge
Posts: 1864
Joined: Wed 11 Apr 2012, 13:32
Location: Connecticut, United States
Contact:

#35 Post by rockedge »

here is a manual I had in some corner of storage...maybe it might help
http://rockedge.org/images2/IBM_Tape_De ... er_IUG.pdf

Post Reply