Выключали сервер на праздники. Теперь не запускается SQL служба
Здравствуйте. Помогите разобраться, в чем проблема. Пробовал разобраться сам, зашел в тупик. Гуглил по выдаваемым ошибкам вроде сводится к тому что нужно восстановить базу master.mdf. Но как восстановить, если sql не запускается.
Вот лог последний
2018-01-04 07:24:17.79 Server Microsoft SQL Server 2008 (RTM) - 10.0.1600.22 (X64)
Jul 9 2008 14:17:44
Copyright © 1988-2008 Microsoft Corporation
Standard Edition (64-bit) on Windows NT 6.1 <X64> (Build 7600: )
2018-01-04 07:24:17.79 Server © 2005 Microsoft Corporation.
2018-01-04 07:24:17.79 Server All rights reserved.
2018-01-04 07:24:17.79 Server Server process ID is 4700.
2018-01-04 07:24:17.79 Server System Manufacturer: 'System manufacturer', System Model: 'System Product Name'.
2018-01-04 07:24:17.79 Server Authentication mode is MIXED.
2018-01-04 07:24:17.79 Server Logging SQL Server messages in file 'D:\SQL BASe New\MSSQL10.MSSQLSERVER\MSSQL\Log\ERRORLOG'.
2018-01-04 07:24:17.79 Server This instance of SQL Server last reported using a process ID of 4444 at 04.01.2018 7:20:53 (local) 04.01.2018 4:20:53 (UTC). This is an informational message only; no user action is required.
2018-01-04 07:24:17.79 Server Registry startup parameters:
-m D:\SQL BASe New\MSSQL10.MSSQLSERVER\MSSQL\DATA\master.mdf
-e D:\SQL BASe New\MSSQL10.MSSQLSERVER\MSSQL\Log\ERRORLOG
-l D:\SQL BASe New\MSSQL10.MSSQLSERVER\MSSQL\DATA\mastlog.ldf
2018-01-04 07:24:17.79 Server Error: 17113, Severity: 16, State: 1.
2018-01-04 07:24:17.79 Server Error 3(Системе не удается найти указанный путь.) occurred while opening file 'master.mdf' to obtain configuration information at startup. An invalid startup option might have caused the error. Verify your startup options, and correct or remove them if necessary.
Вот лог последний
2018-01-04 07:24:17.79 Server Microsoft SQL Server 2008 (RTM) - 10.0.1600.22 (X64)
Jul 9 2008 14:17:44
Copyright © 1988-2008 Microsoft Corporation
Standard Edition (64-bit) on Windows NT 6.1 <X64> (Build 7600: )
2018-01-04 07:24:17.79 Server © 2005 Microsoft Corporation.
2018-01-04 07:24:17.79 Server All rights reserved.
2018-01-04 07:24:17.79 Server Server process ID is 4700.
2018-01-04 07:24:17.79 Server System Manufacturer: 'System manufacturer', System Model: 'System Product Name'.
2018-01-04 07:24:17.79 Server Authentication mode is MIXED.
2018-01-04 07:24:17.79 Server Logging SQL Server messages in file 'D:\SQL BASe New\MSSQL10.MSSQLSERVER\MSSQL\Log\ERRORLOG'.
2018-01-04 07:24:17.79 Server This instance of SQL Server last reported using a process ID of 4444 at 04.01.2018 7:20:53 (local) 04.01.2018 4:20:53 (UTC). This is an informational message only; no user action is required.
2018-01-04 07:24:17.79 Server Registry startup parameters:
-m D:\SQL BASe New\MSSQL10.MSSQLSERVER\MSSQL\DATA\master.mdf
-e D:\SQL BASe New\MSSQL10.MSSQLSERVER\MSSQL\Log\ERRORLOG
-l D:\SQL BASe New\MSSQL10.MSSQLSERVER\MSSQL\DATA\mastlog.ldf
2018-01-04 07:24:17.79 Server Error: 17113, Severity: 16, State: 1.
2018-01-04 07:24:17.79 Server Error 3(Системе не удается найти указанный путь.) occurred while opening file 'master.mdf' to obtain configuration information at startup. An invalid startup option might have caused the error. Verify your startup options, and correct or remove them if necessary.
Найденные решения
Остальные ответы
Подписаться на ответы
Инфостарт бот
Сортировка:
Древо развёрнутое
Свернуть все
2018-01-04 07:43:56.82 Server Microsoft SQL Server 2008 (RTM) - 10.0.1600.22 (X64)
Jul 9 2008 14:17:44
Copyright © 1988-2008 Microsoft Corporation
Standard Edition (64-bit) on Windows NT 6.1 <X64> (Build 7600: )
2018-01-04 07:43:56.84 Server © 2005 Microsoft Corporation.
2018-01-04 07:43:56.84 Server All rights reserved.
2018-01-04 07:43:56.84 Server Server process ID is 5040.
2018-01-04 07:43:56.84 Server System Manufacturer: 'System manufacturer', System Model: 'System Product Name'.
2018-01-04 07:43:56.84 Server Authentication mode is MIXED.
2018-01-04 07:43:56.84 Server Logging SQL Server messages in file 'D:\SQL BASe New\MSSQL10.MSSQLSERVER\MSSQL\Log\ERRORLOG'.
2018-01-04 07:43:56.84 Server This instance of SQL Server last reported using a process ID of 4700 at 04.01.2018 7:24:17 (local) 04.01.2018 4:24:17 (UTC). This is an informational message only; no user action is required.
2018-01-04 07:43:56.84 Server Registry startup parameters:
-d D:\SQL BASe New\MSSQL10.MSSQLSERVER\MSSQL\DATA\master.mdf
-e D:\SQL BASe New\MSSQL10.MSSQLSERVER\MSSQL\Log\ERRORLOG
-l D:\SQL BASe New\MSSQL10.MSSQLSERVER\MSSQL\DATA\mastlog.ldf
2018-01-04 07:43:56.87 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2018-01-04 07:43:56.87 Server Detected 4 CPUs. This is an informational message; no user action is required.
2018-01-04 07:43:56.90 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.
2018-01-04 07:44:02.08 Server Node configuration: node 0: CPU mask: 0x000000000000000f Active CPU mask: 0x000000000000000f. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2018-01-04 07:44:02.11 spid7s Starting up database 'master'.
2018-01-04 07:44:02.15 spid7s WARNING: did not see LOP_CKPT_END.
2018-01-04 07:44:02.15 spid7s Error: 3414, Severity: 21, State: 2.
2018-01-04 07:44:02.15 spid7s An error occurred during recovery, preventing the database 'master' (database ID 1) from restarting. Diagnose the recovery errors and fix them, or restore from a known good backup. If errors are not corrected or expected, contact Technical Support.
2018-01-04 07:44:02.15 spid7s Cannot recover the master database. SQL Server is unable to run. Restore master from a full backup, repair it, or rebuild it. For more information about how to rebuild the master database, see SQL Server Books Online.
Jul 9 2008 14:17:44
Copyright © 1988-2008 Microsoft Corporation
Standard Edition (64-bit) on Windows NT 6.1 <X64> (Build 7600: )
2018-01-04 07:43:56.84 Server © 2005 Microsoft Corporation.
2018-01-04 07:43:56.84 Server All rights reserved.
2018-01-04 07:43:56.84 Server Server process ID is 5040.
2018-01-04 07:43:56.84 Server System Manufacturer: 'System manufacturer', System Model: 'System Product Name'.
2018-01-04 07:43:56.84 Server Authentication mode is MIXED.
2018-01-04 07:43:56.84 Server Logging SQL Server messages in file 'D:\SQL BASe New\MSSQL10.MSSQLSERVER\MSSQL\Log\ERRORLOG'.
2018-01-04 07:43:56.84 Server This instance of SQL Server last reported using a process ID of 4700 at 04.01.2018 7:24:17 (local) 04.01.2018 4:24:17 (UTC). This is an informational message only; no user action is required.
2018-01-04 07:43:56.84 Server Registry startup parameters:
-d D:\SQL BASe New\MSSQL10.MSSQLSERVER\MSSQL\DATA\master.mdf
-e D:\SQL BASe New\MSSQL10.MSSQLSERVER\MSSQL\Log\ERRORLOG
-l D:\SQL BASe New\MSSQL10.MSSQLSERVER\MSSQL\DATA\mastlog.ldf
2018-01-04 07:43:56.87 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2018-01-04 07:43:56.87 Server Detected 4 CPUs. This is an informational message; no user action is required.
2018-01-04 07:43:56.90 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.
2018-01-04 07:44:02.08 Server Node configuration: node 0: CPU mask: 0x000000000000000f Active CPU mask: 0x000000000000000f. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2018-01-04 07:44:02.11 spid7s Starting up database 'master'.
2018-01-04 07:44:02.15 spid7s WARNING: did not see LOP_CKPT_END.
2018-01-04 07:44:02.15 spid7s Error: 3414, Severity: 21, State: 2.
2018-01-04 07:44:02.15 spid7s An error occurred during recovery, preventing the database 'master' (database ID 1) from restarting. Diagnose the recovery errors and fix them, or restore from a known good backup. If errors are not corrected or expected, contact Technical Support.
2018-01-04 07:44:02.15 spid7s Cannot recover the master database. SQL Server is unable to run. Restore master from a full backup, repair it, or rebuild it. For more information about how to rebuild the master database, see SQL Server Books Online.
Для получения уведомлений об ответах подключите телеграм бот:
Инфостарт бот