List of Error Codes


 

ERROR messages generated by the Yamaha recorders:

The following list of error messages came directly from the MMC 3 SCSI Command Set Revision 9.0. The Yamaha Recorders are based on the MMC 3 & SPC SCSI Command Sets.

Note: Any Explanation preceded by "**" will not be from the MMC command set documents, but from Yamaha's technical support staff.  These explanation will be based on the technicians experience in the field and calls received from End Users. Any recommended solutions based on this previous experience may not work for your system, but in most cases there will be more than only one possible cause/solution.

 

Annex A Additional Sense Codes for CD (normative)

This annex lists error codes expected to be generated by CD devices. Specific commands specify that certain errors occur in response to certain conditions, but each command does not contain a comprehensive list of possible error conditions.

A.1.Error Reporting

Any error may be reported in response to any command due to the occurrence of a deferred error. For example, a write error may occur due to a cached write command and that error shall be reported in response to the next command.

Errors listed in Table A.2 are not caused by any specific commands but by actions outside the control of the initiator.

Table A.1 lists all errors that may be generated by CD devices. Not all errors are applicable to all devices.

 

Table A.1 - CD Device Sense Key, ASC and ASCQ Assignments

Sense Key
ASC
ASCQ
Type
Description
0
00
00
R
NO ADDITIONAL SENSE INFORMATION
b
00
06
R
I/O PROCESS TERMINATED
**
Loose or bad cable or cable connection; check termination and parity; check for bent pin on back of Yamaha were cable connects; replace SCSI Card
5
00
11
R
AUDIO PLAY OPERATION IN PROGRESS
**
Software conflict with SCSI Card or Mastering S/W
4
00
17
R
CLEANING REQUESTED
**
Clean Tray or Caddy; Clean disc; Send drive in for service.
3
02
00
R
NO SEEK COMPLETE
**
Try new brand of disc; Send drive in for service.
2
04
00
R
LOGICAL UNIT NOT READY, CAUSE NOT REPORTABLE
**
Retry with new disc; check cable connections and termination; isolate drive on SCSI Card and try again. If possible connect new another computer system.
2
04
01
R
LOGICAL UNIT IS IN PROCESS OF BECOMING READY
**
Very common error message, 90% of the time it’s caused by a command issued by the mastering software while the recorder is still in the process of writing data to the CD. Usually reloading the software resolves the issue or upgrading the mastering software to the latest release. This error is usually followed by a Buffer Underrun error message.
2
04
02
R
LOGICAL UNIT NOT READY, INITIALIZING CMD. REQUIRED
**
Very rare error message. Try different brand of recordable disc.
2
04
03
R
LOGICAL UNIT NOT READY, MANUAL INTERVENTION REQUIRED
** Very rare. Check for improperly loaded disc.
2
04
04
++R
LOGICAL UNIT NOT READY, FORMAT IN PROGRESS
** Mastering software or some other application improperly attempted to communicate to recorder during format process. Look for background software to disable, or disable Auto Insert Notification.
2
04
07
R
LOGICAL UNIT NOT READY, OPERATION IN PROGRESS
**
Normally caused by mastering software or driver on system attempting to communicate to our recorder is in the middle of a write operation. Look for background software to disable, or disable Auto Insert Notification.
2
04
08
R
LOGICAL UNIT NOT READY, LONG WRITE IN PROGRESS
**
This error is caused 95% of the time by a buffer underrun. The mastering software/system failed to transfer data to the buffer fast enough or another application interfered with the process.
4
05
00
R
LOGICAL UNIT DOES NOT RESPOND TO SELECTION
** Check mastering software for support features. Make sure the recorder supports the format or feature you have selected.
3
06
00
R
NO REFERENCE POSITION FOUND
**
Try a different brand of disc, if error repeats send drive in for repair.
5
07
00
R
MULTIPLE PERIPHERAL DEVICES SELECTED
** If attempting to write to more than one recorder at time, please refer to mastering software for tips.
4
08
00
R
LOGICAL UNIT COMMUNICATION FAILURE
**
Possible cable or termination conflict; refer to the Trouble Shooting Technical Manual from our web site at www.yamaha.co.jp/english/product/computer/tech/trouble.html and diagnose our drive with it.
4
08
01
R
LOGICAL UNIT COMMUNICATION TIME-OUT
** Process took too long and timed-out. Clean disc, tray/caddy and try again. Also check cables for good connection and termination.
4
08
02
R
LOGICAL UNIT COMMUNICATION PARITY ERROR
** Check parity settings for SCSI Card and parity jumper on back of recorder.
4
09
00
R
TRACK FOLLOWING ERROR
**
This is a very common error message and can be caused by the following…
  1. Poor Disc; "try two different brands of disc to rule out"
  2. Poor power supply; "try removing from external chassis and connect as internal", if you have an internal recorder, try a different power connector"
  3. Damaged/Defective Recorder
4
09
01
R
TRACKING SERVO FAILURE
**
Common Error message, caused by…
  1. Poor Disc; "try two different brands of disc to rule out"
  2. Poor power supply; "try removing from external chassis and connect as internal", if you have an internal recorder, try a different power connector"
  3. Damaged/Defective Recorder
4
09
02
R
FOCUS SERVO FAILURE
**
This is either poor disc or a damaged optical head on the recorder. Try two different brands of disc, and if both fail the drive is at fault.
4
09
03
R
SPINDLE SERVO FAILURE
**
Caused by poor disc; poorly inserted disc; or defective recorder.
4
09
04
R
HEAD SELECT FAULT
** Reinsert disc and if it happens again send the recorder in for service.
6
0A
00
R
ERROR LOG OVERFLOW
1
0B
00
R
WARNING
** Check previous error message for actual cause of problem.
1
0B
01
R
WARNING - SPECIFIED TEMPERATURE EXCEEDED
** Temperature must not exceed 40 degrees Celsius as measured from the bottom center of the recorder. Check for enough space for air flow between drives.
1
0B
02
R
WARNING - ENCLOSURE DEGRADED
3
0C
00
R
WRITE ERROR
**
Usually preceded by an error message that is the actual cause of your problem
3
0C
07
R
WRITE ERROR - RECOVERY NEEDED
3
0C
08
R
WRITE ERROR - RECOVERY FAILED
3
0C
09
R
WRITE ERROR - LOSS OF STREAMING
3
0C
0A
R
WRITE ERROR - PADDING BLOCKS ADDED
**
This error occurs when the buffer becomes empty during a write operation, and the Yamaha recorder attempts to prevent the buffer underrun when it finds the buffer empty by padding the CD with ZERO’s in the hopes the buffer is in the process of being filled and will be able to continue writing actual data soon

All values are in hex.


 

Table A.1 (cont.) - CD Device Sense Key, ASC and ASCQ Assignments

