Error during boot, V-5-1-0 vxvm:vxconfigd: ERROR: Invalid records in file /etc/vx/

  • Article ID:100024807
  • Modified Date:
  • Product(s):


Boot drive is encapsulated and mirrored.  System had previously panic'ed due to memory issues and had been shutdown a few more times ungracefully in the process of replacing the memory.  After memory replacement, the boot produced an error and did not complete.

Error Message

NOTICE: VxVM vxdmp V-5-0-34 added disk array DISKS, datype = Disk


NOTICE: VxVM vxdmp V-5-3-1700 dmpnode 117/0x0 has migrated from enclosure FAKE_ENCLR_SNO to enclosure DISKS


Jun 7 16:21:03 vxvm:vxconfigd: V-5-1-0 vxvm:vxconfigd: ERROR: Invalid records in file /etc/vx/


OS based issue:

Sun Fire V245, No Keyboard
Copyright 2007 Sun Microsystems, Inc.  All rights reserved.
OpenBoot 4.25.10, 8192 MB memory installed, Serial #78422514.
Ethernet address 0:14:4f:ac:a1:f2, Host ID: 84aca1f2.
  Rebooting with command: boot -s
Boot device: /pci@1e,600000/pci@0/pci@a/pci@0/pci@8/scsi@1/disk@0,0:a  File and args: -s
SunOS Release 5.10 Version Generic_142900-03 64-bit
Copyright 1983-2009 Sun Microsystems, Inc.  All rights reserved.
Use is subject to license terms.
Hardware watchdog enabled
svc.configd: smf(5) database integrity check of:    




 failed. The database might be damaged or a media error might have
  prevented it from being verified.  Additional information useful to
  your service provider is in:




The system will not be able to boot until you have restored a working
database.  svc.startd(1M) will provide a sulogin(1M) prompt for recovery purposes.  The command:




can be run to restore a backup version of your repository.  See for more information.


Requesting System Maintenance Mode
svc.configd exited with status 102 (database initialization failure)


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


Customer remounted root filesystem read/write and ran /lib/svc/bin/restore_repository to restore OS database.


1)  Boot to failsafe mode

# boot -F failsafe


2)  Manually unencapsulate boot drive (see #3 in Related Articles below)

(CD boot not required in Solaris 10; failsafe boot used instead)

3)  Remounted root filesystem read/write

# mount -o remount,rw /


4)  Restore the OS database

# /lib/svc/bin/restore_repository


5)  Destroy rootdg diskgroup

# vxdg destroy rootdg


6)  Rebuild DMP information and device tree

      (may not be necessary but ensures rebuild of necessary /etc/vx/*.info files)

7) Remove the Volume Manager tags from the root disk

# /etc/vx/bin/vxdiskunsetup c#t#d#

8)  Use vxdiskadm option 2 to re-encapsulate boot disk.

# vxdiskadm

9)  Use vxdiskadm option 1 to add secondary drive to rootdg.

# vxdiskadm

10)  Use vxdiskadm option 6 to mirror boot disk to secondary drive.

# vxdiskadm


Applies To

Solaris 10 (sparc)

Storage Foundation 5.0


While this issue was seen for this specific environment, it is likely an issue that may be seen in other platforms.  It is probable that this issue as defined is a Solaris issue, the concept of an OS boot issue may not be obvious when the boot disk is encapsulated.

Related Articles

3 ways to unencapsulate (including manual unencapsulation)

Was this content helpful?

Get Support