Vol_init

Loaded Solaris 10/08. Upon logging in I'm getting errors stating fatal: vol_init: already a daemon running. Then the volfs just goes into maintenance. I have tried clearing the service through svcadm but immediately on the console I see 10 messages of fatal: vol_init: already a dameon running. The log is pretty much no help. I have checked to make sure /var/adm is there and writeable. Also there is a vold.log file and writeable. The other thing I noticed is I can type ls but when I do an ls -l it freezes and when I run format it shows two disks but when I go to look at the partitions on the umounted disk or the mounted disk it just freezes.
Also getting NFS server for Volume Management (/vol) not responding still trying and NFS get attr failed for Server for Volume management (/vol); error 16 (RPC: Failed (unspecefied error)).
The only thing I can think of is after I installed it and rebooted the Solaris 10/08 dvd stayed in the drive. Would this cause all the problems.
Thanks.
Edited by: weocl on Jan 27, 2009 12:10 PM

Hi frnds,
I am able to mount the CD manually, not via vold. meanwhile i have registered a case with SUN also.
Steps which i followed:
Determine the name of the device by entering the following command:
ls -al /dev/sr* |awk '{print "/" $11}'
This command returns the 3 name of the CD-ROM device. In this example, the command returns the string /dev/dsk/c0t6d0s2.
Enter the following commands to mount the CD-ROM: 3
mkdir -p /cdrom/unnamed_cdrom
mount -F hsfs -o ro /dev/dsk/c0t6d0s2 /cdrom/unnamed_cdrom
where /dev/dsk/c0t6d0s2 represents the name of the device that was returned 3 in the preceding step and /cdrom/unnamed_cdrom represents the CD-ROM 3 mount directory
regards,
Alok

