Corrupt Transaction Log on database I have reason to believe the transaction log file on my database is corrupt. 

This database is involved in transaction based replication (both subscription and publishing), and I'm unable to start its log reader agent with an error message which cites "Operating System Error 23". 

I essentially just want to do what it takes to be able to restart the log reader agent, and my best idea so far is to somehow clear the log file, detach from it and reattach to a new log file. I'm not sure what the data loss implications of this would be though. Is this the best solution or is there a better way to deal with a corrupt log file? It is not a production database so avoiding data loss is not absolutely necessary (though preferable). There are no backups.
OS error 23 is "Data error (cyclic redundancy check)."
you can check those by running executing on the command prompt net helpmsg 23, this basically means that you have a serious error on your disk.

As the database is running what you need to to is to 


DONT PANIC
Find your backups 
Script your replication setup
Do a tail-of-the-log backup to have a restore point. 
Run DBCC CHECKDB with NO_INFOMSGS, ALL_ERRORMSGS and keep the output
Turn of the SQL Server and copy the data and log files to a safe place -if possible
Run CHKDSK on the log drive.
Restart the SQL Server and run DBCC CHECKDB again if it comes out clean you should be able to restart the replication if not you will have to restore the database.