Hey,
yeah to take this one away: someone fucked up ;-)
Environment is ESXi 5.1.0
NAS is Fujitsu Celvin q800 with raid 5 consisting of four hdd.
Storytime:
One of the hdds died and was replaced way to late. During recovery process another hdd died and the raid turned to read only, which is better than nothing I assume.
After copying the files from the read only to USB disks and playing around with the NAS there was no chance I could get it back online..
=> I deleted the logical drive and set up a new one. Created the appropiate shares and so on.. identical NFS rights / names everything looked good so far except that after the format was done the filesystem is now ext4 instead of ext3 it had before as the NAS didn't offer anything and just formatted using ext4.
---------------------------
Problem I have now: although the shares have the identical names the shares are not reachable by the ESXi using the old names.
So the NFS still appears offline to the host and VMs appear unreachable.
Checking the datastore settings and trying to mount the storage I found:
old: <NAS IP>:/<share name>
new: <NAS IP>:<share name>, so the '/' is missing now. Might this be caused by the change of filesystem? From Windows it behaves absolutely identical as far as I can say..
I hoped I could just copy the data back to the "original location" and everything would be turning back "green". Guess that's not how this works, esp as I'm not used working with linux anymore..
When checking the datastore location the adressing of "ds:///vmfs/volumes/asdasdas-asdasdas" is showing up.
The newly added storage is obviously different. Is it possible to just change the "logical linkage" between the NFS Name and the new location? As it's not possible to delete the old ones as there are still VMs on the storage, unreachable ofc.
So I just wanted to make sure that there is no other way instead of:
deleting everything referring to old NFS share
delete old NFS share name
create new NFS share with old name but "new location"
spend alot of time to get all the VMs back into the ESXi.
As a not accessable VM can not be checked for it's configuration anymore and when converting everything back all settings will be gone.
Hopefully someone is brave enough to respond as any help / suggestion is highly appreciated!