Jump to content

Random Trouble with BD write/verify


h0ky539

Recommended Posts

Reason I'm posting here is because Imgburns verify is less successful than that of VSO Inspector - I have had to cancel IBs verification several times as it cannot advance regardless of 'retry/continue' & use the VSO prog.

Nevertheless I suspect that there may be an issue with the drive or the media not imgburn.

 

 

Using a HL-DT-ST BD-RE  BH16NS40 1.03-A0 (latest FW) & Verbatim SL 25gb BD-R (Disc ID: CMCMAG-BA5-000) I have recently started getting issues with burns giving me a variety of check condition errors e.g. Power On, Reset, or Bus Device Reset Occurred; Device not ready etc.

I'm burning @4x, sometimes the burn will halt with a check device condition; device not ready, msg normally this will occur after 50% of burn is made.

If the burn completes when verification is run it tends to hang or stop with errors around the 80% area (78%, 84% 86% etc).

 

I put VSO Inspector on to see if that would read the discs & it does & shows some areas of imperfection - surface scan req's can multiple tries & file scan detects unreadable files, read speeds also tank at the same areas. 

 

When running multiple successive ops e.g. - burn/verify; verify; verify;  the drive can sometimes disappear from the device list & I need to rescan in DevMan to get it back.

With DevMan open it doesn't appear to drop from the DVD\CD-ROM Drives list burning burn/verify, but it may afterwards.  I can hit rescan during a halt condition dialog & the entries remain.

Overheating? 

The verify process can take a long time, I had one @1hr+ for 25gb.  :boredom:

 

Any of the resident experts know/guess if this is a dying drive or just a bad media batch?

 



I 11:48:17 ImgBurn Version 2.5.8.0 started!
I 11:48:17 Microsoft Windows 7 Ultimate x64 Edition (6.1, Build 7601 : Service Pack 1)
I 11:48:17 Total Physical Memory: 16,675,416 KiB - Available: 12,696,764 KiB
I 11:48:17 Initialising SPTI...
I 11:48:17 Searching for SCSI / ATAPI devices...
I 11:48:17 -> Drive 1 - Info: DiscSoft Virtual 1.0 (R:) (Virtual)
I 11:48:18 -> Drive 2 - Info: HL-DT-ST BD-RE BH16NS40 1.03-A0 (I:) (SATA)
I 11:48:18 -> Drive 3 - Info: TSSTcorp CDDVDW SH-224DB SB01 (H:) (SATA)
I 11:48:18 Found 1 DVD±RW/RAM, 1 BD-ROM XL and 1 BD-RE XL!
I 11:48:30 Project Successfully Loaded!
I 11:48:30 File Name: C:\Users\\AppData\Roaming\ImgBurn\Project Files\Disc.ibb
I 11:48:42 Operation Started!
I 11:48:42 Building Image Tree...
I 11:48:42 Calculating Totals...
I 11:48:43 Preparing Image...
I 11:48:43 Contents: 1,897 Files, 5 Folders
I 11:48:43 Content Type: Data
I 11:48:43 Data Type: MODE1/2048
I 11:48:43 File System(s): UDF (1.02)
I 11:48:43 Volume Label: Disc
I 11:48:43 Size: 25,011,836,163 bytes
I 11:48:43 Sectors: 12,214,061
I 11:48:43 Image Size: 25,019,023,360 bytes
I 11:48:43 Image Sectors: 12,216,320
I 11:48:45 Operation Successfully Completed! - Duration: 00:00:02
I 11:48:45 Operation Started!
I 11:48:45 Source File: -==/\/[BUILD IMAGE]\/\==-
I 11:48:45 Source File Sectors: 12,216,320 (MODE1/2048)
I 11:48:45 Source File Size: 25,019,023,360 bytes
I 11:48:45 Source File Volume Identifier: Disc
I 11:48:45 Source File Volume Set Identifier: 48C85E1500BA67E3
I 11:48:45 Source File Application Identifier: ImgBurn v2.5.8.0
I 11:48:45 Source File Implementation Identifier: ImgBurn
I 11:48:45 Source File File System(s): UDF (1.02)
I 11:48:45 Destination Device: [4:0:0] HL-DT-ST BD-RE BH16NS40 1.03 (I:) (SATA)
I 11:48:45 Destination Media Type: BD-R (Disc ID: CMCMAG-BA5-000)
I 11:48:45 Destination Media Supported Write Speeds: 4x, 6x, 8x, 10x, 12x
I 11:48:45 Destination Media Sectors: 12,219,392
I 11:48:45 Write Mode: BD
I 11:48:45 Write Type: DAO
I 11:48:45 Write Speed: 4x
I 11:48:45 Hardware Defect Management Active: No
I 11:48:45 BD-R Verify Not Required: Yes
I 11:48:45 Link Size: Auto
I 11:48:45 Lock Volume: Yes
I 11:48:45 Test Mode: No
I 11:48:45 OPC: No
I 11:48:45 BURN-Proof: Enabled
I 11:48:45 Write Speed Successfully Set! - Effective: 17,984 KB/s (4x)
I 11:48:58 Filling Buffer... (80 MiB)
I 11:48:59 Writing LeadIn...
I 11:48:59 Writing Session 1 of 1... (1 Track, LBA: 0 - 12216319)
I 11:48:59 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 12216319)
I 12:12:10 Synchronising Cache...
I 12:12:13 Closing Track...
I 12:12:14 Finalising Disc...
W 12:12:51 Potential 'WaitImmediateIO' Deferred Error - (99%, 0/3) - Power On, Reset, or Bus Device Reset Occurred
W 12:12:51 Finalise Disc Failed! - Reason: Power On, Reset, or Bus Device Reset Occurred
W 12:12:51 Retrying (1 of 3)...
W 12:12:51 Retry Failed - Reason: Cannot Format Medium - Incompatible Medium
W 12:12:51 Retrying (2 of 3)...
W 12:12:51 Retry Failed - Reason: Cannot Format Medium - Incompatible Medium
W 12:12:51 Retrying (3 of 3)...
W 12:12:51 Retry Failed - Reason: Cannot Format Medium - Incompatible Medium
W 12:12:59 Retrying (4)...
W 12:12:59 Retry Failed - Reason: Cannot Format Medium - Incompatible Medium
W 12:13:00 Retrying (5)...
W 12:13:00 Retry Failed - Reason: Cannot Format Medium - Incompatible Medium
W 12:13:00 Retrying (6)...
W 12:13:00 Retry Failed - Reason: Cannot Format Medium - Incompatible Medium
W 12:13:05 Retrying (7)...
W 12:13:05 Retry Failed - Reason: Cannot Format Medium - Incompatible Medium
W 12:13:06 Retrying (8)...
W 12:13:06 Retry Failed - Reason: Cannot Format Medium - Incompatible Medium
I 12:13:08 Exporting Graph Data...
I 12:13:08 Graph Data File: C:\Users\\AppData\Roaming\ImgBurn\Graph Data Files\HL-DT-ST_BD-RE_BH16NS40_1.03_08-JUNE-2016_11-48_CMCMAG-BA5-000_4x.ibg
I 12:13:08 Export Successfully Completed!
I 12:13:08 Operation Successfully Completed! - Duration: 00:24:22
I 12:13:08 Average Write Rate: 17,564 KiB/s (4.0x) - Maximum Write Rate: 17,690 KiB/s (4.0x)
I 12:13:08 Cycling Tray before Verify...
W 12:13:15 Waiting for device to become ready...
I 12:14:26 Device Ready!
I 12:15:51 Operation Started!
I 12:15:51 Source Device: [4:0:0] HL-DT-ST BD-RE BH16NS40 1.03 (I:) (SATA)
I 12:15:51 Source Media Type: BD-R (Disc ID: CMCMAG-BA5-000)
I 12:15:51 Source Media Supported Read Speeds: 2x, 4.2x, 6.2x, 8x, 9.9x, 12.1x
I 12:15:51 Source Media Supported Write Speeds: 4x, 6x, 8x, 10x, 12x
I 12:15:51 Source Media Sectors: 12,216,320
I 12:15:51 Source Media Size: 25,019,023,360 bytes
I 12:15:51 Image File: -==/\/[BUILD IMAGE]\/\==-
I 12:15:51 Image File Sectors: 12,216,320 (MODE1/2048)
I 12:15:51 Image File Size: 25,019,023,360 bytes
I 12:15:51 Image File Volume Identifier:
I 12:15:51 Image File Volume Set Identifier: 48C85E1500BA67E3
I 12:15:51 Image File Application Identifier: ImgBurn v2.5.8.0
I 12:15:51 Image File Implementation Identifier: ImgBurn
I 12:15:51 Image File File System(s): UDF (1.02)
I 12:15:51 Read Speed (Data/Audio): MAX / MAX
I 12:15:52 Read Speed - Effective: 5x - 12.1x
I 12:15:52 Verifying Session 1 of 1... (1 Track, LBA: 0 - 12216319)
I 12:15:52 Verifying Track 1 of 1... (MODE1/2048, LBA: 0 - 12216319)
W 12:35:04 Failed to Read Sectors 10987680 - 10987711 - Reason: Power On, Reset, or Bus Device Reset Occurred
W 12:38:32 Failed to Read Sector 10987680 - Reason: Power On, Reset, or Bus Device Reset Occurred
W 12:38:32 Sector 10987680 maps to File: dummy.txt
W 12:39:30 Retrying (1)...
W 12:40:28 Retry Failed - Reason: Power On, Reset, or Bus Device Reset Occurred
W 12:40:31 Failed to Read Sector 10987680 - Reason: Power On, Reset, or Bus Device Reset Occurred
W 12:40:31 Sector 10987680 maps to File: dummy.txt
W 12:42:02 Failed to Read Sectors 11512336 - 11512367 - Reason: Power On, Reset, or Bus Device Reset Occurred
W 12:42:28 Failed to Read Sector 11512336 - Reason: Power On, Reset, or Bus Device Reset Occurred
W 12:42:28 Sector 11512336 maps to File: dummy.txt
E 12:42:30 Failed to Read Sector 11512336 - Reason: Power On, Reset, or Bus Device Reset Occurred
E 12:42:30 Sector 11512336 maps to File:dummy.txt
E 12:42:31 Failed to Verify Sectors!
I 12:42:32 Exporting Graph Data...
I 12:42:32 Graph Data File: C:\Users\\AppData\Roaming\ImgBurn\Graph Data Files\HL-DT-ST_BD-RE_BH16NS40_1.03_08-JUNE-2016_11-48_CMCMAG-BA5-000_4x.ibg
I 12:42:32 Export Successfully Completed!
E 12:42:32 Operation Failed! - Duration: 00:26:39
I 12:42:32 Average Verify Rate: 14,408 KiB/s (3.3x) - Maximum Verify Rate: 52,059 KiB/s (11.9x)



 

post-55541-0-39837000-1465394665_thumb.png

post-55541-0-32569700-1465394689_thumb.png

Link to comment
Share on other sites

That looks like a driver issue to me. Something is timing out early and resetting the device because it thinks it has got stuck.

 

Right click the drive selection box and pick 'Family Tree'.

 

Close the prompt and then copy + paste everything from the Log window.

Link to comment
Share on other sites

Thanks for the rapid reply! :wink:

Here is the log

I 16:00:49 Device: [4:0:0] HL-DT-ST BD-RE  BH16NS40 1.03 (I:) (SATA)
I 16:00:49 Family Tree:
I 16:00:49 -> ACPI x64-based PC
I 16:00:49 -> Microsoft ACPI-Compliant System
I 16:00:49 -> PCI bus
I 16:00:49 -> Standard AHCI 1.0 Serial ATA Controller (VEN_1002&DEV_4391 - ATI - msahci - v6.1.7601.18231)
I 16:00:49 -> IDE Channel (ATA Channel 5)
I 16:00:49 -> CD-ROM Drive (HL-DT-ST BD-RE  BH16NS40 ATA Device) (Channel 5, Target 0, Lun 0)

I have a AMD 970 mobo & I removed the AMD SATA driver yesterday & let W7 use it's own generic stuff to see if it would make a difference - it hasn't.

Link to comment
Share on other sites

I put the BDRW on the very last header/port, which can be set to IDE.  Tried it yesterday & it didn't like it.

The weird thing is that it has been working for about 15 months on the AHCI BIOS setting.

Will try safe mode in a bit

Thanks

Link to comment
Share on other sites

Well, after a few more hours messing about & swapping cables etc I managed to trash a few more discs & now the BDRW reads nothing at all, just sits there spinning & seeking.

VERY  :swear: at LG, this is 18mths old & has burnt 72 of the verb. discs inc 8 I just trashed. 

Only used for archiving & not for reading/making images so I think that was a really bad MTBF rating!  

 

Is this widely known as a low life-span drive?

 

Thanks again for the assistance, LIGHTNING UK!

Link to comment
Share on other sites

I've had 2 LG Blu-Ray burners and they lasted about a year before needing replacing for various burn related reasons.  So, yours lasted longer than mine.

 

 

I'll never get another LG drive.  I had an LG DVD burner over 10 years ago that was my first clue to avoid them.  Every DVD Video it burned had skips in the play back on DVD players.  What turned me off to the LG Blu-Ray burners was they were pretty lousy readers.  They would fail to read data from discs that my Pioneer would read fine.  So, after my last LG died, I replaced it with a Pioneer.  Pioneer was doing well until their latest firmware borked Ritek RICOH 8x DVD+RW burns, which would fail on Verify, no matter the drive being used for Verify, so it's a burn issue.  I replaced the Pioneer with an ASUS because I have an ASUS external that only failed on one test, Ritek 6x DVD-RW.  But, that test always fails, except on LiteOns and Optiarcs.

 

 

The only reason I got an LG Blu-Ray to begin with was that was all that was available in town.  The only store in town that had any Blu-Ray burners was Best Buy and all they had were LG's.

Link to comment
Share on other sites

I've had 2 LG Blu-Ray burners and they lasted about a year before needing replacing for various burn related reasons.  So, yours lasted longer than mine.

 

 

I'll never get another LG drive.  I had an LG DVD burner over 10 years ago that was my first clue to avoid them.  Every DVD Video it burned had skips in the play back on DVD players.  What turned me off to the LG Blu-Ray burners was they were pretty lousy readers.  They would fail to read data from discs that my Pioneer would read fine.  So, after my last LG died, I replaced it with a Pioneer.  Pioneer was doing well until their latest firmware borked Ritek RICOH 8x DVD+RW burns, which would fail on Verify, no matter the drive being used for Verify, so it's a burn issue.  I replaced the Pioneer with an ASUS because I have an ASUS external that only failed on one test, Ritek 6x DVD-RW.  But, that test always fails, except on LiteOns and Optiarcs.

 

 

The only reason I got an LG Blu-Ray to begin with was that was all that was available in town.  The only store in town that had any Blu-Ray burners was Best Buy and all they had were LG's.

Thanks for the reply.

 

My main complaint on that LG was the number of discs burnt, at less than 1 per week, that really sux.  If I had burnt a disc a day I could at least say I'd had fair use out of it.  When did  DVDRW or CDRW only survive such a small batch before dying?  I had an LG DVDRW way back, & that lasted over 6 years & must have burnt up to 1k dvds in that time.

 

I did see that reading back BDs it had written sometimes took a while for initializing the first dir read - maybe upto 20secs? to read the tree.  Not great.

 

I will not be trying LG again & have just ordered a Pioneer BDR-209EBK

Will see how that goes.

Link to comment
Share on other sites

It seems that the higher speed rewritable DVD's have a quicker failure rate than the lower speed ones.  I'd say on my Ritek 8x DVD+RW, I get maybe 20 rewrites on them before they die.

 

 

Be aware that the latest firmware on that Pioneer drive probably will bork writing to Ritek 8x DVD+RW.  I have a Pioneer BDR-209M and the 1.34-ID60 firmware update caused me to replace it and I will probably never get a Pioneer again.  After updating the firmware, all Verifies on that Ritek media fail Verify.  Even in other drives.  So, it's the writing process that is borked.  The same disc then written in my ASUS USB writes and verifies fine.

Link to comment
Share on other sites

I got the drive & burnt a BD, then tried reading an LG burnt BD & it all worked (!).  So far so good.  Feels like a better built unit than the LG & the read / seek times seem more stable there is no periods of hunting with the thing spinning up & the head racing back & forth as there was on the LG.

 

Funny you mentioned that firmware!

I looked at the 1.34 fw update, mine is currently 1.30, looked at the change log & thought hmmmmm this looks a bit dubious.

I've downloaded it but not used it yet.  

Hearing your info I think I will leave it alone, one duff BDRW is enuf!  Thanks for confirming my suspicion! ;)

 

Is your Asus-usb the Asus (BW-12D1S-U) External?

I looked at those before taking another internal, looks good & it seemed to have good reviews so far.

Edited by h0ky539
Link to comment
Share on other sites

