Hi. I currently have a boot problem with Server 2008R2 when booting from an iSCSI LUN. I performed the install and everything was up and running and working just fine. Preformed a lot of configuration work on the server for Hyper-V/System Center. I performed a clean shutdown of the server. Since I am using Cisco UCS I disassociated the server service profile with the server (once shut down). This was ultimately to remove the local storage as i did not need it anymore (nothing was on the local storage anyways it was all on the SAN). After associating the server profile again to the same physical blade in the UCS Chassis, the server now fails to boot. The loading screen displays as if it is loading, but right before the transition to the user log in screen it actually blue screens saying that windows is shutting down to prevent damage to the disk. (there is no error code, it is simply "informative") suggests running chkdsk. Which i have from the system recovery and returns with 0 errors on the disk. repair attempts I do not have the option to boot in safe mode so this isn't possible (unless I can some how from the system recovery) I have booted from the installation media and reinstall the Cisco VIC drivers just like for the initial installation procedure and can see the OS LUN just fine. I have tried the following on the LUN bootrec /fixmbr, bootrec /fixboot, drive\boot\bootsect.exe /NT60 all - I am currently at a loss right now on how to fix this. I am also relatively new to the IT world so i apologize for any ignorance I may have the moment. What it appears like to me - Everything is there for the OS to boot but it seems as though when I disassociated the UCS service profile, the OS lost the Cisco VIC driver (I no idea how this might have happened). Is there any way to check this and/or install it again from the system recovery command prompt? That is about all i can get to at this point. Thanks for you help its much appreciated!

A few updates. I was able to browse to the drivers folder and have indeed located the correct UCS VIC driver (enic6264.sys) So it is in fact there. I was also able to run the Startup Repair from the system recovery. After everything was completed successfully there was one output. Root cause found: Unspecified changes to system configuration might have caused the problem. Repair action: System files integrity check and repair Result: Failed. Error Code = 0x490 Time Taken = 497160ms But the startup repair states startup repair could not find a problem -The thing is there wasn't a hardware change made. The HW is exactly the same as when it worked. Is there a way around this HW check to force Windows to boot even if the detects a HW change? I have gone as far as removing the service profile, decommissioning the server, re-acknowledging it, and reapplying the profiles. Anyone with ideas? Thanks again for your time!

Hi, Based on the current situation, you may also try to recover the full server. For the detailed steps, please refer to the following Microsoft TechNet article: Recover the Operating System or Full Server http://technet.microsoft.com/en-us/library/cc755163.aspx Regards,Arthur Li TechNet Community Support

Hi, Based on the current situation, you may also try to recover the full server. For the detailed steps, please refer to the following Microsoft TechNet article: Recover the Operating System or Full Server http://technet.microsoft.com/en-us/library/cc755163.aspx Regards,Arthur Li TechNet Community Support