Hi,

It's a hardware problem with the disk drive.

eormally, HP would say "replace the drive, then reload".

If you push, you should be able to get them to help you by
connecting a replacement drive of the same size, (offline) cloning the
old drive to the new drive, and then detaching the bad drive
and booting up.   (There are several ways to clone a drive,
one using a free HP tool, one using <plug> De-Frag/X </plug>.)

Note that this will probably leave you with bad data in some sectors
of some files that were on ldev 4.  We know that the sectors 0x7A5FD0,
etc, are bad ... so after you come back up with the new disk (after the
clone), you'd want to determine which files are on the bad sectors,
and restore those files from the backup.  In this case, you know
the bad file is INVENT48.DATABASE.JOBSCOPE.

What you *don't* know is what other sectors might have had bad data
...
that's the argument in favor of a reload ... it doesn't risk getting
bad data from disk.

OTOH, with the clone mechanism, you get up and running faster ...
and you can then (somehow) build a list of all files that have any
parts on ldev 4 and restore *just* that list!  (Various tools/products
can assist in this.)

In general, I go with the "reload" approach, but I've had a few
sites where they couldn't afford the downtime and wanted to take
the risk with the cloning approach.

So, the answer to "best" is: it depends :)

> I just received the following error messages from a query serial read:
>
> >f invoice-number = " " and date-received ib 990604,990805
> USING SERIAL READ
>  Bad SYSTEM LOGICAL Sector number 0x7A5FD0 on ldev 4 (io_status=FFDD0071)
> Filename of bad file:/JOBSCOPE/DATABASE/INVENT48
>  Bad SYSTEM LOGICAL Sector number 0x7A5FD0 on ldev 4 (io_status=FFDD0071)
> Filename of bad file:/JOBSCOPE/DATABASE/INVENT48
>  Bad SYSTEM LOGICAL Sector number 0x7A5FE0 on ldev 4 (io_status=FFDD0071)
> Filename of bad file:/JOBSCOPE/DATABASE/INVENT48
>  Bad SYSTEM LOGICAL Sector number 0x7A5FF0 on ldev 4 (io_status=FFDD0071)
> Filename of bad file:/JOBSCOPE/DATABASE/INVENT48
...
>  Bad SYSTEM LOGICAL Sector number 0x7A6090 on ldev 4 (io_status=FFDD0071)
> Filename of bad file:/JOBSCOPE/DATABASE/INVENT48
> FREADDIR FAILURE 48 96
>
> Is this a bad drive?
> What is the "best" way to recover from this (other than a complete restore
> from last night's backup)?

--
Stan Sieler                                          [log in to unmask]
                                         http://www.allegro.com/sieler/