#16 cdrwtool blank command incorrect

[Anonymous]

cdrwtool blank command incorrect for dvd+rw (ricoh 5125a)
IDE drive.

without ide-scsi, error is:
Initiating quick
disc blank
hdd: packet command error: status=0x51 {
DriveReady SeekComplete Error }
hdd: packet command
erro: error=0x50
ATAPI device hdd:
Error: Illegal
request -- (Sense key=0x05)
(reserved error code) --
(asc=0x30, ascq=0x05)
The failed "Blank" packet
command was:
"a1 01 00 00 00 00 00 00 00 00 00 00 "

Error in command packet byte 54523 bit 0
wait_cmd:
Input/output error
Command failed: a1 01 00 00 00 00 00 00
00 00 00 00 - sense 05.30.05
blank disc: Illegal
seek

with ide-scsi, error is:
Initiating quick disc
blank
sr0: CDROM (ioctl) reports ILLEGAL
REQUEST.
wait_cmd: Invalid argument
Command
failed: a1 01 00 00 00 00 00 00 00 00 00 00 - sense
05.30.05
blank disc: Illegal seek

I have the packet-
2.4.19-rc1.patch patched into a 2.4.18 kernel, because the
packet-2.4.18.patch was causing kernel oops when I write files to
CDRW.

With the 19-rc1 patch though, I can write CDRWs
fine.

I have also used the DVD+RW format & growisofs
tools found
here:
http://fy.chalmers.se/~appro/linux/DVD+RW/
and
they work fine, but I really want a UDF formatted DVD, not an ISO
formatted one.

Please reply to me here:
derek at
flamesnyper dot com
since I do not have a sourceforge
account at this time.

Thanks.

[Peter English]

Logged In: YES
user_id=577678

Try using the following sequence of commands:

cdrwtool -t 4 -d /dev/cdrom -b fast
cdrwtool -t 4 -d /dev/cdrom -m 4096

Reboot the computer then run:

cdrwtool -t 4 -d /dev/cdrom -u 4096

where /dev/cdrom is the CDRW device.

You may want to adjust the -t 4 arguments to a suitable write
speed for your cdrom device.

Rebooting the computer is very important and you have to do
it to reinitalize the CDRW device.

I believe that there may be a bug in cdrwtool or there may be
variation in CDRW device implementations that cdrwtool may
need to be patched to reinitialize the CDRW after a format.

[Nobody/Anonymous]

Logged In: NO

I had exactly the same problem, and your method work perfectly !

Thanks !

P.s: I have not reboot, but just do a : cdrdao unlock --device /dev/cdrom