I know that there are some network guys on here so I will toss out an issue I am having....
The Gear
-Dell PowerEdge 2950 Server running Win2K8 64bit (fresh install & patched)
-Microsoft iSCSI Initiator
-Cisco Managed switches with a 4 fiber channel VLan between the switches
-Promise M610 VTrak array with 16 X 1.5 TB HDD (setup up as a 15 drive Raid 5 with a hot swap spare)
When I write data to this volume I get errors in the windows system log about corrupt file system that I am not able to repair with chkdsk e: /f.
If I pull the Promise box off the network and just connect it directly to the NIC of a test box running Win2K8 I can read and write to the volume just fine with no corruption errors....After testing it like this for 2 days...back onto my network and bang the corruption begins again. I have replaced all the patch cables with new Cat 6 cables and I have a Fluke Network Analyser which I used to test the cables as good. I was starting to wonder if the switch is the problem but there are no errors in the log files.....I may just temporary replace it with an old D Link 1 GB unmanaged switch I have for testing purposes.
Any ideas what to troubleshoot next or what might be causing the file corruption issues?
I forgot to add that the Promise box was set to GPT and the allocation size set to 64k when I formatted the volume.
The Gear
-Dell PowerEdge 2950 Server running Win2K8 64bit (fresh install & patched)
-Microsoft iSCSI Initiator
-Cisco Managed switches with a 4 fiber channel VLan between the switches
-Promise M610 VTrak array with 16 X 1.5 TB HDD (setup up as a 15 drive Raid 5 with a hot swap spare)
When I write data to this volume I get errors in the windows system log about corrupt file system that I am not able to repair with chkdsk e: /f.
If I pull the Promise box off the network and just connect it directly to the NIC of a test box running Win2K8 I can read and write to the volume just fine with no corruption errors....After testing it like this for 2 days...back onto my network and bang the corruption begins again. I have replaced all the patch cables with new Cat 6 cables and I have a Fluke Network Analyser which I used to test the cables as good. I was starting to wonder if the switch is the problem but there are no errors in the log files.....I may just temporary replace it with an old D Link 1 GB unmanaged switch I have for testing purposes.
Any ideas what to troubleshoot next or what might be causing the file corruption issues?
I forgot to add that the Promise box was set to GPT and the allocation size set to 64k when I formatted the volume.
Comment