6 replies to this topic

[fortinw]

While trying to copy a DVD, all starts well but after about 10 seconds it stops burning and I get the message " SCSI request completed with error", error # 21000005. My burner is an NEC DVD RW ND1300A, external USB drive. I've updated to the latest firmware version and have tried the PX Engine update, neither have worked. Thanks in advance for any help.

[ivanatrox]

are you able to make a disc image from the DVD you try to copy?

[fortinw]

ivanatrox, on Oct 24 2006, 07:23 AM, said:

are you able to make a disc image from the DVD you try to copy?

Yes, disc image worked fine.

[TChris]

fortinw, on Oct 24 2006, 06:15 AM, said:

While trying to copy a DVD, all starts well but after about 10 seconds it stops burning and I get the message " SCSI request completed with error", error # 21000005. My burner is an NEC DVD RW ND1300A, external USB drive. I've updated to the latest firmware version and have tried the PX Engine update, neither have worked. Thanks in advance for any help.

This is exactly the error I get.

I am using Disc Copier.  It made the first copy perfectly, but the next one and four more after it have been coasters.

More specific symptoms:  The Table of Contents burns fine, to 100%.  A couple of seconds after that, I receive the same error "SCSI request completed with error. [0x21000005]".  The data never seems to even start burning.

I too am using an external USB burner.  Mine is an Iomega model DVDRW4224E2Q-D, firmware A110.

I'm using Windows 2000 Professional SP4 with all patches current.  The machine is an HP DC5100 desktop, with 1.5 GB RAM.

The "Error Information" window shows this:

Y: IOMEGA DVDRW4224E2Q-D ("SCSI request completed with error." [0x21000005])
   ULONG: Error Number = 21000005
   STRING: Error String = SCSI request completed with error.
   STRING: Vendor Name = IOMEGA
   STRING: Product Name = DVDRW4224E2Q-D
   STRING: Firmware Revision = A110
   STRING: Drive Letter = Y
   ULONG: Index of the IWrite drive that reported the error. = 00000000
   DATA: Command History - [1st byte: n=cdblen][n bytes:cdb data][1byte: n=cdblen][n bytes:cdb data].... = ptr:0x17D9CFF8, len:65536 [0A 2A 00 FF FF FF 6A 00 00 1C 00 0A 2A 00 FF FF FF 6A 00 00 1C 00...(Repeating this sequence)]
   ULONGARRAY: Command Error History = 21000005; 12040804; 12040804; 12040804; ... (Repeating the last number)
   ULONGARRAY: Command Execution Time History = 00000000; 00000000; 00000000; ... (All zeros)
   ULONGARRAY: Command Execution Start Time History = 0004C25A; 0004C250; 0004C246; 0004C23C; 0004C232; 0004C228; 0004C21E; 0004C214; ...
   DATA: Command History - [1st byte: n=cdblen][n bytes:cdb data][1byte: n=cdblen][n bytes:cdb data].... = ptr:0x17D9CFF8, len:65536 [80 00 00 08 00 00 00 08 00 00 00 00 00 ... (Repeating zeros)]
   ULONG: Address in Blocks = FFFFFF6A
   ULONG: Access Mode = 00000920
   ULONG: Data Mode = 0000001E
   ULONG: Position Index = 00000001


This drive has always been very stable and reliable.  EMC 9 is the first software that ever gave me a problem with it, and even then this is the first.

Any help would be most appreciated!

-Terry

[grandpabruce]

TChris, on Jan 12 2007, 12:35 PM, said:

(Snip) This is exactly the error I get.

I am using Disc Copier.  It made the first copy perfectly, but the next one and four more after it have been coasters.

More specific symptoms:  The Table of Contents burns fine, to 100%.  A couple of seconds after that, I receive the same error "SCSI request completed with error. [0x21000005]".  The data never seems to even start burning.

I too am using an external USB burner.  Mine is an Iomega model DVDRW4224E2Q-D, firmware A110.

I'm using Windows 2000 Professional SP4 with all patches current.  The machine is an HP DC5100 desktop, with 1.5 GB RAM.

This drive has always been very stable and reliable.  EMC 9 is the first software that ever gave me a problem with it, and even then this is the first.

Any help would be most appreciated!

-Terry

Did you try rebooting between burns?

[TChris]

grandpabruce, on Jan 12 2007, 11:56 AM, said:

Did you try rebooting between burns?

Umm... No.  I've never had to do that before.

But, I did go find a firmware update for the drive.  That seems to have fixed the problem.

Thanks for your help!

-Terry

[grandpabruce]

TChris, on Jan 12 2007, 01:03 PM, said:

Umm... No.  I've never had to do that before.

But, I did go find a firmware update for the drive.  That seems to have fixed the problem.

Thanks for your help!

-Terry

I am glad the firmware update fixed the problem for you.  If it happens again, reboot between burns, even if you aren't supposed to have to do that.  I got in the habit of rebooting between burns, way back in version 4.  I still do it, even though I don't have to.

Actually, I think I do it because I have a senior moment everytime I have more than one burn and automatically reboot after the first burn.