NetNews Usenet Archive 1992 #18/NN_1992_18.iso/spool/comp/sys/hp/9406

Text File | 1992-08-18 | 1.5 KB | 40 lines

Newsgroups: comp.sys.hp
Path: sparky!uunet!cis.ohio-state.edu!zaphod.mps.ohio-state.edu!darwin.sura.net!mips!odin!fido!shankar
From: [e-mail] (Shankar Unni)
Subject: Re: Recovering from disk with bad blocks
Message-ID: <[e-mail]>
Sender: [e-mail] (Usenet News Admin)
Organization: Silicon Graphics, Inc.
References: <[e-mail]>
Date: Tue, 18 Aug 1992 20:41:31 GMT
Lines: 28

In article <[e-mail]> [e-mail] (Jeff Heisz) writes:

>The information on this disk is precious to the nth degree.  It is not
>backuped (of course, else why would I ask you this).

/*SALT_IN_WOUND*/
It's obviously not *that* precious, now, is it, if no one cared to
back the thing up?

First of all, try the following:

   dd if=<rawdevice> of=/dev/null bs=1024k

See if you get any errors. If you do, then some sectors/tracks of your
disk are damaged. This is generally bad news.

In any case, try answering "y" to a few of the queries. Sometimes,
fsck manages to fix a things up somewhat. In that case, mount the file
system *READ-ONLY* and *BACK IT UP IMMEDIATELY*.  Then unmount and
re-initialize the disk (maybe using mediainit(1M) and/or scsictl(1M)).
Make a new file system on it, mount it, and recover the contents from
the tape.  Then walk around in it to see what's screwed up.

If you get a seemingly infinite number of errors and prompts from the
fsck, I can't think of anything offhand I can suggest to fix things up.
--
Shankar Unni                E-Mail:    [e-mail]
Silicon Graphics Inc.            Phone:    [phone]