So today was a usual day until the mid afternoon. Eric got a new RAID card (as well as a set of 8 750GB drives) to add to his server ewen, which is strictly a hydrogen survey machine. I helped him pluck the heavy machine from our server racks and place the new drives in trays, etc. The drive trays required unusually small screws, so Eric disappeared for a while hunting around the lab for such things.

Meanwhile, some SETI servers were locking on ewen being off the network. It's a tangled web of network dependencies around here, as you know. And then upon turning the machine on we had to wait a few hours for the thing to build a 4 terabyte RAID array before we could boot the OS and free the stranglehold it had on random machines.

This didn't affect the public projects - it just made it hard to get any work done. But the following was worse. So I'm gearing up to upgrade isaac (the boinc.berkeley.edu server) and was inspecting its empty drive slots when I noticed that gowron (not the download server, but the download *file* server) was rebooting. I must have accidentally grazed against the touch-sensitive power switch right on gowron's front as I was messing with isaac which is right above it in the rack. Well, dammit.

Normally, this would be no big deal, but upon coming back up kryten and penguin (the upload and download servers) weren't given permission to mount it. In short, I uncovered either a bug in gowron's OS or some newly broken configuration, or both. Attempts to set things right required reboots at each step, and one such reboot triggered an entire RAID resync, which normally takes all night (when the project is inactive - several weeks if the project *is* active).

So great. I went home dejected and hating my job. Eventually I checked back in and found the resync of the download partition actually completed, and even though other lesser-used partitions were far from done I found a way to somehow trick gowron into letting kryten and penguin mount its partitions, and voila! The project is back up. As I write this missive gowron is still resyncing and people are connecting and getting work just fine.

- Matt

Well, maybe we have to just write it off to a rig gone wild. I have had one of mine go off into the wild blue yonder and trash the whole cache before.

I'm not sure but I think the problem is the over clocking he is using. Looked at a couple of his results and didn't see that they were aborted, just failed to complete without errors. I hope fixes his OC problem or the selective trashing if that is the case.

It looks like the majority of them are Transfer Aborts with the odd User Abort thrown in just after the WU starts.

I was surfing through some stats and came across this host that seemed to be having problems. Then I figured out that it looks like the the User is selectively trashing WU's that are probably going to drag down his RAC.

Oooh the morality of it all.....

Host ID 2512275