Ok, make a backup right away. I find that disk errors usually come in
groups. If you have one error now, it may be 10 next week. You *may* be able
to recover the disk by reformatting but i wouldn't count on it.
PostgreSQL can't help you here.
On Thu, Sep 05, 2002 at 10:58:46AM +0200, w.hoffmann wrote:
> Yes, here the error message from kernel
>
> xconsole:
> hde:read_intr:status = 0x59{drive ready seek complete data request error
> hde: read_intr: rror 0x01{Addr Mark not found 3 LBAsect:78691376,
> sector=78337040
> end request:I/O error,dev 21:03 (hde), sector78337040
>
>
> ----- Original Message -----
> From: "Martijn van Oosterhout" <kleptog@svana.org>
> To: "w.hoffmann" <w.hoffmann@pointmarketing.de>
> Cc: <jc@mega-bucks.co.jp>; <pgsql-general@postgresql.org>
> Sent: Thursday, September 05, 2002 10:31 AM
> Subject: Re: [GENERAL] cannot read block 6438 Input/Ouput error
>
>
> > Sounds like a hardware error. Are you getting any error messages from your
> > kernel?
> >
> > On Thu, Sep 05, 2002 at 09:33:32AM +0200, w.hoffmann wrote:
> > > Hallo,
> > >
> > > I have a big problem. If i want to handle one table i always get an
> error
> > > "cannot read block 6438 input/output error", what can I do ?
> > >
> > > Thanks a lot
> > >
> > > hoffi
> >
> > --
> > Martijn van Oosterhout <kleptog@svana.org> http://svana.org/kleptog/
> > > There are 10 kinds of people in the world, those that can do binary
> > > arithmetic and those that can't.
>
--
Martijn van Oosterhout <kleptog@svana.org> http://svana.org/kleptog/
> There are 10 kinds of people in the world, those that can do binary
> arithmetic and those that can't.