From: Douglas Gilbert <dougg@torque.net>
To: Orion Poplawski <orion@cora.nwra.com>
Cc: linux-scsi@vger.kernel.org
Subject: Re: Vendor specific cdrom error messages
Date: Wed, 19 Apr 2006 15:02:32 -0400 [thread overview]
Message-ID: <44468948.6000109@torque.net> (raw)
In-Reply-To: <e25obb$2fp$1@sea.gmane.org>
Orion Poplawski wrote:
> I got the following error trying to burn a DVD on an IBM USB2 DVD-R burner:
>
> Nov 7 11:40:36 makani kernel: cdrom: This disc doesn't have any tracks
> I recognize!
> Nov 7 11:41:59 makani kernel: sr 0:0:0:0: SCSI error: return code =
> 0x8000002
> Nov 7 11:41:59 makani kernel: sr0: Current: sense key: Data Protect
> Nov 7 11:41:59 makani kernel: ASC=0x27 <<vendor>> ASCQ=0xff
>
> This is on Fedora Core 4 and kernel 2.6.13-1.1532_FC4.
>
> It turns out that this is because the drive did not have enough power
> (it was not plugged into the separate ac adapter). I was able to
> determine this by booting into Windows, which gave me a nice descriptive
> error message.
>
> I was wondering if it makes sense for the kernel drivers to know these
> error messages and report better errors, of it should be left up to user
> space tools.
I think that you can guess the answer to the above query.
Asc and/or ascq codes >= 0x80 (and <= 0xff) mark the
additional sense code as vendor specific.
The ascq code looks suspicious. An asc/ascq tuple of
<0x27,0x0> ("Write protected") would tie in pretty well
with the sense key of "Data Protect". A better choice
might be <0x5e,0x0> "Low power condition on".
Doug Gilbert
next prev parent reply other threads:[~2006-04-19 19:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-19 16:26 Vendor specific cdrom error messages Orion Poplawski
2006-04-19 19:02 ` Douglas Gilbert [this message]
2006-04-19 21:55 ` Orion Poplawski
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=44468948.6000109@torque.net \
--to=dougg@torque.net \
--cc=linux-scsi@vger.kernel.org \
--cc=orion@cora.nwra.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.