User manual

ManualsBrandsSeagate ManualsAutomobile AccessoriesST3655N

121

122

123

124

125

126

127

128

129

130

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

Program Ended.

Completion and Test Time

The -scrub command reports errors at the block level, by reading each block individually. As such, it sacrifices

speed for granularity. Our 146GB 15000RPM SAS disk takes 10 hours to complete using these options. If you don't

care about individual block numbers, but still want a count of the bad blocks, then use the -scrubq which reads 32

blocks at a time. The same disk that took 10 hours to test with the -scrubq command takes 32 minutes to complete.

If you just need a pass-fail test too see if a particular disk has any read problems, then be sure to add the -scrubt

option so that it terminates on the first error. The results below were run on the same disk which has bad blocks

which we created with this software on blocks 123 and 456.

Slow, Detailed Report

# time /etc/smartmon-ux -scrub /dev/rdsk/c4t15d0s0

Discovered SEAGATE ST3146855SS S/N "3LN29ZZ5" on /dev/rdsk/c4t15d0s0 (Not Enabling SMART)(140014 MB)

Block scrubbing error summary:

Block 123 4/09/00 Count=3 [Controller/drive hardware failed] Track following error

Block 456 4/09/00 Count=3 [Controller/drive hardware failed] Track following error

Program Ended.

real 10h35m40.22s

user 27m8.57s

sys 2h43m53.15s

Faster Report

# time ./smartmon-ux -scrubq /dev/rdsk/c4t15d0s0

Discovered SEAGATE ST3146855SS S/N "3LN29ZZ5" on /dev/rdsk/c4t15d0s0 (Not Enabling SMART)(140014 MB)

Block scrubbing error summary:

Blocks 96 - 112 4/09/00 Count=3 [Controller/drive hardware failed] Track following error

Blocks 448 - 464 4/09/00 Count=3 [Controller/drive hardware failed] Track following error

Program Ended.

real 32m15.85s

user 2m20.74s

sys 5m18.14s

Fastest

# time ./smartmon-ux -scrubq -scrubt /dev/rdsk/c4t15d0s0

Discovered SEAGATE ST3146855SS S/N "3LN29ZZ5" on /dev/rdsk/c4t15d0s0 (Not Enabling SMART)(140014 MB)

Block scrubbing error summary:

Blocks 96 - 128 4/09/00 Count=1 [Controller/drive hardware failed] Track following error

real 0m1.67s

user 0m0.00s

sys 0m0.02s

If your disks support background media scanning, then you can just ask the disk if it has any problems via the -bmsr

command (assuming scanning is enabled). This will generate a report based on the last background scan the

selected disk ran, and any subsequent activity since that scan. It will take less than a second to report all bad blocks

on the disk, regardless of how many you have and where they are located. The disk retains this information through

power-cycles.

217