Burn problem! (Failed to Write Sectors - Reason: Unknown (ASC: 0xA8, ASCQ: 0x03)))

vbimport

#1

Well, I’m using Pioneer DVR-216D (1.09 firmware - latest official firmware) and I’m satisfied, well until now

Recently, I had to reinstall my OS (XP SP3 Pro) and that’s where the problems begun.

All storage devices are SATA as is the mentioned burner. OS is installed on a (2xHDDs) RAID 0 - stripped volume. I think you got the basic idea so I’m gonna continue explaining the problem.

Burn fails every time no matter which burning program I choose. (Nero, ImgBurn, Ashampoo Studio etc.)

I’ve ruled out hardware problems of any kind. I’m confident in my statement because of the fact that after a clean install burning is not a problem. After I install a few drivers it starts acting as is shown on the end of the post.

Right now, I’m installing XP on a virtual machine to determine which driver causes this problems. I’m hoping for your support and expertize.

Technical details:

ImgBrn Log:

I 11:02:16 ImgBurn Version 2.5.5.0 started!
I 11:02:16 Microsoft Windows XP Professional (5.1, Build 2600 : Service Pack 3)
I 11:02:16 Total Physical Memory: 1,046,952 KB  -  Available: 57,128 KB
I 11:02:16 Initialising SPTI...
I 11:02:16 Searching for SCSI / ATAPI devices...
I 11:02:18 -> Drive 1 - Info: PIONEER DVD-RW  DVR-216D 1.09 (F:) (ATA)
I 11:02:18 Found 1 DVD±RW!
I 11:02:53 Operation Started!
I 11:02:53 Source File: C:\Disk C\New Stuff\XPstudent.iso
I 11:02:53 Source File Sectors: 327,040 (MODE1/2048)
I 11:02:53 Source File Size: 669,777,920 bytes
I 11:02:53 Source File Volume Identifier: xp.sp3.lil-fella
I 11:02:53 Source File File System(s): ISO9660 (Bootable), Joliet
I 11:02:53 Destination Device: [2:0:0] PIONEER DVD-RW  DVR-216D 1.09 (F:) (ATA)
I 11:02:53 Destination Media Type: CD-R (Disc ID: 97m22s67f, Daxon) (Speeds: 4x, 10x, 16x, 24x, 32x, 40x)
I 11:02:53 Destination Media Sectors: 359,847
I 11:02:53 Write Mode: CD
I 11:02:53 Write Type: SAO
I 11:02:53 Write Speed: 16x
I 11:02:53 Lock Volume: Yes
I 11:02:53 Test Mode: Yes
I 11:02:53 OPC: No
I 11:02:53 BURN-Proof: Enabled
I 11:02:53 Write Speed Successfully Set! - Effective: 2,822 KB/s (16x)
I 11:02:53 Advanced Settings - Optimal Writing Speed: No
I 11:02:53 Filling Buffer... (40 MB)
I 11:02:55 Writing LeadIn...
W 11:02:55 Failed to Write Sectors -150 - -119 - Reason: Unknown (ASC: 0xA8, ASCQ: 0x03)
W 11:02:55 Retrying (1 of 20)...
W 11:02:55 Retry Failed - Reason: Unknown (ASC: 0xA8, ASCQ: 0x03)
W 11:02:55 Retrying (2 of 20)...
W 11:02:55 Retry Failed - Reason: Unknown (ASC: 0xA8, ASCQ: 0x03)
W 11:02:55 Retrying (3 of 20)...
W 11:02:55 Retry Failed - Reason: Unknown (ASC: 0xA8, ASCQ: 0x03)
W 11:02:55 Retrying (4 of 20)...
W 11:02:55 Retry Failed - Reason: Unknown (ASC: 0xA8, ASCQ: 0x03)
W 11:02:55 Retrying (5 of 20)...
I 11:02:55 Writing LeadIn...
W 11:02:55 Failed to Write Sectors -118 - -87 - Reason: Unknown (ASC: 0xA8, ASCQ: 0x03)
W 11:02:55 Retrying (1 of 20)...
W 11:02:55 Retry Failed - Reason: Unknown (ASC: 0xA8, ASCQ: 0x03)
W 11:02:55 Retrying (2 of 20)...
W 11:02:55 Retry Failed - Reason: Unknown (ASC: 0xA8, ASCQ: 0x03)
W 11:02:55 Retrying (3 of 20)...
I 11:02:55 Writing LeadIn...
W 11:02:55 Failed to Write Sectors -86 - -55 - Reason: Unknown (ASC: 0xA8, ASCQ: 0x03)
W 11:02:55 Retrying (1 of 20)...
W 11:02:55 Retry Failed - Reason: Unknown (ASC: 0xA8, ASCQ: 0x03)
W 11:02:55 Retrying (2 of 20)...
W 11:02:55 Retry Failed - Reason: Unknown (ASC: 0xA8, ASCQ: 0x03)
W 11:02:55 Retrying (3 of 20)...
W 11:02:56 Retry Failed - Reason: Unknown (ASC: 0xA8, ASCQ: 0x03)
W 11:02:56 Retrying (4 of 20)...
W 11:02:56 Retry Failed - Reason: Unknown (ASC: 0xA8, ASCQ: 0x03)
W 11:02:56 Retrying (5 of 20)...
W 11:02:56 Retry Failed - Reason: Unknown (ASC: 0xA8, ASCQ: 0x03)
W 11:02:56 Retrying (6 of 20)...
W 11:02:56 Retry Failed - Reason: Unknown (ASC: 0xA8, ASCQ: 0x03)
W 11:02:56 Retrying (7 of 20)...
W 11:02:56 Retry Failed - Reason: Unknown (ASC: 0xA8, ASCQ: 0x03)
W 11:02:56 Retrying (8 of 20)...
W 11:02:56 Retry Failed - Reason: Unknown (ASC: 0xA8, ASCQ: 0x03)
W 11:02:56 Retrying (9 of 20)...
W 11:02:56 Retry Failed - Reason: Unknown (ASC: 0xA8, ASCQ: 0x03)
W 11:02:56 Retrying (10 of 20)...
W 11:02:56 Retry Failed - Reason: Unknown (ASC: 0xA8, ASCQ: 0x03)
W 11:02:56 Retrying (11 of 20)...
I 11:02:56 Writing LeadIn...
W 11:02:56 Failed to Write Sectors -54 - -23 - Reason: Unknown (ASC: 0xA8, ASCQ: 0x03)
W 11:02:56 Retrying (1 of 20)...
W 11:02:56 Retry Failed - Reason: Unknown (ASC: 0xA8, ASCQ: 0x03)
W 11:02:56 Retrying (2 of 20)...
I 11:02:56 Writing LeadIn...
W 11:02:56 Failed to Write Sectors 0 - 31 - Reason: Unknown (ASC: 0xA8, ASCQ: 0x03)
W 11:02:56 Retrying (1 of 20)...
W 11:02:56 Retry Failed - Reason: Unknown (ASC: 0xA8, ASCQ: 0x03)
W 11:02:56 Retrying (2 of 20)...
W 11:02:56 Retry Failed - Reason: Unknown (ASC: 0xA8, ASCQ: 0x03)
W 11:02:56 Retrying (3 of 20)...
W 11:02:56 Retry Failed - Reason: Unknown (ASC: 0xA8, ASCQ: 0x03)
W 11:02:56 Retrying (4 of 20)...
W 11:02:56 Retry Failed - Reason: Unknown (ASC: 0xA8, ASCQ: 0x03)
W 11:02:56 Retrying (5 of 20)...
I 11:02:56 Writing LeadIn...
W 11:02:56 Failed to Write Sectors 32 - 63 - Reason: Unknown (ASC: 0xA8, ASCQ: 0x03)
W 11:02:56 Retrying (1 of 20)...
W 11:02:56 Retry Failed - Reason: Unknown (ASC: 0xA8, ASCQ: 0x03)
W 11:02:56 Retrying (2 of 20)...
W 11:02:56 Retry Failed - Reason: Unknown (ASC: 0xA8, ASCQ: 0x03)
W 11:02:56 Retrying (3 of 20)...
W 11:02:56 Retry Failed - Reason: Unknown (ASC: 0xA8, ASCQ: 0x03)
W 11:02:56 Retrying (4 of 20)...
W 11:02:56 Retry Failed - Reason: Unknown (ASC: 0xA8, ASCQ: 0x03)
W 11:02:56 Retrying (5 of 20)...
W 11:02:56 Retry Failed - Reason: Unknown (ASC: 0xA8, ASCQ: 0x03)
W 11:02:56 Retrying (6 of 20)...
W 11:02:56 Retry Failed - Reason: Unknown (ASC: 0xA8, ASCQ: 0x03)
W 11:02:56 Retrying (7 of 20)...
W 11:02:56 Retry Failed - Reason: Unknown (ASC: 0xA8, ASCQ: 0x03)
W 11:02:56 Retrying (8 of 20)...
W 11:02:56 Retry Failed - Reason: Unknown (ASC: 0xA8, ASCQ: 0x03)
W 11:02:56 Retrying (9 of 20)...
W 11:02:56 Retry Failed - Reason: Unknown (ASC: 0xA8, ASCQ: 0x03)
W 11:02:56 Retrying (10 of 20)...
W 11:02:56 Retry Failed - Reason: Unknown (ASC: 0xA8, ASCQ: 0x03)
W 11:02:56 Retrying (11 of 20)...
W 11:02:56 Retry Failed - Reason: Unknown (ASC: 0xA8, ASCQ: 0x03)
W 11:02:56 Retrying (12 of 20)...
W 11:02:56 Retry Failed - Reason: Unknown (ASC: 0xA8, ASCQ: 0x03)
W 11:02:56 Retrying (13 of 20)...
W 11:02:56 Retry Failed - Reason: Unknown (ASC: 0xA8, ASCQ: 0x03)
W 11:02:56 Retrying (14 of 20)...
W 11:02:56 Retry Failed - Reason: Unknown (ASC: 0xA8, ASCQ: 0x03)
W 11:02:56 Retrying (15 of 20)...
W 11:02:56 Retry Failed - Reason: Unknown (ASC: 0xA8, ASCQ: 0x03)
W 11:02:56 Retrying (16 of 20)...
W 11:02:56 Retry Failed - Reason: Unknown (ASC: 0xA8, ASCQ: 0x03)
W 11:02:56 Retrying (17 of 20)...
W 11:02:56 Retry Failed - Reason: Unknown (ASC: 0xA8, ASCQ: 0x03)
W 11:02:56 Retrying (18 of 20)...
W 11:02:56 Retry Failed - Reason: Unknown (ASC: 0xA8, ASCQ: 0x03)
W 11:02:56 Retrying (19 of 20)...
W 11:02:56 Retry Failed - Reason: Unknown (ASC: 0xA8, ASCQ: 0x03)
W 11:02:56 Retrying (20 of 20)...
W 11:02:56 Retry Failed - Reason: Unknown (ASC: 0xA8, ASCQ: 0x03)
E 11:04:20 Failed to Write Sectors 32 - 63 - Reason: Unknown (ASC: 0xA8, ASCQ: 0x03)
I 11:04:20 Synchronising Cache...
W 11:04:23 User opted to skip the 'Close Track/Session/Disc' functions.
I 11:04:23 Cycling Tray after Test Write...
E 11:04:43 Failed to Write Image!
E 11:04:43 Operation Failed! - Duration: 00:01:50
I 11:04:43 Average Write Rate: 0 KB/s (0.0x) - Maximum Write Rate: 0 KB/s (0.0x)


