User manual

ManualsBrandsSeagate ManualsAutomobile AccessoriesST3655N

111

112

113

114

115

116

117

118

119

120

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

Self-test (Short offline) completed - FAILED with read error at block #00000000 00016C0F at 13544 powered

hours

Self-test (Short offline) completed - FAILED with read error at block #00000000 00016C0F at 13544 powered

hours

Self-test (Short offline) completed - FAILED with read error at block #00000000 00016C0F at 12810 powered

hours

Self-test (Short offline) completed - FAILED with read error at block #00000000 00016C0F at 12810 powered

hours

Self-test (Short offline) completed - FAILED with read error at block #00000000 00016C0F at 12810 powered

hours

Self-test (Short offline) completed - FAILED with read error at block #00000000 00016C0F at 12810 powered

hours

Self-test (Extended offline) completed - FAILED with read error at block #00000000 00016C0F at 12809

powered hours

Program Ended.

Above also returned immediately. We can see that there is a bad block at hex address 00016C0F. We can also see

that this same bad block consistently appears in all of the self-tests we ran while creating this section of the manual.

Now compare with the results of running the -verify on the same disk. The -verify took nearly 30 minutes,

but it returned all 3 bad blocks.

smartmon-ux -verify \\.\PhysicalDrive1

Discovered Maxtor 6L100P0 S/N "L23MTW0G" on \\.\PhysicalDrive1 (SMART Enabled)

The current device temperature is: 39C (102F) degrees

Beginning SANtools read/verify test for Maxtor 6L100P0 at \\.\PhysicalDrive1 (195813072 blocks, blocksize=512)

Read/Verify error summary:

Event# PowerOnMins HexBlockNumber State Reassignment Status AdditionalInfo

0 - 16c0f ERR reassign failed, data invalid Block 93184 ERR/DEV/STAT:

00/F0/51 Error: DRDY, DSC, ERR

1 - 219a7 ERR reassign failed, data invalid Block 137472 ERR/DEV/STAT:

00/F0/51 Error: DRDY, DSC, ERR

2 - 21a19 ERR reassign failed, data invalid Block 137728 ERR/DEV/STAT:

00/F0/51 Error: DRDY, DSC, ERR

Self-Tests FAQ

Q. What are the dangers of running a self-test?

A. Worst-case scenario, if you kick off a foreground self test on the disk that your operating system is booted to, then

you will crash your O/S, and your disk will be unresponsive until either the self-test completes or you power cycle the

disk. Our software does not care or warn the operator if they run such a test on the boot disk Sometimes this is the

only thing you can do if you want to run tests on your boot disk. We will not second-guess you or stand in your way.

At the conclusion of a self-test, then you may have to recycle power on the peripheral, especially if you ran a

foreground test. Sometimes the host senses that the peripheral went away, so it stops talking to it. Other times the

person(s) who wrote the self-test did it in such a way that requires a power cycle.

Q. What if the self-test locks up and I have to reboot, how do I know if it completed and get results?

A. The results of self-tests are non-volatile. Run smartmon-ux -stra or -str, depending on type of peripheral,

and it will report the results of the last few self-tests that the device ran.

Q. I have a lot of disks that need testing, can I run multiple self-tests concurrently?

A. Absolutely. In fact, if you run the extended background tests then you can easily test 100 disk drives at the same

time with near zero host overhead. The self-tests run inside of the selected peripheral's CPU and firmware. Note that

some peripherals unfortunately lock up a peripheral during a self-test, so if this affects your device, then run multiple

instances of SMARTMonUX.

Q. Why do self tests and other functions not work on USB and sometimes SATA disks?

A. The most common problem with USB and SATA/ATA disks is that the command isn't getting properly translated to

the disk. When you hook up a ATA/SATA device to a USB port, part of the process is that a bridge chip translates the

native ATA commands that the disk uses to SCSI commands that the USB protocol uses. The low-level commands

165