Date: Fri, 04 Jan 2013 13:28:38 -0800 From: "Bruce A. Mah" <bmah@freebsd.org> To: Paul Mather <paul@gromit.homeunix.org> Cc: stable@freebsd.org, Vincent Hoffman <vince@unsane.co.uk> Subject: Re: Solved?: Re: Upgrade of RELENG_8 ZFS boot pool leads to unbootable system Message-ID: <50E74986.2000900@freebsd.org> In-Reply-To: <2775327B-34AE-40D6-8563-D75026887235@gromit.homeunix.org> References: <FA810100-4041-40D7-AE09-77E07C1E3206@gromit.homeunix.org> <50E48610.2040204@infracaninophile.co.uk> <A690C516-E595-4001-8622-096D0CBF6A45@gromit.homeunix.org> <50E6B164.50105@unsane.co.uk> <2775327B-34AE-40D6-8563-D75026887235@gromit.homeunix.org>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] If memory serves me right, Paul Mather wrote: > That's weird. I have the same basic /boot/loader.conf entries > (except for a speed of 115200) and even just putting "-Dh" into > /boot.config leads to the same unbootable system behaviour. :-( > > Maybe something broke recently in the RELENG_8 boot loader? Like I > said originally, that /boot.config entry had been working for me > without problems for a long time. Hi Paul-- I recently ran into this as well. I didn't do any setting of the console bitrate, just "-Dh" in /boot.config, and it caused a server I was upgrading to lock up just as you described. I had to learn about mounting ZFS filesystems from the Fixit environment in a hurry. My workaround was to get rid of /boot.config, which obviously doesn't restore the original functionality. The system in question was (is) running 8.3-RELEASE. Bruce. [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (Darwin) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iEYEARECAAYFAlDnSYYACgkQ2MoxcVugUsOvEgCfW6+WGvbGWPQyNgu5PBIlyZmr bp8AnjThpkk9eqAskXXo/QjV8GZPDk5p =r7Ez -----END PGP SIGNATURE-----help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?50E74986.2000900>