Troubleshooting a recalcitrant vold

Troubleshooting a recalcitrant vold

Post by Greg Menk » Fri, 11 Apr 2003 11:53:35



I am adminning an Ultra 2 and an Ultra 5, both with Solaris 9 9/02,
with recommended patches up to about December 2002.  Vold works fine
on the Ultra 5, but not on the Ultra 2.  Specifically, the Ultra 5
will properly automount a hsfs cd whereas the Ultra 2 will not.  I
know the Ultra 2 cdrom works because if I kill vold, I can manually
mount the cdrom and it works fine.

When I start vold on the Ultra 2, it seems to make it partway through
mounting the cd and gets stuck somewhere.  volrmmount -i indicates "No
default media available", which might be relevant.  I can see vold hit
the cd when it starts, suggesting the config files are at least
plausible.  volrmmount -d only tells me I have "nothing inserted"
instead of some kind of default device.

Increasing the vold log level increases the quantity of undecipherable
messages in /var/adm/vold, but doesn't reveal anything apparently
relevant.

I'm guessing the problem is either related to the scsi cdrom or
perhaps its some kind of Ultra 2-ism.  Any suggestions/hints are
appreciated.

Thanks,

Gregm

 
 
 

Troubleshooting a recalcitrant vold

Post by Dave Uhrin » Fri, 11 Apr 2003 12:09:14



> I'm guessing the problem is either related to the scsi cdrom or
> perhaps its some kind of Ultra 2-ism.  Any suggestions/hints are
> appreciated.

Did you comment this line in /etc/inet/inetd.conf?

100155/1        tli     rpc/ticotsord   wait    root    /usr/lib/smedia/rpc.smserverd rpc.smserverd

 
 
 

Troubleshooting a recalcitrant vold

Post by Greg Menk » Fri, 11 Apr 2003 21:23:02




> > I'm guessing the problem is either related to the scsi cdrom or
> > perhaps its some kind of Ultra 2-ism.  Any suggestions/hints are
> > appreciated.

> Did you comment this line in /etc/inet/inetd.conf?

> 100155/1        tli     rpc/ticotsord   wait    root    /usr/lib/smedia/rpc.smserverd rpc.smserverd

Yes- that fixed it.  Thanks!

Gregm

 
 
 

1. Using "/usr/sbin/vold -d /vold" breaks "eject cdrom"


We have the same problem as you and we also redirect the volume manager
to use /vold instead of /vol.  I can usually get the cdrom to eject by
using "eject /vold/dev/rdsk/c0t6/*" or something like that.  To get floppies
to eject, use "eject /vold/dev/rdiskette0"
--

"You call me sweet, like I'm some kind of cheese" - Brian May

2. How do I load a module at start up?

3. Recalcitrant Floppy!!!

4. dial on demand

5. vold with ZIP disk?

6. Help Please

7. vold won't start: vol_init failed (can't communicate with kernel)

8. Need help with mouse lockup.

9. Possible vold problem: please help.

10. Cachefs with vold

11. vold broken vis-a-vis floppies?

12. Q: vold is not running and crontab/ed

13. vold automounting floppy