In that case, I'd try restoring from the last good full backup and roll the logs forward.

Preferably to a different location (incidentally, have you checked the SQL Server and system logs on that box for IO related errors (esp SQL Server 823, 824 and 825 errors)).

Restore the backup with norecovery, than apply the logs

then run a DBCC CheckDB on the restored database. If it's Ok, take it from there. If the logs are backed up to the same spindles as the database there's a possibility that they're knackered too.

Finally, I would recommend always setting up alerts on errors 17-25 and events 823, 825 and 824 so you get early warning of issues like this.

HTH