Can't see ESXi datastore on synology device after DSM upgrade

I have a VMware ESXi lab in my home using two physical hosts and a Synology NAS device. I've been using this for some years now without issue.  I am setting up a newer lab on two ESXi "hosts" that I'm running on my Mac using VMware Fusion. I set this up the other day and created the VCA on the Synology datastore and it was working just fine.  The only issue I had was speed since my Mac and the two new hosts are living in one part of my house and the Synology device is in the basement connected by a wireless network. While it ran OK, it was obviously a little slow and I decided to move the Synology box to the GB connection near my Mac. There is no routing going on here... it's all one big happy network and the wireless devices just create a mesh network to connect everything together in my house.

Before I moved the Synology box, I noticed that I was woefully behind on my updates so I applied all of the waiting updates. I didn't notice what version of DSM I was on before I started, but I'm on 6.1 now. After I did that and moved the box, I fired everything back up on the new lab and that's when the problems began. The hosts recognize the iSCSI setup and it sees the Synology device and the Synology device sees the iSCSI connections from the lab, but it no longer sees the datastore. I've tried doing everything i can think of in the ESXi environment to get the datastore back and nothing works.  I even took the box back to the basement and fired up the old lab and it also fails to see the datastore.  I haven't done anything to delete or screw with the datastore that I know of and I'd really like to be able to get this running again without having to completely rebuild the lab.
LVL 28
jhyieslaAsked:
Who is Participating?
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
okay...then a few commands to type then..

esxcfg-volume -l 

Open in new window


hopefully it return something like

~ # esxcfg-volume -l
VMFS3 UUID/label: 4cc89503-f054d0d4-2865-00221958e471/nas3-vmfs
Can mount: Yes
Can resignature: No (the volume is being actively used)
Extent name: naa.600140588e9bab7d2b7ed4b53dadc1de:1     range: 0 - 1048319 (MB)

and then type

esxcfg-volume -m 4cc89503-f054d0d4-2865-00221958e471

or

esxcfg-volume -m nas3-vmfs

Open in new window

0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
can you see the LUN connected ? or is the LUN missing as well ?
0
 
jhyieslaAuthor Commented:
In the vSphere web client looking at the host under storage and then the Devices tab, I can see the Synology device and I can see the correct size of the LUN.  Also, when I look at the Synology device's web interface, i can see the IQN numbers and descriptions of the hosts where I've made the iSCSI connection. I don't have to do anything in the Synology software for this to appear.  The only thing missing is the datastore int he Datastores tab.
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
okay, can you get to the console or remote via SSH to host ?
0
 
jhyieslaAuthor Commented:
I can definitely SSH to them.
0
 
jhyieslaAuthor Commented:
When I run the first command, it just returns the prompt; no output.
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
That is odd, that would suggest, it cannot find the datastore.

time to look at the logs....

/var/logs/vmkernel.log
0
 
jhyieslaAuthor Commented:
OK, attaching vmkernel.log file from one of the hosts.
vmkernel.log
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
from the logs...

2018-03-12T11:46:20.006Z cpu0:66027)WARNING: ScsiPath: 4440: The Physical block size "2048" reported by the path vmhba64:C0:T0:L0 is not supported. The only supported physical blocksizes are 512 and 4096
2018-03-12T11:46:20.006Z cpu0:65555)WARNING: ScsiPath: 4440: The Physical block size "2048" reported by the path vmhba64:C0:T0:L0 is not supported. The only supported physical blocksizes are 512 and 4096

So something has changed in DSM...with your upgrade to 6.1, which is causing the storage not to be compatible with ESXi.

do you have any options like here

http://www.virten.net/2016/12/the-physical-block-size-reported-by-the-device-is-not-supported/
0
 
jhyieslaAuthor Commented:
Not sure I do.  There's a lot of settings in there that I've never had to mess with.  I'll have to look thru it and maybe contact Synology.  I'll let you know.  Thanx...
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Physical Block size reporting ????
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
this could also be it.... a forum complaint about iSCSI stack...

https://forum.synology.com/enu/viewtopic.php?t=128566
0
 
jhyieslaAuthor Commented:
K, thanx... I'll look into that.
0
 
jhyieslaAuthor Commented:
I heard from Synology.  The tech had me send him a debug log file and he didn't see really anything in it that indicated a problem. However, he asked if I could see the LUN, which I can, and if I can create another datastore. I looked at that last night and tried to create a test one, that seemed to create OK, but there's so little space on it that I couldn't do anything with it so I deleted it. Now, when I go in to create a datastore in ESXI, the wizard shows that it thinks all of the LUN is free space instead of only a small fraction. I have a feeling that I accidentally did something last night that actually wiped out the datastore and it's just gone.:(

I've also said to the tech that it's not that I can't reproduce the lab, but wondered what caused this in the first place and is there any known incompatibilities with ESXi and this level of the DSM firmware.
0
 
jhyieslaAuthor Commented:
Thanx for your help
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.