BitLocker metadata for the encrypted drive is not valid (0x80310010) - bitlocker

I'm moving an external drive to a new computer.
The drive is protected with Bitlocker, but I can unlock it and view the contents.
However, when I try to configure auto-unlock I see:
C:\>manage-bde -autounlock -enable d:
BitLocker Drive Encryption: Configuration Tool version 10.0.17763
Copyright (C) 2013 Microsoft Corporation. All rights reserved.
ERROR: An error occurred (code 0x80310010):
The BitLocker metadata for the encrypted drive is not valid. You can attempt to repair the drive to restore access.
Is there a way to rebuild the metadata?
Clearly the metadata is valid enough to unlock the volume, so I'm wondering if the error message is even correct.

Further investigation revealed that the error message was incorrect.
The cause of the problem was that the disk was marked as readonly.
After using diskpart to clear the readonly flag, then locking and unlocking the volume, manage-bde -autounlock -enable d: worked correctly.
C:\>diskpart
Microsoft DiskPart version 10.0.17763.1554
Copyright (C) Microsoft Corporation.
On computer: HYPER-V
DISKPART> list volume
Volume ### Ltr Label Fs Type Size Status Info
---------- --- ----------- ----- ---------- ------- --------- --------
Volume 0 C NTFS Partition 465 GB Healthy Boot
Volume 1 Recovery NTFS Partition 499 MB Healthy Hidden
Volume 2 FAT32 Partition 100 MB Healthy System
Volume 3 D DATA ReFS Partition 7449 GB Healthy
DISKPART> select volume 3
Volume 3 is the selected volume.
DISKPART> attributes disk
Current Read-only State : Yes
Read-only : Yes
Boot Disk : No
Pagefile Disk : No
Hibernation File Disk : No
Crashdump Disk : No
Clustered Disk : No
DISKPART> attributes disk clear readonly
Disk attributes cleared successfully.
DISKPART> exit
C:\>manage-bde -lock d:
BitLocker Drive Encryption: Configuration Tool version 10.0.17763
Copyright (C) 2013 Microsoft Corporation. All rights reserved.
Volume D: is now locked
C:\>manage-bde -unlock d: -pw
BitLocker Drive Encryption: Configuration Tool version 10.0.17763
Copyright (C) 2013 Microsoft Corporation. All rights reserved.
Enter the password to unlock this volume:
The password successfully unlocked volume D:.
C:\>manage-bde -autounlock -enable d:
BitLocker Drive Encryption: Configuration Tool version 10.0.17763
Copyright (C) 2013 Microsoft Corporation. All rights reserved.
Key Protectors Added:
External Key:
ID: {3CEFC24B-BBBF-4818-A128-9FA0E87E872D}
External Key File Name:
3CEFC24B-BBBF-4818-A128-9FA0E87E872D.BEK
Automatic unlock enabled.

Related

Can't install SQL server 2017 or 2019 on a new windows 11

Could anyone provide some assistance? We can't install SQL Server 2017 or 2019 on a brandnew Windows 11 pc. We have removed all SQL applications, rebooted and tried again. We had the IT of the customer remove and reinstall Windows after a formatting of the hard disc and tried again after, always the same errors.
System specs are: AMD Ryzen 5 5500U 2.10GHz with 8GB RAM
We get error 0x851A001A in event viewer application log, but "fsutil fsinfo sectorinfo c:" shows the size is 4096.
In SQL Server setup we get the error: "Wait on database engine recovery handle failed check the sql server error log for potential causes"
And in the Log of 2019 for instance we get this:
2022-10-05 14:03:48.75 Server Microsoft SQL Server 2019 (RTM-CU18) (KB5017593) - 15.0.4261.1 (X64)
Sep 12 2022 15:07:06
Copyright (C) 2019 Microsoft Corporation
Express Edition (64-bit) on Windows 10 Pro 10.0 (Build 22621: ) (Hypervisor)
2022-10-05 14:03:48.75 Server UTC adjustment: 2:00
2022-10-05 14:03:48.75 Server (c) Microsoft Corporation.
2022-10-05 14:03:48.75 Server All rights reserved.
2022-10-05 14:03:48.75 Server Server process ID is 7464.
2022-10-05 14:03:48.75 Server System Manufacturer: 'LENOVO', System Model: '20YG00B6MB'.
2022-10-05 14:03:48.75 Server Authentication mode is MIXED.
2022-10-05 14:03:48.75 Server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL15.OXYGEN2\MSSQL\Log\ERRORLOG'.
2022-10-05 14:03:48.75 Server The service account is 'NT Service\MSSQL$OXYGEN2'. This is an informational message; no user action is required.
2022-10-05 14:03:48.75 Server Registry startup parameters:
-d C:\Program Files\Microsoft SQL Server\MSSQL15.OXYGEN2\MSSQL\DATA\master.mdf
-e C:\Program Files\Microsoft SQL Server\MSSQL15.OXYGEN2\MSSQL\Log\ERRORLOG
-l C:\Program Files\Microsoft SQL Server\MSSQL15.OXYGEN2\MSSQL\DATA\mastlog.ldf
2022-10-05 14:03:48.75 Server Command Line Startup Parameters:
-s "OXYGEN2"
-m "SqlSetup"
-T 4022
-T 4010
-T 1905
-T 3701
-T 8015
2022-10-05 14:03:48.76 Server SQL Server detected 1 sockets with 6 cores per socket and 12 logical processors per socket, 12 total logical processors; using 8 logical processors based on SQL Server licensing. This is an informational message; no user action is required.
2022-10-05 14:03:48.76 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2022-10-05 14:03:48.76 Server Detected 6986 MB of RAM. This is an informational message; no user action is required.
2022-10-05 14:03:48.76 Server Using conventional memory in the memory manager.
2022-10-05 14:03:48.76 Server Page exclusion bitmap is enabled.
2022-10-05 14:03:48.84 Server Buffer Pool: Allocating 524288 bytes for 378182 hashPages.
2022-10-05 14:03:48.84 Server Default collation: SQL_Latin1_General_CP1_CI_AS (us_english 1033)
2022-10-05 14:03:48.87 Server Buffer pool extension is already disabled. No action is necessary.
2022-10-05 14:03:48.90 Server Perfmon counters for resource governor pools and groups failed to initialize and are disabled.
2022-10-05 14:03:48.93 Server Query Store settings initialized with enabled = 1,
2022-10-05 14:03:48.93 Server The maximum number of dedicated administrator connections for this instance is '1'
2022-10-05 14:03:48.93 Server This instance of SQL Server last reported using a process ID of 328 at 5/10/2022 14:03:46 (local) 5/10/2022 12:03:46 (UTC). This is an informational message only; no user action is required.
2022-10-05 14:03:48.94 Server Node configuration: node 0: CPU mask: 0x00000000000000ff:0 Active CPU mask: 0x00000000000000ff:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2022-10-05 14:03:48.94 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.
2022-10-05 14:03:48.95 Server In-Memory OLTP initialized on lowend machine.
2022-10-05 14:03:48.96 Server [INFO] Created Extended Events session 'hkenginexesession'
2022-10-05 14:03:48.96 Server Database Instant File Initialization: disabled. For security and performance considerations see the topic 'Database Instant File Initialization' in SQL Server Books Online. This is an informational message only. No user action is required.
2022-10-05 14:03:48.97 Server Total Log Writer threads: 2. This is an informational message; no user action is required.
2022-10-05 14:03:48.97 Server Database Mirroring Transport is disabled in the endpoint configuration.
2022-10-05 14:03:48.97 Server clwb is selected for pmem flush operation.
2022-10-05 14:03:48.97 Server Software Usage Metrics is disabled.
2022-10-05 14:03:48.97 spid10s Warning ******************
2022-10-05 14:03:48.97 spid10s SQL Server started in single-user mode. This an informational message only. No user action is required.
2022-10-05 14:03:48.97 spid10s Starting up database 'master'.
2022-10-05 14:03:48.99 spid10s There have been 256 misaligned log IOs which required falling back to synchronous IO. The current IO is on file C:\Program Files\Microsoft SQL Server\MSSQL15.OXYGEN2\MSSQL\DATA\master.mdf.
2022-10-05 14:03:49.05 Server CLR version v4.0.30319 loaded.
2022-10-05 14:03:49.13 Server Common language runtime (CLR) functionality initialized using CLR version v4.0.30319 from C:\Windows\Microsoft.NET\Framework64\v4.0.30319\.
For systems running Windows 11, some storage devices and new device drivers will display a disk sector size larger than the supported 4 KB sector size.
When this occurs, SQL Server cannot start because of an unsupported file system. SQL Server currently supports sector storage sizes of 512 bytes and 4 KB.
You can fix the problem by running the command:
fsutil fsinfo sectorinfo <volume pathname>
Example:
fsutil fsinfo sectorinfo E:
Look for the value PhysicalBytesPerSectorForAtomicity, returned in bytes. A value of 4096 indicates a sector storage size of 4 KB.
If you are still having problems running SQL server, then you can follow the instructions on this page.

