From owner-freebsd-questions Wed Apr 29 13:52:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA25953 for freebsd-questions-outgoing; Wed, 29 Apr 1998 13:52:57 -0700 (PDT) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from gdi.uoregon.edu (gdi.uoregon.edu [128.223.170.30]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA25914 for ; Wed, 29 Apr 1998 13:52:41 -0700 (PDT) (envelope-from dwhite@gdi.uoregon.edu) Received: from localhost (dwhite@localhost) by gdi.uoregon.edu (8.8.7/8.8.8) with SMTP id NAA13227; Wed, 29 Apr 1998 13:51:52 -0700 (PDT) (envelope-from dwhite@gdi.uoregon.edu) Date: Wed, 29 Apr 1998 13:51:52 -0700 (PDT) From: Doug White Reply-To: Doug White To: Andrew McNaughton cc: Josh , freebsd-questions@FreeBSD.ORG Subject: RE: AAARGH! failure to boot. In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 24 Apr 1998, Andrew McNaughton wrote: > --------------------------------------- > Fixit# fsck -n /mnt2/dev/wd0s3 > ** ?mnt2/dev/rwd0s3 (NO WRITE) > > CANNOT READ: BLK 16 > CONTINUE? yes > > THE FOLLOWING DISK SECTORS COULD NOT BE READ: 16, 17, 18, 19, 20, 21, 22, > 23, 24 > , 25, 26, 27, 28, 29, 30, 31, That is really suspicious. I suspect something overwrote the front end of your drive, or you have a big gouge in the disk surface :( You might as well try -y, and run it several times. If it's truly dead then a reformat will prove it. Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message