SETI for BOINC latest technical news...

[Rattledagger]

From Technical News:

January 10, 2005 - 20:00 UTC
Because of nearby building construction there was an extended power outage last night, during which all of our machines were turned off. Everything powered back up normally, except for one drive in the master science database, which failed upon booting up. Assimilating/splitting is turned off until we can figure out how to recover.

 

[SirUlli]

another Update

UPDATE: we were able to rescue the drive by replacing its circuit board (we figured the disks were good and had circuit boards fry in the past). However, there was slight data corruption in one of the pages on this disk, and therefore the database won't cleanly start. This is probably easy to fix, but we're waiting to hear back from the experts first.

http://setiweb.ssl.berkeley.edu/tech_news.php

Sir Ulli

 

[Rattledagger]

FURTHER UPDATE: the disk has been completely recovered and we're checking database integrity now. Assimilating and splitting will start up again by tomorrow morning.

 

[Doc Brown]

Thanks RD and SirUlli

for all the info on your progress ... glad that it was found now rather than later ... now that give you good reason to create another back-up of the back-up before the back-up is destroyed ...

M<ark ...



😀

 

[Dalephi]

Thanks Rattledagger and SirUlli!!!

 

[JWMiddleton]

Thanks guys!

 

[Rattledagger]

January 11, 2005 - 20:00 UTC
Update on yesterday's disk failure: the database integrity has been checked, and the remaining off-line servers are now being started. For the record, these disk arrays were not only powered down, but unplugged from the wall during the outage. We've had disks (and monitors) die before that were on the edge of failure that finally died during a very clean power cycle. As well, this disk array happens to be completely non-RAIDed. We are firmly aware this is not optimal, and are very actively working towards replacing the array with bigger, RAIDed storage. We would have fallen back to a tape backup if yesterday's disk repair didn't work, and would have only lost scientific results. These are reproducible - just resplit missing tapes and resend work. Yes, there is a net loss of CPU processing, but users would still have the credit for the work completed since the last backup.