Date: Thu, 29 Nov 2018 19:43:23 +0200 From: Toomas Soome <tsoome@me.com> To: Mark Martinec <Mark.Martinec+freebsd@ijs.si> Cc: freebsd-current@freebsd.org, freebsd-stable@freebsd.org Subject: Re: Boot loader stuck after first stage upgrading 11.2 to 12.0-RC2 Message-ID: <5EEBAFC0-4FA3-4219-A918-7376F4223656@me.com> In-Reply-To: <22f5b92a09ea4d62ac3feb74457067f7@ijs.si> References: <22f5b92a09ea4d62ac3feb74457067f7@ijs.si>
next in thread | previous in thread | raw e-mail | index | archive | help
I just did push biosdisk updates to stable/12, I wonder if you could = test those bits=E2=80=A6 rgds, toomas > On 29 Nov 2018, at 17:01, Mark Martinec <Mark.Martinec+freebsd@ijs.si> = wrote: >=20 > After successfully upgraded three hosts from 11.2-p4 to 12.0-RC2 = (amd64, > zfs, bios), I tried my luck with one of our production hosts, and = ended up > with a stuck loader after rebooting with a new kernel (after the first > stage of upgrade). >=20 > These were the steps, and all went smoothly and normally until a = reboot: >=20 > freebsd-update upgrade -r 12.0-RC2 > freebsd-update install > shutdown -r now >=20 > While booting, the 'BTX loader' comes up, lists the BIOS drives, > then the spinner below the list comes up and begins turning, > stuttering, and after a couple of seconds it grinds to a standstill > and nothing happens afterwards. >=20 > At this point the ZFS and the bootstrap loader is supposed to > come up, but it doesn't. >=20 > This host has too zfs pools, the system pool consists of two SSDs > in a zfs mirror (also holding a freebsd-boot partition each), the > other pool is a raidz2 with six JBOD disks on an LSI controller. > The gptzfsboot in both freebsd-boot partitions is fresh from 11.2, > both zpool versions are up-to-date with 11.2. The 'zpool status -v' > is happy with both pools. >=20 > After rebooting from an USB drive and reverting the /boot directory > to a previous version, the machine comes up normally again > with the 11.2-RELEASE-p4. >=20 > I found a file init.core in the / directory, slightly predating the > last reboot with a salvaged system - although it was probably not > a cause of the problem, but a consequence of the rescue operation. >=20 > It is unfortunate that this is a production host, so I can't play > much with it. One or two more quick experiments I can probably > afford, but not much more. Should I just first wait for the > official 12.0 release? Should I try booting with a 12.0 on USB > and try to import pools? Suggestions welcome. >=20 >=20 >=20 > Now that the /boot has been manually restored to the 11.2 state, > A SECOND QUESTION is about freebsd-update, which still thinks we are > in the middle of an upgrade procedure. Trying now to just update > the 11.2-RELEASE-p4 to 11.2-RELEASE-p5, the fetch complains: >=20 > # uname -a > FreeBSD xxx 11.2-RELEASE-p4 FreeBSD 11.2-RELEASE-p4 > # > # freebsd-version > 11.2-RELEASE-p4 > # > # freebsd-update fetch > src component not installed, skipped > You have a partially completed upgrade pending > Run '/usr/sbin/freebsd-update install' first. > Run '/usr/sbin/freebsd-update fetch -F' to proceed anyway. >=20 > So what is the right way to get rid of all traces of the > unsuccessful upgrade, and let freebsd-update believe we are cleanly > at 11.2-p4 ? Removing /var/db/freebsd-update did not help. >=20 > Mark > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to = "freebsd-current-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5EEBAFC0-4FA3-4219-A918-7376F4223656>