#2

Update:

Burn fails also in the newly installed XP on the virtual machine. Well when I think about it it makes sense. Since it’s an I/O error, it only logical that already “polluted” connection will be inherited by a Virtual Machine program. So dead end here. …any ideas?


#3

well, it seams I’m talking to myself… maybe I posted in a wrong sub-forum?

Anyway, I researched a little and found out that my problem is connected to SATA connectors that are part of RAID setup. This is all speculation based on a few articles and my tests on drive behavior in different conditions. I’ll try something along this line, thinker a little with RAID BIOS settings, try to re-detect drives a new and these sort of things. Maybe switch MS SPTI driver with the one from the newest Deamon Tools (all versions of ASPI/ASAPI have failed).


#4

Connecting a drive to select RAID controllers with select BIOS/driver configurations has been known to affect optical drive performance. I’d say your research has been quite fruitful in at least one possible lead.

If you can’t find a BIOS setting that allows for the use of SOME of your SATA ports as legacy IDE ports (read: if you can’t turn RAID support off for some ports, or have no ports designated to treat drives as Just a Bunch Of Disks, or JBOD), then maybe leaving the SATA controller drivers as generic Microsoft drivers will be most beneficial to you (assuming your RAID array still functions well without them). (I have no idea if you can successfully roll back to Microsoft’s generic drivers once other drivers have been installed). That may be the best option. Or triple-check that you cannot find a version of the SATA controller driver that will work for you.

