Ken Murach wrote: > Hi, > I am currently trying to restore a Solaris 10 OS from one of our production > servers from backup to an in-house DR solaris 10 box. > > I did not recover the following from the backup: > > /etc/defaultrouter > /etc/vfstab > /etc/path_to_instt > /etc/name_to_major > /dev/dsk > /dev/rdsk > /etc/netmask > > The restore was succesful and after the restore was done, I then had to > remove veritas (did a pkgrm on all the veritas packages). > > I then did a # rm -rf /dev/vx /etc/vx > > I then ran # devfsadm and # touch /reconfigure and rebooted the server. > > The server didn't come back up for the following: > > svc:/system/vxvm/vxvm-sysboot:default > State: maintenance > Reason: Start method failed repeatedly > > Not sure why svc is trying to start veritas because I did a pkgrm on all > veritas packages?? I had to log into single user mode and run: > > # svccfg delete system/vxvm/vxvm-sysboot:defaut (I also had to svccfg delete > about 5 other vxvm/vxfs services as well) > > I then ran the following command so I could disable ipfilter to get around > this error that I also was receiving: > > svc:/network/ipfilter:default > State: maintenance > Reason: start method exited with $SMF_EXIT_ERR_CONFIG. > > I ran: # svcadm disable network/ipfilter:default and rebooted the server > again. > > Now I'm not getting any svc errors, but the machine will still not boot up > and now I'm getting "Console login service(s) cannot run". > > Am I doing something wrong with my OS recovery?? Why does the svc still see > veritas even though all veritas packages have been removed?? Why am I now > getting this "Console login service(s) cannot run" message? > > Here is the output that I'm currently getting from the svcs -xv command: > > svc:/milestone/devices:default (device configuration milestone) > State: offline > Reason: Dependency svc:system/vxvm/vxvm-startup2 is absent > The error indicates milestone/device still has a dependency on vxvm-startup2 which is strange since svccfg delete fmri should have removed dependency relationship. I don't quite understand how we get here but we can try a couple of things?
- run 'svcprop manifest | grep sxvm-startup2' to see if it's indeed been deleted? - run 'svcadm refresh milestone/devices' then 'svcs -l milestone/devices' to see if that would update the dependency? Lastly you can always manually delete the dangling dependency by - run 'svccfg -s milestone/devices:default listprop' to get target dependency pg name - then 'svccfg delete dependency-pg-name' to delete it -tony