What is Redis change its own configurations

Redis change its own config dir to /etc/cron.d and dbfile to ntp instead of default configuration. Once we restart the redis it will reset to /var/lib/redis and dump.rdb but after awhile, it gives "Failed opening the RDB file" error
Default dire and rdb file has correct permission and redis only allow for internal IPs.
cli output
127.0.0.1:6381> CONFIG GET dir
1) "dir"
2) "/etc/cron.d"
127.0.0.1:6381> CONFIG GET "dbfilename"
1) "dbfilename"
2) "ntp"
/var/log/redis/redis-server.log
3204:M 21 May 16:07:19.124 * Background saving terminated with success
3204:M 21 May 16:12:18.962 * 10000 changes in 60 seconds. Saving...
3204:M 21 May 16:12:18.967 * Background saving started by pid 25469
25469:C 21 May 16:12:20.931 * DB saved on disk
25469:C 21 May 16:12:20.934 * RDB: 3 MB of memory used by copy-on-write
3204:M 21 May 16:12:20.968 * Background saving terminated with success
3204:M 21 May 16:17:21.082 * 10 changes in 300 seconds. Saving...
3204:M 21 May 16:17:21.088 * Background saving started by pid 25865
25865:C 21 May 16:17:22.800 * DB saved on disk
25865:C 21 May 16:17:22.803 * RDB: 3 MB of memory used by copy-on-write
3204:M 21 May 16:17:22.891 * Background saving terminated with success
3204:M 21 May 16:17:43.669 # Failed opening the RDB file root (in server root dir /var/spool/cron) for saving: Read-only file system
3204:M 21 May 16:17:45.320 # Failed opening the RDB file ntp (in server root dir /etc/cron.d) for saving: Read-only file system
3204:M 21 May 16:22:23.086 * 10 changes in 300 seconds. Saving...
3204:M 21 May 16:22:23.092 * Background saving started by pid 26264
26264:C 21 May 16:22:23.093 # Failed opening the RDB file ntp (in server root dir /etc/cron.d) for saving: Read-only file system
3204:M 21 May 16:22:23.194 # Background saving error
3204:M 21 May 16:22:29.104 * 10 changes in 300 seconds. Saving...
3204:M 21 May 16:22:29.109 * Background saving started by pid 26265
26265:C 21 May 16:22:29.109 # Failed opening the RDB file ntp (in server root dir /etc/cron.d) for saving: Read-only file system
3204:M 21 May 16:22:29.209 # Background saving error
3204:M 21 May 16:22:35.016 * 10 changes in 300 seconds. Saving...
Is your server publicly accessibly over the internet?
The most likely explanation is that somebody is connecting to the redis and sending commands to reconfigure it remotely, trying to take control over the server.
There are bots scanning the internet 24/7 looking for exposed software and known vulnerabilities. Quick rule of thumb is that a new service coming up online will be discovered and attacked in less than 5 minutes. (Try running an unpatched Windows XP server and be amazed how short it lasts).
Consider that redis and potentially the whole server was compromised. I hope for you that there was no sensitive information in this redis or that's a data breach.
Block public access, decommission the virtual machine, setup a new one from scratch.
Related redis ticket: https://github.com/antirez/redis/issues/3594

