CVS today. Dual Opteron running
5.3-STABLE #3: Tue Nov 30 01:44:05 EST 2004
Following the instructions in UPDATING, I get the following,
indicating a bad kernel. 2 questions:
1) Is this a known, corrected issue as of today? I ran another
CVSUP and did not see any changed to src.
2) More importantly, I recovered by loading /boot/kernel.old/kernel
and the box is up BUT I am concerned that the NEXT time that I
do "make installkernel" I'll stomp on kernel.old losing this
fallback
procedure. I can certainly copy /boot/kernel.old to /boot/kernel.save
but is there something else I should save? Or is there another
suggested procedure?
/\/\ \/\/
The box failed with:
Mounting root from ufs:/dev/da0s1a
setrootbyname failed
ffs_mountroot: can't find rootvp
Root mount failed: 6
Manual root filesystem specification:
<fstype>:<device> Mount <device> using filesystem
<fstype>
eg. ufs:/dev/da0a
? List valid disk boot devices
<empty line> Abort manual input
mountroot>
On Wed, 19 Jan 2005, Michael R. Wayne wrote:> CVS today. Dual Opteron running > 5.3-STABLE #3: Tue Nov 30 01:44:05 EST 2004 > > Following the instructions in UPDATING, I get the following, > indicating a bad kernel. 2 questions: > > 1) Is this a known, corrected issue as of today? I ran another > CVSUP and did not see any changed to src.Looks like your SCSi controller stopped probing. You'll need to look at the dmesg more closely to identify why.> 2) More importantly, I recovered by loading /boot/kernel.old/kernel > and the box is up BUT I am concerned that the NEXT time that I > do "make installkernel" I'll stomp on kernel.old losing this fallback > procedure. I can certainly copy /boot/kernel.old to /boot/kernel.save > but is there something else I should save? Or is there another > suggested procedure?You can use "make reinstallkernel", which will just spam over the current one without rotating it. I'd make the backup anyway in case you screw up; its also nice to keep a known working kenrel around Just In Case. -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org
On Wed, 19 Jan 2005 16:42:29 -0500, Michael R. Wayne <freebsd@wayne47.com> wrote:> 2) More importantly, I recovered by loading /boot/kernel.old/kernel > and the box is up BUT I am concerned that the NEXT time that I > do "make installkernel" I'll stomp on kernel.old losing this fallback > procedure. I can certainly copy /boot/kernel.old to /boot/kernel.save > but is there something else I should save? Or is there another > suggested procedure? >When I have a bad kernel I do the following after booting the good kernel. cd /boot rm -rf kernel cp -rp kernel.old kernel cp -rp kernel.old kernel.good This way I can reboot the box without going into the loader to load kernel.old. Scot
Hi, Michael, ? 2005-01-19?? 16:42 -0500?Michael R. Wayne???> 2) More importantly, I recovered by loading /boot/kernel.old/kernel > and the box is up BUT I am concerned that the NEXT time that I > do "make installkernel" I'll stomp on kernel.old losing this fallback > procedure. I can certainly copy /boot/kernel.old to /boot/kernel.save > but is there something else I should save? Or is there another > suggested procedure?I personally do: cp -R /boot/kernel /boot/kernel.good If the kernel has provided stability for 30 days. For your case, you may want to do: cp -R /boot/kernel.old /boot/kernel.good since the kernel.old is last known good kernel. Of course kernel.save is a good name. For a STABLE branch you generally won't need to fear that loader changes can prevent you from being able to boot from older kernels. Therefore, I think the procedure you have listed is enough to do. Cheers, -- Xin LI <delphij delphij net> http://www.delphij.net/ -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 187 bytes Desc: =?UTF-8?Q?=E8=BF=99=E6=98=AF=E4=BF=A1=E4=BB=B6=E7=9A=84=E6=95=B0? =?UTF-8?Q?=E5=AD=97=E7=AD=BE=E5=90=8D=E9=83=A8?= =?UTF-8?Q?=E5=88=86?Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20050121/cec03ee2/attachment.bin