Jump to content
chaka

Failed to Read Sectors, Cannot Read Medium - Incompatible Format

Recommended Posts

I have had a couple of discs that failed verification listing an Error (Failed to Read Sectors, Cannot Read Medium - Incompatible Format). But I also had a couple of discs that listed this same statement, but as a Warning, not an Error. The program then completed verification and stated "Operation Successfully Completed". The program displayed 0 read errors and 0 miscompares. My question is, if Imgburn states that it failed to read sectors but then states that verification was successful, is the disc good or not? And why is failing to read sectors sometimes listed as a warning and other times as an error that ends up in a failed verification?

 

; //****************************************\\
;   ImgBurn Version 2.5.7.0 - Log
;   Tuesday, 09 February 2021, 15:45:27
; \\****************************************//
;
;
I 13:30:25 ImgBurn Version 2.5.7.0 started!
I 13:30:25 Microsoft Windows Vista Home Premium x64 Edition (6.0, Build 6002 : Service Pack 2)
I 13:30:25 Total Physical Memory: 4,192,432 KB  -  Available: 2,363,132 KB
I 13:30:25 Initialising SPTI...
I 13:30:25 Searching for SCSI / ATAPI devices...
I 13:30:26 -> Drive 1 - Info: HL-DT-ST BD-RE  BH10LS30 1.02-A0 (E:) (ATA)
I 13:30:26 -> Drive 2 - Info: DVDFab Virtual Drive 1.1 (D:) (SCSI)
I 13:30:26 Found 1 BD-ROM/HD DVD-ROM and 1 BD-RE!
I 13:32:59 Operation Started!
I 13:32:59 Source File: V:\ISO 2\WINGS_OF_THE_HAWK.iso
I 13:32:59 Source File Sectors: 16,496,224 (MODE1/2048)
I 13:32:59 Source File Size: 33,784,266,752 bytes
I 13:32:59 Source File Volume Identifier: WINGS_OF_THE_HAWK
I 13:32:59 Source File Volume Set Identifier: 02E50775        WINGS_OF_THE_HAWK
I 13:32:59 Source File Application Identifier: ScenaristScenaristBD
I 13:32:59 Source File Implementation Identifier: ScenaristScenaristBD
I 13:32:59 Source File File System(s): UDF (2.50)
I 13:32:59 Destination Device: [3:0:0] HL-DT-ST BD-RE  BH10LS30 1.02 (E:) (ATA)
I 13:32:59 Destination Media Type: BD-R (Disc ID: MEI-T02-001)
I 13:32:59 Destination Media Supported Write Speeds: 2x, 4x, 6x, 8x
I 13:32:59 Destination Media Sectors: 24,438,784
I 13:32:59 Write Mode: BD
I 13:32:59 Write Type: DAO
I 13:32:59 Write Speed: 2x
I 13:32:59 Hardware Defect Management Active: No
I 13:32:59 BD-R Verify Not Required: Yes
I 13:32:59 Link Size: Auto
I 13:32:59 Lock Volume: Yes
I 13:32:59 Test Mode: No
I 13:32:59 OPC: No
I 13:32:59 BURN-Proof: Enabled
I 13:32:59 Write Speed Successfully Set! - Effective: 8,991 KB/s (2x)
I 13:33:31 Filling Buffer... (40 MB)
I 13:33:36 Writing LeadIn...
I 13:33:37 Writing Session 1 of 1... (1 Track, LBA: 0 - 16496223)
I 13:33:37 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 16496223)
I 13:33:37 Writing Layer 0... (LBA: 0 - 12219391)
I 14:20:15 Writing Layer 1... (LBA: 12219392 - 16496223)
I 14:36:53 Synchronising Cache...
I 14:36:57 Closing Track...
I 14:36:58 Finalising Disc...
I 14:37:14 Exporting Graph Data...
I 14:37:14 Graph Data File: C:\Users\Administrator\AppData\Roaming\ImgBurn\Graph Data Files\HL-DT-ST_BD-RE_BH10LS30_1.02_TUESDAY-FEBRUARY-09-2021_1-32_PM_MEI-T02-001_2x.ibg
I 14:37:14 Export Successfully Completed!
I 14:37:14 Operation Successfully Completed! - Duration: 01:04:14
I 14:37:14 Average Write Rate: 8,693 KB/s (1.9x) - Maximum Write Rate: 9,061 KB/s (2.0x)
I 14:37:14 Cycling Tray before Verify...
W 14:37:23 Waiting for device to become ready...
I 14:37:44 Device Ready!
I 14:37:45 Operation Started!
I 14:37:45 Source Device: [3:0:0] HL-DT-ST BD-RE  BH10LS30 1.02 (E:) (ATA)
I 14:37:45 Source Media Type: BD-R (Disc ID: MEI-T02-001)
I 14:37:45 Source Media Supported Write Speeds: 2x, 4x, 6x, 8x
I 14:37:45 Image File: V:\ISO 2\WINGS_OF_THE_HAWK.iso
I 14:37:45 Image File Sectors: 16,496,224 (MODE1/2048)
I 14:37:45 Image File Size: 33,784,266,752 bytes
I 14:37:45 Image File Volume Identifier: WINGS_OF_THE_HAWK
I 14:37:45 Image File Volume Set Identifier: 02E50775        WINGS_OF_THE_HAWK
I 14:37:45 Image File Application Identifier: ScenaristScenaristBD
I 14:37:45 Image File Implementation Identifier: ScenaristScenaristBD
I 14:37:45 Image File File System(s): UDF (2.50)
I 14:37:45 Read Speed (Data/Audio): MAX / MAX
I 14:37:46 Verifying Session 1 of 1... (1 Track, LBA: 0 - 16496223)
I 14:37:46 Verifying Track 1 of 1... (MODE1/2048, LBA: 0 - 16496223)
I 14:37:46 Verifying Layer 0... (LBA: 0 - 12219391)
I 15:24:00 Verifying Layer 1... (LBA: 12219392 - 16496223)
W 15:25:39 Failed to Read Sectors 12654656 - 12654687 - Reason: Cannot Read Medium - Incompatible Format
W 15:25:56 Failed to Read Sectors 12702848 - 12702879 - Reason: Cannot Read Medium - Incompatible Format
W 15:26:10 Failed to Read Sectors 12739616 - 12739647 - Reason: Cannot Read Medium - Incompatible Format
I 15:40:28 Exporting Graph Data...
I 15:40:28 Graph Data File: C:\Users\Administrator\AppData\Roaming\ImgBurn\Graph Data Files\HL-DT-ST_BD-RE_BH10LS30_1.02_TUESDAY-FEBRUARY-09-2021_1-32_PM_MEI-T02-001_2x.ibg
I 15:40:28 Export Successfully Completed!
I 15:40:28 Operation Successfully Completed! - Duration: 01:02:41
I 15:40:28 Average Verify Rate: 8,774 KB/s (2.0x) - Maximum Verify Rate: 9,639 KB/s (2.1x)
I 15:45:27 Close Request Acknowledged
I 15:45:27 Closing Down...
I 15:45:27 Shutting down SPTI...
I 15:45:27 ImgBurn closed!
;

