31 May
2000
31 May
'00
2:08 a.m.
Sounds like there might be a bad block in the FAT, or superblock, or
whatever OS/2 calls it. If bootcode or FAT information gets corrupt there
isn't a whole lot you can do about it. You could try hooking it up to a
linux machine and mount it read-only to get your files off. If the FAT is
corrupt the only way to get the drive back is a low level format.
----- Original Message -----
From: "Technoid Mutant" <Technoid(a)cheta.net>
To: <classiccmp(a)classiccmp.org>
Sent: Wednesday, May 31, 2000 6:50 AM
Subject: HPFS 386 HELP!
My warp4 machine ate it'self the other day. At
restart it runs checkdisk,
indicates that it has relocated information stored on a bad sector then
says
it cannot continue. After this the driver reports that
the disk is dirty
and
needs to be checked in order to function.
I pulled the drive and mounted it on another machine I have which is
running
an identical version and service level of warp 4. It
is also running
HPFS386. Checkdisk/F gives the same error as it does when I try to boot
the
disk on the machine it belongs to.
The drive passes diagnostics. I am running Linux from another partition
right
now (it was a dual-boot OS/2, Linux drive but OS/2
won't boot now....).
I've searched the web like crazy for more advanced tools which will work
on an
HPFS386 filesystem to no avail. Any help is
appreciated.
Thanks in advance
Jeff
(technoid(a)cheta.net)