As i stil got +- 1 day worth of work does this afect beta as well ?

Oh well if it goes it goes with a bang (someone find an 24 port Sata Controler)

Will it do any harm to leave the auto-update on Boinc running? It would be great to get work soon, my latest is ay 90% complete now.

--
How big is the array ????

--
How big is the array ????

24x500GB. (12TB of which about 8TB was active with 2TB of parity and 2TB of spares).

Just talked with Matt and Jeff. It looks like we'll have a replacement machine within a few days, but I can't give details just yet because things are still in process.

Eric

This was one of those days. Sometime in the early morning MySQL on sidious crashed and rebooted itself. It had minor indigestion and restarted on its own just fine. Eric had to restart the BOINC projects to clean the pipes.

But when I came in I found Eric dissecting our master database server, thumper. That's never a good sign. He and Jeff informed me that it lost the ability to see any of its internal drives. Tests throughout the day confirmed that diagnosis - there's something dead between the power supply and the disk controllers so the drives don't even spin up. Booting from a DVD and an "fdisk" shows nothing. This system has a "preliminary" motherboard, which is one of the reasons we got it for free, but it has no hardware support.

Meanwhile I went ahead with the usual database backup/compression while we figured out what the heck we're gonna do. We're pretty confident the data is intact and as long as some server somewhere can mount the 24 SATA drives the make up the database the SETI@home science data will be perfectly intact. Failing that, we can recover from tape but unfortunately we're at a bad point in the backup cycle so the most recent tape is a week old.

Since data loss is most likely not an issue, the upshot of thumper being down is that we can't run the splitters or the assimilators. I just restarted the scheduler, but we only had about 300,000 results to process. I checked again just now and it's already down to about 281,000. Brace yourselves for a long outage.

[Edit: things are looking better regarding previously mentioned inability to procure a replacement. In other words, we might get another server relatively quickly.]

- Matt

Matt,

I send you an email a couple of minutes ago about a server, can you read it and get back to me. my email is danmartinaz AT aol DOT com

http://setiathome.berkeley.edu/forum_thread.php?id=39206

--
How big is the array ????

24x500GB. (12TB of which about 8TB was active with 2TB of parity and 2TB of spares).

Just talked with Matt and Jeff. It looks like we'll have a replacement machine within a few days, but I can't give details just yet because things are still in process.

Eric

"I'm trying to maintain a shred of dignity in this world." - Me

Matt, this is my first post on the forums, just because as a long time seti contributor I've been caught up in the car crash.
Can't offer any hardware or any techie suggestions since I'm just an end user on various platforms - but can't help wondering what will happen to the work currently in progress on my linux box which has been delayed by almost a week because of a simple hardware failure (dead power supply - day job meant I couldn't sort it out until now). 'Cos this box isn't the fastest in the world it's going to be some time tomorrow morning before it attempts to report; do you think it's worth carrying on with it, or should I abort the task and wait until y'all are back up?
in other words if I let this box carry on number-crunching and reporting, what will happen to that report, assuming you're able to get things up and running again in the next week or so?

[btw because of *quite* a few hardware problems I've been contributing to this project from a win vista laptop for the past couple of weeks. I'm almost ashamed to admit it! but so it goes.
Windows Vista? I hate it already.]

JD

Matt, this is my first post on the forums, just because as a long time seti contributor I've been caught up in the car crash.
Can't offer any hardware or any techie suggestions since I'm just an end user on various platforms - but can't help wondering what will happen to the work currently in progress on my linux box which has been delayed by almost a week because of a simple hardware failure (dead power supply - day job meant I couldn't sort it out until now). 'Cos this box isn't the fastest in the world it's going to be some time tomorrow morning before it attempts to report; do you think it's worth carrying on with it, or should I abort the task and wait until y'all are back up?
in other words if I let this box carry on number-crunching and reporting, what will happen to that report, assuming you're able to get things up and running again in the next week or so?

[btw because of *quite* a few hardware problems I've been contributing to this project from a win vista laptop for the past couple of weeks. I'm almost ashamed to admit it! but so it goes.
Windows Vista? I hate it already.]

JD

When there is an outage like this, deadlines are generally extended, either "artifically" (by the project) or simply because everyone is "late" and the work pairs-up just fine when things start working.

As i stil got +- 1 day worth of work does this afect beta as well ?

Yep, beta will run out of work as well. I'll be getting a current status report from Matt and Jeff in 20 minutes.