Unable to connect iSCSI LUNs after upgrade to 4.4.1

iSCSI related applications
hyvokar
Starting out
Posts: 26
Joined: Tue Aug 20, 2013 1:28 pm

Unable to connect iSCSI LUNs after upgrade to 4.4.1

Post by hyvokar » Wed Sep 25, 2019 1:22 am

Hi,

I recently upgraded my TS-853A to Firmware version 4.4.1.1064
After that I have not been able to connect any LUNs that was previously created.

I can connect to iSCSI targets on the NAS, but no LUNs are shown to Windows server machines.

If I create a new target with new LUN it shows up on the Windows server as expected.
I have tried to disable LUN and move it to the newly created target ; again the target is connected fine, but LUN does not show up.

Any ideas how to start investigating or fix this?
TS-853A 4GB 5x Seagate IronWolf 6TB + 2x SSD 860 QVO 1TB
TS-1673U-RP 24GB 12x Seagate IronWolf Pro 12TB + 2x SSD 860 EVO M.2 2TB

hyvokar
Starting out
Posts: 26
Joined: Tue Aug 20, 2013 1:28 pm

Re: Unable to connect iSCSI LUNs after upgrade to 4.4.1

Post by hyvokar » Wed Sep 25, 2019 1:34 am

Also, while doing iSCSI configurations on the NAS it seems to randomly freeze (check attachment) with "Applying, please wait..." Been like that for 10mins now.
You do not have the required permissions to view the files attached to this post.
TS-853A 4GB 5x Seagate IronWolf 6TB + 2x SSD 860 QVO 1TB
TS-1673U-RP 24GB 12x Seagate IronWolf Pro 12TB + 2x SSD 860 EVO M.2 2TB

User avatar
storageman
Ask me anything
Posts: 5096
Joined: Thu Sep 22, 2011 10:57 pm

Re: Unable to connect iSCSI LUNs after upgrade to 4.4.1

Post by storageman » Wed Sep 25, 2019 3:55 pm

Was it resolved?
What version of Windows are you connecting to, 32bit will not see more than 2TB.

hyvokar
Starting out
Posts: 26
Joined: Tue Aug 20, 2013 1:28 pm

Re: Unable to connect iSCSI LUNs after upgrade to 4.4.1

Post by hyvokar » Thu Sep 26, 2019 12:34 am

Hi,

not resolved.

Reseted the NAS to the factory defaults, removed all targets and recreated them - same result ; only the LUNs that are created after the upgrade are shown to servers.
Servers are Win2012 R2, 64bit
TS-853A 4GB 5x Seagate IronWolf 6TB + 2x SSD 860 QVO 1TB
TS-1673U-RP 24GB 12x Seagate IronWolf Pro 12TB + 2x SSD 860 EVO M.2 2TB

FSC830
Starting out
Posts: 43
Joined: Thu Mar 03, 2016 1:11 am

Re: Unable to connect iSCSI LUNs after upgrade to 4.4.1

Post by FSC830 » Thu Sep 26, 2019 2:06 pm

Strange, did you create a ticket for this issue to QNAP support?

Regards

User avatar
storageman
Ask me anything
Posts: 5096
Joined: Thu Sep 22, 2011 10:57 pm

Re: Unable to connect iSCSI LUNs after upgrade to 4.4.1

Post by storageman » Thu Sep 26, 2019 4:30 pm

Are u using LUN masking?

hyvokar
Starting out
Posts: 26
Joined: Tue Aug 20, 2013 1:28 pm

Re: Unable to connect iSCSI LUNs after upgrade to 4.4.1

Post by hyvokar » Mon Sep 30, 2019 1:38 pm

Hi,

Thank you for reply, here's the status update.
I opened a ticket with QNAP support same day I posted here, and they are trying to figure this out. So far no progress.

We ended up clearing the iscsi configuration from command line storage_util --iscsi_restore_cfg re-creating all the iSCSI targets but the problem is still the same. Only the LUNs created after upgrade are visible to Windows Servers.
The only difference I could spot with old and new LUNs are that the new ones has "FUA bit support" enabled.

@Storageman : I dont think I am, how can I check?
TS-853A 4GB 5x Seagate IronWolf 6TB + 2x SSD 860 QVO 1TB
TS-1673U-RP 24GB 12x Seagate IronWolf Pro 12TB + 2x SSD 860 EVO M.2 2TB

User avatar
storageman
Ask me anything
Posts: 5096
Joined: Thu Sep 22, 2011 10:57 pm

Re: Unable to connect iSCSI LUNs after upgrade to 4.4.1

Post by storageman » Mon Sep 30, 2019 3:48 pm

Sounds like the config file got corrupted
LUN masking stuff here
https://www.qnap.com/en/how-to/tutorial ... turbo-nas/

hyvokar
Starting out
Posts: 26
Joined: Tue Aug 20, 2013 1:28 pm

Re: Unable to connect iSCSI LUNs after upgrade to 4.4.1

Post by hyvokar » Tue Oct 01, 2019 10:00 pm

Any idea how to fix corrupted config file?

LUN masking is used, RW for LUNs
TS-853A 4GB 5x Seagate IronWolf 6TB + 2x SSD 860 QVO 1TB
TS-1673U-RP 24GB 12x Seagate IronWolf Pro 12TB + 2x SSD 860 EVO M.2 2TB

User avatar
storageman
Ask me anything
Posts: 5096
Joined: Thu Sep 22, 2011 10:57 pm

Re: Unable to connect iSCSI LUNs after upgrade to 4.4.1

Post by storageman » Tue Oct 01, 2019 10:23 pm

Start by turning LUN masking off and reassess the situation
Can't help you with drip drip drip of information.

focher
New here
Posts: 5
Joined: Fri May 13, 2011 2:26 pm

Re: Unable to connect iSCSI LUNs after upgrade to 4.4.1

Post by focher » Sun Oct 06, 2019 5:55 am

I had the same symptoms. Main difference for me is that I am connecting to the iSCSI target with a Mac. I had never had a problem until 4.4.1, and actually have an older QNAP with a different iSCSI volume that I can connect to fine.

In my case, I finally resolved it by checking two options in the initiator (GlobalSAN) that I use:

1. Always send "SessionType" when connecting.
2. Always send "AuthenticationType" when connecting.

Enabling those two options allowed everything to work again. Note that I do not use any authentication for iSCSI.

No idea if that would help you, but figured I'd share because I had the problem occur for me at the same time you did.

hyvokar
Starting out
Posts: 26
Joined: Tue Aug 20, 2013 1:28 pm

Re: Unable to connect iSCSI LUNs after upgrade to 4.4.1

Post by hyvokar » Mon Oct 21, 2019 2:56 pm

Support looked up in to this. For some reason LUNSectorSize is 0 after update.

So long story short, all data lost.
TS-853A 4GB 5x Seagate IronWolf 6TB + 2x SSD 860 QVO 1TB
TS-1673U-RP 24GB 12x Seagate IronWolf Pro 12TB + 2x SSD 860 EVO M.2 2TB

User avatar
storageman
Ask me anything
Posts: 5096
Joined: Thu Sep 22, 2011 10:57 pm

Re: Unable to connect iSCSI LUNs after upgrade to 4.4.1

Post by storageman » Mon Oct 21, 2019 4:36 pm

Never ever upgrade the firmware with LUNs connected to host. Why Qnap don't warn people god knows.

hyvokar
Starting out
Posts: 26
Joined: Tue Aug 20, 2013 1:28 pm

Re: Unable to connect iSCSI LUNs after upgrade to 4.4.1

Post by hyvokar » Thu Oct 24, 2019 2:29 pm

storageman wrote:
Mon Oct 21, 2019 4:36 pm
Never ever upgrade the firmware with LUNs connected to host. Why Qnap don't warn people god knows.
Thanks! Have to keep this in mind.
TS-853A 4GB 5x Seagate IronWolf 6TB + 2x SSD 860 QVO 1TB
TS-1673U-RP 24GB 12x Seagate IronWolf Pro 12TB + 2x SSD 860 EVO M.2 2TB

Live Wire
Starting out
Posts: 20
Joined: Wed Apr 29, 2015 9:13 am

Re: Unable to connect iSCSI LUNs after upgrade to 4.4.1

Post by Live Wire » Sun Oct 27, 2019 8:51 am

I wish I had checked here first before I updated to 4.4.1, but I've done countless updates on my 453 Pro, so I didnt think this would go any different.

I was on July's 4.3.6.0895 and updated to 4.4.1.something. All ESX hosts shut down so no LUNs were connected. Confirmed in QNAP before the update that there were no connections. Successful update, but had same issue others have mentioned. ESX connected just fine to the LUNs, QNAP saw the servers connected, but no Datastores would mount. I had one iSCSI LUN that I use on my Windows 10 client and that was mounting just fine, so take that for whatever it's worth.

I'm coming here after the fact so I didnt see some of the other troubleshooting efforts, but what I did was download 4.3.6.0895 firmware and rolled back to what I had before. I know this isn't exactly the best practice, and QNAP console will bark at you about it, but all I use my QNAP for are iSCSI LUNs for my home lab so I figured they'd be (should be) safe enough considering I wasn't going back too far on firmware versions.

Happy to report that everything worked. Firmware back to 4.3.6 and fired up all my ESX hosts and back in business. Your mileage may vary, so good luck if you attempt this.

Edit: forgot to mention: I don't use LUN masking on the ESX LUNs. I limit access to the LUNs via the initiators tab per target.

LW
Model: TS-453 Pro (2GB RAM)
Firmware: 4.3.6
Spindles: 3x 3TB WD30EFRX (RAID5)
SSD: 1x 256GB Crucial M4
Network: 4Gb/s LACP

Post Reply

Return to “iSCSI – Target & Virtual Disk”