Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
look at all reported bugs in a timely manner.
This was reported against a very old release so I'm going to close it.
If you still have the issue please
* If /boot files are copied to rescue partition manually, the UUID in
the search lines in grub.cfg will not match the UUID of the rescue
partition. A --grub-root-directory option for grub-mkconfig would fix
this.
* grubenv seems to get written to (root)/grub while it is installed in
I did actually copy to /media/label/boot/
(But I have tried it as written above with same result.)
--
failures on grub-install to create rescue boot media
https://bugs.launchpad.net/bugs/498533
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
One error I noticed now:
grub-mkconfig is always writing to /boot/grub/device.map not honoring
the path given with for grub.cfg with -o
--
failures on grub-install to create rescue boot media
https://bugs.launchpad.net/bugs/498533
You received this bug notification because you are a member of
Am Samstag, den 19.12.2009, 16:14 + schrieb ceg:
One error I noticed now:
grub-mkconfig is always writing to /boot/grub/device.map not honoring
the path given with for grub.cfg with -o
grub-mkconfig always uses /boot.
It doestn't have at all any support for something like
Hi, thanks for that quick response. Is there any workaround for Cannot read
`/grub/core.img'?
normally). - Grub2 needed grub-install /dev/sda5 to work again.
Should never happen if both the directory given with --root-directory is
the drive/partition you want and also the device you give
grub-mkconfig always uses /boot.
It doestn't have at all any support for something like --root-directory=
of grub-install.
Hm, I took the option -o, --output=FILE output generated config to
FILE for it.
Also all /etc/grub.d/* files only look in /boot/ for the kernels etc.
That might not
Ah, right, I probably just don't need to grub-mkconfig at all if /boot
is copied.
--
failures on grub-install to create rescue boot media
https://bugs.launchpad.net/bugs/498533
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Am Samstag, den 19.12.2009, 16:59 + schrieb ceg:
Hi, thanks for that quick response. Is there any workaround for
Cannot read `/grub/core.img'?
Either make sure you don't need to use blocklists by using (g)parted to
resize the first partition so there's enough room between MBR and it for
you can use grub-install with --grub-setup=/bin/true
Thanks for this, and your help!
Way cleaner than copying to the rescue partition, over-mounting it to /boot and
than doing update-grub/grub-install.
--
failures on grub-install to create rescue boot media
--grub-setup=/bin/true worked nice! Nailed it down to two issues now.
1)
When I used grub-mkconfig (at that time with -o
/media/label/boot/grub/grub.cfg but shouldn't matter) it did create a faulty
grub.cfg however. It probably looked in /boot/grub for the device.map (as it
does not support
11 matches
Mail list logo
