Jump to content

Recommended Posts

Posted

Hello, 

 

I am having error on all my BD-R DL burned for a while.

The burning process is OK but on veryfing i have always an error on the transition layer i think.

I tried do reduce de % of ocupation to 95% but the error is always there.

 

BD-R DL: 50GB Primeon Media ID: RITEK-DR3-00

Drive: ASUS BW-16D1HT

OS: Win 10 x264 professional

I used this discs thousands of times and never had a problem until now.

The strange thing is that the cake (25x discs) on the first half everything was going well and the second half always this error on veriyfing !

Can you help me?

 

log file:

 

I 05:57:55 ImgBurn Version 2.5.8.0 started!
I 05:57:55 Microsoft Windows 8 Professional x64 Edition (6.2, Build 9200)
I 05:57:55 Total Physical Memory: 16 714 988 KiB  -  Available: 10 053 408 KiB
I 05:57:55 Initialising SPTI...
I 05:57:55 Searching for SCSI / ATAPI devices...
I 05:57:56 -> Drive 1 - Info: ASUS BW-16D1HT 1.01 (F:) (SATA)
I 05:57:56 Found 1 BD-RE XL!
I 05:58:09 Operation Started!
I 05:58:09 Building Image Tree...
I 05:58:09 Calculating Totals...
I 05:58:09 Preparing Image...
I 05:58:09 Contents: 56 Files, 0 Folders
I 05:58:09 Content Type: Data
I 05:58:09 Data Type: MODE1/2048
I 05:58:09 File System(s): UDF (1.02)
I 05:58:09 Volume Label: [Not Configured]
I 05:58:09 Size: 47 170 162 465 bytes
I 05:58:09 Sectors: 23 032 332
I 05:58:09 Image Size: 47 170 912 256 bytes
I 05:58:09 Image Sectors: 23 032 672
I 05:58:09 Operation Successfully Completed! - Duration: 00:00:00
I 06:01:45 Operation Started!
I 06:01:45 Building Image Tree...
I 06:02:00 Calculating Totals...
I 06:02:00 Preparing Image...
I 06:02:00 Contents: 56 Files, 0 Folders
I 06:02:00 Content Type: Data
I 06:02:00 Data Type: MODE1/2048
I 06:02:00 File System(s): UDF (1.02)
I 06:02:00 Volume Label: Malhacao 7 BD4
I 06:02:00 Size: 47 170 162 465 bytes
I 06:02:00 Sectors: 23 032 332
I 06:02:00 Image Size: 47 170 912 256 bytes
I 06:02:00 Image Sectors: 23 032 672
I 06:02:01 Operation Successfully Completed! - Duration: 00:00:15
I 06:02:03 Operation Started!
I 06:02:03 Source File: -==/\/[BUILD IMAGE]\/\==-
I 06:02:04 Source File Sectors: 23 032 672 (MODE1/2048)
I 06:02:04 Source File Size: 47 170 912 256 bytes
I 06:02:04 Source File Volume Identifier: Malhacao 7 BD4
I 06:02:04 Source File Volume Set Identifier: 4F4F3036015F734A
I 06:02:04 Source File Application Identifier: ImgBurn v2.5.8.0
I 06:02:04 Source File Implementation Identifier: ImgBurn
I 06:02:04 Source File File System(s): UDF (1.02)
I 06:02:04 Destination Device: [0:0:0] ASUS BW-16D1HT 1.01 (F:) (SATA)
I 06:02:04 Destination Media Type: BD-R (Disc ID: RITEK-DR3-000)
I 06:02:04 Destination Media Supported Write Speeds: 2x; 4x; 6x
I 06:02:04 Destination Media Sectors: 24 438 784
I 06:02:04 Write Mode: BD
I 06:02:04 Write Type: DAO
I 06:02:04 Write Speed: 2x
I 06:02:04 Hardware Defect Management Active: No
I 06:02:04 BD-R Verify Not Required: Yes
I 06:02:04 Link Size: Auto
I 06:02:04 Lock Volume: Yes
I 06:02:04 Test Mode: No
I 06:02:04 OPC: No
I 06:02:04 BURN-Proof: Enabled
I 06:02:04 Write Speed Successfully Set! - Effective: 8 992 KB/s (2x)
I 06:02:20 Filling Buffer... (80 MiB)
I 06:02:22 Writing LeadIn...
I 06:02:22 Writing Session 1 of 1... (1 Track, LBA: 0 - 23032671)
I 06:02:22 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 23032671)
I 06:02:22 Writing Layer 0... (LBA: 0 - 12219391)
I 06:48:36 Writing Layer 1... (LBA: 12219392 - 23032671)
I 07:29:32 Synchronising Cache...
I 07:29:33 Closing Track...
I 07:29:34 Finalising Disc...
I 07:29:51 Exporting Graph Data...
I 07:29:51 Graph Data File: C:\Users\David GC\AppData\Roaming\ImgBurn\Graph Data Files\ASUS_BW-16D1HT_1.01_MARDI-15-OCTOBRE-2019_06-02_RITEK-DR3-000_2x.ibg
I 07:29:51 Export Successfully Completed!
I 07:29:51 Operation Successfully Completed! - Duration: 01:27:47
I 07:29:51 Average Write Rate: 8 809 KiB/s (2.0x) - Maximum Write Rate: 8 868 KiB/s (2.0x)
I 07:29:51 Cycling Tray before Verify...
W 07:29:58 Waiting for device to become ready...
I 07:30:16 Device Ready!
I 07:30:19 Operation Started!
I 07:30:19 Source Device: [0:0:0] ASUS BW-16D1HT 1.01 (F:) (SATA)
I 07:30:19 Source Media Type: BD-R (Disc ID: RITEK-DR3-000)
I 07:30:19 Source Media Supported Read Speeds: 2x; 4,2x; 6,2x; 8x
I 07:30:19 Source Media Supported Write Speeds: 2x; 4x; 6x
I 07:30:19 Source Media Sectors: 23 032 672
I 07:30:19 Source Media Size: 47 170 912 256 bytes
I 07:30:19 Image File: -==/\/[BUILD IMAGE]\/\==-
I 07:30:19 Image File Sectors: 23 032 672 (MODE1/2048)
I 07:30:19 Image File Size: 47 170 912 256 bytes
I 07:30:19 Image File Volume Identifier: Malhacao 7 BD4
I 07:30:19 Image File Volume Set Identifier: 4F4F3036015F734A
I 07:30:19 Image File Application Identifier: ImgBurn v2.5.8.0
I 07:30:20 Image File Implementation Identifier: ImgBurn
I 07:30:20 Image File File System(s): UDF (1.02)
I 07:30:20 Read Speed (Data/Audio): MAX / MAX
I 07:30:21 Read Speed - Effective: 3,3x - 8x; 8x - 3,3x
I 07:30:21 Verifying Session 1 of 1... (1 Track, LBA: 0 - 23032671)
I 07:30:21 Verifying Track 1 of 1... (MODE1/2048, LBA: 0 - 23032671)
I 07:30:21 Verifying Layer 0... (LBA: 0 - 12219391)
I 07:46:21 Verifying Layer 1... (LBA: 12219392 - 23032671)
W 07:46:32 Failed to Read Sectors 12219424 - 12219455 - Reason: L-EC Uncorrectable Error
W 07:46:41 Failed to Read Sector 12219424 - Reason: Timeout on Logical Unit
W 07:46:41 Sector 12219424 maps to File: \205.mkv
W 09:01:24 Failed to Read Sector 12219425 - Reason: Timeout on Logical Unit
W 09:01:24 Sector 12219425 maps to File: \205.mkv
E 09:01:32 Failed to Read Sector 12219425 - Reason: Timeout on Logical Unit
E 09:01:32 Sector 12219425 maps to File: \205.mkv
E 09:01:33 Failed to Verify Sectors!
I 09:01:34 Exporting Graph Data...
I 09:01:34 Graph Data File: C:\Users\David GC\AppData\Roaming\ImgBurn\Graph Data Files\ASUS_BW-16D1HT_1.01_MARDI-15-OCTOBRE-2019_06-02_RITEK-DR3-000_2x.ibg
I 09:01:34 Export Successfully Completed!
E 09:01:34 Operation Failed! - Duration: 01:31:13
I 09:01:34 Average Verify Rate: 4 466 KiB/s (1.0x) - Maximum Verify Rate: 36 094 KiB/s (8.2x)

 

 

 

 

