Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

HELP! Resized disk SQL is installed on and now SQL won't start Expand / Collapse
Author
Message
Posted Tuesday, December 4, 2012 7:50 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Wednesday, January 9, 2013 5:32 AM
Points: 12, Visits: 17
HELP!

I know, should have had a backup. I have db backups. I wanted the system drive to be larger so I can deploy updates to the server (Server 2003, SQL 2005). I used gParted. Now the SQL service won't start. I know I fixed this in the past but can't find how to do it.

PLEASE HELP! Essential services are down (my fault).
Post #1392501
Posted Tuesday, December 4, 2012 8:37 AM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Today @ 11:52 AM
Points: 42,480, Visits: 35,549
Find the SQL error log. What errors does it list at the end?


Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #1392549
Posted Tuesday, December 4, 2012 8:59 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Wednesday, January 9, 2013 5:32 AM
Points: 12, Visits: 17
See below. Yes I know it says SQL express that's what's throwing me. Full SQL 2005 is installed. This is in a VM.
2012-12-04 10:28:24.28 Server Microsoft SQL Server 2005 - 9.00.4035.00 (Intel X86)
Nov 24 2008 13:01:59
Copyright (c) 1988-2005 Microsoft Corporation
Express Edition on Windows NT 5.2 (Build 3790: Service Pack 2)

2012-12-04 10:28:24.28 Server (c) 2005 Microsoft Corporation.
2012-12-04 10:28:24.28 Server All rights reserved.
2012-12-04 10:28:24.28 Server Server process ID is 1392.
2012-12-04 10:28:24.28 Server Authentication mode is WINDOWS-ONLY.
2012-12-04 10:28:24.28 Server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL.3\MSSQL\LOG\ERRORLOG'.
2012-12-04 10:28:24.28 Server This instance of SQL Server last reported using a process ID of 1376 at 12/4/2012 9:39:31 AM (local) 12/4/2012 2:39:31 PM (UTC). This is an informational message only; no user action is required.
2012-12-04 10:28:24.28 Server Registry startup parameters:
2012-12-04 10:28:24.28 Server -d C:\Program Files\Microsoft SQL Server\MSSQL.3\MSSQL\DATA\master.mdf
2012-12-04 10:28:24.28 Server -e C:\Program Files\Microsoft SQL Server\MSSQL.3\MSSQL\LOG\ERRORLOG
2012-12-04 10:28:24.28 Server -l C:\Program Files\Microsoft SQL Server\MSSQL.3\MSSQL\DATA\mastlog.ldf
2012-12-04 10:28:24.29 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2012-12-04 10:28:24.29 Server Detected 1 CPUs. This is an informational message; no user action is required.
2012-12-04 10:28:24.39 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-04 10:28:24.46 Server Database mirroring has been enabled on this instance of SQL Server.
2012-12-04 10:28:24.52 spid5s Starting up database 'master'.
2012-12-04 10:28:24.59 spid5s Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
2012-12-04 10:28:24.67 spid5s SQL Trace ID 1 was started by login "sa".
2012-12-04 10:28:24.69 spid5s Starting up database 'mssqlsystemresource'.
2012-12-04 10:28:24.70 spid5s The resource database build version is 9.00.4035. This is an informational message only. No user action is required.
2012-12-04 10:28:25.09 Server A self-generated certificate was successfully loaded for encryption.
2012-12-04 10:28:25.09 Server Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\SQLEXPRESS ].
2012-12-04 10:28:25.09 Server Server local connection provider is ready to accept connection on [ \\.\pipe\MSSQL$SQLEXPRESS\sql\query ].
2012-12-04 10:28:25.09 spid5s Server name is 'ABSDSVRVIRT01\SQLEXPRESS'. This is an informational message only. No user action is required.
2012-12-04 10:28:25.09 spid8s Starting up database 'model'.
2012-12-04 10:28:25.09 Server Dedicated administrator connection support was not started because it is not available on this edition of SQL Server. This is an informational message only. No user action is required.
2012-12-04 10:28:25.09 Server SQL Server is now ready for client connections. This is an informational message; no user action is required.
2012-12-04 10:28:25.09 spid5s Starting up database 'msdb'.
2012-12-04 10:28:25.25 spid8s Clearing tempdb database.
2012-12-04 10:28:25.36 spid8s Starting up database 'tempdb'.
2012-12-04 10:28:25.38 spid5s Recovery is complete. This is an informational message only. No user action is required.
2012-12-04 10:28:25.38 spid11s The Service Broker protocol transport is disabled or not configured.
2012-12-04 10:28:25.38 spid11s The Database Mirroring protocol transport is disabled or not configured.
2012-12-04 10:28:25.38 spid11s Service Broker manager has started.
Post #1392558
Posted Tuesday, December 4, 2012 9:04 AM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Today @ 11:52 AM
Points: 42,480, Visits: 35,549
That one's running fine.
If you have another SQL instance that isn't running/won't start, find the error log from that instance (check the startup parameters in SQL config manager to see where it's error log can be found)



Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #1392562
Posted Tuesday, December 4, 2012 9:26 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Wednesday, January 9, 2013 5:32 AM
Points: 12, Visits: 17
Well I found the problem. With the help of the SQL Configuraion Manager I noted my SQL was on my 'D' drive. I knew I had a larger 135gb partition but it didn't "click" with me that I was only seeing a 'C' drive in Computer Management. Finally realized after altering the drives Windows dropped the drive letter for the 'D' drive. Added the drive letter and all is working.

Thanks. Wondered why I did not see a different ERRORLOG. Sigh. Never again.
Post #1392574
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse