Corrupted data, best course of repair?

Today I was charged with fixing a DB, and upon looking into it, I
discovered that there was gigs upon gigs of the errors from below.
Has anyone seen this or, more interesting to me, recovered from this
kind of a failure mode?

Here's a bit of background. The system is a good system with verified
disks/FS, etc., but it's a busy database and (here's what's bugging
me): it's using pg_autovacuum *AND* is a system that gets a power
cycle every few weeks[1]. I'm worried that a non-exclusive vacuum
during recovery is causing some kind of problem. The system was
running fine under 7.4.8 for months, but after an upgrade to 8,
they've been experiencing some "interesting characteristics" that led
them to resolve the system getting wedged by "readjusting a power cord
or toggling a power switch[1]." Any helpful advice? reindex? I
still have the original data files, but they're sizable (~30GB) and I
haven't had a chance to really experiment. A dump/reload has been
done and data is sporadically missing (less than 0.01%) or in some
cases, there are duplicate rows. I'm guessing this is due to data
that's been updated since some kind of index/corruption occurred
during the previous "reboot." fsync was off.

I'll be the first to admit, I've seen a bunch of PG errors, but this
one is new to me. -sc

[1] I'm not the hosting company and I wasn't involved in the
"power-cycle to fix the database" epidemic. I'm doing the
janitorial work to recover, please spare me the lecture.

Aug 21 15:04:32 db postgres[434]: [10-1] ERROR: xlog flush request 1A1/3F1C34FC is not satisfied --- flushed only to 1A1/3A20E26C
Aug 21 15:04:32 db postgres[434]: [10-2] CONTEXT: writing block 3415 of relation 1663/17236/70731682
Aug 21 15:04:32 db postgres[434]: [11-1] WARNING: could not write block 3415 of 1663/17236/70731682
Aug 21 15:04:32 db postgres[434]: [11-2] DETAIL: Multiple failures --- write error may be permanent.
Aug 21 15:04:32 db postgres[199]: [127-1] ERROR: xlog flush request 1A1/3B114118 is not satisfied --- flushed only to 1A1/3A20E26C
Aug 21 15:04:32 db postgres[199]: [127-2] CONTEXT: writing block 16096 of relation 1663/17236/29223136
Aug 21 15:04:32 db postgres[199]: [128-1] WARNING: could not write block 16096 of 1663/17236/29223136
Aug 21 15:04:32 db postgres[199]: [128-2] DETAIL: Multiple failures --- write error may be permanent.
Aug 21 15:04:32 db postgres[435]: [2-1] ERROR: xlog flush request 1A1/3F1C34FC is not satisfied --- flushed only to 1A1/3A20E26C
Aug 21 15:04:32 db postgres[435]: [2-2] CONTEXT: writing block 3415 of relation 1663/17236/70731682
Aug 21 15:04:32 db postgres[435]: [3-1] WARNING: could not write block 3415 of 1663/17236/70731682
Aug 21 15:04:32 db postgres[435]: [3-2] DETAIL: Multiple failures --- write error may be permanent.
Aug 21 15:04:32 db postgres[435]: [4-1] ERROR: xlog flush request 1A1/3F1C34FC is not satisfied --- flushed only to 1A1/3A20E26C
Aug 21 15:04:32 db postgres[435]: [4-2] CONTEXT: writing block 3415 of relation 1663/17236/70731682
Aug 21 15:04:32 db postgres[435]: [5-1] WARNING: could not write block 3415 of 1663/17236/70731682
Aug 21 15:04:32 db postgres[435]: [5-2] DETAIL: Multiple failures --- write error may be permanent.
Aug 21 15:04:32 db postgres[435]: [6-1] ERROR: xlog flush request 1A1/3F1C34FC is not satisfied --- flushed only to 1A1/3A20E26C
Aug 21 15:04:32 db postgres[435]: [6-2] CONTEXT: writing block 3415 of relation 1663/17236/70731682
Aug 21 15:04:32 db postgres[435]: [7-1] WARNING: could not write block 3415 of 1663/17236/70731682
Aug 21 15:04:32 db postgres[435]: [7-2] DETAIL: Multiple failures --- write error may be permanent.
Aug 21 15:04:33 db postgres[392]: [2-1] ERROR: out of memory
Aug 21 15:04:33 db postgres[392]: [2-2] DETAIL: Failed on request of size 20.
Aug 21 15:04:33 db postgres[199]: [129-1] ERROR: xlog flush request 1A1/3B114118 is not satisfied --- flushed only to 1A1/3A20E26C
Aug 21 15:04:33 db postgres[199]: [129-2] CONTEXT: writing block 16096 of relation 1663/17236/29223136
Aug 21 15:04:33 db postgres[199]: [130-1] WARNING: could not write block 16096 of 1663/17236/29223136
Aug 21 15:04:33 db postgres[199]: [130-2] DETAIL: Multiple failures --- write error may be permanent.
Aug 21 15:04:33 db postgres[392]: [3-1] ERROR: xlog flush request 1A1/3F1C34FC is not satisfied --- flushed only to 1A1/3A20E26C
Aug 21 15:04:33 db postgres[392]: [3-2] CONTEXT: writing block 3415 of relation 1663/17236/70731682
Aug 21 15:04:33 db postgres[392]: [4-1] WARNING: could not write block 3415 of 1663/17236/70731682
Aug 21 15:04:33 db postgres[392]: [4-2] DETAIL: Multiple failures --- write error may be permanent.

--
Sean Chittenden