VxVM vxconfigd ERROR V-5-1-1589 enable failed: Volboot file not loaded

VxVM vxconfigd NOTICE V-5-1-11538 volboot: Upgrading protocol version (100) in volboot file to the
  highest version (90) automatically. Might be result of an upgrade.
VxVM vxconfigd ERROR V-5-1-1589 enable failed: Volboot file not loaded
        transactions are disabled

The following workaround can be implemented to restart vxconfigd by recreating the /etc/vx/volboot:

# vxdctl stop ; cat /etc/vx/volboot ; rm /etc/vx/volboot ; vxconfigd -r reset ; vxdctl init ; vxdctl enable

Where "vxconfigd -r reset" is not possible, "vxconfigd -d" can be used.

BEFORE:

root:auksvbms:/root # cat /etc/vx/volboot-bkp
volboot 3.1 0.7 100
hostid auksvbms
hostguid {c915111c-6702-11e3-a3eb-00144fa8acd2}
defaultdg rootdg
bootdg  lu_rootdg
request_threads 0
Command_Shipping 1
end
###############################################################
###############################################################
###############################################################
###############################################################
###############################################################
###############################

AFTER:

root:auksvbms:/root # cat /etc/vx/volboot
volboot 3.1 0.2 90
hostid auksvbms
hostguid {cf201368-67a7-11e3-a3eb-00144fa8acd2}
defaultdg rootdg
bootdg rootdg
request_threads 2
end
###############################################################
###############################################################
###############################################################
###############################################################
###############################################################
#######################################################

NOTE: The protocol version information is only meaningful for the VxVM cluster feature.

___________________________________________________________________
Solution -2

ISSUE:
Volume Manager does not start during boot up after installation

ERROR CODE/ MESSAGE:
======================================================
Hostname: ucabc001
VxVM sysboot INFO V-5-2-3409 starting in boot mode...
NOTICE: VxVM vxdmp V-5-0-34 added disk array DISKS, datype = Disk
NOTICE: VxVM vxdmp V-5-0-0 removed disk array FAKE_ENCLR_SNO, datype = FAKE_ARRAY
Mar 9 03:45:07 vxvm:vxconfigd: V-5-1-1589 enable failed: Volboot file not loaded
Mar 9 03:45:07 vxvm:vxconfigd: transactions are disabled.
======================================================

DIAGNOSTIC STEPS:
Check OS version: (verify if the product is supported)
# uname -a

Check if package was properly installed(completely):
# pkginfo -l VRTSvxvm

Check if Volume Manager modules were loaded:
# modinfo | egrep -i "vx|vrts"

Check if install-db file exists: (if it exists, delete the file)
# ls -l /etc/vx/reconfig.d/state.d/install-db

If install-db file exists then it is the reason why Volume Manager was not able to start up during boot up.

CAUSE:
Install-db file exist causing Volume Manager not to start up automatically during boot up and volboot file was not created properly during installation.

Other possible cause:
- "installonly" option is used during installation
- Ran installer with "-configure" but failed to initialize VM and remove the "install-db" file


SOLUTION:
- Remove install-db file so that Volume Manager will automatically start during boot up
- Create volboot file by running "vxdctl init"
- Enable Volume Manager by running "vxdctl enable"
- Verify volume manager mode by running "vxdctl mode" to check if it is now in enable mode.
- Check if you can now run Veritas commands such as "vxdisk list"



Comments

Post a Comment

Popular posts from this blog

BMCs and the IPMI Protocol

Image
Baseboard Management Controllers (BMCs) are a type of embedded computer used to provide out-of-band monitoring for desktops and servers. These products are sold under many brand names, including HP iLO, Dell DRAC, Sun ILOM, Fujitsu iRMC, IBM IMM, and Supermicro IPMI. BMCs are often implemented as embedded ARM systems, running Linux and connected directly to the southbridge of the host system's motherboard. Network access is obtained either via 'sideband' access to an existing network card or through a dedicated interface. In addition to being built-in to various motherboards, BMCs are also sold as pluggable modules and PCI cards. Nearly all servers and workstations ship with or support some form of BMC. The Intelligent Platform Management Interface (IPMI) is a collection of specifications that define communication protocols for talking both across a local bus as well as the network. This specification is managed by Intel and currently comes in two flavors, ve...
Read more

Logical Domains Reference Manual

Image
Name ldm– command-line interface for the Logical Domains Manager Synopsis ldm or ldm --help [ subcommand ] ldm -V ldm add-domain -i file ldm add-domain [mac-addr= num ] [hostid= num ] [failure-policy=ignore|panic|reset|stop] [master= master-ldom1 ,..., master-ldom4 ] ldom ldm add-domain ldom ... ldm set-domain -i file ldm set-domain [failure-policy=ignore|panic|reset|stop] [master=[ master-ldom1 ,..., master-ldom4 ]] ldom ldm remove-domain -a ldm remove-domain ldom ... ldm list-domain [-e] [-l] [-o format ] [-p] [ ldom ...] ldm migrate-domain [-n] source-ldom [ user @] target-host [: target-ldom ] ldm add-vcpu number ldom ldm set-vcpu number ldom ldm remove-vcpu number ldom ldm add-crypto number ldom ldm set-crypto number ldom ldm remove-crypto number ldom ldm add-memory size [ unit ] ldom ldm set-memory size [ unit ] ldom ldm remove-memory size [ unit ] ldom ldm cancel-operation (migration | reconf) ldom ldm add-io [bypass=on] bus ...
Read more

Understanding How ZFS Calculates Used Space

This document explains how ZFS calculates the amount of used space within a zpool and provides examples of how various ZFS features affect that calculation. DETAILS A ZFS storage pool is a logical collection of devices that provide space for datasets such as filesystems, snapshots and volumes. A zfs pool can be used as a filesystem, i.e. such as mounting/unmounting; to take snapshots that provides read-only (clones are writable copies of snapshots) copies of the filesystem taken in the past; to create volumes that can be accessed as a raw and a block device and for setting properties on datasets. Interaction of all these datasets and associated properties such as quotas, reservations, compression and deduplication (Solaris 11 only) play a role in how ZFS calculates space usage. Neither the du nor df command have been updated to account for ZFS file system space usage. When calculating zfs space usage, always use the following command. # zfs list -r -o space <pool_name...
Read more