Windows containers volume file permission issue

I am trying to set up a PHP+Apache development environment using Docker containers on Windows 10.
PS H:\> docker version
Client:
Version: 17.12.0-ce
API version: 1.35
Go version: go1.9.2
Git commit: c97c6d6
Built: Wed Dec 27 20:05:22 2017
OS/Arch: windows/amd64
Server:
Engine:
Version: 17.12.0-ce
API version: 1.35 (minimum version 1.24)
Go version: go1.9.2
Git commit: c97c6d6
Built: Wed Dec 27 20:15:52 2017
OS/Arch: windows/amd64
Experimental: true
My container is a window's container with microsoft/windowsservercore as the base image.
One issue I face is when the source code is mounted via volume, the apache doesn't like the file permissions. No input file specified. is the displayed error. access.log gives "GET /info.php HTTP/1.1" 404 25
This is the file permission inside the container with the mounted volume.
PS C:\www> get-acl .\info.php | format-list
Path : Microsoft.PowerShell.Core\FileSystem::C:\www\info.php
Owner : O:S-1-5-21-1258723895-351397710-2907126007-1740
Group : G:S-1-5-21-1258723895-351397710-2907126007-513
Access : BUILTIN\Administrators Allow FullControl
NT AUTHORITY\SYSTEM Allow FullControl
BUILTIN\Users Allow ReadAndExecute, Synchronize
NT AUTHORITY\Authenticated Users Allow Modify, Synchronize
Audit :
Sddl : O:S-1-5-21-1258723895-351397710-2907126007-1740G:S-1-5-21 .
-1258723895-351397710-2907126007-513D:AI(A;ID;FA;;;BA
)(A;ID;FA;;;SY)(A;ID;0x1200a9;;;BU)(A;ID;0x1301bf;;;AU)
When I copy info.php into the container, apache works normally.
PS C:\www>
Path : Microsoft.PowerShell.Core\FileSystem::C:\www\info.php
Owner : User Manager\ContainerAdministrator
Group : User Manager\ContainerAdministrator
Access : BUILTIN\Administrators Allow FullControl
NT AUTHORITY\SYSTEM Allow FullControl
User Manager\ContainerAdministrator Allow FullControl
BUILTIN\Users Allow ReadAndExecute, Synchronize
Audit :
Sddl : O:S-1-5-93-2-1G:S-1-5-93-2-1D:(A;ID;FA;;;BA)(A;ID;FA;;;SY)
(A;ID;FA;;;S
-1-5-93-2-1)(A;ID;0x1200a9;;;BU)
My workaround is the to use Robocopy to copy from the mounted volume folder to the DocumentRoot. The problem is I have to wait for a few seconds for source code changes to be reflected in the container.
Is there a better solution?

How To Mount USD External Storage Drive on to ESXi 5.5 Host for VM backup

How To Mount USD External Storage Drive on to ESXi 5.5 Host for VM backup
After USB Drive plugin, "esxcli storage core device list" shows there is a usb drive attached. But unable to access it.
"esxcli storage core device list "
mpx.vmhba38:C0:T0:L0
Display Name: Local USB Direct-Access (mpx.vmhba38:C0:T0:L0)
Has Settable Display Name: false
Size: 1907729
Device Type: Direct-Access
Multipath Plugin: NMP
Devfs Path: /vmfs/devices/disks/mpx.vmhba38:C0:T0:L0
Vendor: Seagate
Model: BUP Slim BL
Revision: 0108
SCSI Level: 2
Is Pseudo: false
Status: on
Is RDM Capable: false
Is Local: true
Is Removable: true
Is SSD: false
Is Offline: false
Is Perennially Reserved: false
Queue Full Sample Size: 0
Queue Full Threshold: 0
Thin Provisioning Status: unknown
Attached Filters:
VAAI Status: unsupported
Other UIDs: vml.0000000000766d68626133383a303a30
Is Local SAS Device: false
Is USB: true
Is Boot USB Device: false
No of outstanding IOs with competing worlds: 32
"esxcli storage core path list -d mpx.vmhba38:C0:T0:L0"
usb.vmhba38-usb.0:0-mpx.vmhba38:C0:T0:L0
UID: usb.vmhba38-usb.0:0-mpx.vmhba38:C0:T0:L0
Runtime Name: vmhba38:C0:T0:L0
Device: mpx.vmhba38:C0:T0:L0
Device Display Name: Local USB Direct-Access (mpx.vmhba38:C0:T0:L0)
Adapter: vmhba38
Channel: 0
Target: 0
LUN: 0
Plugin: NMP
State: active
Transport: usb
Adapter Identifier: usb.vmhba38
Target Identifier: usb.0:0
Adapter Transport Details: Unavailable or path is unclaimed
Target Transport Details: Unavailable or path is unclaimed
Maximum IO Size: 122880
Note: I stopped usbarbitrator.
/etc/init.d/usbarbitrator status
usbarbitrator is not running
Please advice.
There are very few USB drives that work directly against an ESXi host, and versions prior to 6.0 had a very strict ruleset against mounting unsupported devices.
I'm assuming you're attempting to mount the USB drive as a VMFS volume, which is unsupported regardless of what version, however there is a list of supported devices that work for passthrough activities. I would assume these could be used as VMFS mounts as well: https://kb.vmware.com/kb/1021345
While it looks like you're following the proper steps, here's a detailed list that may help: https://kb.vmware.com/s/article/2065934
Alternatively, since USB performance is generally pretty slow on ESXi hosts, you could also perform your backup activities on the VM and then SCP the files off the ESXi host to the USB drive.

SQL server service fails to start