The 1.33 firmware was fine for my needs, so you can probably update to that without problem.  But, I can understand if you're wary of updating something that works since you can't downgrade Pioneer firmware as far as I know.

 

 

My external Asus is the BW-12D1S-U, yes.  I can recommend that but I CANNOT recommend the ASUS BW-16D1HT SATA burner!  Here's my negative review I posted on Amazon.com:

 

"I cannot recommend this drive. After putting it through several tests, it has failed on a variety of media.

This appears to destroy rewritable media! I threw about half a dozen Ritek 8x DVD+RW at it. After a few writes, this drive would eventually write to the disc and render it empty. However, on inserting the disc into any drive afterwards, the drive lights flash infinitely. Windows will not recognize a disc has been inserted but File Explorer will list the disc as empty. I tried the same on a Verbatim BD-RE DL. It did the same thing. So, this drive destroys rewritable media. NOT a good selling point.

I inserted 2 Verbatim BD-RE DL that had been formatted by Windows as giant floppies. I copied over files to them and on random files, Windows would return the "error" Cannot read from source file or disc. Immediately selecting Retry resumes the copy. It did this once on the first disc and twice on the 2nd. However, the real killer is the files actually written to the media are not written correctly! I copied over many parts in a chain of a file backup from Macrium Reflect to these discs. Reflect would load the last file in the chain to get the list of files from the archive. However, on Verify, the first file would fail to read from the first disc! It would cause Reflect to Not Respond and eventually return the "error" Verification failure Read error - permission denied. So, this means the drive wasn't even correctly writing to the BD-RE DL media. Even after I replaced the destroyed disc with a new one. Again, another NOT good selling point.

I had such high hopes for ASUS drives. After Pioneer borked their drives with the latest firmware, I had had an ASUS USB drive that performed almost flawlessly. It only failed on Ritek 6x DVD-RW, but ALL drives except Optiarc and LiteOn fail on them. So, I was looking to replace one of my Pioneers with an SATA ASUS. I am DEFINITELY sorry I went that route. ASUS is now also on my crap list. I would return this drive but I've already removed the proof of purchase from the box to send in for a rebate.

Bottom line is this drive is junk. Do NOT buy!"

 

 

Yeah, I ran the 1.33 firmware updater and it asks if I want to update the drives up just exits out after running without doing anything.  Would have been nice if they'd SAID something about not being able to update the drives.  Fuckers.

Link to comment
Share on other sites

Yeah, I loaded the .EXE in RAR because it was self extracting archive, but it only contained another .EXE and instructions on running it silently.

 

 

I'd guess that Updater.exe's largest internal file would be the firmware file.

Link to comment
Share on other sites

Yeah, I meant from within updater.exe, not the sfx rar file.

 

My 7zip shows a '.rsrc' folder. Within that, a 'BINARY' one. Within that, there's an item named '132' (this is in the 1.34 firmware for the 209M).

 

That '132' item extracts to what looks like a binary firmware.

Link to comment
Share on other sites

  • 3 months later...
FFS !! The Pioneer BD-RW is now giving me grief.  

The disc write process (apparently) goes along without issue, it's just the read back that's a source of trouble.

Got it in June & burnt about 20 25gb bdrs.  Now it has decided to totally lock the system up during verify.

This happens within the first few minutes of the verify op starting.

Everything is locked, inc mouse & KB - cannot even get caps lock to switch on/off!  This also occurs when using a disc tester like VSO Inspector.

I need to reset or power off the PC to get access.

Makes me wonder if anyone does bdrw diagnostic test software.

Anyone have any thoughts on this ?

 

Here's a log, I've tried @4x & 6x with similar early sector read failure on verify/read ops.



