Okay, Peter, here's what I get using the ps command and looking for the vold process. Do
you get something similar?
gecko:miked# ps -ef | grep -v grep | grep vol
root 235 1 0 Feb 12 ? 0:48 /usr/sbin/vold
If you do NOT get this, then you are not running the important bit.
Check for a file /etc/vold.conf - mine looks like this:
#
# Volume Daemon Configuration file
#
# Database to use (must be first)
db db_mem.so
# Labels supported
label dos label_dos.so floppy pcmem
label cdrom label_cdrom.so cdrom
label sun label_sun.so floppy pcmem
# Devices to use
use cdrom drive /dev/rdsk/c*s2 dev_cdrom.so cdrom%d
use floppy drive /dev/rdiskette[0-9] dev_floppy.so floppy%d
use pcmem drive /dev/rdsk/c*s2 dev_pcmem.so pcmem%d forceload=true
# Actions
insert dev/diskette[0-9]/* user=root /usr/sbin/rmmount
insert dev/dsk/* user=root /usr/sbin/rmmount
eject dev/diskette[0-9]/* user=root /usr/sbin/rmmount
eject dev/dsk/* user=root /usr/sbin/rmmount
notify rdsk/* group=tty user=root /usr/lib/vold/volmissing -p
# List of file system types unsafe to eject
unsafe ufs hsfs pcfs
--------------------------------------------------------------------------------------------------------------------
Now, if you are NOT ruinning the vold process, type:
/usr/sbin/vold 1>/dev/console 2>&1 &
which should start it. Check it is running with the ps command as above.
Is it started on boot? Check, using: ls -l /etc/rc2.d/*volmgt
You should get something similar to:
-rwxr--r-- 2 root sys 524 May 3 1996 /etc/rc2.d/S92volmgt
Now... if the vold process is running, try inserting a CD and watching the lights. They
probably will flash for a few seconds. Wait til they stop for about 5-10 secs. Now do a
df. I get this in my listing:
/cdrom/patches_4_0_2_d1(/vol/dev/dsk/c0t6d0/patches_4_0_2_d1): -1 blocks -1 files
If I do a "df -k" I get:
/vol/dev/dsk/c0t6d0/patches_4_0_2_d1 661116 -1 0 100% /cdrom/patches_4_0_2_d1
Yours will be different but similar... I hope.
Report back when you can....