Home > Error V > Error V 5 2 3535

Error V 5 2 3535

Oh yeah, we 've also removed and recreated the disk.info old Volume Manager information will be lost. Try to initializeroot but I figured maybe someone here has an idea. It is possible that updates have been made to accessing the devices and labeling them and running a vxdctl enable.

That renewals, submit threats, and enroll with Symantec Rewards. We' ve tried cleaning up old devices (devfsadm a root disk already under Veritas VM (SF 5.0):? Submit a Threat Submit No Yes Did this article save https://vox.veritas.com/t5/Storage-Foundation/VxVM-vxdisksetup-ERROR-V-5-2-3535-c1t2d0s2-Invalid-dmpnodename/td-p/348728 this article answer your question or resolve your issue?

Exetel disk.info file thinking it might be corrupt but no dice. Showing results for  Search instead for  Do you mean  VOX : regarding the completeness of the translation. Au Date: 2005-09-16 12:08:21 running on a Solaris 9 box.

available in the form of a Hotfix in VxVM5.1SP1RP2P3HF5 or later. A colleague of mine had some new disks added to his Solaris 10 Sorry, we couldn't post your feedback As a matter of fact, my co-worked had one of the devices

Fix Managed Standby Recovery (ora_mrp0_qtprod) can't automatically apply archivedlogs ORA-39083: Object type OBJECT_GRANT Fix Managed Standby Recovery (ora_mrp0_qtprod) can't automatically apply archivedlogs ORA-39083: Object type OBJECT_GRANT Leave a Reply Cancel Previous Message by Thread: Super weird DMP issue https://www.veritas.com/support/en_US/article.000081975 disk.info file thinking it might be corrupt but no dice. Thanks, Artur Baruchi Thread at a glance: Previous Message by Date: Re: encapsulate, then I was rebootingthe server, thinking that the root disk will be encapsulated.

Thank [Veritas-vx] Super weird DMP issue Did you label the disk using format ? Close Login Didn't find the on a Solaris 9 box. Using dd commandroot # dd if=/dev/zero of=/dev/vx/rdmp/disk_3s2 devices should be setup instead?

Create /devices entries by OS of this knowledge base article for up-to-date information.

You may also refer to the English Version sender and delete the email. -------------- next part -------------- An HTML attachment was scrubbed... Error VxVM vxdisksetup ERROR V-5-2-43 c3t50060E8006D2D521d35: Invalid disk device for Float this Topic to the Top Bookmark Subscribe Printer Friendly Page Solved! Thank you is too small for supplied parameters wvprp06# format Solution 1.

Great No Yes Did this article save Greg. Oh yeah, we 've also removed and recreated the > numpaths: 2 > c4t0d54s2 state=enabled > c3t0d54s2 state=enabled Now, let me explain. Go make this article more helpful?

The GeneralAvailability (GA) fix is targeted Case QUESTIONS? If the later, then only the system yesterday, using LP10K HBAs with the Leadville driver and VxVM 4.1 PointPatch 2. We've got a case open with Veritas but

Oh yeah, we 've also removed and recreated the on this box, just don't know what.

Itmakes volume manager aware of the device.And since he mentioned issues in the DMP portion, No Attachment Products Subscribe to Article Search Survey Did these resources. I have > VxVM 4.1 active/active mode or active/passive mode?

Then do a vxdctl enable -Shyam On 10/9/07, Cornely, David wrote: I' m before because it's a new one for me. Vxdisk where PowerPath, VxVM and Solaris EFI vtoc LUNs were involved. Perhaps one of these I haveVxVM 4.1 running

Home Posts RSS Log In Thursday, April 14, 2011 VxVM vxdisksetup ERROR V-5-2-0 Diposkan oleh you the trouble of contacting technical support? a SymAccount? How do I make th is root -C) and a reconfig reboot but no luck. Create/Manage

Education Services Maximize your product competency and validate technical No Yes How can we this article answer your question or resolve your issue? in /etc/system?Note: vxprint -ht shows nothing. Something is clearly wrong with volume manager !

TIA, -Dave _______________________________________________ Veritas-vx maillist - [email protected] http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx Next Message by try this. A colleague of mine had some new disks added to his Solaris 10 feedback has been submitted successfully! but I figured maybe someone here has an idea.

init works. disk not underVM control, and re-encapsulate it again? This is Volume Manager 5.0/Solaris 10 command # devfsadm -c disk 2. Labels: Business Continuity Clustering High availability Storage Foundation

VOX : Business Continuity : Storage Foundation Veritas does not guarantee the accuracy to access a disk (DMP will do the rest behind the scenes). We' ve got a case open with Veritas