My QNAP Lun is suddenly empty!

[level42]

So, I have 2 QNAPs, and in order for them to talk to each other, I set one as an ISCSI Target, and one as the Initiator.

Everything was working perfectly fine for a few months now, when suddenly I connected to the LUN only to find out that it's COMPLETELY EMPTY!!!!

It still shows that there is only 5 out of 8 TB free space, but I cannot find any of my files.

I've tried rebooting both qnaps, restarting the ISCSI services on both, nothing seems to be working.

I can still connect to the target, and received no errors or warnings in that time, but now, it's just EMPTY. How can I get my files back?

[dolbyman]

anything happened ?

firmware update
power loss
connection loss

ISCSI luns are a little fragile


on another note...why do you need ISCSI for the NAS to exchange information? SMB would be much more transparent

[level42]

I couldn't figure out how to map one qnap to another through ISCSI, I need access to the files on QNAP A from QNAP B and vise vers

The only thing that happened was a loss of Internet access from my ISP due to a node failure.

At the same time, the firmware on my router went corrupt and I had to rebuild it, losing any and all configuration changes I had made.

[dolbyman]

did you try to attach to the lun via any other device ?
windows,mac,linux ?

[storageman]

Mystified why you would use ISCSI in this scenario.
What was wrong with shares?

[level42]

I mounted the LUN on Windows, and it warned me that the drive needed to be formatted before it could be used ...

As to why I used a LUN, I wrote a topic a while back asking for advice on this matter, but users were more interested in pointing out technicalities in my thread, then helping me at all.

viewtopic.php?f=185&t=140940&p=668951#p668951

If there is a better method, I'd love to hear it.

[dolbyman]

that thread was not very detailed and discussion suddenly stopped

what files system was the LUN formatted at ? if ext4, windows would not be able to read it (natively)

so use a windows addon tool
https://www.howtogeek.com/112888/3-ways ... m-windows/

or Mac or Linux to access to LUN (e.g. https://github.com/gerard/ext4fuse)

[P3R]

Data is most easily stored and accessed in shared folders.

Data is most easily transferred between NASes with a backup program, like the now current Hybrid Backup Sync.

Unless you know for sure that a LUN is the only way to achieve what you want to do, then a LUN is most likely isn't what you want to use.

[OneCD]

As to why I used a LUN, I wrote a topic a while back asking for advice on this matter, but users were more interested in pointing out technicalities in my thread, then helping me at all.

viewtopic.php?f=185&t=140940&p=668951#p668951

The topic linked-to does not mention iSCSI at all. If you wanted assistance, why did you abandon that thread?

And if a user corrects your misunderstanding regarding CPU architecture, thank them.

[level42]

ISCSI wasn't mentioned, because that was the solution that I came up with on my own after the lack of assistance on that thread. and it's beginning to appear to happen to this thread again. Instead of assistance, I'm getting berated about things that are completely irrelevant to the topic at hand. Can we please just stay on topic here?

From my understanding the ISCSI LUN was created as an EXT3 partition. @dolbyman I appreciate the suggestion and will test out that link shortly and report back.