Error V-5-1-6536 Error Reading Partitions

SERVICES Services Overview Education Services Business Critical Services Consulting Services Managed Services Appliance Services CUSTOMER CENTER Customer Center Support Community MyVeritas Customer Success Licensing Programs Licensing Process ABOUT About Corporate Profile Corporate Leadership Newsroom Research Exchange Investor Relations Careers Legal Contact Us English 中文(简体) English Français Deutsch Italiano 日本語 한국어 Português Español USA Site: Veritas Veritas PartnerNet How to clean up the devices after removing them from LVM for resue under VxVM? Article:000083058 Publish: Article URL:http://www.veritas.com/docs/000083058 Support / Article Sign In Remember me Forgot Password? Don't have a Veritas Account? Create a Veritas Account now! Welcome First Last Your Profile Logout Sign in to Subscribe Please sign in to set up your subscription. Close Sign In Print Article Products Article Languages Subscribe to this Article Manage your Subscriptions Problem Devices after removing them from LVM cannot be initialized under VxVM Error Message # vxdisksetup -i  sdxxxVxVM ERROR V-5-3-12153: Cant open device /dev/vx/dmp/sdxxx  VxVM vxparms ERROR V-5-5-6536 error reading partitions VxVM vxdisksetup ERROR V-5-2-43 /dev/sdxxx : Invalid disk device for vxdisksetup and # vxdisk online sdyyyVxVM vxdisk ERROR V-5-1-531 Device sdyyy :online failed Disk in not useable, bad format. Cause pvremove, vgremove or lvremove  fail to wipe the lvm  label cleanly on a device so that LVM will no longer recognise it or leave disk in not useable state , Solution 1. precheck to ensure the removed devices are not part of an existing physical volumes or volume groups # pvs ( Report information about physical volumes ) # vgs ( Report information about volume groups) 2. Check the currrent status of the device to be reused# vxdisk list | egrep "DEVICE|LVM|error" DEVICE TYPE DISK GROUP STATUS sdxxx auto - - error sdyyy auto - - LVM  # vxdisk list sdxxx.. flags: error private autoconfig ... multipathing information: sdxxx # vxdisk list sdyyy ... flags: LVM error private autoconfig .. multipathing information:sdyyy state enabled 3. check the status of the physical device # fdisk -l /dev/sdxxx .. .. Disk /dev/xxxx doen't contain a valid partition table. # fdisk -l /dev/sdyyy .. .. Disk /dev/yyy doen't contain a valid partition table. No difference between the fdisk output for both device regardless of status=error/LVM 4. Add partition table for the

VMware Veritas initialize Disk Problem Posted 1 year ago in Problem Fix. Operation: When try to  initialize a disk which is under  control of  Veritas  DMP  you can get  error  while reading  parttions, please apply   solution steps.This problem can be  occur  while install new disk also after a  patching  operation. Operation: PHP #vxdisksetup -i hitachi_hus_vm0_0000  format=cdsdisk 1 #vxdisksetup -i hitachi_hus_vm0_0000  format=cdsdisk https://www.veritas.com/support/en_US/article.TECH163914 Error: VxVM vxparms ERROR V-5-1-6536 error reading partitions VxVM vxdisksetup ERROR V-5-2-43 hitachi_hus_vm0_0000: Invalid disk device for vxdisksetup Solution: -Init  options initializes  region of a disks used  by  Vxvm.Also this  options  installing a disk header  and writing  a  default empty configuration on the disk. So be http://casesup.com/knowledgebase/veritas-initialize-disk-problem/ careful before  run this command  .If  you run for a used disk it'll remove  header  information. There are some cases  which I observed that user  removed  ASM or  ZFS  disk header  while try to initialize  disk. PHP #vxdisk init hitachi_hus_vm0_0000 format=cdsdisk #vxdisksetup -i hitachi_hus_vm0_0000 format=cdsdisk 12 #vxdisk init hitachi_hus_vm0_0000 format=cdsdisk#vxdisksetup -i hitachi_hus_vm0_0000 format=cdsdisk About Latest Posts Follow meAbdurrahimI'm a support engineer with extensive experience and administration skills and works for a hi-tech telecommunication company.I provide hardware and software support for the following Unix/Linux platforms.(Oracle Solaris,HP-UX, Linux, IBM-AIX) Follow meLatest posts by Abdurrahim (see all) OracleSolarisT-Series & M-Series Sparc Server Comparisons - April 23, 2016 Comparisons betweenExadataVersions X4-2 X5-2X6-2 - April 12, 2016 Oracle Solaris 11 Network Configuration andNew Features - February 27, 2016 by 1 0 © 2016 Linux/Unix Support. All Rights Reserved. Designed by

[ date ] [ thread ] [ subject ] [ author ] I had a similar issue on RedHat, and I've found that there must be *some* partition table on the disk. So do a fdisk , and then n, p, 1, , , w. This will put http://mailman.eng.auburn.edu/pipermail/veritas-vx/2006-March/011735.html a single partition on the disk that's the length of the disk. It will be destroyed https://www.mail-archive.com/veritas-vx@mailman.eng.auburn.edu/msg01364.html when you initialize the disk, obviously, but it has to be there for some odd reason. I've also seen similar behavior with Solaris. On 3/23/06, mauric at sorint.it wrote: > Hi all, > > I'm working in a Linux RedHat environment with SF HA 4.0 MP3 and storage EMC Cx700 connected on with about 100 luns configured on my systems > > VxVM error v-5-1-6536 has recognized all my luns, but they are in error state (in a SOlaris environment like disks without a valid vtoc): > > [root at HurricaneM2 root]# vxdisk list | more > DEVICE TYPE DISK GROUP STATUS > EMC_CLARiiON0_0 auto - - error > EMC_CLARiiON0_1 auto - - error > EMC_CLARiiON0_2 auto - - error > EMC_CLARiiON0_3 auto - - error > EMC_CLARiiON0_4 auto - - error > ... > ... > > Below the details about one of my disks: > > error v-5-1-6536 error [root at HurricaneM2 root]# vxdisk list EMC_CLARiiON0_1 > Device: EMC_CLARiiON0_1 > devicetag: EMC_CLARiiON0_1 > type: auto > flags: online error private autoconfig > -----------> errno: Disk is not usable > Multipathing information: > numpaths: 2 > sddg state=enabled type=primary > sdc state=enabled type=primary > > (DISK IS NOT USABLE) > > It looks like haven't any correct partition table, in fact from the fdisk -l of every disks I've that: > > # fdisk -l > [...] > Disk /dev/sdp: 80.5 GB, 80530636800 bytes > 255 heads, 63 sectors/track, 9790 cylinders > Units = cylinders of 16065 * 512 = 8225280 bytes > > Disk /dev/sdp doesn't contain a valid partition table > > I've tried to give a "good" partition table on one of my disk using the fdisk utility and "w" option, but I haven't had the expected result, when I try to initialize a disk with vxdisksetup (or vxdiskadm utility) I've got the same error: > > [root at HurricaneM2 root]# /etc/vx/bin/vxdisksetup -i EMC_CLARiiON0_105 > VxVM vxparms ERROR V-5-1-6536 error reading partitions > VxVM vxdisksetup ERROR V-5-2-43 EMC_CLARiiON0_105: Invalid disk device for vxdisksetup > > Can you help me pls? > > Thanks. Maurizio > > _______________________________________________ > Veritas-vx maillist - Veritas-vx at mailman.eng.auburn.edu > http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx > Previous message: [Veritas-vx] Unable to Initialize a disk Next message: [Veritas-vx] Unable to Initialize a disk Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] More information about the Verita

array you are using. You can use vxddladm command to list the array supported by vxvm . regards... Sunny Anthony IT Infrastructure Specialist ITIO Remote Services - R&D Operations Symantec Corporation www.symantec.com _________________________ Office : +91-6615 7065 Mobile : +91 992 241 8579 -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of John Kennedy Sent: Thursday, December 20, 2007 5:07 PM To: Veritas-vx@mailman.eng.auburn.edu Subject: [Veritas-vx] Issue with SLES9 and VxVM All, I have a customer who sent me the following. In a nutshell, they have a disk that is seen by the OS (disk sdco) but not by VxVM. Any clue as to why. I am assuming that if there was a hardware problem the disk would show under VxVM with an error? Thanks, John > We have some Pservers running on the Egenera Hardware which runs Suse > Linux > > # cat SuSE-release > SUSE LINUX Enterprise Server 9 (x86_64) > VERSION = 9 > PATCHLEVEL = 3 > > A new disk was presented on /dev/sdco and a primary partition was > created > > dmesg|grep "Attached scsi disk" > ... > Attached scsi disk sdcj at scsi0, channel 0, id 93, lun 0 > Attached scsi disk sdck at scsi0, channel 0, id 94, lun 0 > Attached scsi disk sdcl at scsi0, channel 0, id 95, lun 0 > Attached scsi disk sdcm at scsi0, channel 0, id 96, lun 0 > Attached scsi disk sdcn at scsi0, channel 0, id 97, lun 0 > Attached scsi disk sdco at scsi0, channel 0, id 87, lun 0 > Attached scsi disk sdco at scsi0, channel 0, id 87, lun 0 --> problem > disk > > sol13d-6008b:/etc# fdisk -l /dev/sdco > > Disk /dev/sdco: 36.5 GB, 36549427200 bytes > 255 heads, 63 sectors/track, 4443 cylinders > Units = cylinders of 16065 * 512 = 8225280 bytes > > Device Boot Start End Blocks Id System > /dev/sdco1 1 4443 35688366 83 Linux > > > We wanted to use sdco under VxVM and attempted to vxdisksetup the disk > but get an error that the /dev/vx/dmp/sdco device did not exist > > sol13d-6008a:/dev/vx/dmp# /etc/vx/bin/vxdisksetup -i /dev/sdco > VxVM ERROR V-5-3-000: Can't open device /dev/vx/dmp/sdco > VxVM vxparms ERROR V-5-1-6536 error reading partitions > VxVM vxdisksetup ERROR V-5-2-43 /dev/sdco: Invalid disk device for > vxdisksetup > > # ls -l /dev/vx/dmp/sdc* > brw------- 1 root root 201, 848 Dec 15 19:45 /dev/vx/dmp/sdc > brw-------