Turns out that the embedded controller is defective. HPE has a tech arriving today to replace the defective part.

@Obsolesce said in UREs Strike InnoDB on MySQL:

@scottalanmiller said in UREs Strike InnoDB on MySQL:

@Pete-S said in UREs Strike InnoDB on MySQL:

Step one is to remove the drives and clone them with dd or recovery tool to a new drive.
You could probably recover 99.9% of the data - if you want.

As you can guess from all of their previous issues, they don't want to pay for any recovery, they just want it magically fixed for free. They don't own any storage onto which to clone it, either.

Then what is the point of any of it? It appears to have zero value to the business.

I said that to them.

@scottalanmiller said:

This means that resilvers expected to fail when we look at the math model that only gives has an average (mean) failure rate we get successful resilver after success resilver. This also means that array expansion operations (replacing one drive at a time with a larger drive) would also be far more likely to be successful than expected based solely on the math averages.

And that's how my boss got away with it heheh (well so far)

If you combine the drive failure rate calculator for RAID 0 with the URE Risk of the RAID 5 calculator you can actually get some decent idea of total risk.

http://www.raid-failure.com/raid0-failure.aspx