Обсуждение: PostgreSQL 9.01 error database help

I am running PostgreSQL 9.01 on windows 2008, RAID 10 with 4 disk.
Yesterday, one of 4 disks RAID 10 error and I copy data directory to
USB.

Today, When I start postgresql i have error log

2011-05-24 17:20:01 ICT LOG:  database system was shut down at
2011-05-24 02:40:49 ICT
2011-05-24 17:20:01 ICT LOG:  unexpected pageaddr 1/A1F8E000 in log
file 1, segment 177, offset 16310272
2011-05-24 17:20:01 ICT LOG:  invalid primary checkpoint record
2011-05-24 17:20:01 ICT LOG:  invalid secondary checkpoint record
2011-05-24 17:20:01 ICT PANIC:  could not locate a valid checkpoint record


This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.

2011-05-24 17:20:01 ICT LOG:  startup process (PID 6252) exited with exit code 3
2011-05-24 17:20:01 ICT LOG:  aborting startup due to startup process failure

Is there any way to help me? Thanks you very much

Tuan Hoang Anh

tuanhoanganh <hatuan05@gmail.com> writes:
> I am running PostgreSQL 9.01 on windows 2008, RAID 10 with 4 disk.
> Yesterday, one of 4 disks RAID 10 error and I copy data directory to
> USB.

> Today, When I start postgresql i have error log

> 2011-05-24 17:20:01 ICT LOG:  database system was shut down at
> 2011-05-24 02:40:49 ICT
> 2011-05-24 17:20:01 ICT LOG:  unexpected pageaddr 1/A1F8E000 in log
> file 1, segment 177, offset 16310272
> 2011-05-24 17:20:01 ICT LOG:  invalid primary checkpoint record
> 2011-05-24 17:20:01 ICT LOG:  invalid secondary checkpoint record
> 2011-05-24 17:20:01 ICT PANIC:  could not locate a valid checkpoint record

It looks like the contents of pg_control are out of sync with what's in
pg_xlog/ ... are you sure you copied the *whole* data directory?

If this is all you have to work with, you can probably use pg_resetxlog
to wipe out the broken WAL data and then you'll be able to start the
database, but expect to find some amount of data corruption if you go
that way.  A dump and reload would probably be wise at that point.

            regards, tom lane