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

Question كيفية عمل share للـ outlook conntact لكل الـ Domain Users

  الحل بسيط جدا عايز الكونتاكت تتحدث دايما بحيث انك لما تضيف يوزر جديد يسمع في الكونتاكت اول حاجه بتدخل علي in office 2003 tools --- email account ---- add address book --- internet directory service (LDAP) type your server name then login info . mark this server require me to logon type any user on active directory and its password then save and close outlook and open it again now you will find all your active directory users in address book

ما هى ال 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

3 things has to be done for better performance

  Tips from Goutham: 3 things has to be done for better performance: By default, XP displays extra graphic objects for menu items which can slow down your display. 1. To turn off these selectively... Right click My Computer Select Properties Click Advanced tab Under Performance, click Settings button To turn them all off, select Adjust for best performance Preference is to leave them all off except for Show shadows under mouse pointer and Show window contents while dragging 2. To speed up the display of the Start Menu Items, turn off the menu shadow. Right click open area of the Desktop Select Properties Click Appearance tab Click Effects button Uncheck Show shadows under menus 3. You can increase system performance by loading more of the system into memory. DO NOT attempt this with less then 512MBs of ram. Your system will become unstable. Click Start Click Run Enter regedit Click OK Go to HKEY_LOCAL_MACHINE SYSTEM CurrentControlSet Control Session Manager Memory Management Double cli