I have a message I e-mailed to Jay Burns describing the issues: [link|http://www.iwethey.org/error-502.html|the new 502 error doc]

As you can see, it wasn't fun again. It also tells me I need to order drives from various places.

And, to reiterate, the drives are already on the way to the Manufacturer for Warranty services.

edit: The 502 has been edited... sorry folks.

here it is anyway:

Jabber is up though. :-P

Yes it is persisting, since 17:43PM EDT (GMT -0400), September 14th, in the year of our Lard 2005. Both hard drives in the Mirror failed Yesterday. Pissing me off.

Drive on Port2 of the Raid controller shunted power on the bus for the drives to ground. Causing the drive on Port0 to not be able to function.

Once I removed the drive on Port2, and restarted, there was some striping corruption, for 2 small areas of disk. That was fixed, I added 2 more 300GB SATA-II drives (port1 and port3), kicked off a re-mirror with Port3 against the drive on Port0. When it completed, I manually failed the drive on Port0. Causing a degraded array again, then kicked off a remirror against Port3 with Port1.

Then once everything was "operational" hardware-wise... I couldn't get *Z* backup.

Admin and I are dealing with the data right now.

What the problem is, one of the transaction headers of a user for the "last active" updates is marked for the clog of it to be in a non-existant file with an offset that doesn't exist either.

Hope fully, we can fix the issue shortly, but we have to find it first.

And, yes the drives are already on the way to the manufacturer for Replacement.