Seeker Posted December 5, 2007 Share Posted December 5, 2007 I was burning a DVD +r DL 2.4 Verbatim and it failed. I have a SONY DVD RW DW-Q28A with latest bios update. Burning 2 folders of av1 videos that gave 97% full. Using UDF/ISO9660 Level 1, Booktype DVD-ROM, speed 2.4 It got to 51% and gave this error message. I Pressed OK to finalise disk It said it could not. Pressed OK to finalise disk again. It did not say a problem 2nd time, But it did not Finalise the disk. This was my first Dual layer DVD. I read the guides. Any advice on what happened or what I did wrong and how to avoid this again. Device Sony SCsiStatus 0x02 Interpretation : Check Condition CDB 2a 00 00 1f c9 60 00 20 00 Interpretion: Write(10) - sectors 2083168 - 283199 Sense Area: 70 00 05 00 00 00 0a 00 00 00 21 00 00 00 00 Interpretion: Invalid Address for write Device Information: SONY DVD RW DW-Q28A KYS4 (ATA) Current Profile: DVD+R DL Disc Information: Status: Incomplete Erasable: No Sessions: 1 Supported Write Speeds: 2.4x, 4x DVD±R DL Boundary Information: L0 Data Zone Capacity: 2,032,544 Changeable: No Physical Format Information (ADIP): Disc ID: MKM-001-00 Book Type: DVD+R DL Part Version: 1 Disc Size: 120mm Maximum Read Rate: Not Specified Number of Layers: 2 Track Path: Opposite Track Path (OTP) Linear Density: 0.293 um/bit Track Density: 0.74 um/track First Physical Sector of Data Area: 196,608 Last Physical Sector of Data Area: 16,580,607 Last Physical Sector in Layer 0: 2,283,519 Physical Format Information (Last Recorded): Disc ID: MKM-001-00 Book Type: DVD-ROM Part Version: 1 Disc Size: 120mm Maximum Read Rate: Not Specified Number of Layers: 2 Track Path: Opposite Track Path (OTP) Linear Density: 0.293 um/bit Track Density: 0.74 um/track First Physical Sector of Data Area: 196,608 Last Physical Sector of Data Area: 2,229,151 Last Physical Sector in Layer 0: 2,229,151 Log: I 19:53:28 ImgBurn Version 2.3.2.0 started! I 19:53:28 Microsoft Windows XP Professional (5.1, Build 2600 : Service Pack 2) I 19:53:28 Total Physical Memory: 1,048,048 KB - Available: 302,780 KB W 19:53:28 Drive C:\ (FAT32) does not support single files > 4 GB in size. W 19:53:28 Drive D:\ (FAT32) does not support single files > 4 GB in size. I 19:53:29 Initialising SPTI... I 19:53:29 Searching for SCSI / ATAPI devices... I 19:53:29 Found 1 DVD±RW! I 19:55:04 Operation Started! I 19:55:04 Building Image Tree... I 19:55:04 Checking Directory Depth... I 19:55:04 Calculating Totals... I 19:55:04 Preparing Image... I 19:55:04 Checking Path Length... I 19:55:04 Image Size: 9,059,041,280 bytes I 19:55:04 Image Sectors: 4,423,360 I 19:55:04 Operation Successfully Completed! - Duration: 00:00:00 I 19:56:51 Operation Started! I 19:56:51 Building Image Tree... I 19:56:51 Checking Directory Depth... I 19:56:51 Calculating Totals... I 19:56:51 Preparing Image... I 19:56:51 Checking Path Length... I 19:56:51 Image Size: 9,059,041,280 bytes I 19:56:51 Image Sectors: 4,423,360 I 19:56:51 Operation Successfully Completed! - Duration: 00:00:00 I 19:57:37 Operation Started! I 19:57:37 Building Image Tree... I 19:57:37 Checking Directory Depth... I 19:57:37 Calculating Totals... I 19:57:37 Preparing Image... I 19:57:37 Checking Path Length... I 19:57:37 Image Size: 9,059,041,280 bytes I 19:57:37 Image Sectors: 4,423,360 I 19:57:37 Operation Successfully Completed! - Duration: 00:00:00 I 19:59:50 Operation Started! I 19:59:50 Building Image Tree... I 19:59:50 Checking Directory Depth... I 19:59:50 Calculating Totals... I 19:59:50 Preparing Image... I 19:59:50 Checking Path Length... I 19:59:50 Image Size: 8,075,051,008 bytes I 19:59:50 Image Sectors: 3,942,896 I 19:59:50 Operation Successfully Completed! - Duration: 00:00:00 I 20:00:14 Operation Started! I 20:00:14 Building Image Tree... I 20:00:14 Checking Directory Depth... I 20:00:14 Calculating Totals... I 20:00:14 Preparing Image... I 20:00:14 Checking Path Length... I 20:00:14 Image Size: 8,325,300,224 bytes I 20:00:15 Image Sectors: 4,065,088 I 20:00:15 Operation Successfully Completed! - Duration: 00:00:00 I 20:01:13 Operation Started! I 20:01:13 Building Image Tree... I 20:01:13 Checking Directory Depth... I 20:01:13 Calculating Totals... I 20:01:13 Preparing Image... I 20:01:13 Checking Path Length... I 20:01:13 Image Size: 9,059,041,280 bytes I 20:01:13 Image Sectors: 4,423,360 I 20:01:13 Operation Successfully Completed! - Duration: 00:00:00 I 20:01:23 Operation Started! I 20:01:23 Building Image Tree... I 20:01:23 Checking Directory Depth... I 20:01:23 Calculating Totals... I 20:01:23 Preparing Image... I 20:01:23 Checking Path Length... I 20:01:23 Image Size: 8,808,792,064 bytes I 20:01:23 Image Sectors: 4,301,168 I 20:01:23 Operation Successfully Completed! - Duration: 00:00:00 I 20:01:59 Operation Started! I 20:01:59 Building Image Tree... I 20:01:59 Checking Directory Depth... I 20:01:59 Calculating Totals... I 20:01:59 Preparing Image... I 20:01:59 Checking Path Length... I 20:01:59 Image Size: 8,075,051,008 bytes I 20:01:59 Image Sectors: 3,942,896 I 20:01:59 Operation Successfully Completed! - Duration: 00:00:00 I 20:02:17 Operation Started! I 20:02:17 Building Image Tree... I 20:02:17 Checking Directory Depth... I 20:02:17 Calculating Totals... I 20:02:17 Preparing Image... I 20:02:17 Checking Path Length... I 20:02:17 Image Size: 8,325,300,224 bytes I 20:02:17 Image Sectors: 4,065,088 I 20:02:17 Operation Successfully Completed! - Duration: 00:00:00 I 21:49:07 Operation Started! I 21:49:07 Building Image Tree... I 21:49:07 Checking Directory Depth... I 21:49:07 Calculating Totals... I 21:49:07 Preparing Image... I 21:49:07 Checking Path Length... I 21:49:07 Image Size: 8,325,300,224 bytes I 21:49:07 Image Sectors: 4,065,088 I 21:49:58 Operation Successfully Completed! - Duration: 00:00:50 I 21:49:58 Operation Started! I 21:49:58 Source File: -==/\/[bUILD IMAGE]\/\==- I 21:49:58 Source File Sectors: 4,065,088 (MODE1/2048) I 21:49:58 Source File Size: 8,325,300,224 bytes I 21:49:58 Source File Volume Identifier: ANGEL_SERIES_5 I 21:49:58 Source File Application Identifier: IMGBURN V2.3.2.0 - THE ULTIMATE IMAGE BURNER! I 21:49:58 Source File Implementation Identifier: ImgBurn I 21:49:58 Source File File System(s): ISO9660, UDF (1.02) I 21:49:58 Destination Device: [0:2:0] SONY DVD RW DW-Q28A KYS4 (E:) (ATA) I 21:49:58 Destination Media Type: DVD+R DL (Disc ID: MKM-001-00) (Speeds: 2.4x, 4x) I 21:49:58 Destination Media Sectors: 4,173,824 I 21:49:58 Write Mode: DVD I 21:49:58 Write Type: DAO I 21:49:58 Write Speed: 2.4x I 21:49:58 Link Size: Auto I 21:49:58 Test Mode: No I 21:49:58 BURN-Proof: Enabled I 21:49:58 Optimal L0 Data Zone Capacity: 2,032,544 I 21:49:58 Optimal L0 Data Zone Method: ECC Block Boundary I 21:50:48 Filling Buffer... (40 MB) I 21:50:50 Writing LeadIn... I 21:50:52 Writing Image... (LBA: 0 - 4065087) I 21:50:52 Writing Layer 0... (LBA: 0 - 2032543) I 22:11:25 Writing Layer 1... (LBA: 2032544 - 4065087) W 22:12:01 Failed to Write Sectors 2083168 - 2083199 - Write Error W 22:12:01 Retrying (1 of 20)... W 22:12:01 Retry Failed - Invalid Address For Write W 23:47:35 Retrying (39)... W 23:47:35 Retry Failed - Invalid Address For Write E 23:54:07 Failed to Write Sectors 2083168 - 2083199 - Write Error I 23:54:07 Synchronising Cache... I 23:54:08 Closing Track... I 23:54:12 Finalising Disc... W 23:54:44 Potential 'WaitImmediateIO' Deferred Error - (0/2) - Session Fixation Error Writing Lead Out E 23:55:43 Failed to Write Image! E 23:55:44 Operation Failed! - Duration: 02:05:45 I 23:55:44 Average Write Rate: 563 KB/s (0.4x) - Maximum Write Rate: 4,095 KB/s (3.0x) Link to comment Share on other sites More sharing options...
LIGHTNING UK! Posted December 5, 2007 Share Posted December 5, 2007 Have you tried at 4x? My samsung s203b doesn't like burning those at 2.4x. Switch to 4x and it's fine. The scans are far better at that speed too - which is the complete opposite from what I'd expect. Link to comment Share on other sites More sharing options...
Seeker Posted December 5, 2007 Author Share Posted December 5, 2007 (edited) I have only tried one at 2.4 x Its not a bad disk then. Or the disk being nearly full. Edited December 5, 2007 by Seeker Link to comment Share on other sites More sharing options...
LIGHTNING UK! Posted December 5, 2007 Share Posted December 5, 2007 I assumed you'd tried more than 1. If you haven't, by all means please do so. Link to comment Share on other sites More sharing options...
Seeker Posted December 6, 2007 Author Share Posted December 6, 2007 Hi a question about the log. Why does the log show a Image size that varies From I 19:55:04 Image Size: 9,059,041,280 bytes I 19:55:04 Image Sectors: 4,423,360 To I 20:01:59 Image Size: 8,075,051,008 bytes I 20:01:59 Image Sectors: 3,942,896 According to windows it should be 8,325,103,616 It does not make sense that it should report a varying file size. When I load the same files now the log shows 8,325,300,224 bytes Not 9,059,041,280 bytes as it did previously. Link to comment Share on other sites More sharing options...
dontasciime Posted December 6, 2007 Share Posted December 6, 2007 scan you hard drive for errors Dunno what your doing to have it show up diff sizes each time but if you building an image instead of burning that might explain it Link to comment Share on other sites More sharing options...
Seeker Posted December 6, 2007 Author Share Posted December 6, 2007 (edited) Yes I was building 2 folders of avi videos from my harddisk. I will check it. Edited December 6, 2007 by Seeker Link to comment Share on other sites More sharing options...
LIGHTNING UK! Posted December 6, 2007 Share Posted December 6, 2007 Could it be that you're selecting a different layer break position? 'Image Size' includes the file system itself. When you look in explorer at the files, that's obviously not taken into account. Link to comment Share on other sites More sharing options...
Seeker Posted December 6, 2007 Author Share Posted December 6, 2007 I used Right Click Properties "size on disk". When I building these 2 folders of avi videos It does not give me a choose of layer break position. I was curios why I was getting a Image size that varies in my log. Link to comment Share on other sites More sharing options...
LIGHTNING UK! Posted December 6, 2007 Share Posted December 6, 2007 Ah ok, just of AVI files, sorry I didn't see that before and assumed it was a DVD Video disc. If you run Build mode on the same content the size will be the same each time - so if the size changed, the source must have changed too. Link to comment Share on other sites More sharing options...
Seeker Posted December 6, 2007 Author Share Posted December 6, 2007 Also I noted. I 21:50:52 Writing Image... (LBA: 0 - 4065087) I 21:50:52 Writing Layer 0... (LBA: 0 - 2032543) I 22:11:25 Writing Layer 1... (LBA: 2032544 - 4065087) W 22:12:01 Failed to Write Sectors 2083168 - 2083199 - Write Erro ImgBurn says the size of layer 0 is, 0 to 2,283,519 Does the fact that it wrote to layer 1 (LBA: 2032544) on layer 0 cause a problem? Link to comment Share on other sites More sharing options...
LIGHTNING UK! Posted December 6, 2007 Share Posted December 6, 2007 That's PHYSICAL sector 2,283,519, not LBA sector. You need to subtract the value of 'First Physical Sector of Data Area' to get it in normal LBA terms (i.e. subtract 196,608) = 2086911 Link to comment Share on other sites More sharing options...
Recommended Posts