| From: | Matt Sealey |
| Date: | 29 Aug 2000 at 20:23:20 |
| Subject: | Re: sick partition |
Hello John
On 29-Aug-00, you wrote:
> Hello Matt
>
> On 28-Aug-00, you wrote:
>
>> It's easy, set the partition to 'automount' first, and then boot with no
>> startup-sequence. Run a disk utility from there:
>
> Ta matt. tried that last night, but just before the world's slowest typist
> manages df0:disksalv a system requester `dh3 Program failed (error #80000004)
> wait for disk activity to finish Suspend Reboot' comes up and it's lockup
> even with suspend
Urg.. shit.. that's not a good sign.. and it can't be a stack problem..
.. how the hell can a disk process be crashing like that? Unless it's validating
and dies because of it. Hmm.. I'd type the following into a script to be put in
the root of your SYS: partition..
Lock DH3:
Format DRIVE DH3: NAME Empty FFS INTL NOICONS
Save it as something short, say 'bang', do a 'protect sys:bang +rweds' on it,
and then instead of typing df0:disksalv, type 'bang'.
You ain't gonna get data back off there, meladdy.
That said, you could set Disksalv up to search for partitions on a disk, see
if it can resurrect it without it being mounted. Version 4 can do it, I don't
know about what version you're using..
Thanks
Quote carefully and read all ADMIN:README mails