Share this post


Link to post
Share on other sites

According to what I looked up, MEI-T02-001 are BD-R made by Panasonic/Matsushita.  Recordable DVD discs made by Panasonic/Matsushita were some of the best quality you could get.  So, it would probably be the case that you're using quality BD-R.

 

Sometimes read issues happen, but ImgBurn "recovers" from them.  These are usually cased by a drive being picky with that particular manufacturer's process for discs.

 

The one time I had this happen with BD-R, ImgBurn tried the read again during the Verify and it was successful on the 2nd attempt.  I then did a variety of read tests on the data and it seemed to just be a hiccup.

 

If you're really concerned, see what happens when you create an image from these same BD-R that return the "read errors."  See if you get more read errors.  If it completes read, it's probably fine.  If it doesn't, then, of course, it most likely isn't.  And, if you're really concerned, since it appears it might be a Blu-Ray movie you made, try playing all of its contents.  If they play without read errors, skips, pauses, pops in audio, pixelation in video, then the disc is most likely okay.

Share this post


Link to post
Share on other sites

The program reads the sectors in chunks. When the drive returns an error, it drops down to reading them 1 at a time so it can pick out the bad one.
What’s happened here is that the drive errored out when reading the chunk, but then succeeded to read them all when doing it 1 by 1.

I would the disc has the potential to be unreliable. Maybe do a stand-alone verify on it and see if the drive fails to read it again in those same locations.

Share this post


Link to post
Share on other sites

×

Important Information

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