Jump to content

I/O errors burning with imgburn


Recommended Posts

Hi there

 

I cannot burn anything with imgburn at the moment CD/DVD/BD it always comes up with a I/O error.

 

I have 2 drives 

 

Liteon 6x BD Burner (not connected) fw YL07

 

Pioneer BDR-206 fw 1.56

 

 

Any help would be much appreciated.

 

Thanks

 

 

 

I 01:09:13 ImgBurn Version 2.5.7.0 started!
I 01:09:13 Microsoft Windows 7 Ultimate x64 Edition (6.1, Build 7601 : Service Pack 1)
I 01:09:13 Total Physical Memory: 6,274,444 KB  -  Available: 4,729,852 KB
I 01:09:13 Initialising SPTI...
I 01:09:13 Searching for SCSI / ATAPI devices...
I 01:09:13 -> Drive 1 - Info: PIONEER BD-RW   BDR-206 1.56 (F:) (ATAPI)
I 01:09:13 Found 1 BD-RE!
I 01:10:14 Operation Started!
I 01:10:14 Building Image Tree...
I 01:10:14 Checking Directory Depth...
I 01:10:14 Calculating Totals...
I 01:10:14 Preparing Image...
I 01:10:15 Checking Path Length...
I 01:10:15 Contents: 1 File, 0 Folders
I 01:10:15 Content Type: Data
I 01:10:15 Data Type: MODE1/2048
I 01:10:15 File System(s): ISO9660, Joliet
I 01:10:15 Volume Label: [Not Configured]
I 01:10:15 Size: 278,694,226 bytes
I 01:10:15 Sectors: 136,082
I 01:10:15 Image Size: 278,757,376 bytes
I 01:10:15 Image Sectors: 136,112
I 01:10:15 Operation Successfully Completed! - Duration: 00:00:00
I 01:16:34 Operation Started!
I 01:16:34 Building Image Tree...
I 01:16:34 Checking Directory Depth...
I 01:16:34 Calculating Totals...
I 01:16:34 Preparing Image...
I 01:16:34 Checking Path Length...
I 01:16:34 Contents: 1 File, 0 Folders
I 01:16:34 Content Type: Data
I 01:16:34 Data Type: MODE1/2048
I 01:16:34 File System(s): ISO9660, Joliet
I 01:16:34 Volume Label: [Not Configured]
I 01:16:34 Size: 278,694,226 bytes
I 01:16:34 Sectors: 136,082
I 01:16:34 Image Size: 278,757,376 bytes
I 01:16:34 Image Sectors: 136,112
I 01:16:34 Operation Successfully Completed! - Duration: 00:00:00
I 01:17:36 Operation Started!
I 01:17:36 Building Image Tree...
I 01:17:53 Checking Directory Depth...
I 01:17:53 Calculating Totals...
I 01:17:53 Preparing Image...
I 01:17:53 Checking Path Length...
I 01:17:53 Contents: 1 File, 0 Folders
I 01:17:53 Content Type: Data
I 01:17:53 Data Type: MODE1/2048
I 01:17:53 File System(s): ISO9660, Joliet
I 01:17:53 Volume Label: TANGLED_EVER_AFT
I 01:17:53 Size: 278,694,226 bytes
I 01:17:53 Sectors: 136,082
I 01:17:53 Image Size: 278,757,376 bytes
I 01:17:53 Image Sectors: 136,112
I 01:17:56 Operation Successfully Completed! - Duration: 00:00:20
I 01:18:00 Operation Started!
I 01:18:00 Source File: -==/\/[bUILD IMAGE]\/\==-
I 01:18:00 Source File Sectors: 136,112 (MODE1/2048)
I 01:18:00 Source File Size: 278,757,376 bytes
I 01:18:00 Source File Volume Identifier: TANGLED_EVER_AFT
I 01:18:00 Source File Volume Set Identifier: UNDEFINED
I 01:18:00 Source File Application Identifier: ImgBurn v2.5.7.0 - The Ultimate Image Burner!
I 01:18:00 Source File Implementation Identifier: ImgBurn v2.5.7.0
I 01:18:00 Source File File System(s): ISO9660, Joliet
I 01:18:00 Destination Device: [0:1:0] PIONEER BD-RW   BDR-206 1.56 (F:) (ATAPI)
I 01:18:00 Destination Media Type: CD-R (Disc ID: 97m27s18f, Plasmon Data Systems)
I 01:18:00 Destination Media Supported Write Speeds: 4x, 10x, 16x, 24x, 32x, 40x
I 01:18:00 Destination Media Sectors: 359,847
I 01:18:00 Write Mode: CD
I 01:18:00 Write Type: SAO
I 01:18:00 Write Speed: MAX
I 01:18:00 Lock Volume: Yes
I 01:18:00 Test Mode: No
I 01:18:01 OPC: No
I 01:18:01 BURN-Proof: Enabled
I 01:18:01 Write Speed Successfully Set! - Effective: 7,056 KB/s (40x)
I 01:18:01 Advanced Settings - Optimal Writing Speed: No
I 01:18:01 Filling Buffer... (80 MB)
I 01:18:02 Writing LeadIn...
W 01:21:04 Failed to Write Sectors 432 - 447 - Reason: The request could not be performed because of an I/O device error.
W 01:21:05 Retrying (1 of 20)...
W 01:21:05 Retry Failed - Reason: Command Sequence Error
W 01:21:05 Retrying (2 of 20)...
W 01:21:05 Retry Failed - Reason: Command Sequence Error
W 01:21:05 Retrying (3 of 20)...
W 01:21:05 Retry Failed - Reason: Command Sequence Error
W 01:21:05 Retrying (4 of 20)...
W 01:21:05 Retry Failed - Reason: Command Sequence Error
W 01:21:05 Retrying (5 of 20)...
W 01:21:05 Retry Failed - Reason: Command Sequence Error
W 01:21:05 Retrying (6 of 20)...
W 01:21:05 Retry Failed - Reason: Command Sequence Error
W 01:21:05 Retrying (7 of 20)...
W 01:21:05 Retry Failed - Reason: Command Sequence Error
W 01:21:05 Retrying (8 of 20)...
W 01:21:05 Retry Failed - Reason: Command Sequence Error
W 01:21:05 Retrying (9 of 20)...
W 01:21:05 Retry Failed - Reason: Command Sequence Error
W 01:21:05 Retrying (10 of 20)...
W 01:21:05 Retry Failed - Reason: Command Sequence Error
W 01:21:05 Retrying (11 of 20)...
W 01:21:05 Retry Failed - Reason: Command Sequence Error
W 01:21:05 Retrying (12 of 20)...
W 01:21:05 Retry Failed - Reason: Command Sequence Error
W 01:21:05 Retrying (13 of 20)...
W 01:21:05 Retry Failed - Reason: Command Sequence Error
W 01:21:05 Retrying (14 of 20)...
W 01:21:05 Retry Failed - Reason: Command Sequence Error
W 01:21:05 Retrying (15 of 20)...
W 01:21:05 Retry Failed - Reason: Command Sequence Error
W 01:21:05 Retrying (16 of 20)...
W 01:21:05 Retry Failed - Reason: Command Sequence Error
W 01:21:05 Retrying (17 of 20)...
W 01:21:05 Retry Failed - Reason: Command Sequence Error
W 01:21:05 Retrying (18 of 20)...
W 01:21:05 Retry Failed - Reason: Command Sequence Error
W 01:21:05 Retrying (19 of 20)...
W 01:21:05 Retry Failed - Reason: Command Sequence Error
W 01:21:05 Retrying (20 of 20)...
W 01:21:05 Retry Failed - Reason: Command Sequence Error
W 01:21:08 Retrying (21)...
W 01:21:08 Retry Failed - Reason: Command Sequence Error
W 01:21:09 Retrying (22)...
W 01:21:09 Retry Failed - Reason: Command Sequence Error
W 01:21:09 Retrying (23)...
W 01:21:09 Retry Failed - Reason: Command Sequence Error
W 01:21:10 Retrying (24)...
W 01:21:10 Retry Failed - Reason: Command Sequence Error
W 01:21:11 Retrying (25)...
W 01:21:11 Retry Failed - Reason: Command Sequence Error
W 01:21:11 Retrying (26)...
W 01:21:11 Retry Failed - Reason: Command Sequence Error
W 01:21:11 Retrying (27)...
W 01:21:11 Retry Failed - Reason: Command Sequence Error
W 01:21:11 Retrying (28)...
W 01:21:11 Retry Failed - Reason: Command Sequence Error
W 01:21:11 Retrying (29)...
W 01:21:11 Retry Failed - Reason: Command Sequence Error
W 01:21:12 Retrying (30)...
W 01:21:12 Retry Failed - Reason: Command Sequence Error
W 01:21:12 Retrying (31)...
W 01:21:12 Retry Failed - Reason: Command Sequence Error
W 01:21:12 Retrying (32)...
W 01:21:12 Retry Failed - Reason: Command Sequence Error
W 01:21:13 Retrying (33)...
W 01:21:13 Retry Failed - Reason: Command Sequence Error
W 01:21:14 Retrying (34)...
W 01:21:14 Retry Failed - Reason: Command Sequence Error
E 01:21:16 Failed to Write Sectors 432 - 447 - Reason: The request could not be performed because of an I/O device error.
I 01:21:16 Synchronising Cache...
W 01:21:22 User opted to skip the 'Close Track/Session/Disc' functions.
E 01:21:22 Failed to Write Image!
E 01:21:22 Operation Failed! - Duration: 00:03:21
I 01:21:22 Average Write Rate: 0 KB/s (0.0x) - Maximum Write Rate: 0 KB/s (0.0x)
 

