none
Exchange server 2007 recover database error log file sector size mismatch RRS feed

  • General discussion

  • Hi all-

    I'm looking for some help, I've been struggling for a week now after a fatal boot crash of my exchange server. I'm trying to move the database onto a new server that has exchange running within the same "organization." I've finally got exchange up and running but I'm having trouble restoring the databases. 

    I was able to recover the files from the crashed server off the drive and still have the physical drive in tact. Initially the esetuil /mh was showing a "clean" shutdown state-but is now showing dirty. :( 

    I've worked through many errors while attempting to do this but I've finally got one stumping me beyond my level of understanding. While trying to recover the database, I'm getting the following error:

    -----------------------------------------------------

    [PS] D:\Program Files\Microsoft\Exchange Server\Mailbox\Mail Users>eseutil /r e02

    Extensible Storage Engine Utilities for Microsoft(R) Exchange Server
    Version 08.01
    Copyright (C) Microsoft Corporation. All Rights Reserved.

    Initiating RECOVERY mode...
        Logfile base name: e02
                Log files: <current directory>
             System files: <current directory>

    Performing soft recovery...

    Operation terminated with error -546 (JET_errLogSectorSizeMismatch, the log file
     sector size does not match the current volume's sector size) after 0.296 second
    s.

    -----------------------------------

    I read some other forums online and also ran these commands hoping to find the problem...but I did not. 

    Drive the logs and databases are on:

    D:\>fsutil fsinfo ntfsinfo d:
    NTFS Volume Serial Number :       0x34c2a031c29ff4f8
    Version :                         3.1
    Number Sectors :                  0x0000000074661fff
    Total Clusters :                  0x000000000e8cc3ff
    Free Clusters  :                  0x0000000008afae31
    Total Reserved :                  0x0000000000000a40
    Bytes Per Sector  :               512
    Bytes Per Cluster :               4096
    Bytes Per FileRecord Segment    : 1024
    Clusters Per FileRecord Segment : 0
    Mft Valid Data Length :           0x00000000120a0000
    Mft Start Lcn  :                  0x00000000000c0000
    Mft2 Start Lcn :                  0x00000000074661ff
    Mft Zone Start :                  0x0000000001747fe0
    Mft Zone End   :                  0x000000000174f120
    RM Identifier:        581B2DE0-5259-19E3-A8AC-9AD0B7CA222B

    Drives that exchange is currently installed on:

    C:\>fsutil fsinfo ntfsinfo c:
    NTFS Volume Serial Number :       0xc6148e92148e84e1
    Version :                         3.1
    Number Sectors :                  0x00000000e8d48fff
    Total Clusters :                  0x000000001d1a91ff
    Free Clusters  :                  0x000000001bf4502a
    Total Reserved :                  0x0000000000000040
    Bytes Per Sector  :               512
    Bytes Per Cluster :               4096
    Bytes Per FileRecord Segment    : 1024
    Clusters Per FileRecord Segment : 0
    Mft Valid Data Length :           0x0000000008b70000
    Mft Start Lcn  :                  0x00000000000c0000
    Mft2 Start Lcn :                  0x000000000e8d48ff
    Mft Zone Start :                  0x00000000000c8b60
    Mft Zone End   :                  0x00000000000cc820
    RM Identifier:        8B812CCD-A3A8-11E5-B279-BEB28F0E05E1

    Can anyone help me? Thank you in advance,

    Thursday, December 17, 2015 12:26 AM

All replies

  • Check this url

    http://blogs.technet.com/b/exchange/archive/2013/04/24/exchange-2010-database-availability-groups-and-disk-sector-sizes.aspx


    Please mark as an answer if this answers your question .

    PREM RANA

    MCSE Exchange 2013, MCSA 2012 Server MCTS Exchange 2007,

    2010, MCITP Exchange 2007, 2010 MCSE 2003 Server,

    MCSA Exchange 2003 ITIL V3 Foundation

    https://ranaprem.wordpress.com/

    This posting is provided AS IS with no warranties and confers no rights.

    Sunday, December 20, 2015 6:57 AM