Sponsored Content
Full Discussion: Unmounting a cd in Solaris
Top Forums UNIX for Dummies Questions & Answers Unmounting a cd in Solaris Post 29938 by Perderabo on Monday 14th of October 2002 03:41:59 PM
Old 10-14-2002
The command is:
eject

Is that what you meant when you said you tried to eject the cd? If the eject command is failing run:
eject -d
to see if knows about the device. Did you mount this manually? On a sun you should just insert a cd and it should mount itself. Did that happen? If vold running? (ps -ef | grep vold)

See the man page on eject for more ideas. But sometimes you need to kill and restart vold:
/etc/init.d/volmgt stop
/etc/init.d/volmgt start
But that should be a last resort.
 

7 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Unmounting /home Permanently

Hi! I got tired of running out of disk space on the different partitions on my Solaris 8 Ultra 5 computer so I tried to make just a big / partition and install everything on that. But somehow I managed to get a 0 byte /home partition :-) I tried to delete this (By just clicking it in X-Windows and... (8 Replies)
Discussion started by: alfabetman
8 Replies

2. AIX

unmounting problem

Hello, can someone help me with the problem am facing unmounting a filesystem I wanted to unmount /oradata cause i created it with a larger size and wanted to umount it , delete the fs and create again with less size. i have done below but nothing so far. 1) iam not in /oradata directory 2) i... (3 Replies)
Discussion started by: karthikosu
3 Replies

3. Solaris

Unable to login using ssh,telnet onto my solaris machine with solaris 10 installed

Hi, I am unable to login into my terminal hosting Solaris 10 and get the below error message "Server refused to allocate pty ld.so.1: sh: fatal: libc.so.1: open failed: No such file or directory " Is there anyways i can get into my machine and what kind of changes are required to be... (7 Replies)
Discussion started by: sankasu
7 Replies

4. AIX

Unmounting a failed NFS mount

I have an NFS file system mounted on one of my AIX servers with "mount -v cifs".. The server from which the file system was mounted has crashed and now my "df -g" output is hanging. Is there any was to unmount this NFS file system? I have tried "umount -f". Doesn't work. Or is there any way in... (6 Replies)
Discussion started by: wibhore
6 Replies

5. AIX

Error unmounting a remote mounted file system

Hi All, I'm facing an issue while trying to unmount a remotely mounted file system, strangely it's not even getting mounted, Kindly find the reply messages. Mounting error msg nfsmnthelp: 1831-019 <Server host>: Cannot mount a file system that is already remotely mounted. mount: 1831-008... (13 Replies)
Discussion started by: Abhishekag
13 Replies

6. Shell Programming and Scripting

Validation of mounting and unmounting

Hi folks, I have below code for unmounting, but i need validation filesystem is unmounted or not, if not it give us error. Please confirm below code or need modification. Please suggest. umount /oradata if then echo "/oradata Unmounted Successfully" else echo... (3 Replies)
Discussion started by: learnbash
3 Replies

7. UNIX for Dummies Questions & Answers

Unmounting NFS idle clients from server

Hello World, We have a software repository server in our environment which we use as an NFS server. Now this has been going on well before I was hired. Now, I observed many users not unmounting the NFS resources after their use. I ran showmount and it showed 513 current sessions. :wall: Is... (7 Replies)
Discussion started by: satish51392111
7 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)
All times are GMT -4. The time now is 12:46 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy