All of lore.kernel.org
 help / color / mirror / Atom feed
From: Douglas Gilbert <dougg@torque.net>
To: linux-kernel@vger.kernel.org, Leung Yau Wai <chris@gist.q-station.net>
Cc: linux-scsi@vger.kernel.org
Subject: Re: dd cdrom error
Date: Thu, 27 Dec 2001 17:33:24 -0500	[thread overview]
Message-ID: <3C2BA1B4.EB853055@torque.net> (raw)

Leung Yau Wai <chris@gist.q-station.net> wrote:
> I come across a problem which seem exist in kernel 
> 2.4.x but not in 2.2.x.
>
> The problem is that, when I try to using dd to create 
> a ISO image of a cdrom then around dumping the end of 
> the disc it will give out the following error message:
>
> e.g. dd if=/dev/cdrom of=n.iso

If dd is used like that, it is surprising you do not get
more errors. An iso9660 image does not necessarily fill
the track. So the IDE equivalent of the SCSI READ CAPACITY 
command will often report a size that includes unwritten 
sectors at the end. Those unwritten sectors can/will cause
IO errors when an attempt is made to read them.

A very useful program called "isosize" has made a return to
util-linux-2.10s (and later). Execute:
  isosize -x /dev/cdrom
to find the number of sectors and the sector size of the iso9660
fs held _within_ the first track. Then use those numbers as the 
"count=" and "bs=" arguments to dd respectively.


If you still have problems try turning DMA off via hdparm
or set the DMA mode back to 33 MHz (-X34).

Doug Gilbert

             reply	other threads:[~2001-12-27 22:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-27 22:33 Douglas Gilbert [this message]
2001-12-28  1:42 ` dd cdrom error Leung Yau Wai
2001-12-28 14:11   ` Alan Cox
2001-12-28 15:30     ` Leung Yau Wai
2001-12-28 16:39       ` Alan Cox
  -- strict thread matches above, loose matches on Subject: below --
2001-12-27  6:54 Leung Yau Wai

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=3C2BA1B4.EB853055@torque.net \
    --to=dougg@torque.net \
    --cc=chris@gist.q-station.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@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 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.