Date: Mon, 20 Apr 2009 21:33:54 -0600 From: Tim Judd <tajudd@gmail.com> To: Daniels Vanags <daniels.vanags@smpbank.lv> Cc: questions@freebsd.org Subject: Re: Dump | Restore Message-ID: <ade45ae90904202033v4bae8ec5k38f23a41525ec09e@mail.gmail.com> In-Reply-To: <E8298C3B2FC1CC43B3FBAC70544780A602D45118@EXCH-01.mbint.multibanka.com> References: <E8298C3B2FC1CC43B3FBAC70544780A602D45118@EXCH-01.mbint.multibanka.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Greetings, On Mon, Apr 20, 2009 at 4:31 AM, Daniels Vanags <daniels.vanags@smpbank.lv>wrote: > > > Unable to successfully dump | restore over ssh. Source machine > FreeBSD 6.2, disk /dev/mirror/gm0s1a, > > target machine FreeBSD 6.2, target disk /dev/ad1s1a mounted on /mnt. > > Run dump -0aLf - / | ssh ip_address ''cd /mnt/ && cat | restore - rf > -'', dump/restore goes without any errors. > > Fstab fixed, but system failure to boot: BTX halted. > > Please help. > > I read up on what the BTX is. BooT eXtender -- url here http://www.freebsd.org/doc/en/books/arch-handbook/boot-boot2.html Long story short, BTX is what brings the PC BIOS/CMOS code execution from 16-bit real mode, to 32-bit protected mode. I've had repeated problems with name-brand PCs that result in a BTX halted. Whiteboxes/custom builds tend to work the best (and IMHO, last the longest). So asking the OP to flag slices or bsdlabels as bootable probably won't help, but I've been wrong before. :D
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ade45ae90904202033v4bae8ec5k38f23a41525ec09e>