Error Writing Vtoc Solaris 10
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 post Next post » Categories alom cde centos cisco clariion cvs ext3 ext4 fibre channel hp data protector hp eva hp jetadmin hp jetdirect hp msl hpux ilom inetd ios jumpstart linux linux tips linux utilitie
known simply as Solaris, is a Unix-based operating system introduced by Sun Microsystems. The Solaris OS is now owned by Oracle. Search Forums Show Threads Show Posts Tag Search Advanced Search Unanswered Threads Find All Thanked Posts Go to Page... learn linux and unix commands - unix shell scripting label a slice on disk erorr Solaris Thread Tools Search this Thread Display Modes #1 02-10-2012 newbi8321 Registered User Join Date: Feb 2012 Last Activity: 25 November 2013, 9:48 AM EST Posts: 3 Thanks: 5 http://www.unixpowered.com/unixpowered/2010/07/19/solaris-10-vtoc-weirdness-on-emc-clariion-array/ Thanked 0 Times in 0 Posts label a slice on disk erorr Hi there, I am trying to do root volume mirroring on SunFire V210 server. I have two disks in it.First one is c1t0do and second one is c1t1do. Both disks already have partitions in them so I am deleting the partitions of second disk(c1t1do) using format command and selecting cylinder start 0 and size http://www.unix.com/solaris/176614-label-slice-disk-erorr.html 0mb. When I do the same on partition 6 I could not able to label the partition 6 and its shows an error. Please help me . Thanks in advance. Code: partition> 6 Part Tag Flag Cylinders Size Blocks 6 unassigned wm 4027 - 4047 104.34MB (21/0/0) 213696 Enter partition id tag[unassigned]: Enter partition permission flags[wm]: Enter new starting cyl[4027]: 0 Enter partition size[213696b, 21c, 20e, 104.34mb, 0.10gb]: 0mb partition> label Ready to label disk, continue? y Warning: error writing VTOC. Warning: no backup labels Label failed. ---------- Post updated at 11:01 PM ---------- Previous update was at 10:42 PM ---------- Solution : You should never make size of slice 2 0mb. Remove advertisements Sponsored Links newbi8321 View Public Profile Find all posts by newbi8321 #2 02-10-2012 cerber0 Registered User Join Date: Nov 2008 Last Activity: 18 September 2016, 8:30 AM EDT Location: Mexico DF Posts: 46 Thanks: 0 Thanked 5 Times in 5 Posts I think that you should not delete the slice 2 (backup partition), this partition normally contains all space on disk. The Following User Says Thank You to cerber0 For This Useful Post: newbi8321(02-10-2012) Remove advertisements Sponsored L
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 https://vox.veritas.com/t5/Storage-Foundation/SAN-disks-on-Solaris-in-error-state-and-cannot-get-initialised/td-p/458089 Blogs Groups Vision 2016 Sign In https://community.emc.com/thread/87685?start=0&tstart=0 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 error writing disks on Solaris in error state and cannot get... VOX : 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 error writing vtoc SAN disks on Solaris in error state and cannot get initialised Maveric63 Level 3 06-06-2012 12:47 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: Busine
Management Converged Platforms Data Protection Infrastructure Management Platform Solutions Security Storage Dell Products for Work Network Servers Education Partners Programs Highlighted Communities Support » Connect » Developers » Partners » Downloads » 日本語コミュニティ EMC Community Dell Community A AppSync Application Xtender Atmos Avamar C Captiva Celerra Centera CLARiiON Cloud Tiering Appliance Connectrix D Data Domain Data Protection Advisor Disk Library DiskXtender Documentum E ECS eRoom G Greenplum H Host Systems I InfoArchive Isilon ISIS Document Imaging L Leap N NetWorker P PowerPath Prosphere R RecoverPoint Replication RSA S ScaleIO Secure Remote Smarts SourceOne & EmailXtender EMC Storage Analytics Symmetrix U Unity V ViPR Controller Support Community > Host Systems Support Forum > Discussions Please enter a title. You can not post a blank message. Please type your message and try again. 12 Replies Latest reply: Nov 16, 2006 10:12 PM by JasonBailey metas not visible to host in cluster environment diskextender Nov 8, 2006 10:51 AM Hi, may be someone came across this problem before. I've opened a case on this as well, but any other suggestions will not hurt. We have a cluster system with two nodes (both see the same metas). We can see the metas from the host side, but not able to write to them. When trying to format a disk get this message "Warning: error writing VTOC", when trying to create a file system:# newfs -m 1 /dev/rdsk/c3t20d51s0 newfs: construct a new file system /dev/rdsk/c3t20d51s0: (y/n)? y write error on sector 16: I/O error 1309Views Tags: none (add) host_systems Content tagged with host_systems , support Content tagged with support , open_systems Content tagged with open_systems Categories: Open Systems 1. Re: metas n