CD-ROM drives are commonly used for duplicating existing CDs, and
for making CD data backups of hard disk files. This article demonstrates
how both tasks can be accomplished using cdrecord on the Solaris[TM]
Operating Environment.
A simple command line program, cdrecord, means burning CDs using Solaris
software is quick, simple, and cost-effective. The cdrecord program, which works
for both SPARC[TM] and Intel Architecture systems, is included on the Solaris
Software Companion CD, and is also available for free
download from
cdrecord 1.9 SPARC 8 or
cdrecord 1.9 INTEL 8 (also
cdrecord
1.9 SPARC 9
)
Cdrecord is installed in /opt/sfw (/opt/sfw/bin/cdrecord).
Blastwave.org has a Solaris cdrecord package (www.blastwave.org/packages.php/cdrtools).
Most SCSII CD drves are compatible with solaris (for more information see
Cdrecord-2.0 drive compatibility list)
For burning CDRs on Solaris, you have to stop the "removable
media manager" process
"vold", because it blocks the CD recorder device
/etc/init.d/volmgt stop. then you can burn the CD and restart
the media manager process
/etc/init.d/volmgt start
While optional, configuring a cdrecord startup file, /etc/default/cdrecord,
will save time in the future. This startup configuration file can hold
information that cdrecord will need every time it's used, such as the CD
recorder's speed, device name, the preferred buffer size, and so on.
Alternately, these options can be entered into the command line before every
use.
To discover the CD recorder and CD-ROM drive device names you can use cdrecord -scanbus at the root prompt. The command output should be similar
to:
# cdrecord -scanbus
cdrecord 1.9 (i386-pc-solaris2.8) Copyright (C) 1995-2000
1,0,0 100) 'CREATIVE' 'CD5233E ' '1.00' Removable CD-ROM
2,4,0 204) 'PLEXTOR' 'CD-R PX-R820T' '1.05' Removable CD-ROM
The device ID is the first three numbers listed in each entry -- in this case,
device 2,4,0 is the CD recorder, for example. The configuraiton file can also
include a recording speed (for example, 8 times), and a buffer size (for
example, 8 megabytes) to help avoid under runs. To create the configuration
file, located in /etc/default/cdrecord, type:
# cat /etc/default/cdrecord
CDR_FIFOSIZE=8m
CDR_SPEED=8
CDR_DEVICE=USCSI:2,4,0
The cdrecord program startup configuration file is now set up for the future!
CD to CD
To duplicate an existing CD, insert the CD into the CD-ROM drive. (Remember,
duplicating CDs might require certain copyright and license permissions!) Then:
Determine the controller and target numbers. These are listed in the cdrecord
-scanbus output (from before): 1,0,0 100) 'CREATIVE' 'CD5233E ' '1.00' Removable
CD-ROM . The first number is the controller number, and the second number is the
target number. In this case, they are one and zero, respectively. Also note that
in the Solaris 8 platform, the IDE CD-ROM drive device names are very similar to
SCSI device names -- both contain target numbers.
Choose an output file with sufficient free hard disk space (at least 700
megabytes recommended). For this example, the free space is located in the
/local file system.
Capture an ISO image file of the CD by typing (at root prompt):
# dd if=/dev/dsk/c1t0d0p0 of=/local/mycdromfile.iso
It will take about five to ten minutes to copy the entire CD image file to
disk. After inserting a blank CD into the CD-ROM drive, burn the image from disk
onto a second CD by typing:
# cdrecord -v /local/mycdromfile.iso
This should take about 15 to 30 minutes, depending on the speed of the CD
burner. In the above command, -v displays each step with extra information, just
in case something isn't successful.
Data to CD
Many users also utilize CD-ROM drives to create data backups on CD of a
system's home directory and files. The Solaris 8 Operating Environment includes
a very useful command for this, mkisofs, which creates an image file when
pointed at a system directory. To make an image file of a home directory, for
example /home/neal, type:
# mkisofs -l -L -r -o /local/mycdromfile2.iso /home/neal
This will take all the files in the /home/neal directory and create a CD-ROM
ISO image file at /local/mycdromfile2.iso.
When this is finished, insert a blank CD into the CD-ROM drive, and type:
# cdrecord -v /local/mycdromfile2.iso
This will copy the data image onto the blank CD, and should take about 15 to
30 minutes depending on the speed of the burner. More information about the
mkisofs command, including all its configurable options, can be found by typing
man mkisofs at a shell prompt.
For additional software and hardware information, documentation, source code,
and a list of supported CD recorders for cdrecord (an open source project),
visit the
Freshmeat Web site.
To learn more about the Solaris Operating Environment, please visit
www.sun.com/solaris.
Issues and methods stated in this article are outdated. Reading it may
still help understand the problems.
You might want to check out the PDF from Sun Blueprints for a much easier
way of doing things these days.
http://www.sun.com/software/solutions/blueprints/0301/BuildBoot.pdf
Preface:
I have been trying to customize a Solaris install CDROM to my own needs.
After several searches without any usable results, I ran into some really
good explanations on this topic on the
SunManagers Mailinglist Archive.
The work of Victoria Lau (vlau@msmail2.hac.com) 'Log
file to customize the Solaris 2.5 boot cdrom' and a paper of James
Hutchinson (lsharp@taz.hutch.org) 'Summary:
How to build a Solaris bootable CDROM' helped alot, but these documents
are Solaris 2.5 specific. Sun changed the CD-Layout from 2.5 to 2.6 :=)
In this document, I will explain how the Sun boots off the CDROM and how
this CDROM could be customized to fit someones needs. This paper refers to
the Solaris 2.6 HW 5/98 CDROM. The new Solaris 2.7 CDROM seems to share the
same layout.
This document is structured in several sections:
1. Introduction to the Sun CDROM layout
2. How is the machine booting off the CDROM and where
does the installation begin.
3. Altering the CDROM
3.1 The VTOC explained
3.2 Two possible methods for changing the CD
4. Testing your future, bootable CDROM
5. Scripts and other goodies
6. Comments from Readers
CD-Writer
Author: arpsam
|
|
Apr 14, 2003 10:57
AM |
|
|
Hi there, I just installed
Solaris 9 on my HP Vectra machine, I have a Mitsumi CD
Writer , is there something like cd writing under solaris,
if yes then how can one write a cd in solaris, and where can
we find drivers and softwares for burnig cd's under solaris.
Samir
Re: CD-Writer
Author: J.Keil
|
|
Apr 14, 2003 11:30
AM (reply 1 of 15) |
|
|
Re: CD-Writer
Author: arpsam
|
|
Apr 14, 2003 12:39
PM (reply 2 of 15) |
|
|
Hi there,
I downloaded the cdrec software from sun, also installed it,
now the question is how to work with it, and how to know if
it is compatible with my cd-rw drive. Is there a manual or a
README where I can read and find out how to work with it?
Thanks though for information.
Re: CD-Writer
Author:
J.Keil
|
|
Apr 15, 2003 6:33 AM
(reply 3 of 15) |
|
|
A list of compatible CD-writer
drives is available on the author's web site:
http://www.fokus.fhg.de/research/cc/glone/employees/joerg.schilling/private/cdwriters-2.0.html
For burning CDRs on Solaris, you have to stop the "removable
media manager" process
"vold", because it blocks the CD recorder device
/etc/init.d/volmgt stop
... burn CDR(s) using cdrecord ...
/etc/init.d/volmgt start
You can use the command "cdrecord -scanbus" to scan for SCSI
/ ATAPI devices, and find
the device address (bus / target / logical unit) of your
CD-recorder.
To burn an ISO9660 image to a CD-R device at bus address
X,Y,Z, use the command
cdrecord dev=X,Y,Z image.iso
A manual page is available under /opt/sfw/man:
man -M /opt/sfw/man cdrecord
Re: CD-Writer
Author:
arpsam
|
|
Apr 15, 2003 8:22 AM
(reply 4 of 15) |
|
|
Is Mitsumi CD-48X5TE compatible
cd writer? I installed the package and I am trying to
execute the command "cdrecord -scanbus", but it says that it
cannot find /dev/rdsk/c1t1d0s2 in warning. What does it
mean. I am new to Solaris and would like to know more.
Samir Patel
Re: CD-Writer
Author: J.Keil
|
|
Apr 16, 2003 11:03
AM (reply 5 of 15) |
|
|
Try to post the exact error
message printed by cdrecord.
You may want to run the command "devfsadm -v -C" to detect
new devices and to clean up unused device nodes. Maybe
/dev/rdsk/c1t1d0* is some old device that is not used any
more.
Does the command "iostat -En" list your mitsumi cd writer?
Re: CD-Writer
Author: arpsam
|
|
Apr 16, 2003 11:32
AM (reply 6 of 15) |
|
|
It gives the following message,
# iostat -En
c1t0d0 Soft Errors: 0 Hard Errors: 0 Transport Errors: 0
Vendor: TEAC Product: CD-532E-B Revision: 2.0A Serial No:
CD-532E-B
Size: 0.00GB <0 bytes>
Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable:
0
Illegal Request: 0 Predictive Failure Analysis: 0
c1t1d0 Soft Errors: 0 Hard Errors: 0 Transport Errors: 0
Vendor: MITSUMI Product: CR-48X5TE Revision: 1.8A Serial No:
CR-48X5TE
Size: 0.00GB <0 bytes>
Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable:
0
Illegal Request: 0 Predictive Failure Analysis: 0
Does this mean anything.
Re: CD-Writer
Author: arpsam
|
|
Apr 16, 2003 11:51
AM (reply 7 of 15) |
|
|
Issuing the command cdrecord
-scanbus following messages are given
# ./cdrecord -scanbus
Cdrecord 1.9 (i386-pc-solaris2.9) Copyright (C) 1995-2000
Jırg Schilling
Warning: Using USCSI interface.
./cdrecord: No such file or directory. Cannot open
'/dev/rdsk/c1t1d0s2'. Cannot open SCSI driver.
./cdrecord: For possible targets try 'cdrecord -scanbus'.
Make sure you are root.
Samir Patel
Re: CD-Writer
Author: J.Keil
|
|
Apr 17, 2003 3:21 AM
(reply 8 of 15) |
|
|
> c1t1d0 Soft Errors: 0 Hard
Errors: 0 Transport Errors: 0
> Vendor: MITSUMI Product: CR-48X5TE Revision: 1.8A Serial
No: CR-48X5TE
>
> Does this mean anything.
Now we know that
1. Solaris does see the "MITSUMI CR-48X5TE" device
2. It's device name is /dev/rdsk/c1t1d0*
> Issuing the command cdrecord -scanbus following messages
are given
>
> # ./cdrecord -scanbus
> Cdrecord 1.9 (i386-pc-solaris2.9) Copyright (C) 1995-2000
Jırg Schilling
> Warning: Using USCSI interface.
> ./cdrecord: No such file or directory. Cannot open
'/dev/rdsk/c1t1d0s2'. Cannot open SCSI driver.
> ./cdrecord: For possible targets try 'cdrecord -scanbus'.
Make sure you are root.
OK, now I'm able to reproduce this error message: It happens
when you run
cdrecord as an ordinary user, that does have permission to
open the
'/dev/rdsk/c1t1d0s2' device.
If you carefully read the messages printed by cdrecord, the
solution for the
problem is mentioned:
Make sure you are root.
You must run cdrecord as user root, non-root users are not
allowed
direct access to disk devices and are not allowed to send
SCSI
commands to them.
Re: CD-Writer
Author: arpsam
|
|
Apr 17, 2003 7:10 AM
(reply 9 of 15) |
|
|
Trying the command after
becoming root produced the same result, you say that the
cd-recorder is detected by iostat command, is there
something that I might have missed during the installation
or during the configuration? I followed the steps that were
given in the README file during the installation.
Samir
Re: CD-Writer
Author: J.Keil
|
|
Apr 17, 2003 10:33
AM (reply 10 of 15) |
|
|
Hmm, try tracing the system
calls using "truss cdrecord -scanbus" and check how the open
on /dev/rdsk/c1t1d0s2 fails.
If it fails with the error EACCESS:
open("/dev/rdsk/c1t1d0s2", O_RDONLY|O_NDELAY) Err#13 EACCES
when you're not root.
And if fails with EBUSY:
open("/dev/rdsk/c1t1d0s2", O_RDONLY|O_NDELAY) Err#16 EBUSY
when you didn't stop the "vold" process.
Re: CD-Writer
Author: arpsam
|
|
Apr 17, 2003 10:48
AM (reply 11 of 15) |
|
|
I ran the above given command
"truss cdrecord -scanbus" and along with a series of
messages I found this as well,
open("/dev/rdsk/c1t0d0s2", O_RDONLY|O_NDELAY) Err#16 EBUSY
open("/dev/rdsk/c1t1d0s2", O_RDONLY|O_NDELAY) Err#16 EBUSY
also at this time I was root.
# who
root console Apr 17 09:57 (:0)
root pts/4 Apr 17 10:01 (:0.0)
What does this mean?
Re: CD-Writer
Author: J.Keil
|
|
Apr 17, 2003 11:29
AM (reply 12 of 15) |
|
|
Some process has these devices
open with an exclusice lock. This is typical behaviour when
"vold"
is still running.
Stop the "vold" process before using cdrecrod. Run
/etc/init.d/volmgt stop
to stop vold. Double check with "pgrep vold" that vold is
not running any more.
(I've seen cases where vold refuses to die, to you may have
to send some signal to vold, using
"pkill vold" or even "pkill -9 vold").
Re: CD-Writer
Author:
arpsam
|
|
Apr 17, 2003 11:41
AM (reply 13 of 15) |
|
|
Ok I ran the cdrecord command
after stopping the vold. The output looks like this,
#cdrecord -scanbus
Cdrecord 1.9 (i386-pc-solaris2.9) Copyright (C) 1995-2000
Jırg Schilling
Warning: Using USCSI interface.
Using libscg version 'schily-0.1'
scsibus1:
1,0,0 100) 'TEAC ' 'CD-532E-B ' '2.0A' Removable CD-ROM
1,1,0 101) 'MITSUMI ' 'CR-48X5TE ' '1.8A' Removable CD-ROM
1,2,0 102) *
1,3,0 103) *
1,4,0 104) *
1,5,0 105) *
1,6,0 106) *
1,7,0 107) *
it says that its a cd-rom, does this mean that it cannot
burn cd's.
Samir
Re: CD-Writer
Author: J.Keil
|
|
Apr 18, 2003 10:47
AM (reply 14 of 15) |
|
|
> It says that its a cd-rom,
does this mean that it cannot burn cd's.
cdrecord doesn't care about the SCSI device type, a device
type "CD-ROM" is OK.
Messages: 1
Registered: May 2004
Location: Great Falls, Virginia |
Junior Member
|
|
Hi,
I have a SUN Ultra 10 with TEAC CD Writer. I tried cdrw command to blank
a cd and in fact it works. I can write a cd. But when I attempted to
create a bootable CD, I am frustrated. I tried cdrecord, BurnIT
(unfortunately they all have only source versions and when I try to
build I get all kinds of hurdles). So I followed NetBSD's instructions
and they seemed very straight forward as seen in
http://www.netbsd.org/Documentation/bootcd.html#sparc64image
But sunbootcd.sh uses sunlabel and I got stuck there. I could create a
CD with solaris 10 .iso file and boot.sh, but without sunlabel, I cannot
use that CD to boot.
Any suggestions? |
I found this, may be usefull for you:
"The first step is to identify the cd recorder device name, which can be found
by scanning the device buses. In order to scan the devices, however, the volume
management must be turned off.
Log in as root
Turn off volume management by typing
/etc/init.d/volmgt
stop
Discover the CD recorder and CD-ROM drive device names by typing cdrecord -scanbus
at the root prompt. The command output should be similar to:
# cdrecord -scanbus
cdrecord 1.9 (i386-pc-solaris2.8) Copyright (C) 1995-2000
1,0,0 100) 'CREATIVE' 'CD5233E ' '1.00' Removable CD-ROM
2,4,0 204) 'PLEXTOR' 'CD-R PX-R820T' '1.05' Removable CD-ROM
The device ID is the first three numbers listed in each entry -- in this case,
device 2,4,0 is the CD recorder, for example. The configuraiton file can also
include a recording speed (for example, 8 times), and a buffer size (for
example, 8 megabytes) to help avoid under runs. To create the configuration
file, located in /etc/default/cdrecord, type:
# cat /etc/default/cdrecord
CDR_FIFOSIZE=8m
CDR_SPEED=8
CDR_DEVICE=USCSI:2,4,0
The cdrecord program startup configuration file is now set up for the future!
After inserting a blank CD into the CD-ROM drive, burn the image from disk onto
a second CD by typing:"
# cdrecord -v /local/mycdromfile.iso
I've used this to create my Solaris express CD's an work fine.
Good luck !
Name:
Glenn Moores
Date: December 11, 2001 at 02:45:54
Pacific
Subject: Installing scsi CDROM into
Ultra30
Hi,
I'm from a
software background and so dont often get into this
HW install stuff, so I need some guidence.....
I've got an Ultra 30 which I need to build, but it
has no CDROM so I'm installing a standard Tosh scsi 40x.
At OK prompt, probe-scsi finds it on Target 3, but
"boot cdrom" doesnt find a boot file and complains
device not ready. I'm assuming this is because the std
cdrom alias is for target 6? I've tried variations on
boot but to no avail.
Any clues?
Response Number 1
Subject: Installing scsi CDROM into
Ultra30
Hi mate, if the cdrom alias is for target 6, then I
guess you can either try to change the target number of
the drive by the jumpers/pins on the back of it, or you
could use the openboot commands to create an alias...
at ok prompt:
show-devs
will show you devices .. basically look for your
cdrom drive device + target on there and use
devalias to create the alias for it.
it's prob set to:
/iommu/sbus/espdma@f,400000,esp@f,800000/sd@6,0:d
you could do
devailias mycdrom
/iommu/sbus/espdma@f,400000,esp@f,800000/sd@3,0:d
and type boot mycdrom - however devalias is only a
temporary thing and will be erased upon
reboot or powerdown. you can use nvalias instead for
a permanent setting. (if you can't change the scsi
target ID then just change the cdrom alias as
necessary)..
Hope this helps.
