BD-RE verify phase error message

[discuser]

I was recently writing a BD-RE-TL and I had enabled my BD writer to verify during write. The write phase did not produce any error messages in Imgburn's log and appeared to proceed normally. However, after write completion and the verify phase began, comparing the source files on the hard disc to the optical disc, I had multiple messages which read:

Failed to Read Sectors XXXXXXX - XXXXXXX - Reason: Unknown (Internal Target Failure) (ASC: 0x44, ASCQ: 0x07)

I wanted to confirm that this is indicating a read issue on the ODD side and not the HDD side. Is that correct? Seems odd that the write with verify phase did not pick up any read errors (or would have reallocated bad sectors with spare sectors), yet during verify only phase, the disc had read problems. I had already re-erased the disc (which had previously been written on once) with spare sectors enabled prior to completely re-writing the contents of the disc. Thanks for any clarification.

 

Edited January 2, 2019 by discuser

[LIGHTNING UK!]

Can you post the log please?

That error is from your optical drive, not a storage device (hdd/ssd or whatever).

 

[discuser]

Thanks for confirming that. I had suspected it was on the ODD end and not the HDD end. That group of messages is the only objectionable / exceptional messages in an otherwise normal log entry.  All messages are the same other than the sector numbers on which the verify failure occured and usually it occurs every few minutes to every 10 minutes. What this tells me is that if this is a disc defect, it is not an issue of any physical contamination on the disc surface on one or multiple particular physical spot, because that should not occur every few minutes on the same layer of the disc. The timing of the multiple read errors suggest the failures are spread across all three layers at multiple spots, and I can confirm that the disc surface is ultra clean as I closely inspect the BD surface and clear all visible dust / contaminants gently with camera lens cleaning paper prior to insertion into the drive for writing.

What I will try is completely re-erase / re-format this disc with spare sectors enabled on my 2nd but identical model Pioneer BD writer on the same computer system, then repeat the exact same write, and see how it verifies. If the result is the same, then I will try a new Sony BD-RE-TL. However, before I re-erase the BD, I may try to simply run a read operation on all the files and see if the same read errors occur, or whether it reads completely smoothly without re-trying at any spot on the disc.

Here is the relevant section of the log below. The media is Sony BD-RE-TL type (made in Japan), which I have used very successfully to date without a hitch or error until now. Though, this was the first write on the same media since a most recent Pioneer firmware update that was released.

