Your message dated Fri, 6 Dec 2013 13:15:08 +0000
with message-id <20131206131508.ga8...@riva.ucam.org>
and subject line Re: Bug#707831: UUID detection code broken, wrongly uses UUID
has caused the Debian Bug report #707831,
regarding Broken UUID detection code makes LVM systems unbootable after adding
a new PV
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
707831: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707831
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: grub-pc
Version: 1.99-27+deb7u1
Severity: serious
/etc/grub.d/10_linux wrongly adds root=UUID entries to grub.cfg if
grub-probe fails
Specifically, in one case I observed grub-probe had failed because a new
disk was added (some months ago) and grub-mkdevicemap had not been run.
Users typically see this error in that case:
/usr/sbin/grub-probe: error: Couldn't find PV pv1. Check your device.map.
The update-grub script should refuse to write out grub.cfg after such
failures. Currently it appears to default to UUID= entries, and if root
is on LVM, the system is then unbootable.
--- End Message ---
--- Begin Message ---
Source: grub2
Source-Version: 2.00-1
On Fri, Dec 06, 2013 at 12:54:58PM +0000, Colin Watson wrote:
> I think most of this was fixed by this upstream commit, and thus is
> fixed in 2.00:
>
> 2012-03-28 Vladimir Serbinenko <phco...@gmail.com>
>
> * grub-core/disk/diskfilter.c (grub_diskfilter_memberlist): Degrade
> the error when some elements are missing into a warning.
>
> In other words, it's not that important that this PV is missing; in
> other cases it might in theory result in missing modules to access bits
> of the VG, but that's not actually going to be true in this case so it's
> fine for grub-probe to carry on anyway.
>
> The piece noting that we shouldn't carry on if GRUB is unable to
> determine the file system of / remains; after consideration I'm inclined
> to agree with it, and I've posted a patch for this upstream.
Vladimir pointed out on IRC that this is necessary in order to support
the case where GRUB can't understand / but can understand /boot, which
is something we want to continue supporting. So I think it's actually
best to consider this fixed with the specific change above to make sure
that we don't care about missing PVs.
Thanks,
--
Colin Watson [cjwat...@debian.org]
--- End Message ---
