From: "Måns Rullgård" <mru@inprovide.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Problem with a CD
Date: Sun, 12 Mar 2006 17:05:35 +0000 [thread overview]
Message-ID: <yw1xd5grbnkw.fsf@agrajag.inprovide.com> (raw)
In-Reply-To: <20060312162825.GA16993@platane.lps.ens.fr>
Eric.Brunet@lps.ens.fr writes:
> Hi all,
>
> In short: I have a CD that windows XP can read but that linux cannot.
>
> I have a mini-CD (with a diameter of 8 cm) that I am trying to read. I
> have tried two computers:
[...]
> 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.)
Do you have any way of checking whether windows reads the file
correctly, or just fails to detect the error?
--
Måns Rullgård
mru@inprovide.com
next prev parent reply other threads:[~2006-03-12 17:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-12 16:28 Eric.Brunet
2006-03-12 17:05 ` Måns Rullgård [this message]
2006-03-12 18:15 ` Patrick Mau
2006-03-12 20:53 ` Jan Engelhardt
2006-03-13 8:30 ` Eric.Brunet
[not found] <5PBCr-4pd-21@gated-at.bofh.it>
2006-03-12 17:00 ` Robert Hancock
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=yw1xd5grbnkw.fsf@agrajag.inprovide.com \
--to=mru@inprovide.com \
--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
all inboxes | Powered by JetHome®