Re: EXTERNAL: Re: Problem with growisofs -- cannot write multisession DVDs without ejecting and reloading tray

"Richardson, Eric J" <[email protected]> wrote:

> Hello Jörg,
>
> Thank you for responding!  I would be happy to use cdrtools for writing, if I could figure out how.  I tried, Lord how I tried.  Unfortunately, I am having less success using mkisofs and cdrecord to make a multisession DVD than I had with growisofs.
>
> I read your howto here:
> http://cdrtools.sourceforge.net/private/man/README/README.multi
>
> Using this, I figured that I make the initial iso (raw) image with this command:
>
> mkisofs -R -o /tmp/file.raw file1file1file1_REDHAT.txt file2file2file2_REDHAT.txt file3file3file3_REDHAT.txt
>
> So far, so good.  I write the file with:
>
> cdrecord -v speed=2 dev=1,0,0 -multi /tmp/file.raw
>
> So far, so good.  Let's try to mount that baby:
>
> mount /dev/sr0 /media/
> mount: you must specify the filesystem type
>
> Fine.  Try it with the filesystem type:
>
> mount -o ro -t iso9660 /dev/sr0 /media/
> mount: no medium found on /dev/sr0
>
> Okay, that's not the end of the world.  I would like to be able to mount it, but what I REALLY want to do is write a second session.  Let's try the msinfo to get the data for the second session:
>
> cdrecord -msinfo dev=2,0,0
> cdrecord: Warning: Cannot read drive buffer.
> cdrecord: Warning: The DMA speed test has been skipped.
> 0,93952
>
> Great!  Let's try a mkisofs now:
>
> mkisofs -R -C 0,93952 -M /dev/sr0 -o /tmp/file.raw file4file4file4_REDHAT.txt file5file5file5_REDHAT.txt file6file6file6_REDHAT.txt 
> Setting input-charset to 'UTF-8' from locale.
> mkisofs: Input/output error. test unit ready: scsi sendcmd: no error
> CDB:  00 00 00 00 00 00
> status: 0x2 (CHECK CONDITION)
> Sense Bytes: 70 00 02 00 00 00 00 0A 00 00 00 00 3A 00 00 00
> Sense Key: 0x2 Not Ready, Segment 0
> Sense Code: 0x3A Qual 0x00 (medium not present) Fru 0x0

It seems that you are using the wrong devices.....

You started with dev=1,0,0, why did you try to use a different device later on?

What if the correct UNIX device name for SCSI dev=1,0,0 on your machine?

I recommend you to start with a 

	cdrecord -scanbus

If there is only on CD-ROM type device on your machine, cdrecord will use the 
right one without a need to specify dev= - read the man pages....

If you like to access the block device (e.g. four mounting), you need to know 
the UNIX device name, I hope that you know the right names for your machine.

Given the fact that you did not report about errors from the first write 
process, I assume that you used the right device. Given the fact that you could 
not mount the device, I assume that you used the wrong UNIX device name.

Jörg

-- 
 EMail:[email protected]                    (home) Jörg Schilling D-13353 Berlin
       joerg.schilling-8LS2qeF34IpklNlQbfROjRvVK+yQ3ZXh@public.gmane.org (work) Blog: http://schily.blogspot.com/
 URL:  http://cdrecord.org/private/ http://sourceforge.net/projects/schilytools/files/'

------------------------------------------------------------------------------
One dashboard for servers and applications across Physical-Virtual-Cloud 
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y