From owner-freebsd-current Thu May 21 17:47:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA14371 for freebsd-current-outgoing; Thu, 21 May 1998 17:47:00 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles145.castles.com [208.214.165.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA14233 for ; Thu, 21 May 1998 17:46:22 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id QAA05515; Thu, 21 May 1998 16:42:16 -0700 (PDT) Message-Id: <199805212342.QAA05515@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Wes Peters cc: freebsd-current@FreeBSD.ORG Subject: Re: Weird disk problems, need help. In-reply-to: Your message of "Thu, 21 May 1998 09:46:27 MDT." <35644C53.8AE81EF2@softweyr.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 21 May 1998 16:42:16 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Tuesday night I installed the newest TTCP patch and built a new kernel. > Something must have happened to my disk before I rebooted with this > kernel; when the system came back up a number of files had been changed > to random device inodes and none of the 3 slices would fsck cleanly. > Since then, whenever I try to boot a new kernel, I get the following > messages: > > /dev/sd0s1a on /: specified device does not match mounted device > Filesystem mount failed, startup aborted. > > Then I end up in single-user mode. The part that is really confusing > is that I can boot the 2.2.6 kernel.GENERIC with no problem; I using > it right now. > > I re-installed the ssys package from the 2.2.6 CD-ROM and recompiled my > kernel just to be sure I hadn't corrupted a source file, and I've > searched the entire system for wayward device files, to no avail. The > boot still fails in the same manner. > > WTF? Any help, or should I just clean the system and start over? Check you don't have "on generic" on the 'kernel' line in your config. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message