From: eazgwmir@umail.furryterror.org (Zygo Blaxell)
To: reiserfs-list@namesys.com
Subject: Re: trolling
Date: 13 Feb 2003 14:54:50 -0500 [thread overview]
Message-ID: <b2gt6a$8dq$1@satsuki.furryterror.org> (raw)
In-Reply-To: 20030212131120.A10438@t-raenon.nmd.msu.ru
In article <20030212131120.A10438@t-raenon.nmd.msu.ru>,
Alexander Lyamin <flx@msu.ru> wrote:
>P.S. "In addition, check your facts before making a statement
>that insults someone and claims something that is completely untrue."
>
>Powersupply units physically damaging hard-drive disks (plates!).
I wouldn't characterize that as "untrue," more like "technically
incomplete." There are lots of ways to permanently disable hard disks
without physically damaging them.
Disk head servo controllers operate using some of the data on the disk
platter as a position encoder, which is used in a feedback scheme
to control the motor. The motor's electrical power is literally a
function of the previous position, the theoretical position, and the
current position as reported by reading data through the disk head.
Assuming that the normal operating rules for the DC servo controller and
write head power are violated (e.g. because the CPU on the disk controller
board is going insane due to invalid power supply feed corrupting its
memory, or due to an external physical shock during a write), it is
possible to corrupt the position data on the platter and permanently lose
the ability to seek to some areas of the platter. The position data was
initially written using frighteningly expensive precision hardware at
the disk drive factory and cannot be regenerated without said equipment.
Speaking of DC server controller operating rule violations...those motors
are fairly powerful, and they normally operate at only a few percent of
their full power most of the time. Very short pulses of significant power
are used during acceleration and deceleration. Full power sustained for
any significant interval of time on the head motor may damage the heads
as they collide with the side of the drive case, or bend the arm the
heads are mounted on. On the other hand, when the motors are moving,
the drive must feed their kinetic energy back into the power supply to
make them stop. A bad power supply can result in position overshoots,
although most disks will correct for these automatically (they'll probably
be a lot slower though).
Consider what happens if the circuit which accelerates the disk from a
standing stop (a fairly high-power circuit, actually the highest power
circuit in the disk drive) does not turn off automatically when the disk
reached its cruising velocity, and instead simply keeps accelerating the
disk as fast as air resistance and maximum power output would allow.
Either the platters will fly apart, or the electronics will cook in
their own heat.
It's also possible to rewrite the disk controller firmware on the disk.
Usually only a minimal loader program is provided in ROM, and the rest
of the drive's firmware is stored on the disk itself--two copies on
two different tracks, near the track 0 index mark where they can be
located with a very simple motor controller program. This trades cheap
disk space and fast RAM for expensive and slow flash ROM.
--
Zygo Blaxell (Laptop) <zblaxell@feedme.hungrycats.org>
GPG = D13D 6651 F446 9787 600B AD1E CCF3 6F93 2823 44AD
prev parent reply other threads:[~2003-02-13 19:54 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-11 18:59 Corrupted/unreadable journal: reiser vs. ext3 Dirk Schenkewitz
2003-02-11 20:27 ` Hans Reiser
2003-02-11 21:30 ` Mike Hodson
2003-02-11 21:47 ` Hans Reiser
2003-02-11 21:58 ` Hans Reiser
2003-02-12 6:35 ` Oleg Drokin
2003-02-11 23:11 ` Adam Goryachev
2003-02-11 23:17 ` Anders Widman
2003-02-12 0:12 ` Hans Reiser
2003-02-12 10:23 ` Anders Widman
2003-02-12 10:47 ` Hans Reiser
2003-02-12 11:12 ` Adam Goryachev
2003-02-12 13:42 ` Anders Widman
2003-02-12 14:15 ` Russell Coker
2003-02-12 15:26 ` Anders Widman
2003-02-12 16:22 ` bscott
2003-02-12 16:28 ` Russell Coker
2003-02-12 16:40 ` Anders Widman
2003-02-13 3:42 ` Zygo Blaxell
2003-02-13 10:13 ` Anders Widman
2003-02-13 14:44 ` Rudy Zijlstra
2003-02-13 3:31 ` Zygo Blaxell
[not found] ` <20030213113003.7ee7af6e.philippe.gramoulle@mmania.com>
2003-02-13 18:17 ` rijndael loopback encryption was [Re: Corrupted/unreadable journal: reiser vs. ext3] Zygo Blaxell
2003-02-12 16:39 ` Corrupted/unreadable journal: reiser vs. ext3 Sam Vilain
2003-02-12 5:12 ` Ross Vandegrift
2003-02-12 7:17 ` Oleg Drokin
2003-02-12 10:17 ` Alexander Lyamin
2003-02-12 10:19 ` Alexander Lyamin
2003-02-12 16:25 ` Vitaly Fertman
2003-02-12 16:56 ` Anders Widman
2003-02-12 17:13 ` Oleg Drokin
2003-02-12 1:02 ` Mike Hodson
2003-02-12 7:25 ` Oleg Drokin
2003-02-12 9:45 ` Hans Reiser
2003-02-12 16:09 ` Sam Vilain
2003-02-12 10:11 ` trolling Alexander Lyamin
2003-02-12 12:32 ` trolling Dirk Schenkewitz
2003-02-12 14:48 ` trolling Chris Mason
2003-02-13 19:54 ` Zygo Blaxell [this message]
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='b2gt6a$8dq$1@satsuki.furryterror.org' \
--to=eazgwmir@umail.furryterror.org \
--cc=reiserfs-list@namesys.com \
/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.