Sense Key
ASC
ASCQ
Type
Description
3
11
00
R
UNRECOVERED READ ERROR
**
Caused by source data being corrupted; or bad cable connection or termination issue.
3
11
01
++R
READ RETRIES EXHAUSTED
**
Possibly caused by source data; or poor recordable disc
3
11
02
++R
ERROR TOO LONG TO CORRECT
** ECC was unable to correct detected error on disc. Try a different brand of recordable disc or another source CD to duplicate from.
3
11
05
R
L-EC UNCORRECTABLE ERROR
3
11
06
R
CIRC UNRECOVERED ERROR
3
11
0F
R
ERROR READING UPC/EAN NUMBER
**
Normally caused by poor recordable disc.
3
11
10
R
ERROR READING ISRC NUMBER
**
If this is the only error message you get, the disc is more than likely at fault and you should try a different brand of disc.
b
11
11
++R
READ ERROR - LOSS OF STREAMING
**
Caused by poor disc; Software conflict with mastering software; defective CD Recorder.
3
15
00
R
RANDOM POSITIONING ERROR
**
This READ error can be caused by poor disc; someone bumping the drive during write operation; or a defective recorder.
3
15
01
R
MECHANICAL POSITIONING ERROR
**
If only happens once every 30 to 100 times of use, may be only someone bumping drive during operation. If consistent, the drive recorder is at fault and should be sent in for repair.
3
15
02
R
POSITIONING ERROR DETECTED BY READ OF MEDIUM
**
If only happens once every 30 to 100 times of use, may be only someone bumping drive during operation. If consistent, the drive recorder is at fault and should be sent in for repair.
1
17
00
R
RECOVERED DATA WITH NO ERROR CORRECTION APPLIED
**
Data was recovered but disc may have damage.
1
17
01
R
RECOVERED DATA WITH RETRIES
**
Data was recovered, but only after numerous retries to get the data from the source CD. CD may be damaged in some fashion.
1
17
02
R
RECOVERED DATA WITH POSITIVE HEAD OFFSET
**
Data was recovered but disc may have damage.
1
17
03
R
RECOVERED DATA WITH NEGATIVE HEAD OFFSET
**
Data was recovered but disc may have damage.
1
17
04
R
RECOVERED DATA WITH RETRIES AND/OR CIRC APPLIED
**
Data was recovered but disc may have damage.
1
17
05
R
RECOVERED DATA USING PREVIOUS SECTOR ID
**
Data was recovered but disc may have damage.
1
17
07
++R
RECOVERED DATA WITHOUT ECC - RECOMMEND REASSIGNMENT
**
Data was recovered but disc may have damage.
1
17
08
++R
RECOVERED DATA WITHOUT ECC - RECOMMEND REWRITE
**
Data was recovered but disc may have damage.
1
17
09
++R
RECOVERED DATA WITHOUT ECC - DATA REWRITTEN
1
18
00
R
RECOVERED DATA WITH ERROR CORRECTION APPLIED
**
Data was recovered but disc may have damage.
1
18
01
R
RECOVERED DATA WITH ERROR CORR. & RETRIES APPLIED
**
Data was recovered but disc may have damage.
1
18
02
R
RECOVERED DATA - DATA AUTO-REALLOCATED
**
Data was recovered but disc may have damage.
1
18
03
R
RECOVERED DATA WITH CIRC
**
Data was recovered but disc may have damage.
1
18
04
R
RECOVERED DATA WITH L-EC
**
Data was recovered but disc may have damage.
1
18
05
R
RECOVERED DATA - RECOMMEND REASSIGNMENT
1
18
06
R
RECOVERED DATA - RECOMMEND REWRITE
**
Data was recovered but disc may have damage.
5
1A
00
R
PARAMETER LIST LENGTH ERROR
4
1B
00
R
SYNCHRONOUS DATA TRANSFER ERROR
** The Yamaha CDR4xx & CRW4xx recorders only support Asynchronous data transfer.
a
1D
00
++R
MISCOMPARE DURING VERIFY OPERATION
**
Possible poor disc, or recorder off alignment
5
20
00
R
INVALID COMMAND OPERATION CODE
**
Check with software developer, or reinstall your mastering software application and try again.
5
21
00
R
LOGICAL BLOCK ADDRESS OUT OF RANGE
**
Possible poor disc; Attempting to write over 650MB of data to the CD; mastering software bug or conflict.
5
21
01
R
INVALID ELEMENT ADDRESS
5
24
00
R
INVALID FIELD IN CDB
** Possible
mastering software bug, please check with developer of your mastering software. Also be sure to have the latest firmware for Yamaha Recorder.
5
25
00
R
LOGICAL UNIT NOT SUPPORTED
**
Check with your mastering software developer to see if they support your model recorder.

All values are in hex.

 

Table A.1 (cont.) - CD Device Sense Key, ASC and ASCQ Assignments

Sense Key
ASC
ASCQ
Type
Description

Note: If your error message falls within this field, your problem is more than likely software related. Please contact the developer of your mastering software with regards to any error messages below.

5
26
00
R
INVALID FIELD IN PARAMETER LIST
5
26
01
R
PARAMETER NOT SUPPORTED
5
26
02
R
PARAMETER VALUE INVALID
5
26
03
R
THRESHOLD PARAMETERS NOT SUPPORTED
5
26
04
R
INVALID RELEASE OF ACTIVE PERSISTENT RESERVATION
5
27
00
++R
WRITE PROTECTED
5
27
01
++R
HARDWARE WRITE PROTECTED
5
27
02
++R
LOGICAL UNIT SOFTWARE WRITE PROTECTED
5
27
03
++R
ASSOCIATED WRITE PROTECT
5
27
04
++R
PERSISTENT WRITE PROTECT
5
27
05
++R
PERMANENT WRITE PROTECT
6
28
00
R
NOT READY TO READY CHANGE, MEDIUM MAY HAVE CHANGED
6
28
01
R
IMPORT OR EXPORT ELEMENT ACCESSED
6
29
00
R
POWER ON, RESET, OR BUS DEVICE RESET OCCURRED
6
29
01
R
POWER ON OCCURRED
6
29
02
R
SCSI BUS RESET OCCURRED
6
29
03
R
BUS DEVICE RESET FUNCTION OCCURRED
6
29
04
R
DEVICE INTERNAL RESET
6
2A
00
R
PARAMETERS CHANGED
6
2A
01
R
MODE PARAMETERS CHANGED
6
2A
02
R
LOG PARAMETERS CHANGED
6
2A
03
R
RESERVATIONS PREEMPTED
5
2B
00
R
COPY CANNOT EXECUTE SINCE HOST CANNOT DISCONNECT
5
2C
00
R
COMMAND SEQUENCE ERROR
5
2C
03
R
CURRENT PROGRAM AREA IS NOT EMPTY
5
2C
04
R
CURRENT PROGRAM AREA IS EMPTY
6
2F
00
R
COMMANDS CLEARED BY ANOTHER INITIATOR
2
30
00
R
INCOMPATIBLE MEDIUM INSTALLED
2
30
01
R
CANNOT READ MEDIUM - UNKNOWN FORMAT
2
30
02
R
CANNOT READ MEDIUM - INCOMPATIBLE FORMAT
2
30
03
++R
CLEANING CARTRIDGE INSTALLED
2
30
04
R
CANNOT WRITE MEDIUM - UNKNOWN FORMAT
2
30
05
R
CANNOT WRITE MEDIUM - INCOMPATIBLE FORMAT
2
30
06
++R
CANNOT FORMAT MEDIUM - INCOMPATIBLE MEDIUM
2
30
07
R
CLEANING FAILURE
5
30
08
R
CANNOT WRITE - APPLICATION CODE MISMATCH
5
30
09
R
CURRENT SESSION NOT FIXATED FOR APPEND

All values are in hex.

 

Table A.1 (cont.) - CD Device Sense Key, ASC and ASCQ Assignments

Sense Key
ASC
ASCQ
Type
Description
3
31
00
R
MEDIUM FORMAT CORRUPTED
3
31
01
R
FORMAT COMMAND FAILED
 
34
00
R
ENCLOSURE FAILURE
 
35
00
R
ENCLOSURE SERVICES FAILURE
 
35
01
R
UNSUPPORTED ENCLOSURE FUNCTION
 
35
02
R
ENCLOSURE SERVICES UNAVAILABLE
 
35
03
R
ENCLOSURE SERVICES TRANSFER FAILURE
 
35
04
R
ENCLOSURE SERVICES TRANSFER REFUSED
1
37
00
R
ROUNDED PARAMETER
5
39
00
R
SAVING PARAMETERS NOT SUPPORTED
2
3A
00
R
MEDIUM NOT PRESENT
2
3A
01
++R
MEDIUM NOT PRESENT - TRAY CLOSED
2
3A
02
++R
MEDIUM NOT PRESENT - TRAY OPEN
6
3B
0D
R
MEDIUM DESTINATION ELEMENT FULL
6
3B
0E
R
MEDIUM SOURCE ELEMENT EMPTY
6
3B
0F
R
END OF MEDIUM REACHED
6
3B
11
R
MEDIUM MAGAZINE NOT ACCESSIBLE
6
3B
12
R
MEDIUM MAGAZINE REMOVED
6
3B
13
R
MEDIUM MAGAZINE INSERTED
6
3B
14
R
MEDIUM MAGAZINE LOCKED
6
3B
15
R
MEDIUM MAGAZINE UNLOCKED
5
3D
00
R
INVALID BITS IN IDENTIFY MESSAGE
2
3E
00
R
LOGICAL UNIT HAS NOT SELF-CONFIGURED YET
4
3E
01
++R
LOGICAL UNIT FAILURE
4
3E
02
++R
TIMEOUT ON LOGICAL UNIT
6
3F
00
R
TARGET OPERATING CONDITIONS HAVE CHANGED
6
3F
01
R
MICROCODE HAS BEEN CHANGED
6
3F
02
R
CHANGED OPERATING DEFINITION
6
3F
03
R
INQUIRY DATA HAS CHANGED
4
40
NN
R
DIAGNOSTIC FAILURE ON COMPONENT NN (80H-FFH)
5
43
00
R
MESSAGE ERROR
4
44
00
R
INTERNAL TARGET FAILURE
b
45
00
R
SELECT OR RESELECT FAILURE
4
46
00
R
UNSUCCESSFUL SOFT RESET
4
47
00
R
SCSI PARITY ERROR
b
48
00
R
INITIATOR DETECTED ERROR MESSAGE RECEIVED
b
49
00
R
INVALID MESSAGE ERROR

All values are in hex.

 

Table A.1 (cont.) - CD Device Sense Key, ASC and ASCQ Assignments

Sense Key
ASC
ASCQ
Type
Description
4
4A
00
R
COMMAND PHASE ERROR
4
4B
00
R
DATA PHASE ERROR
4
4C
00
R
LOGICAL UNIT FAILED SELF-CONFIGURATION
b
4D
NN
R
TAGGED OVERLAPPED COMMANDS (NN = QUEUE TAG)
b
4E
00
R
OVERLAPPED COMMANDS ATTEMPTED
3
51
00
++R
ERASE FAILURE
4
53
00
R
DISC LOAD OR EJECT FAILED
5
53
02
R
MEDIUM REMOVAL PREVENTED
3
57
00
R
UNABLE TO RECOVER TABLE-OF-CONTENTS
6
5A
00
R
OPERATOR REQUEST OR STATE CHANGE INPUT
6
5A
01
R
OPERATOR MEDIUM REMOVAL REQUEST
6
5A
02
++R
OPERATOR SELECTED WRITE PROTECT
6
5A
03
++R
OPERATOR SELECTED WRITE PERMIT
6
5B
00
R
LOG EXCEPTION
6
5B
01
R
THRESHOLD CONDITION MET
6
5B
02
R
LOG COUNTER AT MAXIMUM
6
5B
03
R
LOG LIST CODES EXHAUSTED
6
5D
00
R
FAILURE PREDICTION THRESHOLD EXCEEDED
6
5D
FF
R
FAILURE PREDICTION THRESHOLD EXCEEDED (FALSE)
6
5E
00
R
LOW POWER CONDITION ON
6
5E
01
R
IDLE CONDITION ACTIVATED BY TIMER
6
5E
02
R
STANDBY CONDITION ACTIVATED BY TIMER
6
5E
03
R
IDLE CONDITION ACTIVATED BY COMMAND
6
5E
04
R
STANDBY CONDITION ACTIVATED BY COMMAND
5
63
00
R
END OF USER AREA ENCOUNTERED ON THIS TRACK
5
63
01
R
PACKET DOES NOT FIT IN AVAILABLE SPACE
5
64
00
R
ILLEGAL MODE FOR THIS TRACK
5
64
01
R
INVALID PACKET SIZE
4
65
00
R
VOLTAGE FAULT

All values are in hex.

 

Table A.1 (cont.) - CD Device Sense Key, ASC and ASCQ Assignments

Sense Key
ASC
ASCQ
Type
Description
3
72
00
R
SESSION FIXATION ERROR
3
72
01
R
SESSION FIXATION ERROR WRITING LEAD-IN
3
72
02
R
SESSION FIXATION ERROR WRITING LEAD-OUT
5
72
03
R
SESSION FIXATION ERROR - INCOMPLETE TRACK IN SESSION
5
72
04
R
EMPTY OR PARTIALLY WRITTEN RESERVED TRACK
3
73
00
R
CD CONTROL ERROR
1
73
01
R
POWER CALIBRATION AREA ALMOST FULL
3
73
02
R
POWER CALIBRATION AREA IS FULL
3
73
03
R
POWER CALIBRATION AREA ERROR
3
73
04
R
PROGRAM MEMORY AREA UPDATE FAILURE
3
73
05
R
PROGRAM MEMORY AREA IS FULL

All values are in hex.

 

Table A.2 lists errors that may occur at any time, typically in response to a protocol or hardware error or user intervention.

Table A.2 - CD General Errors

Sense Key
ASC
ASCQ
 
Description
0
00
00
R
NO ADDITIONAL SENSE INFORMATION
b
00
06
R
I/O PROCESS TERMINATED
2
04
00
R
LOGICAL UNIT NOT READY, CAUSE NOT REPORTABLE
2
04
01
R
LOGICAL UNIT IS IN PROCESS OF BECOMING READY
2
04
02
R
LOGICAL UNIT NOT READY, INITIALIZING CMD. REQUIRED
2
04
03
R
LOGICAL UNIT NOT READY, MANUAL INTERVENTION REQUIRED
2
04
04
++R
LOGICAL UNIT NOT READY, FORMAT IN PROGRESS
2
04
07
R
LOGICAL UNIT NOT READY, OPERATION IN PROGRESS
2
04
08
R
LOGICAL UNIT NOT READY, LONG WRITE IN PROGRESS
4
05
00
R
LOGICAL UNIT DOES NOT RESPOND TO SELECTION
5
07
00
R
MULTIPLE PERIPHERAL DEVICES SELECTED
4
08
00
R
LOGICAL UNIT COMMUNICATION FAILURE
4
08
01
R
LOGICAL UNIT COMMUNICATION TIME-OUT
4
08
02
R
LOGICAL UNIT COMMUNICATION PARITY ERROR
6
0A
00
R
ERROR LOG OVERFLOW
1
0B
00
R
WARNING
1
0B
01
R
WARNING - SPECIFIED TEMPERATURE EXCEEDED
1
0B
02
R
WARNING - ENCLOSURE DEGRADED
5
1A
00
R
PARAMETER LIST LENGTH ERROR
4
1B
00
R
SYNCHRONOUS DATA TRANSFER ERROR
5
20
00
R
INVALID COMMAND OPERATION CODE
5
24
00
R
INVALID FIELD IN CDB
5
25
00
R
LOGICAL UNIT NOT SUPPORTED
5
26
00
R
INVALID FIELD IN PARAMETER LIST
5
26
01
R
PARAMETER NOT SUPPORTED
5
26
02
R
PARAMETER VALUE INVALID
6
28
00
R
NOT READY TO READY CHANGE, MEDIUM MAY HAVE CHANGED
6
29
00
R
POWER ON, RESET, OR BUS DEVICE RESET OCCURRED
6
29
01
R
POWER ON OCCURRED
6
29
02
R
SCSI BUS RESET OCCURRED
6
29
03
R
BUS DEVICE RESET FUNCTION OCCURRED
6
29
04
R
DEVICE INTERNAL RESET
6
2A
00
R
PARAMETERS CHANGED
6
2A
01
R
MODE PARAMETERS CHANGED
6
2A
02
R
LOG PARAMETERS CHANGED
6
2F
00
R
COMMANDS CLEARED BY ANOTHER INITIATOR

All values are in hex.

 

Table A.2 (cont.) - CD General Errors

Sense Key
ASC
ASCQ
 
Description
 
34
00
R
ENCLOSURE FAILURE
 
35
00
R
ENCLOSURE SERVICES FAILURE
 
35
01
R
UNSUPPORTED ENCLOSURE FUNCTION
 
35
02
R
ENCLOSURE SERVICES UNAVAILABLE
 
35
03
R
ENCLOSURE SERVICES TRANSFER FAILURE
 
35
04
R
ENCLOSURE SERVICES TRANSFER REFUSED
5
3D
00
R
INVALID BITS IN IDENTIFY MESSAGE
2
3E
00
R
LOGICAL UNIT HAS NOT SELF-CONFIGURED YET
4
3E
01
++R
LOGICAL UNIT FAILURE
4
3E
02
++R
TIMEOUT ON LOGICAL UNIT
6
3F
00
R
TARGET OPERATING CONDITIONS HAVE CHANGED
6
3F
01
R
MICROCODE HAS BEEN CHANGED
6
3F
02
R
CHANGED OPERATING DEFINITION
6
3F
03
R
INQUIRY DATA HAS CHANGED
4
40
NN
R
DIAGNOSTIC FAILURE ON COMPONENT NN (80H-FFH)
5
43
00
R
MESSAGE ERROR
4
44
00
R
INTERNAL TARGET FAILURE
b
45
00
R
SELECT OR RESELECT FAILURE
4
46
00
R
UNSUCCESSFUL SOFT RESET
4
47
00
R
SCSI PARITY ERROR
b
48
00
R
INITIATOR DETECTED ERROR MESSAGE RECEIVED
b
49
00
R
INVALID MESSAGE ERROR
4
4A
00
R
COMMAND PHASE ERROR
4
4B
00
R
DATA PHASE ERROR
4
4C
00
R
LOGICAL UNIT FAILED SELF-CONFIGURATION
b
4D
NN
R
TAGGED OVERLAPPED COMMANDS (NN = QUEUE TAG)
b
4E
00
R
OVERLAPPED COMMANDS ATTEMPTED
6
5A
00
R
OPERATOR REQUEST OR STATE CHANGE INPUT
6
5A
01
R
OPERATOR MEDIUM REMOVAL REQUEST
6
5B
00
R
LOG EXCEPTION
6
5B
01
R
THRESHOLD CONDITION MET
6
5B
02
R
LOG COUNTER AT MAXIMUM
6
5B
03
R
LOG LIST CODES EXHAUSTED
6
5D
00
R
FAILURE PREDICTION THRESHOLD EXCEEDED
6
5D
FF
R
FAILURE PREDICTION THRESHOLD EXCEEDED (FALSE)
4
65
00
R
VOLTAGE FAULT

All values are in hex.

Table A.3 lists errors that may be generated by disc access commands of any type (read of control or user data or writing of control or data area).

 

Table A.3 - CD Disc Access Errors

Sense Key
ASC
ASCQ
 
Description
4
00
17
R
CLEANING REQUESTED
3
02
00
R
NO SEEK COMPLETE
3
06
00
R
NO REFERENCE POSITION FOUND
4
09
00
R
TRACK FOLLOWING ERROR
4
09
01
R
TRACKING SERVO FAILURE
4
09
02
R
FOCUS SERVO FAILURE
4
09
03
R
SPINDLE SERVO FAILURE
4
09
04
R
HEAD SELECT FAULT
3
11
00
R
UNRECOVERED READ ERROR
3
11
01
++R
READ RETRIES EXHAUSTED
3
11
02
++R
ERROR TOO LONG TO CORRECT
3
11
05
R
L-EC UNCORRECTABLE ERROR
3
11
06
R
CIRC UNRECOVERED ERROR
3
11
0F
R
ERROR READING UPC/EAN NUMBER
3
11
10
R
ERROR READING ISRC NUMBER
3
15
00
R
RANDOM POSITIONING ERROR
3
15
01
R
MECHANICAL POSITIONING ERROR
3
15
02
R
POSITIONING ERROR DETECTED BY READ OF MEDIUM
1
17
00
R
RECOVERED DATA WITH NO ERROR CORRECTION APPLIED
1
17
01
R
RECOVERED DATA WITH RETRIES
1
17
02
R
RECOVERED DATA WITH POSITIVE HEAD OFFSET
1
17
03
R
RECOVERED DATA WITH NEGATIVE HEAD OFFSET
1
17
04
R
RECOVERED DATA WITH RETRIES AND/OR CIRC APPLIED
1
17
05
R
RECOVERED DATA USING PREVIOUS SECTOR ID
1
17
07
++R
RECOVERED DATA WITHOUT ECC - RECOMMEND REASSIGNMENT
1
17
08
++R
RECOVERED DATA WITHOUT ECC - RECOMMEND REWRITE
1
17
09
++R
RECOVERED DATA WITHOUT ECC - DATA REWRITTEN
1
18
00
R
RECOVERED DATA WITH ERROR CORRECTION APPLIED
1
18
01
R
RECOVERED DATA WITH ERROR CORR. & RETRIES APPLIED
1
18
02
R
RECOVERED DATA - DATA AUTO-REALLOCATED
1
18
03
R
RECOVERED DATA WITH CIRC
1
18
04
R
RECOVERED DATA WITH L-EC
1
18
05
R
RECOVERED DATA - RECOMMEND REASSIGNMENT
1
18
06
R
RECOVERED DATA - RECOMMEND REWRITE
5
21
00
R
LOGICAL BLOCK ADDRESS OUT OF RANGE

All values are in hex.

Table A.3 (cont.) - CD Disc Access Errors

Sense Key
ASC
ASCQ
 
Description
2
30
00
R
INCOMPATIBLE MEDIUM INSTALLED
2
30
01
R
CANNOT READ MEDIUM - UNKNOWN FORMAT
2
30
02
R
CANNOT READ MEDIUM - INCOMPATIBLE FORMAT
2
30
03
++R
CLEANING CARTRIDGE INSTALLED
2
30
07
R
CLEANING FAILURE
3
31
00
R
MEDIUM FORMAT CORRUPTED
2
3A
00
R
MEDIUM NOT PRESENT
2
3A
01
++R
MEDIUM NOT PRESENT - TRAY CLOSED
2
3A
02
++R
MEDIUM NOT PRESENT - TRAY OPEN
3
57
00
R
UNABLE TO RECOVER TABLE-OF-CONTENTS
6
5E
00
R
LOW POWER CONDITION ON
6
5E
01
R
IDLE CONDITION ACTIVATED BY TIMER
6
5E
02
R
STANDBY CONDITION ACTIVATED BY TIMER
6
5E
03
R
IDLE CONDITION ACTIVATED BY COMMAND
6
5E
04
R
STANDBY CONDITION ACTIVATED BY COMMAND
5
63
00
R
END OF USER AREA ENCOUNTERED ON THIS TRACK
5
64
00
R
ILLEGAL MODE FOR THIS TRACK
3
73
00
R
CD CONTROL ERROR

All values are in hex.

 

Table A.4 describes errors that may be generated by commands that cause user or control data to be written to the medium.

Table A.4 - CD Write Errors

Sense Key
ASC
ASCQ
 
Description
3
0C
00
R
WRITE ERROR
3
0C
07
R
WRITE ERROR - RECOVERY NEEDED
3
0C
08
R
WRITE ERROR - RECOVERY FAILED
3
0C
09
R
WRITE ERROR - LOSS OF STREAMING
3
0C
0A
R
WRITE ERROR - PADDING BLOCKS ADDED
5
27
00
++R
WRITE PROTECTED
5
27
01
++R
HARDWARE WRITE PROTECTED
5
27
02
++R
LOGICAL UNIT SOFTWARE WRITE PROTECTED
5
27
03
++R
ASSOCIATED WRITE PROTECT
5
27
04
++R
PERSISTENT WRITE PROTECT
5
27
05
++R
PERMANENT WRITE PROTECT
2
30
04
R
CANNOT WRITE MEDIUM - UNKNOWN FORMAT
2
30
05
R
CANNOT WRITE MEDIUM - INCOMPATIBLE FORMAT
5
30
08
R
CANNOT WRITE - APPLICATION CODE MISMATCH
5
30
09
R
CURRENT SESSION NOT FIXATED FOR APPEND
6
5A
02
++R
OPERATOR SELECTED WRITE PROTECT
6
5A
03
++R
OPERATOR SELECTED WRITE PERMIT
1
73
01
R
POWER CALIBRATION AREA ALMOST FULL
3
73
02
R
POWER CALIBRATION AREA IS FULL
3
73
03
R
POWER CALIBRATION AREA ERROR
3
73
04
R
PROGRAM MEMORY AREA UPDATE FAILURE
3
73
05
R
PROGRAM MEMORY AREA IS FULL

All values are in hex.

Table A.5 describes errors that may be generated by commands that cause the CD session to be closed.

Table A.5 - CD Fixation Errors

Sense Key
ASC
ASCQ
 
Description
5
2C
03
R
CURRENT PROGRAM AREA IS NOT EMPTY
5
2C
04
R
CURRENT PROGRAM AREA IS EMPTY
3
72
00
R
SESSION FIXATION ERROR
3
72
01
R
SESSION FIXATION ERROR WRITING LEAD-IN
3
72
02
R
SESSION FIXATION ERROR WRITING LEAD-OUT
5
72
03
R
SESSION FIXATION ERROR - INCOMPLETE TRACK IN SESSION
5
72
04
R
EMPTY OR PARTIALLY WRITTEN RESERVED TRACK

All values are in hex.

@

For the CDR100 / CDR102 Series Recorder

Sense Key Error Messages:

03hex - Medium Error:. Indicates that the command terminated with a non- recovered error condition that was probably caused by dust on the disc or an error in the recorded data.
04hex - Hardware Error: Indicates that a hardware failure (e.g., controller or device failure, parity error, etc.) was detected by the CDR100/CDR102 while executing a command or during a self-test.
09hex - Drive Busy: Indicates that the drive is now working for write operation. The drive cannot accept the command now and the host should re-publish the command again.
0Bhex - Aborted Command: Indicates that the CDR100/CDR102 aborted the command.
0Dhex - Volume Overflow: Indicates that the CDR100/CDR102 has reached the end of volume during writing or reading.

 

Additional Sense Code:

09hex - Track Following Error: A problem was encountered during focusing or radial tracking. (Sense Key: Hardware Error).
11hex - Unrecovered Read Error: The previous READ command failed, probably due to a flaw in the disc. (Sense Key: Medium Error).
15hex - Positioning Error: A seek to a requested location on the disc failed. (Sense Key: Hardware Error).
2Chex - Command Sequence Error: The previous command is not allowed in the current operational mode. (Sense Key: Illegal Request).
50hex - Write Operation in Progress: Indicates that a write operation is in progress and cannot accept command. (Sense Key: Aborted Command).
57hex - Unable to Read TOC, PMA, Subcode or ATIP: The drive was unable to read the TOC, PMA, Subcode or ATIP of the current disc. (Sense Key: Medium Error).
ADhex - Buffer Underrun: The write operation terminated because the write buffer was empty. (Sense Key: Aborted Command).
BFhex - Buffer Overflow: Buffer overflow when read CD-DA or Read CD-DA MSF Command. (Sense Key: Illegal Request).


The following list is generated by Adaptec SCSI Cards, Easy CD Pro, & Adaptec CD Creator with the Yamaha  recorders.

 

This section is a list Adaptec Error messages, but with the Explanation/Solution slightly Modified by Yamaha Systems Technology, Inc.’s Technical support Team. Based on their experience with Adaptec Products and the Yamaha Recorders. This section is not a complete list of error messages, just those commonly seen in conjunction with the CD-Recording process.

140-xx-xx-xxHardware failure. CD recorder problem. Contact the recorder manufacturer.

Yamaha supplement: The 140 error message is seen rarely. But when it does show up, there are three possible causes.

1) If the drive is an External Unit, you may have a poor power source in the chassis or it’s power may be fluctuating. A quick test would be to remove the drive from the chassis and supply an alternate power source.( Such as connecting the drive directly to your Computer as an internal)

2) If your drive is an Internal, a bad power connection or too many devices on the same connection (One too many ‘Y’ Split power connectors). Or, rarely, a bad ribbon cable connection.

 

142-xx-xx-xxServo system error. Recorder's laser not powering up properly. If it occurs only rarely, it may mean that the discs and/or drive need to be cleaned, or the recorder is getting too hot. If the problem persists, have the recorder checked by its manufacturer.

Yamaha supplement: The 142 error is more likely to occur than the 140 error above. But the solutions are the same as mentioned for the 140 error. I have yet seen dust to be the cause of this error, but this can not be ruled out (Very unlikely if the drive is new).

However, if this error message only occurs after an extended time of having the drive powered on, you may not have the proper airflow for the Recorder. As a rule, you do not want any recorder sandwiched between two drives. Try to leave 1/2inch to 1 inch of space above and below driver for optimum life on the drive.

 

147-xx-xx-xxPower on, reset or bus device reset occurred. Recorder lost power before last command was sent.

Yamaha supplement: A bad cable connection or bad cables most commonly causes the 147 error message. In most cases, it happens with internal units and the cause is the connector on the 50pin-ribbon cable or the cable itself.

A bent pin on the back of the internal recorder may also cause it. Where the SCSI Cable connects up to the drive.

 

169-xx-xx-xxSession closing action failed. Recorder unable to close the session.

Yamaha supplement: This can be caused by a few other scenarios. In order to find out which is the most likely cause, you must be watching the Recorder just before the error message occurs. What the lights do (blinking sequence) can help you diagnose the problem. You need to know…

  1. Did the error message show up before or after a pop-up message from the mastering software stating "Closing Session, this will take a few minutes", or was it just writing and the error occurred?
  2. If you got the message that it was closing before the error message, the drive failed to close the session and the cause is either the drive or the disc.
  3. If it just occurred, try a very small write and see if the drive is able to complete it with no problem. If it fails the disc or the drive is at fault.
  4. If it just occurred, and attempting to write a very small amount of data passes with no errors, your source data is suspect.

 

171-xx-xx-xxWrite or write append error. Recorder failed to write to CD. Check your source files for empty directories,
zero-byte files, corrupted files, files in use on a network. Make sure the destination CD is free of inconsistencies, fingerprints, and dust. Check settings on the SCSI controller to make sure there are no conflicts. The problem is sometimes resolved by cooling the CD recorder. Clean the recorder and blow the dust out. Try an entirely
different brand of recordable disc. If the problem persists, have the recorder checked by its manufacturer.

Yamaha supplement: This error message is a very common one with the Adaptec Software and SCSI Card. We are not sure exactly what causes it at this time and it’s being looked into by Both Yamaha’s and Adaptec’s Technical Support Staff. There are known causes to this error message, and some of the solutions here will resolve the problem for a few of you.

  1. Firmware version 1.0c and earlier of the Yamaha Recorder CDR400 series has a known SCSI Disconnect issue that causes the 171-xx-xx-xx error message to occur at the very end of a write operation. But if you go back after it fails closing the session, with EasyCD Pro 95 or Adaptec CD Creator, you can close the session and salvage the disc. All your data will be there and the CD will be readable on any CD-ROM drive. Upgrading your Yamaha to 1.0d or higher will resolve this issue. You can find this on Yamaha’s web site at http://www.yamaha.co.jp/english/product/computer/index2.html
  2. Some customers have called with this same 171-xx-xx-xx error message using the Yamaha Recorder, Adaptec CD Creator, and an Adaptec SCSI Card. By down grading Adaptec’s miniport driver 2.0, for Adaptec SCSI Card, to version 1.3 they were able to create CD’s without the 171 error message.(Note: some end users are able to record to the Yamaha without any errors, and they are using Adaptec’s miniport driver 2.0)
  3. If it’s a heat problem, it will be due to the fact you do not have enough airflow. Most computer chassis these days have very good fans. However, if you sandwich a Recorder between two devices and one of them is a hard drive or in some way generates heat., your are bound to have problems eventually. Yamaha Recorders must have space Above & Below to prevent overheating the optical unit. This will also give it a much longer life span. You should have 1/2inch to 1inch of space above and below the drive.
  4. For some customers, going to a 2x speed will resolve this issue with the 171-xx-xx-xx error message. They also occasionally get a "buffer underrun" at 4x speeds, but not always. When they are not getting buffer underruns, they are getting the 171-xx-xx-xx error message at the end of the write operation.
  5. Unfortunately, some customers resolve their issues only by going to another computer( with the same SCSI Card and Recorder). And some have not been able to resolve their issues, even with the help of both Yamaha and Adaptec, and have to close each session manually after it fails.( We are still researching the cause of this)

 

174-xx-xx-xxDevice track/data verify failed.

Yamaha supplement: In order to find out what device is the most likely cause, you must be watching the Recorder just before the error message occurs. What the lights do (blinking sequence) can help you diagnose the problem.

  1. If the drive has a solid green DISC light, and the READ/WRITE light is solid AMBER (write mode) when the error occurs, the SOURCE drive you are using for the write is at fault or the cable connection.
  2. If the drive has a solid green DISC light, and the mastering software reported it’s about to "start writing" or "close the session" and you see the READ/WRITE light blinking AMBER, the cause is may be the Recorder.

 

175-xx-xx-xxBuffer under run. Writing halted. Recorder's cache buffer is empty. See "Cures for Buffer Underruns."

Yamaha supplement: There is absolutely no reason for "Buffer Underruns" with the Yamaha CDR400 Recorder, but especially at 2x or 1x speeds. First thing you need to determine is just how bad is the transfer rate????

  1. If you have the EasyCD Pro 95 software, run the SPEED TEST under the GENERAL options ( where you select write speed). This will only test your source drive and will not involve the Yamaha Recorder in any way. You want no less than 1000kb/sec transfer rate to do a 4x write. If you are getting just a little below 1000kb/sec, you have a problem and you need to go over your system and the devices connected to find out what.( See "Cures for Buffer Underruns" on the Adaptec Web site)
  2. Try a different source drive. I’ve found CD to CD is much more reliable of a test for your system configuration. If you can do a CD to CD write at 4x, then your system configuration is more than likely good. The problem would more than likely be with the source Hard Drive you used. Of course, you need to use a CD-ROM drive that can sustain 4x writes such as any Plextor drive or any drive above 8x read capability.
  3. If you get buffer underruns when doing 2x writes or 1x, you have a serious problem. And if you can not do a CD to CD write in the fashion mentioned in Step 2, you have a serious configuration problem. Could be bad SCSI Card, Driver conflicts, Cables, Memory, Hard Drives, Termination, or worst of all a defective mother board.

 

189-xx-xx-xxThe track mode is either illegal, mismatches with command, Disc or other track types.
The CD format chosen under Close Session in the General tab not compatible with other
data already on the CD.

Yamaha supplement: For the 189 error message, you must watch when it occurs. It should not happen in the middle of a write operation. If it happens during the middle of the write, you must check the type of data you are selecting for the write. This error message has been known to show up when using the EasyCD Pro software to create Enhanced CD’s.

 

194-xx-xx-xxUnknown Adaptor Error. (New error message)

Yamaha supplement: Yamaha has not been able to determine the cause of this error. It only seems to occur with the EasyCD Pro 95 or Adaptec CD Creator software. And it happens at the very end of the write operation. We do not know at this time why the Mastering software is unable to communicate to the SCSI Card towards the end of the write operation.

 

204-xx-xx-xxBad or corrupted medium Recordable CD is corrupt or defective.
This message can also arise due to a problem with the recorder itself. Try these steps:

1.Try a different brand of recordable disc. If the problem persists, then:
2.Have the settings on the SCSI controller double-checked; contact
the controller manufacturer for this from Adaptec, click here). If that doesn't help, then:
3.If the problem persists, have the recorder checked by its manufacturer.

Yamaha supplement: None

 

220-xx-xx-xxSCSl error Generic. SCSI controller timeout before device finished. An inconsistency or
a slight conflict somewhere on the SCSI bus that doesn't surface till the recorder is activated.
If it happens at the end of a write, most likely the controller is timing out before the recorder is
finished. Contact the manufacturer of your SCSI host adapter for tech support.

Yamaha supplement: The 220-xx-xx-xx error messages are very generic, in the very broad sense. However, I’ve never found it to be caused by any CD Recorder, to date. The following is a list of the most likely causes. Each have been diagnosed more than once in the past from customers calling with this error message or a form of it. Listed in order of most frequently occurring…

  1. Bad disc or disc with one session currently recorded in a format not compatible with the format you have selected for the new session. If this is the case, you will be able to pass a test write, but as soon as it begins the actual write you get the 220-xx-xx-xx error message. The error occurs before you are able to begin the actual burn. You will see the DISC light go from a solid GREEN to a blinking amber. The READ/WRITE light on the drive will also be blinking AMBER. Then the drive will eject the disc and report the 220-xx-xx-xx error message.
  2. Old miniport drivers from Adaptec, or a new release of their miniport drivers that has an unknown bug at the time.
  3. Your source drive has disconnected from the SCSI bus or been disconnected by the SCSI Card. Your system will hang, and you have to reboot. If you are able to get back to the Window and close the mastering software application, you will find some devices if not all missing from your device manager. They will not come back until you reboot the system.
  4. Bad cables can cause this 220-xx-xx-xx error message. Your system will hang, and you have to reboot. If you are able to get back to the Window and close the mastering software application, you will find some devices if not all missing from your device manager. They will not come back until you reboot the system.
  5. Bad SCSI Card. It will work as far as loading properly under Windows 95 or NT. All other devices will perform normally when connected to the SCSI Card. Only when you do write operations will you get this error messages. However, in most cases the user has had some unexplainable problems in the past, or occasional problems with devices being seen on the initial boot up, that will indicate a possible bad SCSI Card.
  6. Bad Mother board. Only way to test this is to go to another computer with the same SCSI Card and Recorder.

 

 

