holygamer Posted July 7, 2012 Share Posted July 7, 2012 I thought ImgBurn was supposed to display a message if there was a problem during the burning process? However I sent someone some discs without testing they played first and they told me that the discs didn't play on their Bluray player. Sure enough I burned another disc and tested it and it didn't play. I took my PC to a repair shop and they said the drive had died so why didn't ImgBurn say anything when it was burning the discs? Link to comment Share on other sites More sharing options...
LIGHTNING UK! Posted July 7, 2012 Share Posted July 7, 2012 Where's the log from that burn? If the drive doesn't error out, ImgBurn has nothing to report. Didn't you verify the disc as part of the burn? That would have picked up errors - assuming the drive had a problem with reading the disc. Link to comment Share on other sites More sharing options...
holygamer Posted July 7, 2012 Author Share Posted July 7, 2012 What do you mean by "error out"? It's unrealistic to expect people to do verify the disc as it doubles the burn time. There's normally no need to do it anyway as ImgBurn displays an error message if there's a problem buring the disc such as if you try to burn faster than the disc supports. I never had the log displayed while burning as it never displayed anything helpful in the past. I'm looking at the log file location just now but I only see a log for the past couple of days. Why doesn't it show more logs from previous days? Link to comment Share on other sites More sharing options...
LIGHTNING UK! Posted July 8, 2012 Share Posted July 8, 2012 Here's how things work... ImgBurn submits a command to the drive. The drive reports success/failure at processing said command. -> If it reports 'success', ImgBurn submits the next command...and so on. -> If it reports 'failure', it also returns something called 'SENSE DATA' and within that sense data is the error code. ImgBurn translates the error code into something resembling plain English and displays it to the user. If there was no need to verify, ImgBurn wouldn't enable it by default. Drives don't always error out during a burn. The drive could burn really badly and produce an unreadable disc... that's what verify picks up on. By default, ImgBurn appends (well, prepends) to a single log file. So open the one you see and just find the bit you need. Link to comment Share on other sites More sharing options...
holygamer Posted July 8, 2012 Author Share Posted July 8, 2012 (edited) That all very well and good but like I say verifying doubles the burn time so that isn't really an option for most people who burn a lot of discs every day. Instead I will just test the last disc plays in a Bluray player from every batch I burn. The log file only shows logs from 4th July onwards. Why doesn't it show logs from further back? Also it doesn't seem to log anything until you close the program. Also I've just got half-way burning a Bluray and it failed for no reason. I set the max write speed to 4x to match the 4x supported by the disc. Why did the write fail? Here's the log: I 19:55:42 Operation Started! I 19:55:42 Source File: H:\WWE Raw 1996 97 99 Bluray ISOs\Raw 1997\Raw 1997 Disc 6 - July 28 to September 5.iso I 19:55:42 Source File Sectors: 12,212,576 (MODE1/2048) I 19:55:42 Source File Size: 25,011,355,648 bytes I 19:55:42 Source File Volume Identifier: Raw 1997 Disc 6 - July 28 to September 5 I 19:55:42 Source File Volume Set Identifier: 4049AC3400BA5810 I 19:55:42 Source File Application Identifier: ImgBurn v2.5.5.0 I 19:55:42 Source File Implementation Identifier: ImgBurn I 19:55:42 Source File File System(s): UDF (2.50) I 19:55:42 Destination Device: [2:1:0] HL-DT-ST BD-RE BH10LS38 1.00 (F:) (RAID) I 19:55:42 Destination Media Type: BD-R (Disc ID: PHILIP-R04-000) (Speeds: 2x, 4x, 6x, 8x) I 19:55:42 Destination Media Sectors: 12,219,392 I 19:55:42 Write Mode: BD I 19:55:42 Write Type: DAO I 19:55:42 Write Speed: 4x I 19:55:42 BD-R Verify Not Required: Yes I 19:55:42 Link Size: Auto I 19:55:42 Lock Volume: Yes I 19:55:42 Test Mode: No I 19:55:42 OPC: No I 19:55:42 BURN-Proof: Enabled I 19:55:42 Write Speed Successfully Set! - Effective: 17,982 KB/s (4x) I 19:55:57 Filling Buffer... (40 MB) I 19:55:59 Writing LeadIn... I 19:56:00 Writing Session 1 of 1... (1 Track, LBA: 0 - 12212575) I 19:56:00 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 12212575) W 19:59:24 Waiting for buffers to recover... (LBA: 1700352) W 19:59:40 Waiting for hard disk activity to reach threshold level... I 20:00:39 Writing Sectors... W 20:01:07 Waiting for buffers to recover... (LBA: 1849568) W 20:01:11 Waiting for hard disk activity to reach threshold level... I 20:01:12 Writing Sectors... W 20:02:34 Waiting for buffers to recover... (LBA: 2418592) W 20:03:34 Waiting for hard disk activity to reach threshold level... I 20:05:36 Writing Sectors... W 20:05:37 Failed to Write Sectors 2418624 - 2418655 - Reason: Invalid Address For Write W 20:05:37 Retrying (1 of 20)... W 20:05:37 Retry Failed - Reason: Invalid Address For Write W 20:05:37 Retrying (2 of 20)... W 20:05:37 Retry Failed - Reason: Invalid Address For Write W 20:05:37 Retrying (3 of 20)... W 20:05:37 Retry Failed - Reason: Invalid Address For Write W 20:05:37 Retrying (4 of 20)... W 20:05:37 Retry Failed - Reason: Invalid Address For Write W 20:05:37 Retrying (5 of 20)... W 20:05:37 Retry Failed - Reason: Invalid Address For Write W 20:05:37 Retrying (6 of 20)... W 20:05:37 Retry Failed - Reason: Invalid Address For Write W 20:05:37 Retrying (7 of 20)... W 20:05:37 Retry Failed - Reason: Invalid Address For Write W 20:05:37 Retrying (8 of 20)... W 20:05:37 Retry Failed - Reason: Invalid Address For Write W 20:05:37 Retrying (9 of 20)... W 20:05:37 Retry Failed - Reason: Invalid Address For Write W 20:05:38 Retrying (10 of 20)... W 20:05:38 Retry Failed - Reason: Invalid Address For Write W 20:05:38 Retrying (11 of 20)... W 20:05:38 Retry Failed - Reason: Invalid Address For Write W 20:05:38 Retrying (12 of 20)... W 20:05:38 Retry Failed - Reason: Invalid Address For Write W 20:05:38 Retrying (13 of 20)... W 20:05:38 Retry Failed - Reason: Invalid Address For Write W 20:05:38 Retrying (14 of 20)... W 20:05:38 Retry Failed - Reason: Invalid Address For Write W 20:05:38 Retrying (15 of 20)... W 20:05:38 Retry Failed - Reason: Invalid Address For Write W 20:05:38 Retrying (16 of 20)... W 20:05:38 Retry Failed - Reason: Invalid Address For Write W 20:05:38 Retrying (17 of 20)... W 20:05:38 Retry Failed - Reason: Invalid Address For Write W 20:05:38 Retrying (18 of 20)... W 20:05:38 Retry Failed - Reason: Invalid Address For Write W 20:05:38 Retrying (19 of 20)... W 20:05:38 Retry Failed - Reason: Invalid Address For Write W 20:05:38 Retrying (20 of 20)... W 20:05:38 Retry Failed - Reason: Invalid Address For Write W 20:05:46 Retrying (21)... W 20:05:46 Retry Failed - Reason: Invalid Address For Write W 20:05:47 Retrying (22)... W 20:05:47 Retry Failed - Reason: Invalid Address For Write W 20:05:47 Retrying (23)... W 20:05:47 Retry Failed - Reason: Invalid Address For Write W 20:05:48 Retrying (24)... W 20:05:48 Retry Failed - Reason: Invalid Address For Write W 20:05:49 Retrying (25)... W 20:05:49 Retry Failed - Reason: Invalid Address For Write E 20:05:54 Failed to Write Sectors 2418624 - 2418655 - Reason: Invalid Address For Write E 20:05:54 Next Writable Address: 2418592 I 20:05:54 Synchronising Cache... W 20:05:56 User opted to skip the 'Close Track/Session/Disc' functions. E 20:05:56 Failed to Write Image! I 20:05:56 Exporting Graph Data... I 20:05:56 Graph Data File: C:\Users\Dave\AppData\Roaming\ImgBurn\Graph Data Files\HL-DT-ST_BD-RE_BH10LS38_1.00_08-JULY-2012_19-55_PHILIP-R04-000_4x.ibg I 20:05:56 Export Successfully Completed! E 20:05:56 Operation Failed! - Duration: 00:10:13 I 20:05:56 Average Write Rate: 8,157 KB/s (1.8x) - Maximum Write Rate: 18,276 KB/s (4.1x) Edited July 8, 2012 by holygamer Link to comment Share on other sites More sharing options...
LIGHTNING UK! Posted July 8, 2012 Share Posted July 8, 2012 The program saves the contents of the log window (and all the program settings) when it's closed. It limits the length of the single log to something like 5000 lines. If you burn loads of discs, I guess you'd soon work your way through those 5000 and it would be overwriting new stuff with even newer stuff. I don't know why it failed, your drive just errored out during the burn. It doesn't look like you've got the current version of ImgBurn installed - 2.5.7.0 so please install that. You should also update the firmware on your drive to the current version. http://www.firmwarehq.com/LG/BH10LS38/files.html Link to comment Share on other sites More sharing options...
Recommended Posts