akis73 Posted December 9, 2017 Posted December 9, 2017 (edited) Dear all, Lately I have been noticing that 50gb blu ray backups of movies fail to play on my desktop blu ray player. I get skips and freezes when playing the discs. I produce all my copies wit Imgburn hence I decided to investigate in order to rule out either bad discs or a defective burner. My blu ray burner is relatively new (purchased Aug 2016) and is the LG BH16NS55 and the discs I am burning to are Verbatim ones with MID code VERBAT-IMf-000. Here's the log, I would appreciate it if someone can narrow down the problem. ------------------------------- I 23:48:24 Operation Started!I 23:48:24 Source Device: [4:0:0] HL-DT-ST BD-RE BH16NS55 1.02 (G:) (SATA)I 23:48:24 Source Media Type: BD-R (Disc ID: VERBAT-IMf-000)I 23:48:24 Source Media Supported Read Speeds: 2x; 4x; 6x; 8xI 23:48:24 Source Media Supported Write Speeds: 2x; 4x; 6x; 8xI 23:48:24 Source Media Sectors: 19.421.344I 23:48:24 Source Media Size: 39.774.912.512 bytesI 23:48:24 Image File: I:\METALLICA_NIMES_2009.isoI 23:48:24 Image File Sectors: 19.421.344 (MODE1/2048)I 23:48:24 Image File Size: 39.774.912.512 bytesI 23:48:24 Image File Volume Identifier: METALLICA_NIMES_2009I 23:48:24 Image File Volume Set Identifier: 3B928838________METALLICA_NIMES_2009I 23:48:24 Image File Application Identifier: vso_hwe.dll 4.0.5.464I 23:48:24 Image File Implementation Identifier: VsoSoftwareI 23:48:24 Image File File System(s): UDF (2.50)I 23:48:24 Read Speed (Data/Audio): MAX / MAXI 23:48:25 Read Speed - Effective: 3x - 8x; 8x - 3xI 23:48:25 Verifying Session 1 of 1... (1 Track, LBA: 0 - 19421343)I 23:48:25 Verifying Track 1 of 1... (MODE1/2048, LBA: 0 - 19421343)I 23:48:25 Verifying Layer 0... (LBA: 0 - 12219391)I 00:04:25 Verifying Layer 1... (LBA: 12219392 - 19421343)W 00:04:35 Failed to Read Sectors 12219392 - 12219423 - Reason: L-EC Uncorrectable ErrorW 00:04:43 Failed to Read Sector 12219392 - Reason: L-EC Uncorrectable ErrorW 00:04:43 Sector 12219392 maps to File: \BDMV\STREAM\00011.m2tsW 00:04:52 Retrying (1)...I 00:04:54 Verifying Sectors...W 00:05:20 Failed to Read Sectors 12221856 - 12221887 - Reason: L-EC Uncorrectable ErrorI 00:31:45 Exporting Graph Data...I 00:31:45 Graph Data File: C:\Users\Akis\AppData\Roaming\ImgBurn\Graph Data Files\HL-DT-ST_BD-RE_BH16NS55_1.02_ΣΆΒΒΑΤΟ-9-ΔΕΚΈΜΒΡΙΟς-2017_11-48_μμ_VERBAT-IMf-000.ibgI 00:31:45 Export Successfully Completed!I 00:31:45 Operation Successfully Completed! - Duration: 00:43:20I 00:31:45 Average Verify Rate: 14.945 KiB/s (3.4x) - Maximum Verify Rate: 36.083 KiB/s (8.2x) Edited December 10, 2017 by akis73
dbminter Posted December 10, 2017 Posted December 10, 2017 Probably the fault of the LG drive. I've had about 5 models of different kinds of LG BD burners and they all failed to burn properly to Verbatim BD-RE DL. Constant errors on Verifying the second layer. So, while I've never used BD-R DL to burn in an LG drive, I've come to the conclusion that LG's are terrible writers when it comes to burning BD DL media. And while I've never burned a BD-R DL in my Pioneer drive, I would recommend trying a Pioneer drive for burning BD-R DL. They burn my Verbatim BD-RE DL fine, so I can't see why they wouldn't work fine on Verbatim BD-R DL. Also, have you burned any BD-R DL without playback problems before? Or are all your BD-R DL's burnt doing these playback problems? And notice how your Verify errors occur right at the exact start of the 2nd layer?
akis73 Posted December 10, 2017 Author Posted December 10, 2017 Dear dbminter, Thanks for your reply. Since I purchased the drive off Amazon I contacted them saying the drive has started malfunctioning. So they are sending a replacement drive since it is still under the 2 yr warranty. So this will rule the faulty drive out. The other reason could be the discs but I always buy from the same Japanese seller on ebay who has genuine Verbatim discs. So if it comes down to an LG drive which cannot hold to its standard then this is very disappointing. But I actually have an older Pioneer drive which I am not using so I will try burning the DL discs with that and see what happens. However, don't you think it's a bit strange that all LG drives have trouble burning to DL discs? Unless the one I got was from a defective batch. Thanks once more for your help, I will let you know when I do tests with the Pioneer drive and with the new LG drive when this arrives.
dbminter Posted December 10, 2017 Posted December 10, 2017 Yes, if you get the same results with another LG drive of the same model, you will know it's the drive. My conclusion is based on 5 LG's I've had, 3 of the latest model, and 2 others, and those 3 of the latest don't burn BD-RE DL right at all. Out of 5 burns, only 1 completed write and verify. Your discs shouldn't be the problem. The DID indicates they're the good kind of Verbatim BD media. However, you could always have a bad batch of discs, but I doubt it. No, I don't find it strange at all that all LG drives may be bad at writing BD DL media. If they don't do it right out of the research and development facility, then, they all will not do it right out of the factory. Take ASUS's latest BD burner. It's bad out of the factory, too. Destroys 8x DVD+RW and Verbatm BD-RE and BD-RE DL when it writes to them. It did this on 2 copies of the same drive I tried out, so it's a manufacturing defect. I don't think it's bad batch of drives since I had 3 of the LG's over the course of 3 years that all did the same. LG's are also terrible writers at writing BD-RE SL as giant floppies. They write at half the speed as the Pioneer does. Even writing BD-RE DL as giant floppies are no go on LG drives. They will write the files, but the files will be utterly useless on the disc. All will have had write errors and their contents will be corrupted. LG's are also terrible readers. Yet, oddly enough, I had a disc that my Pioneer wouldn't read but my LG would. Go figure. The only reason I still have an LG is because Pioneer borked the firmware for writing Ritek 8x DVD+RW discs. They will always fail verify and all drives writing afterwards will always fail verify until fully formatted in another drive. My LG is perfectly fine for writing all other kinds of media that I tested it with, Even BD-R SL and BD-RE SL. However, I absolutely always avoid BD-RE DL in it. It's not a reliable drive for writing BD-RE DL, so I can't see it writing BD-R DL well either.
akis73 Posted December 11, 2017 Author Posted December 11, 2017 Dear dbminter, Thanks once more for replying and your interest in my situation. As I said I had an older Pioneer drive (BDR 206) lying around so what I did was to remove the LG drive and install the Pioneer drive instead. So I burnt the movie using the same Verbatim media but this time usiong the Pioneer drive instead of the LG one. And guess what I have a perfect copy which passed the verify process too with no errors. So this leads to the conclusion that there maybe something wrong indeed with this particular LG drive BH16NS55 and Verbatim media having the MID Code VERBAT-IMf-000. However I still think it is unacceptable for such a large company as LG to ship such a drive which fails to burn copies especially of Verbatim media which are considered as top notch. I will try to escalate the matter further with LG, however Amazon will be sending me the same replacement drive and I hope that in the end it will come down to a problematic drive. Which means that I expect the replacement drive to be able to burn a perfect copy without verification errors.
dbminter Posted December 11, 2017 Posted December 11, 2017 Unfortunately, the bottom line is LG is a corporation, and all they care about is money. The profit margins are drastically shrinking on optical products, so manufacturers just don't care anymore. Not that they ever cared before. I told Pioneer about their latest firmware borking 8x DVD+RW Ritek media. Do you think they fixed it? No, because they don't care. You can try swapping LG's all you like. I still say you'll find the same result. ASUS did the same thing. The USB ASUS I have worked on all media tests I threw at it. So, I had high hopes for their internal burner. But, it's borked! Destroys rewritable media! Did this on 2 copies of the same drive. So, which is more likely? That I just happened to get 2 bad drives in a row from different batches or that the drive itself doesn't work right out of the gate?
akis73 Posted December 22, 2017 Author Posted December 22, 2017 (edited) Dear dbminter and dear all, Amazon have now sent me a replacement drive. It appears to be identical to the one I have sent back. It still has the 1.02 f/w (I dont think there is a newer one). The only difference is that the manufacturing date is now Sep 2017. Unfortunately it seems that the drive has been performing even worse than the one I sent back. Here's a log of a 50gb .iso image of blu ray disk I tried to burn a couple of minutes ago. The drive has bombed out while burning the layer change. I am going to send this back too and get Amazon to send me the equivalent Pioneer one, Im fed up with LG @dbminter: I think you were right from the start. I would like to escalate the matter further with LG, however I dont have the time and dont think it's worth it for the 70 EUR the drive costs. I 23:07:52 ImgBurn Version 2.5.8.0 started!I 23:07:52 Microsoft Windows 7 Ultimate x64 Edition (6.1, Build 7601 : Service Pack 1)I 23:07:52 Total Physical Memory: 16.735.892 KiB - Available: 13.832.412 KiBI 23:07:52 Initialising SPTI...I 23:07:52 Searching for SCSI / ATAPI devices...I 23:07:53 -> Drive 1 - Info: HL-DT-ST BD-RE BH16NS55 1.02-01 (G:) (SATA)I 23:07:53 -> Drive 2 - Info: ELBY CLONEDRIVE 1.4 (F:) (SCSI)I 23:07:53 Found 1 BD-ROM/HD DVD-ROM and 1 BD-RE XL!I 23:11:45 Operation Started!I 23:11:45 Source File: H:\WIENER PHILHARMONIKER 2017 NEW YEARS CONCERT.ISOI 23:11:45 Source File Sectors: 18.131.104 (MODE1/2048)I 23:11:45 Source File Size: 37.132.500.992 bytesI 23:11:45 Source File Volume Identifier: WIENER PHILHARMONIKER 2017 NEW YEARS CONCERTI 23:11:45 Source File Volume Set Identifier: 4B1BAAC70114A7E5I 23:11:45 Source File Application Identifier: ImgBurn v2.5.8.0I 23:11:45 Source File Implementation Identifier: ImgBurnI 23:11:45 Source File File System(s): UDF (2.50)I 23:11:45 Destination Device: [4:0:0] HL-DT-ST BD-RE BH16NS55 1.02 (G:) (SATA)I 23:11:45 Destination Media Type: BD-R (Disc ID: VERBAT-IMf-000)I 23:11:45 Destination Media Supported Write Speeds: 2x; 4x; 6x; 8xI 23:11:45 Destination Media Sectors: 24.438.784I 23:11:45 Write Mode: BDI 23:11:45 Write Type: DAOI 23:11:45 Write Speed: MAXI 23:11:45 Hardware Defect Management Active: NoI 23:11:45 BD-R Verify Not Required: YesI 23:11:45 Link Size: AutoI 23:11:45 Lock Volume: YesI 23:11:45 Test Mode: NoI 23:11:45 OPC: NoI 23:11:45 BURN-Proof: EnabledI 23:11:45 Write Speed Successfully Set! - Effective: 35.968 KB/s (8x)I 23:12:21 Filling Buffer... (80 MiB)I 23:12:22 Writing LeadIn...I 23:12:24 Writing Session 1 of 1... (1 Track, LBA: 0 - 18131103)I 23:12:24 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 18131103)I 23:12:24 Writing Layer 0... (LBA: 0 - 12219391)W 23:23:55 Failed to Write Sectors 10944512 - 10944543 - Reason: Invalid Field in CDBW 23:23:55 Retrying (1 of 20)...W 23:23:55 Retry Failed - Reason: Invalid Field in CDBW 23:23:55 Retrying (2 of 20)...W 23:23:55 Retry Failed - Reason: Invalid Field in CDBW 23:23:55 Retrying (3 of 20)...W 23:23:56 Retry Failed - Reason: Invalid Field in CDBW 23:23:56 Retrying (4 of 20)...W 23:23:56 Retry Failed - Reason: Invalid Field in CDBW 23:23:56 Retrying (5 of 20)...W 23:23:56 Retry Failed - Reason: Invalid Field in CDBW 23:23:56 Retrying (6 of 20)...W 23:23:56 Retry Failed - Reason: Invalid Field in CDBW 23:23:56 Retrying (7 of 20)...W 23:23:56 Retry Failed - Reason: Invalid Field in CDBW 23:23:56 Retrying (8 of 20)...W 23:23:56 Retry Failed - Reason: Invalid Field in CDBW 23:23:56 Retrying (9 of 20)...W 23:23:56 Retry Failed - Reason: Invalid Field in CDBW 23:23:56 Retrying (10 of 20)...W 23:23:56 Retry Failed - Reason: Invalid Field in CDBW 23:23:56 Retrying (11 of 20)...W 23:23:56 Retry Failed - Reason: Invalid Field in CDBW 23:23:56 Retrying (12 of 20)...W 23:23:56 Retry Failed - Reason: Invalid Field in CDBW 23:23:56 Retrying (13 of 20)...W 23:23:56 Retry Failed - Reason: Invalid Field in CDBW 23:23:56 Retrying (14 of 20)...W 23:23:56 Retry Failed - Reason: Invalid Field in CDBW 23:23:56 Retrying (15 of 20)...W 23:23:56 Retry Failed - Reason: Invalid Field in CDBW 23:23:56 Retrying (16 of 20)...W 23:23:56 Retry Failed - Reason: Invalid Field in CDBW 23:23:56 Retrying (17 of 20)...W 23:23:56 Retry Failed - Reason: Invalid Field in CDBW 23:23:56 Retrying (18 of 20)...W 23:23:56 Retry Failed - Reason: Invalid Field in CDBW 23:23:56 Retrying (19 of 20)...W 23:23:56 Retry Failed - Reason: Invalid Field in CDBW 23:23:56 Retrying (20 of 20)...W 23:23:56 Retry Failed - Reason: Invalid Field in CDBE 23:24:37 Failed to Write Sectors 10944512 - 10944543 - Reason: Invalid Field in CDBI 23:24:37 Synchronising Cache...W 23:24:37 Synchronise Cache Failed! - Reason: Invalid Field in CDBW 23:24:42 Synchronise Cache Failed! - Reason: Invalid Field in CDBW 23:24:43 User opted to skip the 'Close Track/Session/Disc' functions.E 23:24:43 Failed to Write Image!I 23:24:43 Exporting Graph Data...I 23:24:43 Graph Data File: C:\Users\Akis\AppData\Roaming\ImgBurn\Graph Data Files\HL-DT-ST_BD-RE_BH16NS55_1.02_ΠΑΡΑΣΚΕΥΉ-22-ΔΕΚΈΜΒΡΙΟς-2017_11-11_μμ_VERBAT-IMf-000_MAX.ibgI 23:24:43 Export Successfully Completed!E 23:24:43 Operation Failed! - Duration: 00:12:58I 23:24:43 Average Write Rate: 29.862 KiB/s (6.8x) - Maximum Write Rate: 35.495 KiB/s (8.1x) Edited December 22, 2017 by akis73
dbminter Posted December 23, 2017 Posted December 23, 2017 (edited) Two pieces of new information have come to light since this thread was started. One, there is a 1.03 firmware update for the drive, released about 2 weeks ago, but as far as I know, it doesn't fix any of the problems it still had, after testing it. I think 1.03 is ONLY a fix to prevent people from copying UHD Blu-Ray discs. It seems this update was only one mandated by Hollywood and does nothing to address the inherent flaws in the drive. If you're still willing to try LG drives, some rather odd behavior has been revealed with ImgBurn, ISO's, and LG drives. I didn't discover this, but I've tested it and the workaround does work. If you absolutely don't need to burn from an ISO, try the Write files to disc option from the EZ Mode Picker. I've tested it and it seems to work. If you use an ISO with ImgBurn on an LG with Verbatim BD-RE DL and BD-R DL, it will fail Verify at the layer change 9 times out of 10. However, the 3 tests I ran with the EZ Mode Picker method worked flawlessly. So, I created an ISO with ImgBurn, but I didn't use ImgBurn to burn the ISO. I used Roxio NXT 4 to burn the ISO and it completed without error. I then ran an ImgBurn Verify manually on the disc against the contents and the Verify completed successfully. I did 3 other tests this way and they all performed flawlessly. I then did a compare on the contents and they were written correctly. However, be aware of the drawbacks to this method. If you have a corrupt file during the burn process or a read occurs during copying, then the burn will fail and you've wasted a disc. Or the burn may succeed and the contents were written corrupt to the disc. You should always write to ISO files first IF you have the luxury of doing so. So, if you really want to write ISO's to Verbatim BD-R/E DL in an LG, then use the EZ Mode Picker to Write files to disc without creating an ISO. Or, if you have an ISO made by ImgBurn or any other application, don't let ImgBurn burn the ISO to a Verbatim BD-R/E DL in an LG. It makes absolutely no sense, but it has been independently verified by myself, multiple times, and by someone else who pointed this out to me. So, it's repeatable. However, if you replace the LG with a Pioneer, this should most likely definitely solve your problem. Not a guarantee as the last Pioneer I had was borked out of the box. As for getting help from LG, good luck. I've pointed out to LG for like 3 years of the problems with this drive. They don't care. However, at the time, I didn't realize the ImgBurn problem was isolated to just ImgBurn. But, there are other problems with the LG. For instance, what takes about 2 hours to write contents to a formatted BD-RE DL as a giant floppy in my Pioneer takes 9 hours to write just the FIRST LAYER! And it won't even write contents to the 2nd layer! Returns a error saying it cannot read the files from the "source drive." It's NOT an error reading from the source drive; it's an error writing the contents to the 2nd layer! I wouldn't use LG at all if it weren't for the fact that Pioneer and ASUS don't write Ritek 6x DVD-RW. (The LG won't write Verbatim 6x DVD-RW! Idiots!) And the borked firmware of the Pioneer 1.34 won't write to Ritek 8x DVD+RW. Once my supply of Ritek 6x DVD-RW and 8x DVD+RW are exhausted (You can't get 8x DVD+RW or 6x DVD-RW anywhere on the Internet anymore! ) I will replace the LG with another Pioneer. Edited December 23, 2017 by dbminter
akis73 Posted December 23, 2017 Author Posted December 23, 2017 Dear dbminter, Thanks once more for your reply. So it seems that there is some bug between imgburn and LG drives which leads to failed burns of DL Verbatim media. Thanks for letting me know, as I was not aware of that. I would have asked if this something to be fixed in the near future or due to the LG hardware it cannot be alleviated. But now I have sent the item back to Amazon again and I am going to get my money back. So I am still using my old BDR-206 Pioneer drive which seems to make perfect copies to DL Verbatim media. I never have used Ritek and I see that you are saying that there are nowhere to be found nowadays. I got the LG in the 1st place due to the partial UHD support and slighly faster speeds. I discovered that SL Verbatim media were still burnt @ the same speed as my old Pioneer and also reading from burnt discs was slow. So after ditching LG I think the best drive to get now is the new Pioneer BDR-211UBK which has also full UHD support. Unfrortunately this drive is still very expensive in Europe (200+ euro) so I will wait for the price to come down. Thanks once more for your help and merry Xmas.
dbminter Posted December 23, 2017 Posted December 23, 2017 Well, here's the weird thing. There SHOULDN'T be any difference between burning an ISO and writing files on the fly in ImgBurn. But, actual execution shows there is some kind of weird incompatibility with writing ISO's to Verbatim BD-R/RE DL's in an LG. It has to be something in the LG that is the problem, because, as you know, Pioneers have no problem with this. Even LUK, who knows the code inside and out, has commented there's no difference in the code. But, I've been able to verify it myself, after the original poster posted his workaround. LG's are not very good readers, as you pointed out. However, I had one case where my Pioneer wouldn't read a disc that the LG would. Go figure. I couldn't find anywhere with Google that was still selling 8x DVD+RW, Ritek or otherwise. Ritek had already discontinued their 6x DVD-RW some years ago. I'm holding off on Pioneer's latest BD drive. Since it's only real difference is probably the support of UHD playback, which I don't need. Plus, it's "too" new. I know how well my Pioneer works. And there's probably not a firmware update yet. I don't like getting drives that don't have firmware updates yet, believe it or not. I think they'd just have too many gotchas lurking in the background that haven't been discovered yet.
dbminter Posted December 27, 2017 Posted December 27, 2017 Funny enough, I just had to replace my current Pioneer 2209. After about 2 years, it stopped erasing/writing BD-RE S/DL discs correctly. I'd insert a formatted BD-RE S/DL and delete files from it. File Explorer would show the files were deleted UNTIL the disc was ejected and reinserted. The files are never actually deleted. I put in my 3 to 4 year old copy of the same drive, which still works save for the eject button issue, and it deletes the files fine. So, it was the 3rd Pioneer 2209 I was using. It needed replacing. So, I'm going to use this older one until I can get a new 2209 next month. The drive was also returning errors where files to be written weren't actually written and Windows prompting multiple times to repair these written to discs when inserted.
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now