1. Support
  2. Knowledge base
  3. 100000660

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

Article: 100000660
Last Published: 2023-10-10
Ratings: 4 0
Product(s): InfoScale & Storage Foundation

Problem

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

Solution

ISSUE:
Volume Manager does not start during boot up after installation
 
ERROR CODE/MESSAGE:
======================================================
Hostname:abc001
VxVM sysboot INFO V-5-2-3409 starting in boot mode...
NOTICE: VxVMvxdmp V-5-0-34 added disk array DISKS, datype = Disk
NOTICE: VxVMvxdmp V-5-0-0 removed disk array FAKE_ENCLR_SNO, datype = FAKE_ARRAY
Mar 903:45:07 vxvm:vxconfigd: V-5-1-1589 enable failed: Volboot file notloaded
Mar 903:45:07 vxvm:vxconfigd: transactions are disabled.
======================================================
 
DIAGNOSTICSTEPS:
Check OS version: (verify if the product is supported)
# uname-a
 
Check if package was properly installed(completely):
# pkginfo -lVRTSvxvm
 
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 tostart up during boot up.
 
CAUSE:
Install-db file exists causing Volume Manager not to start up automatically during boot upand volboot file was not created properly during installation.
 
Otherpossible 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 bootup
- Create volboot file by running "vxdctl init"
- EnableVolume Manager by running "vxdctl enable"
- Verify volume manager mode by running "vxdctl mode" to check if it is now in enabled mode.
- Check if you can now run Veritas commands such as "vxdisk list"
 
 
 

 

Was this content helpful?

Article Languages