Hi,
I am in the process of cold moving a number of vm's from our old 5.5 platform to our new 6.5. Our storage server comprises of two disks, boot and storage. The storage disk is 2.7tb and is a separate virtual disk on a separate datastore, thin provisioned. When I register the vm on the new 6.5 host the storage disk doesn't get recognised correctly and has an alert icon next to it. The capacity on the disk is listed as zero, and I cannot increase the capacity as the option is greyed out. In the maximum size option it states: N/A Maximum virtual disk size will not be validated if datastore cluster is selected as storage. In the disk name section it identifies the file location in the following format []/vmfs/volume no xxx.vmdk
If I add the disk as an existing disk all seems fine apart from the fact the maximum disk size is listed as only 67gb (The actual disk size of 2.7tb is picked up) and I cannot change it. The disk file location is listed as expected: datastore name\disk name.vmdk.
Any clues as to why the second disk settings are not picked up correctly? Will the storage disk work/ be safe to use if I dd it as an exisiting disk with the above settings?
Cheers,
Paul
I am in the process of cold moving a number of vm's from our old 5.5 platform to our new 6.5. Our storage server comprises of two disks, boot and storage. The storage disk is 2.7tb and is a separate virtual disk on a separate datastore, thin provisioned. When I register the vm on the new 6.5 host the storage disk doesn't get recognised correctly and has an alert icon next to it. The capacity on the disk is listed as zero, and I cannot increase the capacity as the option is greyed out. In the maximum size option it states: N/A Maximum virtual disk size will not be validated if datastore cluster is selected as storage. In the disk name section it identifies the file location in the following format []/vmfs/volume no xxx.vmdk
If I add the disk as an existing disk all seems fine apart from the fact the maximum disk size is listed as only 67gb (The actual disk size of 2.7tb is picked up) and I cannot change it. The disk file location is listed as expected: datastore name\disk name.vmdk.
Any clues as to why the second disk settings are not picked up correctly? Will the storage disk work/ be safe to use if I dd it as an exisiting disk with the above settings?
Cheers,
Paul
Learn from the best
Network and collaborate with thousands of CTOs, CISOs, and IT Pros rooting for you and your success.
Andrew Hancock - VMware vExpert
See if this solution works for you by signing up for a 7 day free trial.
Unlock 1 Answer and 7 Comments.
Try for 7 days”The time we save is the biggest benefit of E-E to our team. What could take multiple guys 2 hours or more each to find is accessed in around 15 minutes on Experts Exchange.
Our community of experts have been thoroughly vetted for their expertise and industry experience.
The Fellow title is reserved for select members who demonstrate sustained contributions, industry leadership, and outstanding performance. We will announce the experts being inducted into the Experts Exchange Fellowship during the annual Expert Awards, but unlike other awards, Fellow is a lifelong status. This title may not be given every year if there are no obvious candidates.
The Expert of the Year award recognizes an expert who helped improve Experts Exchange in the past year through high levels of contributions and participation on site. This award is given to the expert who has achieved the highest levels of participation, while maintaining quality contributions and professionalism.