Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!munnari.OZ.AU!spool.mu.edu!howland.erols.net!newsfeed.internetmci.com!news.mathworks.com!fu-berlin.de!informatik.tu-muenchen.de!news
From: hafner@suncog2.forwiss.tu-muenchen.de (Walter 'madhouse' Hafner)
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Urgent! Nuked partition tables with booteasy
Date: 27 Aug 1996 16:05:48 GMT
Organization: Technische Universitaet Muenchen, Germany
Lines: 57
Distribution: world
Message-ID: <HAFNER.96Aug27180552@suncog2.forwiss.tu-muenchen.de>
NNTP-Posting-Host: suncog2.forwiss.tu-muenchen.de
Urgent!
=======
First of all: I already installed several Versions of FreeBSD, starting
from 2.0 to 2.1.5 on several computers. On disks dedicated for FreeBSD,
on shared disks with DOS, with NT, with OS/2, I installed from FTP, from
CDROM ... you name it. And I NEVER had any trouble up to now. But half
an hour our ago the shit really hit the fan ...
Short:
I just put a second disk in a PC running NT, installed FreeBSD 2.1.5 on
it and nuked the NT partition tables. What can I do?
Longer:
Pentium 133, 48 MB, Asus Board.
Vendor String:
Award Bios 4.50PG
Version MD2.00.02P * ASUS P55TP4XE
SCSI Controller: Adaptec AHA 2940 BIOS v 1.21
Disks: Micropolis 4221-09 1128R4AV (2 GB, Windows NT 3.51, NTFS, ID #0)
Plextor CD-ROM (ID #2)
Quantum XP 32150 (2 GB, empty, ID #3)
I installed 2.1.5 from CD to the Quantum drive. All went ok. I told
sysinstall to write the boot manager. And as far as I know
_I_didn't_touch_the_Mircopolis_at_all_.
Still, when I rebooted, the boot menu just gave me (F5). When I pressed
F5, the menu responded with (F1) (F5). When I pressed F1 it gave me
(F5) again ...
Using the 2.1.5 boot disk I could boot FreeBSD without trouble, typing
sd(1,a)kernel.
When I booted from a plain DOS disk, fdisk told me that the Quantum had
a non-DOS partition on it and the Micropolis was EMPTY (There SHOULD
have been 3 NTFS partitions on it)!
Well ... the NT disk was an experimental platform and thus wasn't
backuped like our other disks. Still, there was about 2 months of work
on it! Is there any chance to revive the partition tables?
I remember a similar error in 2.1, when installing on a second disk and
NOT writing the boot manager. Could this be a similar effect? Or could
it be the fault of the SCSI BIOS?
Any answers are greatly appreciated!
-Walter
--
Walter Hafner____________________________ hafner@forwiss.tu-muenchen.de
FORWISS Muenchen, FG Kognitive Systeme, Raum O-134, Tel: 089/48095-220
Frueher war alles Wiese ...
<A href=http://www.forwiss.tu-muenchen.de/~hafner/>*CLICK*</A>