public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Robert Hancock <hancockr@shaw.ca>
To: Eric.Brunet@lps.ens.fr
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Problem with a CD
Date: Sun, 12 Mar 2006 11:00:46 -0600	[thread overview]
Message-ID: <441453BE.60002@shaw.ca> (raw)
In-Reply-To: <5PBCr-4pd-21@gated-at.bofh.it>

Eric.Brunet@lps.ens.fr wrote:
> I have error messages in my logs:
> on computer #1, they look like:
> |hdc: command error: status=0x51 { DriveReady SeekComplete Error }
> |hdc: command error: error=0x54 { AbortedCommand LastFailedSense=0x05 }
> |ide: failed opcode was: unknown
> |end_request: I/O error, dev hdc, sector 5008
> |Buffer I/O error on device hdc, logical block 1252
> on computer #2, they are simpler:
> |end_request: I/O error, dev sr0, sector 5008
> |Buffer I/O error on device sr0, logical block 1252
> 
> On both computers, I have the errors on the same sectors/blocks.
> 
> For the two offending files, the errors already occur on the beginings of
> the files.
> 
> Of course, all of this point to a defective CD, except that on both
> computers, I can read the files without any problem with windows XP
> (well, actually, I have only read avseq01.dat, which is a video file. I
> haven't tried the other troublesome file.)
> 
> What could be the problem ?

This is a VCD, right? Those use Mode 2 Form 2 which has weak error 
correction (like an audio CD). It's possible the drive is returning read 
errors and WinXP is ignoring the errors because it's a VCD, and Linux is 
not..

-- 
Robert Hancock      Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/


       reply	other threads:[~2006-03-12 17:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <5PBCr-4pd-21@gated-at.bofh.it>
2006-03-12 17:00 ` Robert Hancock [this message]
2006-03-12 16:28 Problem with a CD Eric.Brunet
2006-03-12 17:05 ` Måns Rullgård
2006-03-12 18:15 ` Patrick Mau
2006-03-12 20:53   ` Jan Engelhardt
2006-03-13  8:30     ` Eric.Brunet

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=441453BE.60002@shaw.ca \
    --to=hancockr@shaw.ca \
    --cc=Eric.Brunet@lps.ens.fr \
    --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