Dave92F1 Posted December 19, 2020 Posted December 19, 2020 I'm trying to burn a 100 GB M-DISC (BDXL quad layer); I keep getting this error. For sure the file was not open at the time. FWIW, the source is drive G: which is a Google Drive File stream drive. But it wrote the first 36 GB just fine, and when I try to read the offending file, I can copy it just fine (tried copying to the desktop). Advice?? (See screenshot at end of post.) Here's the log: I 12:27:46 Operation Started! I 12:27:46 Source File: -==/\/[BUILD IMAGE]\/\==- I 12:27:46 Source File Sectors: 42,660,832 (MODE1/2048) I 12:27:46 Source File Size: 87,369,383,936 bytes I 12:27:46 Source File Volume Identifier: 2020-12-19C I 12:27:46 Source File Volume Set Identifier: 5193636E028AF3D4 I 12:27:46 Source File Application Identifier: ImgBurn v2.5.8.0 I 12:27:46 Source File Implementation Identifier: ImgBurn I 12:27:46 Source File File System(s): UDF (1.02) I 12:27:46 Destination Device: [0:0:0] PIONEER BD-RW BDR-XD07 1.02 (D:) (USB) I 12:27:46 Destination Media Type: BD-R (Disc ID: VERBAT-IMk-000) I 12:27:46 Destination Media Supported Write Speeds: 2x, 4x I 12:27:46 Destination Media Sectors: 48,878,592 I 12:27:46 Write Mode: BD I 12:27:46 Write Type: DAO I 12:27:46 Write Speed: 2x I 12:27:46 Hardware Defect Management Active: No I 12:27:46 BD-R Verify Not Required: Yes I 12:27:46 Link Size: Auto I 12:27:46 Lock Volume: Yes I 12:27:46 Test Mode: No I 12:27:46 OPC: No I 12:27:46 BURN-Proof: Enabled I 12:27:46 Write Speed Successfully Set! - Effective: 8,990 KB/s (2x) I 12:27:46 Advanced Settings - Optimal Writing Speed: No I 12:27:46 Filling Buffer... (80 MiB) I 12:27:47 Writing LeadIn... I 12:27:58 Writing Session 1 of 1... (1 Track, LBA: 0 - 42660831) I 12:27:58 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 42660831) E 13:36:02 Failed to read from file: 'G:\My Drive\dave_data\Archive\DevTools - Editors and Compilers\Microchip (PIC)\XC32\xc32-v2.10-full-install-windows-installer.exe' E 13:36:02 Reason: Reached EOF! I 15:23:30 Synchronising Cache... W 15:23:34 User opted to skip the 'Close Track/Session/Disc' functions. E 15:23:34 Failed to Write Image! I 15:23:34 Exporting Graph Data... I 15:23:34 Graph Data File: C:\Users\Dave\AppData\Roaming\ImgBurn\Graph Data Files\PIONEER_BD-RW_BDR-XD07_1.02_SATURDAY-DECEMBER-19-2020_12-27_PM_VERBAT-IMk-000_2x.ibg I 15:23:34 Export Successfully Completed! E 15:23:34 Operation Failed! - Duration: 02:55:47 I 15:23:34 Average Write Rate: 3,370 KiB/s (0.8x) - Maximum Write Rate: 8,833 KiB/s (2.0x)
dbminter Posted December 19, 2020 Posted December 19, 2020 My guess is if G: is a Google Drive of some kind, a network hiccup might have prevented reading the file contents properly. Thus a premature EOF was reached, which was unexpected versus the file size the ImgBurn job was expecting and reported by the software. I'm not familiar with Google Drives, but I'm guessing they're some kind of network/online/cloud source. I would try copying the contents from the Google Drive to some temporary non network location, adding those files instead of the Google Drive source, and see if that helps. However, this may not be practical, depending on the size of the source you're attempting to read from the Google Drive.
Dave92F1 Posted December 19, 2020 Author Posted December 19, 2020 @dbminter Maybe, but EOF is not the same as a slow-responding storage device. There are plenty of devices that are just slow (not least optical drive readers). Still, worth a try.
Recommended Posts