I can't comment on what others have experienced but I can say that the 2.2.x
kernels for me have not been a problem. There are some minor bugs to be sure
but they are more of a nuisance than anything serious. Moving over to the 2.2.x
kernels have not impeded me in any way. I followed the instructions for the
new kernel upgrades to the letter. I expect deviations from it might cause
problems. In either case I do not recommend you install the new kernel unless
you are in fron of the machine. Your situation is risky and if you're not
careful you may end up with a server or workstation that won't boot. Unless it
is absolutely critical I recommend you hold off trying to fix the tape or any
other issue until you get back to England or have someone else over there do
it for you.
Good Luck......
>Perhaps I didn't mention it, but the machine is in
England and I'm in Arizona!!! I'm >not real excited about making a major jump
in the kernel and I've been watching the >list intently for the past months and
since 2.2 was released, I do not get the feeling >that it is rock-solid. For
those that might be wondering, yes, this is the exact same >machine that I'm
having problems with the Out of File Descriptors and the postings >associated
with it. >
>The I/O errors listed with the dmesg came from various tar and mt rewind attempts... I
>didn't expect different results with the retension command nor did I get them.
>
>Thanks.
>
>Barry
>
>Juan Casero wrote:
>
>> Are you using RedHat 5.2? If so then you should consider moving over to kernel
>> 2.2.x. I currently use kernel 2.2.3 on a RedHat 5.2 system and am able to
>> reliable write data to and receive data from my IDE tape drive using SCSI
>> emulation. However, I don't use SCSI emulation for the other EIDE devices.
>> Things like my hard drives and cdroms I use the EIDE drivers.
>>
>> Put a tape in the drive and then issue the command:
>>
>> $mt -f /dev/st0 reten
>>
>> That should retension the tape and test the communications between the drive
>> and the driver. Post any messages you get.
>>
>> Juan
>>
>> On Tue, 23 Mar 1999, Barry Treahy wrote:
>> >Juan and all... I just rebuilt the kernel with SCSI emulation for the tape drive
>> >and I've included the dmesg which shows that it is recognized, but I'm still
>> >getting errors, now SCSI rather than the errors from native ATAPI. Can anyone
>> >offer 2 cents as to whether these errors are an indication of a failed device,
>> >incorrectly configured kernel (my fault), perhaps a bad SCSI emulation or what?
>> >
>> >TIA
>> >
>> >Barry
>> >
>> >mml1:~# dmesg
>> >8k kernel code, 384k reserved, 792k data)
>> >Swansea University Computer Society NET3.035 for Linux 2.0
>> >NET3: Unix domain sockets 0.13 for Linux NET3.035.
>> >Swansea University Computer Society TCP/IP for NET3.034
>> >IP Protocols: ICMP, UDP, TCP
>> >VFS: Diskquotas version dquot_5.6.0 initialized
>> >Checking 386/387 coupling... Ok, fpu using exception 16 error reporting.
>> >Checking 'hlt' instruction... Ok.
>> >Linux version 2.0.36 (root@mml1) (gcc version 2.7.2.3) #1 Tue Mar 23 16:39:04 GM
>> >T 1999
>> >Starting kswapd v 1.4.2.2
>> >Serial driver version 4.13 with no serial options enabled
>> >tty00 at 0x03f8 (irq = 4) is a 16550A
>> >tty01 at 0x02f8 (irq = 3) is a 16550A
>> >PS/2 auxiliary pointing device detected -- driver installed.
>> >hda: FX240S, ATAPI CDROM drive
>> >hdb: SEAGATE STT8000-A, ATAPI TAPE drive - enabling SCSI emulation
>> >ATAPI overlap supported: No
>> >ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
>> >Floppy drive(s): fd0 is 1.44M
>> >FDC 0 is a National Semiconductor PC87306
>> >(scsi0) <Adaptec AHA-294X Ultra SCSI host adapter> found at PCI 11/0
>> >(scsi0) Wide Channel, SCSI ID=7, 16/255 SCBs
>> >(scsi0) Warning - detected auto-termination
>> >(scsi0) Please verify driver detected settings are correct.
>> >(scsi0) If not, then please properly set the device termination
>> >(scsi0) in the Adaptec SCSI BIOS by hitting CTRL-A when prompted
>> >(scsi0) during machine bootup.
>> >(scsi0) Cables present (Int-50 NO, Int-68 YES, Ext-68 NO)
>> >(scsi0) Downloading sequencer code... 419 instructions downloaded
>> >scsi0 : Adaptec AHA274x/284x/294x (EISA/VLB/PCI-Fast SCSI) 5.1.4/3.2.4
>> > <Adaptec AHA-294X Ultra SCSI host adapter>
>> >scsi1 : SCSI host adapter emulation for IDE ATAPI devices
>> >scsi : 2 hosts.
>> > Vendor: SEAGATE Model: ST34371W Rev: 0360
>> > Type: Direct-Access ANSI SCSI revision: 02
>> >Detected scsi disk sda at scsi0, channel 0, id 0, lun 0
>> > Vendor: IBM Model: DCAS-34330W Rev: S65A
>> > Type: Direct-Access ANSI SCSI revision: 02
>> >Detected scsi disk sdb at scsi0, channel 0, id 1, lun 0
>> > Vendor: SEAGATE Model: STT8000-A Rev: 2.11
>> > Type: Sequential-Access ANSI SCSI revision: 02
>> >Detected scsi tape st0 at scsi1, channel 0, id 0, lun 0
>> >scsi : detected 1 SCSI tape 2 SCSI disks total.
>> >(scsi0:0:0:0) Synchronous at 20.0 Mbyte/sec, offset 8.
>> >SCSI device sda: hdwr sector= 512 bytes. Sectors= 8496960 [4148 MB] [4.1 GB]
>> >(scsi0:0:1:0) Synchronous at 20.0 Mbyte/sec, offset 8.
>> >SCSI device sdb: hdwr sector= 512 bytes. Sectors= 8467200 [4134 MB] [4.1 GB]
>> >PPP: version 2.2.0 (dynamic channel allocation)
>> >TCP compression code copyright 1989 Regents of the University of California
>> >PPP Dynamic channel allocation code copyright 1995 Caldera, Inc.
>> >PPP line discipline registered.
>> >SLIP: version 0.8.4-NET3.019-NEWTTY (dynamic channels, max=256).
>> >CSLIP: code copyright 1989 Regents of the University of California.
>> >3c59x.c:v0.99H 11/17/98 Donald Becker
>> >http://cesdis.gsfc.nasa.gov/linux/drivers/vortex.html
>> >eth0: 3Com 3c905 Boomerang 100baseTx at 0xff00, 00:60:08:27:45:ab, IRQ 9
>> > 8K word-wide RAM 3:5 Rx:Tx split, autoselect/MII interface.
>> > MII transceiver found at address 24, status 786d.
>> > Enabling bus-master transmits and whole-frame receives.
>> >Partition check:
>> > sda: sda1 sda2 sda3 sda4 < sda5 sda6 sda7 >
>> > sdb: sdb1
>> >VFS: Mounted root (ext2 filesystem) readonly.
>> >Adding Swap: 66556k swap-space (priority -1)
>> >Unable to load NLS charset cp437(nls_cp437)
>> >st0: Error with sense data: extra data not valid Current error st09:00: sense key
>> >Illegal Request
>> >Additional sense indicates Invalid command operation code
>> >st0: Error with sense data: extra data not valid Deferred error st09:00: sense key
>> >Hardware Error
>> >st0: Error with sense data: extra data not valid Current error st09:00: sense key
>> >Illegal Request
>> >Additional sense indicates Invalid command operation code
>> >st0: Error with sense data: extra data not valid Current error st09:00: sense key
>> >Hardware Error
>> >mml1:~#
>> >
>> >Juan Casero wrote:
>> >
>> >> On Mon, 22 Mar 1999, Barry Treahy wrote:
>> >>
>> >> I have an HP Colorado 2.5/5.0 GB IDE ATAPI tape drive. When I used the
>> >> ide-tape driver in the kernel I saw the exact same error messages. I have
>> >> recently moved over to SCSI emulation for IDE Tape drives. You can get more
>> >> information about this by posting to linux-tape@vger.rutgers.edu. For what
>> >> it's worth I think the problem is with the tape driver and not with the drive.
>> >>
>> >> Cheers
>> >>
>> >> >>Are there any type of diagnostics that I can run for an IDE tape
>> >> drive >or is anyone aware of problems with this type of configuration and
>> >> >Linux? The kernel is 2.0.36 with a Seagate CTT8000 which is a 4GB TR4
>> >> >type tape drive in a Gateway box. The system has been running for about
>> >> >18 months and the drive runs fine for about 5-7 months, and then we
>> >> >start getting various errors like:
>> >> >
>> >> >mml1:/usr/adm# tar -tvf /dev/ht0
>> >> >tar: Cannot open /dev/ht0: I/O error
>> >> >tar: Error is not recoverable: exiting now
>> >> >mml1:/usr/adm# mt -f /dev/ht0 rewind
>> >> >/dev/ht0: I/O error
>> >> >
>> >> >We swap tapes, old and new, clean the drive and nothing seems to resolve
>> >> >the problem other than swapping the drive out. I'm not a fan of TR4's
>> >> >but I have two SCSI versions of this same drive, CTT8000S, in a SCO and
>> >> >(excuse me) NT machine and though I have had to swap out the SCO drive
>> >> >once, the NT has been fine.
>> >> >
>> >> >The real pain is that GW is of NO help when we contact their support
>> >> >line to replace a swap because we're not running WIN 95 or 98 on their
>> >> >machine. It takes weeks of fighting with these people everytime to get
>> >> >a replacement. I just want to make sure that there isn't something else
>> >> >that I'm missing...
>> >> >
>> >> >TIA
>> >> >
>> >> >Barry
>> >> >
>> >>
>> >> ----------------------------------------
>> >> Content-Type: text/html; name="unnamed"
>> >> Content-Transfer-Encoding: 7bit
>> >> Content-Description:
>> >> ----------------------------------------
>> >>
>> >> --
>> >> Juan Casero
>> >> email: casero@bellsouth.net
>> >> __ _
>> >> / / (_)__ __ ____ __
>> >> / /__/ / _ \/ // /\ \/ / . . . t h e c h o i c e o f a
>> >> /____/_/_//_/\_,_/ /_/\_\ G N U g e n e r a t i o n . . .
>> >
>> >
>> >
>> >-====---====---====---====---====---====---====---====---====---====---====-
>> > to unsubscribe email "unsubscribe linux-admin" to majordomo@vger.rutgers.edu
>> > See the linux-admin FAQ: http://www.kalug.lug.net/linux-admin-FAQ/
>> --
>> Juan Casero
>> email: casero@bellsouth.net
>> __ _
>> / / (_)__ __ ____ __
>> / /__/ / _ \/ // /\ \/ / . . . t h e c h o i c e o f a
>> /____/_/_//_/\_,_/ /_/\_\ G N U g e n e r a t i o n . . .
>
>
>
>-====---====---====---====---====---====---====---====---====---====---====-
> to unsubscribe email "unsubscribe linux-admin" to majordomo@vger.rutgers.edu
> See the linux-admin FAQ: http://www.kalug.lug.net/linux-admin-FAQ/
-- Juan Casero email: casero@bellsouth.net __ _ / / (_)__ __ ____ __ / /__/ / _ \/ // /\ \/ / . . . t h e c h o i c e o f a /____/_/_//_/\_,_/ /_/\_\ G N U g e n e r a t i o n . . .- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/