Добро пожаловать в форум, Guest  >>   Войти | Регистрация | Поиск | Правила | В избранное | Подписаться
Все форумы / Microsoft SQL Server Новый топик    Ответить
 Не стартует сервер после отключения света - прошу помощи  [new]
Alexander_fx
Member

Откуда:
Сообщений: 657
Привет
отрубился свет - а в ИБП батарейки высохли
windows server 2012 стартует
mssql 2012 не поднимается вообще
в логах
The log scan number (234:101:1) passed to log scan in database 'master' is not valid. This error may indicate data corruption or that the log file (.ldf) does not match the data file (.mdf). If this error occurred during replication, re-create the publication. Otherwise, restore from backup if the problem results in a failure during startup.

на сервере team foundation server с ежедневным бекапом
и много других баз но только для чтения
подскажите как поднять сервер с минимальными потерями
бекапа master нет :(
20 ноя 15, 01:52    [18444707]     Ответить | Цитировать Сообщить модератору
 Re: Не стартует сервер после отключения света - прошу помощи  [new]
Relic Hunter
Member

Откуда: AB
Сообщений: 7376
Alexander_fx,

Замени мастер и отсюдова "C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\Binn\Templates". Ну и пользовательские по одной из бэкапа.
20 ноя 15, 02:19    [18444724]     Ответить | Цитировать Сообщить модератору
 Re: Не стартует сервер после отключения света - прошу помощи  [new]
Relic Hunter
Member

Откуда: AB
Сообщений: 7376
PS
или приаттач, если целые.
20 ноя 15, 02:20    [18444726]     Ответить | Цитировать Сообщить модератору
 Re: Не стартует сервер после отключения света - прошу помощи  [new]
Mind
Member

Откуда: Лучший город на Земле
Сообщений: 2322
Alexander_fx,

Rebuild System Databases
20 ноя 15, 02:20    [18444727]     Ответить | Цитировать Сообщить модератору
 Re: Не стартует сервер после отключения света - прошу помощи  [new]
Alexander_fx
Member

Откуда:
Сообщений: 657
запустил с диска setup mssql 2012
выбрал опцию reapir

вот такой лог
подменять на ночь глядя master не стал - боюсь наломать дров
смущает что ошибка не ссылается на master - или Could not find the Database Engine startup handle. это и есть ошибка отсутствия master ?


+
Overall summary:
Final result: Failed: see details below
Exit code (Decimal): -2061893607
Start time: 2015-11-20 03:38:08
End time: 2015-11-20 04:19:20
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 DQ: Use the following information to resolve the error, and then try the setup process again.
Next step for FullText: 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: SQL7
Machine processor count: 4
OS version: Future Windows Version
OS service pack:
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 Configured
SQL Server 2012 SQL7 MSSQL11.SQL7 Database Engine Services 1033 Enterprise Edition 11.2.5343.0 No Yes
SQL Server 2012 SQL7 MSSQL11.SQL7 SQL Server Replication 1033 Enterprise Edition 11.2.5343.0 No Yes
SQL Server 2012 SQL7 MSSQL11.SQL7 Full-Text and Semantic Extractions for Search 1033 Enterprise Edition 11.2.5343.0 No Yes
SQL Server 2012 SQL7 MSSQL11.SQL7 Data Quality Services 1033 Enterprise Edition 11.2.5058.0 No Yes
SQL Server 2012 SQL7 MSAS11.SQL7 Analysis Services 1033 Enterprise Edition 11.2.5343.0 No Yes
SQL Server 2012 SQL7 MSRS11.SQL7 Reporting Services - Native 1033 Enterprise Edition 11.2.5343.0 No Yes
SQL Server 2012 Management Tools - Basic 1033 Enterprise Edition 11.2.5343.0 No Yes
SQL Server 2012 Management Tools - Complete 1033 Enterprise Edition 11.2.5058.0 No Yes
SQL Server 2012 Client Tools Connectivity 1033 Enterprise Edition 11.2.5058.0 No Yes
SQL Server 2012 Client Tools SDK 1033 Enterprise Edition 11.2.5058.0 No Yes
SQL Server 2012 Data Quality Client 1033 11.2.5058.0 No Yes
SQL Server 2012 SQL Server Data Tools 1033 Enterprise Edition 11.2.5343.0 No Yes
SQL Server 2012 Integration Services 1033 Enterprise Edition 11.2.5343.0 No Yes
SQL Server 2012 LocalDB 1033 Express Edition 11.2.5343.0 No Yes
SQL Server 2012 Reporting Services - SharePoint 11.2.5343.0 No Yes

Package properties:
Description: Microsoft SQL Server 2012
ProductName: SQL Server 2012
Type: RTM
Version: 11
SPLevel: 0
Installation location: E:\x64\setup\
Installation edition: Enterprise

User Input Settings:
ACTION: Repair
AGTDOMAINGROUP: <empty>
AGTSVCACCOUNT: NT Service\SQLAgent$SQL7
AGTSVCPASSWORD: <empty>
AGTSVCSTARTUPTYPE: Manual
ASCONFIGDIR: Config
ASSVCACCOUNT: NT Service\MSOLAP$SQL7
ASSVCPASSWORD: <empty>
CLTSTARTUPTYPE: 0
CLTSVCACCOUNT: <empty>
CLTSVCPASSWORD: <empty>
CONFIGURATIONFILE: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20151120_033708\ConfigurationFile.ini
CTLRSTARTUPTYPE: 0
CTLRSVCACCOUNT: <empty>
CTLRSVCPASSWORD: <empty>
ENU: true
FAILOVERCLUSTERGROUP: <empty>
FAILOVERCLUSTERNETWORKNAME: <empty>
FTSVCACCOUNT: NT Service\MSSQLFDLauncher$SQL7
FTSVCPASSWORD: <empty>
HELP: false
IACCEPTSQLSERVERLICENSETERMS: false
INDICATEPROGRESS: false
INSTANCENAME: SQL7
ISSVCACCOUNT: NT Service\MsDtsServer110
ISSVCPASSWORD: <empty>
ISSVCSTARTUPTYPE: Automatic
QUIET: false
QUIETSIMPLE: false
SQLSVCACCOUNT: NT Service\MSSQL$SQL7
SQLSVCPASSWORD: <empty>
UIMODE: Normal
X86: false

Configuration file: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20151120_033708\ConfigurationFile.ini

Detailed results:
Feature: Management Tools - Complete
Status: Passed

Feature: Client Tools Connectivity
Status: Passed

Feature: Client Tools SDK
Status: Passed

Feature: Management Tools - Basic
Status: Passed

Feature: SQL Server Data Tools
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: 0x851A0019
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.5343.0&EvtType=0xD15B4EB2@0x4BDAF9BA@1306@25&EvtType=0xD15B4EB2@0x4BDAF9BA@1306@25

Feature: Data Quality Services
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: 0x851A0019
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.5343.0&EvtType=0xD15B4EB2@0x4BDAF9BA@1306@25&EvtType=0xD15B4EB2@0x4BDAF9BA@1306@25

Feature: Full-Text and Semantic Extractions for Search
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: 0x851A0019
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.5343.0&EvtType=0xD15B4EB2@0x4BDAF9BA@1306@25&EvtType=0xD15B4EB2@0x4BDAF9BA@1306@25

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: 0x851A0019
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.5343.0&EvtType=0xD15B4EB2@0x4BDAF9BA@1306@25&EvtType=0xD15B4EB2@0x4BDAF9BA@1306@25

Feature: Integration Services
Status: Passed

Feature: Data Quality Client
Status: Passed

Feature: Reporting Services - Native
Status: Passed

Feature: Analysis Services
Status: Passed

Feature: Reporting Services - SharePoint
Status: Passed

Feature: SQL Browser
Status: Passed

Feature: Documentation Components
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\20151120_033708\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.


Сообщение было отредактировано: 21 ноя 15, 00:26
20 ноя 15, 04:25    [18444807]     Ответить | Цитировать Сообщить модератору
 Re: Не стартует сервер после отключения света - прошу помощи  [new]
Alexander_fx
Member

Откуда:
Сообщений: 657
Relic Hunter
Alexander_fx,

Замени мастер и отсюдова "C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\Binn\Templates". Ну и пользовательские по одной из бэкапа.


Привет
подскажи плиз откуда брать и куда залить.
по указанному пути нашел master.mdb
а куда его залить?
я правильно понимаю что если прокатит то у меня будет голый инстанс и надо будет ручками коннектить все базы
если да то есть ли способ узнать какие базы с какими путями у меня были -
было десятков 5- основные вспомню но боюсь что нить забыть
20 ноя 15, 17:02    [18448851]     Ответить | Цитировать Сообщить модератору
 Re: Не стартует сервер после отключения света - прошу помощи  [new]
Alexander_fx
Member

Откуда:
Сообщений: 657
Ребята - и напомню у меня mssql сервер не стартует - как я приаттачу или еще что сделаю.
в логах ошибка что я в первом посте написал
Картинка с другого сайта.
http://hostingkartinok.com/show-image.php?id=13d686aa533be77f27e1dbe993f317b1
20 ноя 15, 17:10    [18448908]     Ответить | Цитировать Сообщить модератору
 Re: Не стартует сервер после отключения света - прошу помощи  [new]
Relic Hunter
Member

Откуда: AB
Сообщений: 7376
Alexander_fx
а куда его залить?
я правильно понимаю что если прокатит то у меня будет голый инстанс и надо будет ручками коннектить все базы
если да то есть ли способ узнать какие базы с какими путями у меня были -
было десятков 5- основные вспомню но боюсь что нить забыть
Сюды C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\DATA. Но это дефолтное значение. при установке его могли и поменять. Вы с сервером, что вообще не знакомы?
20 ноя 15, 19:26    [18449668]     Ответить | Цитировать Сообщить модератору
 Re: Не стартует сервер после отключения света - прошу помощи  [new]
Relic Hunter
Member

Откуда: AB
Сообщений: 7376
Alexander_fx
Ребята - и напомню у меня mssql сервер не стартует
А не нужно было репеир запускать. Если подмена мастера не сработает, возможно потребуется переустановить ПО сервера.
20 ноя 15, 19:29    [18449686]     Ответить | Цитировать Сообщить модератору
 Re: Не стартует сервер после отключения света - прошу помощи  [new]
Alexander_fx
Member

Откуда:
Сообщений: 657
да - думаю reapir сделал свое грязное дело
подменил master MSDBData model - и вот теперь такие ошибки
брал из templates - клал в data
что делать дальше? я не сисадмин - базы для домашнего пользования - подскажите кто чем может :(


+
2015-11-20 19:47:15.66 Server Microsoft SQL Server 2012 - 11.0.5343.0 (X64)
May 4 2015 19:11:32
Copyright (c) Microsoft Corporation
Enterprise Edition (64-bit) on Windows NT 6.3 <X64> (Build 9600: ) (Hypervisor)

2015-11-20 19:47:15.66 Server (c) Microsoft Corporation.
2015-11-20 19:47:15.66 Server All rights reserved.
2015-11-20 19:47:15.66 Server Server process ID is 5752.
2015-11-20 19:47:15.66 Server System Manufacturer: 'Gigabyte Technology Co., Ltd.', System Model: 'GA-MA785GMT-UD2H'.
2015-11-20 19:47:15.66 Server Authentication mode is MIXED.
2015-11-20 19:47:15.66 Server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL11.SQL7\MSSQL\Log\ERRORLOG'.
2015-11-20 19:47:15.66 Server The service account is 'NT Service\MSSQL$SQL7'. This is an informational message; no user action is required.
2015-11-20 19:47:15.66 Server Registry startup parameters:
-d C:\Program Files\Microsoft SQL Server\MSSQL11.SQL7\MSSQL\DATA\master.mdf
-e C:\Program Files\Microsoft SQL Server\MSSQL11.SQL7\MSSQL\Log\ERRORLOG
-l C:\Program Files\Microsoft SQL Server\MSSQL11.SQL7\MSSQL\DATA\mastlog.ldf
2015-11-20 19:47:15.66 Server Command Line Startup Parameters:
-s "SQL7"
2015-11-20 19:47:15.89 Server SQL Server detected 1 sockets with 4 cores per socket and 4 logical processors per socket, 4 total logical processors; using 4 logical processors based on SQL Server licensing. This is an informational message; no user action is required.
2015-11-20 19:47:15.89 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2015-11-20 19:47:15.89 Server Detected 15869 MB of RAM. This is an informational message; no user action is required.
2015-11-20 19:47:15.89 Server Using conventional memory in the memory manager.
2015-11-20 19:47:15.97 Server This instance of SQL Server last reported using a process ID of 5420 at 11/20/2015 7:43:56 PM (local) 11/20/2015 4:43:56 PM (UTC). This is an informational message only; no user action is required.
2015-11-20 19:47:15.97 Server Node configuration: node 0: CPU mask: 0x000000000000000f:0 Active CPU mask: 0x000000000000000f:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2015-11-20 19:47:16.03 Server Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required.
2015-11-20 19:47:16.05 spid5s Starting up database 'master'.
2015-11-20 19:47:16.08 Server CLR version v4.0.30319 loaded.
2015-11-20 19:47:16.09 spid5s 1 transactions rolled forward in database 'master' (1:0). This is an informational message only. No user action is required.
2015-11-20 19:47:16.10 spid5s 0 transactions rolled back in database 'master' (1:0). This is an informational message only. No user action is required.
2015-11-20 19:47:16.17 Server Common language runtime (CLR) functionality initialized using CLR version v4.0.30319 from C:\Windows\Microsoft.NET\Framework64\v4.0.30319\.
2015-11-20 19:47:16.32 spid5s Resource governor reconfiguration succeeded.
2015-11-20 19:47:16.32 spid5s SQL Server Audit is starting the audits. This is an informational message. No user action is required.
2015-11-20 19:47:16.32 spid5s SQL Server Audit has started the audits. This is an informational message. No user action is required.
2015-11-20 19:47:16.35 spid5s SQL Trace ID 1 was started by login "sa".
2015-11-20 19:47:16.35 spid5s Server name is 'SQL7\SQL7'. This is an informational message only. No user action is required.
2015-11-20 19:47:16.47 spid10s A self-generated certificate was successfully loaded for encryption.
2015-11-20 19:47:16.47 spid10s Server is listening on [ 'any' <ipv6> 49203].
2015-11-20 19:47:16.47 spid10s Server is listening on [ 'any' <ipv4> 49203].
2015-11-20 19:47:16.47 spid10s Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\SQL7 ].
2015-11-20 19:47:16.47 spid10s Server local connection provider is ready to accept connection on [ \\.\pipe\MSSQL$SQL7\sql\query ].
2015-11-20 19:47:16.47 Server Server is listening on [ ::1 <ipv6> 49204].
2015-11-20 19:47:16.47 Server Server is listening on [ 127.0.0.1 <ipv4> 49204].
2015-11-20 19:47:16.47 Server Dedicated admin connection support was established for listening locally on port 49204.
2015-11-20 19:47:16.48 Server SQL Server is attempting to register a Service Principal Name (SPN) for the SQL Server service. Kerberos authentication will not be possible until a SPN is registered for the SQL Server service. This is an informational message. No user action is required.
2015-11-20 19:47:16.48 Server The SQL Server Network Interface library could not register the Service Principal Name (SPN) [ MSSQLSvc/SQL7:SQL7 ] for the SQL Server service. Windows return code: 0xffffffff, state: 63. Failure to register a SPN might cause integrated authentication to use NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies and if the SPN has not been manually registered.
2015-11-20 19:47:16.48 Server The SQL Server Network Interface library could not register the Service Principal Name (SPN) [ MSSQLSvc/SQL7:49203 ] for the SQL Server service. Windows return code: 0xffffffff, state: 63. Failure to register a SPN might cause integrated authentication to use NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies and if the SPN has not been manually registered.
2015-11-20 19:47:16.56 spid11s A new instance of the full-text filter daemon host process has been successfully started.
2015-11-20 19:47:16.61 spid5s Starting up database 'msdb'.
2015-11-20 19:47:16.61 spid6s Starting up database 'mssqlsystemresource'.
2015-11-20 19:47:16.63 spid5s Error: 17204, Severity: 16, State: 1.
2015-11-20 19:47:16.63 spid5s FCB::Open failed: Could not open file e:\sql11_main_t.obj.x86release\sql\mkmastr\databases\objfre\i386\MSDBData.mdf for file number 1. OS error: 21(The device is not ready.).
2015-11-20 19:47:16.63 spid5s Error: 5120, Severity: 16, State: 101.
2015-11-20 19:47:16.63 spid5s Unable to open the physical file "e:\sql11_main_t.obj.x86release\sql\mkmastr\databases\objfre\i386\MSDBData.mdf". Operating system error 21: "21(The device is not ready.)".
2015-11-20 19:47:16.64 spid6s The resource database build version is 11.00.5058. This is an informational message only. No user action is required.
2015-11-20 19:47:16.64 spid5s Error: 17207, Severity: 16, State: 1.
2015-11-20 19:47:16.64 spid5s FileMgr::StartLogFiles: Operating system error 2(The system cannot find the file specified.) occurred while creating or opening file 'e:\sql11_main_t.obj.x86release\sql\mkmastr\databases\objfre\i386\MSDBLog.ldf'. Diagnose and correct the operating system error, and retry the operation.
2015-11-20 19:47:16.64 spid5s File activation failure. The physical file name "e:\sql11_main_t.obj.x86release\sql\mkmastr\databases\objfre\i386\MSDBLog.ldf" may be incorrect.
2015-11-20 19:47:16.70 spid6s Starting up database 'model'.
2015-11-20 19:47:16.72 spid6s Error: 17204, Severity: 16, State: 1.
2015-11-20 19:47:16.72 spid6s FCB::Open failed: Could not open file e:\sql11_main_t.obj.x86release\sql\mkmastr\databases\objfre\i386\model.mdf for file number 1. OS error: 21(The device is not ready.).
2015-11-20 19:47:16.72 spid6s Error: 5120, Severity: 16, State: 101.
2015-11-20 19:47:16.72 spid6s Unable to open the physical file "e:\sql11_main_t.obj.x86release\sql\mkmastr\databases\objfre\i386\model.mdf". Operating system error 21: "21(The device is not ready.)".
2015-11-20 19:47:16.74 spid6s Error: 17207, Severity: 16, State: 1.
2015-11-20 19:47:16.74 spid6s FileMgr::StartLogFiles: Operating system error 2(The system cannot find the file specified.) occurred while creating or opening file 'e:\sql11_main_t.obj.x86release\sql\mkmastr\databases\objfre\i386\modellog.ldf'. Diagnose and correct the operating system error, and retry the operation.
2015-11-20 19:47:16.74 spid6s File activation failure. The physical file name "e:\sql11_main_t.obj.x86release\sql\mkmastr\databases\objfre\i386\modellog.ldf" may be incorrect.
2015-11-20 19:47:16.74 spid6s Error: 945, Severity: 14, State: 2.
2015-11-20 19:47:16.74 spid6s Database 'model' cannot be opened due to inaccessible files or insufficient memory or disk space. See the SQL Server errorlog for details.
2015-11-20 19:47:16.74 spid6s SQL Server shutdown has been initiated
2015-11-20 19:47:16.74 spid6s SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.
2015-11-20 19:47:17.43 Logon Error: 18456, Severity: 14, State: 5.
2015-11-20 19:47:17.43 Logon Login failed for user 'NT Service\ReportServer$SQL7'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2015-11-20 19:47:17.51 Logon Error: 18456, Severity: 14, State: 5.
2015-11-20 19:47:17.51 Logon Login failed for user 'SQL7\Administrator'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2015-11-20 19:47:17.75 spid6s Error: 25725, Severity: 16, State: 1.
2015-11-20 19:47:17.75 spid6s An error occurred while trying to flush all running Extended Event sessions. Some events may be lost.


Сообщение было отредактировано: 21 ноя 15, 00:27
20 ноя 15, 22:27    [18450571]     Ответить | Цитировать Сообщить модератору
 Re: Не стартует сервер после отключения света - прошу помощи  [new]
o-o
Guest
Alexander_fx,

потому что фигню вы сделали, а не ребилд.
вам Mind дал ссылку на документацию? 18444727
но интереснее, конечно, делать не то, что официальный хэлп продукта описывает,
а то, что придумал Relic Hunter (c).
по ссылке сходите, там пошагово расписано.
и про те файлы, что вам насоветовали тупо скопировать, тоже там же написано,
зачем они.
они используются при ребилде:
BOL
Verify that copies of the master, model, msdb data and log template files exist on the local server.
The default location for the template files is C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\Binn\Templates.
These files are used during the rebuild process and must be present for Setup to succeed.

а не "просто копируются"
20 ноя 15, 23:52    [18451033]     Ответить | Цитировать Сообщить модератору
 Re: Не стартует сервер после отключения света - прошу помощи  [new]
Relic Hunter
Member

Откуда: AB
Сообщений: 7376
o-o,

Во первых, ТС как раз и не сделал, что Relic Hunter рекомендовал, а нажал Repair.
Во вторых..
Using the Template Master Database
For 2008 R2 and 2012 the system database recovery function works differently. Rather than using T-SQL scripts there are template databases created at install time, which are copied over the database and transaction log files of your system databases by the setup.exe /REBUILDDATABASE option. If your msdb and model databases are okay then it may be simpler to manually copy the template files of the master database to where they belong rather than rebuild all three system databases and restore the msdb and model from backup. The template files are found in the "C:\Program Files\Microsoft SQL Server\MSSQL<version>.<instance_name>\MSSQL\Binn\Templates" directory depending on your instance name and version.
21 ноя 15, 00:23    [18451191]     Ответить | Цитировать Сообщить модератору
 Re: Не стартует сервер после отключения света - прошу помощи  [new]
Relic Hunter
Member

Откуда: AB
Сообщений: 7376
Alexander_fx
подменил master MSDBData model - и вот теперь такие ошибки
бл..А это тут при чем? Ты же мастер лечил???? MSDBData model - верни обратно.
21 ноя 15, 00:29    [18451210]     Ответить | Цитировать Сообщить модератору
 Re: Не стартует сервер после отключения света - прошу помощи  [new]
Relic Hunter
Member

Откуда: AB
Сообщений: 7376
Alexander_fx,

Как раз в модели пути к файлам хранятся, которые ты перетер. Но это не страшно :) Делаем это приседание (скопируй папку DATA всторонку прежде)..

