You are not logged in.
Pages: 1
I originally thought this problem was related to my machine, but I've now replicated it on two separate boxes (one of which was under-going a fresh install). This has only been happening to me on the very latest version of the grub-common package (2.00-1), but I couldn't tell you when the last time I tried to install grub2 was (I think a couple of months ago).
Basically, the command line doesn't matter (and I've tested this on both hard drives and flash drives, changing all the parameters to observationally identical parameters to no effect -- root-directory to boot-directory, dropping --no-floppy and --recheck, etc.), but here's an example one:
grub-install --target=i386-pc --root-directory=<path-to-root-of-device> --recheck --no-floppy <device>
The resulting output looks like:
/usr/sbin/grub-install: line 864: 15272 Segmentation fault (core dumped) "$grub_setup" $[allow_floppy} /... etc.
Most of the line is just the specific command being used, so you can look it up pretty easily in grub-install directly. But what's going on on line 864? The specific number, 15272 in this case, changes on every run (I think it's the pid of the process, but I haven't checked that). Is anyone else having this issue?
Thanks!
Last edited by nrujac (2012-09-01 00:37:28)
Offline
Started playing around with filesystem choices, and I've noticed that this only happens with btrfs formatted filesystems. Can anyone confirm?
EDIT: While I wait for someone to confirm, I'm going to try using an ext4 formatted partition to write the boot directory to and then copy it over to the btrfs filesystem that I'm trying to install. No clue if grub installs anything outside of the boot/grub directory it creates but I guess we'll find out.
Last edited by nrujac (2012-09-01 18:41:27)
Offline
Go figure, but the problem has disappeared on one of my boxes. I was about to do my check by having grub install to the ext4 directory first, and then copying the files over myself. I decided (for completeness' sake) to first reproduce the error before trying the workaround. And the installation went through without a hitch. No idea why, how, or what changed. The other machine still has the same issue though.
Offline
Pages: 1