The same thing has happened to us on a number of our databases.  Some of them have been repaired by running dbcc checkdb with the repair_allow_data_Loss but others have had...