Big problem after moving master database
-
Hi, I've just moved the master database to a new disk. After that I changed the startup parameters to point to those new files. It worked perfectly, but at the time of changing those parameters in the failover server (it's clustered) using the command line I couldn't make it. So after several failovers something really weird happened: SQL Server says it can't find the master.mdf file... But what it is really strange: SQLServr.exe was completely corrupted in one of the servers (the one I changed first), being 0Kb long!!! Now I have both servers well configured (I made it with regedit) and I have tried to point back to the previous disk, but it says the same. I've looked also at the effective permissions for the service user, at the locks over the files, read only, etc... No result... I have a backup, but I don't know how to rebuild it since I can't start SQL Server even with -T3607
Hope someone can help me. Thanks in advance.
-
For clustered environment it is ok that you have done in the active instance alone as cluster is OS mirroring the change should have gone to the other server on sync propcess. now tell me what exactly is the problem. you can rebuild the master database using rebuild.exe
Cheers,
Sugeshkumar Rajendran
SQL Server MVP
http://sugeshkr.blogspot.com -
That sync didn't happen
I tried to rebuild the master database but it failed (I checked files weren't read-only, etc.).The error given is:
17113 :
initconfig: Error 2(The system cannot find the file specified.) opening 'master.mdf' for configuration information.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply