locked
exchange 2010 issues with IBM XIV storage RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi, I am working on exchange 2010 enterprise edition which is installed on windows 2008 R2 64bit, we have configured  exchange database on IBM XIV storage. Once one module on xiv got failled during that time my exchange server got rebooted, when i checked the log on exchange server found that its not able to switch over the storage path, even when i have configured multipathing on exchange server. My rest of the windows 2008 server which are on same storage were able to work perfectly fine. Only problem occured with exchange server. I have gone trhough the memory dump error log, following error displayed when i run the memory dump reader

    Result of mini dump

    052911-50076-01.dmp 29/05/2011 05:09:31 Bug checking sting-DRIVER_IRQL_NOT_LESS_OR_EQUAL bug check code:0x000000d1 Parameter1:00000000`00000014 00000000`00000002 00000000`00000000 fffff880`012f41c2 

    Caused My Driver:msdsm.sys Caused By address:msdsm.sys+171c2

    Result of Crashdump 

    * Symbols can not be loaded because symbol path is not initialized. *
    *                                                                   *
    * The Symbol Path can be set by:                                    *
    *   using the _NT_SYMBOL_PATH environment variable.                 *
    *   using the -y <symbol_path> argument when starting the debugger. *
    *   using .sympath and .sympath+                                    *
    *********************************************************************
    Probably caused by : msdsm.sys ( msdsm+171c2 )

    Followup: MachineOwner

     

    Please help me to troubleshoot this issue, just wanted to know whether its exchange 2010 problem  or IBM XIV storage issue

    Monday, June 6, 2011 9:30 AM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote
    Make sure you are using the right and supported MPIO set, whether the XIV or the Microsoft ones. Is this virtualized? Are you using ALUA?
     
     
    "manish rai" wrote in message news:d29809d4-c2ce-47f6-8100-d8af5acf797e...

    Hi, I am working on exchange 2010 enterprise edition which is installed on windows 2008 R2 64bit, we have configured  exchange database on IBM XIV storage. Once one module on xiv got failled during that time my exchange server got rebooted, when i checked the log on exchange server found that its not able to switch over the storage path, even when i have configured multipathing on exchange server. My rest of the windows 2008 server which are on same storage were able to work perfectly fine. Only problem occured with exchange server. I have gone trhough the memory dump error log, following error displayed when i run the memory dump reader

    Result of mini dump

    052911-50076-01.dmp 29/05/2011 05:09:31 Bug checking sting-DRIVER_IRQL_NOT_LESS_OR_EQUAL bug check code:0x000000d1 Parameter1:00000000`00000014 00000000`00000002 00000000`00000000 fffff880`012f41c2

    Caused My Driver:msdsm.sys Caused By address:msdsm.sys+171c2

    Result of Crashdump 

    * Symbols can not be loaded because symbol path is not initialized. *
    *                                                                   *
    * The Symbol Path can be set by:                                    *
    *   using the _NT_SYMBOL_PATH environment variable.                 *
    *   using the -y <symbol_path> argument when starting the debugger. *
    *   using .sympath and ..sympath+                                    *
    *********************************************************************
    Probably caused by : msdsm.sys ( msdsm+171c2 )

    Followup: MachineOwner

     

    Please help me to troubleshoot this issue, just wanted to know whether its exchange 2010 problem  or IBM XIV storage issue

    Mark Arnold, Exchange MVP.
    • Proposed as answer by Terence Yu Tuesday, June 7, 2011 2:24 AM
    • Marked as answer by Terence Yu Thursday, June 16, 2011 9:47 AM
    Monday, June 6, 2011 4:58 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Hi
       According to your saying, it seems to be system or storage error.
       msdsm.sys is part of     Windows 2008 MPIO Feature not exchange.
    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.
    • Marked as answer by Terence Yu Thursday, June 16, 2011 9:48 AM
    Tuesday, June 7, 2011 2:27 AM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote
    I would start by making sure that the firmware and models are the same for storage on server that failed and server that is functioning. Contact IBM to troubleshoot the issue further.
    Monday, June 6, 2011 2:55 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    I am sure that there is nothing wrong with Exchange, its IBM Storage which has the issue and first should get in touch with IBM
    One more thing is, how IBM storage configured for exchange server. 
    Gulab | MCITP: Exchange 2010-2007 | Skype: Gulab.Mallah | Blog: www.ExchangeRanger.blogspot.com
    Monday, June 6, 2011 3:20 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Make sure you are using the right and supported MPIO set, whether the XIV or the Microsoft ones. Is this virtualized? Are you using ALUA?
     
     
    "manish rai" wrote in message news:d29809d4-c2ce-47f6-8100-d8af5acf797e...

    Hi, I am working on exchange 2010 enterprise edition which is installed on windows 2008 R2 64bit, we have configured  exchange database on IBM XIV storage. Once one module on xiv got failled during that time my exchange server got rebooted, when i checked the log on exchange server found that its not able to switch over the storage path, even when i have configured multipathing on exchange server. My rest of the windows 2008 server which are on same storage were able to work perfectly fine. Only problem occured with exchange server. I have gone trhough the memory dump error log, following error displayed when i run the memory dump reader

    Result of mini dump

    052911-50076-01.dmp 29/05/2011 05:09:31 Bug checking sting-DRIVER_IRQL_NOT_LESS_OR_EQUAL bug check code:0x000000d1 Parameter1:00000000`00000014 00000000`00000002 00000000`00000000 fffff880`012f41c2

    Caused My Driver:msdsm.sys Caused By address:msdsm.sys+171c2

    Result of Crashdump 

    * Symbols can not be loaded because symbol path is not initialized. *
    *                                                                   *
    * The Symbol Path can be set by:                                    *
    *   using the _NT_SYMBOL_PATH environment variable.                 *
    *   using the -y <symbol_path> argument when starting the debugger. *
    *   using .sympath and ..sympath+                                    *
    *********************************************************************
    Probably caused by : msdsm.sys ( msdsm+171c2 )

    Followup: MachineOwner

     

    Please help me to troubleshoot this issue, just wanted to know whether its exchange 2010 problem  or IBM XIV storage issue

    Mark Arnold, Exchange MVP.
    • Proposed as answer by Terence Yu Tuesday, June 7, 2011 2:24 AM
    • Marked as answer by Terence Yu Thursday, June 16, 2011 9:47 AM
    Monday, June 6, 2011 4:58 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Hi
       According to your saying, it seems to be system or storage error.
       msdsm.sys is part of     Windows 2008 MPIO Feature not exchange.
    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.
    • Marked as answer by Terence Yu Thursday, June 16, 2011 9:48 AM
    Tuesday, June 7, 2011 2:27 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    But i have few other server windows 2008 r2 which are connected with same storage, it doent effect to other server but only my exchange server gets rebooted in such case when any XIV module gets failled, it happended two time in past one year.

    see the event id generated at that moment when one xiv module got failled

    event ID 17, source MPIO

    Message details: \Device\MPIODisk0 is currently in a degraded state. One or more paths have failed, though the process is now complete.

    Event ID 16, source 16,

    Message Details: A fail-over on \Device\MPIODisk1 occurred.

    after this following event gets generated

    event id 0, source FBDisk

    The description for Event ID 0 from source FBDisk cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

    If the event originated on another computer, the display information had to be saved with the event.

    The following information was included with the event:

    the message resource is present but the message is not found in the string/message table

    event ID 101, source BugCheck

    The computer has rebooted from a bugcheck. The bugcheck was: 0x000000d1 (0x0000000000000014, 0x0000000000000002, 0x0000000000000000, 0xfffff880012f41c2). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 052911-50076-01.

    i have found following article on microsoft that need to install windows r2 service pack1 and in addition to that there are two matches need to be installed,

    KB2460971  and KB2511962 are recommended to install on exchnage server. Should i go ahead with that. Will it be help me to resolve the problem.

     

     

     

     

    Thanks & Regards, Manish Rai
    Tuesday, June 7, 2011 5:16 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    thank you for rreply

    But i have few other server windows 2008 r2 which are connected with same storage, it doent effect to other server but only my exchange server gets rebooted in such case when any XIV module gets failled, it happended two time in past one year.

    see the event id generated at that moment when one xiv module got failled

    event ID 17, source MPIO

    Message details: \Device\MPIODisk0 is currently in a degraded state. One or more paths have failed, though the process is now complete.

    Event ID 16, source 16,

    Message Details: A fail-over on \Device\MPIODisk1 occurred.

    after this following event gets generated

    event id 0, source FBDisk

    The description for Event ID 0 from source FBDisk cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

    If the event originated on another computer, the display information had to be saved with the event.

    The following information was included with the event:

    the message resource is present but the message is not found in the string/message table

    event ID 101, source BugCheck

    The computer has rebooted from a bugcheck. The bugcheck was: 0x000000d1 (0x0000000000000014, 0x0000000000000002, 0x0000000000000000, 0xfffff880012f41c2). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 052911-50076-01.

    i have found following article on microsoft that need to install windows r2 service pack1 and in addition to that there are two matches need to be installed,

    KB2460971  and KB2511962 are recommended to install on exchnage server. Should i go ahead with that. Will it be help me to resolve the problem

    Thanks & Regards, Manish Rai
    Tuesday, June 7, 2011 5:16 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi
       I just search these two KB. There are all windows KB not exchange KB.
       I am not good at managing storage .
       You can post your thread to     http://social.technet.microsoft.com/Forums/fi-FI/winserverfiles/threads

    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.
    Tuesday, June 7, 2011 6:33 AM