Jump to content

Recommended Posts

Posted

Hello all,

from a modest 727MB disc I'm getting an ISO file a little in excess of 33GB.  I assume it must have something to do with the missing sectors, but is there a workround?

 

Thanks in advance.

 

I 16:29:20 ImgBurn Version 2.5.8.0 started!
I 16:29:20 Microsoft Windows 7 Professional x64 Edition (6.1, Build 7601 : Service Pack 1)
I 16:29:20 Total Physical Memory: 16,661,040 KiB  -  Available: 12,547,184 KiB
I 16:29:20 Initialising SPTI...
I 16:29:20 Searching for SCSI / ATAPI devices...
I 16:29:21 -> Drive 1 - Info: PLDS DVD+-RW DH-16ABS PD11 (D:) (ATAPI)
I 16:29:21 Found 1 DVD±RW/RAM!
I 16:31:22 Operation Started!
I 16:31:22 Source Device: [0:1:0] PLDS DVD+-RW DH-16ABS PD11 (D:) (ATAPI)
I 16:31:22 Source Media Type: DVD-R (Book Type: DVD-ROM) (Disc ID: MCC 03RG20)
I 16:31:22 Source Media Supported Read Speeds: 2x, 4x, 6x, 8x, 12x, 16x
I 16:31:22 Source Media Sectors: 355,152 (Track Path: PTP)
I 16:31:22 Source Media Size: 727,351,296 bytes
I 16:31:22 Source Media File System(s): None
I 16:31:22 Read Speed (Data/Audio): MAX / 8x
I 16:31:22 Destination File: C:\CD-burns\Image.iso
I 16:31:22 Destination Free Space: 385,281,118,208 Bytes (376,251,092.00 KiB) (367,432.71 MiB) (358.82 GiB)
I 16:31:22 Destination File System: NTFS
I 16:31:22 File Splitting: Auto
I 16:31:23 Read Speed - Effective: 6.4x - 16x
I 16:31:24 Reading Session 1 of 1... (1 Track, LBA: 16580608 - 16935759)
I 16:31:24 Reading Track 1 of 1... (MODE1/2048, LBA: 16580608 - 16935759)
W 16:31:25 Failed to Read Sectors 16580608 - 16580639 - Reason: Logical Block Address out of Range
W 16:36:02 Found end of Disc! - Sector: 16580608
I 16:36:03 Exporting Graph Data...
I 16:36:04 Graph Data File: C:\Users\agh\AppData\Roaming\ImgBurn\Graph Data Files\PLDS_DVD+-RW_DH-16ABS_PD11_21-DECEMBER-2015_16-31_MCC_03RG20.ibg
I 16:36:04 Export Successfully Completed!
I 16:36:04 Operation Successfully Completed! - Duration: 00:04:40
I 16:36:04 Average Read Rate: 2,536 KiB/s (1.9x) - Maximum Read Rate: 2,536 KiB/s (1.9x)
 
The export folder has two files:
 
image.iso 33,161,214 KB 
image.mds 5KB
Posted

As requested:

 

PLDS DVD+-RW DH-16ABS PD11 (ATAPI)
Current Profile: DVD-R
 
Disc Information:
Status: Complete
State of Last Session: Complete
Erasable: No
Sessions: 1
Sectors: 355,152
Size: 727,351,296 bytes
Time: 78:57:27 (MM:SS:FF)
MID: MCC 03RG20
Supported Read Speeds: 2x, 4x, 6x, 8x, 12x, 16x
Current Read Speed: 2.4x - 6x
 
TOC Information:
Session 1... (LBA: 0)
-> Track 01  (Mode 1, LBA: 0 - 355151)
-> LeadOut  (LBA: 355152)
 
Track Information:
Session 1...
-> Track 01 (LTSA: 16580608, LTS: 355152, LRA: 0)
 
Pre-recorded Information:
Manufacturer ID: MCC 03RG20
 
Physical Format Information (Last Recorded):
Book Type: DVD-ROM
Part Version: 0
Disc Size: 120 mm
Maximum Read Rate: 2.52 Mbps
Number of Layers: 1
Track Path: Parallel Track Path (PTP)
Linear Density: 0.267 um/bit
Track Density: 0.74 um/track
First Physical Sector of Data Area: 0
Last Physical Sector of Data Area: 0
Last Physical Sector in Layer 0: 0
Posted

ImgBurn uses the 'Track Information' reported by the drive for these things and yours claims the 'Logical Track Start Address' (LTSA) is 16580608 rather than 0.

 

If you have access to another drive, try reading the disc in that instead.

 

If you have a Dell machine, this firmware update may fix the issue.

 

http://www.dell.com/support/home/us/en/19/Drivers/DriversDetails?driverId=R211597

Posted

Thanks for the prompt replies and assistance. For the record that Dell firmware update is specific to the DH-16A6S drive and I couldn't Google a reputable source of firmware for the DH-16ABS, so I've worked my way round some of the other PCs in the office and struck lucky third time round using a HP laptop.

Posted

You could try ImgBurn's firmware update check feature.  I can't test to make sure right now as I'm formatting a BD-RE DL so it will take about 90 minutes and the drive is locked so I can't check.  I believe you right click on the drive in the drop down list for target drives and there should be a check for firmware updates option there.  LUK can be more specific if you haven't tried this feature yet.  :)

 

 

Turns out my memory was right.  It's the last option in the list.

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 account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

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