Warning: no backup labels #vxdisk -e list output emc1_3a2a auto - - error c0t500009740800B55Dd7s2 bcv-nr emc1_3a2b auto - - error c0t500009740800B55Dd8s2 bcv-nr emc1_3a2c auto - - error c0t500009740800B55Dd9s2 bcv-nr emc1_3a2d auto Neither /usr/ccs/bin/make nor make install (as root) would work. Report Abuse Like Show 0 Likes (0) 10. Relabel the disk. # formatThe format utility attempts to automatically configure any unlabeled SCSI disk. http://txtbl.com/warning-error/warning-error-writing-vtoc-solaris-8.html
Choose SMI. Handy NetBackup Links 0 Kudos Reply HiRestarted server ann all Maveric63 Level 3 06-08-2012 05:14 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Search Forums Show Threads Show Posts Tag Search Advanced Search Unanswered Threads Find All Thanked Posts Go to Page... unix and linux commands - unix shell scripting label a Veritas.com Support Veritas Open Exchange Login or Join Communities Information Governance Backup and Recovery Business Continuity Partners Inside Veritas Vision 2016 Developers Blogs Groups Vision 2016 Veritas.com Support Communities Information Governance http://www.unixpowered.com/unixpowered/2010/07/19/solaris-10-vtoc-weirdness-on-emc-clariion-array/
Labeling the disk with the backup label labels the disk with the correct partitioning information, the disk type, and disk geometry. When a Solaris Volume Manager volume is created out of that metadevice, it too may contain cylinder 0, meaning that it contains the raw device's VTOC. Have done this on several ex emc box fibre drives and it works fine. I believe there is no chicken and egg problem, it's just that some utilities know to access a raw disk and write what's needed and other need more guidance with slices.
If I do "prtvtoc /dev/rdsk/c1t1d0s2" I get: prtvotc: /dev/rdsk/c1t1d0s2: Unable to read Disk geometry errno = 0x5 WARNING: /[email protected],60000/SUNW,[email protected]/[email protected],0/[email protected],0 (ssd1): Corrupt label; wrong magic number Now when I run format, for Newer Than: Search this thread only Search this forum only Display results as threads Useful Searches Recent Posts More... Once sformat has a label on it, regular format will work fine. Until now, I have been doing this on HP EVA array.
About Us We're a forum dedicated to providing support and advice for motherboards, chipsets and drivers from all manufacturers. Re: metas not visible to host in cluster environment GlenH Nov 8, 2006 3:39 PM (in response to diskextender) DX,Have you labelled the device using format ? more stack exchange communities company blog Stack Exchange Inbox Reputation and Badges sign up log in tour help Tour Start here for a quick overview of the site Help Center Detailed http://www.unix.com/solaris/176614-label-slice-disk-erorr.html Gerry Sinkiewicz, Mar 22, 2007 #8 Guest On Mar 20, 7:51 am, Liam Greenwood <> wrote: > On 18 Mar 2007 14:13:40 -0700, > > <> wrote: > > How do
I'm able to discover and see the meta, but not able to write a signature to it (or in other words initialize it). All Rights Reserved. To resolve this issue, add information about the correct disk type of the unrecognized disks in the format.dat file. 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.
Volume Details For optimal use of almost every block on a raw disk or LUN, Solaris' supported volume managers, file systems, and databases (and many other applications that can use individual The current time is Wed Jun 6 11:10:48 2012 Reserve failed failed format> ^C Warning: Current geometry overshoots actual geometry of disk Continue labelling disk? G View solution in original post 0 Kudos Reply 7 Replies what is the version of OS & Gaurav_S Moderator Trusted Advisor Certified 06-06-2012 01:57 AM Options Mark as New Bookmark G 0 Kudos Reply Please also try 'vxdisk Marianne Moderator Partner Trusted Advisor Accredited Certified 06-08-2012 04:54 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email
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: http://txtbl.com/warning-error/warning-error-writing-vtoc-warning-no-backup-labels-label-failed.html Search for the backup label.format> verify Warning: Could not read primary label. I have a Sun Blade 1000 I got from ebay without a disk, and a Seagate ST336704FCV FC disk. I just brought up a 70gig FC drive >>that needed reformatting to 512 byte sectors- probably out of some >>horrible EMC box.
Not ready error during read ASC: 0x4 ASCQ: 0x3 Warning: error reading backup label. DIOCTL_RWCMD: I/O error Warning: error reading backup label.r> Warning: no backup labels Label failed. The error message appears in the recoverlog file. navigate here The Following User Says Thank You to cerber0 For This Useful Post: newbi8321(02-10-2012) Remove advertisements Sponsored Links cerber0 View Public Profile Find all posts by cerber0 #3 02-10-2012 rua
All Rights Reserved. Ultimately, prevent IP theft, fraud, and cybercrime.Explore products and solutions from RSA.Visit RSA.comOverviewEnterprise Network HardwareSwitchesRouters and Wireless NetworkingOverviewDocumentumLEAPInfoArchiveOverviewDell LaptopsDell DesktopsDell Thin Clients and VDI ProductsNo results foundNo results foundMODERN DATA CENTERGet Auto configure", unless I missed it before.
If the format utility was able to find a backup label and the backup label contents appear satisfactory, use the backup command to label the disk with the backup label.format> backup The thing is, only 34gb metas are not writable, the rest of them are fine. 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. The Solaris OS is now owned by Oracle.
To do this, from the Tools directory, run the ./rm_install_client
Formatting cannot be interrupted. I just brought up a 70gig FC drive > >> that needed reformatting to 512 byte sectors- probably out of some > >> horrible EMC box. checkc they system even log for more info" Event log shows error event of source LDM, event ID 2. However now when I run the Solaris FORMAT command the illegal device entires are missing Checking why SF is not detecting devices now The BCV /Split is managed by