linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andre Hedrick <andre@linux-ide.org>
To: Khalid Aziz <khalid@fc.hp.com>
Cc: Camm Maguire <camm@enhanced.com>, linux-kernel@vger.kernel.org
Subject: Re: 2.2.18 IDE tape problem, with ide-scsi
Date: Tue, 27 Feb 2001 12:26:47 -0800 (PST)	[thread overview]
Message-ID: <Pine.LNX.4.10.10102271223390.32662-100000@master.linux-ide.org> (raw)
In-Reply-To: <3A9BEF68.72EEF0E8@fc.hp.com>



Hi Khalid,

So, is HP going to allow linux to publsih "Tape Alert" as a means to
assist with error checking and testing in general?  Also why did HP
take the 14GB/20GB models and move off the standard QIC or TR-4
IO-Firmware?

Cheers,

Andre Hedrick
Linux ATA Development
ASL Kernel Development
-----------------------------------------------------------------------------
ASL, Inc.                                     Toll free: 1-877-ASL-3535
1757 Houret Court                             Fax: 1-408-941-2071
Milpitas, CA 95035                            Web: www.aslab.com

On Tue, 27 Feb 2001, Khalid Aziz wrote:

> Camm Maguire wrote:
> > 
> > Greetings!  OK, with st debugging, here are the most common errors
> > with the Conner:
> > 
> > Feb 27 14:46:39 intech9 kernel: st0: Error: 28000000, cmd: 8 1 0 0 40 0 Len: 16
> > Feb 27 14:46:39 intech9 kernel: Info fld=0x24, Current st09:00: sns = f0  8
> > Feb 27 14:46:39 intech9 kernel: ASC=14 ASCQ= 3
> > Feb 27 14:46:39 intech9 kernel: Raw sense data:0xf0 0x00 0x08 0x00 0x00 0x00 0x24 0x0a 0x00 0x00 0x00 0x00 0x14 0x03 0x00 0x00
> > Feb 27 14:46:39 intech9 kernel: st0: Sense: f0  0  8  0  0  0 24  a
> > Feb 27 14:46:39 intech9 kernel: st0: Tape error while reading.
> 
> This was a read command that failed. Request sense information shows a
> sense key of 0x08 which is a "Blank check". This sense key indicates
> either a blank medium found or another error at EOD. ASC/ASCQ of
> 0x14/0x03 say "End-Of-Data not found". This indicates something wrong
> with the tape or maybe the drive needs cleaning. Do you get this error
> with more than one tape?
> 
> 
> > Feb 27 14:46:40 intech9 kernel: st0: Error: 28000000, cmd: 5 0 0 0 0 0 Len: 16
> > Feb 27 14:46:40 intech9 kernel: [valid=0] Info fld=0x0, Current st09:00: sns = 70  5
> > Feb 27 14:46:40 intech9 kernel: ASC=20 ASCQ= 0
> > Feb 27 14:46:40 intech9 kernel: Raw sense data:0x70 0x00 0x05 0x00 0x00 0x00 0x00 0x0a 0x00 0x00 0x00 0x00 0x20 0x00 0x00 0x00
> > Feb 27 14:46:40 intech9 kernel: st0: Can't read block limits.
> 
> This was a "Read Block Limits" command which the drive claimed it does
> not recognize. "Read Block Limits" is a mandatory command for SCSI
> sequential access devices which is why "st" is issuing this command. The
> tape drive you have is not SCSI, so the manufacturer chose not to
> implement this command. The driver may still be able to work after "Read
> Block Limits" fails, but I have not read enough code to be sure.
> 
> > Feb 27 14:46:40 intech9 kernel: st0: Mode sense. Length 11, medium b6, WBS 10, BLL 8
> > Feb 27 14:46:40 intech9 kernel: st0: Density 45, tape length: 0, drv buffer: 1
> > Feb 27 14:46:40 intech9 kernel: st0: Block size: 512, buffer size: 32768 (64 blocks).
> > 
> > Any advice appreciated!
> 
> ====================================================================
> Khalid Aziz                             Linux Development Laboratory
> (970)898-9214                                        Hewlett-Packard
> khalid@fc.hp.com                                    Fort Collins, CO

Andre Hedrick
Linux ATA Development
ASL Kernel Development
-----------------------------------------------------------------------------
ASL, Inc.                                     Toll free: 1-877-ASL-3535
1757 Houret Court                             Fax: 1-408-941-2071
Milpitas, CA 95035                            Web: www.aslab.com


  reply	other threads:[~2001-02-27 20:28 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-27 16:06 2.2.18 IDE tape problem, with ide-scsi Camm Maguire
2001-02-27 15:07 ` Khalid Aziz
2001-02-27 17:19   ` Camm Maguire
2001-02-27 15:34     ` Khalid Aziz
2001-02-27 19:52       ` Camm Maguire
2001-02-27 18:18         ` Khalid Aziz
2001-02-27 20:26           ` Andre Hedrick [this message]
2001-02-27 21:26             ` Khalid Aziz
2001-02-28 15:23           ` Camm Maguire
2001-02-28 15:34             ` Mike Dresser
2001-03-07 22:54           ` Camm Maguire
2001-03-12 16:52             ` Khalid Aziz
2001-03-13 14:14               ` Camm Maguire
2001-02-27 17:32     ` Mike Dresser
2001-02-27 18:31       ` Camm Maguire
2001-02-27 18:34         ` Mike Dresser
2001-02-27 19:05           ` Andre Hedrick
2001-02-27 19:40             ` Camm Maguire
2001-03-01 17:02               ` Khalid Aziz
2001-02-27 22:21           ` Alan Cox
2001-02-27 19:01       ` Andre Hedrick
2001-02-27 19:04         ` Mike Dresser
2001-03-07  0:34 ` [PATCH] " Chip Salzenberg
2001-03-07  1:09   ` Andre Hedrick
     [not found] <Pine.LNX.4.10.10102271153560.29323-100000@coffee.psychology.mcmaster.ca>
2001-02-27 17:16 ` Camm Maguire

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.LNX.4.10.10102271223390.32662-100000@master.linux-ide.org \
    --to=andre@linux-ide.org \
    --cc=camm@enhanced.com \
    --cc=khalid@fc.hp.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).