boot from san windows 2003 installation hung at writing start up files to san partition

I am trying to install Windows 2003 in a boot from SAN configuration. I can get the install to start and get all the way to seeing the assigned LUN partition, however when windows attempts to write the setup files to the attached storage it fails with the error "However, this disk does not contain a Windows-compatible partition".
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

looks like you do not have write access to the LUN. If you are using a switch, check zoning permissions.  Also check your HBA to make sure it is not restricting write access.
RetalixUSAAuthor Commented:
figured it out. The issue was that there were two WWPN's able to access the lun, however in the BIOS their was only one for the HBA. Once I removed the (B) side of the fabric and changed the zone to only one WWPN for the Clariion it was able to write to the disk. The problem I am having now is that the install is stuck in an infinite loop. It copies over the files, then reboots...and begins the whole process over again. Any help is appreciated.

All in all...boot from san is not impressive.
You can't and shouldn't necessarily blame the SAN for the reboots.  This problem could be a lot of things, but I would first concentrate on figuring out what works and what doesnt.

can the pc boot the same image from a local disk drive?  Is this a windows-specific problem (try booting a LINUX O/S just to see).   Since you are doing a SAN install, don't forget about the F6+driver thing.
What HBA are you using? Windows boot from SAN can be a pain as you need the SCSIport drivers to run setup and then have to upgrade the drivers to Storport once it's installed. Several instances of booting loop happen but you need to tell us which HBA you're using.

A workaround is to install on local disk and put correct storport drivers in, then image this to the SAN.
RetalixUSAAuthor Commented:
sorry, I have been busy building out this environment. the issue was that even after removing one HBA to enable writing to the SAN space it was not the HBA that was set to boot from. So it would copy the files over, but would not be able to boot as the boot HBA was not the same. Once I fixed that issue it is good to go. All in all though still prefer booting from a local disk. A lot points of failure...

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.