Hello,
I recently created a iSCSI LUN on my QNAP TES-1885U and connected it to my Win2012 server (ServerA) as X: drive. The QNAP and ServerA have a Mellanox 40Gbps card and they are connected directly. Now, I also have a shared folder on the QNAP, so I mapped to the QNAP share on ServerA (net use Z: \\qnap\share1). Then I created a simple robocopy command to copy file contents from the share (Z:) to my iSCSI LUN (X:). This process goes on fine for some time, and then I start getting errors -
" EventID: 0x10300c8
Description: [iSCSI] Target iqn.2004-04.com.qnap:es-x85u:iscsi.nas01santest.1191b5.0 sid 4000013700010200 cid 1 iSCSI command timed out (op code 0) "
During this time, however ServerA goes in an almost non-operational state. It's almost like the CPU is at 100%, thus making it impossible to login or do anything. I end up doing a hard shutdown and hope that it comes back up without any data loss (as it is a production server). This has now happened twice as I've tested the process of coping the files twice.
Once I can get back into ServerA, I see the following in the EventLogs - "Target did not respond in time for a SCSI request. The CDB is given in the dump data." And there are no other events at all during the time the machine is in a crash like state till I restart it.
Can someone please assist me with this and let me know why this is happening and how to fix this issue? Any comments/suggestions are appreciated.
Thank you,
Sau
iSCSI timeout and Win2012 high CPU uitlization
-
- First post
- Posts: 1
- Joined: Fri Sep 29, 2017 3:19 am
- Trexx
- Ask me anything
- Posts: 5393
- Joined: Sat Oct 01, 2011 7:50 am
- Location: Minnesota
Re: iSCSI timeout and Win2012 high CPU uitlization
I would first open a helpdesk ticket with QNAP as this is a community support forum.
Are you running QTS or QES firmware on your NAS? Are you on the most current release?
Can you determine roughly where the copy job is crashing? Is it the same place each time? Could it be a corrupted/inaccessible file that isn't being handled cleanly by robocopy?
Are you running QTS or QES firmware on your NAS? Are you on the most current release?
Can you determine roughly where the copy job is crashing? Is it the same place each time? Could it be a corrupted/inaccessible file that isn't being handled cleanly by robocopy?
Paul
Model: TS-877-1600 FW: 4.5.3.x
QTS (SSD): [RAID-1] 2 x 1TB WD Blue m.2's
Data (HDD): [RAID-5] 6 x 3TB HGST DeskStar
VMs (SSD): [RAID-1] 2 x1TB SK Hynix Gold
Ext. (HDD): TR-004 [Raid-5] 4 x 4TB HGST Ultastor
RAM: Kingston HyperX Fury 64GB DDR4-2666
UPS: CP AVR1350
Model:TVS-673 32GB & TS-228a Offline[/color]
-----------------------------------------------------------------------------------------------------------------------------------------
2018 Plex NAS Compatibility Guide | QNAP Plex FAQ | Moogle's QNAP Faq
Model: TS-877-1600 FW: 4.5.3.x
QTS (SSD): [RAID-1] 2 x 1TB WD Blue m.2's
Data (HDD): [RAID-5] 6 x 3TB HGST DeskStar
VMs (SSD): [RAID-1] 2 x1TB SK Hynix Gold
Ext. (HDD): TR-004 [Raid-5] 4 x 4TB HGST Ultastor
RAM: Kingston HyperX Fury 64GB DDR4-2666
UPS: CP AVR1350
Model:TVS-673 32GB & TS-228a Offline[/color]
-----------------------------------------------------------------------------------------------------------------------------------------
2018 Plex NAS Compatibility Guide | QNAP Plex FAQ | Moogle's QNAP Faq
- storageman
- Ask me anything
- Posts: 5507
- Joined: Thu Sep 22, 2011 10:57 pm
Re: iSCSI timeout and Win2012 high CPU uitlization
Yes QES or QTS?
I suspect a network packet/issue.
Is the share and ISCSI connection running on the same NIC(s)?
Can you run the same test on a 1GbE connection?
What happens when you copy from windows server to LUN rather NAS share.
I suspect a network packet/issue.
Is the share and ISCSI connection running on the same NIC(s)?
Can you run the same test on a 1GbE connection?
What happens when you copy from windows server to LUN rather NAS share.