Repairing of Samsung drives (BURN process)

[Igor]

Resources of Burn tests for Samsung drives can be found on the CD supplied with the kit of PC-3000 complex or in Personal Update box on our server.

In order to use the resources, you should open the database window: aˆ?Tools →Databaseaˆ? and import the required set of resources. In order to launch testing, Burn Code has to be written to a HDD. After searching through the database you will have to determine which of the found files must be written to drive.

For VICTOR, PUMA, VICTORPLUS, and VERNA drives the utility may find several folders containing resources. The name of the source folder containing Burn Code must correspond to the letter code on the driveaˆ™s side label. It means, that if the utility has found folders aˆ?PUMA/Burn Resources 01.06.2005/SP4002H/XXXRaˆ? and aˆ?PUMA/Burn Resources 01.06.2005/SP4002H/XXXSaˆ? for a SP4002H drive with QUMSC code on label, you should select the second one.

Before you rewrite the resources and launch testing, you should back up the driveaˆ™s modules and ROM. You are advised to prepare a separate power supply cable to power the drive during the test, because it may take from 6 hours to 2 days (depending upon the HDD condition).

If the set of resources for a HDD includes HT code, you are advised to perform additional testing and Burn test configuration.
The following actions must precede test launch:
1.Launch the utility in ''Safe mode'' to write HT code or Burn code (the latter applies to models from VICTOR, PUMA to VERNA, VERNALITE). After HT code recording and testing you should write Burn Code.
2. Write the following BURN resources to the drive :
− aˆ?BURN-IN Scriptaˆ?
− aˆ?Overlayaˆ? (necessary for VERNA, VERNALITE, and VANGO only)
− aˆ?Burn Codeaˆ? or aˆ?DownSize Burn Codeaˆ?;
3. Switch the driveaˆ™s power off and on again.

After that the drive will wait for 5 minutes and launch the test then. During the wait interval and testing all status registers are off. If you send a soft reset signal during that period, the drive will switch to aˆ?readyaˆ? status and will be able to access its service area (switch power off and on again to restart test). If a drive has immediately reached readiness, then BURN-IN Script header is: END or FAIL. An error during Burn Code recording is also possible.
If you connect a HDD to terminal during test, you can notice that the drive outputs a message when it launches each test and performs certain operations.
After test completion, the drive must stop the spindle and start continuous blinking with the LED. Test completion can also be easily identified in terminal, where the drive constantly outputs aˆ?LED 00 0000aˆ? strings aˆ“
aˆ?LEDaˆ? means the blinking mode, aˆ?00aˆ? aˆ“ positive result code, other values mean an error. In monitoring mode the aˆ?Stop conditionaˆ? field will contain completion code and its description instead of "No Value" string. If the drive does not stop the spindle and does not demonstrate any other signs of test completion for a very long period (more than 24 hours), you can interrupt the test sending a reset signal to drive or switching its power supply off; then you can check test status using the BISPT module header. If the header is CONT, the test must be resumed, if it is END aˆ“ test has been completed successfully, FAIL means that the test has been erminated because of errors.

After successful completion of the testing procedure you should write to ROM aˆ?Main Codeaˆ? or aˆ?DownSize Main Codeaˆ? depending upon the Burn Code loaded before test, i.e. for aˆ?DownSizeaˆ? models you should load
aˆ?DownSize Main Codeaˆ?. After loading, switch the driveaˆ™s power supply off and on again aˆ“ now it is ready for work.