[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: PX-716SA growisofs won't write DVD

Steve Adeff wrote:


drive is a SATA drive that works fine for CDR's.

growisofs -Z /dev/dvd1=file.ISO

Executing 'builtin_dd if=file.ISO of=/dev/dvd1 obs=32k seek=0'
/dev/dvd1: "Current Write Speed" is 8.2x1385KBps.
    32768/4008509440 ( 0.0%) @0.0x, remaining 14271:43
    32768/4008509440 ( 0.0%) @0.0x, remaining 20388:10
    32768/4008509440 ( 0.0%) @0.0x, remaining 28543:26
    32768/4008509440 ( 0.0%) @0.0x, remaining 34659:53
    32768/4008509440 ( 0.0%) @0.0x, remaining 40776:20
    32768/4008509440 ( 0.0%) @0.0x, remaining 48931:36

dmseg output:
Device sr0 not ready.
Attached scsi generic sg0 at scsi2, channel 0, id 0, lun 0,  type 0
Attached scsi generic sg1 at scsi3, channel 0, id 0, lun 0,  type 5
Attached scsi generic sg2 at scsi6, channel 0, id 0, lun 0,  type 0
Attached scsi generic sg3 at scsi6, channel 0, id 2, lun 0,  type 0
parport0: FIFO is stuck
parport0: BUSY timeout (1) in compat_write_block_pio
DMA write timed out
Device sr0 not ready.
parport0: FIFO is stuck
parport0: BUSY timeout (1) in compat_write_block_pio
DMA write timed out
parport0: FIFO is stuck
parport0: BUSY timeout (1) in compat_write_block_pio
DMA write timed out
parport0: FIFO is stuck
parport0: BUSY timeout (1) in compat_write_block_pio
DMA write timed out
SCSI error : <3 0 0 0> return code = 0x2
parport0: FIFO is stuck
parport0: BUSY timeout (1) in compat_write_block_pio
DMA write timed out
ata4: command 0xa0 timeout, stat 0xd0 host_stat 0x20
SCSI error : <3 0 0 0> return code = 0x2
parport0: FIFO is stuck
parport0: BUSY timeout (1) in compat_write_block_pio
DMA write timed out
parport0: FIFO is stuck
parport0: BUSY timeout (1) in compat_write_block_pio
DMA write timed out
parport0: FIFO is stuck
parport0: BUSY timeout (1) in compat_write_block_pio
DMA write timed out
Same thing I told David, your drive (firmware) may not like the media. Things to try are other brands of media and firmware upgrade. That "device not ready" sounds as if the firmware didn't like the media.
Other thought: try the mediainfo command and see if that provides enlightenment. 

--
E. Robert Bogusta
 It seemed like a good idea at the time
Reply to: