Jump to content

geohei

Members
  • Posts

    35
  • Joined

  • Last visited

Everything posted by geohei

  1. To complete ... I found the following for my "Primeon" media in the log: I 17:09:33 Source Media Type: BD-R (Disc ID: RITEK-DR2-000) Also, I now managed to write successfully 49.947.934.720 and 49.511.464.960 (highest so far) bytes.
  2. I'll give those a try once I finished my Primeon media. Thanks. Just for info ... the media advertises that 50.050.629.632 bytes can be written. However 49.990.926.336 fails, but 49.918.443.520 worked. I will check if this applies for all media (of the remaining Primeon stack).
  3. To make the thread complete. Here the log ... ... I 20:05:17 Writing LeadIn... I 20:05:18 Writing Session 1 of 1... (1 Track, LBA: 0 - 24427359) I 20:05:18 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 24427359) I 20:05:18 Writing Layer 0... (LBA: 0 - 12219391) W 20:25:58 Failed to Write Sectors 10885696 - 10885727 - Reason: Invalid Field in CDB W 20:25:58 Retrying (1 of 20)... W 20:25:58 Retry Failed - Reason: Invalid Field in CDB W 20:25:58 Retrying (2 of 20)... W 20:25:58 Retry Failed - Reason: Invalid Field in CDB W 20:25:58 Retrying (3 of 20)... W 20:25:58 Retry Failed - Reason: Invalid Field in CDB W 20:25:58 Retrying (4 of 20)... W 20:25:58 Retry Failed - Reason: Invalid Field in CDB W 20:25:58 Retrying (5 of 20)... W 20:25:58 Retry Failed - Reason: Invalid Field in CDB W 20:25:58 Retrying (6 of 20)... W 20:25:58 Retry Failed - Reason: Invalid Field in CDB W 20:25:58 Retrying (7 of 20)... W 20:25:58 Retry Failed - Reason: Invalid Field in CDB W 20:25:58 Retrying (8 of 20)... W 20:25:58 Retry Failed - Reason: Invalid Field in CDB W 20:25:58 Retrying (9 of 20)... W 20:25:58 Retry Failed - Reason: Invalid Field in CDB W 20:25:58 Retrying (10 of 20)... W 20:25:58 Retry Failed - Reason: Invalid Field in CDB W 20:25:58 Retrying (11 of 20)... W 20:25:58 Retry Failed - Reason: Invalid Field in CDB W 20:25:58 Retrying (12 of 20)... W 20:25:58 Retry Failed - Reason: Invalid Field in CDB W 20:25:58 Retrying (13 of 20)... W 20:25:58 Retry Failed - Reason: Invalid Field in CDB W 20:25:58 Retrying (14 of 20)... W 20:25:58 Retry Failed - Reason: Invalid Field in CDB W 20:25:58 Retrying (15 of 20)... W 20:25:58 Retry Failed - Reason: Invalid Field in CDB W 20:25:58 Retrying (16 of 20)... W 20:25:58 Retry Failed - Reason: Invalid Field in CDB W 20:25:58 Retrying (17 of 20)... W 20:25:58 Retry Failed - Reason: Invalid Field in CDB W 20:25:58 Retrying (18 of 20)... W 20:25:58 Retry Failed - Reason: Invalid Field in CDB W 20:25:58 Retrying (19 of 20)... W 20:25:58 Retry Failed - Reason: Invalid Field in CDB W 20:25:58 Retrying (20 of 20)... W 20:25:58 Retry Failed - Reason: Invalid Field in CDB E 20:46:05 Failed to Write Sectors 10885696 - 10885727 - Reason: Invalid Field in CDB I 20:46:05 Synchronising Cache... W 20:46:05 Synchronise Cache Failed! - Reason: Invalid Field in CDB E 20:46:08 Synchronise Cache Failed! - Reason: Invalid Field in CDB W 20:46:13 User opted to skip the 'Close Track/Session/Disc' functions. ...
  4. Thanks for the reply. Sorry for the German Amazon link. So basically, you say that BD-R DL media have problems by itself (in general), my particular brand (Primeon) might have issues and the drive (ASUS) could be the culprit. So it could be anything.
  5. https://www.amazon.de/gp/product/B00ULAO50U/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8&th=1 If I get it right, you say the culprit should be the drive, not the media, right? Nevertheless, I'm surprised that the drive might fail to write at the edge, while the rest of the media is written properly. I would have have expected that drive/media combination either writing correctly or mot at all, but not that there is a tolerance (in the drive) which only shows at the edges.
  6. The drive: ASUS BW-16D1HT 3.00 (SATA) The media: Primeon BD-RDL50 GB 2x-8x
  7. Sorry ... replace "tile" with "stack". So the boundary layer is at the outer edge of the media? Is there a difference in production quality within the same media stack? I believe it's strange that one fails an the boundary layer, and the next one work (while trying to write exactly the same data).
  8. Hi. Is it possible, that the same manufacturer/tile of blu-ray BD-R DL (#50 GB) media, has such production tolerances/differences, that only approx. 49.5xx.xxx.xxx bytes (i.s.o 50.050.629.632 bytes) can be written? On top I noticed that one BD-R DL media fails at the layer change (#25 GB) while the next one succeeds (same tile!). Also, Test Mode always runs successfully, while real writes might fail afterwards. Is all of the above "normal"? If yes, I have to leave about 3% free space in the future in order to be safe. Many thanks.
  9. Yes, the drive went stuck forever. I can't recall if it was still spinning or not. I had to stop ImgBurn via Task Manager (End Task). Even after that, the drive was flashing and I could not eject the disc. I had to restart the system. After restart of the system, I checked the disc and it looked like all data was on. Since all data had md5 checksums, I ran them. All data was correct! Nevertheless I didn't "trust" this disc, reduced the volume from 50.045... to 50.043... and this time the write operation succeeded!
  10. Just to make it clear. If the disc reports a capacity to ImgBurn, and ImgBurn knows how much data to write, does this mean that all data (including structures, overhead, ...) fit the disc and will be written successfully? In other words, could it be that the 50.045.xxx.xxx Bytes were too much for the disc and ImgBurn would not complain prioir write, but the drive would eventually just fail to write (like in my case)?
  11. Yes, it is at the very end of the disc. Nevertheless it shouldn't do so. I did many sessions with similar payload (99% full) and never had this issue before.
  12. I 06:24:32 ImgBurn Version 2.5.8.0 started! I 06:24:32 Microsoft Windows 7 Ultimate x64 Edition (6.1, Build 7601 : Service Pack 1) I 06:24:32 Total Physical Memory: 16.664.720 KiB - Available: 11.269.268 KiB W 06:24:32 Drive X:\ (FAT32) does not support single files > 4 GiB in size. I 06:24:32 Initialising SPTI... I 06:24:32 Searching for SCSI / ATAPI devices... I 06:24:32 -> Drive 1 - Info: ASUS BW-16D1HT 3.00 (K:) (SATA) I 06:24:32 -> Drive 2 - Info: ATAPI iHBS312 2 PL17 (L:) (SATA) I 06:24:32 Found 2 BD-ROM/HD DVD-ROMs, 1 BD-RE and 1 BD-RE XL! I 06:24:44 Project Successfully Loaded! I 06:24:44 File Name: E:\Application Data\ImgBurn\Project Files\Doc_647.ibb I 06:24:49 Operation Started! I 06:24:49 Building Image Tree... I 06:24:49 Calculating Totals... I 06:24:49 Preparing Image... I 06:24:49 Contents: 40 Files, 0 Folders I 06:24:49 Content Type: Data I 06:24:49 Data Type: MODE1/2048 I 06:24:49 File System(s): UDF (2.50) I 06:24:49 Volume Label: Documentary_647 I 06:24:49 Size: 50.045.882.694 bytes I 06:24:49 Sectors: 24.436.485 I 06:24:49 Image Size: 50.046.959.616 bytes I 06:24:49 Image Sectors: 24.436.992 I 06:24:58 Operation Successfully Completed! - Duration: 00:00:08 I 06:24:58 Operation Started! I 06:24:58 Source File: -==/\/[BUILD IMAGE]\/\==- I 06:24:58 Source File Sectors: 24.436.992 (MODE1/2048) I 06:24:58 Source File Size: 50.046.959.616 bytes I 06:24:58 Source File Volume Identifier: Documentary_647 I 06:24:58 Source File Volume Set Identifier: 565033180174E085 I 06:24:58 Source File Application Identifier: ImgBurn v2.5.8.0 I 06:24:58 Source File Implementation Identifier: ImgBurn I 06:24:58 Source File File System(s): UDF (2.50) I 06:24:58 Destination Device: [5:0:0] ASUS BW-16D1HT 3.00 (K:) (SATA) I 06:24:58 Destination Media Type: BD-R (Disc ID: RITEK-DR2-000) I 06:24:58 Destination Media Supported Write Speeds: 2x; 4x I 06:24:58 Destination Media Sectors: 24.438.784 I 06:24:58 Write Mode: BD I 06:24:58 Write Type: DAO I 06:24:58 Write Speed: 4x I 06:24:58 Hardware Defect Management Active: No I 06:24:58 BD-R Verify Not Required: Yes I 06:24:58 Link Size: Auto I 06:24:58 Lock Volume: Yes I 06:24:58 Test Mode: No I 06:24:58 OPC: No I 06:24:58 BURN-Proof: Enabled I 06:24:58 Write Speed Successfully Set! - Effective: 17.984 KB/s (4x) I 06:25:24 Filling Buffer... (80 MiB) I 06:25:24 Writing LeadIn... I 06:25:25 Writing Session 1 of 1... (1 Track, LBA: 0 - 24436991) I 06:25:25 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 24436991) I 06:25:25 Writing Layer 0... (LBA: 0 - 12219391) I 06:54:33 Writing Layer 1... (LBA: 12219392 - 24436991) I 07:17:48 Synchronising Cache...
  13. Hi. First time this happened. I wasted already three BR 50 GB on this. No clue why this happens. I have 50.045.xxx.xxx bytes of data to be written. All goes fine until the very end where ImgBurn 2.5.8.0 is stuck w/ the message "Synchronizing Cache..." (in Log). No error messages, also not in Log. Any ideas why? Thanks
  14. That answers my question! Many thanks!
  15. I checked ... the drive writes DVDs and CDs without any problem. Only the BD-Rs create problems. Is this possible? Besides this ... does a burn speed reduction also affect the calibration, or only the burn process itself? Thanks,
  16. Is PHILIP-R04-000 the MID ID? Seems to be Philipps manufactored media sold by TDK? Right? One of the Google hits for Power Calibration Area Error was to update the firmware, which I did now (from PL14 to PL17). After that, I only had one of these lines i.s.o. 20: ... W 08:20:56 Failed to Write Sectors 0 - 31 - Reason: Power Calibration Area Error W 08:20:56 Retrying (1 of 20)... ... Another hint was to clean the lens. Is this really a possible reason for the error rather than a desperate attempt after nothing works? Does a burn speed reduction also affect the calibration or only the burn process itself? 4x burn worked! No calibration errors anymore. Thanks! Thanks,
  17. Hi. I tried to write slightly less than 25 GB to a BD-R (TDK, 4x, 135min, 25GB). I did this already many times before, but never ended up in such a "disaster". I trashed 3 media. The write process either started and stopped somewhere between 46% and 62% (never at the same place), or it didn't start at all. A file image (.iso) works fine! Before I keep on going wasting expensive media, I prefer to ask here what could possibly be wrong. Please help ... I 05:30:55 ImgBurn Version 2.5.8.0 started! I 05:30:55 Microsoft Windows 7 Ultimate x64 Edition (6.1, Build 7601 : Service Pack 1) I 05:30:55 Total Physical Memory: 16.664.440 KiB - Available: 11.428.644 KiB W 05:30:55 Drive X:\ (FAT32) does not support single files > 4 GiB in size. I 05:30:55 Initialising SPTI... I 05:30:55 Searching for SCSI / ATAPI devices... I 05:30:55 -> Drive 1 - Info: ATAPI iHBS312 2 PL14 (K:) (SATA) I 05:30:55 -> Drive 2 - Info: ELBY CLONEDRIVE 1.4 (L:) (SCSI) I 05:30:55 -> Drive 3 - Info: ELBY CLONEDRIVE 1.4 (M:) (SCSI) I 05:30:55 Found 2 BD-ROM/HD DVD-ROMs and 1 BD-RE! I 05:31:08 Project Successfully Loaded! I 05:31:08 File Name: E:\Application Data\ImgBurn\Project Files\Pictures_28.ibb I 05:31:46 Operation Started! I 05:31:46 Building Image Tree... I 05:31:46 Checking Directory Depth... I 05:31:46 Calculating Totals... I 05:31:46 Preparing Image... I 05:32:10 Checking Path Length... I 05:32:10 Contents: 5.584 Files, 27 Folders I 05:32:10 Content Type: Data I 05:32:10 Data Type: MODE1/2048 I 05:32:10 File System(s): ISO9660, UDF (1.02) I 05:32:10 Volume Label: Pictures_28 I 05:32:10 Size: 24.788.299.030 bytes I 05:32:10 Sectors: 12.106.452 I 05:32:10 Image Size: 24.806.948.864 bytes I 05:32:10 Image Sectors: 12.112.768 I 05:33:43 Operation Successfully Completed! - Duration: 00:01:56 I 05:33:43 Operation Started! I 05:33:43 Source File: -==/\/[BUILD IMAGE]\/\==- I 05:33:43 Source File Sectors: 12.112.768 (MODE1/2048) I 05:33:43 Source File Size: 24.806.948.864 bytes I 05:33:43 Source File Volume Identifier: Pictures_28 I 05:33:43 Source File Volume Set Identifier: 475A2BF700B8D379 I 05:33:43 Source File Application Identifier: IMGBURN V2.5.8.0 - THE ULTIMATE IMAGE BURNER! I 05:33:43 Source File Implementation Identifier: ImgBurn I 05:33:43 Source File File System(s): ISO9660; UDF (1.02) I 05:33:43 Destination Device: [5:0:0] ATAPI iHBS312 2 PL14 (K:) (SATA) I 05:33:43 Destination Media Type: BD-R (Disc ID: PHILIP-R04-000) I 05:33:43 Destination Media Supported Write Speeds: 4x; 6x; 8x; 10x I 05:33:43 Destination Media Sectors: 12.219.392 I 05:33:43 Write Mode: BD I 05:33:43 Write Type: DAO I 05:33:43 Write Speed: MAX I 05:33:43 Hardware Defect Management Active: No I 05:33:43 BD-R Verify Not Required: Yes I 05:33:43 Link Size: Auto I 05:33:43 Lock Volume: Yes I 05:33:43 Test Mode: No I 05:33:43 OPC: No I 05:33:43 BURN-Proof: Enabled I 05:33:44 Write Speed Successfully Set! - Effective: 44.950 KB/s (10x) I 05:33:44 Advanced Settings - Force HT: No, Online HT: No, OverSpeed: No, SmartBurn: Yes I 05:33:44 CD/DVD Life Record Count: 16 - CD/DVD Record Count: 3 I 05:33:44 BD Life Record Count: 37 - BD Record Count: 8 I 05:34:30 Filling Buffer... (80 MiB) I 05:34:32 Writing LeadIn... I 05:34:35 Writing Session 1 of 1... (1 Track, LBA: 0 - 12112767) I 05:34:35 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 12112767) W 05:42:35 Failed to Write Sectors 7103168 - 7103199 - Reason: Write Error W 05:42:35 Retrying (1 of 20)... W 05:42:40 Retry Failed - Reason: Invalid Address For Write W 05:42:40 Retrying (2 of 20)... W 05:42:40 Retry Failed - Reason: Invalid Address For Write W 05:42:40 Retrying (3 of 20)... W 05:42:40 Retry Failed - Reason: Invalid Address For Write W 05:42:40 Retrying (4 of 20)... W 05:42:40 Retry Failed - Reason: Invalid Address For Write W 05:42:40 Retrying (5 of 20)... W 05:42:40 Retry Failed - Reason: Invalid Address For Write W 05:42:40 Retrying (6 of 20)... W 05:42:40 Retry Failed - Reason: Invalid Address For Write W 05:42:40 Retrying (7 of 20)... W 05:42:40 Retry Failed - Reason: Invalid Address For Write W 05:42:40 Retrying (8 of 20)... W 05:42:40 Retry Failed - Reason: Invalid Address For Write W 05:42:40 Retrying (9 of 20)... W 05:42:40 Retry Failed - Reason: Invalid Address For Write W 05:42:40 Retrying (10 of 20)... W 05:42:41 Retry Failed - Reason: Invalid Address For Write W 05:42:41 Retrying (11 of 20)... W 05:42:41 Retry Failed - Reason: Invalid Address For Write W 05:42:41 Retrying (12 of 20)... W 05:42:41 Retry Failed - Reason: Invalid Address For Write W 05:42:41 Retrying (13 of 20)... W 05:42:41 Retry Failed - Reason: Invalid Address For Write W 05:42:41 Retrying (14 of 20)... W 05:42:41 Retry Failed - Reason: Invalid Address For Write W 05:42:41 Retrying (15 of 20)... W 05:42:41 Retry Failed - Reason: Invalid Address For Write W 05:42:41 Retrying (16 of 20)... W 05:42:41 Retry Failed - Reason: Invalid Address For Write W 05:42:41 Retrying (17 of 20)... W 05:42:41 Retry Failed - Reason: Invalid Address For Write W 05:42:41 Retrying (18 of 20)... W 05:42:41 Retry Failed - Reason: Invalid Address For Write W 05:42:41 Retrying (19 of 20)... W 05:42:41 Retry Failed - Reason: Invalid Address For Write W 05:42:41 Retrying (20 of 20)... W 05:42:41 Retry Failed - Reason: Invalid Address For Write E 05:43:40 Failed to Write Sectors 7103168 - 7103199 - Reason: Write Error E 05:43:40 Next Writable Address: 0 I 05:43:40 Synchronising Cache... W 05:44:03 User opted to skip the 'Close Track/Session/Disc' functions. E 05:44:03 Failed to Write Image! I 05:44:03 Exporting Graph Data... I 05:44:03 Graph Data File: E:\Application Data\ImgBurn\Graph Data Files\ATAPI_iHBS312_2_PL14_MONDAY-26-OCTOBER-2015_05-33_PHILIP-R04-000_MAX.ibg I 05:44:03 Export Successfully Completed! E 05:44:03 Operation Failed! - Duration: 00:10:20 I 05:44:03 Average Write Rate: 26.066 KiB/s (5.9x) - Maximum Write Rate: 43.203 KiB/s (9.8x) I 06:14:15 ImgBurn Version 2.5.8.0 started! I 06:14:15 Microsoft Windows 7 Ultimate x64 Edition (6.1, Build 7601 : Service Pack 1) I 06:14:15 Total Physical Memory: 16.664.440 KiB - Available: 11.110.428 KiB W 06:14:15 Drive X:\ (FAT32) does not support single files > 4 GiB in size. I 06:14:15 Initialising SPTI... I 06:14:15 Searching for SCSI / ATAPI devices... I 06:14:15 -> Drive 1 - Info: ATAPI iHBS312 2 PL14 (K:) (SATA) I 06:14:15 -> Drive 2 - Info: ELBY CLONEDRIVE 1.4 (L:) (SCSI) I 06:14:15 -> Drive 3 - Info: ELBY CLONEDRIVE 1.4 (M:) (SCSI) I 06:14:15 Found 2 BD-ROM/HD DVD-ROMs and 1 BD-RE! I 06:14:26 Project Successfully Loaded! I 06:14:26 File Name: E:\Application Data\ImgBurn\Project Files\Pictures_28.ibb I 06:15:21 Operation Started! I 06:15:21 Building Image Tree... I 06:15:21 Checking Directory Depth... I 06:15:21 Calculating Totals... I 06:15:21 Preparing Image... I 06:15:46 Checking Path Length... I 06:15:46 Contents: 5.584 Files, 27 Folders I 06:15:46 Content Type: Data I 06:15:46 Data Type: MODE1/2048 I 06:15:46 File System(s): ISO9660, UDF (1.02) I 06:15:46 Volume Label: Pictures_28 I 06:15:46 Size: 24.788.299.030 bytes I 06:15:46 Sectors: 12.106.452 I 06:15:46 Image Size: 24.806.948.864 bytes I 06:15:46 Image Sectors: 12.112.768 I 06:15:46 Operation Successfully Completed! - Duration: 00:00:24 I 06:16:13 Operation Started! I 06:16:13 Building Image Tree... I 06:16:14 Checking Directory Depth... I 06:16:14 Calculating Totals... I 06:16:14 Preparing Image... I 06:16:38 Checking Path Length... I 06:16:38 Contents: 5.584 Files, 27 Folders I 06:16:38 Content Type: Data I 06:16:38 Data Type: MODE1/2048 I 06:16:38 File System(s): ISO9660, UDF (1.02) I 06:16:38 Volume Label: Pictures_28 I 06:16:38 Size: 24.788.299.030 bytes I 06:16:38 Sectors: 12.106.452 I 06:16:38 Image Size: 24.806.948.864 bytes I 06:16:38 Image Sectors: 12.112.768 I 06:16:47 Operation Successfully Completed! - Duration: 00:00:34 I 06:16:47 Operation Started! I 06:16:47 Source File: -==/\/[BUILD IMAGE]\/\==- I 06:16:47 Source File Sectors: 12.112.768 (MODE1/2048) I 06:16:47 Source File Size: 24.806.948.864 bytes I 06:16:47 Source File Volume Identifier: Pictures_28 I 06:16:47 Source File Volume Set Identifier: 475A320600B8D379 I 06:16:47 Source File Application Identifier: IMGBURN V2.5.8.0 - THE ULTIMATE IMAGE BURNER! I 06:16:47 Source File Implementation Identifier: ImgBurn I 06:16:47 Source File File System(s): ISO9660; UDF (1.02) I 06:16:47 Destination Device: [5:0:0] ATAPI iHBS312 2 PL14 (K:) (SATA) I 06:16:47 Destination Media Type: BD-R (Disc ID: PHILIP-R04-000) I 06:16:47 Destination Media Supported Write Speeds: 4x; 6x; 8x; 10x I 06:16:47 Destination Media Sectors: 12.219.392 I 06:16:47 Write Mode: BD I 06:16:47 Write Type: DAO I 06:16:47 Write Speed: MAX I 06:16:47 Hardware Defect Management Active: No I 06:16:47 BD-R Verify Not Required: Yes I 06:16:47 Link Size: Auto I 06:16:47 Lock Volume: Yes I 06:16:47 Test Mode: No I 06:16:47 OPC: No I 06:16:47 BURN-Proof: Enabled I 06:16:49 Write Speed Successfully Set! - Effective: 44.950 KB/s (10x) I 06:16:49 Advanced Settings - Force HT: No, Online HT: No, OverSpeed: No, SmartBurn: Yes I 06:16:49 CD/DVD Life Record Count: 16 - CD/DVD Record Count: 3 I 06:16:49 BD Life Record Count: 38 - BD Record Count: 8 I 06:17:18 Filling Buffer... (80 MiB) I 06:17:20 Writing LeadIn... I 06:17:23 Writing Session 1 of 1... (1 Track, LBA: 0 - 12112767) I 06:17:23 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 12112767) W 06:25:30 Failed to Write Sectors 5678976 - 5679007 - Reason: Write Error W 06:25:30 Retrying (1 of 20)... W 06:25:33 Retry Failed - Reason: Invalid Address For Write W 06:25:33 Retrying (2 of 20)... W 06:25:33 Retry Failed - Reason: Invalid Address For Write W 06:25:33 Retrying (3 of 20)... W 06:25:33 Retry Failed - Reason: Invalid Address For Write W 06:25:33 Retrying (4 of 20)... W 06:25:33 Retry Failed - Reason: Invalid Address For Write W 06:25:33 Retrying (5 of 20)... W 06:25:33 Retry Failed - Reason: Invalid Address For Write W 06:25:33 Retrying (6 of 20)... W 06:25:33 Retry Failed - Reason: Invalid Address For Write W 06:25:33 Retrying (7 of 20)... W 06:25:34 Retry Failed - Reason: Invalid Address For Write W 06:25:34 Retrying (8 of 20)... W 06:25:34 Retry Failed - Reason: Invalid Address For Write W 06:25:34 Retrying (9 of 20)... W 06:25:34 Retry Failed - Reason: Invalid Address For Write W 06:25:34 Retrying (10 of 20)... W 06:25:34 Retry Failed - Reason: Invalid Address For Write W 06:25:34 Retrying (11 of 20)... W 06:25:34 Retry Failed - Reason: Invalid Address For Write W 06:25:34 Retrying (12 of 20)... W 06:25:34 Retry Failed - Reason: Invalid Address For Write W 06:25:34 Retrying (13 of 20)... W 06:25:34 Retry Failed - Reason: Invalid Address For Write W 06:25:34 Retrying (14 of 20)... W 06:25:34 Retry Failed - Reason: Invalid Address For Write W 06:25:34 Retrying (15 of 20)... W 06:25:34 Retry Failed - Reason: Invalid Address For Write W 06:25:34 Retrying (16 of 20)... W 06:25:34 Retry Failed - Reason: Invalid Address For Write W 06:25:34 Retrying (17 of 20)... W 06:25:34 Retry Failed - Reason: Invalid Address For Write W 06:25:34 Retrying (18 of 20)... W 06:25:34 Retry Failed - Reason: Invalid Address For Write W 06:25:34 Retrying (19 of 20)... W 06:25:34 Retry Failed - Reason: Invalid Address For Write W 06:25:34 Retrying (20 of 20)... W 06:25:34 Retry Failed - Reason: Invalid Address For Write W 06:26:05 Retrying (21)... W 06:26:05 Retry Failed - Reason: Invalid Address For Write E 06:26:06 Failed to Write Sectors 5678976 - 5679007 - Reason: Write Error E 06:26:06 Next Writable Address: 0 I 06:26:07 Synchronising Cache... W 06:26:09 User opted to skip the 'Close Track/Session/Disc' functions. E 06:26:09 Failed to Write Image! I 06:26:09 Exporting Graph Data... I 06:26:09 Graph Data File: E:\Application Data\ImgBurn\Graph Data Files\ATAPI_iHBS312_2_PL14_MONDAY-26-OCTOBER-2015_06-16_PHILIP-R04-000_MAX.ibg I 06:26:09 Export Successfully Completed! E 06:26:09 Operation Failed! - Duration: 00:09:21 I 06:26:09 Average Write Rate: 21.716 KiB/s (4.9x) - Maximum Write Rate: 39.980 KiB/s (9.1x) I 06:28:28 Project Successfully Loaded! I 06:28:28 File Name: E:\Application Data\ImgBurn\Project Files\Documentary_324.ibb I 06:28:48 Project Successfully Loaded! I 06:28:48 File Name: E:\Application Data\ImgBurn\Project Files\Pictures_28.ibb I 06:29:11 Operation Started! I 06:29:11 Building Image Tree... I 06:29:12 Checking Directory Depth... I 06:29:12 Calculating Totals... I 06:29:12 Preparing Image... I 06:29:36 Checking Path Length... I 06:29:36 Contents: 5.584 Files, 27 Folders I 06:29:36 Content Type: Data I 06:29:36 Data Type: MODE1/2048 I 06:29:36 File System(s): ISO9660, UDF (1.02) I 06:29:36 Volume Label: Pictures_28 I 06:29:36 Size: 24.788.299.030 bytes I 06:29:36 Sectors: 12.106.452 I 06:29:36 Image Size: 24.806.948.864 bytes I 06:29:36 Image Sectors: 12.112.768 I 06:29:41 Operation Successfully Completed! - Duration: 00:00:29 I 06:29:41 Operation Started! I 06:29:41 Source File: -==/\/[BUILD IMAGE]\/\==- I 06:29:41 Source File Sectors: 12.112.768 (MODE1/2048) I 06:29:41 Source File Size: 24.806.948.864 bytes I 06:29:41 Source File Volume Identifier: Pictures_28 I 06:29:41 Source File Volume Set Identifier: 475A33A500B8D379 I 06:29:41 Source File Application Identifier: IMGBURN V2.5.8.0 - THE ULTIMATE IMAGE BURNER! I 06:29:41 Source File Implementation Identifier: ImgBurn I 06:29:41 Source File File System(s): ISO9660; UDF (1.02) I 06:29:41 Destination Device: [5:0:0] ATAPI iHBS312 2 PL14 (K:) (SATA) I 06:29:41 Destination Media Type: BD-R (Disc ID: CMCMAG-BA3-000) I 06:29:41 Destination Media Supported Write Speeds: 4x; 6x; 8x; 10x I 06:29:41 Destination Media Sectors: 12.219.392 I 06:29:41 Write Mode: BD I 06:29:41 Write Type: DAO I 06:29:41 Write Speed: MAX I 06:29:41 Hardware Defect Management Active: No I 06:29:41 BD-R Verify Not Required: Yes I 06:29:41 Link Size: Auto I 06:29:41 Lock Volume: Yes I 06:29:41 Test Mode: No I 06:29:41 OPC: No I 06:29:41 BURN-Proof: Enabled I 06:29:46 Write Speed Successfully Set! - Effective: 44.950 KB/s (10x) I 06:29:46 Advanced Settings - Force HT: No, Online HT: No, OverSpeed: No, SmartBurn: Yes I 06:29:46 CD/DVD Life Record Count: 16 - CD/DVD Record Count: 3 I 06:29:46 BD Life Record Count: 39 - BD Record Count: 8 I 06:30:05 Filling Buffer... (80 MiB) I 06:30:06 Writing LeadIn... W 06:30:19 Failed to Write Sectors 0 - 31 - Reason: Power Calibration Area Error W 06:30:19 Retrying (1 of 20)... W 06:30:41 Retry Failed - Reason: Power Calibration Area Error W 06:30:41 Retrying (2 of 20)... W 06:30:52 Retry Failed - Reason: Power Calibration Area Error W 06:30:52 Retrying (3 of 20)... W 06:31:04 Retry Failed - Reason: Power Calibration Area Error W 06:31:04 Retrying (4 of 20)... W 06:31:13 Retry Failed - Reason: Device Internal Reset W 06:31:13 Retrying (5 of 20)... W 06:31:22 Retry Failed - Reason: Device Internal Reset W 06:31:22 Retrying (6 of 20)... W 06:31:30 Retry Failed - Reason: Device Internal Reset W 06:31:30 Retrying (7 of 20)... W 06:31:37 Retry Failed - Reason: Device Internal Reset W 06:31:37 Retrying (8 of 20)... W 06:31:45 Retry Failed - Reason: Device Internal Reset W 06:31:45 Retrying (9 of 20)... I 06:31:51 Abort Request Acknowledged W 06:31:52 Retry Failed - Reason: Device Internal Reset E 06:31:52 Failed to Write Sectors 0 - 31 - Reason: Power Calibration Area Error I 06:31:52 Synchronising Cache... W 06:32:05 User opted to skip the 'Close Track/Session/Disc' functions. E 06:32:05 Failed to Write Image! E 06:32:05 Operation Failed! - Duration: 00:02:23 I 06:32:05 Average Write Rate: N/A - Maximum Write Rate: N/A
  18. Ok. That answers all my ?s. Many thanks!
  19. But the .mds contains much more than just the LBA, right? If yes, isn't the != LBA data inside the .mds not relevant for 1:1 restituation of the DVD from the .iso?
  20. Anybody knows this ... ?! Thanks,
  21. Hi. Sorry for the late reply. Yes, it's a video DVD. "Ez-Mode Picker ..." > "Create image file from disc" was used to create the .iso file. Meanwhile I received the .mds file of subject .iso image. I used ... "Tools" > "ISO" > "Display IFO Layer Break Information" ... to load the at a first place the .iso file, then the .mds file. The data shown is the window is identical! Does this mean that I can safely disregard the .mds file of this video .iso image? In other works ... buring the DVD from the .iso, is this DVD 100.00% identical to the burn from the .mds file? If the answer to both questions above is "yes", why does ImgBurn generate an .mds file when creating an image? Thanks,
  22. Hi. I just received an .iso of a DVD+R double layer without .mds file. I'd like to burn this DVD+R. Is it possible to burn the .iso without .mds? Are there any drawbacks while writing without an .mds? If yes, which ones? Thanks,
  23. I would like to archive DVDs and was wondering if I really need the .mds file. Looks like YES. I found also this here. http://en.wikipedia.org/wiki/MDS_file Thanks for the answers. Regards,
  24. Is the layer break the only reason for a .mds? 4314 Bytes (in my sample read/write) is a bit much for a layer break definition. Thanks,
  25. Hi. Basic question ... When I create an image of a DVD, I get an .iso and a .mds file (as per configuration). Now ... when writing back this .iso to a DVD, I can either (1.) select the .iso file (then the .mds is not used) or (2.) the .mds file (where both .iso and .mds is used). What's the difference of the finally burned DVD between choosing the .iso file (1.) or the .mds file (2.)? In other words ... what does the .mds file change to the burn result? Thanks,
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.