Entrar
 
HomeBibliotecaWikiAprenderGaleriaDownloadsSuporte ComunidadeFóruns
Recursos para Profissionais de TI >
> 
> 
Hyper-V Server 2008 R2 SP1 won't boot after exposing cluster shared volumes

问题 Hyper-V Server 2008 R2 SP1 won't boot after exposing cluster shared volumes

  • segunda-feira, 26 de março de 2012 20:35
     
     
    Entrar para Votar
    0

    Hi everyone,

    Quick question, we have a 3-node Hyper-V cluster with 9 CSVs (so far) and 1 witness disk configured - presented over QLogic FC CIOv adapters. Everything is working fine, clustering works well etc. 

    We have built other nodes, to the exact same specifications/patch level (they are IBM 7870 HS22 blades, latest firmware, running Windows Hyper-V Server 2008 R2 SP1). Each blade has a dedicated boot from SAN disk (LUN 0) as well. The new nodes boot/work fine, but when we turn them off, present the shared LUNs to the new node, then turn the server back on it won't boot. It loads the initial Windows boot loader with the slider, then just hangs at a black screen.

    The only way to get it back is to remove the shared volumes. 

    I have enabled boot logging but nothing seems to appear. The host type in our storage platform is set to "Windows Server 2003/Server 2008 Clustered".

    Any ideas would be greatly appreciated. There doesn't appear to be any hotfix which addresses this.

    Many thanks,

     

Todas as Respostas

  • segunda-feira, 26 de março de 2012 22:13
     
     
    Entrar para Votar
    0

    Hmm.. also I haven't applied any additional hotfixes other than from Windows Updates. Eg listed here:

    http://technet.microsoft.com/en-us/library/ff394763%28WS.10%29.aspx
    http://social.technet.microsoft.com/wiki/contents/articles/1349.hyper-v-update-list-for-windows-server-2008-r2.aspx
    http://blogs.technet.com/b/yongrhee/archive/2011/05/22/list-of-hyper-v-windows-server-2008-r2-sp1-hotfixes.aspx
    http://support.microsoft.com/kb/2545685
    http://ramazancan.wordpress.com/2011/08/03/post-sp1-hotfixes-for-windows-2008-r2-sp1-with-failover-clustering-and-hyper-v/

    We don't seem to be experiencing any of the issues listed in these articles.


     
  • terça-feira, 27 de março de 2012 02:37
    Moderador
     
     
    Entrar para Votar
    0
    Hi,
     
    According to the description, it seems that you have an existing 3-node Hyper-V cluster running properly. If so, please help me to collect the following information:
     
    1. Did you get the same issue when you configured the existing cluster nodes?
    2. I am not a storage professional. However, I would like to ask whether there is an option like “Windows Server 2008 only” for host type in your storage platform. Please try to switch to “Windows Server 2008 only” if  there is.
    3. Please try to add a new LUN(not the existing shared LUNs) to the new cluster nodes to see whether you get the same issue.
     

    Vincent Hu

    TechNet Community Support

     
  • terça-feira, 27 de março de 2012 03:06
     
     
    Entrar para Votar
    0

    Hi Vincent,

    Thanks so much for your reply. I didn't have any issues configuring the existing cluster nodes.

    The host type options for my storage are:

    • Windows Server 2003/Server 2008 Clustered
    • Windows Server 2003/Server 2008 Clustered (supports DMP)
    • Windows Server 2003/Server 2008 Non-Clustered
    • Windows Server 2003/Server 2008 Non-Clustered (supports DMP)

    Setting to anything other than "Windows Server 2003/Server 2008 Clustered" causes issues with our shared volumes.

    I've tried adding another LUN to the server and it boots fine. Have also applied KB2517329 since each host has more than 48GB memory and the same processor as the KB article references, and the issue still persists. I'm going to apply some other hyper-v/clustersvc related hot-fixes, however none of the other ones seem related to this particular problem.

    Many thanks,
    Gareth

     
  • terça-feira, 27 de março de 2012 03:12
     
     
    Entrar para Votar
    0

    Also, when we created the cluster originally with 3 nodes, there were only 2 or 3 cluster shared volumes. Then we added the additional ones.

    9 CSVs aren't that much though - so don't see how it would cause any issues.

    It is not an option to expose them one by one to the new node to try to identify the issue, without breaking stuff in production.

     
  • segunda-feira, 2 de abril de 2012 11:22
     
     
    Entrar para Votar
    0

    Hi, Is the SAN vendor engaged and if so, have they evaluated yet?

    I suggest you to engage the Storage vendor to check the following things. 

    1. Upgrade the driver/firmware of the HBA disk controller to which the SAN disks are attached to the latest version. 2. Upgrade the multi-path software to the latest version if installed.

    3. Check the storage settings and ensure they follow the best practice and there is hardware fault when the issue is occurring.

     Additional information: Support for booting from a Storage Area Network (SAN) http://support.microsoft.com/kb/305547

    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.


     
  • segunda-feira, 9 de abril de 2012 12:36
     
     
    Entrar para Votar
    0

    Hi Aaron,

    It's weird, there doesn't seem to be any hardware fault. I've checked the storage configuration and it seems fine, drive/firmware is all the latest available. Multi-path has been updated to latest appropriate version as well.

    It's working fine on 3 servers (the existing host clusters), but new hosts are not booting.

     
  • quarta-feira, 25 de abril de 2012 09:43
     
     
    Entrar para Votar
    0

    Hi ,

    If you enabled boot logging, which is the ntbtlog.txt record the last loaded driver?

    Update the CSVFilter.sys by the following hotfix.

    http://support.microsoft.com/kb/2639032

    By the way, have you tried safe mode with networking?

    Thanks.

    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

     
  • terça-feira, 22 de maio de 2012 12:09
     
     
    Entrar para Votar
    0

    HI Gareth,

    Is there any update?

    Thanks.

    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.