Your message dated Thu, 21 Apr 2011 11:57:54 +0100
with message-id <[email protected]>
and subject line Re: grub-common: segfaulting while scanning a specific lvm LV
has caused the Debian Bug report #599358,
regarding grub-common: segfaulting while scanning a specific lvm LV
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 [email protected]
immediately.)
--
599358: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=599358
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: grub-common
Version: 1.96+20080724-10
Severity: important
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Daniel Fussell <[email protected]>
To: Debian Bug Tracking System <[email protected]>
Subject: grub-common: segfaulting while scanning a specific lvm LV
Message-ID: <[email protected]>
X-Mailer: reportbug 3.45
Date: Wed, 06 Oct 2010 14:28:24 -0600
Package: grub-common
Followup-For: Bug #593652
When doing kernel security updates, aptitude says update-grub failed with error
139.
Checking other bug reports lead me to try grub-probe -vv -d /dev/system/root -t
abstraction
which works fine on my many logical volumes until it get to my root volume
(/dev/system/root),
where it segfaults. Thought there might be some data needing to be flushed, so
ran sync. No dice.
Tried updating grub, but couldn't finish because the other kernels haven't
finished configuring.
The root filesystem (ext3) hadn't been checked in many years, but I'm not in a
position to reboot.
So I created an lvm snapshot and ran fsck on the snapshot; it came up clean.
Then I ran grub-probe, and it finished WITHOUT segfaulting (go fig).
Ran update-grub, it finished without error.
Ran aptitude install, finished configuring the kernels and updated grub without
issue.
-- System Information:
Debian Release: lenny/sid
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.26-1-xen-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages grub-common depends on:
ii base-files 4.0.5 Debian base system miscellaneous f
ii libc6 2.7-14 GNU C Library: Shared libraries
grub-common recommends no packages.
Versions of packages grub-common suggests:
pn multiboot-doc <none> (no description available)
-- no debconf information
-- System Information:
Debian Release: lenny/sid
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.26-1-xen-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages grub-common depends on:
ii base-files 4.0.5 Debian base system miscellaneous f
ii libc6 2.7-14 GNU C Library: Shared libraries
grub-common recommends no packages.
Versions of packages grub-common suggests:
pn multiboot-doc <none> (no description available)
-- no debconf information
--- End Message ---
--- Begin Message ---
Source: grub2
Source-Version: 1.98+20100527-1
On Wed, Oct 06, 2010 at 02:39:33PM -0600, Daniel Fussell wrote:
> When doing kernel security updates, aptitude says update-grub failed with
> error 139.
> Checking other bug reports lead me to try grub-probe -vv -d /dev/system/root
> -t abstraction
> which works fine on my many logical volumes until it get to my root volume
> (/dev/system/root),
> where it segfaults.
This was fixed upstream in this commit:
2010-04-17 Vladimir Serbinenko <[email protected]>
* disk/lvm.c (grub_lvm_memberlist): Issue an error if pv->disk = 0.
... so it should be fixed in squeeze.
Thanks,
--
Colin Watson [[email protected]]
--- End Message ---
