Date: Fri, 22 May 1998 12:43:04 -0700 From: Mike Smith <mike@smith.net.au> To: Terry Lambert <tlambert@primenet.com> Cc: wes@softweyr.com (Wes Peters), freebsd-current@FreeBSD.ORG Subject: Re: Weird disk problems, need help. Message-ID: <199805221943.MAA01503@dingo.cdrom.com> In-Reply-To: Your message of "Fri, 22 May 1998 18:56:31 -0000." <199805221856.LAA27748@usr02.primenet.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> > > > /dev/sd0s1a on /: specified device does not match mounted device > > > > Filesystem mount failed, startup aborted. > > > > > > A change went in that required the slice designator in the fstab, > > > and there was a corresponding change (can't rememebr when) to the > > > MAKEDEV. > > > > Nah, that was before the 2.2.6 release -- this system was upgraded > > the day I got the CD-ROM subscription. This just started Tuesday > > night, and the system still boots with kernel.GENERIC. I've checked > > my config and the only differences between it and GENERIC are devices > > that I don't have. I'm stumped. > > It's comparing the root device with the slice device, which isn't there. Wrong. The device 'sd0s1a' doesn't match the device that was mounted by the kernel as the initial root device. If the slice device wasn't there, you'd never got that far into the mount.a > I'll try to dig out the description of what to do from the -current > archives (from back when that was -current). > > It may want you to rewrite your boot blocks. 8-(. Also wrong. -- \\ 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?199805221943.MAA01503>