Sep 08, 2007
Rosetta@home has experienced a horrendous hardware/fireware failure. We essentially lost the SAN partition upon which the project was running! The newest edition of our SAN hardware was shipped with a firmware revision that contained an insidious bug - one which caused the new SAN disks to vanish after roughly 45 days of service. We - or rather I (KEL) - apologize for the inconveinence, lost time and lost effort that you have endured during our outage. We know full well that your contribution hinges on the understanding that we make maximum use of your valuable resources - that we not waste your time, CPU cylces or good humor. We are planning to express our disappointment to our vendors in clear terms, specifically siting the importance of this project to our research effort. We'll keep you abreast of the outcome.
You People at the Project have been doing one heck of a GREAT JOB! We will see you when we see you.
e já agora:
As almost all of you know, we had the largest computer failure in the history of Rosetta@Home last Tuesday. Not only were we unable to make use of your valuable contributions, but also all of our internal computers were down as well, so the graduate students and postdoctoral fellows in my research group have had their resaearch projects stalled out. Quite a disaster! Fortunately, Keith and Chance, the computer gurus who keep Rosetta@Home and the group cmputer clusters running, are absolute pros, and they have worked miracles to get the project back on line even with this catastrophic failure. (to give you an idea, whenever anybody at the UW wants to set up a computer cluster or has any question to do with large scale computing hardware, Keith and Chance are the people they go to to find the answer). From Keith's most recent email, it appears that things are not fully back to normal, but hopefully we will be running as strong as ever very soon. In fact, as I will post once we are back up to speed, we have a very pressing scientific challenge we will need all of your help on!
Mais uns dias e temos rosetta@home de volta, parece que o problema se deve a um bug no firmware do server.
Dá direito a reclamação...