Date: Thu, 6 Apr 2000 19:23:58 +0100 From: Mark Ovens <mark@ukug.uk.freebsd.org> To: Sean Noonan <snoonan@cx952600-a.fed1.sdca.home.com> Cc: questions@freebsd.org Subject: Re: prob going from 3.4-STABLE to 4.0-STABLE - bad sector table not supported Message-ID: <20000406192358.A236@parish> In-Reply-To: <Pine.BSF.4.21.0004060635500.68697-100000@cx952600-a.fed1.sdca.home.com>; from snoonan@cx952600-a.fed1.sdca.home.com on Thu, Apr 06, 2000 at 06:58:46AM -0700 References: <Pine.BSF.4.21.0004060635500.68697-100000@cx952600-a.fed1.sdca.home.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Apr 06, 2000 at 06:58:46AM -0700, Sean Noonan wrote:
> Hi List:
>
> I waited a few weeks before making the jump to 4.0-STABLE. The
> previous afternoon I cvsuped the 4.0-STABLE sources. Last night I
> attempted to go from 3.4-STABLE (previous cvsup/makeworld approx mid
> Jan) to 4.0-STABLE.
>
> I used the /usr/src/UPDATING file in addition to my normal
> documentation/procedures.
>
> All seemed to go well, until the point came to reboot into single user
> mode. At this point I ran into problems. My rookieness will show
> shortly.
>
> I seem to remember (although I'm a FreeBSD newbie) that the instructions
> "enter -s at the boot prompt" is no longer the way to enter single user
> mode, correct?
>
At the "twirling baton" hit the space-bar, then type ``/kernel -s''
(assuming the kernel you wish to boot is called "kernel") or, at the
10-second countdown, hit the space-bar, then type ``boot -s''.
> At any rate, I let the kernel boot as normal (my intention, since I
> couldn't remember exactly how to get into single user mode, was to
> boot as normal, then do a 'shutdown now'). I saw "4.0-STABLE" flash by
> the screen and was temporarily elated. Then I got this error messages:
>
> Mounting root from ufs:wd0s1a
> wd0: bad sector table not supported
> wd0s1: bad sector table not supported
> Root mount failed: 22
> Mounting root from ufs:wd0a
> wd0: bad sector table not supported
> wd0s1: bad sector table not supported
> Root mount failed: 22
>
> What exactly does this mean? The hard drive appeared perfectly well under
> 3.0-3.4.
>
You didn't change your /etc/fstab entries from wd* to ad* did you?
I'm not 100% sure about this next bit as I've only ever read about it
on the mailing lists, never had to do it for real.
To allow you to boot, even single-user, you'll need to enter:
set rootdev=/dev/ad0s1a
At one of the 2 prompts described above. The problem is I can't
remember which one. Try interrupting the boot at both points, type
``?'' and see which one shows ``set rootdev'' as an option.
Once it's up, edit /etc/fstab.
HTH, and sorry for being a bit vague.
> Some things I tried to solve the problem:
> 1. Re-read all docs, make sure I did everything in order, correct, etc.
> 2. I saw where wd was going to be replaced by ad, so when I had previously
> build my devices with MAKEDEV it did it for both wd and ad. Is building
> both ok? Is order important?
>
> Forgive me this has been answered previously, I did make an attempt to
> search the archives, etc., but am in over my head.
>
> Thanks so much in advance,
>
> -Sean Noonan
> noonans@home.com
>
>
>
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-questions" in the body of the message
--
Beam me up Scottie, there's no intelligent life down here
________________________________________________________________
FreeBSD - The Power To Serve http://www.freebsd.org
My Webpage http://ukug.uk.freebsd.org/~mark/
mailto:mark@ukug.uk.freebsd.org http://www.radan.com
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000406192358.A236>