Date: Tue, 8 Oct 2013 02:27:12 -0700 From: Doug Hardie <bc979@lafn.org> To: Polytropon <freebsd@edvax.de> Cc: freebsd-questions@freebsd.org Subject: Re: 9.1 - 9.2 upgrade Message-ID: <B010B475-D136-4ECF-AB01-B574AE736153@lafn.org> In-Reply-To: <20131005120809.GB43287@webmail.dweimer.local> References: <B5D4B829-3B73-4E5F-BA69-6DFA0F129975@lafn.org> <BCEB7B13-2084-4D4E-9F89-19F29EFBCC54@lafn.org> <62A8B684-0328-42F5-B9E4-D5DF80563D4D@lafn.org> <1bdf3856902efd917ab9d489c8b6e751@dweimer.net> <2B420332-D26F-4926-A53A-787B110B0EFE@lafn.org> <20131005040802.32af9b73.freebsd@edvax.de> <B01899BC-6E07-450F-AB74-A2EC20011F0D@lafn.org> <20131005050307.7bab5735.freebsd@edvax.de> <039B61B6-C918-494C-B327-52E4815660B1@lafn.org> <20131005120809.GB43287@webmail.dweimer.local>
next in thread | previous in thread | raw e-mail | index | archive | help
On 5 October 2013, at 05:08, Polytropon <freebsd@edvax.de> wrote: > On Fri, 4 Oct 2013 21:49:18 -0700, Doug Hardie wrote: >>=20 >> On 4 October 2013, at 20:03, Polytropon <freebsd@edvax.de> wrote: >>=20 >>> On Fri, 4 Oct 2013 19:42:15 -0700, Doug Hardie wrote: >>>>=20 >>>> On 4 October 2013, at 19:08, Polytropon <freebsd@edvax.de> wrote: >>>>=20 >>>>> On Fri, 4 Oct 2013 18:58:52 -0700, Doug Hardie wrote: >>>>>> The exact sequence was: >>>>>>=20 >>>>>> Step 1: freebsd-update from 9.1 to 9.2 >>>>>=20 >>>>> Have you verified in /etc/freebsd-update.conf that "src" >>>>> is definitely part of what should be updated? >>>>=20 >>>> System is not bootable - can't verify anything=85 >>>=20 >>> Does the system (or better, its "enclosure", software-wise) >>> allow booting a rescue system or an emergency media, such >>> as a FreeBSD v9 live system? >>=20 >> Yes - but there is no one there who can successfully be told >> how to run it. >=20 > Not even inserting a USB stick (with the FreeBSD memstick data) > or a CD? >=20 >=20 >=20 >> We have serious communications issues - they want to use back >> slashes and have no idea what a slash is. >=20 > Maybe that is the result of many years of "administration" on > "Windows" PCs. :-) >=20 >=20 >=20 >> Even if you tell them which key to use, they know better and >> use a back slash cause thats what Windoze uses. >=20 > Uh... "knowing better" would disqualify them as maintainers of > a server installation. The inability to learn (or even to read > and follow instructions) is a dangerous thing. >=20 >=20 >=20 >> The disk should be in the mail to me now. I will be able to >> work with it when it arrives. >=20 > Okay, that's also a possible alternative. To be honest, that's > the first time I hear about this procedure. But doable. >=20 >=20 >=20 >>> The file /etc/freebsd-update.conf should contain the line >>>=20 >>> Components src world kernel >>>=20 >>> if you want to make sure the source is properly updated, >>> along with the world and kernel (GENERIC). >>=20 >> As indicated before, I don't think all the source got updated.=20 >> The kernel showed 9.2 after recompilation. However UPDATING >> was not updated. Thats as much as I could check before. >=20 > I assume that this could be possible by inconsistently updated > sources. It would be a good start to remove /usr/src and download > the sources of the correct version via SVN _or_ freebsd-update > again. Before the next installation attempt, /usr/obj should be > removed as well, just to be sure. >=20 >=20 >=20 >>>>>> Step 5: reboot >>>>>=20 >>>>> Attention: Into single-user mode. >>>>=20 >>>> Not possible since the system is located over 100 miles away. >>>> Everything has to be done via remote console. >>>=20 >>> Does this mean "SSH only" or do you have a _real_ console >>> transmission by which you can access the system _prior_ to >>> the OS providing the SSH access? I'm mentioning this because >>> the traditional approach requires (few) steps done in the >>> single-user mode where no SSH connectivity is provided in >>> the "normal" way=85 >>=20 >> I have a telnet box that has serial connections to the console >> ports. That approach has been used without any issues since >> FreeBSD 2.5. I do disable all ports during the process via an >> reduced rc.conf file. >=20 > A serial console should also work, but even though I've been > using serial consoles (and _real_ serial terminals), one thing > I'm not sure about: Is it possible to interrupt (!) the boot > process at an early stage to get to the loader prompt and > boot into single user mode from there? >=20 > Ok > boot -s >=20 > If not, do you have the "beastie menu" (or whatever it is called > today) enabled to go to SUM to perform the "make installworld" step? >=20 > Anyway, if you can install everything is required with the disk > at home, and then send it back to that "datacenter" (according > to your characterization, the quotes are deserved), that should > solve the problems and make sure everything works as intended. The Thick Plottens=85 I received the drives and installed them on a working system. The = failed system is structured with a single partition for the system and = another for swap. For some unknown reason, the BIOS got left configured = to boot the extra disk if its powered up. That turns out to be handy. = I can boot a working system with the corrupt drive powered off. Booting from the corrupt drive yields the normal hardware info followed = by the Beastie image and immediately by a multitude of lines (repeated = many times): Consoles: internal video/keyboard serial port BIOS drive C: is disk0 BIOS drive D: is disk1 BIOS 639kB/1037824kB available memory FreeBSD/x86 bootstrap loader, Revision 1.1 (doug@zool.lafn.org, Thu Oct 3 04:23:13 PDT 2013) Can't work out which disk we are booting from. Guessed BIOS device 0xffffffff not found by probes, defaulting to disk0: I was able to capture these by using a serial console connected to = another computer. The lines only appear on the serial console once. = They scroll by on the real console many time - all too fast to read = anything. Then after a few seconds of that, the screen goes black, and = the system reboots. The cycle then repeats=85 Pressing any key does = nothing. I even filled the keyboard buffer with spaces hoping to stop = boot, but nothing seems to stop it. I checked and the freebsd-update.conf include world sys and src. I = rebuild everything after removing /obj just for grins and giggles. I = have installed the kernel and world using DESTDIR to put it on the = corrupt drive. Same messages again. I now have the corrupt drive mounted on /mnt and am trying to update the = src again. Using: =20 freebsd-update -b /mnt fetch updated files list show /usr/src/sys=85 and updating to 9.1-RELEASE-p7 freebsd-update -b /mnt install This is running slower than molasses in January. Its run for = almost 30 minutes and only 3 files have been updated. There must be = network issues between me and the server. I'll let it run tonight but I = am going to crash now. Long day. More tomorrow. -- Doug=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?B010B475-D136-4ECF-AB01-B574AE736153>