Re: Failure on today's CVS (stable, AMD)
On Wed, Jan 19, 2005 at 07:19:49PM -0800, Doug White wrote: 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. Followup for the archives. The twa driver has known issues right now, a fix is being worked on. I received a patch and applied it, which did indeed solve the problem. My understanding is that this patch should be committed later this week so if you are reading this thread much after Feb 1, 2005 it likely does not apply. /\/\ \/\/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Failure on today's CVS (stable, AMD)
On Wed, 19 Jan 2005 16:42:29 -0500, Michael R. Wayne [EMAIL PROTECTED] 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 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Failure on today's CVS (stable, AMD)
Hi, Michael, 2005-01-19 16:42 -0500Michael 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/ signature.asc Description: =?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?=
Re: Failure on today's CVS (stable, AMD)
Date: Thu, 20 Jan 2005 10:12:04 -0600 From: Scot Hetzel [EMAIL PROTECTED] Sender: [EMAIL PROTECTED] On Wed, 19 Jan 2005 16:42:29 -0500, Michael R. Wayne [EMAIL PROTECTED] 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. While this works (I've done it), make reinstallkernel and make -DMODULES_WITH_WORLD reinstallkernel can also be good friends. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: [EMAIL PROTECTED] Phone: +1 510 486-8634 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Failure on today's CVS (stable, AMD)
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 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Failure on today's CVS (stable, AMD)
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 [EMAIL PROTECTED] | www.FreeBSD.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
