iSCSI LUN Corrupted after reboot

[itbrd]

Hello,
we have a small installation.
One DELL Server as HOST VMware with five Virtual Machine (Windows Server 2016).
The host has few local storage.
Most of the data is on a LUN iSCSI created on the QNAP (following your how-to) attached to the VMware ESXi 6.0 Host.

All has worked good in the lasts months.

Past week we had to shutdown all our hardware due to a maintenance on the electrical system.

We followed a good defined steps, in order to avoid trouble:

1) Normally shutdown all Windows Server 2016 Guest OS
2) Wait five minutes and check vCenter Server: all Guest OS were power off
3) Shutdown our single VMware ESXi 6.0 host
4) Wait five minutes and check QNAP web administration: no opened connection on the iSCSI target
5) Shutdown QNAP


After the maintenance we followed basic steps:

1) Power on QNAP and wait five minutes
2) Power on our single VMware host
3) Wait until the guest OS power on


Here our big issue; our host correctly connect to the QNAP iSCSI LUN, wa can browse datastore and there are all the virtual machines, file, etc..
But the virtual machines can't start (boot loop). The files (vmdk, vmx, etc.) is visible from VMware datastore browser but the data inside the vmdk is corrupted. All the content of the QNAP iSCSI LUN is corrupted, lost, we need to restore all our server from our backup.

No alert, no issue on the QNAP or other hardware (host, switch, etc.).

Now it's impossible for us to lost all our data every time we need to power off the system.
There is something wrong on the above procedure (shutdown and startup)?

We have other QNAP (older then this one) and we have shutdown it many times (also without the proper care, during a power outage) but we have never had a so big issue.

Thank you.

Below the specifications:

- TS-463-U-RP
- WD30EFRX 3TB x 4 (RAID 10)
- One Block LUN thick provisioned

[storageman]

The shutdown startup/method is correct.

You know that model is not on the Vmware approve list.

[itbrd]

Ok thank you.

Set up a VMware ESXi Datastore via iSCSI with QNAP (as how-to from QNAP) is not on the Vmware approve list?

[storageman]

http://partnerweb.vmware.com/comp_guide ... tegory=all

[itbrd]

Ok, the specific TS-463-U-RP model is not on the VMware compatibility list.

Apart the official listing, the QNAP hardware / OS / Firmware are really so different from TS-x53 Series officially listed?

I'll plan a model switching in order to be compliance but I'll ask to QNAP and also to VMware if the model is really not compatible (and what's the meaning of write "VMware Support" on the QNAP TS-463U-RP product page)


Thank you

[storageman]

Yes, doesn't mean it won't work but support are unlikely to help you.

I have seen this before, are you able to test a volume LUN?

[itbrd]

I created a support ticket with Qnap and I hope they can give me some sort of feedback.
Maybe I'll ask support to VMware, but I think it's an issue at QNAP level.

Yes, I can set up a volume LUN, make a test VM with storage on it and then I'll shutdown / startup the entire system.

Before, I have to wait new storage unit and migrate our VMs. (QNAP or others NAS officially listed on VMware compatibility guide)


Thank you

[Godrick]

I have also had corruption with the Feb 4.3.4 release. A reboot of the QNAP got me back, but it's a bit worrying. The system worked flawlessly in the past.

[ronniHartung]

I have also same issue.
chkdsk kind of fixed it, but deleted some of my files.

[storageman]

Personally I would only use ISCSI if you absolutely must do.
Qnap's support of ISCSI issues is poor.