Actually, what computer &/or motherboard do you have? That might help to narrow things down.

Also an option is getting an add-in SATA controller card based on a non-RAID Silicon Image chipset, though that usually comes only when you can’t get the built-in SATA controllers to work for you at all.


#5

Hmm, the windows generic RAID drivers won’t do because they don’t recognize the RAID 0 stripe volume at all.

An old PC. I have it since 2005.

CPU> AMD Athlon 3200+ 64bit
Motherboard: DFI LanParty UT nF4 SLI-D
2xHDD’s are Excelstor Technology J880S 80GB
(2x512MB) Kingmax PC4000 DDR Hardcore Series
ATI Radeon X850XT PE 256MB DDR3 256bit PCIe

SATA connectors 1&2 are connected to the mentioned HDDs
Pioneer DVR-216D is connected to the 3rd. (switching it to the 4th doesn’t do any good either)
4th connector is free, sometimes used for additional HDD (Hitachi).

The most confusing thing is that this setup worked fine for 2 years before recent OS reinstall (XP SP3).


#6

Moving this thread to General Hardware, seems more appropriate.


#7

Well the only thing I can recommend is getting rid of those two old HDD’s (they won’t be reliable) and replacing them with a modern HDD that will be faster and more reliable. In doing that you can do a fresh install without the need for RAID and you will have a nice speed boost from a modern drive. I would recommend a Samsung F3 or F4 drive. Samsung F3 at Newegg


#8

Hmm… yes, I could always do that but I don’t plan investing in this old PC and besides wouldn’t that be avoiding the problem instead of solving it. I can always buy a new HDD, or SATA to PATA converter for my burner, or just make non-RAID setup. Thank you for the possible solution but I’d like to think of that as a last resort option. :slight_smile:

Talking about reliability…
Excelstor Technology J880S HDDs lasted about 5 years in RAID 0 without a single OS reinstall or defragmentation procedure under heavy use of gaming, developer tools like MS VS, MS SQL, Adobe programs, binary data traffic from news servers, etc. In my opinion, that is pretty impressive even if they are now obsolete. :sad:

Now to the problem.

Since all attempts failed, till now that is, these are the things I want to try next:

  • Updating chipset drivers (includes RAID drivers) to the last available version, not from DFI but from makers of the chipset - nVidia. (I think I tried that one but I’ll try it again just to be sure)
  • Thinker a little around I/O divers and detection order or something like that (don’t know just beating blindly around the bush hehe)
  • Switching SATA connectors form 1&2 to 3&4
    (not sure if its gonna be of any effect)
  • Flashing BIOS (very last resort option because I’ve not done it before and because current setup worked earlier)

#9

[B]S O L V E D[/B]

:smiley: :sad: :cool:

As I thought, RAID controller was a little off. hehehe

DFI drivers weren’t up to date. Driver Genius did a nice job here providing me with latest driver versions. After the update and two restarts, I’ve updated [I]NVIDIA RAID Class Controller[/I] second time and this time from [I]Device Manager[/I] just to be sure the new drivers were applied and detected correctly.

Test and Burn successfully completed!!!

Thank you for your support and goodbye

… till the next error ocures. LOL :wink:


#10

Congrats on figuring out the issue. :slight_smile: