Date: Thu, 21 May 1998 16:42:16 -0700 From: Mike Smith <mike@smith.net.au> To: Wes Peters <wes@softweyr.com> Cc: freebsd-current@FreeBSD.ORG Subject: Re: Weird disk problems, need help. Message-ID: <199805212342.QAA05515@antipodes.cdrom.com> In-Reply-To: Your message of "Thu, 21 May 1998 09:46:27 MDT." <35644C53.8AE81EF2@softweyr.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199805212342.QAA05515>