Just for reference, I came across this issue with one of our databases. In my case it was caused by changing the logical and filename for the .mdf and .ldf files, then restarting and another time upgrading SQL.

...for recovery pending that is.

Running a checkdb resolved the issue.