Date: Wed, 01 Jul 2009 18:46:26 +0400 From: Kamigishi Rei <spambox@haruhiism.net> To: Pegasus Mc Cleaft <ken@mthelicon.com> Cc: current@freebsd.org Subject: Re: Has anyone been able to actually boot the AMD64 kernel after r194958? Message-ID: <4A4B76C2.90406@haruhiism.net> In-Reply-To: <D767B0E97EF64503905498B669110606@PegaPegII> References: <895D2AA2E9964CEE970A64C74D2FF622@PegaPegII> <4A4B724D.10506@haruhiism.net> <D767B0E97EF64503905498B669110606@PegaPegII>
next in thread | previous in thread | raw e-mail | index | archive | help
Pegasus Mc Cleaft wrote: > I use ZFS Boot with a three-way mirror (A seperate GPT slice on > each of the drives) and the swap-space is spanned across 3 other > slices (one on each of the boot drives). I think its giving me that > error because it never gets far enough in the boot to swapon those > slices before it panics. Another symptom of this is that it dosent get > far enough to clear the nextboot flag, so when it does go boom, I have > to manually tell it to boot from the working kernel (r194958). Well, then you won't be able to get a core, because by the time doadump starts the filesystem layer is already dead. The kernel just won't be able to save the dump to something as complicated as a 3-disk-span swap space - it can't even dump to a gmirror-based swapspace properly, you know ;) And if you're using ZFS boot, you probably have ZFS built into kernel so I'm not sure if booting without loading zfs.ko is possible as it's already inside... -- Kamigishi Rei KREI-RIPE
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4A4B76C2.90406>