From: Phillip Susi <psusi@cfl.rr.com>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: "linux-os (Dick Johnson)" <linux-os@analogic.com>,
Linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: readahead logic and I/O errors
Date: Wed, 15 Feb 2006 17:51:40 -0500 [thread overview]
Message-ID: <43F3B07C.8040803@cfl.rr.com> (raw)
In-Reply-To: <43F3A4EA.3040000@tls.msk.ru>
Michael Tokarev wrote:
> I opened the drive after BIOS didn't detect it on reboot (after
> power-off). There's one fired (burned? perished? how's that in
I think you mean "fried", which is what happens when something is heated
to excess. "fired" is what happens to you when your boss catches you
stealing office supplies or sleeping with his daughter. It is also what
happens to the bullet when you pull the trigger.
> english?) chip on the plate, wich smells like fired silicone.
> It looks like a ~5mm pit in the center of square chip, full of
> ache, and there's a crack across it. The drive is dead.
>
> I think it's a chip which controls one of the motors of the drive,
> most probably the one which moves the head, because the head
> motor connector is right near the chip.
>
> When I turned off power, the drive was *hot*, and it started
> "trembling" (or chattering) when I turned power off.
>
> It was a dvd-cd combo (read dvd, read-write cd) Teac drive, I
> don't remember the model (there's no label on the drive, and
> I can't send inquiry/identify command to it anymore, obviously).
>
> Yest it looks like a problem in the drive *too*, as it should
> not behave like that in the first place. But the thing is, I
> did know something's bad going on, I saw it, but I wasn't able
> to stop it from linux, only poweroff stopped things from going.
>
> /mjt
I assume the drive was no longer under warranty? It certainly should
not have burned itself out like that, but yea, the kernel should not
keep trying to readahead on error. I ran into a similar problem where I
mounted a filesystem on a cdrw read/write and wrote some files to it.
When I went to unmount it all the writes failed because the media was
not properly formatted to be writable. The kernel kept trying to write
each sector though, and blocked the umount process in the unkillable D
state for a good 20 minutes and kept the drive door locked. Needless to
say, I was very annoyed.
next prev parent reply other threads:[~2006-02-15 22:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-15 20:35 readahead logic and I/O errors Michael Tokarev
2006-02-15 20:59 ` linux-os (Dick Johnson)
2006-02-15 22:02 ` Michael Tokarev
2006-02-15 22:51 ` Phillip Susi [this message]
2006-02-16 6:53 ` Jan Knutar
2006-02-16 10:42 ` Michael Tokarev
2006-02-20 10:57 ` Erik Mouw
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=43F3B07C.8040803@cfl.rr.com \
--to=psusi@cfl.rr.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-os@analogic.com \
--cc=mjt@tls.msk.ru \
/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