Date: Wed, 14 Aug 2013 06:13:28 +0400 From: "Andrey V. Elsukov" <ae@FreeBSD.org> To: Thomas Mueller <mueller6724@bellsouth.net> Cc: freebsd-stable@freebsd.org Subject: Re: Change in loader or kernel: won't boot with kfreebsd in grub2 Message-ID: <520AE7C8.2080606@FreeBSD.org> In-Reply-To: <685155.72446.bm@smtp110.sbc.mail.bf1.yahoo.com> References: <685155.72446.bm@smtp110.sbc.mail.bf1.yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 14.08.2013 05:41, Thomas Mueller wrote: >> On 12.08.2013 19:39, Thomas Mueller wrote: >>> I still wonder why Super Grub Disk kfreebsd worked until >>> recently. > >>> I figure something must have changed in FreeBSD loader or kernel >>> structure since the Super Grub Disk didn't change in that time. >> >>> For currdev, apparently the big hard drive is just recognized as >>> one big drive with no reference to partitions (lsdev). > >> Can you obtain the following information and send it to me? > >> 1. lsdev output from the loader that works 2. gpart list from >> booted system 3. lsdev output from the loader that doesn't work > > -- >> WBR, Andrey V. Elsukov > > I can provide the gpart list from booted system, but how do I capture > lsdev output without copying by pencil and paper? You can just make a photo. > I looked in "man loader" and "man loader.conf". > > I subsequently added some partitions (6,7,12,13,14) for Linux > purposes, but that should have no current effect on booting FreeBSD. An output of `gpart show` contains less information that `gpart list`, it is useless for me :) -- WBR, Andrey V. Elsukov
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?520AE7C8.2080606>