VMware vSphere

 View Only
  • 1.  Unable to extend VMFS Partition after RAID expansion

    Posted Nov 23, 2017 05:32 PM

    I have a ESXi 6.0 host just upgraded to 6.5.  The physical server only has one set of disk storage system, which is running RAID-5. The entire logical drive is used for the host.

    There is no datacenter installed so I manage the host directly by connecting to the ESXi web client.  After adding a new HDD to the RAID system, on reboot, I was able to see the free space in the web client.

    I then tried to increase the datastore capacity by choosing "Expand an existing VMFS datastore extent". But when I assigned the space to the VMFS partition, the task failed with a message of "Cannot change the host configuration".  As suggested by some discussion forums on the internet, I logged on to host using SSH and ran the following commands:

    1. partedUtil getptbl /vmfs/devices/disks/[disk_ID]

    Error: The backup GPT table is not at the end of the disk, as it should be.  This might mean that another operating system believes the disk is smaller.  Fix, by moving the backup to the end (and removing the old backup)?
    Warning: Not all of the space available to /dev/disks/naa.6a4badb021e1ae001eea2a790847ba7d appears to be used, you can fix the GPT to use all of the space (an extra 584843264 blocks) or continue with the current setting? This will also move the backup table at the end if is is not at the end already. diskSize (1754529792) AlternateLBA (1169686527) LastUsableLBA (1169686494) NewLastUsableLBA (1754529758)

    2. partedUtil setptbl /vmfs/devices/disks/[disk_ID] msdos

    Error: Read-only file system during write on /dev/disks/naa.6a4badb021e1ae001eea2a790847ba7d
    WriteNewPtable: error removing gpt signatures from (/dev/disks/naa.6a4badb021e1ae001eea2a790847ba7d)

    3. partedUtil fix /vmfs/devices/disks/[disk_ID]

    Completed with no errors

    4. partedUtil getptbl /vmfs/devices/disks/[disk_ID]

    Completed wiht no errors.  Apparently the "fix" switch did correct the problem earlier.

    5. partedUtil setptbl /vmfs/devices/disks/[disk_ID] msdos

    Error: Read-only file system during write on /dev/disks/naa.6a4badb021e1ae001eea2a790847ba7d
    WriteNewPtable: error removing gpt signatures from (/dev/disks/naa.6a4badb021e1ae001eea2a790847ba7d)

    As stated above, the first "partedUtil getptbl" command returned with an error.  After running "partedUtil fix", the error disappeared but "partedUtil setptbl" still failed and I am still getting the message "Cannot change the host configuration" when adding the extra space to VMFS from the web client.

    I am sure that expanding the datastore is quite a common task but it has been causing me grief.  Any suggestions will be greatly appreciated.



  • 2.  RE: Unable to extend VMFS Partition after RAID expansion

    Posted Nov 23, 2017 06:07 PM

    Try this

    Grow the VMFS Datastore in to the new space using the vmkfstools --growfs command, specifying the partition containing the target VMFS Datastore twice.

    vmkfstools --growfs "/vmfs/devices/disks/device:partition" "/vmfs/devices/disks/device:partition"

    For example:

    vmkfstools --growfs "/vmfs/devices/disks/mpx.vmhba0:C0:T0:L0:5" "/vmfs/devices/disks/mpx.vmhba0:C0:T0:L0:5"

    If you found this or any other answer helpful, please consider the use of the Correct or Helpful to award points.

    Best Regards,

    Deepak Koshal

    CNE|CLA|CWMA|VCP4|VCP5|CCAH



  • 3.  RE: Unable to extend VMFS Partition after RAID expansion

    Posted Nov 24, 2017 05:38 PM

    Thanks for the suggestion.  I did try but got this:

    [root@localhost:/dev/disks] vmkfstools --growfs "/vmfs/devices/disks/naa.6a4badb021e1ae001eea2a790847ba7d:3" "/vmfs/devices/disks/naa.6a4badb021e1ae001eea2a790847ba7d:3"

    Underlying device has no free space

    Error: No space left on device

    I tried try a few other commands to check the actual size of the partition table:

    [root@localhost:~] partedUtil getptbl /dev/disks/naa.6a4badb021e1ae001eea2a790847ba7d

    gpt

    109214 255 63 1754529792

    1 64 8191 C12A7328F81F11D2BA4B00A0C93EC93B systemPartition 128

    5 8224 520191 EBD0A0A2B9E5443387C068B6B72699C7 linuxNative 0

    6 520224 1032191 EBD0A0A2B9E5443387C068B6B72699C7 linuxNative 0

    7 1032224 1257471 9D27538040AD11DBBF97000C2911D1B8 vmkDiagnostic 0

    8 1257504 1843199 EBD0A0A2B9E5443387C068B6B72699C7 linuxNative 0

    9 1843200 7086079 9D27538040AD11DBBF97000C2911D1B8 vmkDiagnostic 0

    2 7086080 15472639 EBD0A0A2B9E5443387C068B6B72699C7 linuxNative 0

    3 15472640 1169686494 AA31E02A400F11DB9590000C2911D1B8 vmfs 0

    [root@localhost:~] partedUtil get /dev/disks/naa.6a4badb021e1ae001eea2a790847ba7d:3

    71846 255 63 1154213855

    [root@localhost:/dev/disks] partedUtil getUsableSectors /dev/disks/naa.6a4badb021e1ae001eea2a790847ba7d

    34 1754529758

    From the web client, I can see and add the extra space to expand VMFS (partition 3).  But then the task would fail if I proceed.



  • 4.  RE: Unable to extend VMFS Partition after RAID expansion

    Posted Nov 24, 2017 06:30 PM

    Check vmkernel.log for any entry related to this storage device. if yes paste it here

    If you found this or any other answer helpful, please consider the use of the Correct or Helpful to award points.

    Best Regards,

    Deepak Koshal

    CNE|CLA|CWMA|VCP4|VCP5|CCAH



  • 5.  RE: Unable to extend VMFS Partition after RAID expansion

    Posted Nov 24, 2017 07:35 PM

    I took a quick look but did not find much clue.  Here is the last portion of the log which seems to have the relevant information. I also copied the log from the browser and saved as a text file for further review.

    2017-11-24T14:14:26.875Z DEBUG    Executing: localcli storage filesystem automount

    2017-11-24T14:14:27.105Z INFO     b''

    2017-11-24T14:14:33.214Z INFO     Discovered lun -- naa.6a4badb021e1ae001eea2a790847ba7d (console /vmfs/devices/disks/naa.6a4badb021e1ae001eea2a790847ba7d) -- DELL     PERC 6/i         (856704 MiB, megaraid_sas)

    2017-11-24T14:14:33.220Z INFO     Scanning naa.6a4badb021e1ae001eea2a790847ba7d for any installs ...

    2017-11-24T14:14:33.221Z INFO     Load vfat, rescanVmfs and automount all at once.

    2017-11-24T14:14:33.224Z cpu5:65574)ScsiDeviceIO: 2948: Cmd(0x439500a18d40) 0x1a, CmdSN 0xcae from world 0 to dev "naa.6a4badb021e1ae001eea2a790847ba7d" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.

    2017-11-24T14:14:33.224Z cpu10:65579)NMP: nmp_ThrottleLogForDevice:3617: Cmd 0x9e (0x439500a18d40, 0) to dev "mpx.vmhba1:C0:T0:L0" on path "vmhba1:C0:T0:L0" Failed: H:0x7 D:0x0 P:0x0 Invalid sense data: 0x0 0x0 0x0. Act:EVAL

    2017-11-24T14:14:33.224Z cpu10:65579)WARNING: NMP: nmp_DeviceRequestFastDeviceProbe:237: NMP device "mpx.vmhba1:C0:T0:L0" state in doubt; requested fast path state update...

    2017-11-24T14:14:33.224Z cpu10:65579)ScsiDeviceIO: 2962: Cmd(0x439500a18d40) 0x9e, CmdSN 0xcaf from world 0 to dev "mpx.vmhba1:C0:T0:L0" failed H:0x7 D:0x0 P:0x0 Invalid sense data: 0x0 0x0 0x0.

    2017-11-24T14:14:33.246Z cpu10:65579)NMP: nmp_ThrottleLogForDevice:3563: last error status from device mpx.vmhba1:C0:T0:L0 repeated 2 times

    2017-11-24T14:14:33.255Z cpu10:65579)NMP: nmp_ThrottleLogForDevice:3617: Cmd 0x9e (0x439500b093c0, 0) to dev "mpx.vmhba1:C0:T0:L0" on path "vmhba1:C0:T0:L0" Failed: H:0x7 D:0x0 P:0x0 Invalid sense data: 0x0 0x0 0x0. Act:EVAL

    2017-11-24T14:14:33.255Z cpu10:65579)ScsiDeviceIO: 2962: Cmd(0x439500b093c0) 0x9e, CmdSN 0xccc from world 0 to dev "mpx.vmhba1:C0:T0:L0" failed H:0x7 D:0x0 P:0x0 Invalid sense data: 0x20 0x46 0x61.

    2017-11-24T14:14:33.272Z cpu10:65579)NMP: nmp_ThrottleLogForDevice:3563: last error status from device mpx.vmhba1:C0:T0:L0 repeated 2 times

    2017-11-24T14:14:33.273Z cpu10:65579)NMP: nmp_ThrottleLogForDevice:3617: Cmd 0x9e (0x439d00651400, 0) to dev "mpx.vmhba1:C0:T0:L0" on path "vmhba1:C0:T0:L0" Failed: H:0x7 D:0x0 P:0x0 Invalid sense data: 0x0 0x0 0x0. Act:EVAL

    2017-11-24T14:14:33.273Z cpu10:65579)ScsiDeviceIO: 2962: Cmd(0x439d00651400) 0x9e, CmdSN 0xcd8 from world 0 to dev "mpx.vmhba1:C0:T0:L0" failed H:0x7 D:0x0 P:0x0 Invalid sense data: 0x20 0x46 0x61.

    2017-11-24T14:14:33.287Z cpu10:65579)ScsiDeviceIO: 2948: Cmd(0x439d00787700) 0x1a, CmdSN 0xd1b from world 0 to dev "naa.6a4badb021e1ae001eea2a790847ba7d" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.

    2017-11-24T14:14:33.291Z cpu10:65579)NMP: nmp_ThrottleLogForDevice:3563: last error status from device mpx.vmhba1:C0:T0:L0 repeated 2 times

    2017-11-24T14:14:33.291Z cpu10:65579)NMP: nmp_ThrottleLogForDevice:3617: Cmd 0x9e (0x439d00651400, 0) to dev "mpx.vmhba1:C0:T0:L0" on path "vmhba1:C0:T0:L0" Failed: H:0x7 D:0x0 P:0x0 Invalid sense data: 0x0 0x0 0x0. Act:EVAL

    2017-11-24T14:14:33.291Z cpu10:65579)ScsiDeviceIO: 2962: Cmd(0x439d00651400) 0x9e, CmdSN 0xd25 from world 0 to dev "mpx.vmhba1:C0:T0:L0" failed H:0x7 D:0x0 P:0x0 Invalid sense data: 0x20 0x46 0x61.

    2017-11-24T14:14:33.313Z cpu10:65579)NMP: nmp_ThrottleLogForDevice:3563: last error status from device mpx.vmhba1:C0:T0:L0 repeated 2 times

    2017-11-24T14:14:33.314Z cpu10:65579)NMP: nmp_ThrottleLogForDevice:3617: Cmd 0x9e (0x439d00651400, 0) to dev "mpx.vmhba1:C0:T0:L0" on path "vmhba1:C0:T0:L0" Failed: H:0x7 D:0x0 P:0x0 Invalid sense data: 0x0 0x0 0x0. Act:EVAL

    2017-11-24T14:14:33.314Z cpu10:65579)ScsiDeviceIO: 2962: Cmd(0x439d00651400) 0x9e, CmdSN 0xd27 from world 0 to dev "mpx.vmhba1:C0:T0:L0" failed H:0x7 D:0x0 P:0x0 Invalid sense data: 0x20 0x46 0x61.

    2017-11-24T14:14:33.336Z cpu10:65579)NMP: nmp_ThrottleLogForDevice:3563: last error status from device mpx.vmhba1:C0:T0:L0 repeated 2 times

    2017-11-24T14:14:33.336Z cpu10:65579)NMP: nmp_ThrottleLogForDevice:3617: Cmd 0x9e (0x439d00651400, 0) to dev "mpx.vmhba1:C0:T0:L0" on path "vmhba1:C0:T0:L0" Failed: H:0x7 D:0x0 P:0x0 Invalid sense data: 0x0 0x0 0x0. Act:EVAL

    2017-11-24T14:14:33.336Z cpu10:65579)ScsiDeviceIO: 2962: Cmd(0x439d00651400) 0x9e, CmdSN 0xd29 from world 0 to dev "mpx.vmhba1:C0:T0:L0" failed H:0x7 D:0x0 P:0x0 Invalid sense data: 0x20 0x46 0x61.

    2017-11-24T14:14:33.358Z cpu10:65579)NMP: nmp_ThrottleLogForDevice:3563: last error status from device mpx.vmhba1:C0:T0:L0 repeated 2 times

    2017-11-24T14:14:33.358Z cpu10:65579)NMP: nmp_ThrottleLogForDevice:3617: Cmd 0x9e (0x439d00651400, 0) to dev "mpx.vmhba1:C0:T0:L0" on path "vmhba1:C0:T0:L0" Failed: H:0x7 D:0x0 P:0x0 Invalid sense data: 0x0 0x0 0x0. Act:EVAL

    2017-11-24T14:14:33.358Z cpu10:65579)ScsiDeviceIO: 2962: Cmd(0x439d00651400) 0x9e, CmdSN 0xd2b from world 0 to dev "mpx.vmhba1:C0:T0:L0" failed H:0x7 D:0x0 P:0x0 Invalid sense data: 0x20 0x46 0x61.

    2017-11-24T14:14:33.380Z cpu10:65579)NMP: nmp_ThrottleLogForDevice:3563: last error status from device mpx.vmhba1:C0:T0:L0 repeated 2 times

    2017-11-24T14:14:33.381Z cpu10:65579)NMP: nmp_ThrottleLogForDevice:3617: Cmd 0x9e (0x439d00651400, 0) to dev "mpx.vmhba1:C0:T0:L0" on path "vmhba1:C0:T0:L0" Failed: H:0x7 D:0x0 P:0x0 Invalid sense data: 0x0 0x0 0x0. Act:EVAL

    2017-11-24T14:14:33.381Z cpu10:65579)ScsiDeviceIO: 2962: Cmd(0x439d00651400) 0x9e, CmdSN 0xd2d from world 0 to dev "mpx.vmhba1:C0:T0:L0" failed H:0x7 D:0x0 P:0x0 Invalid sense data: 0x20 0x46 0x61.

    2017-11-24T14:14:33.396Z cpu10:65579)NMP: nmp_ThrottleLogForDevice:3563: last error status from device mpx.vmhba1:C0:T0:L0 repeated 2 times

    2017-11-24T14:14:33.396Z cpu10:65579)NMP: nmp_ThrottleLogForDevice:3617: Cmd 0x9e (0x439d00651400, 0) to dev "mpx.vmhba1:C0:T0:L0" on path "vmhba1:C0:T0:L0" Failed: H:0x7 D:0x0 P:0x0 Invalid sense data: 0x0 0x0 0x0. Act:EVAL

    2017-11-24T14:14:33.396Z cpu10:65579)ScsiDeviceIO: 2962: Cmd(0x439d00651400) 0x9e, CmdSN 0xd2f from world 0 to dev "mpx.vmhba1:C0:T0:L0" failed H:0x7 D:0x0 P:0x0 Invalid sense data: 0x20 0x46 0x61.

    2017-11-24T14:14:33.411Z cpu10:65579)NMP: nmp_ThrottleLogForDevice:3563: last error status from device mpx.vmhba1:C0:T0:L0 repeated 2 times

    2017-11-24T14:14:33.413Z cpu10:65579)NMP: nmp_ThrottleLogForDevice:3617: Cmd 0x9e (0x439d00667c80, 0) to dev "mpx.vmhba1:C0:T0:L0" on path "vmhba1:C0:T0:L0" Failed: H:0x7 D:0x0 P:0x0 Invalid sense data: 0x0 0x0 0x0. Act:EVAL

    2017-11-24T14:14:33.413Z cpu10:65579)ScsiDeviceIO: 2962: Cmd(0x439d00667c80) 0x9e, CmdSN 0xd31 from world 0 to dev "mpx.vmhba1:C0:T0:L0" failed H:0x7 D:0x0 P:0x0 Invalid sense data: 0x20 0x46 0x61.

    2017-11-24T14:14:33.429Z cpu10:65579)NMP: nmp_ThrottleLogForDevice:3563: last error status from device mpx.vmhba1:C0:T0:L0 repeated 2 times

    2017-11-24T14:14:33.430Z cpu15:65584)NMP: nmp_ThrottleLogForDevice:3617: Cmd 0x9e (0x439d00667c80, 0) to dev "mpx.vmhba1:C0:T0:L0" on path "vmhba1:C0:T0:L0" Failed: H:0x7 D:0x0 P:0x0 Invalid sense data: 0x0 0x0 0x0. Act:EVAL

    2017-11-24T14:14:33.430Z cpu15:65584)ScsiDeviceIO: 2962: Cmd(0x439d00667c80) 0x9e, CmdSN 0xd33 from world 0 to dev "mpx.vmhba1:C0:T0:L0" failed H:0x7 D:0x0 P:0x0 Invalid sense data: 0x20 0x46 0x61.

    2017-11-24T14:14:33.443Z cpu15:65584)NMP: nmp_ThrottleLogForDevice:3563: last error status from device mpx.vmhba1:C0:T0:L0 repeated 2 times

    2017-11-24T14:14:33.445Z cpu15:65584)NMP: nmp_ThrottleLogForDevice:3617: Cmd 0x9e (0x439d006a9300, 0) to dev "mpx.vmhba1:C0:T0:L0" on path "vmhba1:C0:T0:L0" Failed: H:0x7 D:0x0 P:0x0 Invalid sense data: 0x0 0x0 0x0. Act:EVAL

    2017-11-24T14:14:33.445Z cpu15:65584)ScsiDeviceIO: 2962: Cmd(0x439d006a9300) 0x9e, CmdSN 0xd35 from world 0 to dev "mpx.vmhba1:C0:T0:L0" failed H:0x7 D:0x0 P:0x0 Invalid sense data: 0x20 0x46 0x61.

    2017-11-24T14:14:33.459Z cpu15:65584)NMP: nmp_ThrottleLogForDevice:3563: last error status from device mpx.vmhba1:C0:T0:L0 repeated 2 times

    2017-11-24T14:14:33.460Z cpu15:65584)NMP: nmp_ThrottleLogForDevice:3617: Cmd 0x9e (0x439d006a9300, 0) to dev "mpx.vmhba1:C0:T0:L0" on path "vmhba1:C0:T0:L0" Failed: H:0x7 D:0x0 P:0x0 Invalid sense data: 0x0 0x0 0x0. Act:EVAL

    2017-11-24T14:14:33.460Z cpu15:65584)ScsiDeviceIO: 2962: Cmd(0x439d006a9300) 0x9e, CmdSN 0xd37 from world 0 to dev "mpx.vmhba1:C0:T0:L0" failed H:0x7 D:0x0 P:0x0 Invalid sense data: 0x20 0x46 0x61.

    2017-11-24T14:14:33.475Z cpu15:65584)NMP: nmp_ThrottleLogForDevice:3563: last error status from device mpx.vmhba1:C0:T0:L0 repeated 2 times

    2017-11-24T14:14:33.475Z cpu15:65584)NMP: nmp_ThrottleLogForDevice:3617: Cmd 0x9e (0x439d006a9300, 0) to dev "mpx.vmhba1:C0:T0:L0" on path "vmhba1:C0:T0:L0" Failed: H:0x7 D:0x0 P:0x0 Invalid sense data: 0x0 0x0 0x0. Act:EVAL

    2017-11-24T14:14:33.475Z cpu15:65584)ScsiDeviceIO: 2962: Cmd(0x439d006a9300) 0x9e, CmdSN 0xd39 from world 0 to dev "mpx.vmhba1:C0:T0:L0" failed H:0x7 D:0x0 P:0x0 Invalid sense data: 0x20 0x46 0x61.

    2017-11-24T14:14:33.489Z cpu15:65584)NMP: nmp_ThrottleLogForDevice:3563: last error status from device mpx.vmhba1:C0:T0:L0 repeated 2 times

    2017-11-24T14:14:33.489Z cpu15:65584)NMP: nmp_ThrottleLogForDevice:3617: Cmd 0x9e (0x439d006a9300, 0) to dev "mpx.vmhba1:C0:T0:L0" on path "vmhba1:C0:T0:L0" Failed: H:0x7 D:0x0 P:0x0 Invalid sense data: 0x0 0x0 0x0. Act:EVAL

    2017-11-24T14:14:33.489Z cpu15:65584)ScsiDeviceIO: 2962: Cmd(0x439d006a9300) 0x9e, CmdSN 0xd3b from world 0 to dev "mpx.vmhba1:C0:T0:L0" failed H:0x7 D:0x0 P:0x0 Invalid sense data: 0x20 0x46 0x61.

    2017-11-24T14:14:33.506Z cpu15:65584)NMP: nmp_ThrottleLogForDevice:3563: last error status from device mpx.vmhba1:C0:T0:L0 repeated 2 times

    2017-11-24T14:14:33.506Z cpu8:74874)FSS: 5764: No FS driver claimed device 'mpx.vmhba1:C0:T0:L0': No filesystem on the device

    2017-11-24T14:14:33.507Z cpu2:74650)VC: 4511: Device rescan time 49 msec (total number of devices 6)

    2017-11-24T14:14:33.507Z cpu2:74650)VC: 4514: Filesystem probe time 234 msec (devices probed 5 of 6)

    2017-11-24T14:14:33.507Z cpu2:74650)VC: 4516: Refresh open volume time 0 msec

    2017-11-24T14:14:33.507Z DEBUG    Executing: localcli storage filesystem automount

    2017-11-24T14:14:33.727Z INFO     b''

    2017-11-24T14:14:39.745Z DEBUG    Found bootbank partition 5

    2017-11-24T14:14:39.746Z DEBUG    Found locker partition 8

    2017-11-24T14:14:39.747Z DEBUG    Found bootbank partition 6

    2017-11-24T14:14:39.748Z DEBUG    Parsing bootconfig file:  /vmfs/volumes/bad4c87b-919453c1-97de-26568fad488d/boot.cfg

    2017-11-24T14:14:39.758Z DEBUG    Parsing bootconfig file:  /vmfs/volumes/8c96c377-8a179850-1eed-513fb5d3e3e6/boot.cfg

    2017-11-24T14:14:39.760Z INFO       Found ESXi on naa.6a4badb021e1ae001eea2a790847ba7d: {esx : False; esxi : True; lopsided : None; version: (6, 5, 0)}.

    2017-11-24T14:14:39.763Z INFO     runcommand called with: args = '/sbin/localcli --formatter python "storage" "vvol" "storagecontainer" "list" 2>/dev/null', outfile = 'None', returnoutput = 'True', timeout = '0.0'.

    2017-11-24T14:14:39.960Z INFO     runcommand called with: args = '/sbin/localcli --formatter python "storage" "nmp" "device" "list" 2>/dev/null', outfile = 'None', returnoutput = 'True', timeout = '0.0'.

    2017-11-24T14:14:40.436Z INFO     runcommand called with: args = '/sbin/localcli --formatter python "storage" "core" "device" "list" "--exclude-offline" 2>/dev/null', outfile = 'None', returnoutput = 'True', timeout = '0.0'.

    2017-11-24T14:14:40.924Z INFO     runcommand called with: args = '/sbin/localcli --formatter python "storage" "nmp" "device" "list" 2>/dev/null', outfile = 'None', returnoutput = 'True', timeout = '0.0'.

    2017-11-24T14:14:41.129Z INFO     runcommand called with: args = '/sbin/localcli --formatter python "storage" "vvol" "vasaprovider" "list" 2>/dev/null', outfile = 'None', returnoutput = 'True', timeout = '0.0'.

    2017-11-24T14:14:41.349Z INFO     runcommand called with: args = '/sbin/localcli --formatter python "storage" "nmp" "device" "list" 2>/dev/null', outfile = 'None', returnoutput = 'True', timeout = '0.0'.

    2017-11-24T14:14:41.557Z INFO     runcommand called with: args = '/sbin/localcli --formatter python "storage" "core" "device" "list" "--exclude-offline" 2>/dev/null', outfile = 'None', returnoutput = 'True', timeout = '0.0'.

    2017-11-24T14:14:42.021Z INFO     runcommand called with: args = '/sbin/localcli --formatter python "storage" "nmp" "device" "list" 2>/dev/null', outfile = 'None', returnoutput = 'True', timeout = '0.0'.

    2017-11-24T14:14:42.302Z INFO     runcommand called with: args = '/sbin/localcli --formatter python "storage" "core" "device" "list" "--exclude-offline" 2>/dev/null', outfile = 'None', returnoutput = 'True', timeout = '0.0'.



  • 6.  RE: Unable to extend VMFS Partition after RAID expansion

    Posted Nov 24, 2017 07:55 PM

    Make sure your vm's are backed-up and  move the existing vm to another datastore if before running the below command.

    partedUtil setptbl /dev/disks/naa.6a4badb021e1ae001eea2a790847ba7d gpt "3 15472640 1754529758 AA31E02A400F11DB9590000C2911D1B8 0"

    and

    vmkfstools -V

    verify the step number 4 in the below kb after above command.

    Reference kb:

    Recreating a missing VMFS datastore partition in VMware vSphere 5.x and 6.x (2046610)



  • 7.  RE: Unable to extend VMFS Partition after RAID expansion

    Posted Nov 26, 2017 01:53 PM

    After finishing with backing up my VM's, I ran the command as suggested but got a "Read-only file system" error.

    [root@localhost:~] partedUtil setptbl /dev/disks/naa.6a4badb021e1ae001eea2a790847ba7d gpt "3 15472640 1754529758 AA31E02A400F11DB9590000C2911D1B8 0"

    gpt

    0 0 0 0

    3 15472640 1754529758 AA31E02A400F11DB9590000C2911D1B8 0

    Error: Read-only file system during write on /dev/disks/naa.6a4badb021e1ae001eea2a790847ba7dSetPtableGpt: Unable to commit to disk

    [root@localhost:~] esxcli system coredump partition get

       Active: naa.6a4badb021e1ae001eea2a790847ba7d:9

       Configured: naa.6a4badb021e1ae001eea2a790847ba7d:9

    [root@localhost:~] partedUtil getptbl /vmfs/devices/disks/naa.6a4badb021e1ae001eea2a790847ba7d

    gpt

    109214 255 63 1754529792

    1 64 8191 C12A7328F81F11D2BA4B00A0C93EC93B systemPartition 128

    5 8224 520191 EBD0A0A2B9E5443387C068B6B72699C7 linuxNative 0

    6 520224 1032191 EBD0A0A2B9E5443387C068B6B72699C7 linuxNative 0

    7 1032224 1257471 9D27538040AD11DBBF97000C2911D1B8 vmkDiagnostic 0

    8 1257504 1843199 EBD0A0A2B9E5443387C068B6B72699C7 linuxNative 0

    9 1843200 7086079 9D27538040AD11DBBF97000C2911D1B8 vmkDiagnostic 0

    2 7086080 15472639 EBD0A0A2B9E5443387C068B6B72699C7 linuxNative 0

    3 15472640 1169686494 AA31E02A400F11DB9590000C2911D1B8 vmfs 0

    Here is an abstract of the VMKERNEL.log pertinent to the command:

    2017-11-26T08:36:28.382Z cpu0:65569)NMP: nmp_ThrottleLogForDevice:3563: last error status from device mpx.vmhba1:C0:T0:L0 repeated 2 times

    2017-11-26T08:36:28.382Z cpu11:69208)FSS: 5764: No FS driver claimed device 'mpx.vmhba1:C0:T0:L0': No filesystem on the device

    2017-11-26T08:36:28.382Z cpu5:69205)VC: 4511: Device rescan time 73 msec (total number of devices 6)

    2017-11-26T08:36:28.382Z cpu5:69205)VC: 4514: Filesystem probe time 250 msec (devices probed 5 of 6)

    2017-11-26T08:36:28.382Z cpu5:69205)VC: 4516: Refresh open volume time 0 msec

    2017-11-26T08:43:36.952Z cpu10:66140)ScsiDeviceIO: 2948: Cmd(0x439d00682e80) 0x1a, CmdSN 0xa0b from world 0 to dev "naa.6a4badb021e1ae001eea2a790847ba7d" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.

    2017-11-26T08:43:37.734Z cpu12:69268)WARNING: Partition: 1732: naa.6a4badb021e1ae001eea2a790847ba7d: in-use partition 2 modification is not supported

    2017-11-26T08:43:37.734Z cpu12:69268)BC: 2466: Failed to write (uncached) object 'naa.6a4badb021e1ae001eea2a790847ba7d': Read only

    2017-11-26T08:59:53.622Z cpu12:66113)ScsiDeviceIO: 2948: Cmd(0x439d007aed00) 0x1a, CmdSN 0xa66 from world 0 to dev "naa.6a4badb021e1ae001eea2a790847ba7d" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.

    2017-11-26T09:00:22.395Z cpu10:69508)WARNING: Partition: 1732: naa.6a4badb021e1ae001eea2a790847ba7d: in-use partition 2 modification is not supported

    2017-11-26T09:00:22.395Z cpu10:69508)BC: 2466: Failed to write (uncached) object 'naa.6a4badb021e1ae001eea2a790847ba7d': Read only

    2017-11-26T09:00:34.765Z cpu0:65569)ScsiDeviceIO: 2948: Cmd(0x43950a17c180) 0x1a, CmdSN 0xab5 from world 0 to dev "mpx.vmhba1:C0:T0:L0" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0.

    2017-11-26T09:01:01.049Z cpu14:65765)ScsiDeviceIO: 2948: Cmd(0x439d00634d00) 0x1a, CmdSN 0xaea from world 0 to dev "naa.6a4badb021e1ae001eea2a790847ba7d" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.

    2017-11-26T09:06:41.882Z cpu11:69844)WARNING: Partition: 1732: naa.6a4badb021e1ae001eea2a790847ba7d: in-use partition 2 modification is not supported

    2017-11-26T09:06:41.882Z cpu11:69844)BC: 2466: Failed to write (uncached) object 'naa.6a4badb021e1ae001eea2a790847ba7d': Read only



  • 8.  RE: Unable to extend VMFS Partition after RAID expansion

    Posted Nov 26, 2017 10:50 PM

    I am not sure why its reporting partition 2 as our starting sector is not touching the partition 2. continuum​  can you please have a look here suggest if we are doing something wrong.

    Best Regards,

    Deepak Koshal

    CNE|CLA|CWMA|VCP4|VCP5|CCAH



  • 9.  RE: Unable to extend VMFS Partition after RAID expansion

    Posted Nov 27, 2017 03:15 PM

    I do not think you can use ESXi buildin tools to modify the partitiontable of the boot disk.
    I would suggest to you use a Linux LiveCD to modify partition 3.
    But knowing that  expanding a VMFS partition on RAID 5 is a delicate operation I would only attempt to modify the partition if you have already backed up ALL the VMs first.
    Anyway - feel free to call me via skype if you need assistance.
    Ulli