Ok, a nightmare scenario: A partitioned database got wiped and then block-restored, it's now attached but wont go online since the log files are gone. Upon starting SQL service, the db went in suspect mode, so i put it in emergency & single_user and executed dbcc checkdb('dbname',repair_allow_data_loss). After a few seconds i get the result that there is not enough of database data to begin restoring the log. The database is again put in suspect-mode and i'm back where i started. Is the situation beyond all hope of repair? Biting nails here, any ideas?