• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 628
  • Last Modified:

Datastore disappeared after Logical Disk resize on ESXi 5

As mentioned in Question Q_28363425, I migrated a RAID Array from RAIS 1+0 to RAID 5. After it's completion I extended the Logical Disk from roughly 1.8TB to 2.8TB (4x 1TB disks approx).
Now the datastore is gone and not viewable in ESXi.
Looking back I now realise that what has happened is that as the original Logical Disk was in MBR, that now it's over the 2TB limit it's unreadable... Is there any way to revert it or change it without data lost??
0
kiwistag
Asked:
kiwistag
  • 5
  • 3
2 Solutions
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
ESXi 5.0 is not limited to 2TB VMFS datastores anymore, it's 64TB

see here

https://www.vmware.com/pdf/vsphere5/r50/vsphere-50-configuration-maximums.pdf
0
 
kiwistagAuthor Commented:
.. For a GPT disk yes, but as the disk/partitions are still in MBR I'm in trouble.
This system is an upgrade from ESXi 4.1 so doesn't have a GPT format (let alone UEFI).
0
 
kiwistagAuthor Commented:
gPartEd sees all partitions which is a start. I'm looking at here for assistance..
https://communities.vmware.com/thread/412601
0
[Webinar] Improve your customer journey

A positive customer journey is important in attracting and retaining business. To improve this experience, you can use Google Maps APIs to increase checkout conversions, boost user engagement, and optimize order fulfillment. Learn how in this webinar presented by Dito.

 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Okay, this was VMware vSphere 4.0 partition before. You question title suggests ESXi 5.0.

This is the issue.

Has the partition been expanded, as you have just expanded the logical disk?

I would shrink back the VMFS partition, to under 2TB if possible.

Did you take backups before the alteration?
0
 
kiwistagAuthor Commented:
The system has been ESXi for the last year, however beforehand was ESXi 4.1.
The logical disk has been expanded to 3TB, but the partition has not.
The VMFS partition is 1.8TB still, however ESXi 5 cannot read it in this state, I can only assume that as the (RAID LV) disk is bigger than 2TB and it is not GPT that ESXi doesn't know how to read it.
By using the MightyCare Recovery Disk, with it's later FUSE system supporting VMFS-5, I can now read the disk.
I'm copying it now to a NFS share (via SCP - since there are issues with our NAS/SAN and the Linux NFS version it seems), but at 5MBps it's going to be slow copying a main VM of 1.4TB... :/

As for backups, it looks like 1x didn't take and the other one (split-site) is 4-5 days old..

The other VM on there hasn't backed up successfully this week also. At least it's not as mission critical..
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
I think your solution is this is the best course of action, rather than meddle with the logical disk!
0
 
kiwistagAuthor Commented:
It looks like files over 150GB(ish) can't be easily copied. So far through Linux via cp or ftp I get an I/O error.
SCP works but is phenominally slow (1-6MBps max) and from experience seems to time out.
I'm trying dd  from the logical disk to a iSCSI disk.
0
 
Gerald ConnollyCommented:
A classic example of why you should always take a backup before changing things - Just in case

and always make its a viable backup!
0
 
kiwistagAuthor Commented:
Solution is the prevention in a way, ensure backups are consistent.
The recovery was a rather extended process in this scenario.
0

Featured Post

Receive 1:1 tech help

Solve your biggest tech problems alongside global tech experts with 1:1 help.

  • 5
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now