mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@suse.de>
To: Chris Clayton <chris@theclaytons.giointernet.co.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: CDMRW in 2.6
Date: Fri, 13 Aug 2004 15:50:36 +0200	[thread overview]
Message-ID: <20040813135036.GR2663@suse.de> (raw)
In-Reply-To: <200408131435.17362.chris@theclaytons.giointernet.co.uk>

On Fri, Aug 13 2004, Chris Clayton wrote:
> > > I'll try a full (as opposed to quick) blank with cdrwtool plus a
> > > forced format with cdmrw and report back when that has finished.
> >
> > Yes please do that, if that doesn't work it's really screwed.
> 
> Ok, here's the results:
> 
> [chris:~]$ cdrwtool -t 10 -d /dev/hdc -b full
> setting speed to 10
> using device /dev/hdc
> full blank
> 1386KB internal buffer
> setting write speed to 10x
> 
> <<no new messages from dmesg>>
> 
> [chris:~]$ cdmrw -d /dev/hdc -f full -F
> not a mrw formatted disc
> LBA space: DMA
> 
> <<no new messages from dmesg>>
> 
> [chris:~]$ while cdmrw -d /dev/hdc -f full | grep "mrw format running" ; do 
> sleep 20; done
> mrw format running
> <snip>
> mrw format running
> 
> <<no new messages from dmesg>>
> 
> [chris:~]$ mkudffs --media-type=cdrw /dev/hdc
> start=0, blocks=16, type=RESERVED
> start=16, blocks=3, type=VRS
> start=19, blocks=237, type=USPACE
> start=256, blocks=1, type=ANCHOR
> start=257, blocks=31, type=USPACE
> start=288, blocks=32, type=PVDS
> start=320, blocks=32, type=LVID
> start=352, blocks=32, type=STABLE
> start=384, blocks=1024, type=SSPACE
> start=1408, blocks=256480, type=PSPACE
> start=257888, blocks=31, type=USPACE
> start=257919, blocks=1, type=ANCHOR
> start=257920, blocks=160, type=USPACE
> start=258080, blocks=32, type=STABLE
> start=258112, blocks=32, type=RVDS
> start=258144, blocks=31, type=USPACE
> start=258175, blocks=1, type=ANCHOR
> 
> <<the following new messages from dmesg>>
> 
> cdrom: hdc: mrw address space DMA selected
> cdrom open: mrw_status 'mrw complete'
> hdc: command error: status=0x51 { DriveReady SeekComplete Error }
> hdc: command error: error=0x54

Ok yes, same error. It's the drive doing something odd, I have no idea
what...

> I'll try the same process (except the blanking) with a brand new piece of 
> media and report when that is complete.

I doubt it'll help.

-- 
Jens Axboe


  reply	other threads:[~2004-08-13 13:52 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-09 16:25 Chris Clayton
2004-08-12 20:23 ` Bill Davidsen
2004-08-13 12:08   ` Chris Clayton
2004-08-13  7:15 ` Jens Axboe
2004-08-13  7:55   ` Alan Jenkins
2004-08-13  8:01     ` Jens Axboe
2004-08-13 12:47       ` Chris Clayton
2004-08-13 11:47         ` Jens Axboe
2004-12-22  1:24           ` Daniel Drake
2004-08-13 12:53   ` Chris Clayton
2004-08-13 11:54     ` Jens Axboe
2004-08-13 14:35       ` Chris Clayton
2004-08-13 13:50         ` Jens Axboe [this message]
2004-08-13 16:15           ` Chris Clayton

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=20040813135036.GR2663@suse.de \
    --to=axboe@suse.de \
    --cc=chris@theclaytons.giointernet.co.uk \
    --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

Powered by JetHome