pevans360 Posted March 3, 2011 Share Posted March 3, 2011 Have read a bunch of other posts related to this message and tried several suggestions there ... updated the firmware, tried setting different write speeds ... no joy. The blu-ray burner is new and am using Verbatim BD-R DL media. Used ImgBurn in Build mode to copy about a gig of data to the disc. Worked fine. Went to copy some more files and ... get the 'Disc not empty' message and the copy icon is disabled. Tried creating an image from the files with the idea that maybe the image file could be written, but no. If I put in a perfectly clean disc, the icon is enabled. But the point is, I have a 50G disc with 1G of data on it ... and can't figure out how to write anything else to it. I gather from previous posts that 'Status: Complete' means something like the burner thinks the disc is full or no longer writable. Don't understand why that should be. Thanks in advance. PIONEER BD-RW BDR-206 1.05 (SCSI) Current Profile: BD-R Disc Information: Status: Complete State of Last Session: Complete Erasable: No Sessions: 1 Sectors: 535,424 Size: 1,096,548,352 bytes Time: 119:00:74 (MM:SS:FF) Supported Write Speeds: 2x, 4x, 6x, 8x TOC Information: Session 1... (LBA: 0) -> Track 01 (Mode 1, LBA: 0 - 535423) -> LeadOut (LBA: 535424) Disc Definition Structure: Certified: No Scanned: No Manufacturers Name: PIONEER Additional ID: BD-RW BDR-206 Serial Number: JHDP003087WL BD Disc Information (L0): Disc ID: VERBAT-IMf-000 Disc Type: BD-R Disc Size: 120mm Disc Class: 0 Disc Version: 1 Number of Layers: 2 Layer Type: Writable DVD Layer Present: No CD Layer Present: No Channel Bit Length: 74.5nm (25GB Per Layer) Push-Pull Polarity: Positive Recorded Mark Polarity: HTL BCA Present: Yes Maximum Transfer Rate: Not Specified First PAA of Data Zone: 131,072 Last PAA of Data Zone: 1,658,494 BD Disc Information (L1): Disc ID: VERBAT-IMf-000 Disc Type: BD-R Disc Size: 120mm Disc Class: 0 Disc Version: 1 Number of Layers: 2 Layer Type: Writable DVD Layer Present: No CD Layer Present: No Channel Bit Length: 74.5nm (25GB Per Layer) Push-Pull Polarity: Positive Recorded Mark Polarity: HTL BCA Present: Yes Maximum Transfer Rate: Not Specified First PAA of Data Zone: 2,535,808 Last PAA of Data Zone: 4,063,230 Layer Information: Layer 0 Sectors: 12,219,392 (2282%) Layer 1 Sectors: 4,283,283,328 (-2182%) Performance (Write Speed): Descriptor 1... -> B0: 0x00, B1: 0x00, B2: 0x00, B3: 0x00 -> EL: 24438783 (0x0174E7FF) -> RS: 8,990 KB/s (2x) - WS: 8,990 KB/s (2x) Descriptor 2... -> B0: 0x00, B1: 0x00, B2: 0x00, B3: 0x00 -> EL: 24438783 (0x0174E7FF) -> RS: 17,980 KB/s (4x) - WS: 17,980 KB/s (4x) Descriptor 3... -> B0: 0x00, B1: 0x00, B2: 0x00, B3: 0x00 -> EL: 24438783 (0x0174E7FF) -> RS: 26,970 KB/s (6x) - WS: 26,970 KB/s (6x) Descriptor 4... -> B0: 0x00, B1: 0x00, B2: 0x00, B3: 0x00 -> EL: 24438783 (0x0174E7FF) -> RS: 35,960 KB/s (8x) - WS: 35,960 KB/s (8x) I 17:09:58 ImgBurn Version 2.5.5.0 started! I 17:09:58 Microsoft Windows XP Professional (5.1, Build 2600 : Service Pack 3) I 17:09:58 Total Physical Memory: 3,405,208 KB - Available: 1,566,816 KB W 17:09:58 Duplex Secure's SPTD driver can have a detrimental effect on drive performance. I 17:09:58 Initialising SPTI... I 17:09:58 Searching for SCSI / ATAPI devices... I 17:09:58 -> Drive 1 - Info: PIONEER BD-RW BDR-206 1.05 (D:) (SCSI) I 17:09:58 Found 1 BD-RE! I 17:12:52 Operation Started! I 17:12:52 Building Image Tree... I 17:13:16 Calculating Totals... I 17:13:16 Preparing Image... I 17:13:17 Contents: 263 Files, 22 Folders I 17:13:17 Content Type: Data I 17:13:17 Data Type: MODE1/2048 I 17:13:17 File System(s): UDF (1.02) I 17:13:17 Volume Label: MSSQL.1 I 17:13:17 Size: 20,770,772,619 bytes I 17:13:17 Sectors: 10,142,081 I 17:13:17 Image Size: 20,772,159,488 bytes I 17:13:17 Image Sectors: 10,142,656 I 17:13:21 Operation Successfully Completed! - Duration: 00:00:29 I 17:13:21 Operation Started! I 17:13:21 Image Contents: 263 Files, 22 Folders I 17:13:21 Image Sectors: 10,142,656 (MODE1/2048) I 17:13:21 Image Size: 20,772,159,488 bytes I 17:13:21 Image Volume Identifier: MSSQL.1 I 17:13:21 Image Volume Set Identifier: 3E63899A009AC3BF I 17:13:21 Image Application Identifier: ImgBurn v2.5.5.0 I 17:13:21 Image Implementation Identifier: ImgBurn I 17:13:21 Image File System(s): UDF (1.02) I 17:13:21 Destination File: c:\temp\dbImage_20110303.iso I 17:13:21 Destination Free Space: 140,296,523,776 Bytes (137,008,324 KB) (133,797 MB) (130 GB) I 17:13:21 Destination File System: NTFS I 17:13:21 File Splitting: Auto I 17:13:21 Writing Image... W 17:22:32 Failed to open file: 'H:\MSSQL.1\MSSQL\Data\ReportServer.mdf' W 17:22:32 Reason: The process cannot access the file because it is being used by another process. W 17:22:33 Failed to open file: 'H:\MSSQL.1\MSSQL\Data\ReportServer_log.LDF' W 17:22:33 Reason: The process cannot access the file because it is being used by another process. W 17:22:35 Failed to open file: 'H:\MSSQL.1\MSSQL\Data\ReportServerTempDB.mdf' W 17:22:35 Reason: The process cannot access the file because it is being used by another process. W 17:22:36 Failed to open file: 'H:\MSSQL.1\MSSQL\Data\ReportServerTempDB_log.LDF' W 17:22:36 Reason: The process cannot access the file because it is being used by another process. I 17:22:40 Operation Successfully Completed! - Duration: 00:09:18 I 17:22:40 Average Write Rate: 36,353 KB/s (8.1x) - Maximum Write Rate: 107,808 KB/s (24.0x) Link to comment Share on other sites More sharing options...
Rincewind Posted March 4, 2011 Share Posted March 4, 2011 (edited) If you wrote it on a BD-R and not BD-RE then yea it is wasted since imgburn finalized your disc. Edited March 4, 2011 by Rincewind Link to comment Share on other sites More sharing options...
pevans360 Posted March 4, 2011 Author Share Posted March 4, 2011 Thanks for the quick response. Rookie mistake. Lesson learned. Link to comment Share on other sites More sharing options...
pevans360 Posted March 4, 2011 Author Share Posted March 4, 2011 This does bring up a couple of questions / suggestions. I seem to remember working with some burning software a long time ago where the process of 'finalizing' the disc was separate from writing to it. As I recall, you could write to it multiple times. When you exited or ejected the disc, you got the option to finalize. If you chose not to, you could write to it in the future, but ... other software would not be able to read it. So, is it possible / appropriate to make finalization a separate, optional step? Second, if someone is trying to write to a finalized disc, is it possible to display a message saying this instead of the 'Disc not empty' message? Thanks again. Link to comment Share on other sites More sharing options...
Recommended Posts