I 04:41:27 Operation Started!
I 04:41:27 Source File: -==/\/[BUILD IMAGE]\/\==-
I 04:41:27 Source File Sectors: 38,359,328 (MODE1/2048)
I 04:41:27 Source File Size: 78,559,903,744 bytes
I 04:41:27 Source File Volume Identifier: VIDEOARC-3M
I 04:41:27 Source File Volume Set Identifier: 4E22252802494843
I 04:41:27 Source File Application Identifier: ImgBurn v2.5.8.0
I 04:41:27 Source File Implementation Identifier: ImgBurn
I 04:41:27 Source File File System(s): UDF (2.50)
I 04:41:27 Destination Device: [2:0:0] PIONEER BD-RW   BDR-S09 1.51 (T:) (ATA)
I 04:41:27 Destination Media Type: BD-RE (Disc ID: SONY-ET2-002)
I 04:41:27 Destination Media Supported Write Speeds: 2x
I 04:41:27 Destination Media Sectors: 47,305,728
I 04:41:27 Write Mode: BD
I 04:41:27 Write Type: DAO
I 04:41:27 Write Speed: 2x
I 04:41:27 Hardware Defect Management Active: Yes
I 04:41:27 BD-RE FastWrite: No
I 04:41:27 Link Size: Auto
I 04:41:27 Lock Volume: Yes
I 04:41:27 Test Mode: No
I 04:41:27 OPC: No
I 04:41:27 BURN-Proof: Disabled
I 04:41:28 Write Speed Successfully Set! - Effective: 8,990 KB/s (2x)
I 04:41:28 Advanced Settings - Optimal Writing Speed: No
I 04:41:28 Filling Buffer... (80 MiB)
I 04:41:31 Writing LeadIn...
I 04:41:41 Writing Session 1 of 1... (1 Track, LBA: 0 - 38359327)
I 04:41:41 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 38359327)
I 10:08:09 Synchronising Cache...
I 10:08:11 Operation Successfully Completed! - Duration: 05:26:44
I 10:08:11 Average Write Rate: 3,916 KiB/s (0.9x) - Maximum Write Rate: 4,358 KiB/s (1.0x)
I 10:08:12 Operation Started!
I 10:08:12 Source Device: [2:0:0] PIONEER BD-RW   BDR-S09 1.51 (T:) (ATA)
I 10:08:12 Source Media Type: BD-RE (Disc ID: SONY-ET2-002)
I 10:08:12 Source Media Supported Read Speeds: 4x
I 10:08:12 Source Media Supported Write Speeds: 2x
I 10:08:12 Source Media Sectors: 47,305,728
I 10:08:12 Source Media Size: 96,882,130,944 bytes
I 10:08:12 Image File: -==/\/[BUILD IMAGE]\/\==-
I 10:08:12 Image File Sectors: 38,359,328 (MODE1/2048)
I 10:08:13 Image File Size: 78,559,903,744 bytes
I 10:08:13 Image File Volume Identifier: *** 11 character label REDACTED for forum post ***
I 10:08:13 Image File Volume Set Identifier: 4E22252802494843
I 10:08:13 Image File Application Identifier: ImgBurn v2.5.8.0
I 10:08:13 Image File Implementation Identifier: ImgBurn
I 10:08:13 Image File File System(s): UDF (2.50)
I 10:08:13 Read Speed (Data/Audio): MAX / MAX
I 10:08:14 Read Speed - Effective: 4x
I 10:08:14 Verifying Session 1 of 1... (1 Track, LBA: 0 - 38359327)
I 10:08:14 Verifying Track 1 of 1... (MODE1/2048, LBA: 0 - 38359327)
W 10:13:16 Failed to Read Sectors 1317888 - 1317919 - Reason: Unknown (Internal Target Failure) (ASC: 0x44, ASCQ: 0x07)
W 10:15:26 Failed to Read Sectors 1889344 - 1889375 - Reason: Unknown (Internal Target Failure) (ASC: 0x44, ASCQ: 0x07)
W 10:19:05 Failed to Read Sectors 2846720 - 2846751 - Reason: Unknown (Internal Target Failure) (ASC: 0x44, ASCQ: 0x07)
W 10:23:19 Failed to Read Sectors 3960096 - 3960127 - Reason: Unknown (Internal Target Failure) (ASC: 0x44, ASCQ: 0x07)
W 10:23:42 Failed to Read Sectors 4061440 - 4061471 - Reason: Unknown (Internal Target Failure) (ASC: 0x44, ASCQ: 0x07)
W 10:27:47 Failed to Read Sectors 5132544 - 5132575 - Reason: Unknown (Internal Target Failure) (ASC: 0x44, ASCQ: 0x07)
W 10:34:08 Failed to Read Sectors 6803584 - 6803615 - Reason: Unknown (Internal Target Failure) (ASC: 0x44, ASCQ: 0x07)
W 10:40:19 Failed to Read Sectors 8431520 - 8431551 - Reason: Unknown (Internal Target Failure) (ASC: 0x44, ASCQ: 0x07)
W 10:41:50 Failed to Read Sectors 8826592 - 8826623 - Reason: Unknown (Internal Target Failure) (ASC: 0x44, ASCQ: 0x07)
W 10:44:10 Failed to Read Sectors 9437376 - 9437407 - Reason: Unknown (Internal Target Failure) (ASC: 0x44, ASCQ: 0x07)
W 10:55:21 Failed to Read Sectors 12382656 - 12382687 - Reason: Unknown (Internal Target Failure) (ASC: 0x44, ASCQ: 0x07)
W 10:55:31 Failed to Read Sectors 12424192 - 12424223 - Reason: Unknown (Internal Target Failure) (ASC: 0x44, ASCQ: 0x07)
W 10:56:07 Failed to Read Sectors 12577728 - 12577759 - Reason: Unknown (Internal Target Failure) (ASC: 0x44, ASCQ: 0x07)
W 10:57:39 Failed to Read Sectors 12976928 - 12976959 - Reason: Unknown (Internal Target Failure) (ASC: 0x44, ASCQ: 0x07)
W 11:10:53 Failed to Read Sectors 16459232 - 16459263 - Reason: Unknown (Internal Target Failure) (ASC: 0x44, ASCQ: 0x07)
W 11:15:06 Failed to Read Sectors 17566304 - 17566335 - Reason: Unknown (Internal Target Failure) (ASC: 0x44, ASCQ: 0x07)
W 11:15:34 Failed to Read Sectors 17683520 - 17683551 - Reason: Unknown (Internal Target Failure) (ASC: 0x44, ASCQ: 0x07)
W 11:19:39 Failed to Read Sectors 18756384 - 18756415 - Reason: Unknown (Internal Target Failure) (ASC: 0x44, ASCQ: 0x07)
W 11:21:22 Failed to Read Sectors 19205856 - 19205887 - Reason: Unknown (Internal Target Failure) (ASC: 0x44, ASCQ: 0x07)
W 11:22:04 Failed to Read Sectors 19384832 - 19384863 - Reason: Unknown (Internal Target Failure) (ASC: 0x44, ASCQ: 0x07)
W 11:25:32 Failed to Read Sectors 20296096 - 20296127 - Reason: Unknown (Internal Target Failure) (ASC: 0x44, ASCQ: 0x07)
W 11:29:25 Failed to Read Sectors 21314752 - 21314783 - Reason: Unknown (Internal Target Failure) (ASC: 0x44, ASCQ: 0x07)
W 11:37:22 Failed to Read Sectors 23405600 - 23405631 - Reason: Unknown (Internal Target Failure) (ASC: 0x44, ASCQ: 0x07)
W 11:40:35 Failed to Read Sectors 24247872 - 24247903 - Reason: Unknown (Internal Target Failure) (ASC: 0x44, ASCQ: 0x07)
W 11:41:15 Failed to Read Sectors 24423104 - 24423135 - Reason: Unknown (Internal Target Failure) (ASC: 0x44, ASCQ: 0x07)
W 11:43:09 Failed to Read Sectors 24918688 - 24918719 - Reason: Unknown (Internal Target Failure) (ASC: 0x44, ASCQ: 0x07)
W 11:44:35 Failed to Read Sectors 25293504 - 25293535 - Reason: Unknown (Internal Target Failure) (ASC: 0x44, ASCQ: 0x07)
W 11:45:54 Failed to Read Sectors 25635424 - 25635455 - Reason: Unknown (Internal Target Failure) (ASC: 0x44, ASCQ: 0x07)
W 11:48:01 Failed to Read Sectors 26191616 - 26191647 - Reason: Unknown (Internal Target Failure) (ASC: 0x44, ASCQ: 0x07)
W 11:49:57 Failed to Read Sectors 26696192 - 26696223 - Reason: Unknown (Internal Target Failure) (ASC: 0x44, ASCQ: 0x07)
W 11:52:35 Failed to Read Sectors 27388832 - 27388863 - Reason: Unknown (Internal Target Failure) (ASC: 0x44, ASCQ: 0x07)
W 12:01:30 Failed to Read Sectors 29733984 - 29734015 - Reason: Unknown (Internal Target Failure) (ASC: 0x44, ASCQ: 0x07)
W 12:08:03 Failed to Read Sectors 31458272 - 31458303 - Reason: Unknown (Internal Target Failure) (ASC: 0x44, ASCQ: 0x07)
W 12:08:53 Failed to Read Sectors 31676832 - 31676863 - Reason: Unknown (Internal Target Failure) (ASC: 0x44, ASCQ: 0x07)
W 12:11:07 Failed to Read Sectors 32260800 - 32260831 - Reason: Unknown (Internal Target Failure) (ASC: 0x44, ASCQ: 0x07)
W 12:22:48 Failed to Read Sectors 35337568 - 35337599 - Reason: Unknown (Internal Target Failure) (ASC: 0x44, ASCQ: 0x07)
W 12:24:36 Failed to Read Sectors 35808448 - 35808479 - Reason: Unknown (Internal Target Failure) (ASC: 0x44, ASCQ: 0x07)
W 12:29:32 Failed to Read Sectors 37103520 - 37103551 - Reason: Unknown (Internal Target Failure) (ASC: 0x44, ASCQ: 0x07)
W 12:33:01 Failed to Read Sectors 38016704 - 38016735 - Reason: Unknown (Internal Target Failure) (ASC: 0x44, ASCQ: 0x07)
W 12:33:16 Failed to Read Sectors 38078240 - 38078271 - Reason: Unknown (Internal Target Failure) (ASC: 0x44, ASCQ: 0x07)
W 12:34:11 Failed to Read Sectors 38320192 - 38320223 - Reason: Unknown (Internal Target Failure) (ASC: 0x44, ASCQ: 0x07)
W 12:34:16 Failed to Read Sectors 38334336 - 38334367 - Reason: Unknown (Internal Target Failure) (ASC: 0x44, ASCQ: 0x07)
I 12:34:29 Operation Successfully Completed! - Duration: 02:26:09
I 12:34:29 Average Verify Rate: 8,749 KiB/s (2.0x) - Maximum Verify Rate: 8,970 KiB/s (2.0x)
 

[LIGHTNING UK!]

Unfortunately, I have no way of finding out what ASC 0x44, ASCQ 0x07 actually means.

As it's showing a range of sectors and then nothing after it for an individual sector, it means reading the block failed (for that 0x44, 0x07 reason) but when it then retried each sector in that block individually, they were all readable.

So in theory, nothing to much to worry about.

I wonder if subsequent reads would produce errors in the exact same places? Worth a try maybe?

 

 

[discuser]

On 1/2/2019 at 1:45 PM, LIGHTNING UK! said:

I wonder if subsequent reads would produce errors in the exact same places? Worth a try maybe?

After more than a week, I finally got things sorted. But this was an extremely odd and inexplicable case / scenario where it appeared that this was caused by a system issue, seemingly to be software related, on the operating system level with Windows. The reason was unknown. I do not believe that it has to do with viruses or malware. But in summary, something was going on at the operating system level that affected data I/O on both the HDD and ODDs and these symptoms gradually worsened quickly to an alarming level over the course of a couple of days. After going into Windows recovery console via OS CD boot and running full HDD scan and repair / recovery using CHKDSK, the symptoms were improved a bit but not were entirely cleared. Fortunately, I have a full drive C image back up from less than 2 months ago and did a full restore from that and also ran CHKDSK on it. After that, everything with disk I/O on HDD and ODD returned to normal. I used the exact same BD-RE-TL disc and re-erased it fully and rewrote the entire disc with Imgburn and both write and verify phase of the process produced no Imgburn error / warning messages whatsoever. So it strongly implies that this wasn't media fault.

