Virtual hard drives larger than 256GB

Version 1
    This document was generated from CDN thread

    Created by: David Robles on 01-06-2011 06:45:28 PM
    I'm attempting to install an OS (Cisco eCDS 2.5.3) on a virtual machine that requires two 400+GB hard drives using SRE-V software on an SRE-900 with the RAID 0 configuration/installation type. After the SRE-V installation and logging in as root using vSphere Client, the hypervisor seemed to have detected the single 1TB ( more so around 927GB ) physical hard drive and created a datastore for it automatically. However the datastore was configured with a 1MB block size which limits the maximum virtual hard drive capacity to 256 GB. The only way I know to increase the block size would be to delete this datastore and increase the block size from the datastore creation wizard. When I attempt to delete the datastore from hypervisor->Configuration->Storage->Datastores table I get the following error:
     
    "Call "HostDatastoreSystem.RemoveDatastore" for object "ha-datastoresystem" on ESXi "192.168.1.21" failed."
     
    Please advise.

    Subject: RE: Virtual hard drives larger than 256GB
    Replied by: Brett Tiller on 01-06-2011 07:41:12 PM
    Hi David,

    We checked the VMware Knowledgebase.  As you suspected you do need to delete the datastore and then create a new one with the block size you desire.  Regarding the deletion failure, please try the steps provided in this link and let us know the results.  According to VMware this should allow you to delete the datastore.

    http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1017104

    Thanks,

    Brett

    Subject: RE: New Message from David Robles in Service Ready Engine Virtualization -
    Replied by: Brett Tiller on 02-06-2011 05:45:09 PM
    Hi David,



    Glad that¿s working for you.  We¿re taking a look at the failure occurring when using the vSphere client.



    Thanks,



    Brett

    Custom Application Engineer

    http://developer.cisco.com/web/axp <http://developer.cisco.com/web/axp>

    http://developer.cisco.com/web/srev <http://developer.cisco.com/web/srev>





    From: Cisco Developer Community Forums [mailto:cdicuser@developer.cisco.com]
    Sent: Thursday, June 02, 2011 1:27 PM
    To: cdicuser@developer.cisco.com
    Subject: New Message from David Robles in Service Ready Engine Virtualization - SRE-V Beta Tester Questions: RE: Virtual hard drives larger than 256GB



    David Robles has created a new message in the forum "SRE-V Beta Tester Questions":

    --------------------------------------------------------------
    Thanks for the break down Brett. Seems I was using fdisk incorrectly.

    After deleting the datastore via command-line I tried then using the vSphere Client GUI to create the new datastore and I got a similar error alert window as I did with the GUI datatstore removal option:

    "Call "HostDatastoreSystem.CreateVmfsDatastore" for object "ha-datastoresystem" on ESXi "192.168.1.21" failed."

    I then resorted to the pure command-line procedure and got it working. We will note this procedure in case this issue persists in the release build. Thanks again.
    --
    To respond to this post, please click the following link:

    <http://developer.cisco.com/web/srev/forums/-/message_boards/view_message/3995755>

    or simply reply to this email.

    Subject: RE: Virtual hard drives larger than 256GB
    Replied by: David Robles on 02-06-2011 03:05:44 PM
    That post only shows how to remove partitions in case a used partition is what's blocking the datastore removal. However the datastore had no partitions probably since I hadn't created a VM yet. Are there any other methods of removing the datastore via command line?
     
    ~ # fdisk /vmfs/devices/disks/eui.e4580e4e9af60000:3 -l

    Disk /vmfs/devices/disks/eui.e4580e4e9af60000:3: 995.5 GB, 995589619712 bytes
    255 heads, 63 sectors/track, 121040 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes

    Disk /vmfs/devices/disks/eui.e4580e4e9af60000:3 doesn't contain a valid partition table
    ~ # fdisk /vmfs/devices/disks/eui.e4580e4e9af60000:3
    Device contains neither a valid DOS partition table, nor Sun, SGI or OSF disklabel
    Building a new DOS disklabel. Changes will remain in memory only,
    until you decide to write them. After that the previous content
    won't be recoverable.


    The number of cylinders for this disk is set to 121040.
    There is nothing wrong with that, but this is larger than 1024,
    and could in certain setups cause problems with:
    1) software that runs at boot time (e.g., old versions of LILO)
    2) booting and partitioning software from other OSs
       (e.g., DOS FDISK, OS/2 FDISK)
    Warning: invalid flag 0x00,0x00 of partition table 4 will be corrected by w(rite)

    Command (m for help): d
    No partition is defined yet!

    Subject: RE: New Message from David Robles in Service Ready Engine Virtualization -
    Replied by: Brett Tiller on 02-06-2011 03:48:09 PM
    Hi David,

    You should be able to access/delete partitions if you don't specify the partition when using fdisk.  We did see a few issues with the deletion and datastore creation.  Please try the following steps below and let us know your results.

    1.       fdisk /vmfs/devices/disks/eui.e4580e4e9af60000
    2.       Delete just partition 3. This will get rid of the datastore.
        a.       Command (m for help): d
        b.      Partition number (1-4): 3
        c.       Command (m for help): w
                                                                        i.      The partition table has been altered!
    3.      Add new partition 3.
        a.       fdisk /vmfs/devices/disks/eui.e4580e4e9af60000
        b.      Command (m for help): n
        c.       Command action
              e   extended
              p   primary partition (1-4)
             enter: p
        d.      Partition number (1-4): 3
                                                                         i.      First cylinder (537-60788, default 537): Using default value 537
                                                                       ii.      Last cylinder or +size or +sizeM or +sizeK (537-60788, default 60788): Using default value 60788
        e.       Command (m for help): w
                                                                         i.      The partition table has been altered!
    4.      Set partition 3 type
        a.       fdisk /vmfs/devices/disks/eui.e4580e4e9af60000
        b.      Command (m for help): t
                                                                         i.      Partition number (1-4): 3
                                                                       ii.      Hex code (type L to list codes): fb
           iii.      Changed system type of partition 3 to fb (VMFS)
        c.       Command (m for help): w
                                                                        i.      The partition table has been altered!
    5.      Create the new datastore on partition 3 with 8 MB block.
        a.       vmkfstools -C vmfs3 -b 8M -S "datastore1" /dev/disks/eui.e4580e4e9af60000:3
           Checking if remote hosts are using this device as a valid file system. This may take a few seconds...
           Creating vmfs3 file system on "eui. e4580e4e9af60000:3" with blockSize 8388608 and volume label "datastore1".
           Successfully created new volume: 4de697a4-cce8942a-b960-0023eba107fd


    Thanks,

    Brett
    Custom Application Engineer
    http://developer.cisco.com/web/axp <http://developer.cisco.com/web/axp>
    http://developer.cisco.com/web/srev <http://developer.cisco.com/web/srev>

    Subject: RE: Virtual hard drives larger than 256GB
    Replied by: David Robles on 02-06-2011 04:27:29 PM
    Thanks for the break down Brett. Seems I was using fdisk incorrectly.

    After deleting the datastore via command-line I tried then using the vSphere Client GUI to create the new datastore and I got a similar error alert window as I did with the GUI datatstore removal option:

    "Call "HostDatastoreSystem.CreateVmfsDatastore" for object "ha-datastoresystem" on ESXi "192.168.1.21" failed."

    I then resorted to the pure command-line procedure and got it working. We will note this procedure in case this issue persists in the release build. Thanks again.

    Subject: RE: Virtual hard drives larger than 256GB
    Replied by: David Robles on 02-06-2011 08:52:29 PM
    Do you happen to know if this is only a problem with vSphere client or does it also occur with vCenter?

    Subject: RE: New Message from David Robles in Service Ready Engine Virtualization -
    Replied by: Radhika Miriyala on 03-06-2011 12:09:09 PM
    Hi David,

    The behavior will be same in both vSphere client and vCenter.



    Thanks,

    Radhika



    From: Cisco Developer Community Forums [mailto:cdicuser@developer.cisco.com]
    Sent: Thursday, June 02, 2011 5:52 PM
    To: cdicuser@developer.cisco.com
    Subject: New Message from David Robles in Service Ready Engine Virtualization - SRE-V Beta Tester Questions: RE: Virtual hard drives larger than 256GB



    David Robles has created a new message in the forum "SRE-V Beta Tester Questions":

    --------------------------------------------------------------
    Do you happen to know if this is only a problem with vSphere client or does it also occur with vCenter?
    --
    To respond to this post, please click the following link:

    <http://developer.cisco.com/web/srev/forums/-/message_boards/view_message/3996062>

    or simply reply to this email.