Error Writing Vtoc
I have been doing this on HP EVA array. It was pretty straight forward: Grow the LUN on the warning error writing vtoc label failed array itself On the server use type subcommand of the format utility error writing vtoc no backup labels 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 publis
från GoogleLogga inDolda fältSök efter grupper eller meddelanden
[ date ] [ thread ] [ subject ] [ author ] On Sat, 30 http://www.sunhelp.org/pipermail/sparcbook/2000-September/001070.html Sep 2000, Keith Howick wrote: > I think I've done something wrong. After performing the "dd" command I > noticed the driver manufacturer https://docs.oracle.com/cd/E19359-01/819-6151-10/VTOCprotect.html and partition information had been > overwritten with the source drive's information. I thought about it, and > decided to re-format the disk error writing and try again. However, the format command > posts an error, > > "warning: error writing VTOC > Note: a PC-format label cannot be overwritten > Note: if this disk contains a PC label it must > Note be removed before being labelled with format error writing vtoc You need to whipe the disk (at least the first bit). Do something like: dd if=/dev/null of=/dev/??? bs=1024 count=100 And retry the solaris format command. Something similar is what I needed to do before I could use a PC SCSI disk in SUN. (And not like what I needed to do to use an AS/400 SCSI disk in a PC where I had to reformat the drive with another blocksize (512 vs 522 if I recall it correctly.) Hugo. -- Hugo van der Kooij; Oranje Nassaustraat 16; 3155 VJ Maasland hvdkooij at caiw.nl http://home.kabelfoon.nl/~hvdkooij/ -------------------------------------------------------------- Quoting this tagline is illegal! (http://www.dtcc.edu/cs/rfc1855.html) Previous message: [SPARCbook] "Error writing VTOC" Next message: [SPARCbook] "Error writing VTOC" Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] More information about the SPARCBook mailing list
Volume Details Solaris Volume Manager Solaris VTOC Errors Availability Suite Overview A Solaris raw disk or LUN, when initialized by the utility format(1M), contains one or more partitions (slices) with information on the physical layout of the volume. This information is stored in cylinder 0 in the VTOC. The VTOC is located on each formatted disk and, in most cases, mapped in partition 2 (the backup partition), which often includes every block on the raw device. A physical backup of partition 2 to an identical disk's partition 2 copies the data in every single block, including the volume's VTOC. It is recommended that the ONLY time any partition containing a VTOC be used is when identical disks are configured and one is attempting to do a physical backup of one disk's partition 2 to partition 2 of another disk of the same size. Other scenarios of using a partition containing a VTOC are often problematic. 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 partitions on a disk for storage) have knowledge of a volume's VTOC and have incorporated software to exclude writing any data to, or on top of, the volume's VTOC. By using the Solaris prtvtoc(1M), format(1M), or metastat(1M) utilities, a system administrator can determine if any source or destination device has partitions or metadevices containing cylinder 0. If the partitions or volumes are used for backup, mirroring, replication, or snapshots, it must be understood that the VTOC of the source device will be copied to the destination device, possibly changing the destination device's VTOC. If the volumes contained in raw device partitions or volumes do not contain cylinder 0, there would be no change in the disk format, since the VTOC will not be overwritten. If source and destination raw devices or metadevices are identically formatted, and include cylinder 0, the VTOCs will be identical, and there will be no perceived change in the raw device's layout when the volume slice containing the VTOC is overwritten. Solaris Volume Manager When using the Solaris Volume Manager, during metainit processing, if a raw disk partition contains cylinder 0, the associated metadevice may contain cylinder 0. When a Solaris Volume Manager volume is created out of that metadevice, it too may contain cylinder 0,