From owner-freebsd-hackers Thu Jun 8 02:05:30 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id CAA04657 for hackers-outgoing; Thu, 8 Jun 1995 02:05:30 -0700 Received: from vegemite.Stanford.EDU (2842@vegemite.Stanford.EDU [36.159.0.7]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id CAA04645 for ; Thu, 8 Jun 1995 02:05:23 -0700 Received: (hlew@localhost) by vegemite.Stanford.EDU (8.6.10/8.6.4) id CAA14514; Thu, 8 Jun 1995 02:05:15 -0700 Date: Thu, 8 Jun 1995 02:05:15 -0700 (PDT) From: Howard Lew To: Temptation cc: freebsd-hackers@freebsd.org Subject: Re: problem In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: hackers-owner@freebsd.org Precedence: bulk On Thu, 8 Jun 1995, Temptation wrote: > > I installed Freebsd on a machine thats never given me a problem in over a > year. it's the ASUS 486sp3 rev 1.2. Harddrive is Seagate 1gig, about 2/3 > months old, never a problem with it. > For the last week I've been installing a 500meg part of Freebsd alpha. > And there WAS a 500meg Dos part, that was full. I finally got all of > FreeBSD, X, and everything running great. Made new kernels etc.. > Yesterday I installed ALL of packages. I ftped them to my Linux server, > which NFS them to FreeBSD machine, install worked great (pkg_manager), I > used ./sysinstall packages, had a nice menuing system. > When I was done, I played with X a little, downed the machine, cntrl > alt-del, it reset, I turned it off. Today I turn it on, and all part. > are gone. Both Dos and FreeBSD say the drive is empty. I've been around > along time, and I know parts get corrupted etc... but the drive is bare > as if I just bought it. I did a low-level check on the drive, not one > error. > ( stupid part is I have many tapedrives, and I never backup my Dos part., > so all my work is gone.) > Does it now say something like invalid disk media for drive c in dos? If so, then you had a problem similar to mine with 2.0.5A. Did your Seagate hard disk require a special boot manager (ie. On Track Disk Manager with Dynamic Drive Overlay)? If so, the boot code probably got wiped. The DOS stuff is probably still be on your hard disk though. On Track DM had a program to reinstall the boot code (non-destructively available in manual mode) on mine, so I was able to fix the boot problem and get all the data back on my dos partition. /--------------------------------------\ / Howard Lew \ < Email: hlew@genome.stanford.edu > \ http://www.shoppersnet.com / \--------------------------------------/