|
From: Michelle on 6 May 2008 17:32 I am using Solaris 10, x86. As I boot up my computer named "server1", I see these error messages below. Does anyone know what the problem is and how to fix this? By the way, my computer still boots up OK and is functional at the moment. May 6 11:51:40 server1 svc.startd[7]: [ID 652011 daemon.warning] svc:/ system/filesystem/volfs:default: Method "/lib/svc/method/svc-volfs start" failed with exit status 96. May 6 11:51:40 server1 svc.startd[7]: [ID 748625 daemon.error] system/ filesystem/volfs:default misconfigured: transitioned to maintenance (see 'svcs -xv' for details)
From: Gary Mills on 6 May 2008 18:11 In <06b1070b-e135-4808-929a-002aae2f16dc(a)i36g2000prf.googlegroups.com> Michelle <serendipity1276(a)yahoo.com> writes: >As I boot up my computer named "server1", I see these error messages >below. >May 6 11:51:40 server1 svc.startd[7]: [ID 652011 daemon.warning] svc:/ >system/filesystem/volfs:default: Method "/lib/svc/method/svc-volfs >start" failed with exit status 96. >May 6 11:51:40 server1 svc.startd[7]: [ID 748625 daemon.error] system/ >filesystem/volfs:default misconfigured: transitioned to maintenance >(see 'svcs -xv' for details) In that case, you run `svcs -l svc:/system/filesystem/volfs:default' to find the log file for that service, and then look at that log file for the reason. You do the same thing for the other service. -- -Gary Mills- -Unix Support- -U of M Academic Computing and Networking-
From: Reginald Beardsley on 7 May 2008 08:09 Michelle wrote: > I am using Solaris 10, x86. > > As I boot up my computer named "server1", I see these error messages > below. > Does anyone know what the problem is and how to fix this? > > By the way, my computer still boots up OK and is functional at the > moment. > > > > May 6 11:51:40 server1 svc.startd[7]: [ID 652011 daemon.warning] svc:/ > system/filesystem/volfs:default: Method "/lib/svc/method/svc-volfs > start" failed with exit status 96. > > May 6 11:51:40 server1 svc.startd[7]: [ID 748625 daemon.error] system/ > filesystem/volfs:default misconfigured: transitioned to maintenance > (see 'svcs -xv' for details) Oops. My fault. This is the result of renaming volfs.config as I suggested. The startup files for older releases of Solaris 10 used the file's existence to control starting volfs. However, they changed the method for controlling volfs in more recent releases. I hadn't updated at the time you asked. 1) rename vold.config_disabled (or whatever you called it) to vold.config 2) disable volfs using the svcadm facility My apologies for the misinformation. Have Fun! rhb
|
Pages: 1 Prev: UNIX - Let’s get together and feel all right Next: Thanks for everyone's help in this forum! |