Skip to main content

Device expanded/shrank messages are reported in the VMkernel log for VMFS-5

 


 Symptoms
  • A VMFS-5 datastore is no longer visible in vSphere 5 datastores view.
  • A VMFS-5 datastore is no longer mounted in the vSphere 5 datastores view.
  • In the /var/log/vmkernel.log file, you see an entry similar to:

    .. cpu1:44722)WARNING: LVM: 2884: [naa.6006048c7bc7febbf4db26ae0c3263cb:1] Device shrank (actual size 18424453 blocks, stored size 18424507 blocks)

  • A VMFS-5 datastore is mounted in the vSphere 5 datastores view, but in the /var/log/vmkernel.log file you see an entry similar to:

    .. cpu0:44828)LVM: 2891: [naa.6006048c7bc7febbf4db26ae0c3263cb:1] Device expanded (actual size 18424506 blocks, stored size 18422953 blocks)
 Purpose
This article provides steps to correct the VMFS-5 partition table entry using partedUtil. For more information see Using the partedUtil command line utility on ESX and ESXi (1036609).
 Cause
The device size discrepancy is caused by an incorrect ending sector for the VMFS-5 partition on the device.
 Resolution
Depending on the device condition reported, follow one of these methods for the corresponding condition:

Note: This resolution is applicable only if the device has one VMFS-5 partition.

TSE NoteYou do not need to set or unset /Disk/PreventVMFSOverwrite as part of any of these operations since this protection only applies to where the VMFS filesystem exists, which is 17M into the disk from the start of the fb partition. The changes this KB article recommends applies to the MBR or GPT, which is at the front of the disk and NOT past the 17M point.

Device shrank condition

.... cpu1:44722)WARNING: LVM: 2884: [naa.6006048c7bc7febbf4db26ae0c3263cb:1] Device shrank (actual size 18424453 blocks, stored size 18424507 blocks)
  1. Calculate the number of sectors by which the device shrank. For example:

    18424507 - 18424453 = 54

  2. Connect to the ESXi host console and run this command to extract the present ending sector partition information:

    partedUtil getptbl /vmfs/devices/disks/naa.6006048c7bc7febbf4db26ae0c3263cb

    You see output similar to:

    gpt
    1147 255 63 18432000
    1 2048 18426500 AA31E02A400F11DB9590000C2911D1B8 vmfs 0


  3. Calculate the correct ending sector by adding the result of step 1. For example:

    18426500 + 54 = 18426554

  4. Note: Prior to running the VMFS resize command, please verify that VMFS write protection is disabled. If it is not disabled, please disable it temporarily. Please follow the steps below:

    To verify the current status of the VMFS overwrite protection

    esxcfg-advcfg --get /Disk/PreventVMFSOverwrite

    To disable VMFS overwrite protection, run the command:

    esxcfg-advcfg -s 0 /Disk/PreventVMFSOverwrite

    Once the VMFS overwrite is enabled, you can perform the delete or resize operation as follows:

    partedUtil delete /vmfs/devices/disks/naa.6006048c7bc7febbf4db26ae0c3263cb 1

    Alternatively, you can use this partedUtil resize command:

    partedUtil resize "/vmfs/devices/disks/t10.945445000000000063000000000000000000000000000000" 1 2048 18426554

    For more information, see Using the partedUtil command line utility on ESX and ESXi (1036609).

    To re-enable overwrite protection after resizing the partition table, run the command:

    # esxcfg-advcfg -s 1 /Disk/PreventVMFSOverwrite

  5. Run this command to create a new partition table with starting sector 2048 and the ending sector from step 3:

    partedUtil setptbl /vmfs/devices/disks/naa.6006048c7bc7febbf4db26ae0c3263cb gpt "1 2048 18426554 AA31E02A400F11DB9590000C2911D1B8 0"

    You see output similar to:

    gpt
    0 0 0 0
    1 2048 18426554 AA31E02A400F11DB9590000C2911D1B8 0


  6. Run this command to remount the VMFS:

    vmkfstools -V

Device expanded condition:

.... cpu0:44828)LVM: 2891: [naa.6006048c7bc7febbf4db26ae0c3263cb:1] Device expanded (actual size 18424506 blocks, stored size 18422953 blocks)
  1. Calculate the number of sectors by which the device expanded. For example:

    18424506 - 18422953 = 1553

  2. Connect to the ESXi host console and run this command to extract the present ending sector partition information:

    partedUtil getptbl /vmfs/devices/disks/naa.6006048c7bc7febbf4db26ae0c3263cb

    You see output similar to:

    gpt
    1147 255 63 18432000
    1 2048 18426553 AA31E02A400F11DB9590000C2911D1B8 vmfs 0


  3. Calculate the correct ending sector by subtracting the result of step 1. For example:

    18426553 - 1553 = 18425000

  4. Run partedUtil delete or resize command to delete / resize the partition table:

    Note: Prior to running the VMFS resize command, please verify that VMFS write protection is disabled. If it is not disabled, please disable it temporarily. Please follow the steps below:

    To verify the current status of the VMFS overwrite protection

    esxcfg-advcfg --get /Disk/PreventVMFSOverwrite

    To disable VMFS overwrite protection, run the command:

    esxcfg-advcfg -s 0 /Disk/PreventVMFSOverwrite

    Once the VMFS overwrite is enabled, you can perform the delete or resize operation as follows:

    partedUtil delete /vmfs/devices/disks/naa.6006048c7bc7febbf4db26ae0c3263cb 1

    Alternatively , you can use this partedUtil resize command:

    partedUtil resize "/vmfs/devices/disks/t10.945445000000000063000000000000000000000000000000" 1 2048 18425000

    For more information, see Using the partedUtil command line utility on ESX and ESXi (1036609).

    To re-enable overwrite protection after resizing the partition table, run the command:

    esxcfg-advcfg -s 1 /Disk/PreventVMFSOverwrite

  5. Run this command to create new partition table with starting sector 2048 and the ending sector from step 3:

    partedUtil setptbl /vmfs/devices/disks/naa.6006048c7bc7febbf4db26ae0c3263cb gpt "1 2048 18425000 AA31E02A400F11DB9590000C2911D1B8 0"

    You see output similar to:

    gpt
    0 0 0 0
    1 2048 18425000 AA31E02A400F11DB9590000C2911D1B8 0


  6. Run this command to remount the VMFS:

    vmkfstools -V

Comment
Issue :
we could not increase the Size of the datastore after increasing the Size of the Lun from SAN.
Device was already showing the storage with increased size
while we tried to increase the Size of datastore , it could not detect the device,
Resolution :
Increased the Size of Lun again from Storage
Logged in to the host directly
Able to see the device now to increase the size

Comments

Popular posts from this blog

ما هى ال FSMO Roles

  بأختصار ال FSMO Roles هى اختصار ل Flexible Single Operation Master و هى عباره عن 5 Roles فى ال Active Directory و هما بينقسموا لقسمين A - Forest Roles 1- Schema Master Role و هى ال Role اللى بتتحكم فى ال schema و بيكون فى Schema Master Role واحد فى ال Forest بيكون موجود على Domain Controller و بيتم التحكم فيها من خلال ال Active Directory Schema Snap in in MMC بس بعد ما يتعمل Schema Register بواسطه الامر التالى من ال Cmd regsvr32 schmmgmt.dll 2-Domin Naming Master و هى ال Role المسئوله عن تسميه ال Domains و بتتأكد ان مفيش 2 Domain ليهم نفس الاسم فى ال Forest و بيتم التحكم فيها من خلال ال Active Directory Domains & Trusts B- Domain Roles 1-PDC Emulator و هى ال Role اللى بتتحكم فى ال Password change فى ال domain و بتتحكم فى ال time synchronization و هى تعتبر المكان الافتراضى لل GPO's و هى تعتبر Domain Role مش زى الاتنين الاولانيين و بيتم التحكم فيها من خلال ال Active directory Users & Computers عن طريق عمل كليك يمين على اسم الدومين و نختار operations master فى تاب ال PDC Emu

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

    Symptoms A datastore has become inaccessible. A VMFS partition table is missing.   Purpose The partition table is required only during a rescan. This means that the datastore may become inaccessible on a host during a rescan if the VMFS partition was deleted after the last rescan. The partition table is physically located on the LUN, so all vSphere hosts that have access to this LUN can see the change has taken place. However, only the hosts that do a rescan will be affected.   This article provides information on: Determining whether this is the same problem Resolving the problem   Cause This issue occurs because the VMFS partition can be deleted by deleting the datastore from the vSphere Client. This is prevented by the software, if the datastore is in use. It can also happen if a physical server has access to the LUN on the SAN and does an install, for example.   Resolution To resolve this issue: Run the  partedUtil  command on the host with the issues and verify if your output

Unlock the VMware VM vmdk file

  Unlock the VMware VM vmdk file Kill -9 PID Sometimes a file or set of files in a VMFS become locked and any attempts to edit them or delete will give a device or resource busy error, even though the vm associated with the files is not running. If the vm is running then you would need to stop the vm to manipulate the files. If you know that the vm is stopped then you need to find the ESX server that has the files locked and then stop the process that is locking the file(s). 1. Logon to the ESX host where the VM was last known to be running. 2.  vmkfstools -D /vmfs/volumes/path/to/file  to dump information on the file into /var/log/vmkernel 3.  less /var/log/vmkernel  and scroll to the bottom, you will see output like below: a. Nov 29 15:49:17 vm22 vmkernel: 2:00:15:18.435 cpu6:1038)FS3: 130: <START vmware-16.log> b. Nov 29 15:49:17 vm22 vmkernel: 2:00:15:18.435 cpu6:1038)Lock [type 10c00001 offset 30439424 v 21, hb offset 4154368 c. Nov 29 15:49:17 vm22 vmkernel: gen 664