Similar Messages

  • Vol_init failed (can't communicate with kernel)

    Hi,
    I'm running Sol 2.8 on a sparc SUNW, Sun blade 1000 and having problem
    mounting the CDROM. I tried to start vold but
    I'm seeing that /var/adm/messages is logging "vol_init
    failed" and "Can't communicate with kernel". I've seen
    similar error in the archive but no summary.
    Pls help me on this....
    Amit

    check if the following daemon is running. Using command ps -ef | grep vold
    if it isn't run the following command:
    /etc/init.d/volmgt start
    This will restart volume management and should automatically mount the cdrom whenb inserted into the drive

  • Vol_init failed       so i cant access media.

    Hi
    I'm running Sol 2.8 on a sparc SUNW,Sun-Blade-1000 and having problem
    mounting the cdrom. I tried to start vold but
    I'm seeing that /var/adm/messages is logging "vol_init
    failed" and "Can't communicate with kernel". I've seen
    similar error in the archive but no summary. TIA. Will
    summarize.
    Regards
    Amit Agrawal

    I tried at ok prompt
    OK boot -r
    it worked.
    Amit

  • Volfs in maintenance state

    I have an issue with volfs.
    volfs is all the time in maintenance state ( I have had no chance yet to reboot system).
    I tried to use "clear" but it didnt help
    Hera are some details:
    # svcs -a /system/filesystem/volfs
    svcs: -a ignored when used with arguments.
    STATE          STIME    FMRI
    maintenance    12:45:18 svc:/system/filesystem/volfs:default
    # svcs -d /system/filesystem/volfs
    STATE          STIME    FMRI
    online         kw_22    svc:/network/rpc/bind:default
    online         kw_22    svc:/network/rpc/smserver:default
    online         15:25:05 svc:/system/filesystem/local:default
    # svcs -vx /system/filesystem/volfs
    svc:/system/filesystem/volfs:default (Volume Management filesystem)
    State: maintenance since  7 maja 2010 12:45:18 CEST
    Reason: Restarting too quickly.
       See: http://sun.com/msg/SMF-8000-L5
       See: man -M /usr/man -s 7FS volfs
       See: /var/svc/log/system-filesystem-volfs:default.log
    Impact: This service is not running.and here is a log:
    cat  /var/svc/log/system-filesystem-volfs:default.log
    [ maj  7 12:45:16 Enabled. ]
    [ maj  7 12:45:16 Executing start method ("/lib/svc/method/svc-volfs start") ]
    [ maj  7 12:45:16 Method "start" exited with status 0 ]
    Fri May  7 12:45:16 2010 fatal: vol_init: already a daemon running
    [ maj  7 12:45:16 Stopping because all processes in service exited. ]
    [ maj  7 12:45:16 Executing stop method (:kill) ]
    [ maj  7 12:45:16 Executing start method ("/lib/svc/method/svc-volfs start") ]
    [ maj  7 12:45:16 Method "start" exited with status 0 ]
    Fri May  7 12:45:16 2010 fatal: vol_init: already a daemon running
    [ maj  7 12:45:16 Stopping because all processes in service exited. ]
    [ maj  7 12:45:16 Executing stop method (:kill) ]
    [ maj  7 12:45:16 Executing start method ("/lib/svc/method/svc-volfs start") ]
    [ maj  7 12:45:16 Method "start" exited with status 0 ]
    Fri May  7 12:45:16 2010 fatal: vol_init: already a daemon running
    [ maj  7 12:45:17 Stopping because all processes in service exited. ]
    [ maj  7 12:45:17 Executing stop method (:kill) ]
    [ maj  7 12:45:17 Executing start method ("/lib/svc/method/svc-volfs start") ]
    [ maj  7 12:45:17 Method "start" exited with status 0 ]
    Fri May  7 12:45:17 2010 fatal: vol_init: already a daemon running
    [ maj  7 12:45:17 Stopping because all processes in service exited. ]
    [ maj  7 12:45:17 Executing stop method (:kill) ]
    [ maj  7 12:45:17 Executing start method ("/lib/svc/method/svc-volfs start") ]
    [ maj  7 12:45:17 Method "start" exited with status 0 ]
    Fri May  7 12:45:17 2010 fatal: vol_init: already a daemon running
    [ maj  7 12:45:17 Stopping because all processes in service exited. ]
    [ maj  7 12:45:17 Executing stop method (:kill) ]
    [ maj  7 12:45:17 Executing start method ("/lib/svc/method/svc-volfs start") ]
    [ maj  7 12:45:17 Method "start" exited with status 0 ]
    Fri May  7 12:45:17 2010 fatal: vol_init: already a daemon running
    [ maj  7 12:45:17 Stopping because all processes in service exited. ]
    [ maj  7 12:45:17 Executing stop method (:kill) ]
    [ maj  7 12:45:17 Executing start method ("/lib/svc/method/svc-volfs start") ]
    [ maj  7 12:45:17 Method "start" exited with status 0 ]
    Fri May  7 12:45:17 2010 fatal: vol_init: already a daemon running
    [ maj  7 12:45:17 Stopping because all processes in service exited. ]
    [ maj  7 12:45:18 Executing stop method (:kill) ]
    [ maj  7 12:45:18 Executing start method ("/lib/svc/method/svc-volfs start") ]
    [ maj  7 12:45:18 Method "start" exited with status 0 ]
    Fri May  7 12:45:18 2010 fatal: vol_init: already a daemon running
    [ maj  7 12:45:18 Stopping because all processes in service exited. ]
    [ maj  7 12:45:18 Executing stop method (:kill) ]
    [ maj  7 12:45:18 Executing start method ("/lib/svc/method/svc-volfs start") ]Does anyone had similar situation ? How can I bring it back to ENABLE state ?

    Your problem comes from
    Fri May  7 12:45:18 2010 fatal: vol_init: already a daemon runningIt is very likely that the daemon was started outside the service control. Try to stop if and the clear the maintenance mode.
    # ps -ef|grep -i vold
    # kill ....
    # svcadm clear volfs
    # svcs -l volfsCheers
    Andy

  • BOOTPS in maintenance state

    The svc:/network/bootps/udp:default is in maintenance state and each time I use the svcadm clear command to remove this state, it changes to an online state. But when I run the inetadm command again, its back to maintenance state. I ran the svcs -vx command and I get this:
    svc:/network/bootps/udp:default (bootps)
    State: maintenance since Fri Sep 09 15:27:01 2005
    Reason: Restarter svc:/network/inetd:default gave no explanation.
    See: http://sun.com/msg/SMF-8000-9C
    Impact: This service is not running.
    I looked at the following link but it did not help me much at all: http://sun.com/msg/SMF-8000-9C
    The /etc/inet/inetd.conf looks like this:
    #100235/1 tli rpc/ticotsord wait root /usr/lib/fs/cachefs/cachefsd cachefsd"
    #TFTPD - tftp server (primarily used for booting)
    tftp dgram udp6 wait root /usr/sbin/in.tftpd in.tftpd -s /tftpboot
    # Sun ToolTalk Database Server
    #100083/1 tli rpc/tcp wait root /usr/dt/bin/rpc.ttdbserverd rpc.ttdbserverd
    # rpc.cmsd is a data base daemon which manages calendar data backed
    # by files in /var/spool/calendar
    #100068/2-5 dgram rpc/udp wait root /usr/dt/bin/rpc.cmsd rpc.cmsd
    bootps dgram udp wait root /usr/sbin/bootpd bootpd
    Is there anything wrong with this? How can I permantly keep the bootp service to online state. Please help. Thanks.

    Your problem comes from
    Fri May  7 12:45:18 2010 fatal: vol_init: already a daemon runningIt is very likely that the daemon was started outside the service control. Try to stop if and the clear the maintenance mode.
    # ps -ef|grep -i vold
    # kill ....
    # svcadm clear volfs
    # svcs -l volfsCheers
    Andy

  • Core install - no man pages & can not eject cdrom solaris 10

    I did a custom core install for solaris 10. I thought I installed all the packages needed, as well as all the dependacies.
    I have no man pages!
    I can not eject cdrom, I get an error:
    "No such file or directory"
    When I type vold I also get an error:
    "fatal: vol-init failed (cant communicate with kernel)
    I can not start in services by:
    svcadm enable vold
    How do I fix?

    I have fixed the vol_init error
    touch /reconfigure;init 6
    What cd is the man pages on for solaris 10
    would it just be pkgadd -d /yada/yada...

Maybe you are looking for