NET START MSSQL$SQLEXPRESS /f /T3608
SQLCMD -S .\SQLEXPRESS
1>ALTER DATABASE model MODIFY FILE ( NAME = modeldev, FILENAME = 'C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\DATA\model.mdf');
2>ALTER DATABASE model MODIFY FILE ( NAME = modellog, FILENAME = 'C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\DATA\modellog.ldf');
3> go

ALTER DATABASE msdb MODIFY FILE ( NAME = MSDBData, FILENAME = 'C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\DATA\MSDBData.mdf');
ALTER DATABASE msdb MODIFY FILE ( NAME = MSDBLog, FILENAME = 'C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\DATA\MSDBLog.ldf');

ALTER DATABASE tempdb MODIFY FILE ( NAME = tempdev, FILENAME = 'C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\DATA\temp.mdf');
ALTER DATABASE tempdb MODIFY FILE ( NAME = templog, FILENAME = 'C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\DATA\temp.ldf');

go

exit;

NET STOP MSSQL$SQLEXPRESS 
21 ноя 15, 00:51    [18451281]     Ответить | Цитировать Сообщить модератору
 Re: Не стартует сервер после отключения света - прошу помощи  [new]
o-o
Guest
Relic Hunter
o-o,

Во первых, ТС как раз и не сделал, что Relic Hunter рекомендовал, а нажал Repair.
Во вторых..
Using the Template Master Database
For 2008 R2 and 2012 the system database recovery function works differently. Rather than using T-SQL scripts there are template databases created at install time, which are copied over the database and transaction log files of your system databases by the setup.exe /REBUILDDATABASE option. If your msdb and model databases are okay then it may be simpler to manually copy the template files of the master database to where they belong rather than rebuild all three system databases and restore the msdb and model from backup. The template files are found in the "C:\Program Files\Microsoft SQL Server\MSSQL<version>.<instance_name>\MSSQL\Binn\Templates" directory depending on your instance name and version.

