GNU GRUB - Bugs: bug #37569, unknown LVM metadata header
You are not allowed to post comments on this tracker with your current authentication level.
bug #37569: unknown LVM metadata header
Submitter: | Øyvind Hvidsten <bolt> | ||
Submitted: | Sun 14 Oct 2012 08:22:34 AM UTC | ||
Category: | Configuration | Severity: | Major |
Priority: | 5 - Normal | Item Group: | Software Error |
Status: | Works For Me | Privacy: | Public |
Assigned to: | None | Originator Name: | |
Open/Closed: | Closed | Release: | other |
Release: | Reproducibility: | Every Time | |
Planned Release: | None |
Mon 20 Jul 2015 09:22:05 PM UTC, comment #4: |
Øyvind Hvidsten <bolt> |
Tue 19 Mar 2013 04:26:55 PM UTC, comment #3: There were a lot of LVM fixes between 1.99 and 2.00. Please try latest bzr checkout. |
Vladimir Serbinenko <phcoder> |
Tue 19 Mar 2013 04:11:11 PM UTC, comment #2: Confirm to have hit this issue while setting up a lvm over raid1 setup with debian-installer 7.0 rc1: grub 1.99, os-prober 1.56. Installation was successful but received the same unknown LVM metadata header errors when running update-grub (part of a kernel package upgrade).
|
LV_426 <lv_426> |
Sat 03 Nov 2012 09:31:56 AM UTC, comment #1: I rebuilt the raid/lvm setup from scratch, after dd'ing zeroes to the disks. Grub 1.99 still gave the same errors. However, grub 2.00-7 from Debian's experimental archives now produces no errors. What the... |
Øyvind Hvidsten <bolt> |
Sun 14 Oct 2012 08:22:34 AM UTC, original submission:
Setup:
|
Øyvind Hvidsten <bolt> |
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Follow 2 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2015-11-08 | phcoder | Status | None | Works For Me | |
Open/Closed | Open | Closed |
Powered by Savane 3.13-d3ae.
Corresponding source code
I (unfortunately?) no longer have this setup, and have not been able to reproduce this bug since. As nobody else is chiming in, I suggest closing this bug.