01-12-2012 06:30 AM - edited 03-01-2019 10:13 AM
I have install windows 2008 R2 on a B200 to boot from SAN. I have an M81KR (Palo) mezz card. I have tried using the drivers from cco for windows its UCS 2.0.1e. I get the driver installed during the windows install and I can see my storage/LUN. However, after installation OS i have reboot the server but i am not the getting the desktop view of the image i have installed
The UCS firmware is 2.0(1m). My backend storage is an Hitachi USP.
Anyone have a clue what I need to be done to fix this issue?
01-12-2012 11:12 AM
If you are seeing the correct SAN lun during the install process, but, it does not reboot off of that SAN lun, the most likely issue is the SAN LunID that is configured in the boot order does not match what has been masked to your vHBA WWPN on the array.
This is unfortunately very difficult to troubleshoot. Please verify the LunID that has been masked at the array. If it doesn't match exactly, it will fail.
Also, at least for troubleshooting purposes
1) only configure one fabric path during install
2) remove all local disks
Dave
01-13-2012 05:50 AM
Had this issue recently and the workaround was to use the 1.4 fnic driver during the install. You can update it once Windows is up.
01-13-2012 08:45 AM
Jeremy, were you instructed by TAC to do this or was this your own fix? Just curious so if the newer driver is not working, we can go to engineering and ensure this gets corrected.
Sent from Cisco Technical Support iPad App
01-13-2012 08:57 AM
This was my own fix
01-16-2012 08:38 PM
Hi jeremy
May i know what backend storage u have used and had this same issue?. In hitachi USP we are facing this issue for SAN boot but other storages like netapp and EMC with same san boot is working fine no issue with other storage..
01-17-2012 04:18 AM
I think it was an EMC VNX but I can't remember for sure as all of the installs start to run together.
I also had a weird issue once with installing Windows 2008 R2 on a VMAX boot LUN. The fix was to move the SAN boot above the CDROM in the boot policy.
01-17-2012 08:34 PM
hi jeremy
currently we are facing san boot issue with hitachi alone. EMC and Netapp its working good.
As per your suggestion i have tried with 1.4 driver version even then its not booting up facing the same issue.
Os version | windows 2008 R2 enterprise edition |
Language | Japanese |
storage | Hitachi USP |
Storage/LUN size | Checked with 100GB LUN |
Driver version | Checked with both 1.4 and 2.0.1e(latest driver version) |
Blade | UCS B200M2 |
Adapter | Palo[M81KR] |
Do you have any clue for this?
Any right UCS team alias to address this issue?
01-17-2012 10:57 PM
Hi Srinivasan,
You may try to enable "persistent binding" in vHBA configuration. As Dave mentioned earlier, since the windows OS can be installed but once reboot, the boot device can't be found. The possible reason is the LUN ID after reboot is difference with ID when installed.
BR,
John Meng
01-18-2012 03:48 AM
How many paths to the boot LUN are visible? I usually only present 1 path for Windows install and then after multipathing software is configured I present the other paths.
Is the Host LUN ID of the boot LUN correct in the boot policy?
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: