Error Writing Vtoc No Backup Label
I have been doing this on HP EVA array. It was pretty straight forward: Grow the LUN on the array itself On the server use type subcommand of the format utility and Autoconfigure the LUN in question - this where the OS will detect the size increase Grow the filesystem Of course, there are more steps if the LUN is mirrored, but I will leave that out. For some reason when I tried to Autoconfigure the LUN on Clariion format would refuse to replace the VTOC, coming back with the following error: Continue labelling disk? yes
Warning: error writing VTOC.
Warning: no backup labels
Label failed. After a while of trying this and trying that, I got nowhere. I tried searching the web, but the search was not coming up with anything useful. Some people suggested it was a bug in format utility, some installed a different update of Solaris 10, others apparently got it work by booting into single user. None of this was acceptable. The whole point of the exercise is to do this as efficiently as possible with the smallest amount of disruption to service. So no, I will not boot into single user mode. Finally I decided to zero out VTOC, before running format command to Autoconfigure the LUN: bash-3.00# dd if=/dev/zero of=/dev/rdsk/c4t6006016076011F00A83040728E6EDF11d0s2 bs=512 count=1 Sure enough, that worked and I successfully grew the LUN. What bugs me is that the procedure worked fine on EVA array. Sure, it is not exactly the same situation - different hardware, etc. But I do not think I should have to manually zero out VTOC to write a new one, when connected to Clariion. Maybe someone has a definite answer to this? Posted on July 19, 2010 at 10:33 by somedude · Permalink In:clariion, mpxio, multipathing, san, solaris, solaris tips, storage Leave a Reply Name, required Email (will not be published), required Website, if present Notify me of follow-up comments by email. Notify me of new posts by email. Cancel reply « Previous pos
on some of the troubleshooting scenarios related to 1-Touch Recovery: Problem or Error Solution The client is unable to boot. To debug boot problems, use the snoop and truss commands.The client updates the sr.log log files on both the client and the 1-Touch server. If a client's backup completed successfully and is somehow failing to boot, be sure to check the sr.log on the 1-Touch server for any warning. If you are http://www.unixpowered.com/unixpowered/2010/07/19/solaris-10-vtoc-weirdness-on-emc-clariion-array/ using a different 1-Touch server than that was used previously, remove the client?s name from the database of the previous 1-Touch server. Otherwise, the client will not be able to boot off the network because both servers will respond to the client?s RARP request. To do this, from the Tools directory, run the ./rm_install_client http://documentation.commvault.com/commvault/v10/article?p=products/1touch_solaris/troubleshooting.htm
Governance Backup and Recovery Business Continuity Partners Inside Veritas Vision 2016 Developers Information Governance Backup and Recovery Business Continuity Partners Inside Veritas Vision 2016 Developers Blogs Groups Vision 2016 Sign https://vox.veritas.com/t5/Storage-Foundation/SAN-disks-on-Solaris-in-error-state-and-cannot-get-initialised/td-p/458089 In CommunityCategoryBoardResourcesUsers turn on suggestions Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type. Showing results for Search instead for Do you mean VOX : Business Continuity : Storage Foundation : SAN disks on Solaris in error state and cannot get... VOX : error writing Business Continuity : Storage Foundation : SAN disks on Solaris in error state and cannot get... Subscribe to RSS Feed Mark Topic as New Mark Topic as Read Float this Topic to the Top Bookmark Subscribe Printer Friendly Page Solved! Go to Solution SAN disks on Solaris in error state and cannot get initialised Maveric63 Level 3 06-06-2012 12:47 error writing vtoc AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content Hi I zoned some SANdisks to a Solaris 10 host but am unable to initialise the devices. The status is error #VXDISK list output bash-3.00# vxdisk list DEVICE TYPE DISK GROUP STATUS disk_0 auto:cdsdisk data01 REGAN_DG online disk_1 auto:none - - online invalid disk_2 auto:cdsdisk data02 REGAN_DG online disk_3 auto:simple - - online invalid emc1_3a2a auto - - error emc1_3a2b auto - - error emc1_3a2c auto - - error emc1_3a2d auto - - error emc1_3a2e auto - - error emc1_3a2f auto - - error emc1_3a3a auto - - error When trying to do vxdisksetup #vxdisksetup -i emc1_3a2a VxVM vxdisksetup ERROR V-5-2-3535 emc1_3a2a: Invalid dmpnodename for disk device emc1_3a2a. Any ideas how to get these disks online Solved! Go to Solution. Labels: Business Continuity Storage Foundation 1 Kudo Reply 1 Solution Accepted Solutions Accepted Solution! Check out device tree cleanup Gaurav_S Moderator Trusted Advisor Certified 06-06-2012 05:41 AM Options Mark as New Bookmark Subscribe