Sponsored Content
Operating Systems Solaris Sun Blade 100 cdrom problems... Post 302195885 by arjunreddy3 on Friday 16th of May 2008 06:16:28 AM
Old 05-16-2008
cdroms are automaticly mounted by vold. no way to store info vfstab.

once againg u restart the vold service.
#cd /etc/init.d
#sh volmgt stop
#sh volmgt start
#cd
 

10 More Discussions You Might Find Interesting

1. Solaris

Anyone has problems with new Blade 2500????

Hi guys, I am a new member here. This is my first post. I try to purchase some new Blade 2500 for the company. However, the vendor suggests me to get Blade 2000 instead. The vendor said he has many problems with new Silver Blade 2500's. Has anyone here had simlar experience with blade 2500?... (4 Replies)
Discussion started by: facaizhu
4 Replies

2. UNIX for Dummies Questions & Answers

sun blade 100 test-all frozen at pci@1f,0/usb/c,3

platform: sunblade 100 Solaris 10. When running a test-all from the ok prompt on this new (to me) system, it locks up at pci@1f,0/usb/c,3. It's been there for about 25 minutes. I do have a usb keyboard and mouse attached, both are known good. There is no flash stick/ thumb drive... (0 Replies)
Discussion started by: montana77
0 Replies

3. Solaris

Sun Blade 100 Disk Compatibility

It's me again, I was taking my Sun Blade 100 apart last night to see what kind of drive I have. It is a Seagate ST320011A Barracuda ATA IV 20 GB 7200 RPM Ultra ATA/100 IDE. Now 20 gig ain't all that big anymore and I got to thinking about putting a couple bigger drives in there. although I... (7 Replies)
Discussion started by: BrewDudeBob
7 Replies

4. Solaris

Sun Blade 100 Memory Upgrade

Hi, I've been a member for a while but have never posted. I have a Sun Blade 100 desktop and I just installed Solaris 10 and it is unbearably slow. I only have 128 Meg of RAM and need to upgrade. I have searched and found many online resources that have RAM, but I was wondering if anyone has... (12 Replies)
Discussion started by: BrewDudeBob
12 Replies

5. UNIX for Dummies Questions & Answers

Serial Connection sun blade 100 to pc

Hi, If someone please help as my efforts been exhausted in connecting my sun blade 100 serial to my pc. I am using null modem with DB9(female) in sun blade and DB9(female, using gender change) in pc. I am trying both hyper/putty 9600 8 N 1 configurations. Thanks (2 Replies)
Discussion started by: younics
2 Replies

6. Solaris

Sun Blade 150 not a Sun?

I have recently re-installed Solaris 10 on a Sun Blade 150 followed by a patch set (10_Recommended) dated 2011.12.05. I have just noticed /bin/sun now returns false, rather than true. See below. $ uname -a SunOS myblade1 5.10 Generic_147440-07 sun4u sparc SUNW,Sun-Blade-100 $ /bin/sparc &&... (1 Reply)
Discussion started by: apmcd47
1 Replies

7. UNIX for Dummies Questions & Answers

Reinstalling Solaris 9 on Sun Blade 100

For the past ten years I have owned a blade 100, and I had Solaris 9 running on it. Due to the fact, 9 is woefully out of date, I wanted to try 10, but 10 needed more ram, so I beefed up the ram to the full 2 gig. I have two 15 gig ide drives in the box (stock drives). But unfortunately solaris... (2 Replies)
Discussion started by: RichardET
2 Replies

8. Solaris

Sun Blade 150 wont boot off cdrom

Hello, Ive just aquired a blade 150 off ebay.Im new to suns and are having a problem getting it to boot off the cdrom.Openboot continuously tries to do a network boot and I cant enter any commands.Im using an average pc keyboard and it definetly works.Thanks for any help.:wall: (3 Replies)
Discussion started by: chucky
3 Replies

9. Solaris

Memory problems in Blade 6340

We have a 6000 chassis with three blades in it. Two of the blades have "Oracle/Sun" memory in them with no complaints. The third blade is populated with Dataram dimms. That 3rd blade continues to flag a slot bad. Oracle has said they would not support the blade with Dataram memory it it. I didn't... (1 Reply)
Discussion started by: brownwrap
1 Replies

10. Solaris

Execution problems with sun blade 150

hello i have a forte gamma camera Philips device . and its a medical device. this medical device is came with sun blade 150 pc and pegasys is printed on the sun blade pc .the problem is when i switched the power on , the sun blade runs and a white screen appear with the information about the... (6 Replies)
Discussion started by: moh_abaloo
6 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 04:48 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy