Host Interface
Sense | ASC | ASCQ | Error description | |
Key | ||||
|
|
| ||
|
|
|
| |
B | 4E | 00 | OVERLAPPED COMMAND ATTEMPTED | |
|
|
|
| |
4 | 53 | 00 | MEDIA LOAD OR EJECT FAILED | |
5 | 53 | 02 | MEDIUM REMOVAL PREVENTED | |
4 | 83 | 00 | THERMAL ERROR | |
|
|
|
|
Table 4.47 shows the format of the
Table 4.47 Format progress indication bytes
Bit | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | |
Byte | |||||||||
|
|
|
|
|
|
|
| ||
|
|
|
|
|
|
|
|
| |
15 | SKSV |
|
|
| Reserved |
|
|
| |
|
|
| Progress Indication |
|
|
| |||
|
|
|
|
|
|
|
|
|
Progress Indication indicates the rate of formatting completion when the denominator is 65536 (10000h).
INIT should not use the REQUEST SENSE command alone to check the ODD status. Because the REQUEST SENSE command is used by INIT to retrieve sense data that is held by the ODD on various occasions, the contents of the sense data depend on the results of the command executed previously.
Example: Response when the ODD is in Not Ready state When INIT issues the TEST UNIT READY command, the ODD ends processing with Check Condition Status and responds to the REQUEST SENSE command with Not Ready Sense Data. When the INIT issues the INQUIRY command, the ODD responds with Inquiry Data and ends processing with Good status. If INIT continuously issues the REQUEST SENSE command, the ODD responds with No Sense because the previous command has ended normally and the ODD holds no sense data.