Server 2012 Express修复安装失败，生成错误5178
我的服务将不会启动。
为了产生这个问题，我基本上将我的旧硬盘(安装了2012 )克隆到一个新的硬盘驱动器( 750)上。
编辑:我正在添加的信息，我如何克隆我的硬盘驱动器根据SQLRockStar的要求。我用了希捷DiscWizard。当使用简单的“克隆HD”命令时，该程序在试图克隆HD时产生错误。因此，在SeaGate技术支持的帮助下，我“克隆”了它：
- 将新的硬盘(Momentus)放置在从槽中，将旧HD放置在主人中。
- 创建旧HD的备份映像并保存在旧HD上。
- 创建Seagate DiscWizard可引导CD
- 物理交换两个硬盘驱动器的位置，(旧现在在奴隶，新在主人)
- 引导与希捷DiscWizard可引导CD和恢复旧的高清备份映像到新的高清。
之后，我尝试在Momentus上启动2012，但它没有启动。因此，我尝试执行Server的修复安装，但失败了:参见下面的摘要：
Overall summary:
Final result: Failed: see details below
Exit code (Decimal): -2061893608
Start time: 2013-08-12 15:53:13
End time: 2013-08-12 16:13:13
Requested action: Repair
Setup completed with required actions for features.
Troubleshooting information for those features:
Next step for SQLEngine: Use the following information to resolve the error, and then try the setup process again.
Next step for Replication: Use the following information to resolve the error, and then try the setup process again.
Machine Properties:
Machine name: MATT-LAPTOP
Machine processor count: 8
OS version: Windows 7
OS service pack: Service Pack 1
OS region: United States
OS language: English (United States)
OS architecture: x64
Process architecture: 64 Bit
OS clustered: No
Product features discovered:
Product Instance Instance ID Feature Language Edition Version Clustered
SQL Server 2008 Management Tools - Basic 1033 Express Edition 10.0.1600.22 No
SQL Server 2012 SQLEXPRESS MSSQL11.SQLEXPRESS Database Engine Services 1033 Express Edition 11.0.2316.0 No
SQL Server 2012 SQLEXPRESS MSSQL11.SQLEXPRESS SQL Server Replication 1033 Express Edition 11.0.2316.0 No
SQL Server 2012 Management Tools - Basic 1033 Express Edition 11.0.2316.0 No
SQL Server 2012 LocalDB 1033 Express Edition 11.0.2318.0 No
Package properties:
Description: Microsoft SQL Server 2012
ProductName: SQL Server 2012
Type: RTM
Version: 11
SPLevel: 0
Installation location: c:\215ca8b216eb992f2f4a\x64\setup\
Installation edition: Express
User Input Settings:
ACTION: Repair
AGTDOMAINGROUP: <empty>
AGTSVCACCOUNT: NT AUTHORITY\NETWORK SERVICE
AGTSVCPASSWORD: <empty>
AGTSVCSTARTUPTYPE: Disabled
ASCONFIGDIR: Config
ASSVCACCOUNT: <empty>
ASSVCPASSWORD: <empty>
CLTSTARTUPTYPE: 0
CLTSVCACCOUNT: <empty>
CLTSVCPASSWORD: <empty>
CONFIGURATIONFILE:
CTLRSTARTUPTYPE: 0
CTLRSVCACCOUNT: <empty>
CTLRSVCPASSWORD: <empty>
ENU: true
FAILOVERCLUSTERGROUP: <empty>
FAILOVERCLUSTERNETWORKNAME: <empty>
FTSVCACCOUNT: <empty>
FTSVCPASSWORD: <empty>
HELP: false
INDICATEPROGRESS: false
INSTANCENAME: SQLEXPRESS
ISSVCACCOUNT: NT AUTHORITY\Network Service
ISSVCPASSWORD: <empty>
ISSVCSTARTUPTYPE: Automatic
QUIET: false
QUIETSIMPLE: false
SQLSVCACCOUNT: NT Service\MSSQL$SQLEXPRESS
SQLSVCPASSWORD: <empty>
UIMODE: AutoAdvance
X86: false
Configuration file: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20130812_155231\ConfigurationFile.ini
Detailed results:
Feature: Management Tools - Basic
Status: Passed
Feature: Database Engine Services
Status: Failed: see logs for details
Reason for failure: An error occurred during the setup process of the feature.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x851A0018
Error description: Could not find the Database Engine startup handle.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.2316.0&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4024&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4024
Feature: SQL Server Replication
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x851A0018
Error description: Could not find the Database Engine startup handle.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.2316.0&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4024&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4024
Feature: SQL Browser
Status: Passed
Feature: SQL Writer
Status: Passed
Feature: LocalDB
Status: Passed
Feature: SQL Client Connectivity
Status: Passed
Feature: SQL Client Connectivity SDK
Status: Passed
Feature: Setup Support Files
Status: Passed
Rules with failures:
Global rules:
There are no scenario-specific rules.
Rules report file: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20130812_155231\SystemConfigurationCheck_Report.htm
The following warnings were encountered while configuring settings on your SQL Server. These resources / settings were missing or invalid so default values were used in recreating the missing resources. Please review to make sure they don’t require further customization for your applications:
Service SID support has been enabled on the service.
Service SID support has been enabled on the service.
The following resources could not be configured during repair without additional user input. Review the warnings to understand your next steps:
The service failed to start for an unknown reason. For more information, see the event logs and the SQL Server error logs.我看了错误日志，上面写着
错误: 5178，严重性: 16，状态:1不能使用文件'c:\Program \Microsoft Server\MSSQL10.SQLEXPRESS\MSSQL\DATA\master.mdf‘，因为它最初是用扇区大小4096格式化的，现在位于扇区大小3072的卷上。将文件移动到扇区大小相同或小于原扇区大小的卷。
我读了最后一条错误信息，我真的很困惑。我被引导相信这是Server的一个问题，我的HD有4096扇区大小。
更新：
更多信息:我发现我的旧硬盘是512物理扇区大小，我的新高清是4096扇区大小。我听说这两个扇区大小之间存在转换问题，但是SQL Server是唯一在我的系统上产生错误的程序，我不明白。
更新：
我试图卸载Server并重新安装它。它没有成功地安装实例。
更新9-6-2013年：
我通过在硬盘上重新安装windows 7安装了SQL服务器来“修复”了这个问题。然后，我尝试清理一些事情，将新分区移动到硬盘驱动器的开头，并删除问题分区。然后，我不能用那个驱动器启动到窗口，然后，驱动器没有被我的bios看到。所以..。我还给你了！
我想这只是其中之一.
回答 1
Database Administration用户
发布于 2013-08-23 18:28:04
Momentus是一个“高级格式驱动器”，我看到您正在运行Windows7 SP1。如果驱动器运行512 e模式，则会导致Server出现问题。这是因为它可以在512字节边界的某个倍数中创建扇区，而不是总是以4096字节为单位。(您的错误是由6* 512字节扇区引起的。)
如果是这样的话，那么你需要采取一些纠正措施。微软有一篇博客文章和一篇针对Windows7和Windows2009 R2的知识库文章，其中指向了其他链接。
http://support.microsoft.com/kb/982018
如果这是您的问题，您可能需要下载最新的FSUTIL进行调查。http://www.microsoft.com/en-us/download/details.aspx?id=8903
这并不是每个人都能解决的问题。在MSDN论坛中，我发现了一组包含各种修复程序的长时间响应。http://social.msdn.microsoft.com/Forums/sqlserver/en-US/5c090e72-e83d-4fca-a087-75a3df5d2b4f/localdb-cannot-start-strange-error-in-log-contains-sector-size-4096-and-is-now-on-a-volume-with
从这次讨论中，您将看到一些人最终通过更新驱动程序来解决他们的问题。
https://dba.stackexchange.com/questions/48195
复制相似问题
腾讯云开发者
