state of SCSI disk ...

[comitter]

Direct Access IBM-ESXS ST336605LC !# at ctrl 0/1.0
Firmware revision B243
Unit Serial Number: 3FP0Y058

Write errors corrected with possible delays: 0 [4]
Re-writes: 0 [4]
Write errors corrected: 0 [4]
Times write correction algorithm processed: 0 [4]
Bytes written: 4374552998912 [8]
Write total uncorrected errors: 0 [4]
Read errors corrected w/o substantial delay: 4944654 [4]
Read errors corrected with possible delays: 1 [4]
Re-reads: 0 [4]
Read errors corrected: 4944655 [4]
Times read correction algorithm processed: 4944841 [4]
Bytes read: 65166117543936 [8]
Read total uncorrected errors: 0 [4]
Verify errors corrected w/o substantial delay: 29216 [4]
Verify errors corrected with possible delays: 0 [4]
Re-verifications: 0 [4]
Verify errors corrected: 29216 [4]
Times verification correction algorithm processed: 29216 [4]
Bytes verified: 1250054422528 [8]
Verify total uncorrected errors: 0 [4]
Total non-medium errors: 10 [4]
Temperature in degrees celsius: 32
Reference temperature in degrees celsius: 65
Logical blocks sent to initiators: 211094466 [4]
Logical blocks received from initators: 4164908548 [4]
Logical blocks read from cache, sent to initiators: 1645587723 [4]
Number of read and write commands <= current segment size: 984818539
[4]
Number of read and write commands > current segment size: 0 [4]
Write errors corrected with possible delays: 0 [4]
Re-writes: 0 [4]
Write errors corrected: 0 [4]
Times write correction algorithm processed: 0 [4]
Bytes written: 4374552946688 [8]
Write total uncorrected errors: 0 [4]
Read errors corrected w/o substantial delay: 4944654 [4]
Read errors corrected with possible delays: 1 [4]
Re-reads: 0 [4]
Read errors corrected: 4944655 [4]
Times read correction algorithm processed: 4944841 [4]
Bytes read: 65166112465920 [8]
Read total uncorrected errors: 0 [4]
Verify errors corrected w/o substantial delay: 29216 [4]
Verify errors corrected with possible delays: 0 [4]
Re-verifications: 0 [4]
Verify errors corrected: 29216 [4]
Times verification correction algorithm processed: 29216 [4]
Bytes verified: 1250054422528 [8]
Verify total uncorrected errors: 0 [4]
Total non-medium errors: 10 [4]
Temperature in degrees celsius: 31
Reference temperature in degrees celsius: 65
Logical blocks sent to initiators: 211094466 [4]
Logical blocks received from initators: 4164908548 [4]
Logical blocks read from cache, sent to initiators: 1645587723 [4]
Number of read and write commands <= current segment size: 984818539
[4]
Number of read and write commands > current segment size: 0 [4]
Write errors corrected with possible delays: 0 [4]
Re-writes: 0 [4]
Write errors corrected: 0 [4]
Times write correction algorithm processed: 0 [4]
Bytes written: 4374552894464 [8]
Write total uncorrected errors: 0 [4]
Read errors corrected w/o substantial delay: 4944654 [4]
Read errors corrected with possible delays: 1 [4]
Re-reads: 0 [4]
Read errors corrected: 4944655 [4]
Times read correction algorithm processed: 4944841 [4]
Bytes read: 65166111744000 [8]
Read total uncorrected errors: 0 [4]
Verify errors corrected w/o substantial delay: 29216 [4]
Verify errors corrected with possible delays: 0 [4]
Re-verifications: 0 [4]
Verify errors corrected: 29216 [4]
Times verification correction algorithm processed: 29216 [4]
Bytes verified: 1250054422528 [8]
Verify total uncorrected errors: 0 [4]
Total non-medium errors: 10 [4]
Temperature in degrees celsius: 30
Reference temperature in degrees celsius: 65
Logical blocks sent to initiators: 211094466 [4]
Logical blocks received from initators: 4164908548 [4]
Logical blocks read from cache, sent to initiators: 1645587723 [4]
Number of read and write commands <= current segment size: 984818539
[4]
Number of read and write commands > current segment size: 0 [4]
Self-test (reserved): Completed w/o error
Self-test (reserved): Completed w/o error
Self-test (reserved): Completed w/o error
Self-test (reserved): Completed w/o error
Self-test (reserved): Completed w/o error
Self-test (reserved): Completed w/o error
Self-test (reserved): Completed w/o error
Self-test (reserved): Completed w/o error
Self-test (reserved): Completed w/o error
Inquiry page 0h dump:
0000 00 00 03 12 9F 00 01 3E .......>
0008 49 42 4D 2D 45 53 58 53 IBM-ESXS
0010 53 54 33 33 36 36 30 35 ST336605
0018 4C 43 20 20 20 20 21 23 LC !#
0020 42 32 34 33 33 46 50 30 B2433FP0
0028 59 30 35 38 30 36 32 37 Y0580627
0030 42 32 34 33 20 20 20 20 B243
0038 0C 00 00 00 00 00 00 00 ........
0040 00 00 00 00 00 00 00 00 ........
0048 00 00 00 00 00 00 00 00 ........
0050 00 00 00 00 00 00 00 00 ........
0058 00 00 00 00 00 00 00 00 ........
0060 00 00 31 30 30 30 30 31 ..100001
0068 31 37 37 00 30 30 30 31 177.0001
0070 32 32 30 36 50 35 33 32 2206P532
0078 33 20 20 20 20 20 48 32 3 H2
0080 31 37 32 32 20 20 20 20 1722
0088 30 36 50 35 33 32 32 20 06P5322
0090 20 20 00 00 00 00 00 00 ......
0098 00 00 00 00 00 00 00 00 ........
00A0 00 00 00 00 00 .....

Hi.All. Could someone please tell me something about this state of
SCSI disk, is this a corrupt disk or is it usable ?
If usable, where could i use this kind of disk, it seems unreliable or
am i wrong?
What would be tolerance for errors corrected, as you can see every
error is simultaneously corrected.

Thanks.
Maybe at least you could direct me for some link or page...for Q about
hard disk eror tolerance .

Appreciated.
mm

 

[Paul]

Direct Access IBM-ESXS ST336605LC !# at ctrl 0/1.0
Firmware revision B243
Unit Serial Number: 3FP0Y058

Write errors corrected with possible delays: 0 [4]
Re-writes: 0 [4]
Write errors corrected: 0 [4]
Times write correction algorithm processed: 0 [4]
Bytes written: 4374552998912 [8]
Write total uncorrected errors: 0 [4]
Read errors corrected w/o substantial delay: 4944654 [4]
Read errors corrected with possible delays: 1 [4]
Re-reads: 0 [4]
Read errors corrected: 4944655 [4]
Times read correction algorithm processed: 4944841 [4]
Bytes read: 65166117543936 [8]
Read total uncorrected errors: 0 [4]
Verify errors corrected w/o substantial delay: 29216 [4]
Verify errors corrected with possible delays: 0 [4]
Re-verifications: 0 [4]
Verify errors corrected: 29216 [4]
Times verification correction algorithm processed: 29216 [4]
Bytes verified: 1250054422528 [8]
Verify total uncorrected errors: 0 [4]
Total non-medium errors: 10 [4]
Temperature in degrees celsius: 32
Reference temperature in degrees celsius: 65
Logical blocks sent to initiators: 211094466 [4]
Logical blocks received from initators: 4164908548 [4]
Logical blocks read from cache, sent to initiators: 1645587723 [4]
Number of read and write commands <= current segment size: 984818539
[4]
Number of read and write commands > current segment size: 0 [4]
Write errors corrected with possible delays: 0 [4]
Re-writes: 0 [4]
Write errors corrected: 0 [4]
Times write correction algorithm processed: 0 [4]
Bytes written: 4374552946688 [8]
Write total uncorrected errors: 0 [4]
Read errors corrected w/o substantial delay: 4944654 [4]
Read errors corrected with possible delays: 1 [4]
Re-reads: 0 [4]
Read errors corrected: 4944655 [4]
Times read correction algorithm processed: 4944841 [4]
Bytes read: 65166112465920 [8]
Read total uncorrected errors: 0 [4]
Verify errors corrected w/o substantial delay: 29216 [4]
Verify errors corrected with possible delays: 0 [4]
Re-verifications: 0 [4]
Verify errors corrected: 29216 [4]
Times verification correction algorithm processed: 29216 [4]
Bytes verified: 1250054422528 [8]
Verify total uncorrected errors: 0 [4]
Total non-medium errors: 10 [4]
Temperature in degrees celsius: 31
Reference temperature in degrees celsius: 65
Logical blocks sent to initiators: 211094466 [4]
Logical blocks received from initators: 4164908548 [4]
Logical blocks read from cache, sent to initiators: 1645587723 [4]
Number of read and write commands <= current segment size: 984818539
[4]
Number of read and write commands > current segment size: 0 [4]
Write errors corrected with possible delays: 0 [4]
Re-writes: 0 [4]
Write errors corrected: 0 [4]
Times write correction algorithm processed: 0 [4]
Bytes written: 4374552894464 [8]
Write total uncorrected errors: 0 [4]
Read errors corrected w/o substantial delay: 4944654 [4]
Read errors corrected with possible delays: 1 [4]
Re-reads: 0 [4]
Read errors corrected: 4944655 [4]
Times read correction algorithm processed: 4944841 [4]
Bytes read: 65166111744000 [8]
Read total uncorrected errors: 0 [4]
Verify errors corrected w/o substantial delay: 29216 [4]
Verify errors corrected with possible delays: 0 [4]
Re-verifications: 0 [4]
Verify errors corrected: 29216 [4]
Times verification correction algorithm processed: 29216 [4]
Bytes verified: 1250054422528 [8]
Verify total uncorrected errors: 0 [4]
Total non-medium errors: 10 [4]
Temperature in degrees celsius: 30
Reference temperature in degrees celsius: 65
Logical blocks sent to initiators: 211094466 [4]
Logical blocks received from initators: 4164908548 [4]
Logical blocks read from cache, sent to initiators: 1645587723 [4]
Number of read and write commands <= current segment size: 984818539
[4]
Number of read and write commands > current segment size: 0 [4]
Self-test (reserved): Completed w/o error
Self-test (reserved): Completed w/o error
Self-test (reserved): Completed w/o error
Self-test (reserved): Completed w/o error
Self-test (reserved): Completed w/o error
Self-test (reserved): Completed w/o error
Self-test (reserved): Completed w/o error
Self-test (reserved): Completed w/o error
Self-test (reserved): Completed w/o error
Inquiry page 0h dump:
0000 00 00 03 12 9F 00 01 3E .......>
0008 49 42 4D 2D 45 53 58 53 IBM-ESXS
0010 53 54 33 33 36 36 30 35 ST336605
0018 4C 43 20 20 20 20 21 23 LC !#
0020 42 32 34 33 33 46 50 30 B2433FP0
0028 59 30 35 38 30 36 32 37 Y0580627
0030 42 32 34 33 20 20 20 20 B243
0038 0C 00 00 00 00 00 00 00 ........
0040 00 00 00 00 00 00 00 00 ........
0048 00 00 00 00 00 00 00 00 ........
0050 00 00 00 00 00 00 00 00 ........
0058 00 00 00 00 00 00 00 00 ........
0060 00 00 31 30 30 30 30 31 ..100001
0068 31 37 37 00 30 30 30 31 177.0001
0070 32 32 30 36 50 35 33 32 2206P532
0078 33 20 20 20 20 20 48 32 3 H2
0080 31 37 32 32 20 20 20 20 1722
0088 30 36 50 35 33 32 32 20 06P5322
0090 20 20 00 00 00 00 00 00 ......
0098 00 00 00 00 00 00 00 00 ........
00A0 00 00 00 00 00 .....

