SCSI tape library ISCSI
Hi all, it's possible to manage a SCSI tape library (IBM 3581) with ISCSI? I need to use that library attached to a server into another server... Thanks Regards M **
Re: SCSI tape library ISCSI
Hi, it's possible to manage a SCSI tape library (IBM 3581) with ISCSI? I need to use that library attached to a server into another server... well, the aim is to share the tape library across the network.. Is there a way (iscsi or other) to do the job? Regards M
Re: SCSI tape library ISCSI
On 4/9/2010 10:39 AM, Mirco Piccin wrote: Hi, it's possible to manage a SCSI tape library (IBM 3581) with ISCSI? I need to use that library attached to a server into another server... well, the aim is to share the tape library across the network.. Is there a way (iscsi or other) to do the job? Regards M What you need is a SCSI to iSCSI bridge. http://www.attostore.com/iscsibridges.html I do not know of any software that can do this for you. -- Ryan Manikowski ]] Devision Media Services LLC [[ www.devision.us r...@devision.us | 716.771.2282 -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4bbf4a3b.2030...@devision.us
Re: SCSI tape library ISCSI
Mirco Piccin put forth on 4/9/2010 9:39 AM: Hi, it's possible to manage a SCSI tape library (IBM 3581) with ISCSI? I need to use that library attached to a server into another server... well, the aim is to share the tape library across the network.. Is there a way (iscsi or other) to do the job? All you need is an iSCSI bridge such as one of these ATTO units: http://www.attotech.com/products/product.php?cat=5scat=8sku=IPBR-2600-DR0 http://www.attotech.com/products/product.php?cat=5scat=8sku=IPBR-1550-DR0 They'll make that SCSI tape library appear on the iSCSI network as any normal iSCSI device. The 8581 doesn't allow multiple concurrent host access as it was designed in the late 1990s strictly as a single host direct attach tape libraby. Thus you'll need to make sure only one host is accessing the tape library at a time over iSCSI. Attempting concurrent access will cause problems and data loss. CAVEAT: Is your IBM 3581 a model L1x or H1x? H1x uses a high voltage differential SCSI interface. It is NOT compatible with the ATTO bridges above which are both U320 LVD SCSI devices. LVD stands for Low Voltage Differential. If you have the 3581 H1x you will need an iSCSI bridge with a high voltage differential SCSI port such as this: http://www.testequipmentconnection.com/products/28976 If you plug an HVD SCSI device into an LVD only port or vice versa, the LVD device will be permanently damaged and ruined as a result. High Voltage means exactly that. Never never plug HVD SCSI into LVD SCSI. Hope this information helps you. Good luck. -- Stan -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4bbfaa61.10...@hardwarefreak.com
Re: SCSI tape library ISCSI
Hi, thanks for replies. it's possible to manage a SCSI tape library (IBM 3581) with ISCSI? I need to use that library attached to a server into another server... well, the aim is to share the tape library across the network.. Is there a way (iscsi or other) to do the job? What you need is a SCSI to iSCSI bridge. All you need is an iSCSI bridge such as one of these ATTO units: http://www.attotech.com/products/product.php?cat=5scat=8sku=IPBR-2600-DR0 http://www.attotech.com/products/product.php?cat=5scat=8sku=IPBR-1550-DR0 Atto device it's not a really cheap solution :-) Since it's a temporary need, I'll try to find a workaround... Regards M
Re: SCSI tape library ISCSI
Mirco Piccin put forth on 4/9/2010 6:48 PM: Hi, thanks for replies. it's possible to manage a SCSI tape library (IBM 3581) with ISCSI? I need to use that library attached to a server into another server... well, the aim is to share the tape library across the network.. Is there a way (iscsi or other) to do the job? What you need is a SCSI to iSCSI bridge. All you need is an iSCSI bridge such as one of these ATTO units: http://www.attotech.com/products/product.php?cat=5scat=8sku=IPBR-2600-DR0 http://www.attotech.com/products/product.php?cat=5scat=8sku=IPBR-1550-DR0 Atto device it's not a really cheap solution :-) Neither was that IBM 3581 tape library. Since it's a temporary need, I'll try to find a workaround... You should be able to do it with one of the iSCSI targets and a kernel 2.6.x Linux box containing an ethernet port and a SCSI connector/interface compatible with your library. Try looking thoroughly here: http://sourceforge.net/apps/mediawiki/iscsitarget/index.php?title=FrequentlyAskedQuestions and here: http://scst.sourceforge.net/ SCST is probably what you'll want. It apparently allows direct SCSI-iSCSI device pass through, which sounds like what you want/need. -- Stan -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4bbfdaba.20...@hardwarefreak.com
Re: Re: scsi tape drive - debian package
Thanks for responding everyone ! I found a very good tar script which I want to utilise, but I think I need to take a step back. I think I'm missing something, everyone is mentioning, your tape device should be /dev/tape or /dev/st0 etc.. The only things I have under /dev/ are: /dev/ MAKEDEV ataraid ccissfd ida inputprinter pts rd usb I'm not sure if it's there ? ^above. When I issue this command, it shows the tape drive there though. cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 06 Lun: 00 Vendor: DELL Model: 1x4 U2W SCSI BP Rev: 5.35 Type: ProcessorANSI SCSI revision: 02 Host: scsi0 Channel: 02 Id: 00 Lun: 00 Vendor: MegaRAID Model: LD0 RAID5 69356R Rev: 1.01 Type: Direct-AccessANSI SCSI revision: 02 Host: scsi1 Channel: 00 Id: 09 Lun: 00 Vendor: SONY Model: SDX-300C Rev: 0400 Type: Sequential-AccessANSI SCSI revision: 02 Host: scsi2 Channel: 00 Id: 05 Lun: 00 Vendor: NEC Model: CD-ROM DRIVE:466 Rev: 1.06 Type: CD-ROM ANSI SCSI revision: 02 Am I missing something ? Thanks all ! -- Ross. Andrew Schulman [EMAIL PROTECTED] wrote: posted mailed Hi all, I recently attached a SCSI tape drive to my raid box running Debian. It's a SONY Model: SDX-300C I was hoping someone could point me in the right direction on how to get it working, backing up. I had a look at Amanda, that looked very complicated for me ! Is there a simpler software package ? Try tar. When I first got my tape drive, I tried a lot of fancy graphical backup utilities: Perfect Backup, Arkeia, and others. But like you, my needs are simple. In the end I just wrote a shell script to call tar. It's completely adequate for my needs. Remember, the most important thing a tape drive can do is to protect you in case of catastrophe, i.e. hard disk crash. In that event, you may not have X working, you may be working in a very minimal environment after booting from a rescue disk. tar will be there for you, but will you be able to run Arkeia or Amanda? While we're on the subject, consider building a custom rescue CDROM. There are several of them out there. I followed and modified the instructions at http://www.phenix.bnl.gov/~purschke/RescueCD/, with good results. With one of these you can boot your system from CD and be in a good position to call tar to get your files back. Good luck! Andrew. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
scsi tape drive - debian package
Hi all, I recently attached a SCSI tape drive to my raid box running Debian. It's a SONY Model: SDX-300C I was hoping someone could point me in the right direction on how to get it working, backing up. I had a look at Amanda, that looked very complicated for me ! Is there a simpler software package ? Any good HOW-TO's lying about ? I only want to backup files on this box, not across the network, they're all local files. I'm pretty sure I'm halfway there as Debian can see the tape drive (see below) == cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 06 Lun: 00 Vendor: DELL Model: 1x4 U2W SCSI BP Rev: 5.35 Type: ProcessorANSI SCSI revision: 02 Host: scsi0 Channel: 02 Id: 00 Lun: 00 Vendor: MegaRAID Model: LD0 RAID5 69356R Rev: 1.01 Type: Direct-AccessANSI SCSI revision: 02 Host: scsi1 Channel: 00 Id: 09 Lun: 00 Vendor: SONY Model: SDX-300C Rev: 0400 Type: Sequential-AccessANSI SCSI revision: 02 Host: scsi2 Channel: 00 Id: 05 Lun: 00 Vendor: NEC Model: CD-ROM DRIVE:466 Rev: 1.06 Type: CD-ROM ANSI SCSI revision: 02 == Any help would be greatly appreciated ! -- Ross. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: scsi tape drive - debian package
On Thu, Sep 18, 2003 at 10:43:40AM +1000, [EMAIL PROTECTED] wrote: Hi all, I recently attached a SCSI tape drive to my raid box running Debian. It's a SONY Model: SDX-300C I was hoping someone could point me in the right direction on how to get it working, backing up. I had a look at Amanda, that looked very complicated for me ! Amanda is probably overkill for your situation. Is there a simpler software package ? Heh, well simple doesn't necessarily mean easy to use. In that vein, take a look at mt for controlling the drive, tar, dump (for ext2/3 only), or cpio for performing the actual backups. Any good HOW-TO's lying about ? Section 12 of the Linux System Administrators Guide has some examples of using tar for tape backups. http://www.tldp.org/LDP/sag/backups.html Rob -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: scsi tape drive - debian package
posted mailed Hi all, I recently attached a SCSI tape drive to my raid box running Debian. It's a SONY Model: SDX-300C I was hoping someone could point me in the right direction on how to get it working, backing up. I had a look at Amanda, that looked very complicated for me ! Is there a simpler software package ? Try tar. When I first got my tape drive, I tried a lot of fancy graphical backup utilities: Perfect Backup, Arkeia, and others. But like you, my needs are simple. In the end I just wrote a shell script to call tar. It's completely adequate for my needs. Remember, the most important thing a tape drive can do is to protect you in case of catastrophe, i.e. hard disk crash. In that event, you may not have X working, you may be working in a very minimal environment after booting from a rescue disk. tar will be there for you, but will you be able to run Arkeia or Amanda? While we're on the subject, consider building a custom rescue CDROM. There are several of them out there. I followed and modified the instructions at http://www.phenix.bnl.gov/~purschke/RescueCD/, with good results. With one of these you can boot your system from CD and be in a good position to call tar to get your files back. Good luck! Andrew. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Adding SCSI Controller, SCSI Tape, and SCSI Disk to 2.2.20-idepci system
On 13 Jan 2003, 15:30:52, nate wrote:
Doug MacFarlane said:
So I apt-got a 2.4.19-686 kernel image, and when I rebooted, I had to use
modconf to enable the 3c59x driver, and when I rebooted, it runs like
molasses . . . during boot, it takes minutes to complete the calculate
module dependencies step. This hadn't happened before, and I don't have
time to figure it out yet . . .
this is odd, but does it boot eventually? does this happen everytime
it boots? after it boots can you delete /lib/modules/`uname -r`/modules.dep
and run depmod -a ..does it take the same amount of time?
Yes, it boots but runs very slowly.
If I delete modules.dep and then run depmod -a, the depmod completes in less
than a second. But the Calculating Module Dependencies during boot takes
3 minutes . . .
I think I have a problem with initrd - I'm pasting in a piece of dmesg below:
PIIX4: IDE controller on PCI bus 00 dev a1
PIIX4: chipset revision 1
PIIX4: not 100% native mode: will probe irqs later
ide0: BM-DMA at 0x14c0-0x14c7, BIOS settings: hda:DMA, hdb:DMA
ide1: BM-DMA at 0x14c8-0x14cf, BIOS settings: hdc:DMA, hdd:pio
hda: ST34321A, ATA DISK drive
hdb: ST38641A, ATA DISK drive
hdc: TOSHIBA CD-ROM XM-5602B, ATAPI CD/DVD-ROM drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ide1 at 0x170-0x177,0x376 on irq 15
blk: queue cc84eea4, I/O limit 4095Mb (mask 0x)
hda: 8421840 sectors (4312 MB) w/128KiB Cache, CHS=8912/15/63, UDMA(25)
blk: queue cc84eff0, I/O limit 4095Mb (mask 0x)
hdb: 16809660 sectors (8607 MB) w/128KiB Cache, CHS=16676/16/63, UDMA(25)
Partition check:
/dev/ide/host0/bus0/target0/lun0: [PTBL] [557/240/63] p1 p2 p5
/dev/ide/host0/bus0/target1/lun0:hdb: set_multmode: status=0x51 { DriveReady
SeekComplete Error }
hdb: set_multmode: error=0x04 { DriveStatusError }
[PTBL] [/240/63] p1 p5 p6 p7 p8 p9 p2
ext3: No journal on filesystem on ide0(3,69)
I have no idea why it's trying to use ext3 and jbd . . .
When I boot 2.2.20, it, ofcourse, is NOT an initrd kernel, and it runs fine,
and I don't get any of these messages in dmesg . . .
So my workaround will be to recompile the 2.4.29 or 2.4.20 kernel without
changing the config, and leaving off the --initrd make-kpkg option, and editing
lilo.conf to remove the initrd option, and see if that fixes it . . .
Any thoughts?
As always, thanks for your help.
madmac
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
RE: Adding SCSI Controller, SCSI Tape, and SCSI Disk to 2.2.20-idepci system
On 14 Jan 2003, 14:51:26, Colin Ellis wrote:
From looking at your dmesg output, it looks like your drive hdb is on its
way out...
I am concerned about that myself, but when I boot the non-initrd 2.2.20-idepci
kernel, I don't get any of those messages . . .
madmac
-Original Message-
From: Doug MacFarlane [mailto:[EMAIL PROTECTED]]
Sent: 14 January 2003 14:28
To: [EMAIL PROTECTED]; nate; Eduard Bloch
Subject: Re: Adding SCSI Controller, SCSI Tape, and SCSI Disk to
2.2.20-idepci system
On 13 Jan 2003, 15:30:52, nate wrote:
Doug MacFarlane said:
So I apt-got a 2.4.19-686 kernel image, and when I rebooted, I had to
use
modconf to enable the 3c59x driver, and when I rebooted, it runs like
molasses . . . during boot, it takes minutes to complete the calculate
module dependencies step. This hadn't happened before, and I don't have
time to figure it out yet . . .
this is odd, but does it boot eventually? does this happen everytime
it boots? after it boots can you delete
/lib/modules/`uname -r`/modules.dep
and run depmod -a ..does it take the same amount of time?
Yes, it boots but runs very slowly.
If I delete modules.dep and then run depmod -a, the depmod completes in less
than a second. But the Calculating Module Dependencies during boot takes
3 minutes . . .
I think I have a problem with initrd - I'm pasting in a piece of dmesg
below:
PIIX4: IDE controller on PCI bus 00 dev a1
PIIX4: chipset revision 1
PIIX4: not 100% native mode: will probe irqs later
ide0: BM-DMA at 0x14c0-0x14c7, BIOS settings: hda:DMA, hdb:DMA
ide1: BM-DMA at 0x14c8-0x14cf, BIOS settings: hdc:DMA, hdd:pio
hda: ST34321A, ATA DISK drive
hdb: ST38641A, ATA DISK drive
hdc: TOSHIBA CD-ROM XM-5602B, ATAPI CD/DVD-ROM drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ide1 at 0x170-0x177,0x376 on irq 15
blk: queue cc84eea4, I/O limit 4095Mb (mask 0x)
hda: 8421840 sectors (4312 MB) w/128KiB Cache, CHS=8912/15/63, UDMA(25)
blk: queue cc84eff0, I/O limit 4095Mb (mask 0x)
hdb: 16809660 sectors (8607 MB) w/128KiB Cache, CHS=16676/16/63, UDMA(25)
Partition check:
/dev/ide/host0/bus0/target0/lun0: [PTBL] [557/240/63] p1 p2 p5
/dev/ide/host0/bus0/target1/lun0:hdb: set_multmode: status=0x51 {
DriveReady SeekComplete Error }
hdb: set_multmode: error=0x04 { DriveStatusError }
[PTBL] [/240/63] p1 p5 p6 p7 p8 p9 p2
ext3: No journal on filesystem on ide0(3,69)
I have no idea why it's trying to use ext3 and jbd . . .
When I boot 2.2.20, it, ofcourse, is NOT an initrd kernel, and it runs fine,
and I don't get any of these messages in dmesg . . .
So my workaround will be to recompile the 2.4.29 or 2.4.20 kernel without
changing the config, and leaving off the --initrd make-kpkg option, and
editing
lilo.conf to remove the initrd option, and see if that fixes it . . .
Any thoughts?
As always, thanks for your help.
madmac
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact
[EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
RE: Adding SCSI Controller, SCSI Tape, and SCSI Disk to 2.2.20-idepci system
Just a thought, but you may have an IDE controller that requires a
workaround.
I'm not an expert as to the differences in standard IDE controller
configuration between v2.2 and v2.4, but I would guess that some controllers
that required the config option other IDE chipset support in the kernel
v2.2 are automatically supported under v2.4. This may mean that the boot
time DMA modes are different. Try reading ide.txt in the kernel
documentation with regards to setting up the various modes.
Regards,
Colin Ellis
Solution City Ltd
http://www.solution-city.com
-Original Message-
From: Doug MacFarlane [mailto:[EMAIL PROTECTED]]
Sent: 14 January 2003 15:30
To: Colin Ellis; [EMAIL PROTECTED]
Subject: RE: Adding SCSI Controller, SCSI Tape, and SCSI Disk to
2.2.20-idepci system
On 14 Jan 2003, 14:51:26, Colin Ellis wrote:
From looking at your dmesg output, it looks like your drive hdb is on its
way out...
I am concerned about that myself, but when I boot the non-initrd
2.2.20-idepci
kernel, I don't get any of those messages . . .
madmac
-Original Message-
From: Doug MacFarlane [mailto:[EMAIL PROTECTED]]
Sent: 14 January 2003 14:28
To: [EMAIL PROTECTED]; nate; Eduard Bloch
Subject: Re: Adding SCSI Controller, SCSI Tape, and SCSI Disk to
2.2.20-idepci system
On 13 Jan 2003, 15:30:52, nate wrote:
Doug MacFarlane said:
So I apt-got a 2.4.19-686 kernel image, and when I rebooted, I had to
use
modconf to enable the 3c59x driver, and when I rebooted, it runs like
molasses . . . during boot, it takes minutes to complete the calculate
module dependencies step. This hadn't happened before, and I don't
have
time to figure it out yet . . .
this is odd, but does it boot eventually? does this happen everytime
it boots? after it boots can you delete
/lib/modules/`uname -r`/modules.dep
and run depmod -a ..does it take the same amount of time?
Yes, it boots but runs very slowly.
If I delete modules.dep and then run depmod -a, the depmod completes in
less
than a second. But the Calculating Module Dependencies during boot takes
3 minutes . . .
I think I have a problem with initrd - I'm pasting in a piece of dmesg
below:
PIIX4: IDE controller on PCI bus 00 dev a1
PIIX4: chipset revision 1
PIIX4: not 100% native mode: will probe irqs later
ide0: BM-DMA at 0x14c0-0x14c7, BIOS settings: hda:DMA, hdb:DMA
ide1: BM-DMA at 0x14c8-0x14cf, BIOS settings: hdc:DMA, hdd:pio
hda: ST34321A, ATA DISK drive
hdb: ST38641A, ATA DISK drive
hdc: TOSHIBA CD-ROM XM-5602B, ATAPI CD/DVD-ROM drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ide1 at 0x170-0x177,0x376 on irq 15
blk: queue cc84eea4, I/O limit 4095Mb (mask 0x)
hda: 8421840 sectors (4312 MB) w/128KiB Cache, CHS=8912/15/63, UDMA(25)
blk: queue cc84eff0, I/O limit 4095Mb (mask 0x)
hdb: 16809660 sectors (8607 MB) w/128KiB Cache, CHS=16676/16/63, UDMA(25)
Partition check:
/dev/ide/host0/bus0/target0/lun0: [PTBL] [557/240/63] p1 p2 p5
/dev/ide/host0/bus0/target1/lun0:hdb: set_multmode: status=0x51 {
DriveReady SeekComplete Error }
hdb: set_multmode: error=0x04 { DriveStatusError }
[PTBL] [/240/63] p1 p5 p6 p7 p8 p9 p2
ext3: No journal on filesystem on ide0(3,69)
I have no idea why it's trying to use ext3 and jbd . . .
When I boot 2.2.20, it, ofcourse, is NOT an initrd kernel, and it runs
fine,
and I don't get any of these messages in dmesg . . .
So my workaround will be to recompile the 2.4.29 or 2.4.20 kernel without
changing the config, and leaving off the --initrd make-kpkg option, and
editing
lilo.conf to remove the initrd option, and see if that fixes it . . .
Any thoughts?
As always, thanks for your help.
madmac
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact
[EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Adding SCSI Controller, SCSI Tape, and SCSI Disk to 2.2.20-idepci system
Doug MacFarlane said:
Partition check:
/dev/ide/host0/bus0/target0/lun0: [PTBL] [557/240/63] p1 p2 p5
/dev/ide/host0/bus0/target1/lun0:hdb: set_multmode: status=0x51 {
DriveReady SeekComplete Error }
hdb: set_multmode: error=0x04 { DriveStatusError }
[PTBL] [/240/63] p1 p5 p6 p7 p8 p9 p2
ext3: No journal on filesystem on ide0(3,69)
I have no idea why it's trying to use ext3 and jbd . . .
When I boot 2.2.20, it, ofcourse, is NOT an initrd kernel, and it runs
fine, and I don't get any of these messages in dmesg . . .
So my workaround will be to recompile the 2.4.29 or 2.4.20 kernel without
changing the config, and leaving off the --initrd make-kpkg option, and
editing lilo.conf to remove the initrd option, and see if that fixes it .
I did a search on that error and came up with:
http://dvd.sourceforge.net/xine-howto/en_GB/html/howto-10.html
Using Linux, I get an error which contains status=0x51 { DriveReady
SeekComplete Error }
To fix this error, try enabling `Use multi-mode by default' in your kernel
(re-compile setting ATA/IDE/MFM/RLL support - IDE, ATA and ATAPI Block
devices - Use multi-mode by default to `Y'). The relevant piece of kernel
documentation states:
CONFIG_IDEDISK_MULTI_MODE:
If you get this error, try to say Y here:
hda: set_multmode: status=0x51 { DriveReady SeekComplete Error }
hda: set_multmode: error=0x04 { DriveStatusError }
If in doubt, say N.
check /boot/config-`uname -r` for CONFIG_IDEDISK_MULTI_MODE
my redhat 7.3 system has this set to Y, but my custom debian systems
have this set to N ..
not sure what the default is.
changing this may help the other problem(s) as well.
nate
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Adding SCSI Controller, SCSI Tape, and SCSI Disk to 2.2.20-idepci system
Team: Well, I'm confused . . . After a meltdown of my primary Linux desktop, I setup my winblows machine to dual-boot in Debian. My original desktop had been installed by booting woody CDs and installing a vanilla kernel, and then apt-getting 2.418-686-smp kernel images (the kitchen sink variety, I believe). All this ran with no sweat. I had even learned how to compile my own kernel, and had started paring-down all the modules, etc. in the kitchen-sink kernel I was running. And then it died. SCSI controllers on the MB fried. So, my WinBlows PC has problems booting from the woody CD, so I did a floppy install of the 2.2.20-idepci kernel. No sweat. Running fine. But now I want to add a SCSI controller (Symbios), SCSI Tape-drive (HP), and SCSI disk, none of which were on my old desktop. So I figure So I apt-got a 2.4.19-686 kernel image, and when I rebooted, I had to use modconf to enable the 3c59x driver, and when I rebooted, it runs like molasses . . . during boot, it takes minutes to complete the calculate module dependencies step. This hadn't happened before, and I don't have time to figure it out yet . . . So I figure, how hard can it be to add SCSI support and SCSI Tape and Disk support to my 2.2.20-idepci system? Well, there are a lot of docs about what modules you need to load, and how to do it (modconf, insmod, echo modulename /etc/modules.conf and so on), and all of it makes sense to me EXCEPT . . . Where and how do I download the modules from? Where do I put them? and just exactly what is The Debian Way for doing all this? Even Osamu's DebianReference didn't help with this . . . TIA madmac -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Adding SCSI Controller, SCSI Tape, and SCSI Disk to 2.2.20-idepci system
#include hallo.h * Doug MacFarlane [Mon, Jan 13 2003, 10:40:24PM]: My original desktop had been installed by booting woody CDs and installing a vanilla kernel, and then apt-getting 2.418-686-smp kernel images (the kitchen sink variety, Do you have an SMP (multi-processor) system? I believe). All this ran with no sweat. I had even learned how to compile my own kernel, and had started paring-down all the modules, etc. in the kitchen-sink kernel I was running. And then it died. SCSI controllers on the MB fried. So, my WinBlows PC has problems booting from the woody CD, so I did a floppy install of the 2.2.20-idepci kernel. No sweat. Running fine. But now I want to add a SCSI controller (Symbios), SCSI Tape-drive (HP), and SCSI disk, none of which were on my old desktop. So I figure Forget it. -idepci is the worst kernel among the installation kernels. OTOH, it is most safe. So I figure, how hard can it be to add SCSI support and SCSI Tape and Disk support to my 2.2.20-idepci system? Why don't you try kernel-image-2.4.20-something? Well, there are a lot of docs about what modules you need to load, and how to do it (modconf, insmod, echo modulename /etc/modules.conf and so on), and all of it makes sense to me EXCEPT . . . Where and how do I download the modules from? Where do I put them? idepci is a thin installation kernel and not created for daily work, IMHO. Gruss/Regards, Eduard. -- Zum Unlesbarmachen kann man auch cdrecord blank=full auf eine CD-R anwenden ;-) aber doch wohl nur in /dev/mikrowelle oder? :-) Andreas 'Knv' Kanev in de.comp.hardware.cd-brenner -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Adding SCSI Controller, SCSI Tape, and SCSI Disk to 2.2.20-idepci system
Doug MacFarlane said: But now I want to add a SCSI controller (Symbios), SCSI Tape-drive (HP), and SCSI disk, none of which were on my old desktop. So I figure So I apt-got a 2.4.19-686 kernel image, and when I rebooted, I had to use modconf to enable the 3c59x driver, and when I rebooted, it runs like molasses . . . during boot, it takes minutes to complete the calculate module dependencies step. This hadn't happened before, and I don't have time to figure it out yet . . . this is odd, but does it boot eventually? does this happen everytime it boots? after it boots can you delete /lib/modules/`uname -r`/modules.dep and run depmod -a ..does it take the same amount of time? So I figure, how hard can it be to add SCSI support and SCSI Tape and Disk support to my 2.2.20-idepci system? should be pretty easy. .. Where and how do I download the modules from? Where do I put them? I personally build my own kernels, but in your case I would put the names of the modules in /etc/modules. some module names you may need: sym53c416 (SCSI card driver for symbios 53c416) or perhaps you need sym53c8xx (SCSI card driver for symbios SYM53C8XX) and sd_mod (SCSI disk driver) st (SCSI tape driver) scsi_mod (SCSI core driver, should be automatically loaded when you load the SCSI device driver) and just exactly what is The Debian Way for doing all this? Even Osamu's DebianReference didn't help with this . . . uncertain. I suppose one way would be to build your own kernel with kernel-package ..(what I do) good luck nate -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: SCSI-Tape und devfsd
Am Sam, 2002-10-19 um 16.58 schrieb Karsten Rothemund: Hallo Liste, Hallo Karsten, ich habe ein SCSI-Tape (DDS1) geerbt. Jadzia:/etc/devfs# cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 03 Lun: 00 Vendor: PLEXTOR Model: CD-ROM PX-20TS Rev: 1.00 Type: CD-ROM ANSI SCSI revision: 02 Host: scsi0 Channel: 00 Id: 04 Lun: 00 Vendor: GENERIC Model: CRD-RW2 Rev: 1.21 Type: CD-ROM ANSI SCSI revision: 02 Host: scsi0 Channel: 00 Id: 06 Lun: 00 Vendor: EXABYTE Model: EXB-4200 Rev: 148 Type: Sequential-AccessANSI SCSI revision: 02 Jadzia:/etc/devfs# Was muss ich jetzt in /etc/devsf/* (welche Datei?) eintragen, damit ich die zugehoerigen Devices erhalte? /dev/tape existiert nicht (und folglich auch nicht die old-style Device-Eintraege). Ich habe versucht, die CDRom-Eintraege zu kopieren und zu modifizieren, was aber keinen Erfolg brachte. Die Devices werden erzeugt und die noetigen Module geladen, wenn ich auf CDRom und Brenner zugreife. Fuer Tapes habe ich keine Info in der Doku zu devfsd gefunden (kann sein, dass ich sie uebersehen haben - dann sorry, aber stosst mich bitte doch mit der Nase drauf ;). Dankbar fuer jeden Tipp, ich habe hier einen DDS2-Streamer mit devfs laufen. Das hat bei mir out of the box funktioniert. Solange der Streamer nicht benutzt wird, werden keine Devices angelegt. Sobald er das erste mal angesprochen wird, wird das entsprechende Kernelmodul automatisch nachgeladen und dadurch die Device-Einräge erzeugt. Bei mir (SCSI-Id 6) /dev/scsi/host0/bus0/target6/lun0/mt* Die Kompatibility-Links /dev/st0 und /dev/nst0 werden auch erzeugt. Von der Benutzung von einem symbolischen Link /dev/tape auf das eigentliche Gerätefile solltest Du wegen der Unterscheidung zwischen non-rewinding Devices (/dev/nst0) und rewinding Devices (/dev/st0) absehen. Grüße Klaus Duscher -- Häufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
SCSI-Tape und devfsd
Hallo Liste, ich habe ein SCSI-Tape (DDS1) geerbt. Jadzia:/etc/devfs# cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 03 Lun: 00 Vendor: PLEXTOR Model: CD-ROM PX-20TS Rev: 1.00 Type: CD-ROM ANSI SCSI revision: 02 Host: scsi0 Channel: 00 Id: 04 Lun: 00 Vendor: GENERIC Model: CRD-RW2 Rev: 1.21 Type: CD-ROM ANSI SCSI revision: 02 Host: scsi0 Channel: 00 Id: 06 Lun: 00 Vendor: EXABYTE Model: EXB-4200 Rev: 148 Type: Sequential-AccessANSI SCSI revision: 02 Jadzia:/etc/devfs# Was muss ich jetzt in /etc/devsf/* (welche Datei?) eintragen, damit ich die zugehoerigen Devices erhalte? /dev/tape existiert nicht (und folglich auch nicht die old-style Device-Eintraege). Ich habe versucht, die CDRom-Eintraege zu kopieren und zu modifizieren, was aber keinen Erfolg brachte. Die Devices werden erzeugt und die noetigen Module geladen, wenn ich auf CDRom und Brenner zugreife. Fuer Tapes habe ich keine Info in der Doku zu devfsd gefunden (kann sein, dass ich sie uebersehen haben - dann sorry, aber stosst mich bitte doch mit der Nase drauf ;). Dankbar fuer jeden Tipp, -- ciao, Karsten Karsten Rothemund, mailto:karsten.rothemund;etechnik.uni-rostock.de, http://www-ae.e-technik.uni-rostock.de/home/karo/ PGP-Key: finger [EMAIL PROTECTED] (Please use it!) --- This mail address must not be used for advertising or offers of any kind. This address must not be included in mailing lists without my permission. Contraventions will be charged by a fee of 5000 US $. msg21878/pgp0.pgp Description: PGP signature
Re: SCSI-Tape und devfsd
On Sat, 19 Oct 2002 16:58:57 +0200 Karsten Rothemund [EMAIL PROTECTED] wrote: Hallo Liste, ich habe ein SCSI-Tape (DDS1) geerbt. Jadzia:/etc/devfs# cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 03 Lun: 00 Vendor: PLEXTOR Model: CD-ROM PX-20TS Rev: 1.00 Type: CD-ROM ANSI SCSI revision: 02 Host: scsi0 Channel: 00 Id: 04 Lun: 00 Vendor: GENERIC Model: CRD-RW2 Rev: 1.21 Type: CD-ROM ANSI SCSI revision: 02 Host: scsi0 Channel: 00 Id: 06 Lun: 00 Vendor: EXABYTE Model: EXB-4200 Rev: 148 Type: Sequential-AccessANSI SCSI revision: 02 Jadzia:/etc/devfs# Was muss ich jetzt in /etc/devsf/* (welche Datei?) eintragen, damit ich die zugehoerigen Devices erhalte? /dev/tape existiert nicht (und folglich auch nicht die old-style Device-Eintraege). Ich habe versucht, die CDRom-Eintraege zu kopieren und zu modifizieren, was aber keinen Erfolg brachte. Die Devices werden erzeugt und die noetigen Module geladen, wenn ich auf CDRom und Brenner zugreife. Fuer Tapes habe ich keine Info in der Doku zu devfsd gefunden (kann sein, dass ich sie uebersehen haben - dann sorry, aber stosst mich bitte doch mit der Nase drauf ;). Dankbar fuer jeden Tipp, -- ciao, Karsten Hi Kartsen, The Linux 2.4 SCSI subsystem HowTo (/usr/share/doc/HOWTO/en-txt/SCSI-2.4-HOWTO.gz) ist eine wunderbare Hilfe zu Deiner Frage. Dort steht sehr gut beschrieben wie das Ebenen-Modell der SCSI-Module aussieht und welche Module wann wofür erforderlich sind. Auch auf devfs wird eingegangen, so daß Du die Antwort finden wirst. Das alles hier nochmal zu wiederholen ist glaube ich überflüssig. Ich hoffe, daß das nicht nur nach RTFM klingt. Gruß CHristian -- Häufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: SCSI-Tape und devfsd
* Karsten Rothemund [EMAIL PROTECTED] [19-10-02 16:58]: Was muss ich jetzt in /etc/devsf/* (welche Datei?) eintragen, damit ich die zugehoerigen Devices erhalte? /dev/tape existiert nicht (und folglich auch nicht die old-style Device-Eintraege). Lege doch eine Link an. :-) Habe kein Tape. Hier mal ein Beispiel für /dev/dvd $ cat /etc/devfs/conf.d/dvd # create the /dev/dvd symlink REGISTER^cdroms/cdrom1$ CFUNCTION GLOBAL symlink $devname dvd UNREGISTER ^cdroms/cdrom1$ CFUNCTION GLOBAL unlink dvd -- Häufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Installing a SCSI Tape-Drive to an Existing Woody System
Team: I installed an HP DDS-4 SCSI tape-drive to my existing Woody system. Upon the reboot, the startup messages showed that it was detected, but I guess the base install doesn't include support for it because: boulion:/cdrom# tar cvf /dev/st0 /home tar: Removing leading `/' from member names home/ home/lost+found/ home/madmac/ home/madmac/.bashrc home/madmac/.bash_profile home/madmac/.xsession-errors tar: /dev/st0: Wrote only 0 of 10240 bytes tar: Error is not recoverable: exiting now boulion:/cdrom# So I assume I need to install a module for this. My questions: 1. How do I find out what modules support what devices? 2. Where are the instructions for adding/installing a module? All the stuff I found via google and linuxhelp.org was centered around what to do when installing linux, or using kudzu with Red Hat . . . TIA mamdac -- Doug MacFarlane [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Installing a SCSI Tape-Drive to an Existing Woody System
On Sat, Oct 05, 2002 at 06:18:19PM +, Doug MacFarlane wrote: Team: I installed an HP DDS-4 SCSI tape-drive to my existing Woody system. Upon the reboot, the startup messages showed that it was detected, but I guess the base install doesn't include support for it because: boulion:/cdrom# tar cvf /dev/st0 /home tar: Removing leading `/' from member names home/ home/lost+found/ home/madmac/ home/madmac/.bashrc home/madmac/.bash_profile home/madmac/.xsession-errors tar: /dev/st0: Wrote only 0 of 10240 bytes tar: Error is not recoverable: exiting now boulion:/cdrom# So I assume I need to install a module for this. My questions: I think that is not the problem. If I try this on a machine without a tapedrive, I get a 'no such device' error. What does 'mt -f /dev/st0 status' report ? Maybe you should try 'mt -f /dev/st0 setblk 10240' before the tar command (the default tar blocksize is 10240 bytes) 1. How do I find out what modules support what devices? 2. Where are the instructions for adding/installing a module? All the stuff I found via google and linuxhelp.org was centered around what to do when installing linux, or using kudzu with Red Hat . . . TIA mamdac -- Doug MacFarlane [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
SCSI Tape Device
There have been some good posts concerning SCSI device modules that have helped me try to correct my problem, but nonetheless, I'm still stuck. Ok, here is more information. When I was using kernel 2.2.xxx my SCSI tape drive worked. Provided immediately below I am attaching those sections of dmesg output that would appear to be relevant to my SCSI device for kernel 2.2.xxx. Linux version 2.2.17 ([EMAIL PROTECTED]) (gcc version 2.95.2 2313 (Debian GNU/Linux)) #1 Sun Jun 25 09:24:41 EST 2000 md driver 0.36.6 MAX_MD_DEV=4, MAX_REAL=8 (scsi0) found at PCI 0/10/0 (scsi0) Wide Channel, SCSI ID=7, 16/255 SCBs (scsi0) Downloading sequencer code... 415 instructions downloaded scsi: Detection failed (no card) scsi0 : Adaptec AHA274x/284x/294x (EISA/VLB/PCI-Fast SCSI) 5.1.31/3.2.4 scsi : 1 host. (scsi0:0:2:0) Synchronous at 6.67 Mbyte/sec, offset 15. Vendor: ARCHIVE Model: Python 02779-XXX Rev: 6280 Type: Sequential-Access ANSI SCSI revision: 02 scsi : detected total. st: bufsize 32768, wrt 30720, max buffers 5, s/g segs 16. Detected scsi tape st0 at scsi0, channel 0, id 2, lun 0 Serial driver version 4.27 with no serial options enabled After updating to kernel 2.4.18, there is only 1 line related to the SCSI driver in dmesg as shown below: Linux version 2.4.18-386 ([EMAIL PROTECTED]) (gcc version 2.95.4 (Debian prerelease)) #2 Wed Mar 20 20:15:40 EST 2002 SCSI subsystem driver Revision: 1.00 Reading some of the latest SCSI issues I put the only module I would think relates to my SCSI device in my modules file, rebooted. Still it's not working. Here's the output form dmesg now: Linux version 2.4.18-386 ([EMAIL PROTECTED]) (gcc version 2.95.4 20011002 (Debian prerelease)) #2 Sun Apr 14 10:38:08 EST 2002 . SCSI subsystem driver Revision: 1.00 (scsi0) Adaptec AHA-294X SCSI host adapter found at PCI 0/10/0 (scsi0) Wide Channel, SCSI ID=7, 16/255 SCBs (scsi0) Downloading sequencer code... 415 instructions downloaded scsi0 : Adaptec AHA274x/284x/294x (EISA/VLB/PCI-Fast SCSI) 5.2.4/5.2.0 Adaptec AHA-294X SCSI host adapter Vendor: ARCHIVE Model: Python 02779-XXX Rev: 6280 Type: Sequential-Access ANSI SCSI revision: 02 (scsi0:0:2:1) Synchronous at 6.67 Mbyte/sec, offset 15. st: Version 20020205, bufsize 32768, wrt 30720, max init. bufs 4, s/g segs 16 Attached scsi tape st0 at scsi0, channel 0, id 2, lun 0 st0: Block limits 1 - 16777215 bytes. Can anyone help me figure this one out? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
[Fwd: SCSI Tape Device] -- Forget it
Forget my post. It's now working! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: SCSI Tape Device
On Wed, May 01, 2002 at 05:20:05PM -0700, curtis wrote: There have been some good posts concerning SCSI device modules that have helped me try to correct my problem, but nonetheless, I'm still stuck. Ok, here is more information. When I was using kernel 2.2.xxx my SCSI tape drive worked. Provided immediately below I am attaching those sections of dmesg output that would appear to be relevant to my SCSI device for kernel 2.2.xxx. Linux version 2.2.17 ([EMAIL PROTECTED]) (gcc version 2.95.2 2313 (Debian GNU/Linux)) #1 Sun Jun 25 09:24:41 EST 2000 md driver 0.36.6 MAX_MD_DEV=4, MAX_REAL=8 (scsi0) found at PCI 0/10/0 (scsi0) Wide Channel, SCSI ID=7, 16/255 SCBs (scsi0) Downloading sequencer code... 415 instructions downloaded scsi: Detection failed (no card) scsi0 : Adaptec AHA274x/284x/294x (EISA/VLB/PCI-Fast SCSI) 5.1.31/3.2.4 scsi : 1 host. (scsi0:0:2:0) Synchronous at 6.67 Mbyte/sec, offset 15. Vendor: ARCHIVE Model: Python 02779-XXX Rev: 6280 Type: Sequential-Access ANSI SCSI revision: 02 scsi : detected total. st: bufsize 32768, wrt 30720, max buffers 5, s/g segs 16. Detected scsi tape st0 at scsi0, channel 0, id 2, lun 0 Serial driver version 4.27 with no serial options enabled After updating to kernel 2.4.18, there is only 1 line related to the SCSI driver in dmesg as shown below: Linux version 2.4.18-386 ([EMAIL PROTECTED]) (gcc version 2.95.4 (Debian prerelease)) #2 Wed Mar 20 20:15:40 EST 2002 SCSI subsystem driver Revision: 1.00 Reading some of the latest SCSI issues I put the only module I would think relates to my SCSI device in my modules file, rebooted. Still it's not working. Here's the output form dmesg now: Linux version 2.4.18-386 ([EMAIL PROTECTED]) (gcc version 2.95.4 20011002 (Debian prerelease)) #2 Sun Apr 14 10:38:08 EST 2002 . SCSI subsystem driver Revision: 1.00 (scsi0) Adaptec AHA-294X SCSI host adapter found at PCI 0/10/0 (scsi0) Wide Channel, SCSI ID=7, 16/255 SCBs (scsi0) Downloading sequencer code... 415 instructions downloaded scsi0 : Adaptec AHA274x/284x/294x (EISA/VLB/PCI-Fast SCSI) 5.2.4/5.2.0 Adaptec AHA-294X SCSI host adapter Vendor: ARCHIVE Model: Python 02779-XXX Rev: 6280 Type: Sequential-Access ANSI SCSI revision: 02 (scsi0:0:2:1) Synchronous at 6.67 Mbyte/sec, offset 15. st: Version 20020205, bufsize 32768, wrt 30720, max init. bufs 4, s/g segs 16 Attached scsi tape st0 at scsi0, channel 0, id 2, lun 0 st0: Block limits 1 - 16777215 bytes. Can anyone help me figure this one out? I have an old AHA-2940 card. modules loaded: scsi_mod, sd_mod, st, sg, ide-scsi, aic7xxx These work with 2.4.17-386; I haven't checked it yet with 2.4.18. modprobe st may be all you need to do. ide-scsi is loaded because my tape drive is actually ide device. I think sd_mod is needed for zip drive and not tape but am not sure. Jerome pgp5v9GFC1qKe.pgp Description: PGP signature
SCSI Tape Device
Has anyone had a similar problem. While I was under 2.2 kernel my scsi tape drive worked fine. After upgrading to 2.4, however, I can't seem to get it to install or detect my scsi drive no matter what. Any ideas? Curtis -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: SCSI Tape Device
curtis wrote: Has anyone had a similar problem. While I was under 2.2 kernel my scsi tape drive worked fine. After upgrading to 2.4, however, I can't seem to get it to install or detect my scsi drive no matter what. Any ideas? Curtis -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] What's your SCSI I/F H/W? It's a shot in the dark, but... When I upgraded to 2.4.17 tar started hanging my system. It turned out that SCSI disconnects aren't supported for the external SCSI on the Mac 8500. Things worked fine when backing up the internal disks, but the system hung when backing up the outboard disks. A workaround was to reconfigure--I put all disks on the internal SCSI and isolatied the tape drive on the external SCSI. --rich -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: SCSI Tape Device
Has anyone had a similar problem. While I was under 2.2 kernel my scsi tape drive worked fine. After upgrading to 2.4, however, I can't seem to get it to install or detect my scsi drive no matter what. Any ideas? Curtis -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] What's your SCSI I/F H/W? It's a shot in the dark, but... When I upgraded to 2.4.17 tar started hanging my system. It turned out that SCSI disconnects aren't supported for the external SCSI on the Mac 8500. Things worked fine when backing up the internal disks, but the system hung when backing up the outboard disks. A workaround was to reconfigure--I put all disks on the internal SCSI and isolatied the tape drive on the external SCSI. --rich Some more detail would probably be useful. Here are some pointer that helped me install an old Conner Peregrine CTD4004 SCSI DAT Drive on to my Woody box (Compaq Professional Workstation 5000 PPro SMP) kernel 2.4.7. *Make sure that SCSI tape support is compiled into your kernel. *Even if this support is compiled in run dmesg | more after reboot and see if you can spot something like the following: Vendor: ARCHIVE Model: Python 28388-XXX Rev: 5.45 Type: Sequential-Access ANSI SCSI revision: 02 (Sequential-Access is the important bit) Followed by: Attached scsi tape st0 at scsi0, channel 0, id 4, lun 0 *Switch off any power on self diagnostic/fault testing routine. Hope this helps. James James Aitken W: +44 (0) 20 8547 0470 H: +44 (0) 1322 404582 M: +44 (0) 7768 057306 E: [EMAIL PROTECTED] -- Personalised email by http://another.com
Re: SCSI Tape Device
Ok, here is more information. Provided immediately below I am attaching those sections of dmesg output that would appear to be relevant to my SCSI device. First I rebooted under kernel 2.2, which as I have said loads my SCSI device. Here is it's dmesg output: Linux version 2.2.17 ([EMAIL PROTECTED]) (gcc version 2.95.2 2313 (Debian GNU/Linux)) #1 Sun Jun 25 09:24:41 EST 2000 md driver 0.36.6 MAX_MD_DEV=4, MAX_REAL=8 (scsi0) Adaptec AHA-294X SCSI host adapter found at PCI 0/10/0 (scsi0) Wide Channel, SCSI ID=7, 16/255 SCBs (scsi0) Downloading sequencer code... 415 instructions downloaded scsi: fdomain Detection failed (no card) scsi0 : Adaptec AHA274x/284x/294x (EISA/VLB/PCI-Fast SCSI) 5.1.31/3.2.4 Adaptec AHA-294X SCSI host adapter scsi : 1 host. (scsi0:0:2:0) Synchronous at 6.67 Mbyte/sec, offset 15. Vendor: ARCHIVE Model: Python 02779-XXX Rev: 6280 Type: Sequential-Access ANSI SCSI revision: 02 scsi : detected total. st: bufsize 32768, wrt 30720, max buffers 5, s/g segs 16. Detected scsi tape st0 at scsi0, channel 0, id 2, lun 0 Serial driver version 4.27 with no serial options enabled Here then is the dmesg output for kernel 2.4, which has only 1 line related only to the SCSI driver. There is nothing else: Linux version 2.4.18-386 ([EMAIL PROTECTED]) (gcc version 2.95.4 (Debian prerelease)) #2 Wed Mar 20 20:15:40 EST 2002 SCSI subsystem driver Revision: 1.00 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: IDE CD recorder, in machine with SCSI tape?
On Saturday 03 November 2001 01:37, Stan Brown wrote: NOw, acording to the CD Recording HOWTO, I should be able to run cdrecord -scanbus and see what my avaialble devise are. Unfortunately, on both machines it just reports 7 slots, one of which has the SCSI tape in it. I've always had problems with cdrecord -scanbus I never seem to get the second scsi bus on my machines (where all the CD burners are) scaned but using cdrecord dev=1,4,0 speed=8 /path/to.iso works fine for my 8x4x24 Yam. First off SCSI emulation is the second scsi bus (as the first bus is your real scsi card). I'd be guessing that a virtual scsi controler would at the first scsi device (1,0,0) so I'd try 1,1,0. What I would do is to try to burn a cd without a cd in the burner starting at 1,0,0 and increasing that second number (the device id), you'll either get something about the device not existing or it'll barf when it checks the media but before then you'll get a load of info about te burner. HTH Ani
Re: IDE CD recorder, in machine with SCSI tape?
On Fri, Nov 02, 2001 at 06:20:22PM -0800, Thomas Zimmerman wrote: As you have true scsi, you don't need ide-scsi. cdrecord -scanbus shouldtm pick up all of your scsi devices. That it doesn't makes me wonder if enabling your kernel to probe all LUNs will help. It is a kernel config question. I'm sure you just missed the fact that the burner is IDE. :) -- Marc Wilson [EMAIL PROTECTED] [EMAIL PROTECTED] pgppx53Pt016I.pgp Description: PGP signature
Re: IDE CD recorder, in machine with SCSI tape?
On Fri, Nov 02, 2001 at 08:37:40PM -0500, Stan Brown wrote: HP cd16ri CD recorder installed in machines with Aadaptec SCSI host card, each has exactly on device on the SCSI bus. I think you said earlier that the CD-R was on hda? And that it worked? You can mount discs and all? modules deleted Ok, when you loaded ide-scsi, did it see the drive? It should have logged something saying that it had detected a drive to manage. NOw, acording to the CD Recording HOWTO, I should be able to run cdrecord -scanbus and see what my avaialble devise are. Unfortunately, on both machines it just reports 7 slots, one of which has the SCSI tape in it. It should look like this (unused LUN's removed): [19:26][pts/3][16][/home/mwilson] # cdrecord -scanbus Cdrecord 1.10 (i686-pc-linux-gnu) Copyright (C) 1995-2001 J?rg Schilling Linux sg driver version: 3.1.20 Using libscg version 'schily-0.5' scsibus0: 0,5,0 5) 'ARCHIVE ' 'Python 02635-XXX' '567D' Removable Tape 0,6,0 6) 'TOSHIBA ' 'DVD-ROM SD-M1201' '1R08' Removable CD-ROM scsibus1: 1,0,0 100) 'IOMEGA ' 'ZIP 100 ' '14.A' Removable Disk 1,1,0 101) '_NEC' 'NR-7700A' '1.01' Removable CD-ROM [19:26][pts/3][16][/home/mwilson] # You see the normal SCSI bus on my NCR810 card first, with the tape drive and the DVD, and then the simulated SCSI bus produced by ide-scsi that has my Zip and my burner on it. So. It seems that something else is taking control of the device before ide-scsi gets a chance to. That's usually ide-cd, the normal IDE CDROM driver in the kernel. You need to either leave it out (since you can just let ide-scsi do everything), or else tell it to ignore the burner. Or make it a module, and load one or the other when you want them. That would pretty much mean that you'd have to load ide-scsi by hand when you wanted it, unless you engaged in some trickery in /etc/modutils. Try telling ide-cd to ignore the drive, first. Add: append=hda=ide-scsi to your boot (in lilo.conf) and see then whether ide-scsi can control the drive. silly quote deleted, since it resolves to Digital Research being the creators of Windows, rather than Microsoft -- Marc Wilson [EMAIL PROTECTED] [EMAIL PROTECTED] pgpVO6ubuF5Ho.pgp Description: PGP signature
IDE CD recorder, in machine with SCSI tape?
K, at this point i've tried this on 2 different machines. Here's the scenarion HP cd16ri CD recorder installed in machines with Aadaptec SCSI host card, each has exactly on device on the SCSI bus. Both are Debian potato + Progeny + 2.4x kernels ( one 2.4.3, and 1 2.4.9). On the machine at home I have the folowing modules loaded: Module Size Used by sg 22832 0 (autoclean) mousedev4496 0 (unused) input 3904 0 [mousedev] ide-scsi8112 0 aic7xxx 117072 0 scsi_mod 86368 3 [sg ide-scsi aic7xxx] ne 6880 1 NOw, acording to the CD Recording HOWTO, I should be able to run cdrecord -scanbus and see what my avaialble devise are. Unfortunately, on both machines it just reports 7 slots, one of which has the SCSI tape in it. How can I make this scenarion work? BTW on the machine at home the tape device is really a tape changer, and I can control it using mtx, so I know the SCSI generic stuff is working corectly. Thanks for any sugestions. -- Stan Brown [EMAIL PROTECTED]843-745-3154 Charleston SC. -- Windows 98: n. useless extension to a minor patch release for 32-bit extensions and a graphical shell for a 16-bit patch to an 8-bit operating system originally coded for a 4-bit microprocessor, written by a 2-bit company that can't stand for 1 bit of competition. - (c) 2000 Stan Brown. Redistribution via the Microsoft Network is prohibited.
Re: IDE CD recorder, in machine with SCSI tape?
On 02-Nov 08:37, Stan Brown wrote: K, at this point i've tried this on 2 different machines. Here's the scenarion HP cd16ri CD recorder installed in machines with Aadaptec SCSI host card, each has exactly on device on the SCSI bus. Both are Debian potato + Progeny + 2.4x kernels ( one 2.4.3, and 1 2.4.9). On the machine at home I have the folowing modules loaded: Module Size Used by sg 22832 0 (autoclean) mousedev4496 0 (unused) input 3904 0 [mousedev] ide-scsi8112 0 aic7xxx 117072 0 scsi_mod 86368 3 [sg ide-scsi aic7xxx] ne 6880 1 NOw, acording to the CD Recording HOWTO, I should be able to run cdrecord -scanbus and see what my avaialble devise are. Unfortunately, on both machines it just reports 7 slots, one of which has the SCSI tape in it. How can I make this scenarion work? As you have true scsi, you don't need ide-scsi. cdrecord -scanbus shouldtm pick up all of your scsi devices. That it doesn't makes me wonder if enabling your kernel to probe all LUNs will help. It is a kernel config question. BTW on the machine at home the tape device is really a tape changer, and I can control it using mtx, so I know the SCSI generic stuff is working corectly. ...and this shows that scsi works... Thanks for any sugestions. -- Stan Brown [EMAIL PROTECTED] 843-745-3154 Charleston SC. [snip] Thomas pgparHKjrTzs3.pgp Description: PGP signature
[OT] scsi tape problems
hi, i have a problem with my scsi tape (HP C1537A DDS3): the scsi ids are set as follows: Host: scsi0 Channel: 00 Id: 00 Lun: 00 Vendor: IBM Model: DNES-318350Y Rev: SA30 Type: Direct-AccessANSI SCSI revision: 03 Host: scsi0 Channel: 00 Id: 01 Lun: 00 Vendor: IBM Model: DNES-318350Y Rev: SA30 Type: Direct-AccessANSI SCSI revision: 03 Host: scsi0 Channel: 00 Id: 03 Lun: 00 Vendor: HP Model: C1537A Rev: L907 Type: Sequential-AccessANSI SCSI revision: 02 inetmain:/etc/afbackup# and mt -f /dev/nst0 stat reports drive type = Generic SCSI-2 tape drive status = 620756992 sense key error = 0 residue count = 0 file number = 54 block number = 0 Tape block size 0 bytes. Density code 0x25 (unknown). Soft error count since last status=0 General status bits on (8901): EOF EOD ONLINE IM_REP_EN but when i start afbackup the server always reports: mt: /dev/nst0: Input/output error but it dows increase the file nr and if i kill it (i know i never should but as i can't be shure the backup is written...) i see eg drive type = Generic SCSI-2 tape drive status = 620756992 sense key error = 0 residue count = 0 file number = 54 block number = 0 Tape block size 0 bytes. Density code 0x25 (unknown). Soft error count since last status=0 General status bits on (8901): EOF EOD ONLINE IM_REP_EN and mt -f /dev/nst0 rewind works as well. what problem could this be? before changing to the DDS 3 tape drive the DDS 2 drive worked fine. any ideas? tia martin -- GnuPG 1024D/3E8DCCC0 30DC 1D28 1D79 32F5 5E67 3ABB 28EE B35A 3E8D CCC0 work: factline Krisper Fabro Harnoncourt OEG (www.factline.com)
Re: [OT] scsi tape problems
Martin Würtele wrote: hi, i have a problem with my scsi tape (HP C1537A DDS3): the scsi ids are set as follows: Host: scsi0 Channel: 00 Id: 00 Lun: 00 Vendor: IBM Model: DNES-318350Y Rev: SA30 Type: Direct-AccessANSI SCSI revision: 03 Host: scsi0 Channel: 00 Id: 01 Lun: 00 Vendor: IBM Model: DNES-318350Y Rev: SA30 Type: Direct-AccessANSI SCSI revision: 03 Host: scsi0 Channel: 00 Id: 03 Lun: 00 Vendor: HP Model: C1537A Rev: L907 Type: Sequential-AccessANSI SCSI revision: 02 inetmain:/etc/afbackup# and mt -f /dev/nst0 stat reports drive type = Generic SCSI-2 tape drive status = 620756992 sense key error = 0 residue count = 0 file number = 54 block number = 0 Tape block size 0 bytes. Density code 0x25 (unknown). Soft error count since last status=0 General status bits on (8901): EOF EOD ONLINE IM_REP_EN but when i start afbackup the server always reports: mt: /dev/nst0: Input/output error but it dows increase the file nr and if i kill it (i know i never should but as i can't be shure the backup is written...) i see eg drive type = Generic SCSI-2 tape drive status = 620756992 sense key error = 0 residue count = 0 file number = 54 block number = 0 Tape block size 0 bytes. Density code 0x25 (unknown). Soft error count since last status=0 General status bits on (8901): EOF EOD ONLINE IM_REP_EN and mt -f /dev/nst0 rewind works as well. what problem could this be? before changing to the DDS 3 tape drive the DDS 2 drive worked fine. any ideas? You might want to try to isolate the problem a bit to see if the problem has to do with the backup software. A simple way to check this would be to use tar to write and subsequently read back a small backup. Something like: tar cvf /dev/st0 dir_you_want_to_backup should write the backup to the tape and: tar df /dev/st0 should read the tape and perform a diff with the files on disk. If everything is ok no output should be generated. Happy hacking, \Gandalf
Re: [OT] scsi tape problems
On Thu, Jun 28, 2001 at 10:14:54AM +0200, Lars Knudsen wrote: You might want to try to isolate the problem a bit to see if the problem has to do with the backup software. A simple way to check this would be to use tar to write and subsequently read back a small backup. Something like: tar cvf /dev/st0 dir_you_want_to_backup should write the backup to the tape and: tar df /dev/st0 should read the tape and perform a diff with the files on disk. If everything is ok no output should be generated. i can use tar to write backups to the tape, restore and diff doesn't report any differences. could this be some strange afbackup problem? i have afbackup running on 2 other machines with hp dds 2 tape drives and on this machine with sony sdt 9000 dds 3. how come it has that problems with that hp dds 3 drive? yours martin -- GnuPG 1024D/3E8DCCC0 30DC 1D28 1D79 32F5 5E67 3ABB 28EE B35A 3E8D CCC0 work: factline Krisper Fabro Harnoncourt OEG (www.factline.com)
Re: [OT] scsi tape problems
On Thu, 28 Jun 2001 11:35:55 +0200, =?iso-8859-1?Q?Martin_W=FCrtele?= writes: i can use tar to write backups to the tape, restore and diff doesn't report any differences. could this be some strange afbackup problem? i have afbackup running on 2 other machines with hp dds 2 tape drives and on this machine with sony sdt 9000 dds 3. how come it has that problems with that hp dds 3 drive? afbackup doesn´t only have troubles with dds3 drives, I never coould get it to cooperate with my HP C15533A DDS2 drive, also. IIRC the error was quite the same (can´t be sure, though, that´s almost 2 years ago). cheers, rw -- -- Fire and brimstone coming down from the skies! Rivers and seas boiling! -- Forty years of darkness, earthquakes, volcanos! The dead rising from the -- grave! Human sacrifice, dogs and cats living together... mass hysteria! -- - The Ghostbusters explain why not to buy or use any Microsoft products. pgp40kXOKjl4u.pgp Description: PGP signature
Re: [OT] scsi tape problems
On Thu, Jun 28, 2001 at 07:55:14PM +0200, Robert Waldner wrote: afbackup doesn´t only have troubles with dds3 drives, I never coould get it to cooperate with my HP C15533A DDS2 drive, also. IIRC the error was quite the same (can´t be sure, though, that´s almost 2 years ago). okay, so any suggestions for another backup software? taper from potato only supports tapes up to 4 gb :-( yours martin -- GnuPG 1024D/3E8DCCC0 30DC 1D28 1D79 32F5 5E67 3ABB 28EE B35A 3E8D CCC0 work: factline Krisper Fabro Harnoncourt OEG (www.factline.com) pgpes08AkEify.pgp Description: PGP signature
Re: [OT] scsi tape problems
On Thu, 28 Jun 2001 21:08:02 +0200, =?iso-8859-1?Q?Martin_W=FCrtele?= writes: On Thu, Jun 28, 2001 at 07:55:14PM +0200, Robert Waldner wrote: afbackup doesn=B4t only have troubles with dds3 drives, I never coould get it to cooperate with my HP C15533A DDS2 drive, also. IIRC the error was quite the same (can´t be sure, though, that´s almost 2 years ago). okay, so any suggestions for another backup software? taper from potato only supports tapes up to 4 gb :-( well, as I have only a DDS2-drive that´s not a problem for me ;-) but tar should be able to cope with larger tapes, although you may want to keep every volume just below 2 GB, so you can safely copy it to disk should the need arise (and it will, trust me). karsten m. self has a backup-script here: http://kmself.home.netcom.com/Linux/FAQs/backups.html and I did some tweaking, the result of which can be found at: http://gfrastsackl.org/scripts/ , to have it fit my needs. tar has some media-spanning - option, which you could use to keep the backup-files below 2 GB. cheers, rw -- -- AOL would be a giant diesel-smoking bus with hundreds -- of ebola victims on board throwing dead wombats and -- rotten cabbage at the other cars. -- ASR about Information Superhighway analogy pgpghauFJ4Tsr.pgp Description: PGP signature
Re: [OT] scsi tape problems
On Thu, Jun 28, 2001 at 09:25:40PM +0200, Robert Waldner wrote: okay, so any suggestions for another backup software? taper from potato only supports tapes up to 4 gb :-( well, as I have only a DDS2-drive that´s not a problem for me ;-) but tar should be able to cope with larger tapes, although you may want to keep every volume just below 2 GB, so you can safely copy it to disk should the need arise (and it will, trust me). karsten m. self has a backup-script here: http://kmself.home.netcom.com/Linux/FAQs/backups.html nice doku, and the script's fine as well and I did some tweaking, the result of which can be found at: http://gfrastsackl.org/scripts/ , to have it fit my needs. er, access forbidden. can you send me the script or change permissions please? tar has some media-spanning - option, which you could use to keep the backup-files below 2 GB. guess, i'll ether work my way through amanda or just use tar or cpio. thx martin -- GnuPG 1024D/3E8DCCC0 30DC 1D28 1D79 32F5 5E67 3ABB 28EE B35A 3E8D CCC0 work: factline Krisper Fabro Harnoncourt OEG (www.factline.com) pgpi39cX6Lb2Z.pgp Description: PGP signature
Re: [OT] scsi tape problems
Hi all I couldn't locate the following url http://gfrastsackl.org/scripts/ Is it correct? Tks regards Peter Robert Waldner wrote: On Thu, 28 Jun 2001 21:08:02 +0200, =?iso-8859-1?Q?Martin_W=FCrtele?= writes: On Thu, Jun 28, 2001 at 07:55:14PM +0200, Robert Waldner wrote: afbackup doesn=B4t only have troubles with dds3 drives, I never coould get it to cooperate with my HP C15533A DDS2 drive, also. IIRC the error was quite the same (can愒 be sure, though, that愀 almost 2 years ago). okay, so any suggestions for another backup software? taper from potato only supports tapes up to 4 gb :-( well, as I have only a DDS2-drive that愀 not a problem for me ;-) but tar should be able to cope with larger tapes, although you may want to keep every volume just below 2 GB, so you can safely copy it to disk should the need arise (and it will, trust me). karsten m. self has a backup-script here: http://kmself.home.netcom.com/Linux/FAQs/backups.html and I did some tweaking, the result of which can be found at: http://gfrastsackl.org/scripts/ , to have it fit my needs. tar has some media-spanning - option, which you could use to keep the backup-files below 2 GB. cheers, rw -- -- AOL would be a giant diesel-smoking bus with hundreds -- of ebola victims on board throwing dead wombats and -- rotten cabbage at the other cars. -- ASR about Information Superhighway analogy Part 1.2Type: application/pgp-signature
Re: [OT] scsi tape problems
On Thu, 28 Jun 2001 21:38:06 +0200, =?iso-8859-1?Q?Martin_W=FCrtele?= writes: On Thu, Jun 28, 2001 at 09:25:40PM +0200, Robert Waldner wrote: karsten m. self has a backup-script here: http://kmself.home.netcom.com/Linux/FAQs/backups.html nice doku, and the script's fine as well and I did some tweaking, the result of which can be found at: http://gfrastsackl.org/scripts/ , to have it fit my needs. er, access forbidden. can you send me the script or change permissions please? fsck. fixed. tar has some media-spanning - option, which you could use to keep the backup-files below 2 GB. guess, i'll ether work my way through amanda or just use tar or cpio. amanda uses ´dump´, so you may as well go directly there, unless you really need features like planned backups on multiple hosts and the like... cheers, rw -- -- Renting airplanes is like renting sex: It's difficult to arrange -- on short notice on Saturday, the fun things always cost more, and -- someone's always looking at their watch. - Paul Tomblin, asr pgpY1ecHrZtM0.pgp Description: PGP signature
Re: [OT] scsi tape problems
On Thu, 28 Jun 2001 16:30:00 EDT, Peter Kok writes: I couldn't locate the following url http://gfrastsackl.org/scripts/ Is it correct? It is, just a typo in the apache-config. cheers, rw -- -- This also tells they understand our language. They are just not -- willing to speak to us using it. Who knew they were French? -- Babylon 5 pgprwa0fBSGba.pgp Description: PGP signature
Re: Help Please With HP Travan Scsi Tape Drive
Hi All Thanks to Keith and Alexis for their emails and to all others who spent time considering my problem. I reseated the scsi cable connections and the problem resolved itself. This is what the output from the mt command should loo k like. # mt -f /dev/nst0 status drive type = Generic SCSI-2 tape drive status = 1157628416 sense key error = 0 residue count = 0 file number = 0 block number = 0 Tape block size 512 bytes. Density code 0x45 (unknown). Soft error count since last status=0 General status bits on (4101): BOT ONLINE IM_REP_EN # Stephen On Mon, May 07, 2001 at 05:08:27PM +0100, Stephen Broadbridge wrote: Hi All I cannot get my HP Travan T4000S Scsi tape drive to work. I have gathered all the information I can find about the problem into the rest of this email. Am I missing something obvious? Thanks in anticipation of any assistance given. Stephen Here is the version information for my system. $ uname -a Linux Cemy1 2.2.17 #1 Sun Jun 25 09:24:41 EST 2000 i586 unknown and for mt:- $ mt -V GNU mt version 2.4.2 This is what happens when I try to access my tape drive. I get the same sort of result when I try to access /dev/st0. # mt -f /dev/nst0 status mt: /dev/nst0: Input/output error This is here for comparison with the above only. # mt -f /dev/nst1 status mt: /dev/nst1: Device not configured This is evidence of the st.o module on my machine. The file is located at /lib/modules/2.2.17/scsi # file st.o st.o: ELF 32-bit LSB relocatable, Intel 80386, version 1, not stripped Here is a fragment of my /etc/modules file showing that st should load at boot time. # /etc/modules: kernel modules to load at boot time. # lines removed from here ne2k-pci st Here are the two lines from /var/log/messages which suggest to me that the tape drive has been detected:- May 3 15:12:56 cemy1 kernel: st: bufsize 32768, wrt 30720, max buffers 5, s/g segs 16. May 3 15:12:56 cemy1 kernel: Detected scsi tape st0 at scsi0, channel 0, id 6, lun 0 Here is the output from the command lsmod:- # lsmod | egrep st st 24264 0 Here is information from /var/log/messages about the booting of my SCSI bus:- May 3 15:12:56 cemy1 kernel: Vendor: HPModel: T4000s Rev: 1.06 May 3 15:12:56 cemy1 kernel: Type: Sequential-Access ANSI SCSI revision: 02 Here is the information provided about scsi modules by modprobe # modprobe -c | grep scsi path[scsi]=/lib/modules/2.2.17/scsi path[scsi]=/lib/modules/2.2/scsi path[scsi]=/lib/modules/default/scsi path[scsi]=/lib/modules/scsi alias scsi_hostadapter off -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Help Please With HP Travan Scsi Tape Drive
Stephen Broadbridge wrote: Hi All I cannot get my HP Travan T4000S Scsi tape drive to work. I have gathered all the information I can find about the problem into the rest of this email. Am I missing something obvious? Thanks in anticipation of any assistance given. This is what happens when I try to access my tape drive. I get the same sort of result when I try to access /dev/st0. # mt -f /dev/nst0 status mt: /dev/nst0: Input/output error I'd guess you really are having a hardware problem. Check SCSI ID, termination, etc. It could even be that the drive is bad. RANT alt=Sorry, I know this is unhelpful I'm starting to have a low opinion of these Travan SCSI drives. I have one, an AIWA, in a server that occasionally makes me reboot (starts getting above error) for no known reason, after fairly heavy-duty backup use for several weeks or so; and one at home, a Seagate, that now eventually write-fails on any tape I throw at it. I have purchased one more of these at Ebay, and if I have problems with it in the near future, I'll start using DAT for my backup needs, high drive cost or no. /RANT
Help Please With HP Travan Scsi Tape Drive
Hi All I cannot get my HP Travan T4000S Scsi tape drive to work. I have gathered all the information I can find about the problem into the rest of this email. Am I missing something obvious? Thanks in anticipation of any assistance given. Stephen Here is the version information for my system. $ uname -a Linux Cemy1 2.2.17 #1 Sun Jun 25 09:24:41 EST 2000 i586 unknown and for mt:- $ mt -V GNU mt version 2.4.2 This is what happens when I try to access my tape drive. I get the same sort of result when I try to access /dev/st0. # mt -f /dev/nst0 status mt: /dev/nst0: Input/output error This is here for comparison with the above only. # mt -f /dev/nst1 status mt: /dev/nst1: Device not configured This is evidence of the st.o module on my machine. The file is located at /lib/modules/2.2.17/scsi # file st.o st.o: ELF 32-bit LSB relocatable, Intel 80386, version 1, not stripped Here is a fragment of my /etc/modules file showing that st should load at boot time. # /etc/modules: kernel modules to load at boot time. # lines removed from here ne2k-pci st Here are the two lines from /var/log/messages which suggest to me that the tape drive has been detected:- May 3 15:12:56 cemy1 kernel: st: bufsize 32768, wrt 30720, max buffers 5, s/g segs 16. May 3 15:12:56 cemy1 kernel: Detected scsi tape st0 at scsi0, channel 0, id 6, lun 0 Here is the output from the command lsmod:- # lsmod | egrep st st 24264 0 Here is information from /var/log/messages about the booting of my SCSI bus:- May 3 15:12:56 cemy1 kernel: Vendor: HPModel: T4000s Rev: 1.06 May 3 15:12:56 cemy1 kernel: Type: Sequential-Access ANSI SCSI revision: 02 Here is the information provided about scsi modules by modprobe # modprobe -c | grep scsi path[scsi]=/lib/modules/2.2.17/scsi path[scsi]=/lib/modules/2.2/scsi path[scsi]=/lib/modules/default/scsi path[scsi]=/lib/modules/scsi alias scsi_hostadapter off
Devices for SCSI Tape Drives
Could some one tell me where to find descriptions of what the different device designations mean, especially the /dev/nst* and /dev/st* devices? Thanks, Vic Cain -- Prediction is very hard -- especially when it's about the future -- Yogi Berra The future will be better tomorrow - J. Danforth Quayle * Victor R. Cain email: [EMAIL PROTECTED] Ph: (865)483-6097 Fax: by prior arrangement, only
Re: Devices for SCSI Tape Drives
Pending further investigation, we now allege that Victor R. Cain wrote: Could some one tell me where to find descriptions of what the different device designations mean, especially the /dev/nst* and /dev/st* devices? /usr/src/linux/Documentation/devices.txt The /dev/nst* devices are the non-rewinding versions for the /dev/st* devices.
Re: Devices for SCSI Tape Drives
on Tue, Dec 19, 2000 at 11:14:45AM -0500, Andy Bastien ([EMAIL PROTECTED]) wrote: Pending further investigation, we now allege that Victor R. Cain wrote: Could some one tell me where to find descriptions of what the different device designations mean, especially the /dev/nst* and /dev/st* devices? /usr/src/linux/Documentation/devices.txt The /dev/nst* devices are the non-rewinding versions for the /dev/st* devices. Might add -- non-rewinding is generally more convenient to work with -- your tape doesn't reset itself after every command. -- Karsten M. Self kmself@ix.netcom.comhttp://kmself.home.netcom.com/ Evangelist, Zelerate, Inc. http://www.zelerate.org What part of Gestalt don't you understand? There is no K5 cabal http://gestalt-system.sourceforge.net/http://www.kuro5hin.org pgp5IM5vyEIS0.pgp Description: PGP signature
Re: SCSI Tape Drive on a HP NetServer E60
On Fri, 08 Dec 2000 04:12:08 Patrick Cheong Shu Yang wrote: I have just installed Linux onto a HP NetServer E60 which uses the Adaptec AIC7XXX. I am attempting to restore users data into /export/home from a tape but have been unable to. I have used the mt command to determine the status of the drive (/dev/st0, /dev/rst0 and nrst0) but to no avail. It keeps telling me the device is not present. When I do a ls -l /dev/*st* , I can see the devices. Can someone please help me? If more info is need mail me so that I can provide more details. Thx. Have you installed the SCSI tape support kernel module (or compiled it into the kernel)? Do other SCSI devices work? bye
Re: SCSI Tape Drive on a HP NetServer E60
On Fri, Dec 08, 2000 at 11:12:08AM +0800, Patrick Cheong Shu Yang wrote: Hi people, I have just installed Linux onto a HP NetServer E60 which uses the Adaptec AIC7XXX. I am attempting to restore users data into /export/home from a tape but have been unable to. I have used the mt command to determine the status of the drive (/dev/st0, /dev/rst0 and nrst0) but to no avail. It keeps telling me the device is not present. When I do a ls -l /dev/*st* , I can see the devices. Can someone please help me? If more info is need mail me so that I can provide more details. Thx. My apologies for the earlier mail (see above). It would seem that when we got the machine from HP, the SCSI tape drive power cable was attached but the data cable. SO the problem is now solved and I am using the st.o module to load the tape and perform backup. Again, my apologies. I should have checked that first before mailing the list. pgpQ3I6ExEeD6.pgp Description: PGP signature
SCSI Tape Drive on a HP NetServer E60
Hi people, I have just installed Linux onto a HP NetServer E60 which uses the Adaptec AIC7XXX. I am attempting to restore users data into /export/home from a tape but have been unable to. I have used the mt command to determine the status of the drive (/dev/st0, /dev/rst0 and nrst0) but to no avail. It keeps telling me the device is not present. When I do a ls -l /dev/*st* , I can see the devices. Can someone please help me? If more info is need mail me so that I can provide more details. Thx.
Re: SCSI tape errors
On Fri, Jul 14, 2000 at 01:34:13PM +1200, [EMAIL PROTECTED] wrote: Hi i have set up a SCSI DAT tape onto debian slink with kernel 2.0.38 and nfs (no_root_squash) mounted an IBM AIX directory. I use a simple backup program which tars the files from the AIX directory onto tape. It works for a little while but i think it gets into trouble when it trys to proccess a large file (200MB). I started the backup at 9:30pm and it started having problems by 11pm. Here is the error message : Jul 13 23:11:40 tapier kernel: ASC= 4 ASCQ= 1 Jul 13 23:11:40 tapier kernel: Raw sense data:0x70 0x00 0x02 0x00 0x00 0x00 0x00 0x0e 0x00 0x00 0x00 0x00 0x04 0x01 0x00 0x00 Jul 13 23:11:40 tapier kernel: st0: Error with sense data: extra data not valid Current error st09:00: sns = 70 2 Backup program errors are : tar: Read error on /dev/st0: Input/output error tar: Too many errors, quitting tar: Error is not recoverable: exiting now I tried doing a tar listing of the tape this morning and it said the the start record was unable to be read. Does anyone know what is going on... it is a simple proceedure i am doing and am frustrated and perplexed as to why i am having difficulties. I've used SCSI tape under Linux and other Unixes, but not scads. First thing I'd try though is cleaning the drive (use a cleaning tape), second would be trying a second media unit to see if maybe there was something wrong with the tape. Third, I'd find someone who knows more about tape processing and drivers than me to diagnose any remaining problems. -- Karsten M. Self kmself@ix.netcom.com http://www.netcom.com/~kmself Evangelist, Opensales, Inc.http://www.opensales.org What part of Gestalt don't you understand? Debian GNU/Linux rocks! http://gestalt-system.sourceforge.net/K5: http://www.kuro5hin.org GPG fingerprint: F932 8B25 5FDD 2528 D595 DC61 3847 889F 55F2 B9B0 pgpV8HfcGRd6B.pgp Description: PGP signature
Re: SCSI tape errors
On Fri, 14 Jul 2000 13:34:13 +1200, [EMAIL PROTECTED] wrote: i have set up a SCSI DAT tape onto debian slink with kernel 2.0.38 and nfs (no_root_squash) mounted an IBM AIX directory. I use a simple backup program which tars the files from the AIX directory onto tape. It works for a little while but i think it gets into trouble when it trys to proccess a large file (200MB). I started the backup at 9:30pm and it started having problems by 11pm. [...] tar: Read error on /dev/st0: Input/output error tar: Too many errors, quitting tar: Error is not recoverable: exiting now I tried doing a tar listing of the tape this morning and it said the the start record was unable to be read. Is the read/write head clean? Is the tape ok, or has it worn out? Is your SCSI bus clean (i.e. properly terminated, cable within max. length, etc.)? Is the drive ok? Too many questions, but you need to answer them before we can help. -- Sign the EU petition against SPAM: L I N U X .~. http://www.politik-digital.de/spam/The Choice /V\ of a GNU /( )\ Generation ^^-^^
SCSI tape errors
Hi i have set up a SCSI DAT tape onto debian slink with kernel 2.0.38 and nfs (no_root_squash) mounted an IBM AIX directory. I use a simple backup program which tars the files from the AIX directory onto tape. It works for a little while but i think it gets into trouble when it trys to proccess a large file (200MB). I started the backup at 9:30pm and it started having problems by 11pm. Here is the error message : Jul 13 23:11:40 tapier kernel: ASC= 4 ASCQ= 1 Jul 13 23:11:40 tapier kernel: Raw sense data:0x70 0x00 0x02 0x00 0x00 0x00 0x00 0x0e 0x00 0x00 0x00 0x00 0x04 0x01 0x00 0x00 Jul 13 23:11:40 tapier kernel: st0: Error with sense data: extra data not valid Current error st09:00: sns = 70 2 Backup program errors are : tar: Read error on /dev/st0: Input/output error tar: Too many errors, quitting tar: Error is not recoverable: exiting now I tried doing a tar listing of the tape this morning and it said the the start record was unable to be read. Does anyone know what is going on... it is a simple proceedure i am doing and am frustrated and perplexed as to why i am having difficulties. Thanx Zane
Re: scsi tape device
Ryan: I have a similar system. If in /dev/, you have no 'st?' devices, try making them with 'mknod /dev/st0 c 9 0' = 'mknod /dev/st7 c 9 7'. Check the man page for correct options... They should have root:tape ownership and be owner:group RW. Put any users that need acces in group 'tape' Dean Provins Calgary -- For some reason I do not have /dev/st* . I compiled my kernel with scsi tape support and I thought that would do it. Is there something that I am missing. Am I looking in the wrong spot for my tape device. I have a ICP raid card (GDT) which is fully functional and the kernel sees the tape drive Configuring GDT-PCI HA at 0/9 IRQ 3 scsi0 : GDT6518RD scsi : 1 host. Vendor: ICP Model: Host Drive #01 Rev: Type: Direct-Access ANSI SCSI revision: 02 Detected scsi disk sda at scsi0, channel 0, id 1, lun 0 Vendor: HPModel: C1537ARev: L708 Type: Sequential-Access ANSI SCSI revision: 02 Detected scsi tape st0 at scsi0, channel 2, id 3, lun 0 scsi : detected 1 SCSI tape 1 SCSI disk total. SCSI device sda: hdwr sector= 512 bytes. Sectors= 35551845 [17359 MB] [17.4 GB] but I am just lost as to how to access it in taper or kbackup. -Ryan -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null
Re: scsi tape device
Hi, * Mon, Jan 17, 2000 at 09:31:42AM -0700, Dean Allen Provins wrote: I have a similar system. If in /dev/, you have no 'st?' devices, try making them with 'mknod /dev/st0 c 9 0' = 'mknod /dev/st7 c 9 7'. Check the man page for correct options... They should have root:tape ownership and be owner:group RW. Put any users that need acces in group 'tape' ... or simply do: # cd /dev # MAKEDEV st0 That creates all the devices you'll need (st0, st0a, st0l, st0m, nst0, nst0a, nst0l, nst0m) with the correct ownership and permissions. -- David J. Mason [EMAIL PROTECTED]
scsi tape device
For some reason I do not have /dev/st* . I compiled my kernel with scsi tape support and I thought that would do it. Is there something that I am missing. Am I looking in the wrong spot for my tape device. I have a ICP raid card (GDT) which is fully functional and the kernel sees the tape drive Configuring GDT-PCI HA at 0/9 IRQ 3 scsi0 : GDT6518RD scsi : 1 host. Vendor: ICP Model: Host Drive #01 Rev: Type: Direct-Access ANSI SCSI revision: 02 Detected scsi disk sda at scsi0, channel 0, id 1, lun 0 Vendor: HPModel: C1537ARev: L708 Type: Sequential-Access ANSI SCSI revision: 02 Detected scsi tape st0 at scsi0, channel 2, id 3, lun 0 scsi : detected 1 SCSI tape 1 SCSI disk total. SCSI device sda: hdwr sector= 512 bytes. Sectors= 35551845 [17359 MB] [17.4 GB] but I am just lost as to how to access it in taper or kbackup. -Ryan
Re: scsi tape device
You can create the tape devices with `/dev/MAKEDEV', for example... Try `/dev/MAKEDEV -v st0' for creating `/dev/st0' and `/dev/nst0' Jozef Skvarcek _ Dept. of Physics and Astronomy | [EMAIL PROTECTED] Hunter College, City University of New York | 212-772-4032 On Sat, 15 Jan 2000, Ryan White wrote: For some reason I do not have /dev/st* . I compiled my kernel with scsi tape support and I thought that would do it. Is there something that I am missing. Am I looking in the wrong spot for my tape device. I have a ICP raid card (GDT) which is fully functional and the kernel sees the tape drive Configuring GDT-PCI HA at 0/9 IRQ 3 scsi0 : GDT6518RD scsi : 1 host. Vendor: ICP Model: Host Drive #01 Rev: Type: Direct-Access ANSI SCSI revision: 02 Detected scsi disk sda at scsi0, channel 0, id 1, lun 0 Vendor: HPModel: C1537ARev: L708 Type: Sequential-Access ANSI SCSI revision: 02 Detected scsi tape st0 at scsi0, channel 2, id 3, lun 0 scsi : detected 1 SCSI tape 1 SCSI disk total. SCSI device sda: hdwr sector= 512 bytes. Sectors= 35551845 [17359 MB] [17.4 GB] but I am just lost as to how to access it in taper or kbackup. -Ryan -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null
RE: Need SCSI Tape Help
Thanks, MAKEDEV did work but tape support was already in my custom (SMP) kernel. The machine that has all the proper devices without my intervention is running 2.0, so, I guess something is missing in the kernel build process. If I knew where to start, I'd go looking and post a fix. In any case, thanks for all the responses. They were *all* workable which a lot more than I can say for my $calls$ to Redmond :) -Original Message- From: Keith G. Murphy [mailto:[EMAIL PROTECTED] Sent: Friday, October 15, 1999 10:29 AM To: 'Debian List' Subject: Re: Need SCSI Tape Help Mike Barton wrote: Hi all! I'm using slink with an SMP kernel (2.0.36) on a dual Pentium Pro 200 with 256M RAM. The HD setup is a pair of 4 GB Seagate Barracudas on an Adaptec 2940UW along with an SCSI CDROM and a Tandberg 4222 tape drive. I've got a really sweet server here except that I just noticed there are no /dev/st* for the tape drive. Anyone know at what point during the installation these get created? I've got another machine here with an SCSI tape with lots of /dev/st*. I'd sure hate to mknod 'em all by hand on the new beast. Your kernel is configured for SCSI tape support, right? I don't think that's the default. Do a 'make menuconfig' and look for it. If it's there, I believe you can cd to '/dev' and do a MAKEDEV, and that will create all the proper devices for you automatically. Folks, isn't the kernel build process supposed to do this for you? I remember having to do this myself, for a SCSI tape also, I believe. I used make-kpkg, then installed the binary package.
Need SCSI Tape Help
Hi all! I'm using slink with an SMP kernel (2.0.36) on a dual Pentium Pro 200 with 256M RAM. The HD setup is a pair of 4 GB Seagate Barracudas on an Adaptec 2940UW along with an SCSI CDROM and a Tandberg 4222 tape drive. I've got a really sweet server here except that I just noticed there are no /dev/st* for the tape drive. Anyone know at what point during the installation these get created? I've got another machine here with an SCSI tape with lots of /dev/st*. I'd sure hate to mknod 'em all by hand on the new beast. Thanks
Re: Need SCSI Tape Help
Hi all! I'm using slink with an SMP kernel (2.0.36) on a dual Pentium Pro 200 with 256M RAM. The HD setup is a pair of 4 GB Seagate Barracudas on an Adaptec 2940UW along with an SCSI CDROM and a Tandberg 4222 tape drive. I've got a really sweet server here except that I just noticed there are no /dev/st* for the tape drive. Anyone know at what point during the installation these get created? I've got another machine here with an SCSI tape with lots of /dev/st*. I'd sure hate to mknod 'em all by hand on the new beast. Thanks For a single drive, you only need two: /dev/st0 (9,0) and /dev/nst0 (9,128). Dean
Re: Need SCSI Tape Help
Mike Barton wrote: Hi all! I'm using slink with an SMP kernel (2.0.36) on a dual Pentium Pro 200 with 256M RAM. The HD setup is a pair of 4 GB Seagate Barracudas on an Adaptec 2940UW along with an SCSI CDROM and a Tandberg 4222 tape drive. I've got a really sweet server here except that I just noticed there are no /dev/st* for the tape drive. Anyone know at what point during the installation these get created? I've got another machine here with an SCSI tape with lots of /dev/st*. I'd sure hate to mknod 'em all by hand on the new beast. Your kernel is configured for SCSI tape support, right? I don't think that's the default. Do a 'make menuconfig' and look for it. If it's there, I believe you can cd to '/dev' and do a MAKEDEV, and that will create all the proper devices for you automatically. Folks, isn't the kernel build process supposed to do this for you? I remember having to do this myself, for a SCSI tape also, I believe. I used make-kpkg, then installed the binary package.
Re: Need SCSI Tape Help
On Fri, Oct 15, 1999 at 09:28:34AM -0500, Keith G. Murphy wrote: Mike Barton wrote: Hi all! I'm using slink with an SMP kernel (2.0.36) on a dual Pentium Pro 200 with 256M RAM. The HD setup is a pair of 4 GB Seagate Barracudas on an Adaptec 2940UW along with an SCSI CDROM and a Tandberg 4222 tape drive. I've got a really sweet server here except that I just noticed there are no /dev/st* for the tape drive. Anyone know at what point during the installation these get created? I've got another machine here with an SCSI tape with lots of /dev/st*. I'd sure hate to mknod 'em all by hand on the new beast. Your kernel is configured for SCSI tape support, right? I don't think that's the default. Do a 'make menuconfig' and look for it. If it's there, I believe you can cd to '/dev' and do a MAKEDEV, and that will create all the proper devices for you automatically. Folks, isn't the kernel build process supposed to do this for you? I remember having to do this myself, for a SCSI tape also, I believe. I used make-kpkg, then installed the binary package. -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null I had to MAKEDEV for ST* and SG*, maybe we need to re-vist the install scripts? -- *--* Mail: [EMAIL PROTECTED] *--* Voice: 425.739.4247 *--* Fax: 425.827.9577 *--* HTTP://www.otak-k.com/~lawrence/ -- - - - - - - O t a k i n c . - - - - -
Re: SCSI Tape Drive
Pann McCuaig wrote: On Tue, Aug 31, 1999 at 07:34:44AM -0500, Anthony Landreneau wrote: Greetings, I have recently installed a SONY SCSI tape drive onto my linux box. I would like to use the Taper program to back up my hard drive to tape. But I seem to be having a problem with getting the tape drive to work. When I do a cat on /proc/scsi/scsi I get: Attached devices: Host: scsi1 Channel: 00 Id: 00 Lun: 00 Vendor: SONY Model: SDX-300C Rev: 0300 Type: Sequential-AccessANSI SCSI revision: 02 So the OS is seeing the hardware. However when I try to tar or write to /dev/st0 I get an error saying device not found. Any insight onto this matter would be very much appreciated. First step is to see if the device does indeed exist on your system. [cut] If it does not, them 'man MAKEDEV' to learn how to create it. And you need to have support for SCSI tape drives either compiled into your kernel or compiled as a module. Yes, just the other day I had to create this very device with MAKEDEV, after I had compiled and installed a new kernel (2.0.36) using make-kpkg. Is this a bug? (I linked the device into the kernel, i.e., non-modular).
Re: SCSI Tape Drive
On Tue, Aug 31, 1999 at 07:34:44AM -0500, Anthony Landreneau wrote: Greetings, I have recently installed a SONY SCSI tape drive onto my linux box. I would like to use the Taper program to back up my hard drive to tape. But I seem to be having a problem with getting the tape drive to work. When I do a cat on /proc/scsi/scsi I get: Attached devices: Host: scsi1 Channel: 00 Id: 00 Lun: 00 Vendor: SONY Model: SDX-300C Rev: 0300 Type: Sequential-AccessANSI SCSI revision: 02 So the OS is seeing the hardware. However when I try to tar or write to /dev/st0 I get an error saying device not found. Any insight onto this matter would be very much appreciated. First step is to see if the device does indeed exist on your system. $ ls -l /dev/st? crw-rw 1 root disk 9, 0 Mar 22 1998 /dev/st0 crw-rw 1 root disk 9, 1 Mar 22 1998 /dev/st1 crw-rw 1 root disk 9, 2 Mar 22 1998 /dev/st2 crw-rw 1 root disk 9, 3 Mar 22 1998 /dev/st3 crw-rw 1 root disk 9, 4 Mar 22 1998 /dev/st4 crw-rw 1 root disk 9, 5 Mar 22 1998 /dev/st5 crw-rw 1 root disk 9, 6 Mar 22 1998 /dev/st6 crw-rw 1 root disk 9, 7 Mar 22 1998 /dev/st7 If it does not, them 'man MAKEDEV' to learn how to create it. And you need to have support for SCSI tape drives either compiled into your kernel or compiled as a module. $ ls /lib/modules/2.0.36/scsi st.o Luck, Pann -- What's All the Buzz About Linux?L I N U X .~. The Choice /V\ http://www.ourmanpann.com/linux/ of a GNU /( )\ Generation ^^-^^
Re: SCSI Tape Drive
Subject: SCSI Tape Drive Date: Tue, Aug 31, 1999 at 07:34:44AM -0500 In reply to:Anthony Landreneau Quoting Anthony Landreneau([EMAIL PROTECTED]): Greetings, [snip] So the OS is seeing the hardware. However when I try to tar or write to /dev/st0 I get an error saying device not found. Any insight onto this matter would be very much appreciated. apropos tape man mt man st These should get you going. HTH -- The information went data way - ___ Wayne T. Topa [EMAIL PROTECTED]
SCSI Tape Drive
Greetings, I have recently installed a SONY SCSI tape drive onto my linux box. I would like to use the Taper program to back up my hard drive to tape. But I seem to be having a problem with getting the tape drive to work. When I do a cat on /proc/scsi/scsi I get: Attached devices: Host: scsi1 Channel: 00 Id: 00 Lun: 00 Vendor: SONY Model: SDX-300C Rev: 0300 Type: Sequential-AccessANSI SCSI revision: 02 So the OS is seeing the hardware. However when I try to tar or write to /dev/st0 I get an error saying device not found. Any insight onto this matter would be very much appreciated. Anthony
How do I mount SCSI Tape Drive?
I finally got my SCSI card to work (interrupt conflicts with network card!). Now I need to figure out how to mount the tape drive. proc gives me this: cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 02 Lun: 00 Vendor: CONNER Model: CTT8000-SRev: 1.17 Type: Sequential-AccessANSI SCSI revision: 02 How do I mount the tape drive? Thanks, Lance
SCSI Tape Problem Solved
Problem solved. Silly me, I loaded the Tape driver as a module. Once I loaded the module I found out the tape drive was in /dev/st0 Lance
Re: How do I mount SCSI Tape Drive?
On Sat, 21 Aug 1999, Lance Hoffmeyer wrote: I finally got my SCSI card to work (interrupt conflicts with network card!). Now I need to figure out how to mount the tape drive. proc gives me this: cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 02 Lun: 00 Vendor: CONNER Model: CTT8000-SRev: 1.17 Type: Sequential-AccessANSI SCSI revision: 02 How do I mount the tape drive? Lance Mounting: I don't think you can mount tape drives. I think mounting implies the existence of a file system. While there is formatting, there isn't a file system on the tape. I use afio to write my archive directly to the tape device. Disclaimer: I can speak only of my Conner 3080 drive, but the commands don't seem to have much to say about the specific drive, so should be the same for any scsi drives. With the Connor 3080 drive I had to use the command mt -f /dev/st0 erase to get reliable backups. For backups, many use tar, dump, and afio. Some will certainly provide you with favorite scripts. I don't know about dump, and I don't use tar for critical backups. As I understand the tar, tar concatenates the files then compresses the archive, (if you use compression). If you compress then lose any part of the archive due to tape damage, you lose archive from that point on. I understand that Gnu tar is better, but I do not know much about it and I have not used it for serious backups. Contrast this with afio which compresses before it concatenates to form the archive. If you lose a part of the archvie, the afio program will scan forward to find a 'magic number' that signals the start of the next valid file. All you lose is the damaged file. Before you start, please read the afio and mt (mag tape) manuals! Then experiment with backing up and restoring inconsequential files until you are certain you can rely on what you are doing. I usually do this without a script, bare-handed, and will describe how I do it. To do your backups with afio, you need a file list to drive afio: find path.to.directory.you.want.backed.upfile.list Edit file.list, eliminating file you don't want backed up, and perhaps prepare an include.list and/or exclude.list. The backup: cat file.list | afio -ovZ -w include.list -W exclude.list /dev/st0 The device, /dev/st0, will rewind the tape when the tape operation is through. If you want to put a second record at the end of this one, you will need to use the device /dev/nst0 that does not rewind at the end of the backup operation, or to scroll to the end of some number of backups with the mt command: mt -f /dev/nst0 fsf 1 to move the tape forward to the second backup (or use some larger number if you have several backups on the tape) before you run afio -ivZ /dev/nst0 which will leave your tape at the end of the record. mt -f /dev/nst0 rewind should rewind the tape. I write myself notes and keep them with the tapes reminding me how I made the backup and how to reinstall it. I reinstall with afio -ibvZ -w include.list -W exclude_List /dev/st0 where i = install, v= verbose, Z compresses with gzip. I encourage you to read the manual for mt, afio, and experiment with your tape drive. Then as I said earlier, experiment with backing up and restoring inconsequential files until you are certain you can rely on what you are doing. Then build and modify a rescue floppy or tomsrtbt-1.7.118/tomsrtbt-1.7.118.tar.gz (see metalab.unc.edu) to include the mt and afio commands. I acknowledge help many others have given me. Thanks! --David David Teague, [EMAIL PROTECTED] Debian GNU/Linux Because software support is free, timely, useful, technically accurate, and friendly. (I'm hoping this is all of the above!)
HP-T20 SCSI Tape
I've installed a HP-T20 into one of my linux machines and it doesn't seem to be working correctly. I can see in the /proc/scsi/scsi the following, which tells me that the drive is loaded: Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 00 Vendor: IBM Model: DDRS-39130D Rev: DC1B Type: Direct-AccessANSI SCSI revision: 02 Host: scsi0 Channel: 00 Id: 01 Lun: 00 Vendor: IBM Model: DDRS-39130D Rev: DC1B Type: Direct-AccessANSI SCSI revision: 02 Host: scsi0 Channel: 00 Id: 04 Lun: 00 Vendor: HP Model: T20 Rev: 3.01 Type: Sequential-AccessANSI SCSI revision: 02 And when I create the block devices by running: mknod -m 660 /dev/st0 c 9 0 mknod -m 660 /dev/st1 c 9 1 mknod -m 660 /dev/nst0 c 9 128 mknod -m 660 /dev/nst1 c 9 129 It comes back with no problems. But, when I run: # mt -f /dev/st0 status mt: /dev/st0: Operation not supported by device I've also tried st1 and nst1 and nst0. No luck. Or if I try to tar something to it, I get the same problem. Keep in mind that this drive was added after the OS was installed, but everything looks good. Kernel is 2.0.36 running on Debian 2.0. Any help would be greatly appreciated. Ryan C. Sumner Director of Technology LIS Consulting, LLC
Re: HP-T20 SCSI Tape
Hello Ryan, On 17-Aug-99, you wrote: RCS I've installed a HP-T20 into one of my linux machines and it RCS doesn't seem to be working correctly. RCS RCS I can see in the /proc/scsi/scsi the following, which tells me that RCS the drive is loaded: RCS RCS Attached devices: RCS Host: scsi0 Channel: 00 Id: 00 Lun: 00 RCS Vendor: IBM Model: DDRS-39130D Rev: DC1B RCS Type: Direct-AccessANSI SCSI revision: 02 RCS Host: scsi0 Channel: 00 Id: 01 Lun: 00 RCS Vendor: IBM Model: DDRS-39130D Rev: DC1B RCS Type: Direct-AccessANSI SCSI revision: 02 RCS Host: scsi0 Channel: 00 Id: 04 Lun: 00 RCS Vendor: HP Model: T20 Rev: 3.01 RCS Type: Sequential-AccessANSI SCSI revision: 02 RCS RCS And when I create the block devices by running: RCS RCS mknod -m 660 /dev/st0 c 9 0 RCS mknod -m 660 /dev/st1 c 9 1 RCS mknod -m 660 /dev/nst0 c 9 128 RCS mknod -m 660 /dev/nst1 c 9 129 RCS RCS RCS It comes back with no problems. But, when I run: RCS RCS # mt -f /dev/st0 status RCS mt: /dev/st0: Operation not supported by device RCS RCS I've also tried st1 and nst1 and nst0. No luck. RCS RCS Or if I try to tar something to it, I get the same problem. Keep in RCS mind that this drive was added after the OS was installed, but RCS everything looks good. Kernel is 2.0.36 running on Debian 2.0. RCS RCS Any help would be greatly appreciated. RCS RCS RCS Ryan C. Sumner RCS Director of Technology RCS LIS Consulting, LLC RCS RCS I've no direct experience of SCSI tapes on linux but I re-installed a couple of days ago (I'm a newbie trying to figure stuff out so it's a scratch system) and I'm sure I saw a module that could be included that was specifically for SCSI tapes. I've got the impression from other postings that it's, possible (and I would expect it to be so) to add these modules without needing to re-install. I haven't got that far yet so I can't help much further (assuming that this helps anyway). Regards, LeeE -- http://www.spatial.freeserve.co.uk
Where is my SCSI tape drive?
I would expect to see it at /dev/st0 or /dev/tape, but there are no such devices. I see the SCSI device during boot and the DAT drive is recognized. What am I missing?
Re: Where is my SCSI tape drive?
Might want to try making the device with MAKEDEV. Rob On Wed, 9 Jun 1999, David Hamilton wrote: I would expect to see it at /dev/st0 or /dev/tape, but there are no such devices. I see the SCSI device during boot and the DAT drive is recognized. What am I missing? -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null === [EMAIL PROTECTED] : Role-Player, Babylon 5 fanatic 1998-99 Aka Khyron the Backstabber : ICQ# 2325055 Homepage: www.cs.purdue.edu/homes/ratirh Happiness comes in short spurts. Don't be fooled. ===
Ejecting scsi tape
Is there a way to have my system automatically eject a tape from my scsi tape drive? I'm wanting to add this to my backup script, so I don't forget to change to tape and overwrite a backup. thanks
Re: Ejecting scsi tape
Chris Hoover [EMAIL PROTECTED] writes: | Is there a way to have my system automatically eject a tape from my scsi | tape drive? I'm wanting to add this to my backup script, so I don't | forget to change to tape and overwrite a backup. man mt Short answer: mt -f /dev/nst0 rewoff Gary
Re: scsi tape
David B. Teague [EMAIL PROTECTED] writes: There are adaptors that allow backward conpatibility all the way to SCSI I, I know I am using a SCSI II controller on a couple of SCSI devices, but when I moved from An Adaptec 1540A to eht 2840, I had to reformat all drives, and I was desperately hopoing that newer controllers were better behaved. Unfortunally they are not :-(. I recently moved a disk from a NCR810 to Adaptec 2940 and the different drive mapping mangled the partition tabel. Linux ran anyway, but i had to boot from diskette. Be shure to have a full backup! Greetings, Ramin
scsi tape
Hi Debian Users: The question is: can I use SCSI disk drives currently running with an Adaptec 2840 SCSI controller with Bus Logic controller? What about SCSI tapes: can a SCSI tape made on a tape drive with one controller be read with the same tape drive run with another (SCSI) controller? (Reason suggests the affirmative, but reason unfortunately does not always prevail.) Machine Details: Old machine: 486 16 MB Ram, 2840 SCSI controller, several SCSI drives and a 3080 tape for backup. The new machine has a K6-2 350; Mother Board: GBT Technology GA-5AX, INTEL Aladdin AGP chip set, 512K L2 cache, running at 100MHz; 128 MB RAM; 10G fast IDE; Mitsumi 32x FX series ide CD ROM; Yamaha ISA sound card; 8 MB AGP 3d video card (SiS 6326); and a 56kifxsp internal modem. By all guesses, it is a WIN modem. :( Anybody really know? I have another modem known not to be a WIN moedm :) I'll put Frozen on the new machine sometime this week. Questions restated: I need to move the data from the old machine to the new one. I'd like to be able to use the tape drive and some of the SCSI disks with a Bus Logic or other SCSI controller. Will I be able to use the disks unchanged on the machines with a Bus Logic SCSI controller? What about reading the tape drives? --David Teague [EMAIL PROTECTED] Debian GNU LINUX: Because the best technical support comes from those who help for the joy of helping. Thanks, guys! Because software should be expected _not_ to crash. Because reboots are for hardware upgrades and new kernels. Because one should not have one's options circumscribed by a large company.
Re: scsi tape
On Sun, Jan 31, 1999 at 11:23:26AM -0500, David B. Teague wrote: Hi Debian Users: The question is: can I use SCSI disk drives currently running with an Adaptec 2840 SCSI controller with Bus Logic controller? I'm not quite sure what you're asking here. There's not much point to having two controllers on a single SCSI chain... What about SCSI tapes: can a SCSI tape made on a tape drive with one controller be read with the same tape drive run with another (SCSI) controller? (Reason suggests the affirmative, but reason unfortunately does not always prevail.) Yes. Questions restated: I need to move the data from the old machine to the new one. I'd like to be able to use the tape drive and some of the SCSI disks with a Bus Logic or other SCSI controller. Will I be able to use the disks unchanged on the machines with a Bus Logic SCSI controller? What about reading the tape drives? You'll be able to use them provided that the new machine uses the same type of SCSI. If, for instance, then new machine is UW SCSI and the old one is Fast SCSI, you'll need an adaptor device to hook up the old device (unless your card also has a Fast SCSI connector).
Re: scsi tape
On Sun, 31 Jan 1999, John Goerzen wrote: On Sun, Jan 31, 1999 at 11:23:26AM -0500, David B. Teague wrote: Questions restated: I need to move the data from the old machine to the new one. I'd like to be able to use the tape drive and some of the SCSI disks with a Bus Logic or other SCSI controller. Will I be able to use the disks unchanged on the machines with a Bus Logic SCSI controller? What about reading the tape drives? You'll be able to use them provided that the new machine uses the same type of SCSI. If, for instance, then new machine is UW SCSI and the old one is Fast SCSI, you'll need an adaptor device to hook up the old device (unless your card also has a Fast SCSI connector). There are adaptors that allow backward conpatibility all the way to SCSI I, I know I am using a SCSI II controller on a couple of SCSI devices, but when I moved from An Adaptec 1540A to eht 2840, I had to reformat all drives, and I was desperately hopoing that newer controllers were better behaved. David
scsi tape problems
Hi all, My scsi tape has been giving me problems lately and I wonder if anyone can shed some light on what to look for. When I do my backups it has been failing with the following message after it has done part of the backup. The logs say the following: Jan 13 11:47:57 brian kernel: st0: Error with sense data: extra data not valid Current error st09:00: sns = 70 3 Jan 13 11:47:57 brian kernel: ASC=f0 ASCQ=2b Jan 13 11:47:57 brian kernel: Raw sense data:0x70 0x00 0x03 0x00 0x00 0x00 0x00 0x0a 0x00 0x00 0x00 0x00 0xf0 0x2b 0x00 0x00 Jan 13 11:47:57 brian kernel: st0: Error with sense data: extra data not valid Current error st09:00: sns = 70 3 Jan 13 11:47:57 brian kernel: ASC=f0 ASCQ=2b Jan 13 11:47:57 brian kernel: Raw sense data:0x70 0x00 0x03 0x00 0x00 0x00 0x00 0x0a 0x00 0x00 0x00 0x00 0xf0 0x2b 0x00 0x00 Jan 13 11:47:57 brian kernel: st0: Error with sense data: extra data not valid Current error st09:00: sns = 70 3 Jan 13 11:47:57 brian kernel: ASC=f0 ASCQ=2b Jan 13 11:47:57 brian kernel: Raw sense data:0x70 0x00 0x03 0x00 0x00 0x00 0x00 0x0a 0x00 0x00 0x00 0x00 0xf0 0x2b 0x00 0x00 And then then tar reports: tar (grandchild): Cannot write to /dev/st0: Input/output error tar (grandchild): Error is not recoverable: exiting now If I try to do anything with the tape it gives an Input/output error. If I remove and reinsert the tape it will work for a while and then repeat the above errors. The setup from dmesg is: scsi0 : Tekram DC390(T) V1.11 Feb-05-1997 scsi : 1 host. Vendor: Seagate Model: STT8000N Rev: 3.12 Type: Sequential-Access ANSI SCSI revision: 02 Detected scsi tape st0 at scsi0, channel 0, id 4, lun 0 scsi : detected 1 SCSI tape total. The drive uses TR-4 cartridges. Thanks for any input, -- Brian - Never criticize anybody until you have walked a mile in their shoes, because by that time you will be a mile away and have their shoes. - unknown Mechanical Engineering[EMAIL PROTECTED] Purdue University http://www.ecn.purdue.edu/~servis -
scsi tape problems (resent)
(I am resending this since I did not see it on the list, if it is a repeat sorry) Hi all, My scsi tape has been giving me problems lately and I wonder if anyone can shed some light on what to look for. When I do my backups it has been failing with the following message after it has done part of the backup. The logs say the following: Jan 13 11:47:57 brian kernel: st0: Error with sense data: extra data not valid Current error st09:00: sns = 70 3 Jan 13 11:47:57 brian kernel: ASC=f0 ASCQ=2b Jan 13 11:47:57 brian kernel: Raw sense data:0x70 0x00 0x03 0x00 0x00 0x00 0x00 0x0a 0x00 0x00 0x00 0x00 0xf0 0x2b 0x00 0x00 Jan 13 11:47:57 brian kernel: st0: Error with sense data: extra data not valid Current error st09:00: sns = 70 3 Jan 13 11:47:57 brian kernel: ASC=f0 ASCQ=2b Jan 13 11:47:57 brian kernel: Raw sense data:0x70 0x00 0x03 0x00 0x00 0x00 0x00 0x0a 0x00 0x00 0x00 0x00 0xf0 0x2b 0x00 0x00 Jan 13 11:47:57 brian kernel: st0: Error with sense data: extra data not valid Current error st09:00: sns = 70 3 Jan 13 11:47:57 brian kernel: ASC=f0 ASCQ=2b Jan 13 11:47:57 brian kernel: Raw sense data:0x70 0x00 0x03 0x00 0x00 0x00 0x00 0x0a 0x00 0x00 0x00 0x00 0xf0 0x2b 0x00 0x00 And then then tar reports: tar (grandchild): Cannot write to /dev/st0: Input/output error tar (grandchild): Error is not recoverable: exiting now If I try to do anything with the tape it gives an Input/output error. If I remove and reinsert the tape it will work for a while and then repeat the above errors. The setup from dmesg is: scsi0 : Tekram DC390(T) V1.11 Feb-05-1997 scsi : 1 host. Vendor: Seagate Model: STT8000N Rev: 3.12 Type: Sequential-Access ANSI SCSI revision: 02 Detected scsi tape st0 at scsi0, channel 0, id 4, lun 0 scsi : detected 1 SCSI tape total. The drive uses TR-4 cartridges. Thanks for any input, -- Brian - Never criticize anybody until you have walked a mile in their shoes, because by that time you will be a mile away and have their shoes. - unknown Mechanical Engineering[EMAIL PROTECTED] Purdue University http://www.ecn.purdue.edu/~servis -
Re: Backups seem to take too long(scsi tape)
On: Wed, 4 Nov 1998 12:29:57 -0500 (EST) servis writes: Hi all, I have a Seagate Tapestore 8G on a scsi-2 controller. When I back up my drives(ext2, vfat) and some smbfs mounted drives(over a 10-T) it seems to take too long. I am just using tar whith compression. Here are the stats from tar: Total bytes written: 5752760320 (5.8 Gb) (contained in 130541 files/dir) Elapsed time: 05:14:882, 18882 sec Throughput per second: 298Kb/sec Is this expected? The tape says that it should get between 600Kb/sec and 1000Kb/sec depending on compression ratio. What can I do to speed this up? Use tar without compression and let your tape use its hardware compression. Software compression is usually quite slow,[1] on my computer slower than the tape speed. Torsten BTW: With hardware compression enabled I get about 700 KB/s with a DDS2-DAT tape on a DDS1 tape (2GB uncompressed capacity). Footnotes: [1] about 500 KB/s using gzip -9 on a Pentium 133 CPU.
Backups seem to take too long(scsi tape)
Hi all, I have a Seagate Tapestore 8G on a scsi-2 controller. When I back up my drives(ext2, vfat) and some smbfs mounted drives(over a 10-T) it seems to take too long. I am just using tar whith compression. Here are the stats from tar: Total bytes written: 5752760320 (5.8 Gb) (contained in 130541 files/dir) Elapsed time: 05:14:882, 18882 sec Throughput per second: 298Kb/sec Is this expected? The tape says that it should get between 600Kb/sec and 1000Kb/sec depending on compression ratio. What can I do to speed this up? Thanks, -- Brian - Never criticize anybody until you have walked a mile in their shoes, because by that time you will be a mile away and have their shoes. - unknown Mechanical Engineering [EMAIL PROTECTED] Purdue University http://www.ecn.purdue.edu/~servis -
How to access SCSI-tape and Aiee: scheduling in interrupt 00125dd9
As the subject says I have two problems. 1: I have Linux running on a ACER, with and Advansys SCSI card installed. Now I want to connect a tape station and get access to it - how do I do it?. This I get when I boot: Sep 16 14:00:38 beluga kernel: Failed initialization of WD-7000 SCSI card! Sep 16 14:00:38 beluga kernel: ppa: Version 1.42 Sep 16 14:00:38 beluga kernel: ppa: Probing port 03bc Sep 16 14:00:38 beluga kernel: ppa: Probing port 0378 Sep 16 14:00:38 beluga kernel: ppa: SPP port present Sep 16 14:00:38 beluga kernel: ppa: ECP with a 16 byte FIFO present Sep 16 14:00:38 beluga kernel: ppa: Failed Intel bug check. (Phony EPP in ECP) Sep 16 14:00:38 beluga kernel: ppa: Probing port 0278 Sep 16 14:00:38 beluga kernel: scsi0 : AdvanSys SCSI 3.1E: PCI Ultra 16 CDB: IO 7000/F, I RQ 11 Sep 16 14:00:38 beluga kernel: scsi : 1 host. Sep 16 14:00:38 beluga kernel: scsi : detected total. 2: Just installed two new Siemens-Nixdorff.with a Millinium II AGP graphics card two disks and a Adaptec 2940 SCSI controller. The installation went smoothly and so did the first half hour or so, but then both machines went down with this message: Aiee: scheduling in interrupt 00125dd9 To get them up again I had to turn the power off and on. Does anybody know what this can be? Yours Karsten Bolding -- ** Karsten Bolding, CEC - Joint Research Centre, ISPRA Direct: +39 (0)332 789314 Space Applications Institute Sec. +39 (0)332 789177 Marine Environment Unit, TP690 FAX: +39 (0)332 789034 I-21020 Ispra(VA) - Italy E-mail: [EMAIL PROTECTED] **
Off-topic:non-scsi tape backup?
Sorry if this is off-topic, it's just that this list has proven to be so helpful in many areas. Please suggest any alternate news groups that may be better for this question. I've not been receiving the debian-users digest list lately and am reposting this in part to test if this bounces, and to reissue the question. I'd like to get my tape backup working under Linux. I have a connor QIC-3020 Travan tape system. This drive has a separate controler which is connected to an ISA slot. It uses the same IRQ (6) as the floppy and the same DMA channel (2). I believe this is a tape drive which could connect directly to the floppy controler, but I never could get it working that way. My questions are: Is anyone familiar with this type of tape backup system, and has gotten it working under Linux? DoI need the interface card or is it better to run it directly from the floppy controler? I'm not interested in performance (speed) since I'll do backups lat at night. Is this an ftape issue and if so, how do I proceed to configure? Thanx in advance for any help. Regards, Ed Young
Re: scsi tape devices?
On Tue, 26 May 1998 [EMAIL PROTECTED] wrote: Can someone tell me what the *a, *l, and *m devices are/do for for my scsi tape drive? The Linux Device List was not very enlighting. 0 crw-rw 1 root disk 9, 128 May 28 1997 /dev/nst0 0 crw-rw 1 root disk 9, 224 May 28 1997 /dev/nst0a 0 crw-rw 1 root disk 9, 160 May 28 1997 /dev/nst0l 0 crw-rw 1 root disk 9, 192 May 28 1997 /dev/nst0m 0 crw-rw 1 root disk 9, 0 May 28 1997 /dev/st0 0 crw-rw 1 root disk 9, 96 May 28 1997 /dev/st0a 0 crw-rw 1 root disk 9, 32 May 28 1997 /dev/st0l 0 crw-rw 1 root disk 9, 64 May 28 1997 /dev/st0m Thanks, Brian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] I think these are for devices with multiple recording density. I have not experience with these devices under LINUX, but under ULTRIX they are used to select the recording density on QIC tape : l = low, m : medium, h : high. || | Jean-Luc ANTHOINE [EMAIL PROTECTED]| | I.U.T. de Belfort, Departement Informatique, BP 527, F-90016 BELFORT CEDEX | | Phone : (33) 03 84 58 77 76 Fax : (33) 03 84 58 77 81| || -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
scsi tape devices?
Can someone tell me what the *a, *l, and *m devices are/do for for my scsi tape drive? The Linux Device List was not very enlighting. 0 crw-rw 1 root disk 9, 128 May 28 1997 /dev/nst0 0 crw-rw 1 root disk 9, 224 May 28 1997 /dev/nst0a 0 crw-rw 1 root disk 9, 160 May 28 1997 /dev/nst0l 0 crw-rw 1 root disk 9, 192 May 28 1997 /dev/nst0m 0 crw-rw 1 root disk 9, 0 May 28 1997 /dev/st0 0 crw-rw 1 root disk 9, 96 May 28 1997 /dev/st0a 0 crw-rw 1 root disk 9, 32 May 28 1997 /dev/st0l 0 crw-rw 1 root disk 9, 64 May 28 1997 /dev/st0m Thanks, Brian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: SCSI tape problems
(A copy of this message has also been posted to the following newsgroups: linux.debian.user) Can't anyone please offer some assistance... I'd really like to get SCSI working... Thanks again In article [EMAIL PROTECTED], [EMAIL PROTECTED] (Glenn Tenney KOTJ) wrote: Well, I spent the evening getting the Adaptec AVA-1505 card working. I finally got it so that the system now boots and sees the card. This card is supposed to be supported by the AHA152x support. Here are the kern.log messages now (heads of each line clipped for breavity) from when I just rebooted. I have one 1/4 inch Teac tape drive on ID 1 (with a tape in it): kernel: aha152x: BIOS test: passed, detected 1 controller(s) kernel: aha152x0: vital data: PORTBASE=0x340, IRQ=11, SCSI ID=7, reconnect=enabled, parity=enabled, synchronous=disabled, delay=100, extended translation=disabled kernel: aha152x: trying software interrupt, lost. kernel: aha152x: IRQ 11 possibly wrong. Please verify. kernel: scsi1 : Adaptec 152x SCSI driver; $Revision: 1.18 $ kernel: scsi : 1 host. kernel: scsi : aborting command due to timeout : pid 0, scsi1, channel 0, id 0, lun 0 Test Unit Ready 00 00 00 00 00 kernel: scsi : aborting command due to timeout : pid 0, scsi1, channel 0, id 0, lun 0 Test Unit Ready 00 00 00 00 00 kernel: scsi : aborting command due to timeout : pid 1, scsi1, channel 0, id 1, lun 0 Test Unit Ready 00 00 00 00 00 kernel: scsi : aborting command due to timeout : pid 1, scsi1, channel 0, id 1, lun 0 Test Unit Ready 00 00 00 00 00 ... and so on through id 7 The problems I have now (for which I'd appreciate some ideas) are: 1. What can I do about the IRQ being possibly wrong? 2. It doesn't seem to find the tape drive... I really want to use it for backups, so what can I do? The last time I had the drive turned on it was on a Mac and worked aok; the last time I used the cable, it too worked ok. Thanks for any help... suggestions... pointers... And, yes, I have read the SCSI how-to's... -- Glenn Tenney KOTJ The email address has been changed since spam is not allowed here, but you can figure it out... -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: SCSI tape problems
On Sun, 5 Apr 1998, Glenn Tenney KOTJ wrote: : (A copy of this message has also been posted to the following newsgroups: : linux.debian.user) : : Can't anyone please offer some assistance... I'd really like to get SCSI : working... : : Thanks again : : : In article [EMAIL PROTECTED], : [EMAIL PROTECTED] (Glenn Tenney KOTJ) wrote: : Well, I spent the evening getting the Adaptec AVA-1505 card working. I : finally got it so that the system now boots and sees the card. This card : is supposed to be supported by the AHA152x support. : : Here are the kern.log messages now (heads of each line clipped for : breavity) from when I just rebooted. I have one 1/4 inch Teac tape drive : on ID 1 (with a tape in it): : : kernel: aha152x: BIOS test: passed, detected 1 controller(s) : kernel: aha152x0: vital data: PORTBASE=0x340, IRQ=11, SCSI ID=7, : reconnect=enabled, parity=enabled, synchronous=disabled, delay=100, : extended translation=disabled : kernel: aha152x: trying software interrupt, lost. : kernel: aha152x: IRQ 11 possibly wrong. Please verify. : kernel: scsi1 : Adaptec 152x SCSI driver; $Revision: 1.18 $ : kernel: scsi : 1 host. : kernel: scsi : aborting command due to timeout : pid 0, scsi1, channel 0, : id 0, lun 0 Test Unit Ready 00 00 00 00 00 : kernel: scsi : aborting command due to timeout : pid 0, scsi1, channel 0, : id 0, lun 0 Test Unit Ready 00 00 00 00 00 : kernel: scsi : aborting command due to timeout : pid 1, scsi1, channel 0, : id 1, lun 0 Test Unit Ready 00 00 00 00 00 : kernel: scsi : aborting command due to timeout : pid 1, scsi1, channel 0, : id 1, lun 0 Test Unit Ready 00 00 00 00 00 : ... and so on through id 7 : : The problems I have now (for which I'd appreciate some ideas) are: : : 1. What can I do about the IRQ being possibly wrong? : : 2. It doesn't seem to find the tape drive... I really want to use it for : backups, so what can I do? The last time I had the drive turned on it : was on a Mac and worked aok; the last time I used the cable, it too worked : ok. : : Thanks for any help... suggestions... pointers... And, yes, I have read : the SCSI how-to's... Well, I just fought with an Adaptec 1510A today, so let's see what we can come up with. First, are you passing parameters to the kernel? If so, what are they? The aha152x driver assumes that the Adaptec cards are at 0x340, since that's the factory default. Since my 1510 has no BIOS at all it's not autodetected. I did a WAG and wrote aha152x=0x340 at the boot prompt. I got the same results you did. However, after I RTFM the Adaptec install docs (http://www.adaptec.com), I found that my HBA had been set to 0x140, IRQ 11. Passing aha152x=0x140,11 solved the problem. If you have more than one HBA, you may need to alter the order in which the kernel recognizes them. This is mentioned in the HOWTO, but briefly one must edit the struct builtin_scsi_hosts[] in file drivers/scsi/hosts.c Finally, your HBA may be conflicting with another card. Again, the Adaptec doc can help you here ... removing other cards is sometimes helpful. -- Nathan Norman MidcoNet - 410 South Phillips Avenue - Sioux Falls, SD 57104 mailto://[EMAIL PROTECTED] http://www.midco.net finger [EMAIL PROTECTED] for PGP Key: (0xA33B86E9) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: SCSI tape problems
I have an AVA-1505 working properly. Dumb question, but do you have the IRQ on the card set to what you are having LILO pass to the kernel? That could be the reason for the error message you're getting. Matt On Sun, 5 Apr 1998, Glenn Tenney KOTJ wrote: (A copy of this message has also been posted to the following newsgroups: linux.debian.user) Can't anyone please offer some assistance... I'd really like to get SCSI working... Thanks again In article [EMAIL PROTECTED], [EMAIL PROTECTED] (Glenn Tenney KOTJ) wrote: Well, I spent the evening getting the Adaptec AVA-1505 card working. I finally got it so that the system now boots and sees the card. This card is supposed to be supported by the AHA152x support. Here are the kern.log messages now (heads of each line clipped for breavity) from when I just rebooted. I have one 1/4 inch Teac tape drive on ID 1 (with a tape in it): kernel: aha152x: BIOS test: passed, detected 1 controller(s) kernel: aha152x0: vital data: PORTBASE=0x340, IRQ=11, SCSI ID=7, reconnect=enabled, parity=enabled, synchronous=disabled, delay=100, extended translation=disabled kernel: aha152x: trying software interrupt, lost. kernel: aha152x: IRQ 11 possibly wrong. Please verify. kernel: scsi1 : Adaptec 152x SCSI driver; $Revision: 1.18 $ kernel: scsi : 1 host. kernel: scsi : aborting command due to timeout : pid 0, scsi1, channel 0, id 0, lun 0 Test Unit Ready 00 00 00 00 00 kernel: scsi : aborting command due to timeout : pid 0, scsi1, channel 0, id 0, lun 0 Test Unit Ready 00 00 00 00 00 kernel: scsi : aborting command due to timeout : pid 1, scsi1, channel 0, id 1, lun 0 Test Unit Ready 00 00 00 00 00 kernel: scsi : aborting command due to timeout : pid 1, scsi1, channel 0, id 1, lun 0 Test Unit Ready 00 00 00 00 00 ... and so on through id 7 The problems I have now (for which I'd appreciate some ideas) are: 1. What can I do about the IRQ being possibly wrong? 2. It doesn't seem to find the tape drive... I really want to use it for backups, so what can I do? The last time I had the drive turned on it was on a Mac and worked aok; the last time I used the cable, it too worked ok. Thanks for any help... suggestions... pointers... And, yes, I have read the SCSI how-to's... -- Glenn Tenney KOTJ The email address has been changed since spam is not allowed here, but you can figure it out... -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
SCSI tape problems
Well, I spent the evening getting the Adaptec AVA-1505 card working. I finally got it so that the system now boots and sees the card. This card is supposed to be supported by the AHA152x support. Here are the kern.log messages now (heads of each line clipped for breavity) from when I just rebooted. I have one 1/4 inch Teac tape drive on ID 1 (with a tape in it): kernel: aha152x: BIOS test: passed, detected 1 controller(s) kernel: aha152x0: vital data: PORTBASE=0x340, IRQ=11, SCSI ID=7, reconnect=enabled, parity=enabled, synchronous=disabled, delay=100, extended translation=disabled kernel: aha152x: trying software interrupt, lost. kernel: aha152x: IRQ 11 possibly wrong. Please verify. kernel: scsi1 : Adaptec 152x SCSI driver; $Revision: 1.18 $ kernel: scsi : 1 host. kernel: scsi : aborting command due to timeout : pid 0, scsi1, channel 0, id 0, lun 0 Test Unit Ready 00 00 00 00 00 kernel: scsi : aborting command due to timeout : pid 0, scsi1, channel 0, id 0, lun 0 Test Unit Ready 00 00 00 00 00 kernel: scsi : aborting command due to timeout : pid 1, scsi1, channel 0, id 1, lun 0 Test Unit Ready 00 00 00 00 00 kernel: scsi : aborting command due to timeout : pid 1, scsi1, channel 0, id 1, lun 0 Test Unit Ready 00 00 00 00 00 ... and so on through id 7 The problems I have now (for which I'd appreciate some ideas) are: 1. What can I do about the IRQ being possibly wrong? 2. It doesn't seem to find the tape drive... I really want to use it for backups, so what can I do? The last time I had the drive turned on it was on a Mac and worked aok; the last time I used the cable, it too worked ok. Thanks for any help... suggestions... pointers... And, yes, I have read the SCSI how-to's... -- Glenn Tenney KOTJ The email address has been changed since spam is not allowed here, but you can figure it out... -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
scsi: tape drive gets ONE partition's signals, load reaches 17.
For four months, I noticed no problems with my tape drive or my disk drive. In the last two weeks, I have updated a few packages in hamm, but not many. I now have two indicators that just one partition (out of 8+ partitions) on my disk drive gets its signals diverted to the tape drive. 1. mke2fs -c /dev/sdc12 results in a churning of the tape /dev/st0 for 30 minutes until I kill the process. Then I have difficulty typing a character as the load meter shows 17 horizontal lines. 2. When making backups, only the partition /dev/sdc12 fails. If I duplicate its contents to another partition, dump succeeds. Again, dumping to this /dev/sdc12 partition churns the tape drive for at least 30 minutes until I kill the dump command. The above disk drive is a wide 9GB Fujitsu. The above tape drive is an old Exabyte 8200 8mm. I have two other narrow 2GB Seagate drives externally attached. All these scsi devices are attached to an Adaptec 2940UW adapter. Because of this mixing of scsi signals between one disk drive partition and the tape drive, I no longer use the partition /dev/sdc12. The setup of my Adaptec 2940UW refuses any ultra scsi protocol, preventing an ultra problem. This cross-signal problem seems inexplicable. Has anyone any explanations/solutions? -- Jim Burt, NJ9L, Fairfax, Virginia, USA [EMAIL PROTECTED] http://www.mnsinc.com/jameson [EMAIL PROTECTED] It is not the shortcomings of others, nor what others have done or not done that one should think about, but what one has done or not done oneself. --Dhammapada [dp command for quotes from the Dhammapada, in Linux] -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
problem using SCSI tape devices
I have just switched from RedHat 4.2 (gee, it seems I preface all my mail to this list with that...grin) and am having a problem accessing my tape drive (a Conner DDS-2 SCSI drive) The drive responds to the mt commands I have issued (ie, mt tell, mt datcompression, mt rewind, etc) but I have been unable to either restore any of the backups I already had on tape before the switch or write to tape (using tar). The console locks up and I cannot free it by switching to another VT and killing the process. Here are some more details: $TAPE = /dev/tape which is a symlink to /dev/nst0 BTW, what are those other devices -- nst0a, nst0l, nst0m, etc? I am using kernel 2.0.32 with support for generic SCSI, Buslogic SCSI adapters, SCSI tapes, SCSI disks I was using the command tar -xv * to restore a complete archive to the current directory Any help would be greatly appreciated... Thanks! Tim -- ## # # # # # # ## ## # # # # # Debian GNU Linux ## # # # # # # ## # ## # # # # Power to the people... # # # ## # # E-Mail: Tim Ferrell [EMAIL PROTECTED] -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: dev for SCSI tape
Lawrence wrote:
Oliver Elphick wrote:
Lawrence wrote:
What is the likely device name in the /dev directory for a SCSI tape
drive? is it /dev/tape? Anyone using the Seagate Travan SCSI backup?
SCSI tape drives are:
crw-rw-rw- 2 root root 9, 0 Feb 19 1997 /dev/st0
crw-rw-rw- 1 root root 9, 96 Feb 19 1997 /dev/st0a
crw-rw-rw- 1 root root 9, 32 Feb 19 1997 /dev/st0l
crw-rw-rw- 1 root root 9, 64 Feb 19 1997 /dev/st0m
If you have more than one you can create /dev/st1 and so on
The SCSI tapes are assigned to st[0-9] in the order that they are recognis
ed
at boot time.
What is the meaning of suffix {a,l,m}?
From /usr/src/linux/Documentation/device.txt:
9 charSCSI tape devices
0 = /dev/st0 First SCSI tape, mode 0
1 = /dev/st1 Second SCSI tape, mode 0
...
32 = /dev/st0l First SCSI tape, mode 1
33 = /dev/st1l Second SCSI tape, mode 1
...
64 = /dev/st0m First SCSI tape, mode 2
65 = /dev/st1m Second SCSI tape, mode 2
...
96 = /dev/st0a First SCSI tape, mode 3
97 = /dev/st1a Second SCSI tape, mode 3
...
128 = /dev/nst0 First SCSI tape, mode 0, no rewind
129 = /dev/nst1 Second SCSI tape, mode 0, no rewind
...
160 = /dev/nst0lFirst SCSI tape, mode 1, no rewind
161 = /dev/nst1lSecond SCSI tape, mode 1, no rewind
...
192 = /dev/nst0mFirst SCSI tape, mode 2, no rewind
193 = /dev/nst1mSecond SCSI tape, mode 2, no rewind
...
224 = /dev/nst0aFirst SCSI tape, mode 3, no rewind
225 = /dev/nst1aSecond SCSI tape, mode 3, no rewind
...
No rewind refers to the omission of the default
automatic rewind on device close. The MTREW or MTOFFL
ioctl()'s can be used to rewind the tape regardless of
the device used to access it.
I can't find any documentation that explains (comprehensibly) what the
modes are. I believe that l = low density and m = medium density; I have
no idea what a is. It may be that the tape hardware may not support
the use of these other modes. I have not tried to use any but the
default (minor number = {0,128}) with my DDS drive.
--
Oliver Elphick[EMAIL PROTECTED]
Isle of Wight http://www.lfix.co.uk/oliver
PGP key from public servers; key ID 32B8FAA1
Unsolicited email advertisements are not welcome; any person sending
such will be invoiced for telephone time used in downloading together
with a £25 administration charge.
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to
[EMAIL PROTECTED] .
Trouble? e-mail to [EMAIL PROTECTED] .
dev for SCSI tape
What is the likely device name in the /dev directory for a SCSI tape drive? is it /dev/tape? Anyone using the Seagate Travan SCSI backup? Lawrence -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: dev for SCSI tape
Lawrence [EMAIL PROTECTED] wrote: : What is the likely device name in the /dev directory for a SCSI tape : drive? is it /dev/tape? Anyone using the Seagate Travan SCSI backup? Mine is /dev/st0 for the rewinding device and /dev/nst0 for the non-rewinding. It's an H-P SureStore 2000 DAT unit. E.- -- Eloy A. Paris Information Technology Department Rockwell Automation de Venezuela Telephone: +58-2-9432311 Fax: +58-2-9431645 -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
