Command Sequence Error and Synchronising Cache problem

[marcusb]

Hello All!

 

I have two Optiarc AD-7170S SATA DVD-RW drives and both exhibit the same two problems when trying to use ImgBurn, but both do not happen when using ISO Recorder v3 (http://isorecorder.alexfeinman.com/Vista.htm).

 

First, if I use a DVD-R disc, it does not matter what brand (I've tried many!) I get a Command Sequence Error. Here is a log for what it's worth on that issue:

 

I 22:28:31 ImgBurn Version 2.3.1.0 started!

I 22:28:31 Microsoft Windows Vista Ultimate Edition (6.0, Build 6000)

I 22:28:31 Total Physical Memory: 2,077,932 KB - Available: 1,306,332 KB

I 22:28:31 Initialising SPTI...

I 22:28:31 Searching for SCSI / ATAPI devices...

I 22:28:32 Found 2 DVD?RW/RAMs!

I 22:33:38 Operation Started!

I 22:33:38 Source File: C:\Users\Marcus N Brannon\Downloads\vista_6000.16386.061101-2205-LRMAIK_EN.img

I 22:33:38 Source File Sectors: 507,986 (MODE1/2048)

I 22:33:38 Source File Size: 1,040,355,328 bytes

I 22:33:38 Source File Volume Identifier: WLHAIK

I 22:33:38 Source File Application Identifier: CDIMAGE 2.52 (03/09/2004 TM)

I 22:33:38 Source File File System(s): ISO9660

I 22:33:38 Destination Device: [0:2:0] Optiarc DVD RW AD-7170S 1.00 (E:) (ATAPI)

I 22:33:38 Destination Media Type: DVD-R (Disc ID: RITEKF1) (Speeds: 2x, 4x, 6x, 8x, 12x, 16x)

I 22:33:38 Destination Media Sectors: 2,298,496

I 22:33:38 Write Mode: DVD

I 22:33:38 Write Type: DAO

I 22:33:38 Write Speed: 2x

I 22:33:38 Link Size: Auto

I 22:33:38 Test Mode: No

I 22:33:38 BURN-Proof: Enabled

I 22:33:38 Filling Buffer... (40 MB)

I 22:33:39 Writing LeadIn...

W 22:33:39 Failed to Write Sectors 0 - 31 - Command Sequence Error

W 22:33:39 Retrying (1 of 5)...

W 22:33:39 Retry Failed - Command Sequence Error

W 22:33:39 Retrying (2 of 5)...

W 22:33:39 Retry Failed - Command Sequence Error

W 22:33:39 Retrying (3 of 5)...

W 22:33:39 Retry Failed - Command Sequence Error

W 22:33:39 Retrying (4 of 5)...

W 22:33:39 Retry Failed - Command Sequence Error

W 22:33:39 Retrying (5 of 5)...

W 22:33:39 Retry Failed - Command Sequence Error

E 22:33:40 Failed to Write Sectors 0 - 31 - Command Sequence Error

I 22:33:40 Synchronising Cache...

E 22:33:41 Failed to Write Image!

E 22:33:41 Operation Failed! - Duration: 00:00:02

I 22:33:41 Average Write Rate: N/A - Maximum Write Rate: N/A

 

I know usually this is a problem with the drive itself not supporting the media or something along those lines, however, I am able to burn using Windows Vista or ISO Recorder v3 just fine onto the same disc.

 

My second problem is when I user DVD+R discs. All the data will be written to the disc but ImgBurn will hang and say "Synchronising Cache". I've let the PC sit for well over an hour to see if anything changed and it never sych's the cache. If I eject the disc the data is readable on my PC, but say in the case of a DVD movie, is not readable on stand-alone players. ImgBurn says the disc is "Incomplete" in the read mode. Again- there are no problems burning with Vista itself OR using ISO Recorder v3. Here is a log of this problem after I eject the disc:

 

I 22:45:55 ImgBurn Version 2.3.1.0 started!

I 22:45:55 Microsoft Windows Vista Ultimate Edition (6.0, Build 6000)

I 22:45:55 Total Physical Memory: 2,077,932 KB - Available: 1,137,360 KB

I 22:45:55 Initialising SPTI...

I 22:45:55 Searching for SCSI / ATAPI devices...

I 22:46:05 Found 2 DVD?RW/RAMs!

I 22:46:39 Operation Started!

I 22:46:39 Source File: C:\Users\Marcus N Brannon\Downloads\vista_6000.16386.061101-2205-LRMAIK_EN.img

I 22:46:39 Source File Sectors: 507,986 (MODE1/2048)

I 22:46:39 Source File Size: 1,040,355,328 bytes

I 22:46:39 Source File Volume Identifier: WLHAIK

I 22:46:39 Source File Application Identifier: CDIMAGE 2.52 (03/09/2004 TM)

I 22:46:39 Source File File System(s): ISO9660

I 22:46:39 Destination Device: [0:1:0] Optiarc DVD RW AD-7170S 1.00 (D:) (ATAPI)

I 22:46:39 Destination Media Type: DVD+R (Disc ID: RITEK-R03-02) (Speeds: 2.4x, 4x, 6x, 8x)

I 22:46:39 Destination Media Sectors: 2,295,104

I 22:46:39 Write Mode: DVD

I 22:46:39 Write Type: DAO

I 22:46:39 Write Speed: MAX

I 22:46:39 Link Size: Auto

I 22:46:39 Test Mode: No

I 22:46:39 BURN-Proof: Enabled

I 22:46:39 Filling Buffer... (40 MB)

I 22:46:40 Writing LeadIn...

I 22:47:05 Writing Image... (LBA: 0 - 507985)

I 22:48:59 Synchronising Cache...

I 22:52:21 Closing Track...

E 22:52:26 Close Track Failed! - Reason: No Additional Sense Information

I 22:52:26 Closing Track (Last Attempt!)...

E 22:52:26 Close Track Failed! - Reason: No Additional Sense Information

I 22:52:26 Finalising Disc...

E 22:52:27 Finalise Disc Failed! - Reason: No Additional Sense Information

I 22:52:27 Finalising Disc (Last Attempt!)...

E 22:52:27 Finalise Disc Failed! - Reason: No Additional Sense Information

E 22:52:27 Failed to Write Image!

E 22:52:27 Operation Failed! - Duration: 00:05:47

I 22:52:27 Average Write Rate: 8,990 KB/s (6.5x) - Maximum Write Rate: 11,521 KB/s (8.3x)

 

 

The specs on my PC are:

 

Windows Vista Ultimate x64

Core2Duo 6300

Intel DG965WH

2x 320 GB SATA Seagate drives in RAID 0

2x Optiarc AD-7170S

 

The mobo is in RAID mode so the SATA Ports are using AHCI. I have all the latest updated drivers and firmwares. I'd chalk this up to driver/bios/ahci/sata weirdness if only Vista/ISO Recorder didn't work, but since they do I have to believe the problem lies in ImgBurn somewhere. I appreciate any and all help on the subject, ImgBurn was my burner of choice before all this!

 

-Marcus

Edited April 10, 2007 by marcusb

[Shamus_McFartfinger]

I 22:33:38 Destination Media Type: DVD-R (Disc ID: RITEKF1) (Speeds: 2x, 4x, 6x, 8x, 12x, 16x)

I 22:46:39 Destination Media Type: DVD+R (Disc ID: RITEK-R03-02) (Speeds: 2.4x, 4x, 6x, 8x)

 

You say you've tried different media but all I see are Riteks ...... which are garbage. The "Command Sequence Error" and "No Additional Sense Information" errors are media errors. If you can post a log showing a failure with Verbatim or Taiyo Yuden media, we'll be able to do more. As for the other programs working properly, who knows?

 

BTW, there's some firmware updates available for your drive (You have v1.00)

 

NEC firmware v1.03 http://liggydee.cdfreaks.com/disclaimer/en...3_orig.zip.html

 

NEC modified firmware v1.04 http://liggydee.cdfreaks.com/fwinfo/en/7170a/1o4

[mmalves]

BTW, there's some firmware updates available for your drive (You have v1.00)

 

NEC firmware v1.03 http://liggydee.cdfreaks.com/disclaimer/en...3_orig.zip.html

 

NEC modified firmware v1.04 http://liggydee.cdfreaks.com/fwinfo/en/7170a/1o4

Wrong model. Those are 1.03 for the ATA model (AD-7170A) and his drives are SATA models:

I 22:46:39 Destination Device: [0:1:0] Optiarc DVD RW AD-7170S 1.00 (D:) (ATAPI)

I 22:33:38 Destination Device: [0:2:0] Optiarc DVD RW AD-7170S 1.00 (E:) (ATAPI)

 

There seems to be 2 options available for this drive on that page:

1. the original 1.00 firmware (RPC-1 and RPC-2 versions);
   
2. a hacked one based on 1.00 to allow bitsetting DVD+R(W) to DVD-ROM (RPC-1 and RPC-2 versions).
   

RPC - Region Playback Control (RPC-1 plays DVDs from any region while RPC-2 obeys the regional setting).

[Shamus_McFartfinger]

Crap. Dunno how I messed that one up. Good call.

[mmalves]

Crap. Dunno how I messed that one up. Good call.

I can think of a couple of reasons...

Or maybe you were drooling over Altercuno's ever changing and always top-notch avatar and personal photo...

[LIGHTNING UK!]

Look in the Tools -> Filter Driver options feature.

 

What does it list for your PC?

 

When you use Vista's own burning interface (IMAPI), or indeed ISO Recorder (because it uses that too), it might be going in at a lower level.

 

Something higher up is probably messing with things.

 

You might also like to try changing the write mode to 'Incremental' (rather than 'SAO') in the settings.

 

Then you try manually forcing the transfer length to 16.

 

As for the actual errors, the command sequence one is bogus, there's nothing wrong with the command sequence or everyone else in the world would have this issue - and on all OS's. The commands I send do not vary according to OS.

 

The 2nd one 'No Additional Sense Information' is not one I've seen in years! If a drive fails to complete a command issued to it, it should at least return the error code - yours isn't.

 

Now again, that's either because the some filter driver is messing with things or it's because the drive's firmware is just crap.

 

I'd very much like to see a test with some decent discs (i.e. TYG02, MCC-003-00 etc). Ritek haven't made anything decent in about 4 years. (Since RITEKG04 !)

[marcusb]

Here is a listing of my filter drivers:

 

===============================================

Filter Driver Load Order - ImgBurn v2.3.1.0

===============================================

 

Upper Device Filter: [None Found]

Upper Class Filter: [None Found]

Device: CD/DVD-ROM Device

Lower Class Filter: [None Found]

Lower Device Filter: [None Found]

 

Originally though there was a "GEARAspiWDM" in the Upper Class Filter. It is part of iTunes and I believe it's a 32-bit DLL and it won't work on Vista x64. iTunes anyway always told me there were no burners. Anyway, I removed it yesterday before posting thinking it too might be the problem but it seems it was not.

 

What is the difference between SAO and Incremental? Is it just how the drive handles it or will it affect compatibility on other readers?

 

I know my media is not the highest of quality, but if I can burn with Vista and playback on any other device I've tried I don't think I'm dealing with a media issue to be fair to it. I've tried with a few others though but I'll see if I can find any "good" ones.

 

Look in the Tools -> Filter Driver options feature.

 

What does it list for your PC?

 

When you use Vista's own burning interface (IMAPI), or indeed ISO Recorder (because it uses that too), it might be going in at a lower level.

 

Something higher up is probably messing with things.

 

You might also like to try changing the write mode to 'Incremental' (rather than 'SAO') in the settings.

 

Then you try manually forcing the transfer length to 16.

 

As for the actual errors, the command sequence one is bogus, there's nothing wrong with the command sequence or everyone else in the world would have this issue - and on all OS's. The commands I send do not vary according to OS.

 

The 2nd one 'No Additional Sense Information' is not one I've seen in years! If a drive fails to complete a command issued to it, it should at least return the error code - yours isn't.

 

Now again, that's either because the some filter driver is messing with things or it's because the drive's firmware is just crap.

 

I'd very much like to see a test with some decent discs (i.e. TYG02, MCC-003-00 etc). Ritek haven't made anything decent in about 4 years. (Since RITEKG04 !)

[marcusb]

Quick update: I found the 64-bit GEAR software on their site and I installed it and I can burn in iTunes on the same DVD-Rs that give Command Sequence Error in ImgBurn. Here is what my filter list looks like now.

 

===============================================

Filter Driver Load Order - ImgBurn v2.3.1.0

===============================================

 

Upper Device Filter: [None Found]

Upper Class Filter: GEARAspiWDM

Device: CD/DVD-ROM Device

Lower Class Filter: [None Found]

Lower Device Filter: [None Found]

 

Filter Name: GEARAspiWDM

File Name: C:\Windows\System32\Drivers\GEARAspiWDM.sys

File Version: 2.0.6.1

File Description: CD/DVD Class Filter Driver

Product Name: GEAR.wrks

Product Version: 8.xx [2.0.6.1]

Company Name: GEAR Software Inc.

Copyright: Copyright ? GEAR Software Inc. 2006

Edited April 10, 2007 by marcusb

[LIGHTNING UK!]

At this time, I honestly have no idea why it's saying that.

 

Attempt another burn, but this time, before you click the 'Write' button, press F8 to enable I/O debug mode.

 

Then once it's errored out and you've kinda exited the burn (pressed 'ok' or whatever), save the log to a file and upload it to the forum.

 

This might be a big ask, but do you have any other machines you could try that drive in? or perhaps under another OS? I'd just like to figure out where the problem lies exactly. If it ends up being the drive, I guess I'll have to buy one - unless they fix the issue in a firmware update.

[marcusb]

Alright, here are the logs for both types of burns. I only have one other machine that has a SATA connection and it's running Vista 32-bit, but I can try it sometime just to see. If I get frustrated enough I'll install XP and try on this machine.

 

At this time, I honestly have no idea why it's saying that.

 

Attempt another burn, but this time, before you click the 'Write' button, press F8 to enable I/O debug mode.

 

Then once it's errored out and you've kinda exited the burn (pressed 'ok' or whatever), save the log to a file and upload it to the forum.

 

This might be a big ask, but do you have any other machines you could try that drive in? or perhaps under another OS? I'd just like to figure out where the problem lies exactly. If it ends up being the drive, I guess I'll have to buy one - unless they fix the issue in a firmware update.

DVD_R_Synch_Cache.log

DVD_R_Command_Sequence_Error.log

Edited April 10, 2007 by marcusb

[LIGHTNING UK!]

I 09:31:14 Writing Image... (LBA: 0 - 507985)

I 09:36:18 Synchronising Cache...

I 09:36:19 [0:2:0] Optiarc DVD RW AD-7170S 1.00 (E:) (ATAPI)

I 09:36:19 CDB: 35 02 00 00 00 00 00 00 00 00

I 09:36:19 CDB Interpretation: Synchronise Cache

I 09:36:20 [0:2:0] Optiarc DVD RW AD-7170S 1.00 (E:) (ATAPI)

I 09:36:20 CDB: 00 00 00 00 00 00

I 09:36:20 CDB Interpretation: Test Unit Ready

I 09:36:20 [0:2:0] Optiarc DVD RW AD-7170S 1.00 (E:) (ATAPI)

I 09:36:20 CDB: 25 00 00 00 00 00 00 00 00 00

I 09:36:20 CDB Interpretation: Read Capacity

E 09:36:20 SENSE: 70 00 02 00 00 00 00 0A 00 00 00 00 04 08 00 00 00 00 00 00 00 00 00 00

E 09:36:20 SENSE Interpretation: Logical Unit not ready, Long Write in progress

I 09:36:21 [0:2:0] Optiarc DVD RW AD-7170S 1.00 (E:) (ATAPI)

I 09:36:21 CDB: 25 00 00 00 00 00 00 00 00 00

I 09:36:21 CDB Interpretation: Read Capacity

E 09:36:21 SENSE: 70 00 02 00 00 00 00 0A 00 00 00 00 04 08 00 00 00 00 00 00 00 00 00 00

E 09:36:21 SENSE Interpretation: Logical Unit not ready, Long Write in progress

.

.

.

I 09:36:49 [0:2:0] Optiarc DVD RW AD-7170S 1.00 (E:) (ATAPI)

I 09:36:49 CDB: 25 00 00 00 00 00 00 00 00 00

I 09:36:49 CDB Interpretation: Read Capacity

E 09:36:49 SENSE: 70 00 02 00 00 00 00 0A 00 00 00 00 04 08 00 00 00 00 00 00 00 00 00 00

E 09:36:49 SENSE Interpretation: Logical Unit not ready, Long Write in progress

I 09:36:50 [0:2:0] Optiarc DVD RW AD-7170S 1.00 (E:) (ATAPI)

I 09:36:50 CDB: 25 00 00 00 00 00 00 00 00 00

I 09:36:50 CDB Interpretation: Read Capacity

E 09:36:50 SENSE: 70 00 02 00 00 00 00 0A 00 00 00 00 3A 00 00 00 00 00 00 00 00 00 00 00

E 09:36:50 SENSE Interpretation: Medium Not Present

I 09:36:50 [0:2:0] Optiarc DVD RW AD-7170S 1.00 (E:) (ATAPI)

I 09:36:50 CDB: 51 00 00 00 00 00 00 00 20 00

I 09:36:50 CDB Interpretation: Read Disc Information

E 09:36:50 SENSE: 70 00 02 00 00 00 00 0A 00 00 00 00 3A 00 00 00 00 00 00 00 00 00 00 00

E 09:36:50 SENSE Interpretation: Medium Not Present

I 09:36:50 Closing Track...

 

So where it changes from 'Logical Unit not ready, Long Write in progress' to 'Medium Not Present', is that you ejecting the disc?

 

As you can see from the log, the program asks the drive 'Have you finished yet?' every second via the 'Read Capacity' command.

 

Up until the point when the status changed to 'Medium Not Present', the drive was still responding 'No, I haven't finished', along with the error code 'Logical Unit not ready, Long Write in progress'.

 

That's what I'd expect it to say.

 

If the drive doesn't think it's ready, the drive doesn't think it's ready.

 

Again, the drive is doing all the work at this point, ImgBurn is simply querying it's status.

 

Make from that what you will.

[marcusb]

Again, the drive is doing all the work at this point, ImgBurn is simply querying it's status.

 

Make from that what you will.

 

Well that I understand but the drive works in any other instance. I did try chanigng to incrmeental but the burn fails again at the end. I realize this is not a ImgBurn problem exclusively, but it obviously works in some capacity. I'll try emailing NEC on this.

[LIGHTNING UK!]

You never actually answered this:

 

So where it changes from 'Logical Unit not ready, Long Write in progress' to 'Medium Not Present', is that you ejecting the disc?

 

Leave it going for at least 10 minutes before you eject the disc and leave it logging with I/O debug mode enabled.

 

Oh and I guess that you must be disabling all the tray locking stuff if that's actually possible? - normally you wouldn't/shouldn't be able to do it!

[marcusb]

You never actually answered this:

 

So where it changes from 'Logical Unit not ready, Long Write in progress' to 'Medium Not Present', is that you ejecting the disc?

 

Leave it going for at least 10 minutes before you eject the disc and leave it logging with I/O debug mode enabled.

 

Oh and I guess that you must be disabling all the tray locking stuff if that's actually possible? - normally you wouldn't/shouldn't be able to do it!

 

Sorry, I was at work and was just typing a quick reply. Yes "Medium Not Present" is when I eject the disc myself and no, I did not disable tray locking during that process, I did however after just to see if it made a difference in anything and it did not. I can make the log as you request, but if it's not going to help I don't want to waste your time- I understand ImgBurn isn't going to be compatible with everything on the planet. Thats the nature of computers. I do have one question though- whats the difference between DAO and Incremental? Do they produce the same results on the disc just using different processes?

[LIGHTNING UK!]

To be honest, I don't know!

 

You'd have to ask the people who make the drives / firmware.

 

I only know about it as specifying one number or another number in a structure I fill out to set the write parameters.

 

Oh and about ImgBurn not being compatible.... that's the thing, it SHOULD be! The drives are supposed to follow the MMC specs (www.t10.org), and I do too. The program works just fine with the cupboard full of drives that I have (including a 7173 which should be similar to your 7170), so I can only assume ImgBurn has found a glitch in the drives firmware.

 

If you could test the drive in another pc (without the raid / ahci thing enable), it would really help. I'll happily fork out for a 7170S if there's actually going to be something for me too look at. What annoys me is when I get a drive, install it and it works fine! (yes this has happened on several occasions, hence the cupboard full of drives )

 

When I asked about the 'locking' of the drive, I simply mean that you should not be able to eject the disc at that time. The tray would normally get locked at the start of the burn and only then unlocked once it's has finished. Pressing the eject button shouldn't do anything until it's unlocked. So if the settings were still configured such that the tray is locked during a write operation (this is on the 'Device' tab in the settings), it's weird that the eject button worked.

[marcusb]

To be honest, I don't know!

 

You'd have to ask the people who make the drives / firmware.

 

I only know about it as specifying one number or another number in a structure I fill out to set the write parameters.

 

Oh and about ImgBurn not being compatible.... that's the thing, it SHOULD be! The drives are supposed to follow the MMC specs (www.t10.org), and I do too. The program works just fine with the cupboard full of drives that I have (including a 7173 which should be similar to your 7170), so I can only assume ImgBurn has found a glitch in the drives firmware.

 

If you could test the drive in another pc (without the raid / ahci thing enable), it would really help. I'll happily fork out for a 7170S if there's actually going to be something for me too look at. What annoys me is when I get a drive, install it and it works fine! (yes this has happened on several occasions, hence the cupboard full of drives )

 

When I asked about the 'locking' of the drive, I simply mean that you should not be able to eject the disc at that time. The tray would normally get locked at the start of the burn and only then unlocked once it's has finished. Pressing the eject button shouldn't do anything until it's unlocked. So if the settings were still configured such that the tray is locked during a write operation (this is on the 'Device' tab in the settings), it's weird that the eject button worked.

 

Yeah, the drive is not locked, I was talking about the same thing- I can freely open it when its stuck @ synchronising cache. I turned the options off to lock the drives to see if it changed anything, but it didn't. I'll definitely stick one of these in my AMD Vista 32 machine and report on what I find! Thank you so much for your time!

[marcusb]

Ok, I put the drive in my AMD based system and it burned a DVD-R and +R flawlessly. The drive runs in IDE compat mode on the AMD system though, and I don't believe I can change that. So maybe it's the AHCI mode in my BIOS? Maybe I'll have to email intel on this one...

[marcusb]

Ok, I put the drive in my AMD based system and it burned a DVD-R and +R flawlessly. The drive runs in IDE compat mode on the AMD system though, and I don't believe I can change that. So maybe it's the AHCI mode in my BIOS? Maybe I'll have to email intel on this one...

 

Thought I'd provide an update in case someone else has the same issue: I'm now using the latest Intel Matrix Storage software (available @ http://downloadcenter.intel.com/filter_res...mp;submit=Go%21 and it seems to have fixed my issues with using ImgBurn! I can burn successfully now!

Edited June 7, 2007 by marcusb