I had the same thing happening while running in VirtualBox. Tested on a bare-metal machine afterward the results were the same - following the how-to's on running a ZFS root, or a ZFS swap device, or a gmirror root that included swap (w/o ZFS at all) produced what your screenshot shows. My platform is amd64.
Scott -----Original Message----- From: owner-freebsd-sta...@freebsd.org [mailto:owner-freebsd-sta...@freebsd.org] On Behalf Of GNUbie Sent: Thursday, July 01, 2010 9:14 AM To: freebsd-stable@freebsd.org Cc: maurov...@gmail.com; free...@jdc.parodius.com Subject: Re: Unable to boot FreeBSD 8.0-p3 Hello Jeremy, On Fri, Jul 2, 2010 at 12:06 AM, Jeremy Chadwick <free...@jdc.parodius.com> wrote: > > Kernel crash dumps are not enabled by default. You need to define the > following in /etc/rc.conf before that will happen: > > dumpdev="auto" Ok. So, the line "Cannot dump. Device not defined or unavailable." is already going to be an output of the kernel crash. Meaning, during bootup, somehow the kernel crash and since crash dumps was not defined, that is why I was getting that message I just mentioned. Moving forward, what are your recommendations in order for me to be able to boot from my system? Regards, GNUbie _______________________________________________ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" _______________________________________________ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
