Sponsored Content
Operating Systems Solaris CDROM will not eject - says device busy Post 302362738 by jimmy54321 on Saturday 17th of October 2009 08:19:03 AM
Old 10-17-2009
Thanks for all the feedback.

I managed to solve it by...

# volmgt stop

physically ejecting CD

# volmgt start
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

umount, device busy, but..

I'm trying to unmount a file system, but umount says the device is busy. A fuser -c /myfs tells me that nothing on this fs is in use. Any idea? Oh, and btw, why isn't my signature beeing displayed? Show user's signature is enabled and I have entered one :/ (10 Replies)
Discussion started by: sTorm
10 Replies

2. Solaris

cdrom will not eject

Hi I have placed a CD into the rom and now I can not eject it. when i type in eject cdrom i get the follwing error root@ssdb0009 # eject cdrom /vol/dev/rdsk/c0t6d0/dp_a0500_solaris_7_and_8_cd: Device busy Therefore i try and eject it with the -f option (eject -f cdrom) I still get the... (4 Replies)
Discussion started by: dennisca
4 Replies

3. AIX

Eject CDROM?

Now i have a prolem! I double click on my zip file from cdrom. System can not read my zip file and i can not eject my cdrom. How can i manage process and can i end a process or how can i eject my cdrom? please have me! thanks (4 Replies)
Discussion started by: leenguyen0101
4 Replies

4. HP-UX

Cannot umount - device busy

Anyone have any idea why I cannot umount a directory even though fuser shows no process attached to it? fuser -cu /data/oracle/GMPSHRDM/export /data/oracle/GMPSHRDM/export: umount /data/oracle/GMPSHRDM/export umount: cannot unmount /data/oracle/GMPSHRDM/export : Device busy umount:... (2 Replies)
Discussion started by: keelba
2 Replies

5. Solaris

SF V210 CDROM drive auto eject!

Hi, When I insert a cd to CDROM drive in SF V210 Solaris 10 it took seconds then eject it auto! How can I solve this issue? Thanks Regards :) (8 Replies)
Discussion started by: HishamN
8 Replies

6. UNIX for Dummies Questions & Answers

Device or resource busy??

Hi, I'm trying to do a sharity mount to mount a terastation network drive. I'm getting a Device or resource busy message after my mount command. Please see output below... # /usr/local/sharity3/bin/sharity mount smb://labbackup01/bakup_data /mnt/labbackup01 Device or resource busy.... (2 Replies)
Discussion started by: orahi001
2 Replies

7. Solaris

How to eject boot cdrom after booting from it?

Hey everyone, I currently have a sparcstation 5, and am trying to run some scripts on it without booting off the hard drive. Currently I am using a Solaris 8 install cd to boot into single user mode. However, the scripts I have are on a different CD. What I would like to do is to use the... (6 Replies)
Discussion started by: idlechatter
6 Replies

8. Solaris

Trying to eject cdrom

The green cdrom light is blinking on our Sun Solaris server. I tried the eject command to eject cdrom: eject cdrom cdrom: No such file or directory bash-2.05# eject No default media available bash-2.05# eject cdrom0 cdrom0: No such file or directory The message log file shows: Oct 19... (6 Replies)
Discussion started by: agarcia19
6 Replies

9. HP-UX

Failed to open tape device /dev/rmt/0mn:Device busy (errno = 16)

Hi, Unable to make tape backup, please help. /opt/ignite/bin/make_tape_recovery -a /dev/rmt/?mn -I -v -m tar -x inc_entire=vg00 * Creating local directories for configuration files and archive. ======= 04/25/16 16:28:08 IST Started /opt/ignite/bin/make_tape_recovery. (Mon... (4 Replies)
Discussion started by: anuragr
4 Replies

10. UNIX for Beginners Questions & Answers

Mount : Device busy

mount -f nfs 1234:/export/ert /der/fr/ert mount : /der/fr/ert: device busy normally I will then do an fuser filesystem and kill the pids, which I did. now if I do an fuser /der/fr/ert I get the mount point and no pid > fuser /der/fr/ert /der/fr/ert: but it... (1 Reply)
Discussion started by: goya
1 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 09:38 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy