Date: Thu, 06 Aug 2015 10:30:14 -0700 From: Cary <cary@SDF.org> To: freebsd-questions@freebsd.org Subject: Re: windows entry for grub2 Message-ID: <55C399A6.4030905@SDF.org> In-Reply-To: <20150806011313.Horde.2QXs18DRBiA3e2WofhttL83@mail.parts-unknown.org> References: <20150804034108.Horde._OTrFyjhdRQUM4x9GSp-yLG@mail.parts-unknown.org> <CAFYkXjm9eJVdVFkbzR9esVf8D9qeF5aLZ3Hj8rGRN2HRAb3Etg@mail.gmail.com> <20150804132218.Horde.Gj6WjgZdXie82Uv8hJ6DwzP@mail.parts-unknown.org> <55C1418A.8020904@SDF.org> <20150804201540.Horde.tVjfGgqFaL11N353NCxJOb4@mail.parts-unknown.org> <55C1AD48.4060004@SDF.org> <20150805021737.Horde.Aqa-ovKXshlnp4t4PUEB8rw@mail.parts-unknown.org> <55C2388B.8030803@SDF.org> <20150806011313.Horde.2QXs18DRBiA3e2WofhttL83@mail.parts-unknown.org>
next in thread | previous in thread | raw e-mail | index | archive | help
David Benfell wrote: > Quoting Cary <cary@sdf.org>: >> >> >> That's all. If you've got it, that will be nice to hear. > > It was weird. In the past, when I've run into difficulty with EFI boot entries, > efibootmgr (under Linux) has been my friend. This tool can add boot entries, > change the order in which they are attempted, delete boot entries, and probably > a few other things. > > So when grub was still missing, I booted into Linux, ran efibootmgr, added the > entry and tried again. The invocation is very specific. You specify the drive > *and* the partition the efi file is in. > > No joy. Any entries I added disappeared by the reboot. And just so we're clear, > rebooting to Linux and running efibootmgr confirmed that the entries had > disappeared. > > So I got a Windows recovery disk and tried getting *it* to fix the boot. I tried > just about every option there was on that thing. Still no joy. It flatly refused. > > As to your specific points, the system didn't just come with Windows. Dell adds > a bunch of partitions with various utilities and recovery programs. But there > didn't seem to be any way to access them--unless I got grub running. Some of > those partitions are msdosfs and I'm pretty sure that's what grub-mkconfig was > responding to. > > Very sorry to learn that the multiboot did not succeed. I was a little worried. Its not a simple task, but it isn't very difficult to make a rescue cd or usb stick using grub. I wish I had thought to recommend that. Possibly you would not have had to wipe away the oem's partitions. In any case there's the option to start over thanks to bsdinstall(8). -- cary@sdf.org SDF Public Access UNIX System - http://sdf.org ------------------------------
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?55C399A6.4030905>