Hi.All. Could someone please tell me something about this state of
SCSI disk, is this a corrupt disk or is it usable ?
If usable, where could i use this kind of disk, it seems unreliable or
am i wrong?
What would be tolerance for errors corrected, as you can see every
error is simultaneously corrected.

Thanks.
Maybe at least you could direct me for some link or page...for Q about
hard disk eror tolerance .

Appreciated.
mm

The drive may see errors, but that is why it has error
correction algorithms built in. Only one event was marked
as requiring so much attention as to cause a delay. That
might affect performance, or cause the command to time out.

Read errors corrected with possible delays: 1 [4]

SCSI disks are nice, in that the interface allows the
"factory defect list" and the "grown defect list" to be
extracted from the drive. If you keep track of the grown
defect list, and how quickly it is growing with time, that
can give an idea of the potential health of the disk.

The purpose of the factory defect list, is in case you ever
need to format the drive. By restoring the factory defect list,
you can mark the bad blocks that were known at the factory.
The grown defect list, on the other hand, are the errors that
are detected while the disk is being used.

For some of the SCSI disks I had, but no longer use, the disks
passed all possible tests you could run. I stopped using them
because the bearing noise was getting so bad, I no longer
trusted the drives to hold valuable data. And that is a
subjective decision you're going to have to make at some point.

As well, there are some drives, taken from old server equipment,
which are just too noisy for desktop usage. One IBM drive,
lets off a "squeak" every 71 seconds, as a form of internal
self test, and a desktop user would rapidly be driven insane
by that noise. So not every spare SCSI disk taken from old
server equipment is worth having. Some should be left in the
server room.

I used to have seven SCSI drives in a computer, and eventually
replaced them with one IDE drive. The noise situation is much
improved.

Paul

 

[comitter]

Direct Access IBM-ESXS ST336605LC    !# at ctrl 0/1.0
Firmware revision B243
Unit Serial Number: 3FP0Y058

Write errors corrected with possible delays: 0 [4]
Re-writes: 0 [4]
Write errors corrected: 0 [4]
Times write correction algorithm processed: 0 [4]
Bytes written: 4374552998912 [8]
Write total uncorrected errors: 0 [4]
Read errors corrected w/o substantial delay: 4944654 [4]
Read errors corrected with possible delays: 1 [4]
Re-reads: 0 [4]
Read errors corrected: 4944655 [4]
Times read correction algorithm processed: 4944841 [4]
Bytes read: 65166117543936 [8]
Read total uncorrected errors: 0 [4]
Verify errors corrected w/o substantial delay: 29216 [4]
Verify errors corrected with possible delays: 0 [4]
Re-verifications: 0 [4]
Verify errors corrected: 29216 [4]
Times verification correction algorithm processed: 29216 [4]
Bytes verified: 1250054422528 [8]
Verify total uncorrected errors: 0 [4]
Total non-medium errors: 10 [4]
Temperature in degrees celsius: 32
Reference temperature in degrees celsius: 65
Logical blocks sent to initiators: 211094466 [4]
Logical blocks received from initators: 4164908548 [4]
Logical blocks read from cache, sent to initiators: 1645587723 [4]
Number of read and write commands <= current segment size: 984818539
[4]
Number of read and write commands > current segment size: 0 [4]
Write errors corrected with possible delays: 0 [4]
Re-writes: 0 [4]
Write errors corrected: 0 [4]
Times write correction algorithm processed: 0 [4]
Bytes written: 4374552946688 [8]
Write total uncorrected errors: 0 [4]
Read errors corrected w/o substantial delay: 4944654 [4]
Read errors corrected with possible delays: 1 [4]
Re-reads: 0 [4]
Read errors corrected: 4944655 [4]
Times read correction algorithm processed: 4944841 [4]
Bytes read: 65166112465920 [8]
Read total uncorrected errors: 0 [4]
Verify errors corrected w/o substantial delay: 29216 [4]
Verify errors corrected with possible delays: 0 [4]
Re-verifications: 0 [4]
Verify errors corrected: 29216 [4]
Times verification correction algorithm processed: 29216 [4]
Bytes verified: 1250054422528 [8]
Verify total uncorrected errors: 0 [4]
Total non-medium errors: 10 [4]
Temperature in degrees celsius: 31
Reference temperature in degrees celsius: 65
Logical blocks sent to initiators: 211094466 [4]
Logical blocks received from initators: 4164908548 [4]
Logical blocks read from cache, sent to initiators: 1645587723 [4]
Number of read and write commands <= current segment size: 984818539
[4]
Number of read and write commands > current segment size: 0 [4]
Write errors corrected with possible delays: 0 [4]
Re-writes: 0 [4]
Write errors corrected: 0 [4]
Times write correction algorithm processed: 0 [4]
Bytes written: 4374552894464 [8]
Write total uncorrected errors: 0 [4]
Read errors corrected w/o substantial delay: 4944654 [4]
Read errors corrected with possible delays: 1 [4]
Re-reads: 0 [4]
Read errors corrected: 4944655 [4]
Times read correction algorithm processed: 4944841 [4]
Bytes read: 65166111744000 [8]
Read total uncorrected errors: 0 [4]
Verify errors corrected w/o substantial delay: 29216 [4]
Verify errors corrected with possible delays: 0 [4]
Re-verifications: 0 [4]
Verify errors corrected: 29216 [4]
Times verification correction algorithm processed: 29216 [4]
Bytes verified: 1250054422528 [8]
Verify total uncorrected errors: 0 [4]
Total non-medium errors: 10 [4]
Temperature in degrees celsius: 30
Reference temperature in degrees celsius: 65
Logical blocks sent to initiators: 211094466 [4]
Logical blocks received from initators: 4164908548 [4]
Logical blocks read from cache, sent to initiators: 1645587723 [4]
Number of read and write commands <= current segment size: 984818539
[4]
Number of read and write commands > current segment size: 0 [4]
Self-test (reserved): Completed w/o error
Self-test (reserved): Completed w/o error
Self-test (reserved): Completed w/o error
Self-test (reserved): Completed w/o error
Self-test (reserved): Completed w/o error
Self-test (reserved): Completed w/o error
Self-test (reserved): Completed w/o error
Self-test (reserved): Completed w/o error
Self-test (reserved): Completed w/o error
Inquiry page 0h dump:
0000  00 00 03 12 9F 00 01 3E  .......>
0008  49 42 4D 2D 45 53 58 53  IBM-ESXS
0010  53 54 33 33 36 36 30 35  ST336605
0018  4C 43 20 20 20 20 21 23  LC    !#
0020  42 32 34 33 33 46 50 30  B2433FP0
0028  59 30 35 38 30 36 32 37  Y0580627
0030  42 32 34 33 20 20 20 20  B243
0038  0C 00 00 00 00 00 00 00  ........
0040  00 00 00 00 00 00 00 00  ........
0048  00 00 00 00 00 00 00 00  ........
0050  00 00 00 00 00 00 00 00  ........
0058  00 00 00 00 00 00 00 00  ........
0060  00 00 31 30 30 30 30 31  ..100001
0068  31 37 37 00 30 30 30 31  177.0001
0070  32 32 30 36 50 35 33 32  2206P532
0078  33 20 20 20 20 20 48 32  3     H2
0080  31 37 32 32 20 20 20 20  1722
0088  30 36 50 35 33 32 32 20  06P5322
0090  20 20 00 00 00 00 00 00    ......
0098  00 00 00 00 00 00 00 00  ........
00A0  00 00 00 00 00           .....

