March 3, 2009

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

Posted in Solaris at 6:25 pm by alessiodini

I see this error after a reboot on a cluster node.
The complete message is :

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

changed /kernel/drv/md.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”

Mar 3 18:52:09 svc.startd[8]: svc:/system/boot-archive:default: Method “/lib/svc/method/boot-archive” failed with exit status 95.
Mar 3 18:52:09 svc.startd[8]: 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): Mar 3 18:52:11 Cluster.CCR: /usr/cluster/bin/scgdevs: _cladm failed. Pleaseensure the node is in cluster mode.
Mar 3 18:52:11 Cluster.CCR: /usr/cluster/bin/scgdevs: _cladm failed. Pleaseensure the node is in cluster mode.
Login incorrect

Root password for system maintenance (control-d to bypass):

damn it!!!

I run “boot -F failsafe” :

asuka>init 0
asuka>svc.startd: The system is coming down. Please wait.
svc.startd: 92 system services are now being stopped.
svc.startd: The system is down.
syncing file systems… done
Program terminated
ok boot -F failsafe
Resetting …

Sun Ultra 5/10 UPA/PCI (UltraSPARC-IIi 400MHz), No Keyboard
OpenBoot 3.31, 640 MB (60 ns) memory installed, Serial #16648126.
Ethernet address 8:0:20:fe:7:be, Host ID: 80fe07be.

Rebooting with command: boot -F failsafe
Boot device: /pci@1f,0/pci@1,1/ide@3/disk@0,0:a File and args: -F failsafe
SunOS Release 5.10 Version Generic_137137-09 64-bit
Copyright 1983-2008 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
Configuring devices.
Searching for installed OS instances…
SUNW,qfe2: 100 Mbps full duplex link up – internal transceiver
SUNW,qfe0: 100 Mbps full duplex link up – internal transceiver
WARNING: /pci@1f,0/pci@1/scsi@1,1/sd@3,0 (sd19):
reservation conflict

WARNING: /pci@1f,0/pci@1/scsi@1,1/sd@3,0 (sd19):
reservation conflict

WARNING: /pci@1f,0/pci@1/scsi@1,1/sd@3,0 (sd19):
reservation conflict

WARNING: /pci@1f,0/pci@1/scsi@1,1/sd@3,0 (sd19):
reservation conflict

WARNING: /pci@1f,0/pci@1/scsi@1,1/sd@3,0 (sd19):
reservation conflict

WARNING: /pci@1f,0/pci@1/scsi@1,1/sd@3,0 (sd19):
reservation conflict

WARNING: /pci@1f,0/pci@1/scsi@1,1/sd@3,0 (sd19):
reservation conflict

WARNING: /pci@1f,0/pci@1/scsi@1,1/sd@3,0 (sd19):
reservation conflict

An out of sync boot archive was detected on /dev/dsk/c0t0d0s0.
The boot archive is a cache of files used during boot and
should be kept in sync to ensure proper system operation.

Do you wish to automatically update this boot archive? [y,n,?] y
** /dev/rdsk/c0t0d0s0
** Last Mounted on /
** Phase 1 – Check Blocks and Sizes
** Phase 2 – Check Pathnames
** Phase 3a – Check Connectivity
** Phase 3b – Verify Shadows/ACLs
** Phase 4 – Check Reference Counts
** Phase 5 – Check Cylinder Groups

CORRECT BAD CG SUMMARIES FOR CG 0? y

CORRECTED SUPERBLOCK SUMMARIES FOR CG 0
CORRECTED SUMMARIES FOR CG 0
FRAG BITMAP WRONG
FIX? y

CORRECT GLOBAL SUMMARY
SALVAGE? y

Log was discarded, updating cyl groups
205118 files, 6465638 used, 11405076 free (240012 frags, 1395633 blocks, 1.3% fragmentation)

***** FILE SYSTEM WAS MODIFIED *****
Updating boot archive on /dev/dsk/c0t0d0s0.

Then i reboot and the system comes up without problems!

Advertisements

5 Comments »

  1. Gaurav Mittal said,

    Hi,

    I also found the same issue and i fixed it the same way. but my problem is little more here.

    After fixing the issue i created the image of the system, as reflashed the server with the Jump start server putting this image in the jump start server.

    After the flashing was over i got the same error.

    So this looks like the above fix is not consistent over flashing.

    Any idea how can we fix this.

    • alessiodini said,

      Hi,
      it’s strange. For fix this problem i need to analyze the system.
      If you want you can send me a explorer and i can analyze the components of the system like:
      – volume manager ( if used )
      – patch level
      – file that differ from the boot archive
      and other.

  2. Gaurav Mittal said,

    Hi,

    Thanks for replying.

    I have the explorer output but how to send that. I even have the screen capture of the flashing starting from “boot cdrom – install”.

    Kindly let me know the email ID of your so that I can send it.

    I am flashing the server with Custom DVD by cleaning up the product directory and putting the flash archive there. The DVD also contains the sysidcfg, profiles, rules,etc. So, its non-interactive flashing.

    Is there any chance that jumpstart code being old may not be compatible with the U6 flar image.

    Regards,
    Gaurav

  3. Gaurav Mittal said,

    I could find the issue and it was the jump start that I was using was way too old version of Solaris version, which was not compatable with Solaris 10 U6 flash archive. I extracted the jumpstart code from the Solaris10 U6 DVD and then every thing worked fine. Below is the link that tells how to extract the image.

    http://blogs.sun.com/jcecere/entry/creating_a_customized_boot_dvd

    but now the problem that i am facing is while doing the live upgrade it fails saying

    # Upgrading new environment, Please wait…
    [2009/04/30 16:57:26 upgradePlatform.sh] START : LUUPGRADE
    Validating the contents of the media .
    The media is a standard Solaris media.
    Validating the contents of the miniroot .
    Locating the flash install program.
    ERROR: The path does not exist.
    ERROR: The pfinstall library directory does not exist.
    [2009/04/30 16:57:41 upgradePlatform.sh] END : LUUPGRADE
    FAILED.
    : Could not upgrade boot environment.

    Not sure if you could help me in this.

    Regards,
    Gaurav Mittal


Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: