Nope, that's just a login failure, not related at all.
We need all the errors that suggested to you that the file was corrupt. Honestly though, at this point just restore your latest backup and carry on. This database has been down for 2 days already, no reason to waste more time investigating fixes that might not work when you can restore a backup.
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)SQL In The Wild
: Discussions on DB performance with occasional diversions into recoverability
We walk in the dark places no others will enter
We stand on the bridge and no one may pass