However, I did do an indirect disc quality test on the Sony BD-RE-TL disc initially prior to rewriting it, and Opti-Drive Control reported some interesting information. Since the Pioneer drives doesn't report direct error rates using the disc quality test function on Opti-Drive Control, I opted to use the TRANSFER RATE test which would usually reveal read difficulties on a disc as indicated by drive speed slow downs. The disc was read at 4X speed in CLV mode. A problem with Opti-Drive Control that was discovered during this transfer rate test was that this utility doesn't yet support BD capacities beyond dual layer / 50 GB, so when the read test got to that limit, the graphing routine would produce invalid plottings and I suspect that the X-axis scaling is also wrong. But I think one could surmise where the (first) layer switch occurs since that could be inferred from the valley-point of the spindle speed (green plot). As you can see, the green plot data becomes invalid as it rises steeply above the 4X Y-axis level in the latter part of the read test.

The first graph shows the severe and repeated errors at strangely regular intervals encountered during the initial occurance of the problem. This is clearly abnormal and concerning as far as integrity of a full 90 GB disc of data is concerned. Interestingly, when the same test is repeated with the same disc on a second identical Pioneer BD writer in the same computer system (second graph), the second drive seems to read the badly written disc much more tolerably with only one major dip in transfer speed.

The third and fourth graphs posted is after the computer system was restored to normal operating state, reading another (different) full BD-RE-TL disc written to full capacity of data (90.2 GB formatted capacity) using the first and second identical model Pioneer 09 series drive both installed on the same computer system. This disc verified with no reported errors from Imgburn so any errors were within the corrective capacity of the ODD. I think the X-axis scaling of the drive spindle speed is wrong, because the valley of the green plot is at the 23 GB mark which is correct for a BD-DL disc, since BD-DL is 46 GB formatted capacity and 23 GB per layer. However, I think the program got confused on handling BD-TL media. On TL media, it's 90.2 GB formatted capacity so it's basically 30 GB per layer, and we could see that at the 30 GB point for both 3rd and 4th graph plots, there's a dip in data transfer rate and drive rotational speed, so this appears to be the normal dip in transfer rate near the L0 (deepest layer) to L1 layer (middle layer) switching point. However, it can be seen that the second and newer drive on this computer, which was manufactured a few years later compared to the first drive even though both drives are the exact same model number and firmware, performs better during the layer switch as well as handling other disc errors, at least in reading this particular type of BDRE-TL media.

