01-02-2009
Quote:
Originally Posted by
computerguy_2
Hello,
I'm a new SA fairly familar with Solaris. I'm using the COEInstaller tool and am unable to read a cd. The cd is fine.
The machine continues to see the last cdrom I've used which was an image. I've tried restarted the server, restarted COEInstaller but the machine still see's the last cdrom.
Is there a way to clear this
Please help...
Hi computerguy_2,
Before executing any commands use the man pages for more back round information on the command;
ie # man vold
But for the moment try this......
As user root, try running the following command, at CLI (command line interface)
# /etc/init.d/volmgt stop
&
# /etc/init.d/volmgt start
I hope this is of help
Jnike
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
ok here is what i do and get:
# mount /dev/sd6a /cdrom
mount /dev/sd6a write-protected
ok so what do i do its a external cdrom and its on scsi number 6. its a SparcSTATION 2. we're trying to put red hat sparc 6.2 on it but it wont boot. i am about to take the hard drives out and install it a... (8 Replies)
Discussion started by: wixifer
8 Replies
2. UNIX for Dummies Questions & Answers
Hallo,
who can help me to configure a scsi cd writer to my sun server enterprice 1000.
1. Hardware configuration
2. Burn program
etc..
Please send me links or dokuments were i can get more infos about this theme.
regards joerg (1 Reply)
Discussion started by: joerg
1 Replies
3. Solaris
Here's some cmd output:
bash-2.05# ls /dev/dsk/*
/dev/dsk/c0t0d0s0 /dev/dsk/c0t0d0s4 /dev/dsk/c0t1d0s0 /dev/dsk/c0t1d0s4
/dev/dsk/c0t0d0s1 /dev/dsk/c0t0d0s5 /dev/dsk/c0t1d0s1 /dev/dsk/c0t1d0s5
/dev/dsk/c0t0d0s2 /dev/dsk/c0t0d0s6 /dev/dsk/c0t1d0s2 /dev/dsk/c0t1d0s6
/dev/dsk/c0t0d0s3 ... (4 Replies)
Discussion started by: AJA
4 Replies
4. Solaris
I have Sun Solaris 10 (x86 based). I installed Solaris through CDROMs by booting the system through CDs only. But now when I try to use the same CDROM, it ejects out CD after few seconds, the CDROM blinks as long as the CD is in. But it throws it out. I tried killing and restarting "VOLD". Also bye... (3 Replies)
Discussion started by: stushar2000
3 Replies
5. Solaris
I am having trouble reading floppy and crom in single user mode.
running volcheck doesn't do anything
I am using Solaris -10 on Sun blade 150.
Has anybody seen this problem .. or do I have to manually mount the cdrom ...and floppy ???
thanks (2 Replies)
Discussion started by: ajnabi
2 Replies
6. Solaris
Hello,
First i'm Dutch, and my English is not very well. Sorry. :D
I have got a Sun Microsystems Ultra 3D (with SPARC processor). The file must be burned to a DVD. And my computer can onley read a cd.
How to get Solaris 10 on a few cds?
Please help me.
Thanks a lot..
Greets. (21 Replies)
Discussion started by: TomW
21 Replies
7. Solaris
hi unix friends,
has anyone faced this problem before ? i inserted my cd into my X1450 machine, it says I/O error.
mount -F hsfs -o ro /dev/dsk/clt0d0s0 /cdrom
mount: I/O error
mount: cannot mount /dev/dsk/c1t0d0s0
what should i do ? (4 Replies)
Discussion started by: Exposure
4 Replies
8. Solaris
Hello,
I've read many posts that offer tips on how to mount a CDROM but I haven't seen any on how to get the system to recognize the CDROM drive.
I was transferring files from CDROM to the hard drive successfully. I entered the third CDROM and the system refused to automount it. I tried... (2 Replies)
Discussion started by: TrueSon
2 Replies
9. Solaris
Hi everybody
Having a strange problem on a x4270m2 Sun server.
Jumpstarting it from dvd drive. After install the dvddrive does not exist.
Be aware jumpstart is custommade
bash-3.00# mount -F hsfs -o ro /dev/dsk/c1t4d0p0 /cdrom
mount: No such device
mount: cannot mount... (7 Replies)
Discussion started by: stockhes
7 Replies
10. Solaris
Good day everyone,
I am trying to install some new senmail patch on my Solaris 10 system.
I know the cdrom for my CP3260 blade servers in my rack worked for the last patches installed. However, when I went to copy from the .tar file from the cdrom to the /tmp. I received an error cannot... (2 Replies)
Discussion started by: cookiecrumbs
2 Replies
vold(1M) System Administration Commands vold(1M)
NAME
vold - Volume Management daemon to manage removable media devices
SYNOPSIS
/usr/sbin/vold [-n] [-t] [-v] [-f config-file] [-l log-file] [-d root-dir] [-L debug-level]
DESCRIPTION
The Volume Management daemon, vold, creates and maintains a file system image rooted at root-dir that contains symbolic names for removable
media devices. These devices include CD-ROMs, floppies, DVDs, and USB 1394 devices. The default root-dir is set to /vol if no directory is
specified by the -d option.
vold reads the /etc/vold.conf configuration file upon startup. If the configuration file is modified later, vold must be told to reread the
/etc/vold.conf file. Do this by entering:
example# kill -HUP vold_pid
To tell vold to clean up and exit, the SIGTERM signal is used:
example# kill -TERM vold_pid
where vold_pid is the process ID of vold.
A disk storage device can not be removed or inserted while vold is active. To remove or insert a removeable mass storage device such as a
USB memory stick, first stop the daemon by issuing the command /etc/init.d/volmgt stop. After the device has been removed or inserted,
restart the daemon by issuing the command /etc/init.d/volmgt start.
OPTIONS
The following options are supported:
-n Never writeback. Volume Management updates media labels with unique information if labels are not unique. This flag keeps
Volume Management from changing your media. The default setting is FALSE.
-t Dump NFS trace information to the log file. The default setting is FALSE.
-v Provide lots of status information to the log file. The default setting is FALSE (do not provide status info to log file).
-d root-dir Specify an alternate root directory. The default location is /vol. Setting this will also cause other Volume Management
utilities to use this as the default root directory.
-fconfig-file Specify an alternate configuration file. The default file is /etc/vold.conf.
-llog-file Specify an alternate log file. The default log file is /var/adm/vold.log.
-Ldebug-level Change the level (verbosity) of debug messages sent to the log file. The range is 0 to 99 where 0 is nothing and 99 is
everything. The default level is 0.
ENVIRONMENT VARIABLES
vold sets the following environment variables to aid programs which are called when events such as insert, notify, and eject occur:
VOLUME_ACTION Event that caused this program to be executed.
VOLUME_PATH Pathname of the matched regex from the vold.conf file.
VOLUME_DEVICE Device (in /vol/dev) that applies to the media.
VOLUME_NAME Name of the volume in question.
VOLUME_USER User ID of the user causing the event to occur.
VOLUME_SYMNAME Symbolic name of a device containing the volume.
VOLUME_MEDIATYPE Name of the type of media (CD-ROM, floppy or rmdisk)
FILES
/etc/vold.conf Volume Management daemon configuration file. Directs the Volume Management daemon to control certain devices, and
causes events to occur when specific criteria are met.
/usr/lib/vold/*.so.1 Shared objects called by Volume Management daemon when certain actions occur.
/var/adm/vold.log the default log file location (see the -l option for a description).
/vol the default Volume Management root directory.
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWvolu |
+-----------------------------+-----------------------------+
SEE ALSO
volcancel(1), volcheck(1), volmissing(1), rmmount(1M), rpc.smserverd(1M), rmmount.conf(4), vold.conf(4), attributes(5), volfs(7FS)
System Administration Guide: Basic Administration
SunOS 5.10 13 Sept 2004 vold(1M)