We have a number of SAN boot Windows 2003 R2 x64 servers which all exhibit the same behavior regarding crashdump creation. Testing has been perfromed by using the CrashOnCtrlScroll registry key, so far no files have been created (not even minidumps) regardless of the recovery settings.
We get Event ID 49 from source ftdisk on every restart, which then goes on to state: "Configuring the Page file for crash dump failed..."
Sufficient free space is available is available on the system drive. We have even tried reducing the amount of system memory to make absolutely sure this is not a factor.
I have seen on another forum that a SAN aware storport.sys file is available from Microsoft but have been unable to locate it on the Microsoft site.
HP EVA SAN
HP BL 465 g7 blades
Windows 2003 R2 Enterprise Edition x64
Configured to boot from san
Crashdump debugging is not officially supported here, please contact Microsoft Customer Support Service (CSS) if you need any help on this. To obtain the phone numbers for specific technology request, please refer to the website listed below: http://support.microsoft.com/default.aspx?scid=fh;EN-US;PHONENUMBERS
If you are outside the US, please refer to http://support.microsoft.com for regional support phone numbers.