We had a SQL Server 2005 x64 Enterprise SP2 attached to an MSA 1500 SAN with the HA kit. The backplane experienced problems and messed up the MBR on the two volumes where the data and log files reside. The database shutdown unclean and it took a while to get the SAN backup and moving. We fixed the MBR's and the data is there (both ldf and mdf). However, the logfile is corrupt and the database is stuck in recovery mode. You can't attach the database and if you trick it (by creating a new database then repointing it to the existing log and datafiles) the database loads but is inaccessible. It is not marked as suspect, emergency or repair, it's just there and you can't enumerate it in SQL Server Management studio. I spent quite a bit of time with MS PSS trying to rebuild the log file and then finally trying to do a emergency mode repair, but to no avail. When I put the DB in emergency mode, sys.databases still shows it as in recovery mode.
Any ideas? The data is there, and I'm ok with consistency issues as I can rectify them with the repair_allow_data_loss option if I can ever get access to the DB.
Start Free Trial
