1 Reply Latest reply on Feb 11, 2019 2:55 PM by SheridanWendt

    Vmware ESX 5.5 cannot see Lun on HP P2000 Storage System

    MohammadRavaghi Lurker

      hi folks,

      we have deployed vsphere 5.5 that includes 2 HP DL380G7 Servers and HP MSA P2000 Storage as our SAN. it worked fine for about 1 year but yesterday we had a power failure. there are 2 LUNs created and mapped to hosts. Lun 11 is accessible and working perfect. but hosts in cluster cannot see the LUN number 21. however if i try to directly connect to esx Servers using vmware vsphere client and add storage, i can see the storage and i can add it. the problems is why i cannot see Disk inside Vcenter. and why when i try to add it directly inside client (connected to ESX and not vmware Vcenter) it asks for format and wipe of all data. even inside Vcenter i can see Path and devices are working fine and can see the space and Partition format assigned to disk. there are some errors inside vmkernel which i add below.

      2016-12-28T11:57:31.704Z cpu16:35861 opID=cbd8c8a1)VC: 2064: Refresh open volume time 1 msec

      2016-12-28T11:57:31.858Z cpu10:34074 opID=89cd1ef9)World: 14296: VC opID hostd-8f35 maps to vmkernel opID 89cd1ef9

      2016-12-28T11:57:39.220Z cpu14:33444)lpfc: lpfc_rportStats:3778: 0:(0) Compression log for fcp target 0, path is ok, TMGMT: abts=0, tgt_rst=1, lun_rst=0

      2016-12-28T11:57:40.016Z cpu15:34075)World: 14296: VC opID hostd-90f1 maps to vmkernel opID 97d2fbe2

      2016-12-28T11:58:00.010Z cpu7:34437)World: 14296: VC opID hostd-2138 maps to vmkernel opID 34571439

      2016-12-28T11:58:06.793Z cpu7:64688)WARNING: NMP: nmp_IssueCommandToDevice:3488: I/O could not be issued to device "naa.600c0ff000142c3a4d129e5701000000" due to Not found

      2016-12-28T11:58:06.793Z cpu7:64688)WARNING: NMP: nmp_DeviceRetryCommand:133: Device "naa.600c0ff000142c3a4d129e5701000000": awaiting fast path state update for failover with I/O blocked. No prior reservation exists on the device.

      2016-12-28T11:58:06.793Z cpu7:64688)WARNING: NMP: nmp_DeviceStartLoop:723: NMP Device "naa.600c0ff000142c3a4d129e5701000000" is blocked. Not starting I/O from device.

      2016-12-28T11:58:07.708Z cpu6:34789)lpfc: lpfc_scsi_cmd_iocb_cmpl:2157: 0:(0):3271: FCP cmd xa3 failed <0/21> sid x010300, did x010000, oxid xffff SCSI Chk Cond - Not Ready: Data(x2:x2:x4:x3)

      2016-12-28T11:58:07.708Z cpu11:63301)WARNING: VMW_SATP_ALUA: satp_alua_issueCommandOnPath:690: Path "vmhba2:C0:T0:L21" determined to be in unexpected NOT READY state when probed (0x2/0x4/0x3).

      2016-12-28T11:58:07.708Z cpu12:33480)WARNING: NMP: nmpDeviceAttemptFailover:603: Retry world failover device "naa.600c0ff000142c3a4d129e5701000000" - issuing command 0x412e835bd200

      2016-12-28T11:58:07.708Z cpu12:33480)WARNING: NMP: nmpDeviceAttemptFailover:678: Retry world failover device "naa.600c0ff000142c3a4d129e5701000000" - failed to issue command due to Not found (APD), try again...

      2016-12-28T11:58:07.708Z cpu12:33480)WARNING: NMP: nmpDeviceAttemptFailover:728: Logical device "naa.600c0ff000142c3a4d129e5701000000": awaiting fast path state update...

      2016-12-28T11:58:08.708Z cpu6:35827)lpfc: lpfc_scsi_cmd_iocb_cmpl:2157: 0:(0):3271: FCP cmd xa3 failed <0/21> sid x010300, did x010000, oxid xffff SCSI Chk Cond - Not Ready: Data(x2:x2:x4:x3)

      2016-12-28T11:58:08.708Z cpu8:63245)WARNING: VMW_SATP_ALUA: satp_alua_issueCommandOnPath:690: Path "vmhba2:C0:T0:L21" determined to be in unexpected NOT READY state when probed (0x2/0x4/0x3).

      2016-12-28T11:58:08.708Z cpu19:64603)WARNING: NMP: nmpDeviceAttemptFailover:603: Retry world failover device "naa.600c0ff000142c3a4d129e5701000000" - issuing command 0x412e835bd200

      2016-12-28T11:58:08.708Z cpu19:64603)WARNING: NMP: nmpDeviceAttemptFailover:678: Retry world failover device "naa.600c0ff000142c3a4d129e5701000000" - failed to issue command due to Not found (APD), try again...

      2016-12-28T11:58:08.708Z cpu19:64603)WARNING: NMP: nmpDeviceAttemptFailover:728: Logical device "naa.600c0ff000142c3a4d129e5701000000": awaiting fast path state update...

      2016-12-28T11:58:09.708Z cpu6:35830)lpfc: lpfc_scsi_cmd_iocb_cmpl:2157: 0:(0):3271: FCP cmd xa3 failed <0/21> sid x010300, did x010000, oxid xffff SCSI Chk Cond - Not Ready: Data(x2:x2:x4:x3)

      2016-12-28T11:58:09.708Z cpu17:61464)WARNING: VMW_SATP_ALUA: satp_alua_issueCommandOnPath:690: Path "vmhba2:C0:T0:L21" determined to be in unexpected NOT READY state when probed (0x2/0x4/0x3).

      2016-12-28T11:58:10.708Z cpu6:32800)lpfc: lpfc_scsi_cmd_iocb_cmpl:2157: 0:(0):3271: FCP cmd xa3 failed <0/21> sid x010300, did x010000, oxid xffff SCSI Chk Cond - Not Ready: Data(x2:x2:x4:x3)

      2016-12-28T11:58:10.708Z cpu22:60638)WARNING: VMW_SATP_ALUA: satp_alua_issueCommandOnPath:690: Path "vmhba2:C0:T0:L21" determined to be in unexpected NOT READY state when probed (0x2/0x4/0x3).

      2016-12-28T11:58:11.708Z cpu6:35830)lpfc: lpfc_scsi_cmd_iocb_cmpl:2157: 0:(0):3271: FCP cmd xa3 failed <0/21> sid x010300, did x010000, oxid xffff SCSI Chk Cond - Not Ready: Data(x2:x2:x4:x3)

      2016-12-28T11:58:11.708Z cpu5:59848)WARNING: VMW_SATP_ALUA: satp_alua_issueCommandOnPath:690: Path "vmhba2:C0:T0:L21" determined to be in unexpected NOT READY state when probed (0x2/0x4/0x3).

      2016-12-28T11:58:12.708Z cpu6:34789)lpfc: lpfc_scsi_cmd_iocb_cmpl:2157: 0:(0):3271: FCP cmd xa3 failed <0/21> sid x010300, did x010000, oxid xffff SCSI Chk Cond - Not Ready: Data(x2:x2:x4:x3)

      2016-12-28T11:58:12.708Z cpu16:64462)WARNING: VMW_SATP_ALUA: satp_alua_issueCommandOnPath:690: Path "vmhba2:C0:T0:L21" determined to be in unexpected NOT READY state when probed (0x2/0x4/0x3).

      2016-12-28T11:58:13.708Z cpu6:33663)lpfc: lpfc_scsi_cmd_iocb_cmpl:2157: 0:(0):3271: FCP cmd xa3 failed <0/21> sid x010300, did x010000, oxid xffff SCSI Chk Cond - Not Ready: Data(x2:x2:x4:x3)

      2016-12-28T11:58:13.708Z cpu3:32998)WARNING: VMW_SATP_ALUA: satp_alua_issueCommandOnPath:690: Path "vmhba2:C0:T0:L21" determined to be in unexpected NOT READY state when probed (0x2/0x4/0x3).

      2016-12-28T11:58:14.708Z cpu6:34789)lpfc: lpfc_scsi_cmd_iocb_cmpl:2157: 0:(0):3271: FCP cmd xa3 failed <0/21> sid x010300, did x010000, oxid xffff SCSI Chk Cond - Not Ready: Data(x2:x2:x4:x3)

      2016-12-28T11:58:14.708Z cpu10:64065)WARNING: VMW_SATP_ALUA: satp_alua_issueCommandOnPath:690: Path "vmhba2:C0:T0:L21" determined to be in unexpected NOT READY state when probed (0x2/0x4/0x3).

      2016-12-28T11:58:15.708Z cpu6:35837)lpfc: lpfc_scsi_cmd_iocb_cmpl:2157: 0:(0):3271: FCP cmd xa3 failed <0/21> sid x010300, did x010000, oxid xffff SCSI Chk Cond - Not Ready: Data(x2:x2:x4:x3)

      2016-12-28T11:58:15.708Z cpu4:63301)WARNING: VMW_SATP_ALUA: satp_alua_issueCommandOnPath:690: Path "vmhba2:C0:T0:L21" determined to be in unexpected NOT READY state when probed (0x2/0x4/0x3).

      2016-12-28T11:58:16.708Z cpu6:35830)lpfc: lpfc_scsi_cmd_iocb_cmpl:2157: 0:(0):3271: FCP cmd xa3 failed <0/21> sid x010300, did x010000, oxid xffff SCSI Chk Cond - Not Ready: Data(x2:x2:x4:x3)

      2016-12-28T11:58:16.708Z cpu0:63245)WARNING: VMW_SATP_ALUA: satp_alua_issueCommandOnPath:690: Path "vmhba2:C0:T0:L21" determined to be in unexpected NOT READY state when probed (0x2/0x4/0x3).

      2016-12-28T11:58:17.708Z cpu6:32800)lpfc: lpfc_scsi_cmd_iocb_cmpl:2157: 0:(0):3271: FCP cmd xa3 failed <0/21> sid x010300, did x010000, oxid xffff SCSI Chk Cond - Not Ready: Data(x2:x2:x4:x3)

      2016-12-28T11:58:17.708Z cpu12:61464)WARNING: VMW_SATP_ALUA: satp_alua_issueCommandOnPath:690: Path "vmhba2:C0:T0:L21" determined to be in unexpected NOT READY state when probed (0x2/0x4/0x3).

      2016-12-28T11:58:18.708Z cpu6:35836)lpfc: lpfc_scsi_cmd_iocb_cmpl:2157: 0:(0):3271: FCP cmd xa3 failed <0/21> sid x010300, did x010000, oxid xffff SCSI Chk Cond - Not Ready: Data(x2:x2:x4:x3)

      2016-12-28T11:58:18.708Z cpu22:60638)WARNING: VMW_SATP_ALUA: satp_alua_issueCommandOnPath:690: Path "vmhba2:C0:T0:L21" determined to be in unexpected NOT READY state when probed (0x2/0x4/0x3).

      2016-12-28T11:58:19.708Z cpu6:34789)lpfc: lpfc_scsi_cmd_iocb_cmpl:2157: 0:(0):3271: FCP cmd xa3 failed <0/21> sid x010300, did x010000, oxid xffff SCSI Chk Cond - Not Ready: Data(x2:x2:x4:x3)

      2016-12-28T11:58:19.708Z cpu5:59848)WARNING: VMW_SATP_ALUA: satp_alua_issueCommandOnPath:690: Path "vmhba2:C0:T0:L21" determined to be in unexpected NOT READY state when probed (0x2/0x4/0x3).

        • 1. Re: Vmware ESX 5.5 cannot see Lun on HP P2000 Storage System
          SheridanWendt Lurker

          I know this thread is old but I've also recently run into a similar problem. My ESXi 6.7 host gives me an error when I try to create a datastore on a volume on my HP P2000 StorageWorks array. The error that ESXi gives me in the web browser is "Failed to create VMFS datastore: Cannot change the host configuration"

           

          Already Tried:

          -Deleting the RAID array and making a new one

          -Deleting the volume and making a new one

          -Manually creating partitions using fdisk

          -Manually creating partition tables using partedUtil

           

           

          Below are the VMkernel logs.

           

          2019-02-11T22:18:26.424Z cpu14:2097435)WARNING: ScsiDevice: 7641: GetDeviceAttributes during periodic probe'naa.600c0ff00011cebd0000000000000000': failed with Not found

          2019-02-11T22:23:26.418Z cpu14:2097435)WARNING: VMW_SATP_ALUA: satp_alua_issueCommandOnPath:792: Path "vmhba64:C1:T0:L4" determined to be in unexpected NOT READY state when probed (0x2/0x4/0x3).

          2019-02-11T22:23:26.420Z cpu12:2097435)WARNING: VMW_SATP_ALUA: satp_alua_issueCommandOnPath:792: Path "vmhba64:C2:T0:L4" determined to be in unexpected NOT READY state when probed (0x2/0x4/0x3).

          2019-02-11T22:23:26.420Z cpu12:2097435)WARNING: VMW_SATP_ALUA: satp_alua_issueCommandOnPath:792: Path "vmhba64:C0:T0:L4" determined to be in unexpected NOT READY state when probed (0x2/0x4/0x3).

          2019-02-11T22:23:26.421Z cpu12:2097435)WARNING: VMW_SATP_ALUA: satp_alua_issueCommandOnPath:792: Path "vmhba64:C1:T0:L5" determined to be in unexpected NOT READY state when probed (0x2/0x4/0x3).

          2019-02-11T22:23:26.422Z cpu12:2097435)WARNING: VMW_SATP_ALUA: satp_alua_issueCommandOnPath:792: Path "vmhba64:C2:T0:L5" determined to be in unexpected NOT READY state when probed (0x2/0x4/0x3).

          2019-02-11T22:23:26.423Z cpu12:2097435)WARNING: VMW_SATP_ALUA: satp_alua_issueCommandOnPath:792: Path "vmhba64:C0:T0:L5" determined to be in unexpected NOT READY state when probed (0x2/0x4/0x3).

          2019-02-11T22:23:26.423Z cpu12:2097435)WARNING: ScsiDevice: 7641: GetDeviceAttributes during periodic probe'naa.600c0ff00011dc040000000000000000': failed with Not found

          2019-02-11T22:23:26.424Z cpu12:2097435)WARNING: ScsiDevice: 7641: GetDeviceAttributes during periodic probe'naa.600c0ff00011cebd0000000000000000': failed with Not found

          2019-02-11T22:28:26.419Z cpu12:2097435)WARNING: VMW_SATP_ALUA: satp_alua_issueCommandOnPath:792: Path "vmhba64:C1:T0:L4" determined to be in unexpected NOT READY state when probed (0x2/0x4/0x3).

          2019-02-11T22:28:26.420Z cpu12:2097435)WARNING: VMW_SATP_ALUA: satp_alua_issueCommandOnPath:792: Path "vmhba64:C2:T0:L4" determined to be in unexpected NOT READY state when probed (0x2/0x4/0x3).

          2019-02-11T22:28:26.420Z cpu12:2097435)WARNING: VMW_SATP_ALUA: satp_alua_issueCommandOnPath:792: Path "vmhba64:C0:T0:L4" determined to be in unexpected NOT READY state when probed (0x2/0x4/0x3).

          2019-02-11T22:28:26.422Z cpu12:2097435)WARNING: VMW_SATP_ALUA: satp_alua_issueCommandOnPath:792: Path "vmhba64:C1:T0:L5" determined to be in unexpected NOT READY state when probed (0x2/0x4/0x3).

          2019-02-11T22:28:26.423Z cpu12:2097435)WARNING: VMW_SATP_ALUA: satp_alua_issueCommandOnPath:792: Path "vmhba64:C2:T0:L5" determined to be in unexpected NOT READY state when probed (0x2/0x4/0x3).

          2019-02-11T22:28:26.423Z cpu12:2097435)WARNING: VMW_SATP_ALUA: satp_alua_issueCommandOnPath:792: Path "vmhba64:C0:T0:L5" determined to be in unexpected NOT READY state when probed (0x2/0x4/0x3).

          2019-02-11T22:28:26.423Z cpu12:2097435)WARNING: ScsiDevice: 7641: GetDeviceAttributes during periodic probe'naa.600c0ff00011dc040000000000000000': failed with Not found

          2019-02-11T22:28:26.424Z cpu12:2097435)WARNING: ScsiDevice: 7641: GetDeviceAttributes during periodic probe'naa.600c0ff00011cebd0000000000000000': failed with Not found

          2019-02-11T22:33:26.435Z cpu12:2097435)WARNING: VMW_SATP_ALUA: satp_alua_issueCommandOnPath:792: Path "vmhba64:C1:T0:L4" determined to be in unexpected NOT READY state when probed (0x2/0x4/0x3).

          2019-02-11T22:33:26.437Z cpu12:2097435)WARNING: VMW_SATP_ALUA: satp_alua_issueCommandOnPath:792: Path "vmhba64:C2:T0:L4" determined to be in unexpected NOT READY state when probed (0x2/0x4/0x3).

          2019-02-11T22:33:26.438Z cpu12:2097435)WARNING: VMW_SATP_ALUA: satp_alua_issueCommandOnPath:792: Path "vmhba64:C0:T0:L4" determined to be in unexpected NOT READY state when probed (0x2/0x4/0x3).

          2019-02-11T22:33:26.438Z cpu12:2097435)WARNING: VMW_SATP_ALUA: satp_alua_issueCommandOnPath:792: Path "vmhba64:C1:T0:L5" determined to be in unexpected NOT READY state when probed (0x2/0x4/0x3).

          2019-02-11T22:33:26.438Z cpu12:2097435)WARNING: VMW_SATP_ALUA: satp_alua_issueCommandOnPath:792: Path "vmhba64:C2:T0:L5" determined to be in unexpected NOT READY state when probed (0x2/0x4/0x3).

          2019-02-11T22:33:26.439Z cpu12:2097435)WARNING: VMW_SATP_ALUA: satp_alua_issueCommandOnPath:792: Path "vmhba64:C0:T0:L5" determined to be in unexpected NOT READY state when probed (0x2/0x4/0x3).

          2019-02-11T22:33:26.439Z cpu12:2097435)WARNING: ScsiDevice: 7641: GetDeviceAttributes during periodic probe'naa.600c0ff00011dc040000000000000000': failed with Not found

          2019-02-11T22:33:26.440Z cpu12:2097435)WARNING: ScsiDevice: 7641: GetDeviceAttributes during periodic probe'naa.600c0ff00011cebd0000000000000000': failed with Not found

          2019-02-11T22:33:26.449Z cpu3:2097429)StorageApdHandler: 977: APD Handle  Created with lock[StorageApd-0x4303bde69e90]

          2019-02-11T22:33:26.449Z cpu3:2097429)ScsiEvents: 501: Event Subsystem: Device Events, Created!

          2019-02-11T22:33:26.449Z cpu3:2097429)VMWARE SCSI Id: Id for vmhba64:C1:T0:L6

          0x60 0x0c 0x0f 0xf0 0x00 0x11 0xce 0xbd 0x0f 0x92 0x61 0x5c 0x01 0x00 0x00 0x00 0x50 0x32 0x30 0x30 0x30 0x47

          2019-02-11T22:33:26.449Z cpu3:2097429)VMWARE SCSI Id: Id for vmhba64:C2:T0:L6

          0x60 0x0c 0x0f 0xf0 0x00 0x11 0xce 0xbd 0x0f 0x92 0x61 0x5c 0x01 0x00 0x00 0x00 0x50 0x32 0x30 0x30 0x30 0x47

          2019-02-11T22:33:26.450Z cpu3:2097429)VMWARE SCSI Id: Id for vmhba64:C0:T0:L6

          0x60 0x0c 0x0f 0xf0 0x00 0x11 0xce 0xbd 0x0f 0x92 0x61 0x5c 0x01 0x00 0x00 0x00 0x50 0x32 0x30 0x30 0x30 0x47

          2019-02-11T22:33:26.450Z cpu3:2097429)ScsiDeviceIO: 9297: Get VPD 86 Inquiry for device "naa.600c0ff00011cebd0f92615c01000000" from Plugin "NMP" failed. Not supported

          2019-02-11T22:33:26.450Z cpu3:2097429)ScsiDeviceIO: 7998: QErr is correctly set to 0x0 for device naa.600c0ff00011cebd0f92615c01000000.

          2019-02-11T22:33:26.451Z cpu3:2097429)ScsiDeviceIO: 8495: Could not detect setting of sitpua for device naa.600c0ff00011cebd0f92615c01000000. Error Not supported.

          2019-02-11T22:33:26.467Z cpu3:2097429)ScsiEvents: 300: EventSubsystem: Device Events, Event Mask: 40, Parameter: 0x4303bde743c0, Registered!

          2019-02-11T22:33:26.467Z cpu3:2097429)ScsiEvents: 300: EventSubsystem: Device Events, Event Mask: 200, Parameter: 0x4303bde743c0, Registered!

          2019-02-11T22:33:26.467Z cpu3:2097429)ScsiEvents: 300: EventSubsystem: Device Events, Event Mask: 800, Parameter: 0x4303bde743c0, Registered!

          2019-02-11T22:33:26.467Z cpu3:2097429)ScsiEvents: 300: EventSubsystem: Device Events, Event Mask: 400, Parameter: 0x4303bde743c0, Registered!

          2019-02-11T22:33:26.467Z cpu3:2097429)ScsiEvents: 300: EventSubsystem: Device Events, Event Mask: 8, Parameter: 0x4303bde743c0, Registered!

          2019-02-11T22:33:26.467Z cpu3:2097429)ScsiDevice: 4936: Successfully registered device "naa.600c0ff00011cebd0f92615c01000000" from plugin "NMP" of type 0

          2019-02-11T22:33:26.467Z cpu3:2097429)NMP: nmp_DeviceUpdateProtectionInfo:747: Set protection info for device 'naa.600c0ff00011cebd0f92615c01000000', Enabled: 0 ProtType: 0x0 Guard: 0x0 ProtMask: 0x0

          2019-02-11T22:33:26.467Z cpu3:2097429)ScsiEvents: 300: EventSubsystem: Device Events, Event Mask: 180, Parameter: 0x4309de76e2a0, Registered!

          2019-02-11T22:33:34.797Z cpu5:2098772 opID=2a26ee8a)World: 11942: VC opID 0d3b2165 maps to vmkernel opID 2a26ee8a

          2019-02-11T22:33:34.797Z cpu5:2098772 opID=2a26ee8a)NVDManagement: 1478: No nvdimms found on the system

          2019-02-11T22:34:14.375Z cpu5:2099337 opID=7e6bf57)World: 11942: VC opID 0d3b2170 maps to vmkernel opID 7e6bf57

          2019-02-11T22:34:14.375Z cpu5:2099337 opID=7e6bf57)VC: 4616: Device rescan time 699 msec (total number of devices 3)

          2019-02-11T22:34:14.375Z cpu5:2099337 opID=7e6bf57)VC: 4619: Filesystem probe time 2770 msec (devices probed 3 of 3)

          2019-02-11T22:34:14.375Z cpu5:2099337 opID=7e6bf57)VC: 4621: Refresh open volume time 0 msec

          2019-02-11T22:34:23.498Z cpu6:2097446)ScsiPath: 8458: DeletePath : adapter=vmhba64, channel=0, target=0, lun=4

          2019-02-11T22:34:23.498Z cpu0:2097448)ScsiPath: 8458: DeletePath : adapter=vmhba64, channel=0, target=0, lun=5

          2019-02-11T22:34:23.498Z cpu6:2097446)WARNING: VMW_SATP_ALUA: satp_alua_issueCommandOnPath:792: Path "vmhba64:C1:T0:L4" determined to be in unexpected NOT READY state when probed (0x2/0x4/0x3).

          2019-02-11T22:34:23.499Z cpu6:2097446)WARNING: VMW_SATP_ALUA: satp_alua_issueCommandOnPath:792: Path "vmhba64:C2:T0:L4" determined to be in unexpected NOT READY state when probed (0x2/0x4/0x3).

          2019-02-11T22:34:23.499Z cpu6:2097446)WARNING: ScsiPath: 8537: Remove path: vmhba64:C0:T0:L4

          2019-02-11T22:34:23.499Z cpu6:2097446)ScsiPath: 8458: DeletePath : adapter=vmhba64, channel=2, target=0, lun=4

          2019-02-11T22:34:23.499Z cpu0:2097448)WARNING: VMW_SATP_ALUA: satp_alua_issueCommandOnPath:792: Path "vmhba64:C1:T0:L5" determined to be in unexpected NOT READY state when probed (0x2/0x4/0x3).

          [root@localhost:~] partedUtil getptbl

          Usage:

          Get Partitions : get <diskName>

          Set Partitions : set <diskName> ["partNum startSector endSector type attr"]*

          Delete Partition : delete <diskName> <partNum>

          Resize Partition : resize <diskName> <partNum> <start> <end>

          Get Partitions : getptbl <diskName>

          Set Partitions : setptbl <diskName> <label> ["partNum startSector endSector type/guid attr"]*

          Fix Partition Table : fix <diskName>

          Create New Label (all existing data will be lost): mklabel <diskName> <label>

          Show commonly used partition type guids : showGuids

          Get usable first and last sectors : getUsableSectors <diskName>

          Fix GPT Table interactively : fixGpt <diskName>

          Show Partition Information : partinfo <diskName> <partNum>

          Add Partition Information : add <diskName> <label> ["partNum startSector endSector type/guid attr"]

           

           

          [root@localhost:~] partedUtil -l

          Usage:

          Get Partitions : get <diskName>

          Set Partitions : set <diskName> ["partNum startSector endSector type attr"]*

          Delete Partition : delete <diskName> <partNum>

          Resize Partition : resize <diskName> <partNum> <start> <end>

          Get Partitions : getptbl <diskName>

          Set Partitions : setptbl <diskName> <label> ["partNum startSector endSector type/guid attr"]*

          Fix Partition Table : fix <diskName>

          Create New Label (all existing data will be lost): mklabel <diskName> <label>

          Show commonly used partition type guids : showGuids

          Get usable first and last sectors : getUsableSectors <diskName>

          Fix GPT Table interactively : fixGpt <diskName>

          Show Partition Information : partinfo <diskName> <partNum>

          Add Partition Information : add <diskName> <label> ["partNum startSector endSector type/guid attr"]

           

           

          [root@localhost:~] fdisk -l

           

           

          ***

          *** The fdisk command is deprecated: fdisk does not handle GPT partitions.  Please use partedUtil

          ***

           

           

           

           

          Disk /dev/disks/naa.600c0ff00011cebd0f92615c01000000: 499.5 GB, 499590955008 bytes

          255 heads, 63 sectors/track, 60738 cylinders

          Units = cylinders of 16065 * 512 = 8225280 bytes

           

           

          Disk /dev/disks/naa.600c0ff00011cebd0f92615c01000000 doesn't contain a valid partition table

          Found valid GPT with protective MBR; using GPT

           

           

          Disk /dev/disks/mpx.vmhba32:C0:T0:L0: 15278080 sectors, 3364M

          Logical sector size: 512

          Disk identifier (GUID): e75aaf72-26be-4f51-9ad1-b8d85ca2ddb2

          Partition table holds up to 128 entries

          First usable sector is 34, last usable sector is 15278046

           

           

          Number  Start (sector)    End (sector)  Size       Code  Name

             1              64            8191       4064K   0700

             5            8224          520191        249M   0700

             6          520224         1032191        249M   0700

             7         1032224         1257471        109M   0700

             8         1257504         1843199        285M   0700

             9         1843200         7086079       2560M   0700