Hi.All. Could someone please tell me something about this state of
SCSI disk, is this a corrupt disk or is it usable ?
If usable, where could i use this kind of disk, it seems unreliable or
am i wrong?
What would be tolerance for errors corrected, as you can see every
error is simultaneously corrected.

Thanks.
Maybe at least you could direct me for some link or page...for Q about
hard disk eror tolerance .

Appreciated.
mm

The drive may see errors, but that is why it has error
correction algorithms built in. Only one event was marked
as requiring so much attention as to cause a delay. That
might affect performance, or cause the command to time out.

Read errors corrected with possible delays: 1 [4]

SCSI disks are nice, in that the interface allows the
"factory defect list" and the "grown defect list" to be
extracted from the drive. If you keep track of the grown
defect list, and how quickly it is growing with time, that
can give an idea of the potential health of the disk.

The purpose of the factory defect list, is in case you ever
need to format the drive. By restoring the factory defect list,
you can mark the bad blocks that were known at the factory.
The grown defect list, on the other hand, are the errors that
are detected while the disk is being used.

For some of the SCSI disks I had, but no longer use, the disks
passed all possible tests you could run. I stopped using them
because the bearing noise was getting so bad, I no longer
trusted the drives to hold valuable data. And that is a
subjective decision you're going to have to make at some point.

As well, there are some drives, taken from old server equipment,
which are just too noisy for desktop usage. One IBM drive,
lets off a "squeak" every 71 seconds, as a form of internal
self test, and a desktop user would rapidly be driven insane
by that noise. So not every spare SCSI disk taken from old
server equipment is worth having. Some should be left in the
server room.

I used to have seven SCSI drives in a computer, and eventually
replaced them with one IDE drive. The noise situation is much
improved.

    Paul- Sakrij citirani tekst -

- Prikaži citirani tekst -

Yeah, it had taken a while i've learned SCSI basics. Most of the older
disks seem fine, clean lists, very few factory defects, but must
confirm that they are mostly loudy, of course for desktop PC-s,
ie.usual stuff. Most, of very fine quality made, like a painting. I
bumped on only one which gave me a headache with sounds arising from
it, but lucky for the disk, i was calmed Just trying to find out,
what would be some tolerant/critical point over which SCSI HDD becomes
a danger for storing or serving as a string for data flow, perhaps
that would be that first error or second, it's obviously subjective
decision as you have already said and mostly depends about those
rustle papers.

This one goes into dismantling.period. Although this one is fully
quiet, only starting it, gives his personal voices, i suspect every
one has it own sounds, and a very good-hearing man and a long-year
scsi technician could discern every SCSI HDD's store-quality only by
it's starting sound.

Tnx Paul