"{ DriveReady SeekComplete Error }" while burning CDR's

[tdb]

I started getting this error this weekend when I tried to read a cdr I burned with cdrecord:

Code: Select all

Apr 17 17:03:50 ferrari end_request: I/O error, dev hdc, sector 26816
Apr 17 17:03:50 ferrari Buffer I/O error on device hdc, logical block 6704
Apr 17 17:03:51 ferrari hdc: command error: status=0x51 { DriveReady SeekComplete Error }
Apr 17 17:03:51 ferrari hdc: command error: error=0x51 { IllegalLengthIndication LastFailedSense=0x05 }
Apr 17 17:03:51 ferrari ide: failed opcode was: unknown

I get the error when I try to read from the disk using dd and md5sum using /dev/hdc. I have an Acer Ferrari 4005, with a Matshita UJ-845S dvd-ram. Everything burned fine up until this weekend. I have not made any changes to the kernel or any settings. I burned the discs using:

Code: Select all

cdrecord dev=/dev/hdc image.iso

as a regular user. cdrecord gave no errors during the burn process. I only get that error when I try to access the disk using md5sum or dd. Both programs exit unsuccessfully with a "Read/Write error".

[eldad]

Try to read the files instead:

Code: Select all

for x in $(find /mnt/cdrom -type f)
do
        echo Testing:$x
        cat $x > /dev/null
done

If you get no errors after it is completed, then as I suspect from the IllegalLengthIndication flag, you are just trying to read after the end of the CD data.

[tdb]

I ran the script and the files read properly with no errors. After researching the issue further, I found that it is a problem with reading past the last track on the cd. When I burned the cdr's using cdrecord, I didn't use the -pad and -dao options, which are apparently good things to do. I first noticed the error when I was trying to do an install on a new server I got. I noticed tons of read errors from the gentoo livecd I just burned. I did a straight md5sum on /dev/hdc to try and verify the burn, and started getting all the errors. So you think it is just that you can't do an md5sum on a raw, unmounted cdr?

What is the best way to verify that a cdr was burned properly? Knoppix gives the option to verify the burn from the cd itself, is there a way to do that with Gentoo?

[eldad]

I myself use k3b which has an option to verify images byte-by-byte.
I use it when I burn personal stuff I wouldn't be able to recreate and it never failed me.

[tdb]

I found two websites that do a very good job of telling how to get good burns under linux. The same author has two sites, one for CD's and one for DVD's.

http://www.troubleshooters.com/linux/coasterless.htm

http://www.troubleshooters.com/linux/co ... ss_dvd.htm

Basically, I should have burned with DAO mode, which apparently will pad out the end of the data track. I haven't tested yet to make sure this is my problem, but it all makes sense to me. I guess XCDRoast did all these automatically for me. These were some of my first few burns using cdrecord.

[RayVad]

Same problem here. But i solved it by swapping the CD-player.

Two possible causes in my opinion:

1. the CD player is dirty or maybe broken.
2. The CD player is not being able to read the CD's correctly, burned by the CDWriter. (which reminds me of issues from the past)

Hope this helps to solve your problem too.

Best regards,
Ray