Home > Error V > Vxvm Vxdctl Error V-5-1-1589 Enable Failed: Error In Disk Group Configuration Copies

Vxvm Vxdctl Error V-5-1-1589 Enable Failed: Error In Disk Group Configuration Copies

Contents

eventually it come back . Attachment Products Subscribe to Article Search Survey Did this article answer your question or resolve your issue? Create/Manage Case QUESTIONS? Terms of use for this information are found in Legal Notices.

Related Articles Article Languages x Translated Content Please note that this document is a translation from English, and may have a peek here

G 0 Kudos Reply You have no keyless keys mikebounds Moderator Partner Trusted Advisor Accredited ‎02-27-2013 01:48 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email You may also refer to the English Version of this knowledge base article for up-to-date information. Evaluate the error messages to determine the root cause of the problem. You may also refer to the English Version of this knowledge base article for up-to-date information. my site

Error V 5 1 1589

This error can also result from the command vxdctl enable. Save configurations After logging in, you can retrieve past reports, share reports with colleagues, review notifications you received, and retain custom settings. No Yes Did this article save you the trouble of contacting technical support? Otherwise, look for I/O error messages during the boot process that indicate either a hardware problem or misconfiguration of any logical volume management software being used for the /var file system.

If it was working setup, what & all products are installed ? What is the output of vxdctl license From the info in the thread, it appears you were using a license key as opposed to being in "keyless" mode cheers tony 0 CALL US: 1 (866) 837-4827 Solutions Unstructured Data Growth Multi-Vendor Hybrid Cloud Healthcare Government Products Backup and Recovery Business Continuity Storage Management Information Governance Products A-Z Services Education Services Business Critical This may be because of root file system corruption, a full root file system, or if /var is a separate file system, because it has become corrupted or has not been

ps -ef |grep vxconfig giving : root 16165 1 0 Jan 29 ? 126:39 vxconfigd –kroot 16165 1 0 Jan 29 ? 126:39 vxconfigd –k any ideas ? VOX : Business Continuity : Discussions : VxVM vxdctl ERROR V-5-1-1589 enable failed: Licens... Follow the instruction there to complete verification. https://www.veritas.com/support/en_US/article.TECH75640 If the root file system is full, increase its size or remove files to make space for the tempdb file.

Solved! There is a vxconfigd/licensefix in Rolling Patch 2 (RP2) Looking at the version info, it would appear that you have 5.1SP1 with no patches. Attachment Products Subscribe to Article Search Survey Did this article answer your question or resolve your issue? This message has several variations, described below:VxVM vxconfigd ERROR V-5-1-1589 enable failed: abortingThe failure was fatal and vxconfigd was forced to exit.

Volboot File Not Loaded

Showing results for  Search instead for  Do you mean  VOX : Business Continuity : Discussions : VxVM vxdctl ERROR V-5-1-1589 enable failed: Licens... No Yes How can we make this article more helpful? Error V 5 1 1589 after like 3 months issue appeared ,TECH75640 solved the issue .. You should consider installing the latest rolling patch (RP3) for 5.1SP1 which is available for downloadfrom https://sort.symantec.com/patch cheers tony View solution in original post 0 Kudos Reply 13 Replies You should

It is possible that updates have been made to the original version after this document was translated and published. http://smartphpstatistics.com/error-v/vxvm-vxdisk-error-v-5-1-684-ipc-failure-configuration-daemon-is-not-accessible.html As such /etc/name_to_major should contain a valid entry for each Volume Manager kernel module. Step 2: This confirmation page will display that your e-mail verification is completed (i.e., "You have been verified as an active Veritas employee"). Was this a working SFORA 5.1SP1 system that suddenly stopped or is it a new system ?

The most likely cause is that the operating system is unable to create interprocess communication channels to other utilities.VxVM vxconfigd ERROR V-5-1-1589 enable failed: Error check group configuration copies. If /var is a separate file system, make sure that it has an entry in /etc/vfstab. Check for valid driver to major number bindings in /etc/name_to_major:The Solaris operating system uses entries in /etc/name_to_major to bind device drivers such as Volume Manager kernel modules to major numbers. Check This Out The most likely cause is that the operating system is unable to create interprocess communication channels to other utilities.

For example:# vxconfigd -kVxVM vxconfigd ERROR V-5-1-8726 /dev/vx/info: No such file or directory# vxconfigd -r resetVxVM vxconfigd ERROR V-5-1-7840 cannot open /dev/vx/config: No such file or directorySolution:This situation normally arises due Email Address (Optional) Your feedback has been submitted successfully! Database file not foundThe directory /var/vxvm/tempdb is inaccessible.

Load modules and restart vxconfigd:After checking the above points, if Volume Manager kernel modules are still not loaded, they should be manually loaded either by rebooting the machine and allowing normal

Close Sign In Print Article Products Article Languages Subscribe to this Article Manage your Subscriptions Problem V-5-1-1589 enable failed: Volboot file not loaded Solution ISSUE: Volume Manager does not start Also verify that the encapsulation (if configured) of your boot disk is complete and correct.VxVM vxconfigd ERROR V-5-1-1589 enable failed: transactions are disabledEvaluate the error messages to determine the root cause Thank You! Mike 0 Kudos Reply [email protected] # vxkeyless -v hytham_fekry Level 4 Partner Accredited Certified ‎02-27-2013 04:39 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email

Run vxconfigd in disabled mode: # vxconfigd -m disable Reinitialize the volboot file: # vxdctl init diego # vxdctl add disk sda privoffset=2144 Reset vxconfigd in boot mode: # vxconfigd -kr If for any reasons, you have not received the e-mail verification, go back and try again. It is possible that updates have been made to the original version after this document was translated and published. this contact form Menu Close Search SOLUTIONS Solutions Overview Unstructured Data Growth Multi-Vendor Hybrid Cloud Healthcare Government PRODUCTS Product Overview Backup and Recovery Business Continuity Storage Management Information Governance Products A-Z SERVICES Services Overview

No Yes How can we make this article more helpful? Read and accept Terms of Service DECLINE Menu Close Search SOLUTIONS Solutions Overview Unstructured Data Growth Multi-Vendor Hybrid Cloud Healthcare Government PRODUCTS Product Overview Backup and Recovery Business Continuity Storage Management Step 3: Refresh the [here] page after email validation is done. Email Address (Optional) Your feedback has been submitted successfully!

Get notifications about ASLs/APMs, HCLs, patches, and high availability agents As a registered user, you can create notifications to receive updates about NetBackup Future Platform and Feature Plans, NetBackup hot fixes/EEBs Create/Manage Case QUESTIONS? Thank You! If /var is a separate file system, it has corrupted or not been mounted.

Anonymous users cannot access these features. It is possible that updates have been made to the original version after this document was translated and published. Thank You! Database file not found If the root file system is full, increase its size or remove files to make space for the tempdb file.

Error Code details V-5-1-1589 Severity: Error Component: Volume Manager Message: enable failed: Description: This message is displayed when the regular startup of vxconfigd fails. Labels: Business Continuity Error messages Patch Solaris Storage Foundation 1 Kudo Reply 1 Solution Accepted Solutions Accepted Solution! As such if entries for Volume Manager kernel modules are missing from /etc/name_to_major, Volume Manager kernel modules may be unable to load. The possible reasons are: The root file system has corrupted.

Email Address (Optional) Your feedback has been submitted successfully!