The svc.startd could not start all the required services for the server to boot to level 3. I read the message and I had no clue. So I went back to my DVD from oracle and read about SMF after taking a nap to clear my head. It was tough.
So many services could not be started. They all went to the maintenance state. I copied a backup service repository to fix the problem....
See methods below:
1) Run this command and follow instructions
This did not work properly. So I did number 2.
2)
The repository database was built as if the system was starting for the first time after installation. It worked. There is another method to fix services in maintenance state but I did not use it because I had solved the problem. Oh I almost forgot. The reason the services where going to maintenance state was because I deleted the root entry in /etc/vfstab to do some practice work . How to boot a server if the root partition cannot be mounted from disk.
I had a power failure the other day and when my relatively new Solaris 10 machine rebooted it is thrown into maintenance mode.
I've found the following lines in the /var/adm/messages file, I'm assuming this is the root cause of the problem. However, I don't have the slightest idea on how to... (9 Replies)
I think that if the directory /tcb exists, HP-UX is in trusted mode and the passwd data is somewhere in /tcb/files/auth. But that's all I remember.
Also I think recent versions of HP-UX can have a /etc/shadow file. (0 Replies)
Hello All,
On solaris 10 server i could see the FTP service is in maintenance mode always :mad:
Could some assist?
svcs -xv
svc:/network/nfs/nlockmgr:default (NFS lock manager)
State: maintenance since Tue 28 Jul 2009 11:47:55 AM BST
Reason: Restarting too quickly.
See: Sun... (5 Replies)
Hi,
I have installed Hudson on a Solaris 11 server, using the installation instructions available at Paul Oswald: Hudson Solaris SMF Manifest.
When I perform svcs -l hudson, I get:
fmri svc:/application/hudson:default
name Hudson Continuous Build Server
enabled true... (4 Replies)
I have a Solaris 10 SunFire v880 machine and I'm having trouble with Samba.
Samba has worked on this machine but since the machine has been re-booted Samba has not worked.
Machine details are:
cat /etc/release
Solaris 10 10/08 s10s_u6wos_07b SPARC
Copyright 2008... (2 Replies)
I have seen similar threads on this issue, but I have not seen a fix. Basically I am getting a lot of rcp bind errors. Below find the output of "svcs -xv". not sure where to begin:
# svcs -xv
svc:/network/rpc/bind:default (RPC bindings)
State: maintenance since Fri May 25 14:13:18 2012... (14 Replies)
:confused:
when i tried to look the status of DNS-client, it is in maintenance mode.....
Please tell me how to bring it back to online mode...PLEASE TELL ME STEP BY STEP.... PLEASE...
:wall: (2 Replies)
Hi Guys
Required help in Redhat 6.1.
After installation of Redhat 6.1 in VMware system is not going in GUI mode.
please to solve the issue...
Thanks... (5 Replies)
Hi this may be a easy question to answer but thanks in advance.
So I was able to download the VIOS media from IBM and currently I am burning it to a cd/dvd right now.
The steps I've collected so far are from the net. can you please confirm and add on to the steps if there are any steps... (0 Replies)
i booted into maintenance mode
boot -- -s
from the console
I got the
Root password for system maintenance (control-d to bypass)
I did control -d
and then logged in
it told me that I was booting into boot -s
but after I did a control -d and logged in
who -r shows
... (9 Replies)
Discussion started by: goya
9 Replies
LEARN ABOUT BSD
fastboot
REBOOT(8) System Manager's Manual REBOOT(8)NAME
reboot - stopping and restarting the system
SYNOPSIS
/sbin/reboot [ -lqnhdarsfRD ]
/sbin/halt [ -lqndars ]
/sbin/fastboot [ -lqndarsRD ]
DESCRIPTION
2.11BSD is started by placing it in memory at location zero and transferring to its entry point. Since the system is not reentrant, it is
necessary to read it in from disk or tape each time it is to be boot strapped.
Rebooting a running system: When the system is running and a reboot is desired, shutdown(8) is normally used to stop time sharing and put
the system into single user mode. If there are no users then /sbin/reboot can be used without shutting the system down first.
Reboot normally causes the disks to be synced and allows the system to perform other shutdown activities such as resynchronizing hardware
time-of-day clocks. A multi-user reboot (as described below) is then initiated. This causes a system to be booted and an automatic disk
check to be performed. If all this succeeds without incident, the system is then brought up for multi-user operation.
Options to reboot are:
-l Don't try to tell syslogd(8) what's about to happen.
-q Reboot quickly and ungracefully, without shutting down running processes first.
-n Don't sync before rebooting. This can be used if a disk or the processor is on fire.
-h Don't reboot, simply halt the processor.
-d Dump memory onto the dump device, usually part of swap, before rebooting. The dump is done in the same way as after a panic.
-a Have the system booter ask for the name of the system to be booted, rather than immediately booting the default system (/unix).
-r Mount the root file system as read only when the system reboots. This is not supported by the kernel in 2.11BSD.
-s Don't enter multi-user mode after system has rebooted - stay in single user mode.
-f Fast reboot. Omit the automatic file system consistency check when the system reboots and goes multi-user. This is accomplished by
passing a fast reboot flag on to the rebooting kernel. This currently prevents the use of -f flag in conjunction with the -h (halt)
flag.
-D Set the autoconfig(8) debug flag. This is normally not used unless one is debugging the autoconfig program.
-R Tells the kernel to use the compiled in root device. Normally the system uses the device from which it was booted as the
root/swap/pipe/dump device.
Reboot normally places a shutdown record in the login accounting file /usr/adm/wtmp. This is inhibited if the -q or -n options are
present. Note that the -f (fast reboot) and -n (don't sync) options are contradictory; the request for a fast reboot is ignored in this
case.
Halt and fastboot are synonymous with ``reboot -h'' and ``reboot -f'', respectively.
Power fail and crash recovery: Normally, the system will reboot itself at power-up or after crashes if the contents of low memory are
intact. An automatic consistency check of the file systems will be performed, and unless this fails, the system will resume multi-user
operations.
SEE ALSO autoconfig(8), sync(2), utmp(8), shutdown(8), syslogd(8)3rd Berkeley Distribution May 24, 1996 REBOOT(8)