Posted

Stop using ritek cheap crap, that's about the worst quality you can get. Get verbatim datalife plus online.

Sent from my Pixel 3 XL using Tapatalk

Posted
9 minutes ago, Ch3vr0n said:

Stop using ritek cheap crap, that's about the worst quality you can get. Get verbatim datalife plus online.

Sent from my Pixel 3 XL using Tapatalk
 

Thank you.

Do you have an idea why the error happens just now and not before?

Posted

Either that or your drive only just now started to act up.  Given how you've not had problems with the media before, even though it's cheap, it would seem either the manufacture of the discs was changed or your drive needs replacing and it only just now is showing up that it needs such.  However, it seems highly unlikely they'd change the manufacturing process of discs right in the middle of a cake stack of discs that did work.

 

If you still get failures on Verbatim discs, then you do know it's your drive that needs replacing.  So, your best bet is probably, at this point, to invest is some good quality Verbatim BD-R DL's and see if the problem persists.  If it does, the drive probably needs replacing.

  • 2 weeks later...
Posted

Hello, 

 

I just tried BD-r DL verbatim datalifePlus 50gb with VERBAT- IMF-000 and everything was OK.

 

The problem was the Ritek media type.


Thank you.

Posted

It generally is.  Multiple layer media from anyone other than Verbatim is asking for trouble.  However, with Verbatim's sale to CMC, the worst maker of optical media out there, I expect the axe to fall anytime now.  It's already started with their MCC DVD+R DataLife Plus and the LG WH16NS60.  Either Verbatim or CMC changed the manufacturing process so these discs are useless on that drive.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

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