Lenovo ThinkCentre M55e Hardware Maintenance Manual - Page 52

Quick, erase, drive

Get Lenovo ThinkCentre M55e PDF manuals and user guides View all Lenovo ThinkCentre M55e manuals
Add to My Manuals
Save this manual to your list of manuals

Page 52 highlights

v Write-Splice Repair - detects and corrects Error Correction Code errors during Verify tests. v Auto Spin Down - a gradual spin down of the drive platters to avoid damaging the media. v Manufacturer Log - an in-depth manufacturer supported log of errors on the drive. Multitasking: To allow simultaneous testing of multiple hard drives whenever possible, the FDAT module is written as a set of multitasking functions. Each drive under test can run the same test or run a different test at the same time. Each subtest is written to handle a single test pass and all test variables are kept track of in a structure unique for each drive. However, when testing IDE drives, FDAT will not perform simultaneous testing of IDE drives that are attached to the same IDE cable. For example, if FDAT is testing four IDE drives on a PC, it will perform simultaneous testing on drives 1 and 3 first (master drives), then perform tests on 2 and 4 (slave drives). FDAT will also perform simultaneous testing on a master and slave that are on separate IDE cables, but will not perform simultaneous tests on a master and slave on the same IDE cable. This generally increases the amount of time needed to test multiple IDE drives. Another limitation of FDAT'S multitasking capability is the use of Ultra DMA (UDMA). Only one drive at a time can access the UDMA channel and the UDMA channel buffer must be kept high in order to maintain a speed advantage over other data transfer modes. In order to use the UDMA channel during testing, users must disable the multitasking feature. Destructive versus non-destructive testing: Most of the tests found in FDAT are non-destructive. This means that PC-Doctor program will preserve any data that is present on the tested media prior to beginning any destructive operations (such as write operations). However, users can run certain tests in destructive mode (i.e. surface scan tests). Destructive tests will speed up testing because FDAT does not preserve the data on the media prior to the test beginning. Unlike non-destructive tests, any data present on the media prior to the test beginning is lost. FDAT allows for enabling or disabling destructive tests, as well as specifying a range of destructive and non-destructive sectors on the tested drive. This is done through the configuration of the FDAT.INI. If destructive and non-destructive ranges somehow overlap, then the overlapped area is considered non-destructive. For example, if users specify both destructive and non-destructive ranges as the same, then the entire drive is tested as non-destructive. Quick and Full erase - hard drive The diagnostics program offers two hard drive format utilities: v Quick Erase Hard Drive v Full Erase Hard Drive The Quick Erase Hard Drive provides a DOS utility that performs the following: v Destroys the Master Boot Record (MBR) on the hard drive. 46 Hardware Maintenance Manual

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
v
Write-Splice
Repair
-
detects
and
corrects
Error
Correction
Code
errors
during
Verify
tests.
v
Auto
Spin
Down
-
a
gradual
spin
down
of
the
drive
platters
to
avoid
damaging
the
media.
v
Manufacturer
Log
-
an
in-depth
manufacturer
supported
log
of
errors
on
the
drive.
Multitasking:
To
allow
simultaneous
testing
of
multiple
hard
drives
whenever
possible,
the
FDAT
module
is
written
as
a
set
of
multitasking
functions.
Each
drive
under
test
can
run
the
same
test
or
run
a
different
test
at
the
same
time.
Each
subtest
is
written
to
handle
a
single
test
pass
and
all
test
variables
are
kept
track
of
in
a
structure
unique
for
each
drive.
However,
when
testing
IDE
drives,
FDAT
will
not
perform
simultaneous
testing
of
IDE
drives
that
are
attached
to
the
same
IDE
cable.
For
example,
if
FDAT
is
testing
four
IDE
drives
on
a
PC,
it
will
perform
simultaneous
testing
on
drives
1
and
3
first
(master
drives),
then
perform
tests
on
2
and
4
(slave
drives).
FDAT
will
also
perform
simultaneous
testing
on
a
master
and
slave
that
are
on
separate
IDE
cables,
but
will
not
perform
simultaneous
tests
on
a
master
and
slave
on
the
same
IDE
cable.
This
generally
increases
the
amount
of
time
needed
to
test
multiple
IDE
drives.
Another
limitation
of
FDAT’S
multitasking
capability
is
the
use
of
Ultra
DMA
(UDMA).
Only
one
drive
at
a
time
can
access
the
UDMA
channel
and
the
UDMA
channel
buffer
must
be
kept
high
in
order
to
maintain
a
speed
advantage
over
other
data
transfer
modes.
In
order
to
use
the
UDMA
channel
during
testing,
users
must
disable
the
multitasking
feature.
Destructive
versus
non-destructive
testing:
Most
of
the
tests
found
in
FDAT
are
non-destructive.
This
means
that
PC-Doctor
program
will
preserve
any
data
that
is
present
on
the
tested
media
prior
to
beginning
any
destructive
operations
(such
as
write
operations).
However,
users
can
run
certain
tests
in
destructive
mode
(i.e.
surface
scan
tests).
Destructive
tests
will
speed
up
testing
because
FDAT
does
not
preserve
the
data
on
the
media
prior
to
the
test
beginning.
Unlike
non-destructive
tests,
any
data
present
on
the
media
prior
to
the
test
beginning
is
lost.
FDAT
allows
for
enabling
or
disabling
destructive
tests,
as
well
as
specifying
a
range
of
destructive
and
non-destructive
sectors
on
the
tested
drive.
This
is
done
through
the
configuration
of
the
FDAT.INI.
If
destructive
and
non-destructive
ranges
somehow
overlap,
then
the
overlapped
area
is
considered
non-destructive.
For
example,
if
users
specify
both
destructive
and
non-destructive
ranges
as
the
same,
then
the
entire
drive
is
tested
as
non-destructive.
Quick
and
Full
erase
-
hard
drive
The
diagnostics
program
offers
two
hard
drive
format
utilities:
v
Quick
Erase
Hard
Drive
v
Full
Erase
Hard
Drive
The
Quick
Erase
Hard
Drive
provides
a
DOS
utility
that
performs
the
following:
v
Destroys
the
Master
Boot
Record
(MBR)
on
the
hard
drive.
46
Hardware
Maintenance
Manual