From: matthieu castet <castet.matthieu@free.fr>
To: Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: ide-cd and bad sectors
Date: Sat, 02 Jul 2005 16:14:02 +0200 [thread overview]
Message-ID: <42C6A12A.8030009@free.fr> (raw)
Hi,
I use 2.6.12 vanilla kernel.
Since some time when a disk has bad sector because it is damaged or
overburned, the Linux kernel seem too hang for this device :
the process reading is unkillable (even with SIGKILL).
the kernel seem to try to read the next sectors, but always failed.
The only way to stop the kernel trying to read the disc is to reboot or
don't lock the drive and eject it, with the button on the device.
When hard-ejecting it, there are something strange in the log : the
kernel failed for 508 sector (is there a so big cache for disk request ?
If this is the case that explain why the kernel seem too hang as it need
1-2s per bad sector).
Also at the end of the log [1] you could see that the 2 last message
report error for the first sectors that produce the error. Is that
normal : I thought this sector already produced an "media error (bad
sector)" and should be skipped ?
Also I was wondering if all the sector that ide-cd failed to read are
bad sector, or if ide-cd failed to put the drive in a consistent state
for reading the next sector after corrupted one.
IIRC on 2.4 kernel there wasn't such problem, I even managed to recover
some damaged disk...
thanks
Matthieu
[1]
Jul 2 15:10:13 localhost kernel: hdc: media error (bad sector):
status=0x51 { D
riveReady SeekComplete Error }
Jul 2 15:10:13 localhost kernel: hdc: media error (bad sector):
error=0x30 { La
stFailedSense=0x03 }
Jul 2 15:10:13 localhost kernel: ide: failed opcode was: unknown
Jul 2 15:10:13 localhost kernel: end_request: I/O error, dev hdc,
sector 119095
12
Jul 2 15:10:13 localhost kernel: printk: 105 messages suppressed.
Jul 2 15:10:13 localhost kernel: Buffer I/O error on device hdc,
logical block
2977378
Jul 2 15:10:17 localhost kernel: hdc: media error (bad sector):
status=0x51 { D
riveReady SeekComplete Error }
Jul 2 15:10:17 localhost kernel: hdc: media error (bad sector):
error=0x30 { La
stFailedSense=0x03 }
Jul 2 15:10:17 localhost kernel: ide: failed opcode was: unknown
Jul 2 15:10:17 localhost kernel: end_request: I/O error, dev hdc,
sector 119095
16
[...]
Jul 2 15:12:03 localhost kernel: hdc: tray open
Jul 2 15:12:03 localhost kernel: end_request: I/O error, dev hdc,
sector 119100
16
Jul 2 15:12:03 localhost kernel: hdc: tray open
Jul 2 15:12:03 localhost kernel: end_request: I/O error, dev hdc,
sector 119100
20
Jul 2 15:12:03 localhost kernel: hdc: tray open
Jul 2 15:12:03 localhost kernel: end_request: I/O error, dev hdc,
sector 119095
12
Jul 2 15:12:03 localhost kernel: hdc: tray open
Jul 2 15:12:03 localhost kernel: end_request: I/O error, dev hdc,
sector 119095
16
next reply other threads:[~2005-07-02 14:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-02 14:14 matthieu castet [this message]
2005-07-04 22:42 ` ide-cd and bad sectors Jan Knutar
2005-07-05 16:00 ` Alan Cox
2005-07-05 18:21 ` matthieu castet
2005-07-06 20:09 ` Bill Davidsen
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=42C6A12A.8030009@free.fr \
--to=castet.matthieu@free.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