I've crossposted this one into the SCO Unix newsgroup, where you're
more likely to find SCO Unix expertise.
$I have an old 386 based server running SCO 3.2v5.0.5 and an Old Foxpro
$for Unix application.
$
$The power company shutoff the power to the building without warning us
$adequately, to do re-wiring in the area.
$The server, although on a battery backup, eventually just lost power.
Uh-oh ... no UPS monitoring. If your UPS supports that, and if
there's a UPS monitoring program available for SCO Unix that supports
your UPS model, it would be a Good Idea to install it once you've
resurrected the server.
$When power was restored and we re-booted the server I got some bad
$ERROR in Fixed Disk (Minor 4)
$Blkno-244, cmd-0002, Status=0004, sector-16553, Cyl Head 1/7, Boot not
$found
$Cannot open
$Stage 1 boot failure
$Error Loading HD(40)/boot
$
$Is there any chance we can get around this problem at least briefly?
To get this far, the partition table, plus several sectors near
the start of the Unix partition, are all OK, but you have some damage
within one of the filesystems (the boot filesystem, assuming you're
running in a default configuration with separate boot and root
filesystems). I'm not 100% sure, but it looks like it's not in
the /boot program itself, but rather in something that needs to
exist in order for /boot to be located (the root directory or
the inode table or something like that).
If that's the only thing that's damaged, you can boot using your
emergency boot/root diskettes and get access to the data. It would
even be possible to use your emergency diskettes to load the boot
code and the kernel off the diskettes, then use the hard drive for
your root filesystem, but I'd need a bit more info about how your
system is configured in order to give you the details on that (the
contents of /etc/default/boot on the hard drive's root filesystem
should give enough info for that).
I wouldn't be surprised if other things were damaged, too, but
you'll find out soon enough. If any of your hard drive filesystems
won't mount, try mounting them read-only; damaged filesystems
will sometimes mount read-only but not read-write.
Good luck!
--
Quote:>>>----------------> http://www.stevedunn.ca/ <----------------<<<
------------------------------------------------------------------
Say hi to my cat -- http://www.stevedunn.ca/photos/toby/
by