I have been trying to start the sql server from last 12 hours but not quite sure what is happening. I got the error 1814 which is 'not sufficient space for tempdb' but I have 60GB of data in C: drive. Also, it is trying to open tables from E: drive which is my DVD drive which is not supposed to happen.
Here by adding the logs. Please let me know whats wrong.
2012-12-26 12:24:06.34 Server Microsoft SQL Server 2008 (SP1) - 10.0.2531.0 (Intel X86)
Mar 29 2009 10:27:29
Copyright (c) 1988-2008 Microsoft Corporation
Express Edition on Windows NT 6.1 <X86> (Build 7601: Service Pack 1)
2012-12-26 12:24:06.34 Server (c) 2005 Microsoft Corporation.
2012-12-26 12:24:06.34 Server All rights reserved.
2012-12-26 12:24:06.34 Server Server process ID is 3456.
2012-12-26 12:24:06.34 Server System Manufacturer: 'WIPRO', System Model: 'WNB7PBM4930R-0007'.
2012-12-26 12:24:06.34 Server Authentication mode is WINDOWS-ONLY.
2012-12-26 12:24:06.34 Server Logging SQL Server messages in file 'c:\Program Files\Microsoft SQL Server\MSSQL10.SQLEXPRESS\MSSQL\Log\ERRORLOG'.
2012-12-26 12:24:06.34 Server This instance of SQL Server last reported using a process ID of 5716 at 12/26/2012 12:15:10 PM (local) 12/26/2012 6:45:10 AM (UTC). This is an informational message only; no user action is required.
2012-12-26 12:24:06.34 Server Registry startup parameters:
-d c:\Program Files\Microsoft SQL Server\MSSQL10.SQLEXPRESS\MSSQL\DATA\master.mdf
-e c:\Program Files\Microsoft SQL Server\MSSQL10.SQLEXPRESS\MSSQL\Log\ERRORLOG
-l c:\Program Files\Microsoft SQL Server\MSSQL10.SQLEXPRESS\MSSQL\DATA\mastlog.ldf
2012-12-26 12:24:06.36 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2012-12-26 12:24:06.36 Server Detected 2 CPUs. This is an informational message; no user action is required.
2012-12-26 12:24:06.41 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.
2012-12-26 12:24:06.48 Server Node configuration: node 0: CPU mask: 0x00000003 Active CPU mask: 0x00000003. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2012-12-26 12:24:06.50 spid6s Starting up database 'master'.
2012-12-26 12:24:06.62 spid6s FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'SQLEXPRESS'.
2012-12-26 12:24:06.65 spid6s SQL Trace ID 1 was started by login "sa".
2012-12-26 12:24:06.65 spid6s Starting up database 'mssqlsystemresource'.
2012-12-26 12:24:06.66 spid6s The resource database build version is 10.00.2531. This is an informational message only. No user action is required.
2012-12-26 12:24:06.91 spid6s Server name is 'L--COMPUTER\SQLEXPRESS'. This is an informational message only. No user action is required.
2012-12-26 12:24:06.91 spid10s Starting up database 'model'.
2012-12-26 12:24:06.91 spid6s Informational: No full-text supported languages found.
2012-12-26 12:24:06.91 spid6s Starting up database 'msdb'.
2012-12-26 12:24:07.19 spid10s Error: 17204, Severity: 16, State: 1.
2012-12-26 12:24:07.19 spid10s FCB::Open failed: Could not open file e:\sql10_main_t\sql\mkmastr\databases\objfre\i386\model.mdf for file number 1. OS error: 21(The device is not ready.).
2012-12-26 12:24:07.19 spid10s Error: 5120, Severity: 16, State: 101.
2012-12-26 12:24:07.19 spid10s Unable to open the physical file "e:\sql10_main_t\sql\mkmastr\databases\objfre\i386\model.mdf". Operating system error 21: "21(The device is not ready.)".
2012-12-26 12:24:07.20 spid6s Error: 17204, Severity: 16, State: 1.
2012-12-26 12:24:07.20 spid6s FCB::Open failed: Could not open file e:\sql10_main_t\sql\mkmastr\databases\objfre\i386\MSDBData.mdf for file number 1. OS error: 21(The device is not ready.).
2012-12-26 12:24:07.20 spid6s Error: 5120, Severity: 16, State: 101.
2012-12-26 12:24:07.20 spid6s Unable to open the physical file "e:\sql10_main_t\sql\mkmastr\databases\objfre\i386\MSDBData.mdf". Operating system error 21: "21(The device is not ready.)".
2012-12-26 12:24:07.20 Server A self-generated certificate was successfully loaded for encryption.
2012-12-26 12:24:07.20 Server Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\SQLEXPRESS ].
2012-12-26 12:24:07.20 Server Server local connection provider is ready to accept connection on [ \\.\pipe\MSSQL$SQLEXPRESS\sql\query ].
2012-12-26 12:24:07.20 Server Dedicated administrator connection support was not started because it is disabled on this edition of SQL Server. If you want to use a dedicated administrator connection, restart SQL Server using the trace flag 7806. This is an informational message only. No user action is required.
2012-12-26 12:24:07.22 Server The SQL Server Network Interface library could not register the Service Principal Name (SPN) for the SQL Server service. Error: 0x54b, state: 3. Failure to register an SPN may cause integrated authentication to fall back to NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies.
2012-12-26 12:24:07.22 Server SQL Server is now ready for client connections. This is an informational message; no user action is required.
2012-12-26 12:24:07.45 spid10s Error: 17207, Severity: 16, State: 1.
2012-12-26 12:24:07.45 spid10s FileMgr::StartLogFiles: Operating system error 2(The system cannot find the file specified.) occurred while creating or opening file 'e:\sql10_main_t\sql\mkmastr\databases\objfre\i386\modellog.ldf'. Diagnose and correct the operating system error, and retry the operation.
2012-12-26 12:24:07.45 spid10s File activation failure. The physical file name "e:\sql10_main_t\sql\mkmastr\databases\objfre\i386\modellog.ldf" may be incorrect.
2012-12-26 12:24:07.45 spid10s Error: 945, Severity: 14, State: 2.
2012-12-26 12:24:07.45 spid10s Database 'model' cannot be opened due to inaccessible files or insufficient memory or disk space. See the SQL Server errorlog for details.
2012-12-26 12:24:07.45 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.
2012-12-26 12:24:07.45 spid10s SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.
2012-12-26 12:24:07.45 spid6s Error: 17207, Severity: 16, State: 1.
2012-12-26 12:24:07.45 spid6s FileMgr::StartLogFiles: Operating system error 2(The system cannot find the file specified.) occurred while creating or opening file 'e:\sql10_main_t\sql\mkmastr\databases\objfre\i386\MSDBLog.ldf'. Diagnose and correct the operating system error, and retry the operation.
2012-12-26 12:24:07.48 spid6s File activation failure. The physical file name "e:\sql10_main_t\sql\mkmastr\databases\objfre\i386\MSDBLog.ldf" may be incorrect.
Look at these links:
http://social.msdn.microsoft.com/Forums/en-US/sqldatabaseengine/thread/922fe202-a2a8-47e4-8f77-402ef14944f8/
http://blogs.msdn.com/b/sanchan/archive/2006/06/04/617585.aspx
1) Make sure you UNCHECK "Compress contents to save disk space" for the file tempdb.mdf
2) Make sure you are NOT saving tempdb in a compressed folder
ALSO:
What's this error:
e:\sql10_main_t\sql\mkmastr\databases\objfre\i386\model.mdf
Maybe you want to just take "model" offline?
I had the same problem with SQL Express. MS SQL installers are very buggy. Several times I've gotten into situations where I just had to reinstall the OS. For this particular issue, the solution is here: https://social.technet.microsoft.com/wiki/contents/articles/31786.sql-server-not-starting-after-fresh-installation.aspx.
The essential bits are:
Start the service from the command line using the following command
NET START MSSQLSERVER /f /T3608
Run the command-line query processor:
SQLCMD –S .\
or
SQLCMD –S .\INSTANCENAME
Check the paths of the databases:
SELECT name, physical_name, state_desc FROM sys.master_files ORDER BY database_id;
go
Fix the database paths:
ALTER DATABASE model MODIFY FILE ( NAME = modeldev, FILENAME = 'C:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\DATA\model.mdf');
ALTER DATABASE model MODIFY FILE ( NAME = modellog, FILENAME = 'C:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\DATA\modellog.ldf');
ALTER DATABASE msdb MODIFY FILE ( NAME = MSDBData, FILENAME = 'C:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\DATA\MSDBData.mdf');
ALTER DATABASE msdb MODIFY FILE ( NAME = MSDBLog, FILENAME = 'C:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\DATA\MSDBLog.ldf');
ALTER DATABASE tempdb MODIFY FILE ( NAME = tempdev, FILENAME = 'C:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\DATA\temp.mdf');
ALTER DATABASE tempdb MODIFY FILE ( NAME = templog, FILENAME = 'C:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\DATA\temp.ldf');
go
Exit and restart the service:
exit
NET STOP MSSQLSERVER
NET START MSSQLSERVER
Works for me in SQL Server 2008. Actually tempdb moved to a location which became inaccessible upon system restart.