Hi All,
I got a big problem here.
While setting up a sun cluster, I accidentally tried out "bootadm update-archive" as I was unable to bring the cluster up.
After which, i tried a reconfiguration reboot.
Now The system is always booting into maintanence mode with error message
"svc:/system/boot-archive:default: Method or service exit timed out.
Killing contract 31.
svc:system/boot-archive:default: Method "/lib/svc/methodboot-archive" failed due to signal KILL.
svc startd[7]: system/boot-archive:default failed: transitioned to maintenance."
Steps I have tried out:
1) Tried to rebuild boot-archive thru 'failsafe'
2) Tried svcadm clear system/boot-archive
svcs -x boot-archive shows the service is in maintanence mode with 75 dependant services not running.
Nothing worked out:mad:
Being a newbie, ur help at this point will be really appreciated.
Thanx in advance,
Manu
What does this command show:
tail -20 /etc/svc/volatile/system-boot-archive:default.log
1 Like
Executing start method ("/lib/svc/method/boot-archive")
Method or service exit timed out. Killing contract 12
Method start failed due to signal KILL
------------------------------------------
Same message repeated with contract 15, 17 ......
In maintenance mode try:
svccfg -s boot-archive setprop start/timeout_seconds=180
Then
init 6
I am getting the following error message:
"svccfg: Unexpected libscf error on line 11040 of svccfg_libscf.c: backend is read only"
-Manu
What does this say (post full output):
mount
/ on pci@0,0/pci8086,25e3@3/pci103c,3234@0/sd@0,0: a read/write/setuid/devices/dev=800080 on Wed Dec31 16:00:00 1969
/devices on /devices read/write/setuid/devices/dev=47c0000 on Thu Mar 3 12:09:58 2011
/system/contract on ctfs read/write/setuid/devices/dev=4840001 on Thu Mar 3 12:09:58 2011
/proc on proc read/write/setuid/devices/dev=4800000 on Thu Mar 3 12:09:58 2011
/etc/mnttab on mnttab read/write/setuid/devices/dev=4880001 on Thu Mar 3 12:09:58 2011
/etc/svc/volatile on swap read/write/setuid/devices/xattr/dev=48c0001 on Thu Mar 3 12:09:58 2011
/system/object on objfs read/write/setuid/devices/dev=4900001 on Thu Mar 3 12:09:58 2011
/etc/dfs/sharetab on sharefs read/write/setuid/devices/dev=4940001 on Thu Mar 3 12:09:58 2011
/lib/libc.so.1 on /usr/lib/libc_hwcap1.so.1 read/write/setuid/devices/dev=800080 on Thu Mar 3 12:09:58 2011
Ok... Try this: boot with failsafe, then when it asks about mounting root filesystem under /a say "y". Then run "svccfg" in interactive mode:
svccfg
And while at svc:> prompt run those commands:
svc:> repository /a/etc/svc/repository.db
svc:> select boot-archive
svc:/system/boot-archive> setprop start/timeout_seconds=180
svc:/system/boot-archive> quit
Then reboot the server with
init 6
Hmmm.. Tried that also
Still same result...
But I have a clue now
/boot/solaris/filelist.ramdisk have the following entry upon creating the cluster.
"etc/cluster/nodeid"
But wen verified, the file is not present under /etc/cluster.
I tried to remove that entry.
But the file opens as read only in failsafe.
Please help me out.