нет.
это ровно последствия вашего совета.
показываю на примере инстанса sql_2008
(на картинке видно, что несмотря на название, это не 2008, а 2008 R2)
сперва я его запускаю, убеждаюсь, что жив-здоров,
создаю базу db1.
останавливаю инстанс и изображаю, что мастер навернулся.
копирую только мастер из темплэйтов.
что остальные файлы системных баз не трогаю,
можете увидеть из даты их создания/модификации.
инстанс более не стартует.
в еррорлоге ровно то, что предъявил ТС:
+

2015-11-21 12:41:03.74 Server Microsoft SQL Server 2008 R2 (SP3) - 10.50.6000.34 (X64)
Aug 19 2014 12:21:34
Copyright (c) Microsoft Corporation
Developer Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1)

2015-11-21 12:41:03.74 Server (c) Microsoft Corporation.
2015-11-21 12:41:03.74 Server All rights reserved.
2015-11-21 12:41:03.74 Server Server process ID is 4488.
2015-11-21 12:41:03.74 Server System Manufacturer: 'Hewlett-Packard', System Model: 'HP Pavilion g6 Notebook PC'.
2015-11-21 12:41:03.74 Server Authentication mode is MIXED.
2015-11-21 12:41:03.74 Server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL10_50.SQL_2008\MSSQL\Log\ERRORLOG'.
2015-11-21 12:41:03.74 Server This instance of SQL Server last reported using a process ID of 2796 at 21/11/2015 12:39:50 (local) 21/11/2015 11:39:50 (UTC). This is an informational message only; no user action is required.
2015-11-21 12:41:03.74 Server Registry startup parameters:
-d C:\Program Files\Microsoft SQL Server\MSSQL10_50.SQL_2008\MSSQL\DATA\master.mdf
-e C:\Program Files\Microsoft SQL Server\MSSQL10_50.SQL_2008\MSSQL\Log\ERRORLOG
-l C:\Program Files\Microsoft SQL Server\MSSQL10_50.SQL_2008\MSSQL\DATA\mastlog.ldf
2015-11-21 12:41:03.75 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2015-11-21 12:41:03.75 Server Detected 4 CPUs. This is an informational message; no user action is required.
2015-11-21 12:41:03.81 Server Using locked pages for buffer pool.
2015-11-21 12:41:03.89 Server Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required.
2015-11-21 12:41:03.92 Server Node configuration: node 0: CPU mask: 0x000000000000000f:0 Active CPU mask: 0x000000000000000f:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2015-11-21 12:41:03.95 spid7s Starting up database 'master'.
2015-11-21 12:41:04.15 spid7s Resource governor reconfiguration succeeded.
2015-11-21 12:41:04.15 spid7s SQL Server Audit is starting the audits. This is an informational message. No user action is required.
2015-11-21 12:41:04.15 spid7s SQL Server Audit has started the audits. This is an informational message. No user action is required.
2015-11-21 12:41:04.16 spid7s FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'SQL_2008'.
2015-11-21 12:41:04.20 spid7s SQL Trace ID 1 was started by login "sa".
2015-11-21 12:41:04.20 spid7s Starting up database 'mssqlsystemresource'.
2015-11-21 12:41:04.24 spid7s The resource database build version is 10.50.6000. This is an informational message only. No user action is required.
2015-11-21 12:41:04.40 spid7s Server name is 'HP\SQL_2008'. This is an informational message only. No user action is required.
2015-11-21 12:41:04.40 spid10s Starting up database 'model'.
2015-11-21 12:41:04.40 spid7s Informational: No full-text supported languages found.
2015-11-21 12:41:04.40 spid7s Starting up database 'msdb'.
2015-11-21 12:41:04.41 spid7s Error: 17204, Severity: 16, State: 1.
2015-11-21 12:41:04.41 spid7s FCB::Open failed: Could not open file e:\sql10_main_t.obj.x86fre\sql\mkmastr\databases\objfre\i386\MSDBData.mdf for file number 1. OS error: 3(failed to retrieve text for this error. Reason: 15100).
2015-11-21 12:41:04.41 spid7s Error: 5120, Severity: 16, State: 101.
2015-11-21 12:41:04.41 spid7s Unable to open the physical file "e:\sql10_main_t.obj.x86fre\sql\mkmastr\databases\objfre\i386\MSDBData.mdf". Operating system error 3: "3(failed to retrieve text for this error. Reason: 15105)".
2015-11-21 12:41:04.41 spid7s Error: 17207, Severity: 16, State: 1.
2015-11-21 12:41:04.41 spid7s FileMgr::StartLogFiles: Operating system error 2(failed to retrieve text for this error. Reason: 15105) occurred while creating or opening file 'e:\sql10_main_t.obj.x86fre\sql\mkmastr\databases\objfre\i386\MSDBLog.ldf'. Diagnose and correct the operating system error, and retry the operation.
2015-11-21 12:41:04.41 spid7s File activation failure. The physical file name "e:\sql10_main_t.obj.x86fre\sql\mkmastr\databases\objfre\i386\MSDBLog.ldf" may be incorrect.
2015-11-21 12:41:04.42 spid10s Error: 17204, Severity: 16, State: 1.
2015-11-21 12:41:04.42 spid10s FCB::Open failed: Could not open file e:\sql10_main_t.obj.x86fre\sql\mkmastr\databases\objfre\i386\model.mdf for file number 1. OS error: 3(failed to retrieve text for this error. Reason: 15105).
2015-11-21 12:41:04.42 spid10s Error: 5120, Severity: 16, State: 101.
2015-11-21 12:41:04.42 spid10s Unable to open the physical file "e:\sql10_main_t.obj.x86fre\sql\mkmastr\databases\objfre\i386\model.mdf". Operating system error 3: "3(failed to retrieve text for this error. Reason: 15105)".
2015-11-21 12:41:04.42 spid10s Error: 17207, Severity: 16, State: 1.
2015-11-21 12:41:04.42 spid10s FileMgr::StartLogFiles: Operating system error 2(failed to retrieve text for this error. Reason: 15105) occurred while creating or opening file 'e:\sql10_main_t.obj.x86fre\sql\mkmastr\databases\objfre\i386\modellog.ldf'. Diagnose and correct the operating system error, and retry the operation.
2015-11-21 12:41:04.42 spid10s File activation failure. The physical file name "e:\sql10_main_t.obj.x86fre\sql\mkmastr\databases\objfre\i386\modellog.ldf" may be incorrect.
2015-11-21 12:41:04.42 spid10s Error: 945, Severity: 14, State: 2.
2015-11-21 12:41:04.42 spid10s Database 'model' cannot be opened due to inaccessible files or insufficient memory or disk space. See the SQL Server errorlog for details.
2015-11-21 12:41:04.42 spid10s Could not create tempdb. You may not have enough disk space available. Free additional disk space by deleting other files on the tempdb drive and then restart SQL Server. Check for additional errors in the event log that may indicate why the tempdb files could not be initialized.
2015-11-21 12:41:04.42 spid10s SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.

теперь вопрос к вам.
вы сами пробовали проделать то, что насоветовали?
то, что вы процитировали, это BOL?
или вот отсюда скопировано:
Restoring the SQL Server Master Database Even Without a Backup
а теперь подумайте сами.
исходя из ошибок в еррорлоге.
разве непонятно, что пути к моделу и мсдб хранятся *в мастере*,
т.е. это вы, простым копированием, не переправили их на нужные?
а Login failed for user 'SQL7\Administrator' о чем говорит?
наверное, в темплэйтном мастере нет ни намека на какие-то логины.
а теперь вернемся к документированному ребилду.
это не тупое копирование.
в Setup /QUIET /ACTION=REBUILDDATABASE /INSTANCENAME=InstanceName /SQLSYSADMINACCOUNTS=accounts [ /SAPWD= StrongPassword ] [ /SQLCOLLATION=CollationName]
вы указываете логин(ы), к-ый потом будет попадать на сервер.
и инстанс подымется, т.к. все системные базы будут лежать по дефолтному пути установки и мастер "будет об эом знать":
BOL
When the master, model, msdb, and tempdb system databases are rebuilt, the databases are dropped and re-created in their original location.

все это обеспечивает тот самый ребилд системных баз

К сообщению приложен файл. Размер - 146Kb
21 ноя 15, 15:11    [18452181]     Ответить | Цитировать Сообщить модератору
Все форумы / Microsoft SQL Server Ответить