Partitions seen as raw on Lenovo SAN
Hello, we have a BIG problem with a SAN (Lenovo DS2200). The new Windows 2016 server failed and we have setup an old Lenovo server, installing once again Windows server 2016.
Problem is, we can't access the storage inside the SAN. The connection is Fiber Channel and we see the partitions, but we only see them as raw partitions and can't find a way to access the data to recover it (it's basically virtual machines for a cluster).
We know the data is whole, because we can see this from the SAN web interface. But we cannot access it.
We never had to deal with something like this, so I was wondering if some kind soul would share some ideas here because we are drowning right now. Customer's at our throat.
Problem is, we can't access the storage inside the SAN. The connection is Fiber Channel and we see the partitions, but we only see them as raw partitions and can't find a way to access the data to recover it (it's basically virtual machines for a cluster).
We know the data is whole, because we can see this from the SAN web interface. But we cannot access it.
We never had to deal with something like this, so I was wondering if some kind soul would share some ideas here because we are drowning right now. Customer's at our throat.
How are accessing theSAN resource.
FC is merely the mode by which the SAN presents the LUNs
Double check you zoned access on the SAN for the new system.
Double check that you mount the LUN in the same way the prior was
Do not initialize.
If the 2016 is a hyper-v host, the LUN might need to be loaded under the hyper-v as a storage resources, versus under the oS host as a device.
The raw part suggests that you are accessing the LUN in a different way compared to the prior
I.e. The VM storage is raw with vhd/vhdx items within.
If yours an includes requisite space, create a new similar sized LUN, close this one into the new, and try to access.
..
FC is merely the mode by which the SAN presents the LUNs
Double check you zoned access on the SAN for the new system.
Double check that you mount the LUN in the same way the prior was
Do not initialize.
If the 2016 is a hyper-v host, the LUN might need to be loaded under the hyper-v as a storage resources, versus under the oS host as a device.
The raw part suggests that you are accessing the LUN in a different way compared to the prior
I.e. The VM storage is raw with vhd/vhdx items within.
If yours an includes requisite space, create a new similar sized LUN, close this one into the new, and try to access.
..
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
I am uncertain whether hyper-v needs an ntfs formatted partition to be used as the VM storage volume.
Not clear what is seen on the San interface.
There are reason to use raw, unmounted partitions, volumes. As a storage volume.
When the FC LUN is connected, in hyper-v the storage is pointed to and rescanned, does it not reflect the VMs stored there?
DO NOT INITIALIZE THE VOLUME UNDER ANY CIRCUMSTANCE OR IT WILL WIPE THE DATA.
Did your install match the prior I.e. Loaded as hyper-v core?
Not clear what is seen on the San interface.
There are reason to use raw, unmounted partitions, volumes. As a storage volume.
When the FC LUN is connected, in hyper-v the storage is pointed to and rescanned, does it not reflect the VMs stored there?
DO NOT INITIALIZE THE VOLUME UNDER ANY CIRCUMSTANCE OR IT WILL WIPE THE DATA.
Did your install match the prior I.e. Loaded as hyper-v core?
ASKER
I recovered the vhd files using Easeus Data Recovery. Not sure what the reason was for partitions to be unusable.
How did the original server fail? That's probably the source of the partition wipe.
ASKER
The original server, which was brand new, lost its embedded raid controller and probably one hard drive.
Okay, that is indeed the likely culprit.
But, check the FC switch setup to make sure permissions are given to the newly stood up server(s). There should be some names or GUIDs/IDs that indicate permission to access the LUNs on the SAN.
The permissions may need to be configured on the FC NICs/Ports on the server(s).
EDIT: And, permissions may need to be added to the LUNs list too.