External USB2 question for Wind

vbimport

#1

@Wind,

This might not be your area of expertise but I wonder if you may have an idea of what is going on with this. I previously had a 1633 in this external case which has the ALI M5621 USB Bridge in it. There were no problem reading or burning with this combination. With the 5S or 6S drives in this case I get the following which is cut from ImgBurn:

I 22:44:13 Initialising SPTI…
I 22:44:13 Searching for SCSI / ATAPI devices…
I 22:44:13 Found 2 DVD-ROMs, 2 DVD±RWs and 3 DVD±RW/RAMs!
I 22:44:18 Operation Started!
I 22:44:18 Source File: E:\DVD Images\TEST.ISO
I 22:44:18 Source File Sectors: 2,233,747 (MODE1/2048)
I 22:44:18 Source File Size: 4,574,713,856 bytes
I 22:44:18 Source File Implementation Identifier: DVD Shrink
I 22:44:19 Destination Device: [0:0:0] LITE-ON DVDRW SHW-1635S YV6J (K:) (USB)
I 22:44:19 Destination Media Type: DVD-R (Disc ID: MCC 03RG20) (Speeds: 2x, 4x, 6x, 8x, 12x, 16x)
I 22:44:19 Destination Media Sectors: 2,298,496
I 22:44:19 Write Mode: DVD
I 22:44:19 Write Type: DAO
I 22:44:19 Write Speed: MAX
I 22:44:19 Link Size: Auto
I 22:44:19 Test Mode: No
I 22:44:19 BURN-Proof: Enabled
I 22:44:19 Filling Buffer…
I 22:44:19 Writing LeadIn…
W 22:44:56 Failed to Write Sectors 32 - 63 - The semaphore timeout period has expired.
W 22:44:56 Retrying (1 of 20)…
W 22:44:56 Retry Failed - Power On, Reset, or Bus Device Reset Occurred
W 22:44:56 Retrying (2 of 20)…
W 22:44:57 Retry Failed - The semaphore timeout period has expired.
W 22:44:57 Retrying (3 of 20)…
W 22:44:57 Retry Failed - The semaphore timeout period has expired.
W 22:44:57 Retrying (4 of 20)…
W 22:45:00 Retry Failed - The semaphore timeout period has expired.
W 22:45:00 Retrying (5 of 20)…
W 22:45:01 Retry Failed - Power On, Reset, or Bus Device Reset Occurred
W 22:45:01 Retrying (6 of 20)…
W 22:45:04 Retry Failed - The semaphore timeout period has expired.
W 22:45:04 Retrying (7 of 20)…
W 22:45:04 Retry Failed - Power On, Reset, or Bus Device Reset Occurred
W 22:45:04 Retrying (8 of 20)…
I 22:45:04 Writing LeadIn…
I 22:45:05 Writing Image…
I 22:50:03 Synchronising Cache…
I 22:50:15 Operation Successfully Completed! - Duration: 00:05:56
I 22:50:15 Average Write Rate: 15,042 KB/s (10.9x) - Maximum Write Rate: 21,830 KB/s (15.8x)

You can see the semaphore timeout’s and bus resets. I wonder if something is different about the IDE interface in these newer drives or if this is a fault of the ALI chipset? The burn does eventually work, but only after a number of retries.


#2

OK, this shall be something wrong with the communication between drive interface and USB chipset. Usually, drive will return “Long Write Inprogress” status to host when writing Lead-in. If Drive did, then system shall wait and can’t issue a “ATAPI Soft Reset”. Anyway, I’ll pass this to our interface engineers to check out. It maybe our firmware or just ALI USB chipset.


#3

HeHe…maybe I can share some job of our CS department. (If I am able to, I’ll be glad to.) :slight_smile:


#4

After I check the log in detail, I think that’s OK for the burn. And I think it is safe to forget this.


#5

I agree that it may be safe to ignore this, I just wonder why I dont see this with the 812/832 or 1633 drives in this same case. The burns do work so it’s not a big problem but if the interface engineers could look at it that would be great. It could be a very simple problem or like you said a problem with the ALI chipset.

You know, maybe they will pay you double to do the CS job!! HeHe…


#6

Here’s a little more information. I found a firmware update for the ALI chipset. It does not change this issue. What I have found is this only happens with -R burns. +R burns do not generate the semaphore or bus reset messages.


#7

OK, I’ll pass it to our interface engineer, anyway. Thank you for your information. :slight_smile: