Don't understand why this burn failed

Discussion in 'Nero discussion' started by doodler, May 11, 2006.

  1. doodler

    doodler Member

    Joined:
    May 11, 2006
    Messages:
    6
    Likes Received:
    0
    Trophy Points:
    11
    Could someone please look at this log and poinit oout the relevent places to look for failure reasons. I'm kind of a newbie and just don't get it.

    Thanks so much...


    Windows XP 5.1
    IA32
    WinAspi: File 'Wnaspi32.dll': Ver=4.71 (0002), size=45056 bytes, created 11/21/2005 1:48:21 AM
    ahead WinASPI: File 'C:\Program Files\Ahead\Nero\Wnaspi32.dll': Ver=2.0.1.74, size=164112 bytes, created 10/26/2004 6:35:34 PM
    Nero Version: 6.6.0.18
    Internal Version: 6, 6, 0, 18e
    (Nero Express)
    Recorder: <PLEXTOR DVDR PX-716A> Version: 1.09 - HA 1 TA 0 - 6.6.0.18
    Adapter driver: <atapi> HA 1
    Drive buffer : 8192kB
    Bus Type : default (0) -> ATAPI, detected: ATAPI
    CD-ROM: <PLEXTOR DVDR PX-716A >Version: 1.09 - HA 1 TA 0 - 6.6.0.18
    Adapter driver: <atapi> HA 1

    === Scsi-Device-Map ===
    DiskPeripheral : WDC WD4000KS-00MNB0 iaStor Port 0 ID 0 DMA: On
    DiskPeripheral : ST3200822AS iaStor Port 0 ID 1 DMA: Off
    DiskPeripheral : HDS722512VLSA80 iaStor Port 0 ID 2 DMA: Off
    CdRomPeripheral : PLEXTOR DVDR PX-716A atapi Port 1 ID 0 DMA: On
    CdRomPeripheral : TEAC DVD+RW DV-W58E atapi Port 1 ID 1 DMA: On
    DiskPeripheral : Maxtor 6Y160P0 YAR4 ultra Port 2 ID 0 DMA: Off
    DiskPeripheral : Maxtor 6Y160P0 YAR4 ultra Port 2 ID 1 DMA: Off
    DiskPeripheral : Maxtor 6Y120P0 YAR4 ultra Port 2 ID 2 DMA: Off

    === CDRom-Device-Map ===
    PLEXTOR DVDR PX-716A D: CDRom0
    TEAC DVD+RW DV-W58E E: CDRom1
    =======================

    AutoRun : 1
    Excluded drive IDs:
    WriteBufferSize: 83886080 (0) Byte
    ShowDrvBufStat : 0
    BUFE : 0
    Physical memory : 1021MB (1046044kB)
    Free physical memory: 548MB (562088kB)
    Memory in use : 46
    Uncached PFiles: 0x0
    Use Inquiry : 1
    Global Bus Type: default (0)
    Check supported media : Disabled (0)

    11.5.2006
    Burn DVD Image
    7:29:50 AM #1 Text 0 File Reader.cpp, Line 127
    Reader running

    7:29:50 AM #2 Text 0 File Writer.cpp, Line 122
    Writer PLEXTOR DVDR PX-716A running

    7:29:50 AM #3 Text 0 File Burncd.cpp, Line 3233
    Turn on Disc-At-Once, using DVD media

    7:29:50 AM #4 Text 0 File DlgWaitCD.cpp, Line 270
    Last possible write address on media: 2295103 (510:01.28, 4482MB)
    Last address to be written: 2286427 (508:05.52, 4465MB)

    7:29:50 AM #5 Text 0 File DlgWaitCD.cpp, Line 282
    Write in overburning mode: NO (enabled: CD)

    7:29:50 AM #6 Text 0 File DlgWaitCD.cpp, Line 2483
    Recorder: PLEXTOR DVDR PX-716A, Media type: DVD+R
    Disc Manufacturer ID: YUDEN000, Media Type ID: T02, Product revision number: 0
    Disc Application Code: 0, Extended Information Indicators: 3

    7:29:50 AM #7 Text 0 File DlgWaitCD.cpp, Line 448
    >>> Protocol of DlgWaitCD activities: <<<
    =========================================

    7:29:50 AM #8 Text 0 File ThreadedTransferInterface.cpp, Line 838
    Setup items (after recorder preparation)
    0: TRM_DATA_MODE1 (2 - CD-ROM Mode 1, ISO 9660)
    2 indices, index0 (150) not provided
    original disc pos #0 + 2286428 (2286428) = #2286428/508:5.53
    not relocatable, disc pos for caching/writing not required/not required, no patch infos
    -> TRM_DATA_MODE1, 2048, config 0, wanted index0 0 blocks, length 2286428 blocks [PLEXTOR DVDR PX-716A]
    --------------------------------------------------------------

    7:29:50 AM #9 Text 0 File ThreadedTransferInterface.cpp, Line 1051
    Prepare recorder [PLEXTOR DVDR PX-716A] for write in CUE-sheet-DAO
    DAO infos:
    ==========
    MCN: ""
    TOCType: 0x00; Session Closed, disc fixated
    Tracks 1 to 1:
    1: TRM_DATA_MODE1, 2048/0x00, FilePos 0 0 4682604544, ISRC ""
    DAO layout:
    ===========
    __Start_|____Track_|_Idx_|_CtrlAdr_|_RecDep__________
    0 | lead-in | 0 | 0x41 | 0x00
    0 | 1 | 0 | 0x41 | 0x00
    0 | 1 | 1 | 0x41 | 0x00
    2286428 | lead-out | 1 | 0x41 | 0x00

    7:29:50 AM #10 Phase 24 File dlgbrnst.cpp, Line 1832
    Caching of files started

    7:29:50 AM #11 Text 0 File Burncd.cpp, Line 4122
    Cache writing successful.

    7:29:50 AM #12 Phase 25 File dlgbrnst.cpp, Line 1832
    Caching of files completed

    7:29:50 AM #13 Phase 36 File dlgbrnst.cpp, Line 1832
    Burn process started at 6x (8,310 KB/s)

    7:29:50 AM #14 Text 0 File ThreadedTransferInterface.cpp, Line 2661
    Verifying disc position of item 0 (not relocatable, no disc pos, no patch infos, orig at #0): write at #0

    7:29:50 AM #15 Text 0 File Cdrdrv.cpp, Line 8892
    ---- DVD Structure: Physical Format Information (00h) ----
    Layer: 0, Address: 0 (0 h), AGID: 0; Length: 258
    Book Type: DVD+R (10), Part Version: 1.0x (1)
    Disc Size: 120 mm, Maximum Rate: <not specified> (F h)
    Number of Layers: 1, Track Path: Parallel Track Path (PTP), Layer Type: recordable
    Linear Density: 0,267 um/bit, Track Density: 0,74 um/track
    Starting Physical Sector Number of Data Area: 30000 h (DVD-ROM, DVD-R/-RW, DVD+R/+RW)
    End Physical Sector Number of Data Area: 26053F h
    End Sector Number in Layer 0: 0 h (LBN: FFFD0000 h, 4193920 MB)
    Data in Burst Cutting Area (BCA) does not exist
    Disc Application Code: 0 / 0 h
    Extended Information indicators: 3 h
    Disc Manufacturer ID: YUDEN000
    Media type ID: T02
    Product revision number: 0
    Number of Physical format information bytes in use in ADIP up to byte 63: 56
    Media Specific [16..63]:
    00 00 03 59 55 44 45 4E - 30 30 30 54 30 32 00 38 ...YUDEN000T02.8
    23 54 37 10 02 4E 72 02 - 8C 63 16 16 0B 0B 0A 0A #T7..Nr..c......
    01 19 1B 0C 0C 0C 0D 01 - 00 00 00 00 00 00 00 00 ................

    7:29:50 AM #16 Text 0 File DVDR.cpp, Line 5659
    Drive: PLEXTOR DVDR PX-716A
    Book Type request [PX]: DVD-ROM
    Changing the Book Type was finished successfully, return code 0

    7:29:50 AM #17 CDR -1207 File DVDR.cpp, Line 5306
    Book Type automatically set to: DVD-ROM

    7:29:50 AM #18 Text 0 File DVDPlusRW.cpp, Line 659
    Start write address at LBA 0
    DVD high compatibility mode: Yes

    7:29:52 AM #19 Text 0 File Cdrdrv.cpp, Line 1288
    07:29:52.000 - PLEXTOR DVDR PX-716A\H1 T0 : Queue again later

    7:40:01 AM #20 SCSI -1114 File Cdrdrv.cpp, Line 1436
    SCSI Exec, HA 1, TA 0, LUN 0, buffer 0x03810000
    Status: 0x04 (0x01, SCSI_ERR)
    HA-Status 0x00 (0x00, OK)
    TA-Status 0x02 (0x01, SCSI_TASTATUS_CHKCOND)
    Sense Key: 0x06 (KEY_UNIT_ATTENTION)
    Sense Code: 0x29
    Sense Qual: 0x00
    CDB Data: 0x2A 0x00 0x00 0x1A 0x2E 0xA0 0x00 0x00 0x20 0x00 0x00 0x00
    Sense Data: 0x70 0x00 0x06 0x00 0x00 0x00 0x00 0x0A
    0x00 0x00 0x00 0x00 0x29 0x00

    7:40:01 AM #21 CDR -1114 File Writer.cpp, Line 311
    Reset occurred

    7:40:01 AM #22 Text 0 File ThreadedTransfer.cpp, Line 228
    all writers idle, stopping conversion

    7:40:01 AM #23 Text 0 File ThreadedTransfer.cpp, Line 222
    conversion idle, stopping reader

    7:40:01 AM #24 SCSI -1066 File Cdrdrv.cpp, Line 1182
    SCSI Exec, HA 1, TA 0, LUN 0
    Status: 0x04 (0x01, SCSI_ERR)
    HA-Status 0x00 (0x00, OK)
    TA-Status 0x02 (0x01, SCSI_TASTATUS_CHKCOND)
    Sense Key: 0x05 (KEY_ILLEGAL_REQUEST)
    Sense Code: 0x24
    Sense Qual: 0x00
    CDB Data: 0x5B 0x01 0x01 0x00 0x00 0x01 0x00 0x00 0x00 0x00 0x00 0x00
    Sense Data: 0x70 0x00 0x05 0x00 0x00 0x00 0x00 0x0A
    0x00 0x00 0x00 0x00 0x24 0x00

    7:40:01 AM #25 SCSI -1066 File Cdrdrv.cpp, Line 1182
    SCSI Exec, HA 1, TA 0, LUN 0
    Status: 0x04 (0x01, SCSI_ERR)
    HA-Status 0x00 (0x00, OK)
    TA-Status 0x02 (0x01, SCSI_TASTATUS_CHKCOND)
    Sense Key: 0x05 (KEY_ILLEGAL_REQUEST)
    Sense Code: 0x24
    Sense Qual: 0x00
    CDB Data: 0x5B 0x01 0x06 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
    Sense Data: 0x70 0x00 0x05 0x00 0x00 0x00 0x00 0x0A
    0x00 0x00 0x00 0x00 0x24 0x00

    7:40:01 AM #26 Text 0 File DVDR.cpp, Line 5659
    Drive: PLEXTOR DVDR PX-716A
    Book Type request [PX]: DVD-ROM
    Changing the Book Type was finished successfully, return code 0

    7:40:01 AM #27 CDR -1066 File WriterStatus.cpp, Line 167
    Invalid field in command

    7:40:01 AM #28 TRANSFER -24 File WriterStatus.cpp, Line 167
    Could not perform end of Disc-at-once

    7:40:01 AM #29 Phase 38 File dlgbrnst.cpp, Line 1832
    Burn process failed at 6x (8,310 KB/s)


    Existing drivers:
    File 'Drivers\ASPI32.SYS': Ver=4.71 (0002) built by: WinDDK, size=16512 bytes, created 11/21/2005 1:48:21 AM
    File 'Drivers\PXHELP20.SYS': Ver=2.03.32a, size=20640 bytes, created 4/6/2006 2:15:29 PM (Prassi/Veritas driver for win 2K)
    File 'Drivers\atapi.sys': Ver=5.1.2600.2180 (xpsp_sp2_rtm.040803-2158), size=95360 bytes, created 8/3/2004 10:59:44 PM (Adapter driver for rec)

    Registry Keys:
    HKLM\Software\Microsoft\Windows NT\CurrentVersion\WinLogon\AllocateCDROMs : 0 (Security Option)
     
  2. LOCOENG

    LOCOENG Moderator Staff Member

    Joined:
    Feb 4, 2005
    Messages:
    10,818
    Likes Received:
    4
    Trophy Points:
    118
    DMA should be on for all drives...here is a guide: http://forums.afterdawn.com/thread_view.cfm/260038

    You are attempting to burn too close to the edge of the disc, reduce your target size in DVD Shrink or Recode to 4300.



     
  3. doodler

    doodler Member

    Joined:
    May 11, 2006
    Messages:
    6
    Likes Received:
    0
    Trophy Points:
    11
    Thanks. I'll try those suggestions.
     
  4. LOCOENG

    LOCOENG Moderator Staff Member

    Joined:
    Feb 4, 2005
    Messages:
    10,818
    Likes Received:
    4
    Trophy Points:
    118
    You are very welcome...good luck and happy burning.
     
  5. doodler

    doodler Member

    Joined:
    May 11, 2006
    Messages:
    6
    Likes Received:
    0
    Trophy Points:
    11
    I was looking, and all the drives that are listed as 'DMA: Off' are either 1st gen SATA or on an Ultra ATA controller card.

    [bold]=== Scsi-Device-Map ===
    DiskPeripheral : WDC WD4000KS-00MNB0 iaStor Port 0 ID 0 DMA: On
    DiskPeripheral : ST3200822AS iaStor Port 0 ID 1 DMA: Off
    DiskPeripheral : HDS722512VLSA80 iaStor Port 0 ID 2 DMA: Off
    CdRomPeripheral : PLEXTOR DVDR PX-716A atapi Port 1 ID 0 DMA: On
    CdRomPeripheral : TEAC DVD+RW DV-W58E atapi Port 1 ID 1 DMA: On
    DiskPeripheral : Maxtor 6Y160P0 YAR4 ultra Port 2 ID 0 DMA: Off
    DiskPeripheral : Maxtor 6Y160P0 YAR4 ultra Port 2 ID 1 DMA: Off
    DiskPeripheral : Maxtor 6Y120P0 YAR4 ultra Port 2 ID 2 DMA: Off[/bold]

    The WDC WD4000KS with the DMA on is a new 2nd gen SATA drive.

    Looking in the device manager, I only see DMA settings for IDE ATA/ATAPI controllers. The SATA AHCI controller and Ultra ATA Storage Controller don't have any mention of DMA.

    Is there somewhere else I can go to turn on DMA on SATA controllers?
     
  6. Saltgrass

    Saltgrass Regular member

    Joined:
    Apr 2, 2006
    Messages:
    1,116
    Likes Received:
    0
    Trophy Points:
    46
    I am not good at these logs, but is the following line normal or indicate a problem.

    7:40:01 AM #21 CDR -1114 File Writer.cpp, Line 311
    Reset occurred
     
  7. LOCOENG

    LOCOENG Moderator Staff Member

    Joined:
    Feb 4, 2005
    Messages:
    10,818
    Likes Received:
    4
    Trophy Points:
    118
    I'm not sure on the DMA for SATA drives, but if your data is coming off the WD4000KS which has the DMA enabled , you should be OK.
     
  8. gwendolin

    gwendolin Senior member

    Joined:
    Jun 29, 2005
    Messages:
    7,447
    Likes Received:
    0
    Trophy Points:
    116
    [bold]
    Solution:

    If you do a search on SCSI Command Errors, you will find that many others have had the same issue as yours with USB Recorders, regardless of the software used. Meaning, it occurs with Nero, CD Creator, RecordNow, etc.

    And the error message varies from SCSI Command Error, Bus Rest, etc...

    In most cases, users have found that updating the drivers for the USB Controller resolves the issue. Other found a new External Chassis for the Recorder resolved the issue. And we provided a work around in our MMC.DLL file that causes our software to reissue the command till the recorder is free and accpets, instead of timing out so soon after a lack of response from the device. This resolved the issue for some, but not for others. This MMC.DLL file is part of Nero 6.6.0.3 and above builds.

    Try to disconnected all USB devices except for the external DVD burner.

    As a last resort, after trying the above solutions and others, they finally connect as an internal to the system and all issues are resolved.
     
  9. doodler

    doodler Member

    Joined:
    May 11, 2006
    Messages:
    6
    Likes Received:
    0
    Trophy Points:
    11
    Thanks guys for the advice.

    Gwendolin, thank you for the in-depth solution, but none of my drives are USB, so either you have misunderstood my problem, or I am misunderstanding your solution.

    My Hard drive setup is as follows:

    Attached to Motherboard SATA:
    DiskPeripheral : WDC WD4000KS-00MNB0 iaStor Port 0 ID 0 DMA: On
    DiskPeripheral : ST3200822AS iaStor Port 0 ID 1 DMA: Off
    DiskPeripheral : HDS722512VLSA80 iaStor Port 0 ID 2 DMA: Off

    Attached to Motherboard IDE:
    CdRomPeripheral : PLEXTOR DVDR PX-716A atapi Port 1 ID 0 DMA: On
    CdRomPeripheral : TEAC DVD+RW DV-W58E atapi Port 1 ID 1 DMA: On

    Attached to IDE ATA133 Controller expansion card:
    DiskPeripheral : Maxtor 6Y160P0 YAR4 ultra Port 2 ID 0 DMA: Off
    DiskPeripheral : Maxtor 6Y160P0 YAR4 ultra Port 2 ID 1 DMA: Off
    DiskPeripheral : Maxtor 6Y120P0 YAR4 ultra Port 2 ID 2 DMA: Off

    The data I write from is stored on the ST3200822AS (DMA off) drive. I have been writing succcessfully from that drive since I installed the OS a month or so ago. It has been listed as DMA off during all that time and I assumed this was because it was a 1st gen SATA drive, whereas the WD4000KS listed as DMA on is a newer 2nd gen drive. I had assumed 1st gen drives either didn't support/need DMA, or the BIOS just didn't see them as DMA capable.

    Ata any rate, you guys are great for helping, and I really appreciate your time.

     
  10. doodler

    doodler Member

    Joined:
    May 11, 2006
    Messages:
    6
    Likes Received:
    0
    Trophy Points:
    11
    I just read this from a guy on Microsoft's Technet forum. He was confused by his PC not reporting his SATA drive in DMA so he wrote to Intel tech support asking about it. Below is their reply:

    [bold]Thank you for contacting Intel(R) Technical Support.

    The PIO, DMA and UDMA concepts are exclusively for IDE ATA/TAPI drives. These terms do not apply for Serial ATA drives. The fastest ATA mode is UDMA 6 (133 MB/s) while the Serial ATA controller can transfer data up to 150 MB/s. Operating systems and other applications may recognize Serial ATA drives as UDMA5/6 for compatibility purposes only. However, this does not reflect the correct transfer rate of your drive.

    Please do not hesitate to contact us again if you need further assistance."[/bold]
     
  11. LOCOENG

    LOCOENG Moderator Staff Member

    Joined:
    Feb 4, 2005
    Messages:
    10,818
    Likes Received:
    4
    Trophy Points:
    118
    Good information...so only your ide drives need to be in DMA, unless there is a compatability issue.
     
  12. arniebear

    arniebear Active member

    Joined:
    Jan 2, 2005
    Messages:
    7,191
    Likes Received:
    0
    Trophy Points:
    96
    I have two SATA drives which are showing to be in DMA mode and that's the way they came with my Dell, it has Intel Chipset. Using the chipset utility my SATA I/O controller reads IDE mode, so what is that saying then? This is the way the Chipset sw sets it up on installation. And the two SATA drives read DMA on.

    [​IMG]

     
  13. doodler

    doodler Member

    Joined:
    May 11, 2006
    Messages:
    6
    Likes Received:
    0
    Trophy Points:
    11
    Apparently, different chipsets report SATA in different ways.

    It seems like SATA has been around long enough for everyone to have a standard way of cataloging or reporting them.

    I suppose we each have to know our motherboards intimately in order to get the most out of them.
     

Share This Page