Browse Prior Art Database

Enhanced Drive Self Test

IP.com Disclosure Number: IPCOM000247316D
Publication Date: 2016-Aug-22
Document File: 1 page(s) / 35K

Publishing Venue

The IP.com Prior Art Database

Abstract

Current manufacturing processes required drive testing / exercise to be performed using an external equipment that would drive the IO towards the drive.This can be expensive. Basically what we are looking for is drive self test tool to be implemented inside the drives, part of the microcode. that would give the ability to an external user to issue via SCSI commands or send diag, instructions to the drive to perform certain test. The idea is to move the computation burden from the Tester towards the drive, therefore with a fairly inexpensive tester one could run a multitude of drives.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 100% of the total text.

Page 01 of 1

Enhanced Drive Self Test


Basically the drive manufacturer will have to implement inside the drive code the functions that would be triggered externally by this commands.

This commands can be either implemented via a nbew SCIS command or as a parameter list to an already existing SCIS command or by any other modality.

1. Parameters to be passed to the command:
- Will use the send diag command.

PARAM1: write|read|verify|mixed


PARAM2: sequential|random|butterfly
PARAM3: patern(low freq | high freq | pseudo random)
PARAM4: nr_of_blocks exercised at a time
PARAM5: START_LBA|STOP_LBA
PARAM6: start|stop|run_time
PARAM7: SOE(stop on error)|ROE(run on error)

2. Commands needed to be implemented to provide the following results: - PROGRESS:
- % completed
- nr. of write, read, verify, mixed
- time passed.


- PASS|FAIL
- RC (Return Code)

3. Other environmental requirements
- Has to support JBOD.

- Has to support 512/522/524 format.

- Special log page for results for this diagnostic and to specify a log page that is consistent across all the drive vendors to provide

easier data analysis within IBM.


- DRIVE manufacturer will have to maintain compatibility between shippable (regular) code and the mfg only stress code.

1