User manual

ManualsBrandsSeagate ManualsAutomobile AccessoriesST3655N

SANtools® S.M.A.R.T. Disk Monitor (SMARTMon-UX)66

Number of read and write commands <= current segment size: 366966 [4]

Number of read and write commands > current segment size: 76687 [4]

Power-on time in minutes: 38260 [4]

Time in minutes until the next scheduled interrupt for a S.M.A.R.T. measurement: 66 [4]

Write errors corrected with possible delays: 0 [4]

Total write errors: 0 [4]

Write errors corrected: 0 [4]

Times correction algorithm processed (on writes): 0 [4]

Bytes processed (on writes): 3401038336 [8]

Unrecovered errors (on writes): 0 [4]

Read errors corrected without substantial delay: 887 [4]

Read errors corrected with possible delays: 0 [4]

Total read errors: 0 [4]

Read errors corrected: 887 [4]

Times correction algorithm processed (on reads): 887 [4]

Bytes processed (on reads): 88372689408 [8]

Unrecovered errors (on reads): 0 [4]

Verify errors corrected without substantial delay: 0 [4]

Verify errors corrected with possible delays: 0 [4]

Total verify errors: 0 [4]

Verify errors corrected: 0 [4]

Times correction algorithm processed (on verifys): 0 [4]

Bytes processed (on verifys): 0 [8]

Unrecovered errors (on verifys): 0 [4]

Total Non-medium errors: 0 [4]

Current temperature +/- 3 degrees C: 37

Reference temperature +/- 3 degrees C: 65

Self-test (extended background): FAILED in segment #0 at Block #00000000 000238CFh @ 214 powered hours

[Drive media failed] Unrecovered read error ASC=11 ASCQ=00, SelfTestByte=00, VendorSpecificByte=E4

Self-test (short background): Completed w/o error @ 134 powered hours

Self-test (short background): Completed w/o error @ 24 powered hours

Self-test (standard): Completed w/o error @ 1 powered hours

Terminating program.

If you sent the command with the -Cx option, then the numbers in brackets would be suppressed. The bracketized

field shows you how many bytes the selected peripheral allocates for the resulting data. This is useful in the event you

need to assess the possibility that the field rolled over (like an odometer).

# /etc/smartmon-ux -Cx

Discovered SEAGATE ST336605FC S/N "3FP009Z6" on /hw/scsi/sc2d66l0 [SES] (SMART enabled) (34732 MB)

Statistical log pages dump below [# of bytes reserved for value in device]:

Port receiving this command 0=A, 1=B: 1

Port A link failure count: 0

Port A loss of synchronization count: 2

...

There are some interesting things to see here:

· Read or Write errors - We have 887 corrected read errors. Note that your operating system would not report

recovered errors, only unrecovered errors. Recovered errors means your system successfully retried the operation,

but this cost you I/O and CPU cycles. If you had any Unrecovered errors, you have some corrupted data.

· Number of minutes drive has been powered on. This disk has been powered on for 38260 minutes, nearly a

month. This is a Seagate-specific setting, and certain models of disk report this value as minutes since LAST power

on, while other disks report this as cumulative minutes drive has been powered on since leaving the factory. We do

not differentiate between the two, because there is no 100% infallible way to tell the difference. By looking at the

other statistics, however, we can make an educated guess that the drive has been up a week since last power

cycle. We can tell by examining the cumulative blocks read. Our IRIX box is only used for compiling and testing

code, so having 17GBs read in the 6 months we have had it is reasonable and having read 17GBs in last week is

not correct.

· The number in parentheses to the right of each value tells you how many bytes that the disk maintains to store

these values.

· Use that to make a judgment call to see if you have had an overflow. The disk drive does not maintain an overflow

counter, so there is no way to know if you really did have a field overflow.

· You can see that the disk processed 83,780,118 blocks, but only had 45,424,812 cache hits. That corresponds to

over a 54% read cache hit rate.