Solaris 10 Boot-archive Issue during reboot

The boot-archive service, svc:/system/boot-archive, is managed by SMF. This procedure shows how to update the boot archive when an inconsistent archive is detected during the boot process. Clearing the service works the same as running the boot -F failsafe command. Note that when you use this method to update the boot archives, there is no need to boot the failsafe archive or run the bootadm update-archive command. This command runs silently after the boot-archive service has been cleared.

Note :  –
The preferred method for correcting an inconsistent boot archive is to boot the system in failsafe mode. See the following references for instructions on booting the failsafe archive:
For SPARC based systems, see Booting a SPARC Based System From the Network.
For x86 based systems, see Booting the Failsafe Archive on an x86 Based System.


1.    During the process of booting the system, if a warning similar to the following is displayed, ignore the warning.

WARNING: The following files in / differ from the boot archive:

    changed file-name
2.    The system will enter system maintenance mode.
3.    Clear the boot-archive service by typing the following command:

# svcadm clear system/boot-archive
4.    After this command is run, the bootadm update-archive command runs silently. If the boot archive is updated successfully, the system is rebooted.
5.    Verify the service is running.

# svcs boot-archive
STATE          STIME    FMRI
online          9:02:38 svc:/system/boot-archive:default

Example 13–1 SPARC: Updating an inconsistent Boot Archive by Clearing the Boot-Archive Service


screen not found.
Can't open input device.
Keyboard not present.  Using ttya for input and output.

Sun Enterprise 220R (2 X UltraSPARC-II 450MHz), No Keyboard
OpenBoot 3.23, 1024 MB memory installed, Serial #13116682.
Ethernet address 8:0:20:c8:25:a, Host ID: 80c8250a.



Rebooting with command: boot                                         
Boot device: /pci@1f,4000/scsi@3/disk@1,0:a  File and args:
SunOS Release 5.10 64-bit
Copyright 1983-2007 Sun Microsystems, Inc.  All rights reserved.
Use is subject to license terms.
DEBUG enabled
misc/forthdebug (507204 bytes) loaded
Hostname: marnie

WARNING: The following files in / differ from the boot archive:

    changed /kernel/drv/sd.conf

The recommended action is to reboot to the failsafe archive to correct
the above inconsistency. To accomplish this, on a GRUB-based platform,
reboot and select the "Solaris failsafe" option from the boot menu.
On an OBP-based platform, reboot then type "boot -F failsafe". Then
follow the prompts to update the boot archive. Alternately, to continue
booting at your own risk, you may clear the service by running:
"svcadm clear system/boot-archive"

Nov 21 15:47:20 svc.startd[100004]: svc:/system/boot-archive:default: Method
"/lib/svc/method/boot-archive" failed with exit status 95.
Nov 21 15:47:20 svc.startd[100004]: system/boot-archive:default failed fatally:
transitioned to maintenance (see 'svcs -xv' for details)
Requesting System Maintenance Mode
(See /lib/svc/share/README for more information.)
Console login service(s) cannot run

Root password for system maintenance (control-d to bypass):
single-user privilege assigned to /dev/console.
Entering System Maintenance Mode

Nov 21 15:48:36 su: 'su root' succeeded for root on /dev/console
Sun Microsystems Inc.   SunOS 5.10,
2007
.
.
.#
#
# svcadm clear system/boot-archive
#
# NIS domain name is mpklab.sfbay.sun.com
/dev/rdsk/c0t1d0s5 is clean
Reading ZFS config: done.
#
# bootadm update-archive
# svcs boot-archive
STATE          STIME    FMRI
online          9:02:38 svc:/system/boot-archive:default

No comments:

Usage of Man Command

To read a manual page for a Unix command, one can use
 
man <command_name> 

At a shell prompt: for example, "man ftp". In order to simplify navigation through the output, man generally uses the less terminal pager.Pages are traditionally referred to using the notation "name(section)": for example, ftp(1). The same page name may appear in more than one section of the manual, as when the names of system calls, user commands, or macro packages coincide. Examples are man(1) and man(7), or exit(2) and exit(3). The syntax for accessing the non-default manual section varies between different man implementations. On Linux and *BSD, for example, the syntax for reading printf(3) is
 
man 3 printf
 
which searches for printf in section 3 of the man pages.


For More Info : http://en.wikipedia.org/wiki/Man_page 
 
No comments:

Solaris Tunable Parameters

Solaris Kernel Tunable Parameters


  • General Kernel and Memory Parameters
  • fsflush and Related Parameters
  • Process-Sizing Parameters
  • Paging-Related Parameters
  • Swapping-Related Parameters
  • Kernel Memory Allocator
  • General Driver Parameter
  • General I/O Parameters
  • General File System Parameters
  • UFS Parameters
  • TMPFS Parameters
  • Pseudo Terminals
  • STREAMS Parameters
  • System V Message Queues
  • System V Semaphores
  • System V Shared Memory
  • Scheduling
  • Timers
  • sun4u or sun4v Specific Parameters
  • Solaris Volume Manager Parameters
  • Network Driver Parameters
     
  • NFS Tunable Parameters
    • Tuning the NFS Environment
    • NFS Module Parameters
    • nfssrv Module Parameters
    • rpcmod Module Parameters

       
    • Internet Protocol Suite Tunable Parameters
      • IP Tunable Parameters
      • TCP Tunable Parameters
      • UDP Tunable Parameters
      • IPQoS Tunable Parameter
      • SCTP Tunable Parameters
      • Per-Route Metrics
No comments:
Subscribe to: Posts (Atom)