mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Richard B. Johnson" <root@chaos.analogic.com>
To: root@mauve.demon.co.uk
Cc: "H.Rosmanith (Kernel Mailing List)"
	<kernel@wildsau.idv.uni.linz.at>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: usb-storage: how to ruin your hardware(?)
Date: Wed, 27 Aug 2003 15:58:14 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.53.0308271535060.5064@chaos> (raw)
In-Reply-To: <200308271933.UAA14620@mauve.demon.co.uk>

On Wed, 27 Aug 2003 root@mauve.demon.co.uk wrote:

> >
> > On Wed, 27 Aug 2003, H.Rosmanith (Kernel Mailing List) wrote:
> >
> > > > > "after the first write the flash device failed entirely". That doen't
> <snip>
> > Remember when AT Class machines had a BIOS that allowed you
> > to low-level format hard drives? When early IDE drives came
> > out, persons tried to format them and they got destroyed.
> > So, BIOS vendors took away the format capability.
> >
> > The IDE drive companies started a lie that was repeated so
> > often that it seemed true. It was that IDE drives didn't
> > have 'formatters' and, therefore, could only be formatted
> > at the factory. Of course, if this was true, how come
> > the format command did anything??  The truth was that
>
> This is actually true, and has been since around 80Mb or so.
> There is no absolute positioning information on the disk drive that can
> be used to lay down new positioning information for the tracks.
> Before this, there used to be a stepper motor that could position the
> head at track 743, or a seperate head that read track information from
> a dedicated surface.
>

No. Embedded servo-tracks have been used for this. Once a track is
written at the factory, even if the sectors are corrupt, it can
still be used for servo position because even corrupt data has
the spectral information necessary for the servo to find the
center of the track. The only possible problem is that you can't
find even one good sector to verify the track information. Both
the track number and the sector number is in the sector header.

You can low-level format many/most/all SCSI disks and ESDI disks
even though they also have embedded servo and voice-coil
positioners with no stepper motors and no feedback except from
the track information that you re-write.

Embedded servos work because the magnetic domains are always
too large for the data bits. This means that the system
ends up acting like a low-pass filter. The phase through
this filter changes, depending upon the position of the
head relative to when it was written. The servo nulls the
phase-shift to be what it was when the track was written.
This gets the head to the center of the track.

You do need some kind of independent positioner to write
the first tracks at the factory. Most use a 'formatter'
fixture that contains the feedback hardware necessary to do this.

Prototype drives get tracks written entirely using a software
approximation method where the first track is written slightly
off from the home position,  the next tracks are written
where the read-level from the previous write has fallen
6 dB (50%), as the positioner current is 'bumped' to overcome
friction and move to the next incremental track location.

This is not done for production drives because it is too
slow. However, this will allow the designer to experimentally
determine the maximim possible capacity of the drive, i.e.,
maximum number of cylinders.

> > these drives stored their parameters on the disk platters.
> > If you re-wrote the first real sectors on the drive, the
>
> This is more likely the problem, but
>

Cheers,
Dick Johnson
Penguin : Linux version 2.4.22 on an i686 machine (794.73 BogoMips).
            Note 96.31% of all statistics are fiction.



  reply	other threads:[~2003-08-27 19:57 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-21  1:34 H.Rosmanith (Kernel Mailing List)
2003-08-21  1:55 ` Matthew Dharm
2003-08-21  2:05   ` H.Rosmanith (Kernel Mailing List)
2003-08-21  2:35     ` Brandon Stewart
2003-08-21  6:17     ` Martin Schlemmer
2003-08-21 10:16   ` Maciej Soltysiak
2003-08-21  7:11 ` Alan Cox
2003-08-22 10:44   ` H.Rosmanith (Kernel Mailing List)
2003-08-27 15:11     ` H.Rosmanith (Kernel Mailing List)
2003-08-27 15:37       ` Richard B. Johnson
2003-08-27 19:33         ` root
2003-08-27 19:58           ` Richard B. Johnson [this message]
2003-08-28  2:59         ` H.Rosmanith (Kernel Mailing List)
2003-08-28 13:44           ` Andries Brouwer
2003-08-28 16:18             ` H.Rosmanith (Kernel Mailing List)
2003-08-28 20:25               ` Andries Brouwer
2003-08-29 10:25               ` Henning P. Schmiedehausen
2003-08-29 16:11                 ` H.Rosmanith (Kernel Mailing List)
2003-09-09  9:57                   ` Peter Werner
2003-09-15 22:57                     ` H.Rosmanith (Kernel Mailing List)
2003-08-27 16:10       ` Bas Mevissen
     [not found] <mMAP.NQ.15@gated-at.bofh.it>
     [not found] ` <mMUh.12N.19@gated-at.bofh.it>
     [not found]   ` <mUI5.7Hp.27@gated-at.bofh.it>
2003-08-21 12:35     ` Ihar 'Philips' Filipau
2003-08-22  1:06       ` jw schultz

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=Pine.LNX.4.53.0308271535060.5064@chaos \
    --to=root@chaos.analogic.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=kernel@wildsau.idv.uni.linz.at \
    --cc=linux-kernel@vger.kernel.org \
    --cc=root@mauve.demon.co.uk \
    /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®