240-xx-xx-xxOptimum power calibration failure. Recorder unable to calibrate laser power for the disc.
May be due to the disc itself; try another brand. If the problem persists, have the recorder
checked by its manufacturer.

Yamaha supplement: None

 

 

The following is an unedited list of Adaptec Error messages.

# Text Explanation/Solution

100 Virtual CD image not open.

Your hard disk may be write-protected, or the database may be corrupt. Run hard disk diagnostics, rebuild the Data Track list.

 101 Bad File type specified. The file type is illegal or unsupported.

 102 File on HD not found. The software cannot find a specified file to record.

 103 XCD engine already in use. Attempted to start more than one instance of the program.

 104 Virtual CD image already open. Attempted to open more than once instance of the same database.

 105 Error saving Virtual CD image. Your hard disk may be write-protected. Corrupt file or other error in
database. Run hard disk diagnostics, rebuild the Data Track list.

 106 Empty virtual CD image. There are no files in the database to be recorded.

 107 User canceled operation. The current operation was canceled by the user.

 108 Error creating file. This error can refer to Easy-CD's temporary files or to a real ISO image
being written. Make sure the temporary directory has enough space available, and that only one temporary
directory is set. (That is, if you're running Win 95, there should be no temporary listed in the autoexec.bat file).

109 Error writing file. Recorder unable to write to the temporary directory, the .ISO image, or the CD.

110 Error opening file.

111 Error reading file.

112 No device driver has been selected. No .drv file found for the recorder. Reinstall the software

113 Device driver already selected. Something is trying to load the driver again.

114 Error adding file to virtual CD image. Database error. Retry the last command, rebuild the Data Track list.

115 Invalid parameter. The recorder was sent a command it was unable to decipher.

116 Invalid file name. The file name is not permitted with the file naming option you have chosen.

117 Directory not found. Database error. Retry the last command, rebuild the Data Track list.

118 Could not delete file. The file may be write-protected or it may be a database error. Run hard
disk diagnostics, retry the command, rebuild the Data Track list.

119 Bad XCD handle.

120 End of virtual CD image reached.

121 End of current directory in virtual CD image reached.

122 File added to virtual CD image. A new file was added to an existing database.

123 Existing file re-added to virtual CD image. File re-added to database.

124 Existing file in virtual CD image replaced by newer version. File in database replaced with newer version.

125 Existing file not re-added to virtual CD image because not newer. File not re-added. Database already contains newer or current version.

126 File not added because already present. File not added because it is already in the database.

127 xx

128 No valid track to load has been found on disc. The recorder is unable to access the CD to load the track.

129 No valid track to verify has been found on disc. The recorder is unable to access the CD to verify the track.

130 Disc must be blank for Disc-At-Once. Disc-at-Once requires a disc to be written and closed in one operation;
it can only be performed on a blank CD.

131 CD size too small to hold current image. Use a larger recordable CD.

132 The mode of this virtual CD image cannot be changed because its contents refer to previous tracks on the disc.
In adding data to a disc which already contains some data, you have selected a different format under Close Session
than the format of the previous session(s). This is not allowed, so please change the selected format to match what's
already on the disc.

133 Byte-per-byte verify failed at sector xxxx . New CD does not acceptably resemble source data.

134 Verify failed because CD track is shorter than source. The written track is smaller than the source.

135 Verify failed because source is shorter than CD track. The written track is larger than the source.

136 Virtual CD image Mount or FixUp not performed. The mount (of data from a previous track) or fix up (of new files to be
recorded) did not occur. There may be a problem with the source files.

137 The specified SCSI source is not supported. Device selected as source not supported.

138 File in VCD not found.

140 Hardware failure. CD recorder problem. Contact the recorder manufacturer.

141 LUN failure. Internal controller communication problem.

142 Servo system error. Recorder's laser not powering up properly. If it occurs only rarely, it may mean that the discs
and/or drive need to be cleaned, or the recorder is getting too hot. If the problem persists, have the recorder checked
by its manufacturer.

143 Internal or device controller error. Recorder unable to recover error during writing. May possibly be caused by
cable problems or a conflict in SCSI device drivers.

144 Diagnostic, power on or self test failure. Recorder error. If the problem persists, have the recorder checked by its manufacturer.

145 Cache buffer failure. Problem with the recorder's buffer. If the problem persists, have the recorder checked by its manufacturer.

146 Unit not ready. CD recorder not ready. Wait a few seconds and retry. If that doesn't work, check the cables.

147 Power on, reset or bus device reset occurred. Recorder lost power before last command was sent.

148 Medium load or eject failed. The loading or unloading of the disc failed.

160 Unrecoverable read error. If the error occurs when trying to read a track to hard disk from the
recorder, ensure there are no smudges, scratches, etc. on the source CD. Also make sure there is enough
room on the hard drive to store the track.

161 Recovered data. There was an error, but the recorder was able to recover.

164 Illegal or under conflict sector size.

165 Read-write error. Previous read command failed, possibly due to a flaw on the disc. Make sure the temporary
directory has plenty of room. Try a different recordable disc. If the problem persists, try a different brand. If it still
persists, have the recorder checked by its manufacturer.

166 Seek positioning error. CD recorder error. Try a different brand of recordable disc. If the problem persists, have
the recorder checked by its manufacturer.

167 Invalid sector address.

168 End of user area encountered or stopped on non-data sector. Disc full, data transfer halted on non-data block.

169 Session closing action failed. Recorder unable to close the session.

170 End of medium reached. The disc is full.

171 Write or write append error. Recorder failed to write to CD. Check your source files for empty directories, zero-byte files,
corrupted files, files in use on a network. Make sure the destination CD is free of inconsistencies, fingerprints, and dust.
Check settings on the SCSI controller to make sure there are no conflicts. The problem is sometimes resolved by cooling the
CD recorder. Clean the recorder and blow the dust out. Try an entirely different brand of recordable disc. If the problem persists,
have the recorder checked by its manufacturer.

174 Device track/data verify failed.

175 Buffer under run. Writing halted. Recorder's cache buffer is empty. See "Cures for Buffer Underruns."

176 Absorption control error occurred. Problem with the recordable disc. Clean it, try a new disc, or a different
brand. If the problem persists, have the recorder checked by its manufacturer.

178 Illegal transfer length or data track length error. Transfer length in command descriptor block will overflow write buffer.

179 UPC\Barcode reading error.

180 ISRC reading error.

183 Current Program area empty. Corrupt disc. Try new disc.

184 Current Program area not empty.

185 Recovery needed. Recorder was powered down during write.

186 Catalog number conflict.

187 Invalid ISRC number. International Standard Recording Code for track is invalid.

188 ISRC reading error. Trouble reading the International Standard Recording Code.

189 The track mode is either illegal, mismatches with command, Disc or other track types. The CD format chosen
under Close Session in the General tab not compatible with other data already on the CD.

190 Unit busy. Reissue last write. Command sent before unit was ready.

192 Buffer overflow. Source device is transferring data too fast for the recorder.

193 Write area already written.

200 Medium changed. A new disc has been put in the CD recorder.

201 Medium not present. No disc is loaded in the CD recorder.

202 Not enough recordable area. Attempting to write too much data to the CD.

203 Not recordable or write-protected Disc. Disc is closed and cannot be written to.

204 Bad or corrupted medium Recordable CD is corrupt or defective. This message can also arise due
to a problem with the recorder itself. Try these steps:

1.Try a different brand of recordable disc. If the problem persists, then:

2.Have the settings on the SCSI controller double-checked; contact the controller manufacturer
for this (if your SCSI host adapter is from Adaptec, click here). If that doesn't help, then:

3.If the problem persists, have the recorder checked by its manufacturer.

205 Tray out. The recorder's CD tray has been ejected but not retracted.

206 Operator medium removal request. You requested to unload the disc.

207 Medium removal is prevented. Cannot remove the CD at this time.

208 Illegal track number. There is an invalid track number in the command descriptor block.

209 Application code conflict.

210 Unable to read Medium TOC, PMA or subcode. Disc may be corrupt.

211 Disc style mismatch. The CD format chosen under Close Session in the General tab not compatible with other
data already on the CD. This error sometimes occurs if a previous session on the CD was written on a different recorder.

212 Total Disc track number will exceed 99. Attempting to write too many tracks to the CD.

220 SCSl error Generic. SCSI controller timeout before device finished. An inconsistency or a slight conflict somewhere
on the SCSI bus that doesn't surface till the recorder is activated. If it happens at the end of a write, most likely the controller
is timing out before the recorder is finished. Contact the manufacturer of your SCSI host adapter for tech support.

220-1 SCSI Target timeout Device not responding before the time-out limit. The software cannot communicate with a SCSI device,
possibly because your SCSI bus was reset. This is sometimes caused by conflicts between real-mode and protected-mode SCSI
drivers on a Windows 95 system. Try REMming out any SCSI drivers in your CONFIG.SYS file; the drivers provided with
Windows 95 should be sufficient on their own.

220-2 SCSI Check target return sense Recorder indicates that source file(s) have changed from original configuration.
This usually occurs with the files being written from hard disk. If it occurs during a disc-to-disc copy, check your source
CD-ROM drive. It should preferably be SCSI 2, and able to reliably transfer data without corrupting it. If you are copying
audio, it needs to be capable of digital audio extraction. Also make sure the source CD you are trying to copy is not somehow
copy protected. There are some CDs our software cannot copy.

220-3 SCSI Specified Target/LUN is busy. The specified device is busy. Wait for it to become ready.

220-4 SCSI Target reservation conflict. Device is waiting for another program to release it. Reset the hardware.

220-5 SCSI Request completed with error. Write finished with error. This error means that a target sense code was
not sent back by the source device. Contact the manufacturer of your SCSI cards for configuration advice.

220-6 SCSI Selection timeout. This is a SCSI selection timeout error, indicating a SCSI setup problem. Please contact the
maker of your SCSI host adapter.

220-7 SCSI Data over-run/under-run

220-8 SCSI Unexpected Bus Free. Hardware. Check for improper termination.

220-9 SCSI Target bus phase sequence failure. Controller set-up problem. Contact the manufacturer of your SCSI host adapter.

220-10 (aka 220-0a) SCSI request aborted by host. The controller has aborted the procedure. Make sure auto-insert notification
is disabled for all CD devices on the SCSI bus!

Disable SCSI disconnect settings for both the card and the recorder. If it was already disabled, try enabling it.

In Windows 95, press Ctrl + Alt + Del and close any other open applications (except Explorer!) in the Close Program dialog box.

Check your hardware configuration for the controller. Make sure there are no conflicts.

 

220-11(aka220-0a) SCSI Invalid Host Adapter number "SCSI initialization failed. In order to run this program

You must have WNASPI32.DLL installed and started" Controller unknown, not supported, or set up incorrectly.

 

In Windows 95/98:

Check DEVICE MANAGER in 95 and confirm that your SCSI
CONTROLLER doesn't have a red X or yellow exclamation point.
Search the system for all instances of WNASPI32.DLL and delete all except the one in the \WINDOWS\SYSTEM\ directory.

 

In Windows NT:

Check SCSI DEVICES and confirm that your SCSI CONTROLLER
doesn't have a red X or yellow exclamation point. If the
WNASPI32.DLL file is in the system32 directory, then go to Control
Panel, either Devices or Services, find the ASPI line, and make sure it
says either BOOT or Automatic in the Start column.

Search the system for all instances of WNASPI32.DLL and delete all
except the one in the \WINDOWS\SYSTEM\ directory.

Then (if you do see a red X or yellow exclamation point):

Note: These warning signals can also indicate a hardware problem.

If you are using an Adaptec controller, download WNASPI32.DLL
from the Adaptec FTP site, and install it.

If your SCSI card is not from Adaptec, check with its vendor for an
up-to-date ASPI layer, or re-install the original Windows 95 or NT
ASPI layer. Make sure the controller you are using is FULLY ASPI
compliant.

220-12 SCSI request block has one, or more, parameters set incorrectly. Indicates an incorrect setting on the
SCSI card. Double-check the IRQ and Port address to make sure they aren't trying to share with something
else in the system. Make sure there are no yellow exclamation points in Device Manager (My Computer: Properties),
and no blue marks if you double-click on the computer icon at the top of Device Manager.

220-13 SCSI manager is momentarily busy

220-14 (aka 220-0e) SCSI Transfer data size too big

220-15 (aka 220-0f) SCSI Unknown error

220-16 SCSI Command pending on specified device

220-17 SCSI Failed init

220-18 SCSI Device not installed. ASPI shell internal error.

220-19 SCSI Invalid command. The previous SCSl command is not supported by the device.

220-20 SCSI Unable to abort Command. Unable to cancel. Operation will continue.

221 Command sequence, descriptor, code or parameter-list error. Check with the maker of your SCSI host adapter for
proper setup. Uninstall and reinstall the software.

222 Aborted command. Command aborted.

223 SCSI interface communication, parity or select error. Communication error between SCSI card and servo prevent
command from being performed.

224 Invalid LUN. Logical unit field of command descriptor was non-zero.

230 Error exchanging medium.

231 Input element or magazine error.

232 Output element or magazine error.

233 Mechanical error. Hardware error.

234 Unit stopped due to error.

234 Unit stopped due to error. Recorder stopped. Try resending unrecorded data.

235 Door is open. The tray has been ejected and not retracted.

240 Optimum power calibration failure. Recorder unable to calibrate laser power for the disc. May be due to the
disc itself; try another brand. If the problem persists, have the recorder checked by its manufacturer.

241 Calibration area almost full. Only a few Optimum Power Calibration areas left on this recordable disc.

242 Calibration area full. It is no longer possible to write to this disc because the Optimum Power Calibration area is full.

243 PMA read-update error. Unable to access the Program Memory Area.

244 Unexpected error. An unexpected error occurred. Restart the recorder.

245 Out of memory. The memory/temporary directory is full.

246 The Specified device is not supported by this driver. The device specified is not supported by the software.

247 Unrecoverable error (generic). Generic. Restart the software.

248 Mode parameters changed. The mode originally set for the track has been changed.

249 Function not available. The function chosen is not available.

250 The selected device does not support such function. The device specified does not support the chosen function.

252 Write process error. Uncorrectable error. Restart the software. If this doesn't help, reinstall software.

back