Edited January 13, 2019 by discuser

[dbminter]

Sudden, inexplicable Windows errors popping up out of the clear blue is nothing new.  You've learned the best lesson in why you should have disc images of your Windows partition.  I take one every day and keep a week's retention of daily backups.  I also take a weekly backup and keep a month's retention of those.  I also take a monthly image and retain a year's worth of those.  And, lastly, I do a yearly image and retain those for a year.  Since you're most unlikely to discover a sudden error shortly after it pops up, you never know how far back you'll need to restore from to fix it.

[discuser]

Yes, except this isn't just some random problem with Windows. It was a very specific and never before encountered disk I/O issue that even looked like a hardware problem at first. its symptoms appeared even well before the pre-desktop loading phase finished in Windows, it was something fundamental on the lowest level of OS services. Could have been some type of damage to the installation somehow or it was altered during updating of my anti-virus software. I've been using both DOS and Windows for decades, and have never encountered something like this on a highly stabilized, tightened and lean running OS installation that's been running stably for a very long time. Best just to restore from image than to spend time hunting and fixing the problem. Though ultimately, it was interesting to see the disc tests afterwards in the graphs I posted.

Edited January 13, 2019 by discuser

[dbminter]

But, it is a random Windows problem.  It was working fine one day and then stopped working right that was fixed by restoring Windows to a previous point where it was working fine and apparently resumed working fine again.  That's what I define as a random Windows problem.  And Windows is prone to doing just such things.  It will randomly forget user settings or how to perform an operation it had done just fine before.  Or randomly delete important program files that are needed for a program's operation so that it won't work anymore, etc.

[discuser]

18 hours ago, dbminter said:

But, it is a random Windows problem.  It was working fine one day and then stopped working right that was fixed by restoring Windows to a previous point where it was working fine and apparently resumed working fine again.  That's what I define as a random Windows problem.  And Windows is prone to doing just such things.  It will randomly forget user settings or how to perform an operation it had done just fine before.  Or randomly delete important program files that are needed for a program's operation so that it won't work anymore, etc.

I actually have my suspicions about what the cause is, likely due to a software update in a particular installed program due to the timing of the symptoms' occurance, but didn't want to go into it at length and keep the subject matter on topic related to ODD observations. As for back up, it's a practice for safe computing which goes without saying.

Edited January 14, 2019 by discuser