I also found this in my archive :

-- DBCC rebuild_log (dbname [, filename])

-- -- -- -- Create new database with same name, stop SQL Server, replace the MDF file from original database file

-- -- -- -- and restart SQL Server to see whether your database is back in suspect mode.

-- -- -- -- If it does, reset the database to emergency mode and run DBCC Rebuild_Log to recreate the log file.

-- -- -- -- Once database is back to normal, run DBCC checkdb to ensure there is no integrity error,

-- -- -- --  otherwise, you have to BCP the data out.

-- -- --

Allen Cui http://www.sqlservercentral.com did an article on this "Undocumented DBCC Command REBUILD_LOG"