generalk
asked on
Internal Target Failure while burning CD-RW
After spending the entire last week comming up with the perfect image for a rescue CD, cdrecord told me this:
status: 0x2 (CHECK CONDITION)
Sense Bytes: F0 00 04 00 03 8B EA 13 00 00 00 00 44 88 00 00
Sense Key: 0x4 Hardware Error, Segment 0
Sense Code: 0x44 Qual 0x88 (internal target failure) [No matching qualifier] Fru 0x0
Sense flags: Blk 232426 (valid)
While there's plenty of info there, the key words seem to be "internal target failure". Research on google tells me that indeed, this error is caused by an "internal target failure".
Does anybody know what exactly an internal target is or why it would fail?
P.S. This 300 points is for telling me what the problem is. 300 more if you can tell me how to fix this without a trip to MircoCenter.
status: 0x2 (CHECK CONDITION)
Sense Bytes: F0 00 04 00 03 8B EA 13 00 00 00 00 44 88 00 00
Sense Key: 0x4 Hardware Error, Segment 0
Sense Code: 0x44 Qual 0x88 (internal target failure) [No matching qualifier] Fru 0x0
Sense flags: Blk 232426 (valid)
While there's plenty of info there, the key words seem to be "internal target failure". Research on google tells me that indeed, this error is caused by an "internal target failure".
Does anybody know what exactly an internal target is or why it would fail?
P.S. This 300 points is for telling me what the problem is. 300 more if you can tell me how to fix this without a trip to MircoCenter.
ASKER
I'm not piping, and I've tried every speed the burner supports.
Here's the strange thing that I've just discovered. I seem to be able to burn images less than 450 MB without a problem, but anything more than that produces the error cited above. Full erasures also fail, while blank=fast works just fine.
It seems the burner can only write the first ~450MB of a disc. Any ideas?
Here's the strange thing that I've just discovered. I seem to be able to burn images less than 450 MB without a problem, but anything more than that produces the error cited above. Full erasures also fail, while blank=fast works just fine.
It seems the burner can only write the first ~450MB of a disc. Any ideas?
swap >= 450MB?
Hi there,
There appears to be several possible causes, the following relates to the actual CD used.
http://archives.real-time.com/pipermail/tclug-list/2002-December/054428.html
then there is this, which looks at the settings
http://www.mail-archive.com/dvdrtools-users@nongnu.org/msg00113.html
There appears to be several possible causes, the following relates to the actual CD used.
http://archives.real-time.com/pipermail/tclug-list/2002-December/054428.html
then there is this, which looks at the settings
http://www.mail-archive.com/dvdrtools-users@nongnu.org/msg00113.html
ASKER
I don't think I understand chicagoan's comment, but this information may be relevant.
gk@gk:~$ cat /proc/swaps
Filename Type Size Used Priority
/dev/hda3 partition 489972 5516 -1
gk@headless ~ $ cat /proc/swaps
Filename Type Size Used Priority
/dev/hda3 partition 1052248 0 -1
In response to the first article posted by philby11, I don't think this is a media problem because I'm using a Phillips 4x CD-RW in a Phillips 4x CD-RW drive. I've also tried Memorex CD-Rs rated at 8x but burning at 2x.
The second link points to a thread where the ultimate resolution was to pass the -V flag to mkisofs. I don't see how this could impact the burning process, and I think that he just got lucky on the third attampt. Never the less, I did change the -volid flag that I had been passing to mkisofs to a -V flag, and for good measure, I added a -V cdrecord as well.
Aside from a torrent of debugging information, the result was the same.
gk@gk:~$ cat /proc/swaps
Filename Type Size Used Priority
/dev/hda3 partition 489972 5516 -1
gk@headless ~ $ cat /proc/swaps
Filename Type Size Used Priority
/dev/hda3 partition 1052248 0 -1
In response to the first article posted by philby11, I don't think this is a media problem because I'm using a Phillips 4x CD-RW in a Phillips 4x CD-RW drive. I've also tried Memorex CD-Rs rated at 8x but burning at 2x.
The second link points to a thread where the ultimate resolution was to pass the -V flag to mkisofs. I don't see how this could impact the burning process, and I think that he just got lucky on the third attampt. Never the less, I did change the -volid flag that I had been passing to mkisofs to a -V flag, and for good measure, I added a -V cdrecord as well.
Aside from a torrent of debugging information, the result was the same.
Have you tried a -dummy burn with this image? With another image that's worked b4?
If other general operations are failing, considering a Phillips 4x CD-RW must have a few miles on it, maybe you should pull the drive and test it on another machine. If that works you can go about debugging your app an device files.
If other general operations are failing, considering a Phillips 4x CD-RW must have a few miles on it, maybe you should pull the drive and test it on another machine. If that works you can go about debugging your app an device files.
ASKER
I tried it with -dummy and got the same results.
I don't have any large images that have worked before.
I have tried the drive on a couple of machines (gk and headless from above), but both of them linux with cdrecord. I thought about trying to burn from Windows, but I've never been able to burn reliably there and the error messages are signigificantly less helpful.
Despite its age the drive hasn't been used enough to be worn out. It's burned less than 500 CDs. Even so, at this point I'm basically assuming that this mysterious error means that the drive is busted.
The question still stands, what is an internal target, and how does it fail?
I don't have any large images that have worked before.
I have tried the drive on a couple of machines (gk and headless from above), but both of them linux with cdrecord. I thought about trying to burn from Windows, but I've never been able to burn reliably there and the error messages are signigificantly less helpful.
Despite its age the drive hasn't been used enough to be worn out. It's burned less than 500 CDs. Even so, at this point I'm basically assuming that this mysterious error means that the drive is busted.
The question still stands, what is an internal target, and how does it fail?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
oops - sent that before i was done editing it - the last bit is from the manpage of cd record and the line numbers don't apply here -
decoding the error just shows a hardware error and a qualifier for which I can't find a reference (nor is there one in your scsierrs.c as it says "No matching qualifier"
If you'd like to learn more about the subsystem take a look at
http://www.tldp.org/HOWTO/SCSI-Programming-HOWTO-21.html#ss21.1
decoding the error just shows a hardware error and a qualifier for which I can't find a reference (nor is there one in your scsierrs.c as it says "No matching qualifier"
If you'd like to learn more about the subsystem take a look at
http://www.tldp.org/HOWTO/SCSI-Programming-HOWTO-21.html#ss21.1
use '-o boot.iso' with mkisofs instead of piping it to cdrecord to see if there's a problem with your compilation
the use -dummy with cdrecord to see if it's having problems with your image
if all's well try to write at a slower speed...
"your milage may vary"