public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jorge Nerin <comandante@zaralinux.com>
To: Vojtech Pavlik <vojtech@suse.cz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Cannot write a 90' cd
Date: Fri, 24 May 2002 01:25:25 +0200	[thread overview]
Message-ID: <3CED7A65.7010004@zaralinux.com> (raw)
In-Reply-To: <3CED69EB.2060003@zaralinux.com> <20020524005754.I27005@ucw.cz>

Vojtech Pavlik wrote:
> 
> 90 minute CD-Rs have a tighter leading track, and only some CD-R drives
> are able to cope with that. For example my Ricoh doesn't, failing some
> 54 minutes after start. There is nothing you can do about that.
> 

It could be that, but I suspect something strange, the cd reports itself to be 
about 80', then cdrecord is unable to write past this 80', after cdrecord 
fixates the cd and ejects it I can see that there is still a virgin zone of 
about 5 milimeters at the edge of the disk.

On the other hand I have been able to overburn some cd to gain about half a 
minute when needed, but these were 74 or 80 minutes media.

The most strange thing is the scsi error, "no error":

Input/output error. write_g1: scsi sendcmd: no error
CDB:  2A 00 00 05 7D 89 00 00 1F 00
status: 0x2 (CHECK CONDITION)
Sense Bytes: 70 00 05 00 00 00 00 0A 00 00 00 00 63 00 00 00
Sense Key: 0x5 Illegal Request, Segment 0
Sense Code: 0x63 Qual 0x00 (end of user area encountered on this track) Fru 0x0
Sense flags: Blk 0 (not valid)
cmd finished after 0.004s timeout 40s

-- 
Jorge Nerin
<comandante@zaralinux.com>


  reply	other threads:[~2002-05-23 23:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-23 22:15 Cannot write a 90' cd Jorge Nerin
2002-05-23 22:57 ` Vojtech Pavlik
2002-05-23 23:25   ` Jorge Nerin [this message]
2002-05-24  2:17     ` Marc Wilson
2002-06-04 22:36     ` Ricky Beam
2002-06-04 22:56       ` Ricky Beam

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=3CED7A65.7010004@zaralinux.com \
    --to=comandante@zaralinux.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vojtech@suse.cz \
    /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