Please file a new bug with full details, rather than reopening this one.
It's unlikely to be quite the same cause.
** Changed in: grub2 (Ubuntu)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This seems to have regressed in grub2 1.99 on Natty, or else I've
stumbled onto another problem.
Discussion started here:
http://ubuntuforums.org/showthread.php?p=10183644
--
grub-probe fails with btrfs root (and ext3 /boot)
https://bugs.launchpad.net/bugs/450260
You received this bug
On Thursday 02,December,2010 07:29 AM, Nobu wrote:
This seems to have regressed in grub2 1.99 on Natty, or else I've
stumbled onto another problem.
Discussion started here:
http://ubuntuforums.org/showthread.php?p=10183644
Yeah, it doesn't work on my Maverick system either, using a
This bug was fixed in the package grub2 - 1.98+20100614-1ubuntu1
---
grub2 (1.98+20100614-1ubuntu1) maverick; urgency=low
* Resynchronise with Debian:
- Add btrfs probing support, currently only in the single-device case
(LP: #450260).
- Insert partmap module in
** Branch linked: lp:~ubuntu-core-dev/ubuntu/maverick/grub2/maverick
--
grub-probe fails with btrfs root (and ext3 /boot)
https://bugs.launchpad.net/bugs/450260
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
** Changed in: grub2 (Debian)
Status: Fix Committed = Fix Released
--
grub-probe fails with btrfs root (and ext3 /boot)
https://bugs.launchpad.net/bugs/450260
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
** Changed in: grub2 (Debian)
Status: Incomplete = Fix Committed
--
grub-probe fails with btrfs root (and ext3 /boot)
https://bugs.launchpad.net/bugs/450260
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
Maybe it's fixed for some people but apparently not for everyone. In
any case I think I understand what's going on here (we should be using
statvfs, or something like that) so please leave this open.
** Changed in: grub2 (Ubuntu)
Status: Invalid = Triaged
--
grub-probe fails with btrfs
Marking invalid as per last comment.
** Changed in: grub2 (Ubuntu)
Status: Triaged = Invalid
--
grub-probe fails with btrfs root (and ext3 /boot)
https://bugs.launchpad.net/bugs/450260
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Marking invalid as per last comment.
--
grub-probe fails with btrfs root (and ext3 /boot)
https://bugs.launchpad.net/bugs/450260
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
I'm running Lucid, and update-grub still fails in the same way.
Adding GRUB_DEVICE in /etc/default/grub is not enough, you also need the
|| true patch, because the script (grub-mkconfig) always tests for
root, before it even loads /etc/default/grub.
For me an acceptable fix would be that if
Upgraded to Ubuntu Lucid, this bug no longer applies; update-grub runs
fine. If you got your btrfs root partition on top of crypto, bug #551055
still applies.
--
grub-probe fails with btrfs root (and ext3 /boot)
https://bugs.launchpad.net/bugs/450260
You received this bug notification because
** Tags added: patch
--
grub-probe fails with btrfs root (and ext3 /boot)
https://bugs.launchpad.net/bugs/450260
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
If your btrfs root partition is on top of any crypto devices, you'll be
also affected by bug #551055. I posted a procedure for Ubuntu Karmic in
comment 4 there, involving instructions from both threads. It restores
full automagic functionality both for update-grub and update-initramfs.
--
Well since everyone seems pretty much fixed on the idea that static
GRUB_DEVICE and GRUB_DEVICE_UUID entries are ok, just have two posing
questions.
How do you suppose we get those entries there in the first place?
What would we do in the event that a UUID changes (if unlikely, I know :) ?
Or
I definitely wouldn't call the GRUB_DEVICE solution acceptable. Btrfs is still
quite new and I don't think it makes sense to merge it hacks like this. I
believe that this is a case where the bleeding edge users should need to build
their own packages and maintain their own configuration. Trying
This is more serious than it seems, not simply a matter of convenience.
Packages like desktop-base, which runs update-grub in postinst, fail to
install properly when running on a btrfs root.
--
grub-probe fails with btrfs root (and ext3 /boot)
https://bugs.launchpad.net/bugs/450260
You received
This seems to be a pretty good workaround allowing manual override of
the root device. Simply drop a GRUB_DEVICE=/dev/... line into
/etc/default/grub and things should just work again. Certainly not a
permanent solution, but then again btrfs has quite a while until it sees
usage outside of
** Changed in: grub2 (Ubuntu)
Status: Confirmed = Triaged
** Changed in: grub2 (Ubuntu)
Importance: Undecided = Medium
--
grub-probe fails with btrfs root (and ext3 /boot)
https://bugs.launchpad.net/bugs/450260
You received this bug notification because you are a member of Ubuntu
** Changed in: grub2 (Debian)
Status: New = Incomplete
--
grub-probe fails with btrfs root (and ext3 /boot)
https://bugs.launchpad.net/bugs/450260
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
By changing grub-mkconfig, update-grub no longer fails and I can produce
a valid grub.cfg. However, grub still fails at boot with Unknown
Filesystem in up-to-date ubuntu karmic and leaves you at the rescue
prompt.
However, I can boot to a root btrfs filesystem.
My setup:
/dev/sda1 is /boot
Please excuse me. My failure to boot was solved by re-running grub-
install after I added my seperate /boot partition.
--
grub-probe fails with btrfs root (and ext3 /boot)
https://bugs.launchpad.net/bugs/450260
You received this bug notification because you are a member of Ubuntu
Bugs, which is
A simpler change would be to to add || true to the end of the
GRUB_DEVICE=... line in grub-mkconfig, and then set your root device
by hand in /etc/default/grub, or something along those lines.
--
grub-probe fails with btrfs root (and ext3 /boot)
https://bugs.launchpad.net/bugs/450260
You
Is anything happening with this upstream?
I've managed to get grub2 working via backporting the legacy 0.97 shell probe
functions into the grub-mkconfig_lib file. But this doesn't really seem right.
Attached my changes against this post anyway for people to see.
Regards
Iain
** Attachment
Just a note,
1) Not surprisingly, doesn't work on amd64 as well.
2) Good old grub 0.97 is not complaining when /boot has it's own partition.
Frank
--
grub-probe fails with btrfs root (and ext3 /boot)
https://bugs.launchpad.net/bugs/450260
You received this bug notification because you are a
** Changed in: grub2 (Ubuntu)
Status: New = Confirmed
--
grub-probe fails with btrfs root (and ext3 /boot)
https://bugs.launchpad.net/bugs/450260
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Oh, and the device map is fine, so it's not that...
j...@fehung:~$ cat /boot/grub/device.map
(hd0) /dev/sda
--
grub-probe fails with btrfs root (and ext3 /boot)
https://bugs.launchpad.net/bugs/450260
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Bug watch added: Debian Bug tracker #540786
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=540786
** Also affects: grub2 (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=540786
Importance: Unknown
Status: Unknown
--
grub-probe fails with btrfs root (and ext3
** Changed in: grub2 (Debian)
Status: Unknown = New
--
grub-probe fails with btrfs root (and ext3 /boot)
https://bugs.launchpad.net/bugs/450260
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
29 matches
Mail list logo
