burning issues.... [unresolved and moving on]

[CPUnltd]

over the last week, I have had the strangest issue I have ever seen...

I have used multiple burners on my system (grafburn, k3b, brasero won't start up, graveman and turbojet) and for some unexplainable reason, the burn goes through fine, but the disk has a blank burn on it... there is NEVER any actual retrievable data on these disks... This is a real pain, as I need to burn info for people and I just can't with this issue... how do I figure out wtf is causing this?



I noticed that there isn't a hardware or software issue area on here or the dev forum, so I technically have nowhere to post this question... I hope someone notices it at some point...

[KDulcimer]

Sounds like a hardware error to me. Try a different drive.

[gettinther]

What system are you using?

[Allen]

Run k3b from a terminal and check the output. Check closely the disc properties. I had basically the same problem and it turned out to be defective disks.

[CPUnltd]

Well, if it's defective disks, then I hit a sudden rash of them fro a pack that has been good and lasted me a long time... I doubt it's that, since I tried a cdrw that gave me the same issue and burned to it in a laptop with no problems... firmware issue has been expressed as a possibility, but who knows...

gett, please elaborate on your question.. what do you mean when you ask what system am I using? If you mean OS, I am using pclos currently (built off minime, pre BU) with XP on the system as dual boot (which I haven't logged into in many months) and XP installed on a vm that I use for tesitng websites in IE that I build and occasionally burn or erase disks...

allen: what do I look for in k3b via console? I've never burned with k3b via console, so I wouldn't know what to look for...

[Allen]

I'll post a copy of my console output of an iso burn on K3B. First what you look for is that your device is identified correctly. Second that the disk is correct and third that your drive is locking and unlocking for the burn process. The actual burn stats are in your debugging output. I burned this on a "not too distant" remaster of PCLOS 2009 so it should be fairly close to your system.

[CPUnltd]

this has resulted in the removal of a completely broken burner (separate from the one in quesiton) and replaced with a new one. For now, I will be moving on from this topic, as I need to finish some work and mandvd/manslide are holding me up, so I will focus on fixing them and finishing my web design work before I deal with this issue again... Thanks for the help guys... but for now, I'm putting it on the shelf...

[z3r0_k00l75]

CPUnltd, did you ever find the answer to this problem?? I know its out-of-date by a year, I was just curious.