Jump to content

itm

Members
  • Posts

    14
  • Joined

  • Last visited

Posts posted by itm

  1. I've been burning backups to 25GB BD-R's using ImgBurn for a number of years. I've just tried to recover files from some of the discs (burned about 5 years ago), and there are a batch of about 10 discs which can't be read at all - they are all TDK blue label discs. When I insert any of the discs into the drive I get "The Device is not ready".

    I guess that this was a bad batch of discs, but was wondering whether there were any utilities (for Windows 10) which might be able to recover any of the data from these discs?

  2. TBH I can't remember if they're DVD-R or DVD+R, just that they are DL. I guess ImgBurn must be reporting them correctly if it says that they're DVD+R?

    I use BD-RE's most of the time now, so it's not really worth investing in another batch of dual-layer DVD's - particularly as I have a shedload of blank single-layer DVD-R, DVD+R and DVD-RW discs in my cupboard. It's a shame that it's the DL discs that are failing, as I only had a few of them left (even fewer now that the last 3 are coasters).

  3. Ah OK I didn't realise that. 

    So I've just successfully burned a 4.7GB DVD-RW, which suggests that the CD/DVD laser is OK?

    I've just tried reading some of the DVD-R's from this batch that were burned about 7-8 years ago and they're still fine. It's odd that the rest of the batch suddenly can't be written to.

  4. Yes I did wonder about the shelf life of the discs. In the past a spindle of 50 of these discs would last me a few years, but these days I'm mainly burning to BD-RE discs so the DVD-R's have been lying around for longer than usual. They've been kept in a warm dry place so I was hoping they'd still be OK.

    I've just managed to burn a 25GB BD-RE using the same drive, so the hardware seems to be OK.

  5. I am using ImgBurn 2.5.8.0 to burn files and folders to a dual-layer DVD-R disc, from a batch of blank discs that I have used before successfully. I'm getting these errors after about 15 minutes:

    I/O Error!
    
    Device: [0:0:0] HL-DT-ST BD-RE  BH10LS30 1.02 (E:) (SATA)
    
    ScsiStatus: 0x02
    Interpretation: Check Condition
    
    CDB: 2A 00 00 19 6F E0 00 00 20 00
    Interpretation: Write (10) - Sectors: 1667040 - 1667071
    
    Sense Area: 70 00 04 00 00 00 00 0A 35 01 04 3E 09 01 00 00 00 00
    SK Interpretation: Hardware Error
    ASC/ASCQ Interpretation: Tracking Servo Failure

    The size of the project was reported as follows immediately prior to burning:

    File System(s): UDF (1.02)
    Volume Label: Backup_671
    
    Size: 8,329,678,885 bytes
    Sectors: 4,068,760
    
    Image Size: 8,339,881,984 bytes
    Image Sectors: 4,072,208

    The UI reports the project as 7.76GiB, 7.76GiB Used, 200MiB (205,387 KiB) Free, and I get no warning about the disc being too small to accommodate the data.

    I've tried this 4 times now, with discs from the same batch, and got errors every time. The latest log is below. For some reason it reports that Drive I: (which is neither the source or destination device - it's my Google Drive mapping) does not support single files > 4GB, but as it's a warning I guess it's not relevant to the problem. It also reports the O/S as Windows 8 Professional, even though I'm running Windows 10 Pro (???).

    Any idea what the problem might be?

    I 12:16:54 ImgBurn Version 2.5.8.0 started!
    I 12:16:54 Microsoft Windows 8 Professional x64 Edition (6.2, Build 9200)
    I 12:16:54 Total Physical Memory: 33,495,920 KiB  -  Available: 18,490,800 KiB
    W 12:16:54 Drive I:\ (FAT32) does not support single files > 4 GiB in size.
    I 12:16:54 Initialising SPTI...
    I 12:16:54 Searching for SCSI / ATAPI devices...
    I 12:16:54 -> Drive 1 - Info: HL-DT-ST BD-RE  BH10LS30 1.02-A0 (E:) (SATA)
    I 12:16:54 Found 1 BD-RE!
    I 12:18:25 Project Successfully Loaded!
    I 12:18:25 File Name: C:\Users\itm\AppData\Roaming\ImgBurn\Project Files\My Project.ibb
    I 12:19:21 Operation Started!
    I 12:19:21 Building Image Tree...
    I 12:19:34 Calculating Totals...
    I 12:19:34 Preparing Image...
    I 12:19:35 Contents: 2,819 Files, 129 Folders
    I 12:19:35 Content Type: Data
    I 12:19:35 Data Type: MODE1/2048
    I 12:19:35 File System(s): UDF (1.02)
    I 12:19:35 Volume Label: Warez_671
    I 12:19:35 Size: 8,329,678,885 bytes
    I 12:19:35 Sectors: 4,068,760
    I 12:19:35 Image Size: 8,339,881,984 bytes
    I 12:19:35 Image Sectors: 4,072,208
    I 12:19:48 Operation Successfully Completed! - Duration: 00:00:27
    I 12:19:48 Operation Started!
    I 12:19:48 Source File: -==/\/[BUILD IMAGE]\/\==-
    I 12:19:48 Source File Sectors: 4,072,208 (MODE1/2048)
    I 12:19:48 Source File Size: 8,339,881,984 bytes
    I 12:19:48 Source File Volume Identifier: Warez_671
    I 12:19:48 Source File Volume Set Identifier: 5387626A003E230C
    I 12:19:48 Source File Application Identifier: ImgBurn v2.5.8.0
    I 12:19:48 Source File Implementation Identifier: ImgBurn
    I 12:19:48 Source File File System(s): UDF (1.02)
    I 12:19:48 Destination Device: [0:0:0] HL-DT-ST BD-RE  BH10LS30 1.02 (E:) (SATA)
    I 12:19:48 Destination Media Type: DVD+R DL (Disc ID: RICOHJPN-D01-67)
    I 12:19:48 Destination Media Supported Write Speeds: 4x, 8x
    I 12:19:48 Destination Media Sectors: 4,072,224
    I 12:19:48 Destination Media L0 Data Zone Capacity: 2,036,112 (Changeable: No)
    I 12:19:48 Write Mode: DVD
    I 12:19:48 Write Type: DAO
    I 12:19:48 Write Speed: MAX
    I 12:19:48 DVD+R DL Reserve Track: No
    I 12:19:48 Link Size: Auto
    I 12:19:48 Lock Volume: Yes
    I 12:19:48 Test Mode: No
    I 12:19:48 OPC: No
    I 12:19:48 BURN-Proof: Enabled
    W 12:19:48 Write Speed Miscompare! - MODE SENSE: 11,080 KB/s (8x), GET PERFORMANCE: 5,939 KB/s (4.3x)
    I 12:19:48 Write Speed Successfully Set! - Effective: 5,939 KB/s (4.3x)
    I 12:19:48 Book Type Setting: DVD-ROM
    I 12:19:48 Optimal L0 Data Zone Capacity: 2,036,112
    I 12:19:48 Optimal L0 Data Zone Method: ECC Block Boundary
    I 12:19:48 Set L0 Data Zone Capacity Succeeded!
    I 12:19:48 L0 Data Zone Capacity - Effective: 2,036,112
    I 12:19:50 Filling Buffer... (80 MiB)
    I 12:19:51 Writing LeadIn...
    I 12:19:52 Writing Session 1 of 1... (1 Track, LBA: 0 - 4072207)
    I 12:19:52 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 4072207)
    I 12:19:52 Writing Layer 0... (LBA: 0 - 2036111)
    W 12:30:19 Failed to Write Sectors 1667040 - 1667071 - Reason: Tracking Servo Failure
    W 12:30:19 Retrying (1 of 20)...
    W 12:30:19 Retry Failed - Reason: Tracking Servo Failure
    W 12:30:19 Retrying (2 of 20)...
    W 12:30:19 Retry Failed - Reason: Invalid Address For Write
    W 12:30:19 Retrying (3 of 20)...
    W 12:30:19 Retry Failed - Reason: Invalid Address For Write
    W 12:30:19 Retrying (4 of 20)...
    W 12:30:19 Retry Failed - Reason: Invalid Address For Write
    W 12:30:19 Retrying (5 of 20)...
    W 12:30:19 Retry Failed - Reason: Invalid Address For Write
    W 12:30:19 Retrying (6 of 20)...
    W 12:30:19 Retry Failed - Reason: Invalid Address For Write
    W 12:30:19 Retrying (7 of 20)...
    W 12:30:19 Retry Failed - Reason: Invalid Address For Write
    W 12:30:19 Retrying (8 of 20)...
    W 12:30:19 Retry Failed - Reason: Invalid Address For Write
    W 12:30:19 Retrying (9 of 20)...
    W 12:30:19 Retry Failed - Reason: Invalid Address For Write
    W 12:30:19 Retrying (10 of 20)...
    W 12:30:19 Retry Failed - Reason: Invalid Address For Write
    W 12:30:19 Retrying (11 of 20)...
    W 12:30:19 Retry Failed - Reason: Invalid Address For Write
    W 12:30:19 Retrying (12 of 20)...
    W 12:30:19 Retry Failed - Reason: Invalid Address For Write
    W 12:30:19 Retrying (13 of 20)...
    W 12:30:19 Retry Failed - Reason: Invalid Address For Write
    W 12:30:19 Retrying (14 of 20)...
    W 12:30:19 Retry Failed - Reason: Invalid Address For Write
    W 12:30:19 Retrying (15 of 20)...
    W 12:30:19 Retry Failed - Reason: Invalid Address For Write
    W 12:30:19 Retrying (16 of 20)...
    W 12:30:19 Retry Failed - Reason: Invalid Address For Write
    W 12:30:19 Retrying (17 of 20)...
    W 12:30:19 Retry Failed - Reason: Invalid Address For Write
    W 12:30:19 Retrying (18 of 20)...
    W 12:30:19 Retry Failed - Reason: Invalid Address For Write
    W 12:30:19 Retrying (19 of 20)...
    W 12:30:19 Retry Failed - Reason: Invalid Address For Write
    W 12:30:19 Retrying (20 of 20)...
    W 12:30:19 Retry Failed - Reason: Invalid Address For Write
    E 12:34:59 Failed to Write Sectors 1667040 - 1667071 - Reason: Tracking Servo Failure
    E 12:34:59 Next Writable Address: 1665792
    I 12:34:59 Synchronising Cache...
    W 12:35:03 User opted to skip the 'Close Track/Session/Disc' functions.
    E 12:35:03 Failed to Write Image!
    I 12:35:03 Exporting Graph Data...
    I 12:35:03 Graph Data File: C:\Users\itm\AppData\Roaming\ImgBurn\Graph Data Files\HL-DT-ST_BD-RE_BH10LS30_1.02_07-DECEMBER-2021_12-19_RICOHJPN-D01-67_MAX.ibg
    I 12:35:03 Export Successfully Completed!
    E 12:35:03 Operation Failed! - Duration: 00:15:14
    I 12:35:03 Average Write Rate: 3,680 KiB/s (2.7x) - Maximum Write Rate: 5,442 KiB/s (4.0x)


     

  6. To summarise...I was trying to write 4 files (large .exe files) to a 7GB DVD-R, from a half empty tub that I hadn't used for a few years. The first couple of burns failed, at which point I suspected that maybe the media had degraded while sat on the shelf (I had noticed some moisture on the discs which I needed to wipe off - I suspect this dated back to a leak in my study over a year ago). When the third burn failed I decided that I should try an alternative media, in case there was in fact a problem with the drive or software. So I tried burning the same files to a 4GB DVD-RW (forgetting that it had half the capacity of the DVD-R's). When I got the warning message about the capacity I tried again, but only burning two of the four files, so that they would fit on the disc. I got the same error that I had with the DVD-R's. At that point I posted my message here.

  7. OK so I followed dbminter's instructions to update the drive firmware, then rebooted. After the reboot everything was fine  -thanks!

    I've been using the same DV-R/W media for 5+ years without any problems (am actually using discs from the same pack that I bought 5 years ago), so it didn't seem like a media compatibility issue. 

    ???

  8. This was the last entry from the log:

    I 18:30:40 Operation Started!
    I 18:30:40 Building Image Tree...
    I 18:30:46 Calculating Totals...
    I 18:30:46 Preparing Image...
    I 18:30:46 Contents: 4 Files, 1 Folder
    I 18:30:46 Content Type: Data
    I 18:30:46 Data Type: MODE1/2048
    I 18:30:46 File System(s): UDF (1.02)
    I 18:30:46 Volume Label: Realtracks & Realdrums5
    I 18:30:46 Size: 6,556,174,779 bytes
    I 18:30:46 Sectors: 3,201,259
    I 18:30:46 Image Size: 6,556,745,728 bytes
    I 18:30:46 Image Sectors: 3,201,536
    I 18:30:47 Operation Successfully Completed! - Duration: 00:00:07
    W 18:30:49 User accepted disc space warning and is attempting to overburn!
    I 18:30:49 Operation Started!
    I 18:30:49 Source File: -==/\/[BUILD IMAGE]\/\==-
    I 18:30:49 Source File Sectors: 3,201,536 (MODE1/2048)
    I 18:30:49 Source File Size: 6,556,745,728 bytes
    I 18:30:49 Source File Volume Identifier: Realtracks & Realdrums5
    I 18:30:49 Source File Volume Set Identifier: 509E93D40030D9F6
    I 18:30:49 Source File Application Identifier: ImgBurn v2.5.8.0
    I 18:30:49 Source File Implementation Identifier: ImgBurn
    I 18:30:49 Source File File System(s): UDF (1.02)
    I 18:30:49 Destination Device: [0:0:0] HL-DT-ST BD-RE  BH10LS30 1.00 (E:) (SATA)
    I 18:30:49 Destination Media Type: DVD-RW (Disc ID: TDK502sakuM3)
    I 18:30:49 Destination Media Supported Write Speeds: 2x
    I 18:30:49 Destination Media Sectors: 2,298,496
    I 18:30:49 Write Mode: DVD
    I 18:30:49 Write Type: DAO
    I 18:30:49 Write Speed: MAX
    I 18:30:49 Link Size: Auto
    I 18:30:49 Lock Volume: Yes
    I 18:30:49 Test Mode: No
    I 18:30:49 OPC: No
    I 18:30:49 BURN-Proof: Enabled
    I 18:30:49 Write Speed Successfully Set! - Effective: 2,770 KB/s (2x)
    E 18:31:00 Failed to Reserve Track! - Reason: Invalid Field in CDB
    E 18:31:02 Operation Failed! - Duration: 00:00:12
    I 18:31:02 Average Write Rate: N/A - Maximum Write Rate: N/A
    I 18:31:25 Close Request Acknowledged
    I 18:31:25 Closing Down...
    I 18:31:26 Shutting down SPTI...
    I 18:31:26 ImgBurn closed!

     

  9. I am using ImgBurn 2.5.8.0 on Windows 10, attempting to burn 4 .exe files in a folder to a 7GB DVD-R. A number of attempts have now failed with the error below. The files vary in size from 1.5GB to 1.9GB.

    Any idea why I am getting this error?

    I/O Error!

    Device: [0:0:0] HL-DT-ST BD-RE  BH10LS30 1.00 (E:) (SATA)

    ScsiStatus: 0x02
    Interpretation: Check Condition

    CDB: 53 00 00 00 00 00 30 DA 00 00
    Interpretation: Reserve Track - Sectors: 3,201,536

    Sense Area: 70 00 05 00 00 00 00 0A 53 00 00 0D 24 00 00 C0 00 05
    SK Interpretation: Illegal Request
    ASC/ASCQ Interpretation: Invalid Field in CDB
     

  10. I was burning a 25GB BD-R using Imgburn 2.5.80 (on Windows 10 Pro). I accidentally happened upon a keystroke which seems to have paused the disc burning process. The progress window has gone, the BD-RW drive is no longer being accessed, and the green bar at the bottom of the Disk Layout Editor has a white highlight scrolling across it repeatedly. To the right of the green bar it says 99% (I suspect that is the % full figure for the disc, rather than the progress of the burn?).

    Can anyone advise on how I can resume and complete the burning process?

×
×
  • Create New...

Important Information

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