System administrators often experience problems when configuring a SAN into a server cluster. If there is a problem configuring a SAN into a server cluster, here are five error events that you might see in the system logs:
- Warning event ID 11 with event source %HBADriverName%, "The driver detected a controller error on Device\ScsiPortN."
- Warning event ID 50 with event source Disk, "The system was attempting to transfer file data from buffers to \Device\HarddiskVolume N. The write operation failed, and only some of the data may have been written to the file."
- Warning event ID 51 with event source FTDISK, "An error was detected on device during a paging operation."
- Warning event ID 9 with event source %HBADriverName%, "Lost Delayed Write Data: The device, \Device\ScsiPortN , did not respond within the timeout period."
- Warning event ID 26 with event source Application Popup, "Windows—Delayed Write Failed: Windows was unable to save all the data for the file \Device\Harddisk Volume N\MFT$. The data has been lost. This error may be caused by a failure of your computer hardware or network connection. Please try to save this file elsewhere."
If you get one of these event errors, you can try reconfiguring the SAN or turn to your hardware vendor for assistance. The hardware vendor of the SAN is the
About the author: Rahul Shah currently works at a software firm in India, where he is a systems administrator maintaining Windows servers. He has also worked for various software firms in testing and analytics, and also has experiences deploying client/server applications in different Windows configurations.
More information on this topic:
- Tip: Best practices for backing up clusters
- Topics: SANs
- RSS: Sign up for our RSS feed to receive expert advice every day.
This was first published in October 2006