iSCSI LUN Blank? Data Lost?

[jhagan]

TS-869 Pro firmware 4.1.3 - connected to ESXi 6.0 host.

I have an urgent issue. We had some trouble with ESXi server today and had to reboot it. The iSCSI based data store went missing so I tried to re-attach it. The iSCSI Storage Adapter shows the QNAP connected.

In vSphere if I go to Storage - Add Storage I can walk through a wizard that will connect to the 2TB LUN but it says "the hard disk is blank". I cancel since I don't want to format the drive.

Is there anything I can try or is the LUN trash? The QNAP shows a 2TB LUN "connected" and 74% allocated.

Any advice is greatly appreciated.

[elohab85]

A similar problem occurred like Jhagan had after a few power outages.

We use TS-412U firmware 4.2.0 - connected to ESXi 6.0 host. I tried everything Jhagan did. But the problem progress still. The iSCSI based data store went missing. The iSCSI Storage shows the QNAP connected. I can not find my luns on QNAP Storage Manager. The QNAP shows a 10 TB LUN "connected" and 99% allocated. I got help from QNAP Help Desk via Remote Connection(SSH). But They says; "We did not have way to reach it you need to find the data recovery company if its important. Sorry if I have way then I will help in my best but I can not saw it".

I find a link that below when surfing to internet,
http://www.it-support-singapore.com/it- ... -recovery/

according to you, Should I do as described in the link.

or Is there any way to solve this problem?

Any advice is greatly appreciated

Best Regards
Murat Çelebi

[mturkyilmaz]

Lun Not Found

[schumaku]

What's in /etc/config/iscsi_trgt.conf ?

[~] # cat /etc/config/iscsi_trgt.conf
...

Container files still around?

[~] # ls -als /share/MD0_DATA/.@iscsi.img/
...

[rickkellen]

It looks like I have a similar issue so I am just posting here to see if I could get some help finding the missing files on the Virtual Disk.

Here is what is in the /etc/config/iscsi_trgt.conf on the hardware that is acting as the Virtual Disk
[iSCSIPortal]
bServiceEnable = TRUE
servicePort = 3260
initiatorBitmap00 = 00000001
bISNSEnable = FALSE
ISNSIP =
targetIQNPrefix = iqn.2004-04.com.nas:storage:iscsi.
targetBitmap00 = 00000001
LUNBitmap00 = 00000001
[init0Info]
initiatorIndex = 0
initiatorIQN = iqn.2004-04.com.qnap:all:iscsi.default.ffffff
initiatorAlias = Default Policy
initiatorTargetBitmap00 = 00000001
initiatorLUNBitmap00 = 00000001
[InitiatorKey]
iqn.2004-04.com.qnap:all:iscsi.default.ffffff = 0
[target0Info]
targetIndex = 0
targetName = moconas02
targetIQN = iqn.2004-04.com.nas:storage:iscsi.moconas02.c3c6ca
targetAlias = moconas02
bTargetDataDigest = FALSE
bTargetHeaderDigest = FALSE
targetStatus = 0
targetInitBitmap00 = 00000001
targetLUNNumBitmap00 = 00000001
targetLUNBitmap00 = 00000001
[TargetKey]
target_iqn.2004-04.com.nas:storage:iscsi.moconas02.c3c6ca = 0
[target0Init0Info]
targetIndex = 0
initiatorIndex = 0
bCHAPEnable = FALSE
bMutualCHAPEnable = FALSE
CHAPUserName =
CHAPPasswd =
mutualCHAPUserName =
mutualCHAPPasswd =
[LUN0Info]
LUNIndex = 0
LUNName = moconas02
LUNPath = /share/MD0_DATA
LUNMetaPath = /share/MD0_DATA/.@iscsi.img/iSCSI-moconas02-4ce5654b:006
LUNCapacity = 5593088
LUNFileCount = 6
LUNThinAllocate = TRUE
LUNStatus = 2
LUNInitBitmap00 = 00000001
LUNAttachedTarget = 0
LUNNumber = 0
LUNEnable = TRUE
LUNSerialNum = 4981b0d3-32a6-4654-893e-6a9c3d2aa641
FBNumber = 0
[LUNKey]
LUN_moconas02 = 0
[LUN0Init0Info]
LUNIndex = 0
initiatorIndex = 0
initiatorLUNNumber = -1
accessMode = 1

And here are what shows up for the "Container files" using ls -als /share/MD0_DATA/.@iscsi.img/
4 drwxrwxrwx 2 admin administ 4096 Jan 5 2011 ./
4 drwxrwxrwx 19 admin administ 4096 Jul 29 2012 ../
1049219868 -rw------- 1 admin administ1099511627776 Nov 18 2010 iSCSI-moconas02-4ce5654b.000
1073740680 -rw------- 1 admin administ1099511627776 Nov 18 2010 iSCSI-moconas02-4ce5654b.001
1073738192 -rw------- 1 admin administ1099511627776 Nov 18 2010 iSCSI-moconas02-4ce5654b.002
994787116 -rw------- 1 admin administ1099511627776 Nov 18 2010 iSCSI-moconas02-4ce5654b.003
911674276 -rw------- 1 admin administ1099511627776 Nov 18 2010 iSCSI-moconas02-4ce5654b.004
358613716 -rw------- 1 admin administ367219703808 Nov 18 2010 iSCSI-moconas02-4ce5654b.005
4 -rw------- 1 admin administ 1048576 Jan 5 2011 virtual_lun0

Any help getting the files to show up again would be greatly appreciated.

[dolbyman]

what nas model
what firmware
what issues do/did you have
no backups of the LUN?

[rickkellen]

It is a different brand. Tandberg DPS2142 with firmware version 3.4.4 Build 0718T. Research indicated it is basically a rebranded Turbo NAS. I believe a TS-459U.

The units were powered down for a while. I needed to retrieve an old file that was on this hardware. When everything was powered up the NAS with the virtual disk had an IP conflict. I changed the IP of that unit and tried to add it again as a virtual disk with the new IP. After trying to add it I got an error that it couldn't connect but the previous Virtual Disk connection showed up as connected with the new IP. I thought everything was fine but then when I looked at the Share Folder that was on the Virtual Disk it showed up with no folders or files. I have tried rebooting and reconnecting but that has not fixed the problem. I am fairly sure that the files are still there because the disk usage shows 5208.94GB used and 288GB free space and there is nothing other than the Virtual Disk Share items on that NAS.

I had been running backups to duplicate hardware but unfortunately that hardware has the exact same issue.

[dolbyman]

tried to attach a different machine to that LUN ?

hard to give support for an ancient modified firmware... as the hardware might be QNAP , but the firmware is basically unknown to us here

[rickkellen]

Completely understand not being able to provide support for different firmware. It was more just a hope that there might be some way to find a path to where the files are stored on the NAS so they could be copied to another device. Or if there was just some standard known fix when an issue like this happens.

[storageman]

You should have started an new thread!

With this lack of information is difficult to help. No screenshots or IP address details
Can you see the LUN(s) listed?
Did you try recreating the target?
Why would you have got an IP conflict?
Google "qnap lun recovery" and unofficialqnapsupport.net