I 17:06:36 ImgBurn Version 2.5.8.0 started!
I 17:06:36 Microsoft Windows 7 Ultimate x64 Edition (6.1, Build 7601 : Service Pack 1)
I 17:06:36 Total Physical Memory: 16,675,396 KiB - Available: 13,446,448 KiB
I 17:06:36 Initialising SPTI...
I 17:06:36 Searching for SCSI / ATAPI devices...
I 17:06:36 -> Drive 1 - Info: DiscSoft Virtual 1.0 (S:) (Virtual)
I 17:06:36 -> Drive 2 - Info: DiscSoft Virtual 1.0 (J:) (Virtual)
I 17:06:36 -> Drive 3 - Info: PIONEER BD-RW BDR-209M 1.30-ID60 (I:) (ATA)
I 17:06:37 -> Drive 4 - Info: TSSTcorp CDDVDW SH-224DB SB01 (H:) (ATA)
I 17:06:37 Found 1 DVD±RW/RAM, 2 BD-ROM XLs and 1 BD-RE XL!
I 17:06:47 Project Successfully Loaded!
I 17:06:47 File Name: C:\Users\__________.ibb
I 17:07:39 Operation Started!
I 17:07:39 Building Image Tree...
I 17:07:39 Calculating Totals...
I 17:07:39 Preparing Image...
I 17:07:40 Contents: 1,937 Files, 11 Folders
I 17:07:40 Content Type: Data
I 17:07:40 Data Type: MODE1/2048
I 17:07:40 File System(s): UDF (1.02)
I 17:07:40 Volume Label: -
I 17:07:40 Size: 24,991,539,455 bytes
I 17:07:40 Sectors: 12,204,172
I 17:07:40 Image Size: 24,998,838,272 bytes
I 17:07:40 Image Sectors: 12,206,464
I 17:07:42 Operation Successfully Completed! - Duration: 00:00:02
I 17:07:42 Operation Started!
I 17:07:42 Source File: -==/\/[BUILD IMAGE]\/\==-
I 17:07:42 Source File Sectors: 12,206,464 (MODE1/2048)
I 17:07:42 Source File Size: 24,998,838,272 bytes
I 17:07:42 Source File Volume Identifier: -
I 17:07:42 Source File Volume Set Identifier: 494B88F300BA4175
I 17:07:42 Source File Application Identifier: ImgBurn v2.5.8.0
I 17:07:42 Source File Implementation Identifier: ImgBurn
I 17:07:42 Source File File System(s): UDF (1.02)
I 17:07:42 Destination Device: [0:1:0] PIONEER BD-RW BDR-209M 1.30 (I:) (ATA)
I 17:07:42 Destination Media Type: BD-R (Disc ID: CMCMAG-BA5-000)
I 17:07:42 Destination Media Supported Write Speeds: 2x, 4x, 6x, 8x, 10x, 12x
I 17:07:42 Destination Media Sectors: 12,219,392
I 17:07:42 Write Mode: BD
I 17:07:42 Write Type: DAO
I 17:07:42 Write Speed: 4x
I 17:07:42 Hardware Defect Management Active: No
I 17:07:42 BD-R Verify Not Required: Yes
I 17:07:42 Link Size: Auto
I 17:07:42 Lock Volume: Yes
I 17:07:42 Test Mode: No
I 17:07:42 OPC: Yes
I 17:07:42 BURN-Proof: Enabled
I 17:07:43 Write Speed Successfully Set! - Effective: 17,980 KB/s (4x)
I 17:07:43 Advanced Settings - Optimal Writing Speed: No
I 17:07:59 Filling Buffer... (80 MiB)
I 17:08:04 Writing LeadIn...
I 17:08:05 Writing Session 1 of 1... (1 Track, LBA: 0 - 12206463)
I 17:08:06 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 12206463)
I 17:31:34 Synchronising Cache...
I 17:31:35 Closing Track...
I 17:31:36 Finalising Disc...
I 17:31:51 Exporting Graph Data...
I 17:31:51 Graph Data File: C:\Users\__\AppData\Roaming\ImgBurn\Graph Data Files\PIONEER_BD-RW_BDR-209M_1.30_11-OCTOBER-2016_17-07_CMCMAG-BA5-000_4x.ibg
I 17:31:51 Export Successfully Completed!
I 17:31:51 Operation Successfully Completed! - Duration: 00:24:09
I 17:31:51 Average Write Rate: 17,338 KiB/s (3.9x) - Maximum Write Rate: 18,981 KiB/s (4.3x)
I 17:31:51 Cycling Tray before Verify...
I 17:32:07 Device Ready!
I 17:32:08 Operation Started!
I 17:32:08 Source Device: [0:1:0] PIONEER BD-RW BDR-209M 1.30 (I:) (ATA)
I 17:32:09 Source Media Type: BD-R (Disc ID: CMCMAG-BA5-000)
I 17:32:09 Source Media Supported Read Speeds: 12x
I 17:32:09 Source Media Supported Write Speeds: 2x, 4x, 6x, 8x, 10x, 12x
I 17:32:09 Source Media Sectors: 12,206,464
I 17:32:09 Source Media Size: 24,998,838,272 bytes
I 17:32:09 Image File: -==/\/[BUILD IMAGE]\/\==-
I 17:32:09 Image File Sectors: 12,206,464 (MODE1/2048)
I 17:32:09 Image File Size: 24,998,838,272 bytes
I 17:32:09 Image File Volume Identifier: -
I 17:32:09 Image File Volume Set Identifier: 494B88F300BA4175
I 17:32:09 Image File Application Identifier: ImgBurn v2.5.8.0
I 17:32:09 Image File Implementation Identifier: ImgBurn
I 17:32:09 Image File File System(s): UDF (1.02)
I 17:32:09 Read Speed (Data/Audio): MAX / MAX
I 17:32:10 Read Speed - Effective: 5x - 12x
I 17:32:10 Verifying Session 1 of 1... (1 Track, LBA: 0 - 12206463)
I 17:32:10 Verifying Track 1 of 1... (MODE1/2048, LBA: 0 - 12206463)
W 17:32:12 Failed to Read Sectors 64 - 95 - Reason: Unknown (Internal Target Failure) (ASC: 0x44, ASCQ: 0x07)
W 17:32:12 Failed to Read Sectors 256 - 287 - Reason: Unknown (Internal Target Failure) (ASC: 0x44, ASCQ: 0x07)
W 17:32:12 Failed to Read Sector 317 - Reason: Synchronous Data Transfer Error
W 17:36:34 Retrying (1)...
I 17:36:34 Verifying Sectors...
W 17:36:34 Failed to Read Sector 325 - Reason: Unknown (Internal Target Failure) (ASC: 0x44, ASCQ: 0x07)
W 17:36:36 Failed to Read Sector 329 - Reason: Synchronous Data Transfer Error
W 17:36:36 Failed to Read Sectors 400 - 431 - Reason: Unknown (Internal Target Failure) (ASC: 0x44, ASCQ: 0x07)
W 17:36:36 Failed to Read Sector 436 - Reason: Unknown (Internal Target Failure) (ASC: 0x44, ASCQ: 0x07)
W 17:36:37 Failed to Read Sectors 896 - 927 - Reason: Synchronous Data Transfer Error
W 17:36:37 Failed to Read Sector 930 - Reason: Unknown (Internal Target Failure) (ASC: 0x44, ASCQ: 0x07)
E 17:36:39 Failed to Read Sector 930 - Reason: Unknown (Internal Target Failure) (ASC: 0x44, ASCQ: 0x07)
E 17:36:39 Failed to Verify Sectors!
I 17:36:40 Exporting Graph Data...
I 17:36:40 Graph Data File: C:\Users\-\AppData\Roaming\ImgBurn\Graph Data Files\PIONEER_BD-RW_BDR-209M_1.30_11-OCTOBER-2016_17-07_CMCMAG-BA5-000_4x.ibg
I 17:36:40 Export Successfully Completed!
E 17:36:40 Operation Failed! - Duration: 00:04:30
I 17:36:40 Average Verify Rate: 6 KiB/s (0.0x) - Maximum Verify Rate: 6 KiB/s (0.0x)


Link to comment
Share on other sites

Pioneer's can be iffy things.  Take this story.

 

 

I've had 3 of the same burners: one to replace my LG, one to serve as my read source, and a 3rd one to replace my first one because Eject didn't always work on the first time.  Well, the eject issue started up with my 3rd Pioneer after like 7 months, so there's some kind of design flaw there.  Then, after only 9 months, my 3rd burner started crapping out randomly during writes to BD-R.  I had to swap it out and replace it with my 1st burner, which is almost 2 years old, but still burns.  Just doesn't eject on the first time each time.

 

 

Then there's the 1.34 firmware.  It's borked on Ritek 8x DVD+RW media.  Burns complete but all Verifies fail.  Regressing the firmware back to 1.33, and it's all smooth sailing.

 

 

So, what can you do?  :unknown:  Pioneer is really the only option I've ever found that works "well."  So, you have to take its flaws with its benefits.  I may try the ASUS again with the express intent of being able to to return it, in case I just got a bad sample drive.

Link to comment
Share on other sites

×
×
  • Create New...

Important Information

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