[lug] growisofs w/Plextor 740A

[Hugh Brown]

On Wed, 23 Nov 2005, Gary Hodges wrote:

> I posted this to linux.debian.user and haven't received any responses.
> I've since installed the same model drive on a very similar machine I
> have local access to (the one in question is in Nevada) and the drive
> worked as one would expect. I have a few extra drives so I think I'll
> just send out another, but maybe someone here will have a suggestion
> that will get things going.
>
> Some additional info and my original post to l.d.u below.
>
> Cheers,
> Gary
>
> ***The original post***
> Sarge install, all updates.
>
> I had a DVD drive fail recently and replaced it with a Plextor 740A. I'm
> now having problems writing disks. With a very small file as a test
> things work out fine (i.e. I can mount and view the file contents after
> writing) using the command I have used for a couple years:

I have sarge as well, all updates applied.  I'm not running with the
ide-scsi module and my kernel is 2.6.8-2-686, an unmodified Debian kernel.

I recently purchased the 740A as well.  I've used it to burn several CDRs
w/ no problem.  I've burned 4 or 5 DVDs with k3b (which uses growisofs
under the hood), and got three DVDs that worked fine.  The rest had
problem
areas.  I could read 80% of the data on the DVD, but the files in
certain directories were unreadable.  I haven't gotten back around to
testing to see if it was user error.  All the DVDs were essentially full
(media was DVD-R).

>
> growisofs -M /dev/scd0 -l -r -J /data/tmpdir
>
> If I write something larger, e.g., 30MB and run the same command as
> above it apparently writes OK but when I try to mount the disk I get the
> following:
>
> mount: block device /dev/scd0 is write-protected, mounting read-only
> mount: Not a directory
>

This error looks like you are trying to mount to a file instead of to a
directory (e.g. mount /dev/scd0 /some/file )




> I'm using all the same commands I have used successfully for almost two
> years. An older copy of growisofs also produces the same behavior. Is
> this an issue with the drive?

If you are using a 2.6 kernel, I'd recommend turning off the ide-scsi.  If
using 2.4, then I'd give k3b a whirl (if you can).

Hugh