NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
ndlbox
Sep 16, 2011Aspirant
iSCSI w. Server 2008 R2 locks up on large writes
I have a ReadyNAS Pro Business Edition [X-RAID2] running RAIDiator 4.2.19. The entire thing is running one iSCSI LUN connected to one physical host. When I try to copy a large amount of data to it (...
Grievous
Sep 20, 2011Aspirant
Going through the logs there are two things that we noted.
1. Your volume is completely full. That shouldn't cause a problem, but it's worth noting. How large is this iSCSI LUN anyway?
2. There are a lot of network packet errors, as well as the ReadyNAS complaining about receiving packets out of order. What switch are you using and has anything been changed from default on that switch if it's managed?
You can open Frontview and browse to the network settings page for ethernet 1(eth0), and hit the show errors button and you'll see the error counts that we saw in the logs. If you were to try and reproduce this again after resetting that error count, can you verify that no other access to the NAS was occurring(no one using CIFS or anything) and see if the error count is still increasing? If so, then it would indicate a network problem(likely a client side or switch configuration issue since it's all receive errors on the NAS side and only happens when you're writing)
1. Your volume is completely full. That shouldn't cause a problem, but it's worth noting. How large is this iSCSI LUN anyway?
2. There are a lot of network packet errors, as well as the ReadyNAS complaining about receiving packets out of order. What switch are you using and has anything been changed from default on that switch if it's managed?
You can open Frontview and browse to the network settings page for ethernet 1(eth0), and hit the show errors button and you'll see the error counts that we saw in the logs. If you were to try and reproduce this again after resetting that error count, can you verify that no other access to the NAS was occurring(no one using CIFS or anything) and see if the error count is still increasing? If so, then it would indicate a network problem(likely a client side or switch configuration issue since it's all receive errors on the NAS side and only happens when you're writing)
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!