We are seeing an issue that a volume SAN volume we access from W2K3 using an iscsi connector becomes corrupt after an unexpected power down of the windows server. The volume can normally be recovered by mounting it and performing a chkdsk f: /f which returns thousands of:
"replacing invalid security id with default security id for file XXX"
once completed the volume seems stable although on the last occasion we had to delete and recreate the volume and restore the files from backup.
Has anyone had a similar experience ?
My gut feeling is the iSCSI San is fine (as we have Oracle partitions on their too which are ok) but it is being caused by the way in which Windows connects and read/writes files.

Any suggestions / comments welcome