Date: Tue, 17 Mar 1998 13:30:19 +0000 (GMT) From: Scot Elliott <scot@online.barbour-index.co.uk> To: stable@FreeBSD.ORG Subject: Re: ATTENTION: Call for opinion re: root device naming change Message-ID: <Pine.BSF.3.96.980317131715.1771A-100000@daffy.online.barbour-index.co.uk> In-Reply-To: <l03130300b13423dde761@[208.2.87.4]>
next in thread | previous in thread | raw e-mail | index | archive | help
I've had a few problems witht the new code too. The first couple were caused by my not reading the instructions properly; theese were SCSI devices and I did get it all working OK. The big problem came when upgrading a system that was origionally a 2.1.5 system with IDE disks. The fstab file had a "wd0a" entry for the root device. I changed this to wd0s1a - which mounts OK on /dist on the 2.2.5-RELEASE system. But when I booted with my new 2.2.6-BETA kernel, it didn't even have a chance to get into single user mode. Just got mesages about "unable to mount root device" - followed by a panic and a reboot. I tried to change the "kernel root on .." entry to wd0s1a - and still the same thing. So I had to give up and revert to 2.2.5-STABLE.. The machine's miles away so it's kind of hard to test these things. Anyone got any ideas? Thanks. Scot. On Tue, 17 Mar 1998, Richard Wackerbarth wrote: > Date: Tue, 17 Mar 1998 07:06:14 -0600 > From: Richard Wackerbarth <rkw@dataplex.net> > To: Studded <Studded@dal.net> > Cc: Mike Smith <mike@smith.net.au>, stable@FreeBSD.ORG > Subject: Re: ATTENTION: Call for opinion re: root device naming change > > At 8:50 PM -0600 3/16/98, Studded wrote: > >Strong vote for keeping it in. In my mind (and with all due respect to > >those involved) the problems we've seen were caused by too little > >notice, too little regression testing, and too few people reading the > >right lists at all. It seems to me that the bugs have been worked out of > >the thing, and we have an opportunity to shout the news from the > > I believe that this is incorrect. I, am I am sure others who might not be > so vocal, > have a configuration that I don't know how to use with the new kernel. > > As I understand it, Mike understands the problem but does not (yet) have a > solution > short of reformatting the HD. > > > That said, I did think of another way to handle the problem of a > >mismatch between a new kernel and an old mount. Put the test for most up > >to date mount version that someone suggested previously into > >/usr/sbin/config. If the user is about to do damage, config should bomb > >loud and ugly with the appropriate information. In fact, this method > >could be extensible to other cases in the future with a little thought. > >:) > > This is not a version mismatch problem. I have the latest (-stable) of > everything. This includes the "mount", MAKEDEV, and kernel changes. All > imagined sd0 entries are in /dev, etc. > > At a MINIMUM, I think that we need a script which will examine the HD's, > the /dev tree and fstab and tell us what to change BEFORE we try to use it. > > Richard Wackerbarth > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > ----------------------------------------------------------------------------- Scot Elliott (scot@poptart.org) | Work: +44 (0)171 7046777 PGP fingerprint: FCAE9ED3A234FEB59F8C7F9DDD112D | Home: +44 (0)181 8961019 ----------------------------------------------------------------------------- Public key available by finger at: finger scot@poptart.org or at: http://www.poptart.org/pgpkey.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.96.980317131715.1771A-100000>