Edited by deathstar_gamer713
Link to comment
Share on other sites

Hi spinningwheel

 

Thanks I will try cleaning the laser lens, I have two bluray drives with the same problem so I doubt they both have the same problems.

 

 

I do use decent discs for bluray Verbatim bd+r and I use TDK Gold CD-R and Ritek DVD's which seem to be ok although I have read that they are far from the best.

 

Thanks for your reply anyway.

Link to comment
Share on other sites

Hi there

 

I tried cleaning the lens manually in the pioneer and it still does not work

 

PC ITS NOT WORKING ON (WITH CLEAN INSTALL AND MOBO & GRAPHICS DRIVERS)

 

Intel i7 2600k

6gb kingston ram

Nvidia GTX 460

2 X 1TB SAMSUNG HDD IN RAID 128KB STRIPED

1 X PIONEER BDR-206 BD BURNER

1X LG GGW-H20L BD BURNER

 

It has been working fine on this rig for about 2 years or a bit more.

 

However I put both drives in an old pc and they both worked flawlessly

 

pc they do work in

 

AMD e6420 64bit cpu

Nvidia Ge 8600 GTS

4.0gb ram

1WD 200gb IDE hdd

1 Samsung 500gb Sata hdd

??  p5kse motherboard.

 

 

Could a power supply cause I/O errors if it was damaged (although everything else including hdd works perfectly) as I have run this on Modified sinewave inverter power.

 

Could it be I/O issue with motherboard that is causing the problem or a combination that the ps damaged the mb.

 

Thanks any assistance would be great.

Edited by deathstar_gamer713
Link to comment
Share on other sites

×
×
  • Create New...

Important Information

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