Debian Bug report logs -
#586143
Doesn't boot: Unaligned pointer 4c191bea
Reported by: Guido Günther <agx@sigxcpu.org>
Date: Wed, 16 Jun 2010 19:21:05 UTC
Severity: critical
Merged with 586187,
586377
Found in versions grub2/1.98+20100614-1, grub2/1.98+20100614-2
Fixed in version grub2/1.98+20100617-1
Done: Colin Watson <cjwatson@debian.org>
Bug is archived. No further changes may be made.
Toggle useless messages
Report forwarded
to debian-bugs-dist@lists.debian.org, GRUB Maintainers <pkg-grub-devel@lists.alioth.debian.org>:
Bug#586143; Package grub-pc.
(Wed, 16 Jun 2010 19:21:08 GMT) (full text, mbox, link).
Acknowledgement sent
to Guido Günther <agx@sigxcpu.org>:
New Bug report received and forwarded. Copy sent to GRUB Maintainers <pkg-grub-devel@lists.alioth.debian.org>.
(Wed, 16 Jun 2010 19:21:08 GMT) (full text, mbox, link).
Message #5 received at submit@bugs.debian.org (full text, mbox, reply):
Package: grub-pc
Version: 1.98+20100614-1
Severity: critical
Hi,
after the upgrade:
grub-pc 1.98+20100527-2 1.98+20100614-1
system won't boot anymore. Grub prints:
Unaligned pointer 0x4c191bea - press any key
After pressing a key it says "No operation system found" - seems grub
quit. Downgrading to 1.98 and running grub-setup /dev/sda makes the
system boot again.
-- Guido
-- Package-specific info:
*********************** BEGIN /proc/mounts
/dev/mapper/vg_system-lv_root / ext3 rw,relatime,errors=remount-ro,barrier=0,data=writeback 0 0
/dev/sda3 /boot ext3 rw,relatime,errors=continue,barrier=0,data=writeback 0 0
/dev/mapper/vg_system-lv_home /home ext3 rw,relatime,errors=continue,barrier=0,data=writeback 0 0
/dev/mapper/vg_system-lv_scratch /var/scratch ext3 rw,relatime,errors=continue,barrier=0,data=writeback 0 0
*********************** END /proc/mounts
*********************** BEGIN /boot/grub/device.map
(hd0) /dev/sda
*********************** END /boot/grub/device.map
*********************** BEGIN /boot/grub/grub.cfg
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by /usr/sbin/grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#
### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
load_env
fi
set default="${saved_entry}"
if [ ${prev_saved_entry} ]; then
set saved_entry=${prev_saved_entry}
save_env saved_entry
set prev_saved_entry=
save_env prev_saved_entry
set boot_once=true
fi
function savedefault {
if [ -z ${boot_once} ]; then
saved_entry=${chosen}
save_env saved_entry
fi
}
insmod ext2
set root='(hd0,3)'
search --no-floppy --fs-uuid --set bd9e51e7-a624-447f-8a07-435456f3772c
if loadfont /grub/unicode.pf2 ; then
set gfxmode=640x480
insmod gfxterm
insmod vbe
if terminal_output gfxterm ; then true ; else
# For backward compatibility with versions of terminal.mod that don't
# understand terminal_output
terminal gfxterm
fi
fi
insmod ext2
set root='(hd0,3)'
search --no-floppy --fs-uuid --set bd9e51e7-a624-447f-8a07-435456f3772c
set locale_dir=($root)/grub/locale
set lang=
insmod gettext
set timeout=5
### END /etc/grub.d/00_header ###
### BEGIN /etc/grub.d/05_debian_theme ###
insmod ext2
set root='(hd0,3)'
search --no-floppy --fs-uuid --set bd9e51e7-a624-447f-8a07-435456f3772c
insmod png
if background_image /grub/moreblue-orbit-grub.png ; then
set color_normal=black/black
set color_highlight=magenta/black
else
set menu_color_normal=cyan/blue
set menu_color_highlight=white/blue
fi
### END /etc/grub.d/05_debian_theme ###
### BEGIN /etc/grub.d/10_linux ###
menuentry "Debian GNU/Linux, with Linux 2.6.35-rc3" --class debian --class gnu-linux --class gnu --class os {
insmod ext2
set root='(hd0,3)'
search --no-floppy --fs-uuid --set bd9e51e7-a624-447f-8a07-435456f3772c
echo Loading Linux 2.6.35-rc3 ...
linux /vmlinuz-2.6.35-rc3 root=/dev/mapper/vg_system-lv_root ro acpi_backlight=vendor splash i915.modeset=1 quiet
echo Loading initial ramdisk ...
initrd /initrd.img-2.6.35-rc3
}
menuentry "Debian GNU/Linux, with Linux 2.6.34" --class debian --class gnu-linux --class gnu --class os {
insmod ext2
set root='(hd0,3)'
search --no-floppy --fs-uuid --set bd9e51e7-a624-447f-8a07-435456f3772c
echo Loading Linux 2.6.34 ...
linux /vmlinuz-2.6.34 root=/dev/mapper/vg_system-lv_root ro acpi_backlight=vendor splash i915.modeset=1 quiet
echo Loading initial ramdisk ...
initrd /initrd.img-2.6.34
}
menuentry "Debian GNU/Linux, with Linux 2.6.33.1" --class debian --class gnu-linux --class gnu --class os {
insmod ext2
set root='(hd0,3)'
search --no-floppy --fs-uuid --set bd9e51e7-a624-447f-8a07-435456f3772c
echo Loading Linux 2.6.33.1 ...
linux /vmlinuz-2.6.33.1 root=/dev/mapper/vg_system-lv_root ro acpi_backlight=vendor splash i915.modeset=1 quiet
echo Loading initial ramdisk ...
initrd /initrd.img-2.6.33.1
}
menuentry "Debian GNU/Linux, with Linux 2.6.33" --class debian --class gnu-linux --class gnu --class os {
insmod ext2
set root='(hd0,3)'
search --no-floppy --fs-uuid --set bd9e51e7-a624-447f-8a07-435456f3772c
echo Loading Linux 2.6.33 ...
linux /vmlinuz-2.6.33 root=/dev/mapper/vg_system-lv_root ro acpi_backlight=vendor splash i915.modeset=1 quiet
echo Loading initial ramdisk ...
initrd /initrd.img-2.6.33
}
menuentry "Debian GNU/Linux, with Linux 2.6.32-5-686" --class debian --class gnu-linux --class gnu --class os {
insmod ext2
set root='(hd0,3)'
search --no-floppy --fs-uuid --set bd9e51e7-a624-447f-8a07-435456f3772c
echo Loading Linux 2.6.32-5-686 ...
linux /vmlinuz-2.6.32-5-686 root=/dev/mapper/vg_system-lv_root ro acpi_backlight=vendor splash i915.modeset=1 quiet
echo Loading initial ramdisk ...
initrd /initrd.img-2.6.32-5-686
}
### END /etc/grub.d/10_linux ###
### BEGIN /etc/grub.d/30_os-prober ###
### END /etc/grub.d/30_os-prober ###
### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.
### END /etc/grub.d/40_custom ###
### BEGIN /etc/grub.d/41_custom ###
if [ -f $prefix/custom.cfg ]; then
source $prefix/custom.cfg;
fi
### END /etc/grub.d/41_custom ###
*********************** END /boot/grub/grub.cfg
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.35-rc3 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages grub-pc depends on:
ii debconf [debconf-2.0] 1.5.32 Debian configuration management sy
ii grub-common 1.98-1 GRand Unified Bootloader, version
ii libc6 2.11.2-1 Embedded GNU C Library: Shared lib
ii ucf 3.0025 Update Configuration File: preserv
grub-pc recommends no packages.
Versions of packages grub-pc suggests:
ii desktop-base 5.0.5 common files for the Debian Deskto
-- debconf information:
grub2/kfreebsd_cmdline:
* grub2/linux_cmdline: acpi_backlight=vendor splash i915.modeset=1
* grub-pc/chainload_from_menu.lst: true
grub-pc/kopt_extracted: true
* grub-pc/install_devices: /dev/sda
grub-pc/postrm_purge_boot_grub: false
grub2/kfreebsd_cmdline_default: quiet
* grub2/linux_cmdline_default: quiet
Information forwarded
to debian-bugs-dist@lists.debian.org, GRUB Maintainers <pkg-grub-devel@lists.alioth.debian.org>:
Bug#586143; Package grub-pc.
(Wed, 16 Jun 2010 20:51:03 GMT) (full text, mbox, link).
Acknowledgement sent
to Colin Watson <cjwatson@debian.org>:
Extra info received and forwarded to list. Copy sent to GRUB Maintainers <pkg-grub-devel@lists.alioth.debian.org>.
(Wed, 16 Jun 2010 20:51:03 GMT) (full text, mbox, link).
Message #10 received at 586143@bugs.debian.org (full text, mbox, reply):
On Wed, Jun 16, 2010 at 09:17:10PM +0200, Guido Günther wrote:
> after the upgrade:
>
> grub-pc 1.98+20100527-2 1.98+20100614-1
>
> system won't boot anymore. Grub prints:
>
> Unaligned pointer 0x4c191bea - press any key
>
> After pressing a key it says "No operation system found" - seems grub
> quit. Downgrading to 1.98 and running grub-setup /dev/sda makes the
> system boot again.
(Don't use grub-setup directly; use grub-install.)
With 1.98+20100614-1, could you please temporarily apply this patch to
/usr/sbin/grub-install:
--- grub-install.orig 2010-06-04 17:56:55.000000000 +0100
+++ grub-install 2010-06-16 21:45:44.000000000 +0100
@@ -285,6 +285,9 @@
prefix_drive=
config_opt=
+echo 'set debug=all' > ${grubdir}/load.cfg
+config_opt="-c ${grubdir}/load.cfg "
+
if [ "x${devabstraction_module}" = "x" ] ; then
if [ x"${install_device}" != x ]; then
if echo "${install_device}" | grep -qx "(.*)" ; then
@@ -305,7 +308,7 @@
echo "UUID needed with ata mod, but the filesystem containing ${grubdir} does not support UUIDs." 1>&2
exit 1
fi
- echo "search.fs_uuid ${uuid} root " > ${grubdir}/load.cfg
+ echo "search.fs_uuid ${uuid} root " >> ${grubdir}/load.cfg
echo 'set prefix=($root)'"${relative_grubdir}" >> ${grubdir}/load.cfg
config_opt="-c ${grubdir}/load.cfg "
modules="$modules search_fs_uuid"
@@ -315,7 +318,7 @@
echo "You attempted a cross-disk install, but the filesystem containing ${grubdir} does not support UUIDs." 1>&2
exit 1
fi
- echo "search.fs_uuid ${uuid} root " > ${grubdir}/load.cfg
+ echo "search.fs_uuid ${uuid} root " >> ${grubdir}/load.cfg
echo 'set prefix=($root)'"${relative_grubdir}" >> ${grubdir}/load.cfg
config_opt="-c ${grubdir}/load.cfg "
modules="$modules search_fs_uuid"
Then run 'grub-install /dev/sda', reboot, and show me as much of the
output as you can, and certainly the end of it. Hopefully it's failing
late enough for this to be useful!
Thanks,
--
Colin Watson [cjwatson@debian.org]
Information forwarded
to debian-bugs-dist@lists.debian.org, GRUB Maintainers <pkg-grub-devel@lists.alioth.debian.org>:
Bug#586143; Package grub-pc.
(Thu, 17 Jun 2010 13:03:02 GMT) (full text, mbox, link).
Acknowledgement sent
to Jeff Wallace <jeff@tjwallace.ca>:
Extra info received and forwarded to list. Copy sent to GRUB Maintainers <pkg-grub-devel@lists.alioth.debian.org>.
(Thu, 17 Jun 2010 13:03:02 GMT) (full text, mbox, link).
Message #15 received at 586143@bugs.debian.org (full text, mbox, reply):
[Message part 1 (text/plain, inline)]
I also have the same problem. I see "unaligned pointer 0x4c12b6ea" when
booting. After restarting 2 times I was able to boot grub properly and get
into Debian.
[Message part 2 (text/html, inline)]
Information forwarded
to debian-bugs-dist@lists.debian.org, GRUB Maintainers <pkg-grub-devel@lists.alioth.debian.org>:
Bug#586143; Package grub-pc.
(Thu, 17 Jun 2010 16:21:03 GMT) (full text, mbox, link).
Acknowledgement sent
to bjb@linuxbutler.ca:
Extra info received and forwarded to list. Copy sent to GRUB Maintainers <pkg-grub-devel@lists.alioth.debian.org>.
(Thu, 17 Jun 2010 16:21:03 GMT) (full text, mbox, link).
Message #20 received at 586143@bugs.debian.org (full text, mbox, reply):
With grub-pc 1.98+20100614-2,
I had the same failure, with unaligned pointer 0x4c19a146.
This occurred before any other output to the screen by
grub. No menu, no shell, nothing.
downgraded to
grub-pc 1.98+20100602-2 (and grub-common 1.98+20100602-2)
and the problem went away.
The problem occurred after an upgrade from
grub-pc (and grub-common) 1.98+20100602-2 to 1.98+20100614-2.
This was on a Thinkpad T43.
bjb
Information forwarded
to debian-bugs-dist@lists.debian.org, GRUB Maintainers <pkg-grub-devel@lists.alioth.debian.org>:
Bug#586143; Package grub-pc.
(Thu, 17 Jun 2010 16:54:13 GMT) (full text, mbox, link).
Acknowledgement sent
to Frederik Schwarzer <schwarzerf@gmail.com>:
Extra info received and forwarded to list. Copy sent to GRUB Maintainers <pkg-grub-devel@lists.alioth.debian.org>.
(Thu, 17 Jun 2010 16:54:13 GMT) (full text, mbox, link).
Message #25 received at 586143@bugs.debian.org (full text, mbox, reply):
Hi,
the patch from message #10 fixed this for me.
I applied the changes, ran "grub-setup /dev/sda" and rebooted.
Regards
Information forwarded
to debian-bugs-dist@lists.debian.org, GRUB Maintainers <pkg-grub-devel@lists.alioth.debian.org>:
Bug#586143; Package grub-pc.
(Thu, 17 Jun 2010 17:21:08 GMT) (full text, mbox, link).
Acknowledgement sent
to Colin Watson <cjwatson@debian.org>:
Extra info received and forwarded to list. Copy sent to GRUB Maintainers <pkg-grub-devel@lists.alioth.debian.org>.
(Thu, 17 Jun 2010 17:21:08 GMT) (full text, mbox, link).
Message #30 received at 586143@bugs.debian.org (full text, mbox, reply):
On Thu, Jun 17, 2010 at 06:45:26PM +0200, Frederik Schwarzer wrote:
> the patch from message #10 fixed this for me.
Argh! It wasn't meant to fix it, it was meant to gather more
information ...
> I applied the changes, ran "grub-setup /dev/sda" and rebooted.
The instructions in message #10 were to run 'grub-install /dev/sda', not
'grub-setup /dev/sda'; grub-setup is not normally intended to be used
directly. Could you please try with grub-install instead?
Thanks,
--
Colin Watson [cjwatson@debian.org]
Information forwarded
to debian-bugs-dist@lists.debian.org, GRUB Maintainers <pkg-grub-devel@lists.alioth.debian.org>:
Bug#586143; Package grub-pc.
(Thu, 17 Jun 2010 19:51:03 GMT) (full text, mbox, link).
Acknowledgement sent
to bsimon1 <bsimon1@cox.net>:
Extra info received and forwarded to list. Copy sent to GRUB Maintainers <pkg-grub-devel@lists.alioth.debian.org>.
(Thu, 17 Jun 2010 19:51:03 GMT) (full text, mbox, link).
Message #35 received at 586143@bugs.debian.org (full text, mbox, reply):
[Message part 1 (text/plain, inline)]
Apparently, an update went in without grub being put back on the boot sector
(therefore, the pointer error). I ran into the same problem and, in the end,
was able to fix it simply by running grub-install.
[Message part 2 (text/html, inline)]
Information forwarded
to debian-bugs-dist@lists.debian.org, GRUB Maintainers <pkg-grub-devel@lists.alioth.debian.org>:
Bug#586143; Package grub-pc.
(Thu, 17 Jun 2010 20:03:09 GMT) (full text, mbox, link).
Acknowledgement sent
to Jeffrey G Thomas <Jeffrey.Thomas@sierra-bravo.com>:
Extra info received and forwarded to list. Copy sent to GRUB Maintainers <pkg-grub-devel@lists.alioth.debian.org>.
(Thu, 17 Jun 2010 20:03:09 GMT) (full text, mbox, link).
Message #40 received at 586143@bugs.debian.org (full text, mbox, reply):
[Message part 1 (text/plain, inline)]
Echoing Guido, I had the same issue with both of these:
> grub-pc 1.98+20100614-1
> grub-pc 1.98+20100614-2
And my system won't boot anymore. Grub reads:
> Unaligned pointer 0x4c194c76 - press any key
After pressing a key it says "No operation system found"
I don't even have a chance to edit the Grub boot line :(
Downgrading to 1.98 (testing) and running:
> grub-setup /dev/sda
makes it all work.
Suggestions to run:
> 'grub-install /dev/sda'
fails with:
> '/usr/bin/grub-mkimage: Not found.'
Jeffrey
[signature.asc (application/pgp-signature, inline)]
Information forwarded
to debian-bugs-dist@lists.debian.org, GRUB Maintainers <pkg-grub-devel@lists.alioth.debian.org>:
Bug#586143; Package grub-pc.
(Thu, 17 Jun 2010 20:21:03 GMT) (full text, mbox, link).
Acknowledgement sent
to Colin Watson <cjwatson@debian.org>:
Extra info received and forwarded to list. Copy sent to GRUB Maintainers <pkg-grub-devel@lists.alioth.debian.org>.
(Thu, 17 Jun 2010 20:21:03 GMT) (full text, mbox, link).
Message #45 received at 586143@bugs.debian.org (full text, mbox, reply):
On Thu, Jun 17, 2010 at 03:01:43PM -0500, Jeffrey G Thomas wrote:
> Downgrading to 1.98 (testing) and running:
> > grub-setup /dev/sda
> makes it all work.
grub-setup should not be run directly. If you get into the habit of
doing this you should expect it to break at some point.
> Suggestions to run:
> > 'grub-install /dev/sda'
> fails with:
> > '/usr/bin/grub-mkimage: Not found.'
... so you'll definitely have to fix that! That's not good news and I
wouldn't recommend leaving your system that way. I think the downgrade
has probably been botched somehow, since in 1.98-1 grub-mkimage lived in
the grub-pc package but in more recent versions it lives in grub-common.
Regards,
--
Colin Watson [cjwatson@debian.org]
Information forwarded
to debian-bugs-dist@lists.debian.org, GRUB Maintainers <pkg-grub-devel@lists.alioth.debian.org>:
Bug#586143; Package grub-pc.
(Thu, 17 Jun 2010 20:21:05 GMT) (full text, mbox, link).
Acknowledgement sent
to Andreas Jacob <andreasjacob@gmx.de>:
Extra info received and forwarded to list. Copy sent to GRUB Maintainers <pkg-grub-devel@lists.alioth.debian.org>.
(Thu, 17 Jun 2010 20:21:05 GMT) (full text, mbox, link).
Message #50 received at 586143@bugs.debian.org (full text, mbox, reply):
I run also in these problem. And like bsimon1 sayed, a grub-install
did fix the problem. I assume, that there could be a problem with the
update-script which leaves grub stalled. I checked
/var/log/apt/term.log, and there where no error-message when updating
grub.
Cheers Andreas
Information forwarded
to debian-bugs-dist@lists.debian.org, GRUB Maintainers <pkg-grub-devel@lists.alioth.debian.org>:
Bug#586143; Package grub-pc.
(Thu, 17 Jun 2010 20:51:05 GMT) (full text, mbox, link).
Acknowledgement sent
to Colin Watson <cjwatson@debian.org>:
Extra info received and forwarded to list. Copy sent to GRUB Maintainers <pkg-grub-devel@lists.alioth.debian.org>.
(Thu, 17 Jun 2010 20:51:05 GMT) (full text, mbox, link).
Message #55 received at 586143@bugs.debian.org (full text, mbox, reply):
On Thu, Jun 17, 2010 at 10:02:26PM +0200, Andreas Jacob wrote:
> I run also in these problem. And like bsimon1 sayed, a grub-install
> did fix the problem. I assume, that there could be a problem with the
> update-script which leaves grub stalled. I checked
> /var/log/apt/term.log, and there where no error-message when updating
> grub.
Could you attach the output of 'debconf-show grub-pc' (run as root) and
the contents of /proc/mounts, please?
It has long been the case that if you don't run grub-install on upgrade,
or if you run it on the wrong device, then you'll run into problems.
It's beginning to sound like this is just another duplicate of that
general class of problem, although it's slightly surprising that we're
getting so many of them all of a sudden. Perhaps this is due to
Vladimir's iterator changes on 2010-06-10 changing the ABI between
kernel and modules.
--
Colin Watson [cjwatson@debian.org]
Information forwarded
to debian-bugs-dist@lists.debian.org, GRUB Maintainers <pkg-grub-devel@lists.alioth.debian.org>:
Bug#586143; Package grub-pc.
(Thu, 17 Jun 2010 20:57:04 GMT) (full text, mbox, link).
Acknowledgement sent
to Jeffrey G Thomas <Jeffrey.Thomas@sierra-bravo.com>:
Extra info received and forwarded to list. Copy sent to GRUB Maintainers <pkg-grub-devel@lists.alioth.debian.org>.
(Thu, 17 Jun 2010 20:57:04 GMT) (full text, mbox, link).
Message #60 received at 586143@bugs.debian.org (full text, mbox, reply):
[Message part 1 (text/plain, inline)]
> grub-setup should not be run directly. If you get into the habit of
> doing this you should expect it to break at some point.
In theory, I shouldn't need to make a habit of this :)
> I think the downgrade
> has probably been botched somehow, since in 1.98-1 grub-mkimage lived in
> the grub-pc package but in more recent versions it lives in grub-common
The downgrade downgraded both the grub-pc and grub-common packages so it should have worked, no?
Jeffrey
[signature.asc (application/pgp-signature, inline)]
Information forwarded
to debian-bugs-dist@lists.debian.org, GRUB Maintainers <pkg-grub-devel@lists.alioth.debian.org>:
Bug#586143; Package grub-pc.
(Thu, 17 Jun 2010 21:00:04 GMT) (full text, mbox, link).
Acknowledgement sent
to Colin Watson <cjwatson@debian.org>:
Extra info received and forwarded to list. Copy sent to GRUB Maintainers <pkg-grub-devel@lists.alioth.debian.org>.
(Thu, 17 Jun 2010 21:00:04 GMT) (full text, mbox, link).
Message #65 received at 586143@bugs.debian.org (full text, mbox, reply):
On Thu, Jun 17, 2010 at 03:52:14PM -0500, Jeffrey G Thomas wrote:
> > grub-setup should not be run directly. If you get into the habit of
> > doing this you should expect it to break at some point.
>
> In theory, I shouldn't need to make a habit of this :)
>
> > I think the downgrade
> > has probably been botched somehow, since in 1.98-1 grub-mkimage lived in
> > the grub-pc package but in more recent versions it lives in grub-common
>
> The downgrade downgraded both the grub-pc and grub-common packages so
> it should have worked, no?
Ideally, but evidently not. Downgrades are sometimes a bit hairy,
particularly when files have moved around. I suggest reinstalling
grub-common.
--
Colin Watson [cjwatson@debian.org]
Information forwarded
to debian-bugs-dist@lists.debian.org, GRUB Maintainers <pkg-grub-devel@lists.alioth.debian.org>:
Bug#586143; Package grub-pc.
(Thu, 17 Jun 2010 21:12:03 GMT) (full text, mbox, link).
Acknowledgement sent
to Andreas Jacob <andreasjacob@gmx.de>:
Extra info received and forwarded to list. Copy sent to GRUB Maintainers <pkg-grub-devel@lists.alioth.debian.org>.
(Thu, 17 Jun 2010 21:12:04 GMT) (full text, mbox, link).
Message #70 received at 586143@bugs.debian.org (full text, mbox, reply):
debconf-show grub-pc :
grub2/kfreebsd_cmdline:
* grub2/linux_cmdline:
* grub-pc/chainload_from_menu.lst: true
grub-pc/kopt_extracted: false
grub-pc/postrm_purge_boot_grub: false
grub2/kfreebsd_cmdline_default: quiet
* grub2/linux_cmdline_default: quiet
* grub-pc/install_devices: /dev/sda
cat /proc/mounts
rootfs / rootfs rw 0 0
none /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0
none /proc proc rw,nosuid,nodev,noexec,relatime 0 0
none /dev devtmpfs rw,relatime,size=1668512k,nr_inodes=417128,mode=755 0 0
none /dev/pts devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 0 0
/dev/mapper/vgworf-lvrootdir / ext3
rw,relatime,errors=remount-ro,data=ordered 0 0
tmpfs /lib/init/rw tmpfs rw,nosuid,relatime,mode=755 0 0
tmpfs /dev/shm tmpfs rw,nosuid,nodev,relatime 0 0
/dev/mapper/vgworf-lvvar /var ext3
rw,relatime,errors=remount-ro,data=ordered 0 0
/dev/mapper/vgworf-lvusr /usr ext3
rw,relatime,errors=remount-ro,data=ordered 0 0
/dev/mapper/vgworf-lvroot /root ext3
rw,relatime,errors=remount-ro,data=ordered 0 0
/dev/mapper/vgworf-lvtmp /tmp ext3
rw,relatime,errors=remount-ro,data=ordered 0 0
/dev/mapper/vgworf-lvhome /home ext3
rw,relatime,errors=remount-ro,data=ordered 0 0
/dev/mapper/vgworf-lvvm /var/lib/libvirt ext3
rw,relatime,errors=remount-ro,data=ordered 0 0
/dev/sda3 /boot ext3 rw,relatime,errors=remount-ro,data=ordered 0 0
/dev/mapper/vgworf-lvsupport /mnt/support ext3
rw,relatime,errors=remount-ro,data=ordered 0 0
fusectl /sys/fs/fuse/connections fusectl rw,relatime 0 0
binfmt_misc /proc/sys/fs/binfmt_misc binfmt_misc
rw,nosuid,nodev,noexec,relatime 0 0
If it helps, some notes about my setup:
- My setup is based on an Luks crypted LVM2 partition (sda5).
- Also the rootdirectory lies as logical volume within the crypted LVM2
Cheers Andreas
Information forwarded
to debian-bugs-dist@lists.debian.org, GRUB Maintainers <pkg-grub-devel@lists.alioth.debian.org>:
Bug#586143; Package grub-pc.
(Thu, 17 Jun 2010 21:45:03 GMT) (full text, mbox, link).
Acknowledgement sent
to Andreas Jacob <andreasjacob@gmx.de>:
Extra info received and forwarded to list. Copy sent to GRUB Maintainers <pkg-grub-devel@lists.alioth.debian.org>.
(Thu, 17 Jun 2010 21:45:03 GMT) (full text, mbox, link).
Message #75 received at 586143@bugs.debian.org (full text, mbox, reply):
May be these information about my setup are also helpfull:
blkid:
/dev/sda2: UUID="F86C05696C0523CA" LABEL="System" TYPE="ntfs"
/dev/sda1: UUID="92A8D1D6A8D1B945" LABEL="WINRE" TYPE="ntfs"
/dev/sda3: UUID="62421195-3682-43bb-a335-11939005e9ba" TYPE="ext3" LABEL="boot"
/dev/sda5: UUID="777465a6-c5be-4c5c-b380-8b35b249904a" TYPE="crypto_LUKS"
/dev/mapper/lukssda5: UUID="yB8zfZ-TnM5-HiSY-KQRK-V3Qt-WqDc-1AZWrN"
TYPE="LVM2_member"
/dev/mapper/vgworf-lvhome: UUID="393b6854-14e8-4924-9dc1-b20eb6fbcd43"
TYPE="ext3"
/dev/mapper/vgworf-lvrootdir:
UUID="41b1c2c2-f109-420f-aec7-4f3d82836830" TYPE="ext3"
/dev/mapper/vgworf-lvusr: UUID="3bc14fd2-2eda-49de-ab35-91047a2326b5"
TYPE="ext3"
/dev/mapper/vgworf-lvvm: UUID="7a44be97-0428-4887-9b84-bf79f74f4ca0"
SEC_TYPE="ext2" TYPE="ext3"
/dev/mapper/vgworf-lvvar: UUID="238d66bc-518a-4fcf-9e6f-7ebf5dbfebd2"
TYPE="ext3"
/dev/mapper/vgworf-lvtmp: UUID="09692ded-2c76-4b08-8125-0bbdfcc1fb2d"
TYPE="ext3"
/dev/mapper/vgworf-lvroot: UUID="ff8c7f5a-97d1-4523-aa53-613d65233b7b"
TYPE="ext3"
/dev/mapper/vgworf-lvswap: UUID="297e5ad3-f92c-47ae-ac20-779f6f656de8"
TYPE="swap"
/dev/mapper/vgworf-lvsupport:
UUID="1db76830-fa09-409c-9fb8-ffd6f8e59309" SEC_TYPE="ext2"
TYPE="ext3"
fstab:
proc /proc proc defaults 0 0
UUID=41b1c2c2-f109-420f-aec7-4f3d82836830 / ext3
defaults,errors=remount-ro 0 1
UUID=238d66bc-518a-4fcf-9e6f-7ebf5dbfebd2 /var ext3
defaults,errors=remount-ro 0 1
UUID=3bc14fd2-2eda-49de-ab35-91047a2326b5 /usr ext3
defaults,errors=remount-ro 0 1
UUID=ff8c7f5a-97d1-4523-aa53-613d65233b7b /root ext3
defaults,errors=remount-ro 0 1
UUID=09692ded-2c76-4b08-8125-0bbdfcc1fb2d /tmp ext3
defaults,errors=remount-ro 0 1
UUID=393b6854-14e8-4924-9dc1-b20eb6fbcd43 /home ext3
defaults,errors=remount-ro 0 1
UUID=7a44be97-0428-4887-9b84-bf79f74f4ca0 /var/lib/libvirt
ext3 defaults,errors=remount-ro 0 1
UUID=62421195-3682-43bb-a335-11939005e9ba /boot ext3
defaults,errors=remount-ro 0 1
UUID=1db76830-fa09-409c-9fb8-ffd6f8e59309 /mnt/support ext3
defaults,errors=remount-ro 0 1
UUID=297e5ad3-f92c-47ae-ac20-779f6f656de8 none swap
sw 0 0
/dev/cdrom3 /media/cdrom0 udf,iso9660 user,noauto 0 0
UUID=F86C05696C0523CA /mnt/windows auto user,noauto 0 0
Cheers Andreas
Information forwarded
to debian-bugs-dist@lists.debian.org, GRUB Maintainers <pkg-grub-devel@lists.alioth.debian.org>:
Bug#586143; Package grub-pc.
(Fri, 18 Jun 2010 00:48:06 GMT) (full text, mbox, link).
Acknowledgement sent
to André Nunes <dede.mathias@gmail.com>:
Extra info received and forwarded to list. Copy sent to GRUB Maintainers <pkg-grub-devel@lists.alioth.debian.org>.
(Fri, 18 Jun 2010 00:48:06 GMT) (full text, mbox, link).
Message #80 received at 586143@bugs.debian.org (full text, mbox, reply):
[Message part 1 (text/plain, inline)]
Same problem here, bur a little bit worse: I can't get my system back! I
tryed to aptitude downgrade grub-pc and grub-common to 1.98-1 and also to
grub-legacy, but I keep getting the same error:
/usr/sbin/grub-probe: error: no mapping exists for tagesuhu-root
Auto-detection of a filesystem module failed
Please specify the module with the option '--modules' explicitly
My system is encrypted with dm-crypt and luks, only the boot partition is
left unencrypted.
Also, during aptitude update, I get a lot of messages regarding perl not
being able to read my locale settings
Any help just to get the system up?
André Nunes Batista
Blog: http://tagesuhu.wordpress.com/
PGP Public Key: 0x7b0590cb6722cf80
[Message part 2 (text/html, inline)]
Information forwarded
to debian-bugs-dist@lists.debian.org, GRUB Maintainers <pkg-grub-devel@lists.alioth.debian.org>:
Bug#586143; Package grub-pc.
(Fri, 18 Jun 2010 11:06:12 GMT) (full text, mbox, link).
Acknowledgement sent
to Colin Watson <cjwatson@debian.org>:
Extra info received and forwarded to list. Copy sent to GRUB Maintainers <pkg-grub-devel@lists.alioth.debian.org>.
(Fri, 18 Jun 2010 11:06:12 GMT) (full text, mbox, link).
Message #85 received at 586143@bugs.debian.org (full text, mbox, reply):
On Thu, Jun 17, 2010 at 09:44:26PM -0300, André Nunes wrote:
> Same problem here, bur a little bit worse: I can't get my system back! I
> tryed to aptitude downgrade grub-pc and grub-common to 1.98-1 and also to
> grub-legacy, but I keep getting the same error:
Even though everyone in this bug log seems to be doing this, it's
unlikely actually to be the best idea, and it certainly won't help to
resolve this bug. Try upgrading again; record the output from the
upgrade, and send it to me; and if you see the problem again, get the
value of grub-pc/install_devices using 'debconf-show grub-pc', and try
running 'grub-install /dev/sda' (replacing /dev/sda with the value of
grub-pc/install_devices') to see if that fixes it, as others have
reported.
What I really need is a way to replicate this. I've tried LVM and
LVM+crypto installs in a virtual machine, upgraded to the latest version
of grub-common and grub-pc, and so far have been unable to recreate
this.
> /usr/sbin/grub-probe: error: no mapping exists for tagesuhu-root
... probably because downgrading to 1.98-1 loses a bunch of other fixes
that are relevant for LVM ...
--
Colin Watson [cjwatson@debian.org]
Information forwarded
to debian-bugs-dist@lists.debian.org, GRUB Maintainers <pkg-grub-devel@lists.alioth.debian.org>:
Bug#586143; Package grub-pc.
(Fri, 18 Jun 2010 12:03:06 GMT) (full text, mbox, link).
Acknowledgement sent
to Salvatore Bonaccorso <salvatore.bonaccorso@gmail.com>:
Extra info received and forwarded to list. Copy sent to GRUB Maintainers <pkg-grub-devel@lists.alioth.debian.org>.
(Fri, 18 Jun 2010 12:03:06 GMT) (full text, mbox, link).
Message #90 received at 586143@bugs.debian.org (full text, mbox, reply):
[Message part 1 (text/plain, inline)]
Hi Colin
I'm not the original reporter but experience the similar problem,
getting 'unaligned pointer 0x4c1b0297'. I tried to collect the
information you requested for that:
On Fri, Jun 18, 2010 at 12:04:15PM +0100, Colin Watson wrote:
> On Thu, Jun 17, 2010 at 09:44:26PM -0300, André Nunes wrote:
> > Same problem here, bur a little bit worse: I can't get my system back! I
> > tryed to aptitude downgrade grub-pc and grub-common to 1.98-1 and also to
> > grub-legacy, but I keep getting the same error:
>
> Even though everyone in this bug log seems to be doing this, it's
> unlikely actually to be the best idea, and it certainly won't help to
> resolve this bug. Try upgrading again; record the output from the
> upgrade, and send it to me; and if you see the problem again, get the
> value of grub-pc/install_devices using 'debconf-show grub-pc', and try
> running 'grub-install /dev/sda' (replacing /dev/sda with the value of
> grub-pc/install_devices') to see if that fixes it, as others have
> reported.
Here is the output of the upgrade:
---(upgrade)------------------------------------------------------------
eldamar:~# aptitude -D -V -v --purge-unused install grub-pc grub-common
Reading package lists... Done
Building dependency tree
Reading state information... Done
Reading extended state information... Done
Initializing package states... Done
Reading task descriptions... Done
The following packages will be upgraded:
grub-common [1.98+20100602-2 -> 1.98+20100614-2] grub-pc [1.98+20100602-2 -> 1.98+20100614-2]
2 packages upgraded, 0 newly installed, 0 to remove and 33 not upgraded.
Need to get 0B/2,532kB of archives. After unpacking 1,282kB will be used.
Do you want to continue? [Y/n/?] y
Writing extended state information... Done
Reading package fields... Done
Reading package status... Done
Retrieving bug reports... Done
Parsing Found/Fixed information... Done
critical bugs of grub-pc (1.98+20100602-2 -> 1.98+20100614-2) <unfixed>
#586143 - Doesn't boot: Unaligned pointer 4c191bea
Summary:
grub-pc(1 bug)
Are you sure you want to install/upgrade the above packages? [Y/n/?/...] y
Reading changelogs... Done
Preconfiguring packages ...
(Reading database ... 159789 files and directories currently installed.)
Preparing to replace grub-pc 1.98+20100602-2 (using .../grub-pc_1.98+20100614-2_i386.deb) ...
Unpacking replacement grub-pc ...
Preparing to replace grub-common 1.98+20100602-2 (using .../grub-common_1.98+20100614-2_i386.deb) ...
Unpacking replacement grub-common ...
Processing triggers for man-db ...
Processing triggers for install-info ...
Setting up grub-common (1.98+20100614-2) ...
Installing new version of config file /etc/grub.d/00_header ...
Installing new version of config file /etc/grub.d/10_linux ...
Setting up grub-pc (1.98+20100614-2) ...
Installing new version of config file /etc/grub.d/05_debian_theme ...
Generating core.img
Saving menu.lst backup in /boot/grub/menu.lst_backup_by_grub2_postinst
Running update-grub Legacy to hook our core.img in it
Searching for GRUB installation directory ... found: /boot/grub
Searching for default file ... found: /boot/grub/default
Testing for an existing GRUB menu.lst file ... found: /boot/grub/menu.lst
Searching for splash image ... none found, skipping ...
Found GRUB 2: /boot/grub/core.img
Found kernel: /boot/vmlinuz-2.6.32-5-686
Found kernel: /boot/vmlinuz-2.6.32-4-686
Found kernel: /boot/vmlinuz-2.6.32-2-686
Updating /boot/grub/menu.lst ... done
Generating grub.cfg ...
Found background image: moreblue-orbit-grub.png
Found linux image: /boot/vmlinuz-2.6.32-5-686
Found initrd image: /boot/initrd.img-2.6.32-5-686
Found linux image: /boot/vmlinuz-2.6.32-4-686
Found initrd image: /boot/initrd.img-2.6.32-4-686
Found linux image: /boot/vmlinuz-2.6.32-2-686
Found initrd image: /boot/initrd.img-2.6.32-2-686
done
Reading package lists... Done
Building dependency tree
Reading state information... Done
Reading extended state information... Done
Initializing package states... Done
Reading task descriptions... Done
Current status: 0 broken [+0], 33 updates [-2], 29436 new [+0].
eldamar:~#
------------------------------------------------------------------------
The debconf values are the following:
---(debconf)------------------------------------------------------------
grub2/kfreebsd_cmdline:
* grub2/linux_cmdline:
* grub-pc/chainload_from_menu.lst: true
grub-pc/kopt_extracted: true
* grub-pc/install_devices: /dev/sda
grub-pc/postrm_purge_boot_grub: false
grub2/kfreebsd_cmdline_default: quiet
* grub2/linux_cmdline_default:
------------------------------------------------------------------------
The machine bootet up showing the above error message. Then I bootet
into live-cd, moutet proc, /dev/sda1 and /dev into chroot and
re-run dpkg-reconfigure -plow grub-pc and run grub-install /dev/sda:
grub-install on /dev/sda in a chroot says 'Installation finished. No
error reported'.
After that the machine bootet correctly! Do you need some other
information?
Bests
Salvatore
[signature.asc (application/pgp-signature, inline)]
Information forwarded
to debian-bugs-dist@lists.debian.org, GRUB Maintainers <pkg-grub-devel@lists.alioth.debian.org>:
Bug#586143; Package grub-pc.
(Fri, 18 Jun 2010 12:12:15 GMT) (full text, mbox, link).
Acknowledgement sent
to Colin Watson <cjwatson@debian.org>:
Extra info received and forwarded to list. Copy sent to GRUB Maintainers <pkg-grub-devel@lists.alioth.debian.org>.
(Fri, 18 Jun 2010 12:12:15 GMT) (full text, mbox, link).
Message #95 received at 586143@bugs.debian.org (full text, mbox, reply):
On Fri, Jun 18, 2010 at 01:59:15PM +0200, Salvatore Bonaccorso wrote:
> I'm not the original reporter but experience the similar problem,
> getting 'unaligned pointer 0x4c1b0297'. I tried to collect the
> information you requested for that:
Thanks. This is the most interesting part:
> Generating core.img
> Saving menu.lst backup in /boot/grub/menu.lst_backup_by_grub2_postinst
> Running update-grub Legacy to hook our core.img in it
[...]
I've just gone through an extensive debugging session with an affected
user on IRC who had the same symptom (thanks, dileX), and I believe I
understand the problem now. I would like to confirm one fact with the
people who have contributed to this bug report so far, namely:
Does the file /boot/grub/stage2 exist on your system?
I strongly suspect at this point that that will be the case for all of
you, and if that's the case then I know what to do.
Thanks,
--
Colin Watson [cjwatson@debian.org]
Information forwarded
to debian-bugs-dist@lists.debian.org, GRUB Maintainers <pkg-grub-devel@lists.alioth.debian.org>:
Bug#586143; Package grub-pc.
(Fri, 18 Jun 2010 12:33:05 GMT) (full text, mbox, link).
Acknowledgement sent
to Andreas Jacob <andreasjacob@gmx.de>:
Extra info received and forwarded to list. Copy sent to GRUB Maintainers <pkg-grub-devel@lists.alioth.debian.org>.
(Fri, 18 Jun 2010 12:33:05 GMT) (full text, mbox, link).
Message #100 received at 586143@bugs.debian.org (full text, mbox, reply):
Nope, the file /boot/grub/stage2 is actually (system works) not
present in the given directory, or elsewhere under /boot.
Cheers Andreas
Information forwarded
to debian-bugs-dist@lists.debian.org, GRUB Maintainers <pkg-grub-devel@lists.alioth.debian.org>:
Bug#586143; Package grub-pc.
(Fri, 18 Jun 2010 12:51:03 GMT) (full text, mbox, link).
Acknowledgement sent
to Salvatore Bonaccorso <salvatore.bonaccorso@gmail.com>:
Extra info received and forwarded to list. Copy sent to GRUB Maintainers <pkg-grub-devel@lists.alioth.debian.org>.
(Fri, 18 Jun 2010 12:51:03 GMT) (full text, mbox, link).
Message #105 received at 586143@bugs.debian.org (full text, mbox, reply):
[Message part 1 (text/plain, inline)]
Hi
On Fri, Jun 18, 2010 at 01:10:42PM +0100, Colin Watson wrote:
> On Fri, Jun 18, 2010 at 01:59:15PM +0200, Salvatore Bonaccorso wrote:
> > I'm not the original reporter but experience the similar problem,
> > getting 'unaligned pointer 0x4c1b0297'. I tried to collect the
> > information you requested for that:
>
> Thanks. This is the most interesting part:
>
> > Generating core.img
> > Saving menu.lst backup in /boot/grub/menu.lst_backup_by_grub2_postinst
> > Running update-grub Legacy to hook our core.img in it
> [...]
>
> I've just gone through an extensive debugging session with an affected
> user on IRC who had the same symptom (thanks, dileX), and I believe I
> understand the problem now. I would like to confirm one fact with the
> people who have contributed to this bug report so far, namely:
>
> Does the file /boot/grub/stage2 exist on your system?
>
> I strongly suspect at this point that that will be the case for all of
> you, and if that's the case then I know what to do.
Yes I can confirm: /boot/grub/stage2 exists on the problematic hosts!
Thanks for your work, Colin
Bests
Salvatore
[signature.asc (application/pgp-signature, inline)]
Information forwarded
to debian-bugs-dist@lists.debian.org, GRUB Maintainers <pkg-grub-devel@lists.alioth.debian.org>:
Bug#586143; Package grub-pc.
(Fri, 18 Jun 2010 13:36:03 GMT) (full text, mbox, link).
Acknowledgement sent
to Dominique Dumont <dominique.dumont@hp.com>:
Extra info received and forwarded to list. Copy sent to GRUB Maintainers <pkg-grub-devel@lists.alioth.debian.org>.
(Fri, 18 Jun 2010 13:36:03 GMT) (full text, mbox, link).
Message #110 received at 586143@bugs.debian.org (full text, mbox, reply):
Hello
I can confirm that I have /boot/grub/stage2 on a non-booting laptop.
With system-rescuecd, I've moved stage2 in stage2.bak, but this is not enough
to fix the problem.
For other googlers, here's how I fixed my laptop:
- boot systemrescuecd
- mount -t ext3 /dev/sda2 /mnt/custom/dev
- mount --bind /proc /mnt/custom/proc
- mount --bind /dev/ /mnt/custom/dev
- chroot /mnt/custom bin/bash
- grub-install /dev/sda
After that, my laptop rebooted without problem.
Of course, you'll have to use the correct device file for your system (i.e.
replace /dev/sda2 with the device contains your root partition).
Hope this helps
Dominique
--
http://config-model.wiki.sourceforge.net/ -o- http://search.cpan.org/~ddumont/
http://www.ohloh.net/accounts/ddumont
Information forwarded
to debian-bugs-dist@lists.debian.org, GRUB Maintainers <pkg-grub-devel@lists.alioth.debian.org>:
Bug#586143; Package grub-pc.
(Fri, 18 Jun 2010 14:21:08 GMT) (full text, mbox, link).
Acknowledgement sent
to sedat.dilek@gmail.com:
Extra info received and forwarded to list. Copy sent to GRUB Maintainers <pkg-grub-devel@lists.alioth.debian.org>.
(Fri, 18 Jun 2010 14:21:08 GMT) (full text, mbox, link).
Message #115 received at 586143@bugs.debian.org (full text, mbox, reply):
Hi Dominique,
I tried to reproduce on how to fix the problem: You have a little
typo, here are the correct steps:
1. boot systemrescuecd
2. mount -t ext3 /dev/sda2 /mnt/custom <--- TYPO
3. mount --bind /proc /mnt/custom/proc
4. mount --bind /dev/ /mnt/custom/dev
5. chroot /mnt/custom bin/bash
6. grub-install /dev/sda
Kind Regards,
- Sedat -
Information forwarded
to debian-bugs-dist@lists.debian.org, GRUB Maintainers <pkg-grub-devel@lists.alioth.debian.org>:
Bug#586143; Package grub-pc.
(Fri, 18 Jun 2010 14:33:04 GMT) (full text, mbox, link).
Acknowledgement sent
to sedat.dilek@gmail.com:
Extra info received and forwarded to list. Copy sent to GRUB Maintainers <pkg-grub-devel@lists.alioth.debian.org>.
(Fri, 18 Jun 2010 14:33:05 GMT) (full text, mbox, link).
Message #120 received at 586143@bugs.debian.org (full text, mbox, reply):
These informations in addition:
# df | grep custom
/dev/sdb2 24034944 2740660 20073344 13% /mnt/custom
# mount | tail -3
/dev/sdb2 on /mnt/custom type ext4 (rw)
/proc on /mnt/custom/proc type none (rw,bind)
/dev on /mnt/custom/dev type none (rw,bind)
From my testing:
--- MOUNTS ---
# mount -t ext4 /dev/sdb2 /mnt/custom
# mount --bind /proc /mnt/custom/proc
# mount --bind /dev /mnt/custom/dev
--- CHROOT ---
# chroot /mnt/custom bin/bash
# grub-install /dev/sda
Installation finished. No error reported.
# exit
--- UMOUNTS ---
# umount /mnt/custom/dev
# umount /mnt/custom/proc
# umount /mnt/custom
- Sedat -
On Fri, Jun 18, 2010 at 4:16 PM, Sedat Dilek <sedat.dilek@googlemail.com> wrote:
> Hi Dominique,
>
> I tried to reproduce on how to fix the problem: You have a little
> typo, here are the correct steps:
>
> 1. boot systemrescuecd
> 2. mount -t ext3 /dev/sda2 /mnt/custom <--- TYPO
> 3. mount --bind /proc /mnt/custom/proc
> 4. mount --bind /dev/ /mnt/custom/dev
> 5. chroot /mnt/custom bin/bash
> 6. grub-install /dev/sda
>
> Kind Regards,
> - Sedat -
>
Information stored
:
Bug#586143; Package grub-pc.
(Fri, 18 Jun 2010 18:45:03 GMT) (full text, mbox, link).
Acknowledgement sent
to Guido Günther <agx@sigxcpu.org>:
Extra info received and filed, but not forwarded.
(Fri, 18 Jun 2010 18:45:03 GMT) (full text, mbox, link).
Message #125 received at 586143-quiet@bugs.debian.org (full text, mbox, reply):
On Fri, Jun 18, 2010 at 01:10:42PM +0100, Colin Watson wrote:
> On Fri, Jun 18, 2010 at 01:59:15PM +0200, Salvatore Bonaccorso wrote:
> > I'm not the original reporter but experience the similar problem,
> > getting 'unaligned pointer 0x4c1b0297'. I tried to collect the
> > information you requested for that:
>
> Thanks. This is the most interesting part:
>
> > Generating core.img
> > Saving menu.lst backup in /boot/grub/menu.lst_backup_by_grub2_postinst
> > Running update-grub Legacy to hook our core.img in it
> [...]
>
> I've just gone through an extensive debugging session with an affected
> user on IRC who had the same symptom (thanks, dileX), and I believe I
> understand the problem now. I would like to confirm one fact with the
> people who have contributed to this bug report so far, namely:
>
> Does the file /boot/grub/stage2 exist on your system?
Yept. It's there.
-- Guidio
Information forwarded
to debian-bugs-dist@lists.debian.org, GRUB Maintainers <pkg-grub-devel@lists.alioth.debian.org>:
Bug#586143; Package grub-pc.
(Fri, 18 Jun 2010 18:51:05 GMT) (full text, mbox, link).
Acknowledgement sent
to mahashakti89 <mahashakti89@orange.fr>:
Extra info received and forwarded to list. Copy sent to GRUB Maintainers <pkg-grub-devel@lists.alioth.debian.org>.
(Fri, 18 Jun 2010 18:51:05 GMT) (full text, mbox, link).
Message #130 received at 586143@bugs.debian.org (full text, mbox, reply):
Hi!
I can confirm the bug, on a desktop machine I was unable to boot - it
worked on a laptop -on the desktop I had to chroot the system and to downgrade
grub-pc and grub-common. I decided to find some informations on the bug, read
all the messages on bugs.debian.org concerning this one,and about
possible solutions and gave the one with #grub-install /dev/sdx a chance.
I did the upgrade, ran the command and ... the system is now booting without a problem.
Regards
mahashakti89
Information forwarded
to debian-bugs-dist@lists.debian.org, GRUB Maintainers <pkg-grub-devel@lists.alioth.debian.org>:
Bug#586143; Package grub-pc.
(Fri, 18 Jun 2010 18:57:03 GMT) (full text, mbox, link).
Acknowledgement sent
to Colin Watson <cjwatson@debian.org>:
Extra info received and forwarded to list. Copy sent to GRUB Maintainers <pkg-grub-devel@lists.alioth.debian.org>.
(Fri, 18 Jun 2010 18:57:03 GMT) (full text, mbox, link).
Message #135 received at 586143@bugs.debian.org (full text, mbox, reply):
On Fri, Jun 18, 2010 at 02:31:44PM +0200, Andreas Jacob wrote:
> Nope, the file /boot/grub/stage2 is actually (system works) not
> present in the given directory, or elsewhere under /boot.
In that case, I think you have some different problem, since the other
respondents on this bug (including the original reporter) have
/boot/grub/stage2 and I have a pretty complete theory for how that could
cause this bug. Could you please file a new bug report with full
details so that we can analyse your problem separately?
Thanks,
--
Colin Watson [cjwatson@debian.org]
Information forwarded
to debian-bugs-dist@lists.debian.org, GRUB Maintainers <pkg-grub-devel@lists.alioth.debian.org>:
Bug#586143; Package grub-pc.
(Fri, 18 Jun 2010 19:00:06 GMT) (full text, mbox, link).
Acknowledgement sent
to Colin Watson <cjwatson@debian.org>:
Extra info received and forwarded to list. Copy sent to GRUB Maintainers <pkg-grub-devel@lists.alioth.debian.org>.
(Fri, 18 Jun 2010 19:00:06 GMT) (full text, mbox, link).
Message #140 received at 586143@bugs.debian.org (full text, mbox, reply):
On Fri, Jun 18, 2010 at 08:48:06PM +0200, mahashakti89 wrote:
> I can confirm the bug, on a desktop machine I was unable to boot - it
> worked on a laptop -on the desktop I had to chroot the system and to downgrade
> grub-pc and grub-common. I decided to find some informations on the bug, read
> all the messages on bugs.debian.org concerning this one,and about
> possible solutions and gave the one with #grub-install /dev/sdx a chance.
> I did the upgrade, ran the command and ... the system is now booting without a problem.
Could you please confirm whether or not you have a file
/boot/grub/stage2 on your system?
Thanks,
--
Colin Watson [cjwatson@debian.org]
Information forwarded
to debian-bugs-dist@lists.debian.org, GRUB Maintainers <pkg-grub-devel@lists.alioth.debian.org>:
Bug#586143; Package grub-pc.
(Fri, 18 Jun 2010 19:33:05 GMT) (full text, mbox, link).
Acknowledgement sent
to mahashakti89 <mahashakti89@orange.fr>:
Extra info received and forwarded to list. Copy sent to GRUB Maintainers <pkg-grub-devel@lists.alioth.debian.org>.
(Fri, 18 Jun 2010 19:33:05 GMT) (full text, mbox, link).
Message #145 received at 586143@bugs.debian.org (full text, mbox, reply):
On Fri, Jun 18, 2010 Colin Watson wrote :
> Could you please confirm whether or not you have a file
> /boot/grub/stage2 on your system?
I purged the boot directory from all stage files belonging to the old
GRUB package. There is now no such file (stage2) on my system.
Regards
mahashakti89
Information forwarded
to debian-bugs-dist@lists.debian.org, GRUB Maintainers <pkg-grub-devel@lists.alioth.debian.org>:
Bug#586143; Package grub-pc.
(Fri, 18 Jun 2010 19:45:07 GMT) (full text, mbox, link).
Acknowledgement sent
to "Steffen Möller" <steffen_moeller@gmx.de>:
Extra info received and forwarded to list. Copy sent to GRUB Maintainers <pkg-grub-devel@lists.alioth.debian.org>.
(Fri, 18 Jun 2010 19:45:07 GMT) (full text, mbox, link).
Message #150 received at 586143@bugs.debian.org (full text, mbox, reply):
Hello,
this grub version needs to be removed immediately from unstable. It discourages enormously the use of unstable to filter for testing.
The /boot/grub/stage/stage2 and stage1 files are existing on my system.
Maybe I was too happy with unstable for too long and have given my 64bit rescue USB sticks as presents to too many people (where are those beasts) and I just cannot do the chroot with the 3year old 32bit putty that I have come across.
Steffen
Information forwarded
to debian-bugs-dist@lists.debian.org, GRUB Maintainers <pkg-grub-devel@lists.alioth.debian.org>:
Bug#586143; Package grub-pc.
(Fri, 18 Jun 2010 19:51:03 GMT) (full text, mbox, link).
Acknowledgement sent
to mahashakti89 <mahashakti89@orange.fr>:
Extra info received and forwarded to list. Copy sent to GRUB Maintainers <pkg-grub-devel@lists.alioth.debian.org>.
(Fri, 18 Jun 2010 19:51:03 GMT) (full text, mbox, link).
Message #155 received at 586143@bugs.debian.org (full text, mbox, reply):
Sorry for the second post , my first message could be ambiguous, so ...
On Fri, Jun 18, 2010 Colin Watson wrote :
> Could you please confirm whether or not you have a file
> /boot/grub/stage2 on your system?
A LONG TIME AGO I purged the boot directory from all stage files belonging to the old GRUB package. There is now no such file (stage2) on my system.
Regards
mahashakti89
Information forwarded
to debian-bugs-dist@lists.debian.org, GRUB Maintainers <pkg-grub-devel@lists.alioth.debian.org>:
Bug#586143; Package grub-pc.
(Fri, 18 Jun 2010 20:45:08 GMT) (full text, mbox, link).
Acknowledgement sent
to Colin Watson <cjwatson@debian.org>:
Extra info received and forwarded to list. Copy sent to GRUB Maintainers <pkg-grub-devel@lists.alioth.debian.org>.
(Fri, 18 Jun 2010 20:45:08 GMT) (full text, mbox, link).
Message #160 received at 586143@bugs.debian.org (full text, mbox, reply):
On Fri, Jun 18, 2010 at 09:49:57PM +0200, mahashakti89 wrote:
> On Fri, Jun 18, 2010 Colin Watson wrote :
>> Could you please confirm whether or not you have a file
>> /boot/grub/stage2 on your system?
>
> A LONG TIME AGO I purged the boot directory from all stage files
> belonging to the old GRUB package. There is now no such file (stage2)
> on my system.
Then could you please file a new bug rather than following up to this
one, so that we can analyse your problem separately?
Thanks,
--
Colin Watson [cjwatson@debian.org]
Information forwarded
to debian-bugs-dist@lists.debian.org, GRUB Maintainers <pkg-grub-devel@lists.alioth.debian.org>:
Bug#586143; Package grub-pc.
(Fri, 18 Jun 2010 20:48:08 GMT) (full text, mbox, link).
Acknowledgement sent
to Colin Watson <cjwatson@debian.org>:
Extra info received and forwarded to list. Copy sent to GRUB Maintainers <pkg-grub-devel@lists.alioth.debian.org>.
(Fri, 18 Jun 2010 20:48:08 GMT) (full text, mbox, link).
Message #165 received at 586143@bugs.debian.org (full text, mbox, reply):
On Fri, Jun 18, 2010 at 09:42:29PM +0200, Steffen Möller wrote:
> this grub version needs to be removed immediately from unstable. It
> discourages enormously the use of unstable to filter for testing.
No. I'll be fixing it very soon (as soon as I get a few hours in a row
where I can concentrate on it); removing it would make it very difficult
for me to find problems. ftpmaster, please disregard this. unstable is
unstable.
--
Colin Watson [cjwatson@debian.org]
Information forwarded
to debian-bugs-dist@lists.debian.org, GRUB Maintainers <pkg-grub-devel@lists.alioth.debian.org>:
Bug#586143; Package grub-pc.
(Fri, 18 Jun 2010 21:30:03 GMT) (full text, mbox, link).
Acknowledgement sent
to Joerg Jaspert <joerg@debian.org>:
Extra info received and forwarded to list. Copy sent to GRUB Maintainers <pkg-grub-devel@lists.alioth.debian.org>.
(Fri, 18 Jun 2010 21:30:03 GMT) (full text, mbox, link).
Message #170 received at 586143@bugs.debian.org (full text, mbox, reply):
>> this grub version needs to be removed immediately from unstable. It
>> discourages enormously the use of unstable to filter for testing.
Oh suuuure.
> No. I'll be fixing it very soon (as soon as I get a few hours in a row
> where I can concentrate on it); removing it would make it very difficult
> for me to find problems. ftpmaster, please disregard this. unstable is
> unstable.
There is no RM bug filed, so no action to take anyways.
--
bye, Joerg
Some NM:
>A developer contacts you and asks you to met for a keysign. What is
>your response and why?
Do you like beer? When do we meet? [...]
Information forwarded
to debian-bugs-dist@lists.debian.org, GRUB Maintainers <pkg-grub-devel@lists.alioth.debian.org>:
Bug#586143; Package grub-pc.
(Fri, 18 Jun 2010 22:27:08 GMT) (full text, mbox, link).
Acknowledgement sent
to Torsten Werner <twerner@debian.org>:
Extra info received and forwarded to list. Copy sent to GRUB Maintainers <pkg-grub-devel@lists.alioth.debian.org>.
(Fri, 18 Jun 2010 22:27:08 GMT) (full text, mbox, link).
Message #175 received at 586143@bugs.debian.org (full text, mbox, reply):
Hi,
Am 18.06.2010 21:42, schrieb "Steffen Möller":
> this grub version needs to be removed immediately from unstable.
just purge the grub2 related binary packages from your system if you do
not like them. :)
Removing a package from unstable would remove it from testing too
because testing tracks unstable. I doubt that this makes sense for the
grub2 package.
Cheers,
Torsten
Information forwarded
to debian-bugs-dist@lists.debian.org, GRUB Maintainers <pkg-grub-devel@lists.alioth.debian.org>:
Bug#586143; Package grub-pc.
(Fri, 18 Jun 2010 23:00:05 GMT) (full text, mbox, link).
Acknowledgement sent
to "Steffen Möller" <steffen_moeller@gmx.de>:
Extra info received and forwarded to list. Copy sent to GRUB Maintainers <pkg-grub-devel@lists.alioth.debian.org>.
(Fri, 18 Jun 2010 23:00:05 GMT) (full text, mbox, link).
Message #180 received at 586143@bugs.debian.org (full text, mbox, reply):
Hi Torsten,
> Datum: Sat, 19 Jun 2010 00:23:17 +0200
> Von: Torsten Werner <twerner@debian.org>
> Am 18.06.2010 21:42, schrieb "Steffen Möller":
> > this grub version needs to be removed immediately from unstable.
>
> just purge the grub2 related binary packages from your system if you do
> not like them. :)
:)
> Removing a package from unstable would remove it from testing too
> because testing tracks unstable. I doubt that this makes sense for the
> grub2 package.
Good point. My intention obviously was not to have more fellows
temporarily brick their systen. How many will it be if this is fixed
within the next day? 100? 250? 500? 1000? Well, if it is just 10 then
everything just fine how it is. If it is 20 I am not so sure any more.
Cheers,
Steffen
Information forwarded
to debian-bugs-dist@lists.debian.org, GRUB Maintainers <pkg-grub-devel@lists.alioth.debian.org>:
Bug#586143; Package grub-pc.
(Fri, 18 Jun 2010 23:09:06 GMT) (full text, mbox, link).
Acknowledgement sent
to Andreas Jacob <andreasjacob@gmx.de>:
Extra info received and forwarded to list. Copy sent to GRUB Maintainers <pkg-grub-devel@lists.alioth.debian.org>.
(Fri, 18 Jun 2010 23:09:06 GMT) (full text, mbox, link).
Message #185 received at 586143@bugs.debian.org (full text, mbox, reply):
Hi Colin
Could it be that grub-install, or your patched debug version did
remove the stage2 file? When I execute a grub-install, it seems to
touch or to rewrite almost all files under /boot/grub. May be it also
deletes the stage2 file?
Unfortunately i have no backup from /boot where i can look if these
file were there before. But I did the grub update within a
safe-upgrade, shuted down my laptop, an 2 hours later on rebooting
there was the described behaviour. Meanwhile it's impossible for me to
reproduce the error.
As i can read here, some other people have also no stage2 file but the
same behavior. This couldn't be contretemps.
Cheers Andreas
2010/6/18 Colin Watson <cjwatson@debian.org>:
> On Fri, Jun 18, 2010 at 02:31:44PM +0200, Andreas Jacob wrote:
>> Nope, the file /boot/grub/stage2 is actually (system works) not
>> present in the given directory, or elsewhere under /boot.
>
> In that case, I think you have some different problem, since the other
> respondents on this bug (including the original reporter) have
> /boot/grub/stage2 and I have a pretty complete theory for how that could
> cause this bug. Could you please file a new bug report with full
> details so that we can analyse your problem separately?
>
Information forwarded
to debian-bugs-dist@lists.debian.org, GRUB Maintainers <pkg-grub-devel@lists.alioth.debian.org>:
Bug#586143; Package grub-pc.
(Fri, 18 Jun 2010 23:33:09 GMT) (full text, mbox, link).
Acknowledgement sent
to Colin Watson <cjwatson@debian.org>:
Extra info received and forwarded to list. Copy sent to GRUB Maintainers <pkg-grub-devel@lists.alioth.debian.org>.
(Fri, 18 Jun 2010 23:33:09 GMT) (full text, mbox, link).
Message #190 received at 586143@bugs.debian.org (full text, mbox, reply):
On Sat, Jun 19, 2010 at 01:07:06AM +0200, Andreas Jacob wrote:
> Could it be that grub-install, or your patched debug version did
> remove the stage2 file? When I execute a grub-install, it seems to
> touch or to rewrite almost all files under /boot/grub. May be it also
> deletes the stage2 file?
No, it's very specific about what files it touches and it doesn't touch
stage2.
> Unfortunately i have no backup from /boot where i can look if these
> file were there before. But I did the grub update within a
> safe-upgrade, shuted down my laptop, an 2 hours later on rebooting
> there was the described behaviour. Meanwhile it's impossible for me to
> reproduce the error.
>
> As i can read here, some other people have also no stage2 file but the
> same behavior. This couldn't be contretemps.
As a matter of fact it could well be. There are layers to this problem.
The direct cause is that the core image and /boot/grub/*.mod have got
out of sync and can no longer call each other's code directly in the way
they expect to be able to. However, there are a variety of reasons why
that could happen, and in fact none of them are really particularly new!
We get a batch of these bug reports each time the interface between
GRUB's core image and modules changes in any significant way. #554790
is essentially a cluster of the same kinds of problems; the symptoms are
different, but that's not very relevant.
The fact that most people this time round are seeing this due to the
presence of /boot/grub/stage2 is very interesting, because that's a
separate and easier-to-fix problem: I have a fix in progress already,
but of course I need to construct tests for it locally before unleashing
it on the world. I want to keep this bug report for just that
situation, because bug reports should ideally be separated by cause
rather than by symptom if there's any hope of tracking and fixing them
in an organised way. After all, the purpose of bug reports is to
improve the software, not to be forums.
We've interpreted #554790 and its merged bugs as the situation where the
core image and modules get out of sync due to installing GRUB to the
wrong device, which can happen quite easily on multiple-disk systems. I
have code for this but it still has known incorrect behaviours and needs
work; but I absolutely intend to get this landed for squeeze.
Sometimes it's just user error, where somebody has installed GRUB to a
partition but the BIOS is actually booting from a separate installation
in the MBR which has wound up orphaned.
But what I'm interested in is making sure there aren't any situations I
haven't thought of yet. This bug was a brand new cause for a problem I
thought I'd fully classified, and that was fascinating and useful.
Perhaps you have a different brand new cause - or perhaps you
essentially have #554790. Without analysis, I can't tell, and I don't
want to use this bug for an analysis of your problem because we have
already established that it seems to be qualitatively different in cause
despite having similar symptoms.
Regards,
--
Colin Watson [cjwatson@debian.org]
Forcibly Merged 586143 586187.
Request was from Colin Watson <cjwatson@debian.org>
to control@bugs.debian.org.
(Sat, 19 Jun 2010 00:03:06 GMT) (full text, mbox, link).
Reply sent
to Colin Watson <cjwatson@debian.org>:
You have taken responsibility.
(Sat, 19 Jun 2010 01:39:13 GMT) (full text, mbox, link).
Notification sent
to Guido Günther <agx@sigxcpu.org>:
Bug acknowledged by developer.
(Sat, 19 Jun 2010 01:39:13 GMT) (full text, mbox, link).
Message #199 received at 586143-close@bugs.debian.org (full text, mbox, reply):
Source: grub2
Source-Version: 1.98+20100617-1
We believe that the bug you reported is fixed in the latest version of
grub2, which is due to be installed in the Debian FTP archive:
grub-common_1.98+20100617-1_i386.deb
to main/g/grub2/grub-common_1.98+20100617-1_i386.deb
grub-coreboot_1.98+20100617-1_i386.deb
to main/g/grub2/grub-coreboot_1.98+20100617-1_i386.deb
grub-efi-amd64_1.98+20100617-1_i386.deb
to main/g/grub2/grub-efi-amd64_1.98+20100617-1_i386.deb
grub-efi-ia32_1.98+20100617-1_i386.deb
to main/g/grub2/grub-efi-ia32_1.98+20100617-1_i386.deb
grub-efi_1.98+20100617-1_i386.deb
to main/g/grub2/grub-efi_1.98+20100617-1_i386.deb
grub-emu_1.98+20100617-1_i386.deb
to main/g/grub2/grub-emu_1.98+20100617-1_i386.deb
grub-firmware-qemu_1.98+20100617-1_i386.deb
to main/g/grub2/grub-firmware-qemu_1.98+20100617-1_i386.deb
grub-ieee1275_1.98+20100617-1_i386.deb
to main/g/grub2/grub-ieee1275_1.98+20100617-1_i386.deb
grub-linuxbios_1.98+20100617-1_i386.deb
to main/g/grub2/grub-linuxbios_1.98+20100617-1_i386.deb
grub-pc_1.98+20100617-1_i386.deb
to main/g/grub2/grub-pc_1.98+20100617-1_i386.deb
grub-rescue-pc_1.98+20100617-1_i386.deb
to main/g/grub2/grub-rescue-pc_1.98+20100617-1_i386.deb
grub2_1.98+20100617-1.diff.gz
to main/g/grub2/grub2_1.98+20100617-1.diff.gz
grub2_1.98+20100617-1.dsc
to main/g/grub2/grub2_1.98+20100617-1.dsc
grub2_1.98+20100617-1_i386.deb
to main/g/grub2/grub2_1.98+20100617-1_i386.deb
grub2_1.98+20100617.orig.tar.gz
to main/g/grub2/grub2_1.98+20100617.orig.tar.gz
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 586143@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Colin Watson <cjwatson@debian.org> (supplier of updated grub2 package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@debian.org)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Format: 1.8
Date: Sat, 19 Jun 2010 01:31:40 +0100
Source: grub2
Binary: grub2 grub-linuxbios grub-efi grub-common grub-emu grub-pc grub-rescue-pc grub-coreboot grub-efi-ia32 grub-efi-amd64 grub-ieee1275 grub-firmware-qemu grub-yeeloong
Architecture: source i386
Version: 1.98+20100617-1
Distribution: unstable
Urgency: low
Maintainer: GRUB Maintainers <pkg-grub-devel@lists.alioth.debian.org>
Changed-By: Colin Watson <cjwatson@debian.org>
Description:
grub-common - GRand Unified Bootloader, version 2 (common files)
grub-coreboot - GRand Unified Bootloader, version 2 (Coreboot version)
grub-efi - GRand Unified Bootloader, version 2 (dummy package)
grub-efi-amd64 - GRand Unified Bootloader, version 2 (EFI-AMD64 version)
grub-efi-ia32 - GRand Unified Bootloader, version 2 (EFI-IA32 version)
grub-emu - GRand Unified Bootloader, version 2 (emulated version)
grub-firmware-qemu - GRUB firmware image for QEMU
grub-ieee1275 - GRand Unified Bootloader, version 2 (Open Firmware version)
grub-linuxbios - GRand Unified Bootloader, version 2 (dummy package)
grub-pc - GRand Unified Bootloader, version 2 (PC/BIOS version)
grub-rescue-pc - GRUB bootable rescue images, version 2 (PC/BIOS version)
grub-yeeloong - GRand Unified Bootloader, version 2 (Yeeloong version)
grub2 - GRand Unified Bootloader, version 2 (dummy package)
Closes: 547944 550477 557425 585068 586143
Changes:
grub2 (1.98+20100617-1) unstable; urgency=low
.
* New Bazaar snapshot.
- Fix i386-pc prefix handling with nested partitions (closes: #585068).
.
* When running grub-pc.postinst from upgrade-from-grub-legacy, tell it to
disregard the fact that /boot/grub/stage2 and /boot/grub/menu.lst still
exist (closes: #550477).
* Touch a marker file when grub-install is run but GRUB Legacy files are
still around. If that marker file is present, pretend that GRUB Legacy
files are missing when upgrading.
* If GRUB Legacy files are present when upgrading, scan boot sectors of
all disks for GRUB 2. If we find GRUB 2 installed anywhere, then ask
the user if they want to finish conversion to GRUB 2, and warn them that
not doing so may render the system unbootable (closes: #586143).
* Leaving grub-pc/install_devices empty makes sense in some situations,
but more often than not is a mistake. On the other hand, automatically
selecting all disk devices would upset some people too. Compromise by
simply asking for explicit confirmation if grub-pc/install_devices is
left empty, defaulting to false so that simply selecting all the
defaults in debconf can't leave you with an unbootable system (closes:
#547944, #557425).
Checksums-Sha1:
f33d9a746c81a49b36c4f35554b19500130dea17 2822 grub2_1.98+20100617-1.dsc
ce1c3018663dfb9a70e967a5a44f44df481b9038 1822574 grub2_1.98+20100617.orig.tar.gz
1290b42212ccfb7476548f81661e7616b7dc7d84 398878 grub2_1.98+20100617-1.diff.gz
3cbce865ae2577908f23f1be8e82d1032191c286 263702 grub2_1.98+20100617-1_i386.deb
1368f85102b5dc3a970a7b60af4aaf3116b02f83 262470 grub-linuxbios_1.98+20100617-1_i386.deb
4e3cb546078f4382aee5d2eebbbbf2ed61da13ab 262470 grub-efi_1.98+20100617-1_i386.deb
8010f421dfdcaa2b9a19f14db5810c31b16a1150 1615230 grub-common_1.98+20100617-1_i386.deb
cadf9db56247fa8e05c3f000008e1f645fb1304c 2603038 grub-emu_1.98+20100617-1_i386.deb
98e4c0ec1a88777bcd6d1bc43837ba3c5a055f27 916338 grub-pc_1.98+20100617-1_i386.deb
6548d519a1710921ed3be4f36f5bf19118ecedc6 1395554 grub-rescue-pc_1.98+20100617-1_i386.deb
d3cfd00724f1f66bfd4b2045d8a94d66836f26ca 718548 grub-coreboot_1.98+20100617-1_i386.deb
facde914db821d01b6bf7fc94d7ab02f82e956ad 753666 grub-efi-ia32_1.98+20100617-1_i386.deb
ffba4991b2942079f17a70b0f332a6f04a9afcc3 828256 grub-efi-amd64_1.98+20100617-1_i386.deb
3ca1cb51c84ac4d7cdb06948f30e2bc907bb4c08 712414 grub-ieee1275_1.98+20100617-1_i386.deb
3f4e449709104aba91d34fe37a67e550f92ae0a1 665628 grub-firmware-qemu_1.98+20100617-1_i386.deb
Checksums-Sha256:
8139015cddfe1ac132f7457b391b4ef51beac3d316aae14f8467efadc41b28a8 2822 grub2_1.98+20100617-1.dsc
8c5350708a6579ed2b0ceed0a8ff137baaf072a2587cd84c6c19f5bd61f5c273 1822574 grub2_1.98+20100617.orig.tar.gz
23f82e004636dd05cc6c8f5c2238e58d8b40399cc69f69b1e5e2379e45dbfb71 398878 grub2_1.98+20100617-1.diff.gz
5d94b62889efbfdee63297410f990451ebfd91a7b4698f6749282b71cad40ccd 263702 grub2_1.98+20100617-1_i386.deb
810c9d7b6e53a2fa667c5d2416da2750719ff3e73dfbac9912c1a5fa3515c22e 262470 grub-linuxbios_1.98+20100617-1_i386.deb
a305a94939090e19dd5ff37f6637a9482e9df9deab3883ab816fe22ba16e6c22 262470 grub-efi_1.98+20100617-1_i386.deb
c3baceb5bdf2874b3192dfc6dde9813cbe2d9f4e38fa594a8e03844b83f92907 1615230 grub-common_1.98+20100617-1_i386.deb
82ce4b8b298721443ae03bfed866f3d0a5571681f9957d98219b75f711ddc650 2603038 grub-emu_1.98+20100617-1_i386.deb
13f28fd767962c6063d89fdf7b56c32f9603b2091a096123331fbb966b4b9fbe 916338 grub-pc_1.98+20100617-1_i386.deb
b3ccc46c4a9d311fb94e5c7dea868908fe9c7d9454720a9a776d1fc80a326103 1395554 grub-rescue-pc_1.98+20100617-1_i386.deb
738f93c13edd1043effdb82d7ca6e4ddc49c88e9c31a0c13b91cdd621fbf4397 718548 grub-coreboot_1.98+20100617-1_i386.deb
8723bb89dcc4423957c6c8870da7b2d013e4bee7098e7ae21bbdcc4438f50972 753666 grub-efi-ia32_1.98+20100617-1_i386.deb
27bd7b3bf6d084a91edd60e8d0c6779b85eb0de24660b680980b52b65f7e610a 828256 grub-efi-amd64_1.98+20100617-1_i386.deb
5091de0d68b65227c588b7a37c05e66cde96eda810c79f4b2518c8ca66210f3d 712414 grub-ieee1275_1.98+20100617-1_i386.deb
28b22c5c2c56912df302658bc56af9cc0dada21472b7b449952d8fd5f1fc5132 665628 grub-firmware-qemu_1.98+20100617-1_i386.deb
Files:
7f9b52461301d9b976d8a7c9ce883ed7 2822 admin extra grub2_1.98+20100617-1.dsc
7fcc9fc3fde341e42ff52ae2ac187a34 1822574 admin extra grub2_1.98+20100617.orig.tar.gz
94cca16db597c0b6f77bc330c94a3c4b 398878 admin extra grub2_1.98+20100617-1.diff.gz
7a0a384ed09c154c0783e624c3d244e6 263702 admin extra grub2_1.98+20100617-1_i386.deb
a35c44ccbb9fe1fb9113190e10a8b165 262470 admin extra grub-linuxbios_1.98+20100617-1_i386.deb
75882bfd90614bfc39649aae9215c36d 262470 admin extra grub-efi_1.98+20100617-1_i386.deb
7cd4e7ef3512b3942411fdb3773dfa8d 1615230 admin extra grub-common_1.98+20100617-1_i386.deb
a1fc41823495894a0b00dce172a1ad08 2603038 admin extra grub-emu_1.98+20100617-1_i386.deb
8391eef0ad7d169eee4b59db2584d303 916338 admin extra grub-pc_1.98+20100617-1_i386.deb
d576ca5ee33cc44e97f4c7ff9761dd76 1395554 admin extra grub-rescue-pc_1.98+20100617-1_i386.deb
64fe65293bb75e74b87669d9d51abf9b 718548 admin extra grub-coreboot_1.98+20100617-1_i386.deb
ec6e3dee8ab26461b557003e518d200f 753666 admin extra grub-efi-ia32_1.98+20100617-1_i386.deb
a1d73bfaddaf9be99ad92023d1a81c92 828256 admin extra grub-efi-amd64_1.98+20100617-1_i386.deb
93b6f859946ff4b8e3db83e2bf7abe2b 712414 admin extra grub-ieee1275_1.98+20100617-1_i386.deb
cc42b60272fbd92d950ef472bfe8497c 665628 admin extra grub-firmware-qemu_1.98+20100617-1_i386.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Colin Watson <cjwatson@debian.org> -- Debian developer
iQIVAwUBTBwUcTk1h9l9hlALAQj1dw/+KHKKpVb6WJ3gw8buKEAoqULOsI5P4d4C
amAf7tPKGgERNWrDAic3QMk5vUFfhdQ2dQ3weba9dEfSOZhid2kBq2mcTQsKjY4Y
pIaxpkd5zpegcruNjGOcQXnVrUiDerydKUktKs6GkWIFRtN/TC2D+yuUubQWl68P
thKNrQa9180K3XFapWFXmrltPrOOqvI+VU7LlQxGTadg44enOuzNPq+Lg66JxF50
vgxI/k+6JjzDvQ3CRzFnnJ18CRoUY/ajdPULZH3gahK6y+Yw4MQNeqNvH++F/aAg
OnhPHyKbQC69PgSbC/nV9d8EFnWFWplw4GPoMMmicjnoDy4+hxaZhfzu3bKa/rSQ
TIVE16etiCoMcPxka0trkuBIDG38fSJLyFQpir2NkGxgf+CSp0dtYD6Ml6QMXpSA
biY27iaiNi29mGuIhtv/qbvULyCNR7NOVKQ2qrFGKbyKOjsPJNAIU0WduKLCQ6GW
MH7f/jxWjkPET6KEkrhjcE3ULFSXIbigmGqHgxUf9z7mRYDrJUgcds3Omun3Bo2Y
q70QSi/YizZeV1gVpzRWmULDaUHK4t/3zg/Ce2ZRxnohQl+NzN0JfOLqt7XNAJ8H
AEIZhA9jsqO55BtwevhwUzivsSYRvUQIHoRN2gyH2LKmcVIWGjijqOVHXNLBcv/H
M5iVQAf1QMc=
=jTyQ
-----END PGP SIGNATURE-----
Reply sent
to Colin Watson <cjwatson@debian.org>:
You have taken responsibility.
(Sat, 19 Jun 2010 01:39:14 GMT) (full text, mbox, link).
Notification sent
to Giuseppe Sacco <giuseppe@eppesuigoccas.homedns.org>:
Bug acknowledged by developer.
(Sat, 19 Jun 2010 01:39:14 GMT) (full text, mbox, link).
Reply sent
to Colin Watson <cjwatson@debian.org>:
You have taken responsibility.
(Sat, 19 Jun 2010 01:39:14 GMT) (full text, mbox, link).
Notification sent
to Kurt Roeckx <kurt@roeckx.be>:
Bug acknowledged by developer.
(Sat, 19 Jun 2010 01:39:15 GMT) (full text, mbox, link).
Information forwarded
to debian-bugs-dist@lists.debian.org, GRUB Maintainers <pkg-grub-devel@lists.alioth.debian.org>:
Bug#586143; Package grub-pc.
(Sat, 19 Jun 2010 08:06:05 GMT) (full text, mbox, link).
Acknowledgement sent
to Andreas Jacob <andreasjacob@gmx.de>:
Extra info received and forwarded to list. Copy sent to GRUB Maintainers <pkg-grub-devel@lists.alioth.debian.org>.
(Sat, 19 Jun 2010 08:06:05 GMT) (full text, mbox, link).
Message #214 received at 586143@bugs.debian.org (full text, mbox, reply):
Hi Colin
I think, i 've found the solution, why there was no stage2 file in my
/boot/grub directory. Yesterday morning, i was looking around in
/boot/grub and inspected the menu.lst file. There was a note, which
was saying to run the upgrade-from-grub-legacy script, when grub2 is
working. So i did these on yesterday morning.
Today, i looked inside the /usr/sbin/upgrade-from-grub-legacy script,
and found, that these script probably deleted the stage2 file.
In other words, the chance, that the stage2 file were present, when
running into tis error might be verry close to 100 percent. ;-)
Thanx for your work
Andreas
Information forwarded
to debian-bugs-dist@lists.debian.org, GRUB Maintainers <pkg-grub-devel@lists.alioth.debian.org>:
Bug#586143; Package grub-pc.
(Sat, 19 Jun 2010 15:48:06 GMT) (full text, mbox, link).
Acknowledgement sent
to bjb@linuxbutler.ca:
Extra info received and forwarded to list. Copy sent to GRUB Maintainers <pkg-grub-devel@lists.alioth.debian.org>.
(Sat, 19 Jun 2010 15:48:06 GMT) (full text, mbox, link).
Message #219 received at 586143@bugs.debian.org (full text, mbox, reply):
Yes, this file /boot/grub/stage2 exists on my system.
Thanks for your work on grub.
bjb
On Fri, Jun 18, 2010 at 01:10:42PM +0100, Colin Watson wrote:
> On Fri, Jun 18, 2010 at 01:59:15PM +0200, Salvatore Bonaccorso wrote:
> > I'm not the original reporter but experience the similar problem,
> > getting 'unaligned pointer 0x4c1b0297'. I tried to collect the
> > information you requested for that:
>
> Thanks. This is the most interesting part:
>
> > Generating core.img
> > Saving menu.lst backup in /boot/grub/menu.lst_backup_by_grub2_postinst
> > Running update-grub Legacy to hook our core.img in it
> [...]
>
> I've just gone through an extensive debugging session with an affected
> user on IRC who had the same symptom (thanks, dileX), and I believe I
> understand the problem now. I would like to confirm one fact with the
> people who have contributed to this bug report so far, namely:
>
> Does the file /boot/grub/stage2 exist on your system?
>
> I strongly suspect at this point that that will be the case for all of
> you, and if that's the case then I know what to do.
>
> Thanks,
>
> --
> Colin Watson [cjwatson@debian.org]
---end quoted text---
Information forwarded
to debian-bugs-dist@lists.debian.org, GRUB Maintainers <pkg-grub-devel@lists.alioth.debian.org>:
Bug#586143; Package grub-pc.
(Sun, 20 Jun 2010 11:48:04 GMT) (full text, mbox, link).
Acknowledgement sent
to "C. Scott Ananian" <cscott@cscott.net>:
Extra info received and forwarded to list. Copy sent to GRUB Maintainers <pkg-grub-devel@lists.alioth.debian.org>.
(Sun, 20 Jun 2010 11:48:05 GMT) (full text, mbox, link).
Message #224 received at 586143@bugs.debian.org (full text, mbox, reply):
Package: grub-pc
Version: 1.98+20100614-1
Severity: normal
File: grub
Saw this in grub 1.98+20100614-1. Booting into a rescue disk, mounting and
chroot'ing to my old system, and running 'grub-install /dev/sda' fixed the
problem.
--scott
-- Package-specific info:
*********************** BEGIN /proc/mounts
/dev/disk/by-uuid/fef0083a-c372-479f-8cea-34858d7e1de4 / ext3 rw,relatime,errors=remount-ro,user_xattr,data=ordered 0 0
/dev/sdb /media/4AE3-8F6D vfat rw,nosuid,nodev,relatime,uid=1000,gid=1000,fmask=0022,dmask=0077,codepage=cp437,iocharset=utf8,shortname=mixed,showexec,utf8,flush,errors=remount-ro 0 0
*********************** END /proc/mounts
*********************** BEGIN /boot/grub/device.map
(hd0) /dev/sda
*********************** END /boot/grub/device.map
*********************** BEGIN /boot/grub/grub.cfg
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#
### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
load_env
fi
set default="0"
if [ "${prev_saved_entry}" ]; then
set saved_entry="${prev_saved_entry}"
save_env saved_entry
set prev_saved_entry=
save_env prev_saved_entry
set boot_once=true
fi
function savedefault {
if [ -z "${boot_once}" ]; then
saved_entry="${chosen}"
save_env saved_entry
fi
}
insmod part_msdos
insmod ext2
set root='(hd0,msdos1)'
search --no-floppy --fs-uuid --set fef0083a-c372-479f-8cea-34858d7e1de4
if loadfont /usr/share/grub/unicode.pf2 ; then
set gfxmode=640x480
insmod gfxterm
insmod vbe
fi
if terminal_output gfxterm ; then true ; else
# For backward compatibility with versions of terminal.mod that don't
# understand terminal_output
terminal gfxterm
fi
insmod part_msdos
insmod ext2
set root='(hd0,msdos1)'
search --no-floppy --fs-uuid --set fef0083a-c372-479f-8cea-34858d7e1de4
set locale_dir=($root)/boot/grub/locale
set lang=en
insmod gettext
set timeout=5
### END /etc/grub.d/00_header ###
### BEGIN /etc/grub.d/05_debian_theme ###
insmod part_msdos
insmod ext2
set root='(hd0,msdos1)'
search --no-floppy --fs-uuid --set fef0083a-c372-479f-8cea-34858d7e1de4
insmod png
if background_image /boot/grub/moreblue-orbit-grub.png ; then
set color_normal=black/black
set color_highlight=magenta/black
else
set menu_color_normal=cyan/blue
set menu_color_highlight=white/blue
fi
### END /etc/grub.d/05_debian_theme ###
### BEGIN /etc/grub.d/10_linux ###
menuentry 'Debian GNU/Linux, with Linux 2.6.32-5-686' --class debian --class gnu-linux --class gnu --class os {
insmod part_msdos
insmod ext2
set root='(hd0,msdos1)'
search --no-floppy --fs-uuid --set fef0083a-c372-479f-8cea-34858d7e1de4
echo 'Loading Linux 2.6.32-5-686 ...'
linux /boot/vmlinuz-2.6.32-5-686 root=UUID=fef0083a-c372-479f-8cea-34858d7e1de4 ro quiet
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-2.6.32-5-686
}
menuentry 'Debian GNU/Linux, with Linux 2.6.32-5-686 (recovery mode)' --class debian --class gnu-linux --class gnu --class os {
insmod part_msdos
insmod ext2
set root='(hd0,msdos1)'
search --no-floppy --fs-uuid --set fef0083a-c372-479f-8cea-34858d7e1de4
echo 'Loading Linux 2.6.32-5-686 ...'
linux /boot/vmlinuz-2.6.32-5-686 root=UUID=fef0083a-c372-479f-8cea-34858d7e1de4 ro single
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-2.6.32-5-686
}
menuentry 'Debian GNU/Linux, with Linux 2.6.32-3-686' --class debian --class gnu-linux --class gnu --class os {
insmod part_msdos
insmod ext2
set root='(hd0,msdos1)'
search --no-floppy --fs-uuid --set fef0083a-c372-479f-8cea-34858d7e1de4
echo 'Loading Linux 2.6.32-3-686 ...'
linux /boot/vmlinuz-2.6.32-3-686 root=UUID=fef0083a-c372-479f-8cea-34858d7e1de4 ro quiet
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-2.6.32-3-686
}
menuentry 'Debian GNU/Linux, with Linux 2.6.32-3-686 (recovery mode)' --class debian --class gnu-linux --class gnu --class os {
insmod part_msdos
insmod ext2
set root='(hd0,msdos1)'
search --no-floppy --fs-uuid --set fef0083a-c372-479f-8cea-34858d7e1de4
echo 'Loading Linux 2.6.32-3-686 ...'
linux /boot/vmlinuz-2.6.32-3-686 root=UUID=fef0083a-c372-479f-8cea-34858d7e1de4 ro single
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-2.6.32-3-686
}
menuentry 'Debian GNU/Linux, with Linux 2.6.32-2-686' --class debian --class gnu-linux --class gnu --class os {
insmod part_msdos
insmod ext2
set root='(hd0,msdos1)'
search --no-floppy --fs-uuid --set fef0083a-c372-479f-8cea-34858d7e1de4
echo 'Loading Linux 2.6.32-2-686 ...'
linux /boot/vmlinuz-2.6.32-2-686 root=UUID=fef0083a-c372-479f-8cea-34858d7e1de4 ro quiet
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-2.6.32-2-686
}
menuentry 'Debian GNU/Linux, with Linux 2.6.32-2-686 (recovery mode)' --class debian --class gnu-linux --class gnu --class os {
insmod part_msdos
insmod ext2
set root='(hd0,msdos1)'
search --no-floppy --fs-uuid --set fef0083a-c372-479f-8cea-34858d7e1de4
echo 'Loading Linux 2.6.32-2-686 ...'
linux /boot/vmlinuz-2.6.32-2-686 root=UUID=fef0083a-c372-479f-8cea-34858d7e1de4 ro single
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-2.6.32-2-686
}
### END /etc/grub.d/10_linux ###
### BEGIN /etc/grub.d/30_os-prober ###
### END /etc/grub.d/30_os-prober ###
### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.
### END /etc/grub.d/40_custom ###
### BEGIN /etc/grub.d/41_custom ###
if [ -f $prefix/custom.cfg ]; then
source $prefix/custom.cfg;
fi
### END /etc/grub.d/41_custom ###
*********************** END /boot/grub/grub.cfg
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.32-5-686 (SMP w/2 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-pc depends on:
ii debconf [debconf-2.0] 1.5.32 Debian configuration management sy
ii grub-common 1.98+20100614-1 GRand Unified Bootloader, version
ii libc6 2.11.2-1 Embedded GNU C Library: Shared lib
ii libdevmapper1.02.1 2:1.02.48-1 The Linux Kernel Device Mapper use
ii ucf 3.0025 Update Configuration File: preserv
grub-pc recommends no packages.
Versions of packages grub-pc suggests:
ii desktop-base 5.0.5 common files for the Debian Deskto
-- debconf information:
grub2/kfreebsd_cmdline:
* grub2/linux_cmdline:
* grub-pc/chainload_from_menu.lst: true
grub-pc/kopt_extracted: false
grub-pc/postrm_purge_boot_grub: false
grub2/kfreebsd_cmdline_default: quiet
* grub2/linux_cmdline_default: quiet
* grub-pc/install_devices: /dev/sda
Information forwarded
to debian-bugs-dist@lists.debian.org, GRUB Maintainers <pkg-grub-devel@lists.alioth.debian.org>:
Bug#586143; Package grub-pc.
(Sun, 20 Jun 2010 21:21:09 GMT) (full text, mbox, link).
Acknowledgement sent
to Colin Watson <cjwatson@debian.org>:
Extra info received and forwarded to list. Copy sent to GRUB Maintainers <pkg-grub-devel@lists.alioth.debian.org>.
(Sun, 20 Jun 2010 21:21:09 GMT) (full text, mbox, link).
Message #229 received at 586143@bugs.debian.org (full text, mbox, reply):
On Sat, Jun 19, 2010 at 10:03:44AM +0200, Andreas Jacob wrote:
> I think, i 've found the solution, why there was no stage2 file in my
> /boot/grub directory. Yesterday morning, i was looking around in
> /boot/grub and inspected the menu.lst file. There was a note, which
> was saying to run the upgrade-from-grub-legacy script, when grub2 is
> working. So i did these on yesterday morning.
> Today, i looked inside the /usr/sbin/upgrade-from-grub-legacy script,
> and found, that these script probably deleted the stage2 file.
>
> In other words, the chance, that the stage2 file were present, when
> running into tis error might be verry close to 100 percent. ;-)
That makes complete sense. Thanks for following up.
--
Colin Watson [cjwatson@debian.org]
Information forwarded
to debian-bugs-dist@lists.debian.org, GRUB Maintainers <pkg-grub-devel@lists.alioth.debian.org>:
Bug#586143; Package grub-pc.
(Sun, 20 Jun 2010 21:27:12 GMT) (full text, mbox, link).
Acknowledgement sent
to Colin Watson <cjwatson@debian.org>:
Extra info received and forwarded to list. Copy sent to GRUB Maintainers <pkg-grub-devel@lists.alioth.debian.org>.
(Sun, 20 Jun 2010 21:27:12 GMT) (full text, mbox, link).
Message #234 received at 586143@bugs.debian.org (full text, mbox, reply):
On Wed, Jun 16, 2010 at 06:49:12PM -0400, C. Scott Ananian wrote:
> Saw this in grub 1.98+20100614-1. Booting into a rescue disk, mounting and
> chroot'ing to my old system, and running 'grub-install /dev/sda' fixed the
> problem.
Please check whether /boot/grub/stage2 existed (assuming you haven't
already upgraded to 1.98+20100617-1, which will offer to remove it for
you if it exists and it detects that you've run grub-install with GRUB 2
at some point).
--
Colin Watson [cjwatson@debian.org]
Information forwarded
to debian-bugs-dist@lists.debian.org, GRUB Maintainers <pkg-grub-devel@lists.alioth.debian.org>:
Bug#586143; Package grub-pc.
(Tue, 22 Jun 2010 14:21:03 GMT) (full text, mbox, link).
Acknowledgement sent
to Jeffrey G Thomas <Jeffrey.Thomas@sierra-bravo.com>:
Extra info received and forwarded to list. Copy sent to GRUB Maintainers <pkg-grub-devel@lists.alioth.debian.org>.
(Tue, 22 Jun 2010 14:21:03 GMT) (full text, mbox, link).
Message #239 received at 586143@bugs.debian.org (full text, mbox, reply):
[Message part 1 (text/plain, inline)]
> Does the file /boot/grub/stage2 exist on your system?
Yes that file exists on my system and has a date from before the failed upgrade:
$ ls -la /boot/grub/stage2
-rw-r--r-- 1 root root 128552 Jul 7 2008 /boot/grub/stage2
Jeffrey
[signature.asc (application/pgp-signature, inline)]
Information forwarded
to debian-bugs-dist@lists.debian.org, GRUB Maintainers <pkg-grub-devel@lists.alioth.debian.org>:
Bug#586143; Package grub-pc.
(Thu, 01 Jul 2010 21:45:03 GMT) (full text, mbox, link).
Acknowledgement sent
to Vladimir 'φ-coder/phcoder' Serbinenko <phcoder@gmail.com>:
Extra info received and forwarded to list. Copy sent to GRUB Maintainers <pkg-grub-devel@lists.alioth.debian.org>.
(Thu, 01 Jul 2010 21:45:03 GMT) (full text, mbox, link).
Message #244 received at 586143@bugs.debian.org (full text, mbox, reply):
[Message part 1 (text/plain, inline)]
On 06/18/2010 02:44 AM, André Nunes wrote:
> Same problem here, bur a little bit worse: I can't get my system back!
> I tryed to aptitude downgrade grub-pc and grub-common to 1.98-1 and
> also to grub-legacy, but I keep getting the same error:
>
> /usr/sbin/grub-probe: error: no mapping exists for tagesuhu-root
> Auto-detection of a filesystem module failed
> Please specify the module with the option '--modules' explicitly
>
> My system is encrypted with dm-crypt and luks, only the boot partition
> is left unencrypted.
>
> Also, during aptitude update, I get a lot of messages regarding perl
> not being able to read my locale settings
>
> Any help just to get the system up?
>
Do you have LVM snapshots? If so this bug was recently fixed upstream.
> André Nunes Batista
> Blog: http://tagesuhu.wordpress.com/
> PGP Public Key: 0x7b0590cb6722cf80
>
>
> _______________________________________________
> Pkg-grub-devel mailing list
> Pkg-grub-devel@lists.alioth.debian.org
> http://lists.alioth.debian.org/mailman/listinfo/pkg-grub-devel
--
Regards
Vladimir 'φ-coder/phcoder' Serbinenko
[signature.asc (application/pgp-signature, attachment)]
Information forwarded
to debian-bugs-dist@lists.debian.org, GRUB Maintainers <pkg-grub-devel@lists.alioth.debian.org>:
Bug#586143; Package grub-pc.
(Thu, 01 Jul 2010 23:30:02 GMT) (full text, mbox, link).
Acknowledgement sent
to André Nunes <dede.mathias@gmail.com>:
Extra info received and forwarded to list. Copy sent to GRUB Maintainers <pkg-grub-devel@lists.alioth.debian.org>.
(Thu, 01 Jul 2010 23:30:02 GMT) (full text, mbox, link).
Message #249 received at 586143@bugs.debian.org (full text, mbox, reply):
No, I do not.
I also filed another bug (#586449) and did some debugging with Colin,
but he didn't find out what it is until now.
Just in case that matter, my swap partition was also an encrypted lvm
logical volume and during the last shutdown what I actualy did was a
system hibernation. Maybe snapshots and system freezes have something
in common?
André Nunes Batista
Blog: http://tagesuhu.wordpress.com/
PGP Public Key: 0x7b0590cb6722cf80
2010/7/1 Vladimir 'φ-coder/phcoder' Serbinenko <phcoder@gmail.com>
> Do you have LVM snapshots? If so this bug was recently fixed upstream.
Information forwarded
to debian-bugs-dist@lists.debian.org, GRUB Maintainers <pkg-grub-devel@lists.alioth.debian.org>:
Bug#586143; Package grub-pc.
(Thu, 01 Jul 2010 23:55:39 GMT) (full text, mbox, link).
Acknowledgement sent
to Vladimir 'φ-coder/phcoder' Serbinenko <phcoder@gmail.com>:
Extra info received and forwarded to list. Copy sent to GRUB Maintainers <pkg-grub-devel@lists.alioth.debian.org>.
(Thu, 01 Jul 2010 23:55:39 GMT) (full text, mbox, link).
Message #254 received at 586143@bugs.debian.org (full text, mbox, reply):
[Message part 1 (text/plain, inline)]
On 07/02/2010 01:27 AM, André Nunes wrote:
> No, I do not.
>
> I also filed another bug (#586449) and did some debugging with Colin,
> but he didn't find out what it is until now.
>
> Just in case that matter, my swap partition was also an encrypted lvm
> logical volume and during the last shutdown what I actualy did was a
> system hibernation. Maybe snapshots and system freezes have something
> in common?
>
>
Is / or /boot encrypted?
> André Nunes Batista
> Blog: http://tagesuhu.wordpress.com/
> PGP Public Key: 0x7b0590cb6722cf80
>
>
> 2010/7/1 Vladimir 'φ-coder/phcoder' Serbinenko <phcoder@gmail.com>
>
>> Do you have LVM snapshots? If so this bug was recently fixed upstream.
>>
>
--
Regards
Vladimir 'φ-coder/phcoder' Serbinenko
[signature.asc (application/pgp-signature, attachment)]
Information forwarded
to debian-bugs-dist@lists.debian.org, GRUB Maintainers <pkg-grub-devel@lists.alioth.debian.org>:
Bug#586143; Package grub-pc.
(Fri, 02 Jul 2010 00:42:03 GMT) (full text, mbox, link).
Acknowledgement sent
to André Nunes <dede.mathias@gmail.com>:
Extra info received and forwarded to list. Copy sent to GRUB Maintainers <pkg-grub-devel@lists.alioth.debian.org>.
(Fri, 02 Jul 2010 00:42:03 GMT) (full text, mbox, link).
Message #259 received at 586143@bugs.debian.org (full text, mbox, reply):
/boot is not, but the rest of the system is encrypted using LVM,
dm-crypt and LUKS.
André Nunes Batista
Blog: http://tagesuhu.wordpress.com/
PGP Public Key: 0x7b0590cb6722cf80
2010/7/1 Vladimir 'φ-coder/phcoder' Serbinenko <phcoder@gmail.com>:
> On 07/02/2010 01:27 AM, André Nunes wrote:
>> No, I do not.
>>
>> I also filed another bug (#586449) and did some debugging with Colin,
>> but he didn't find out what it is until now.
>>
>> Just in case that matter, my swap partition was also an encrypted lvm
>> logical volume and during the last shutdown what I actualy did was a
>> system hibernation. Maybe snapshots and system freezes have something
>> in common?
>>
>>
> Is / or /boot encrypted?
>> André Nunes Batista
>> Blog: http://tagesuhu.wordpress.com/
>> PGP Public Key: 0x7b0590cb6722cf80
>>
>>
>> 2010/7/1 Vladimir 'φ-coder/phcoder' Serbinenko <phcoder@gmail.com>
>>
>>> Do you have LVM snapshots? If so this bug was recently fixed upstream.
>>>
>>
>
>
> --
> Regards
> Vladimir 'φ-coder/phcoder' Serbinenko
>
>
>
Bug archived.
Request was from Debbugs Internal Request <owner@bugs.debian.org>
to internal_control@bugs.debian.org.
(Fri, 30 Jul 2010 07:33:47 GMT) (full text, mbox, link).
Send a report that this bug log contains spam.
Debian bug tracking system administrator <owner@bugs.debian.org>.
Last modified:
Tue Jan 9 17:56:46 2018;
Machine Name:
buxtehude
Debian Bug tracking system
Debbugs is free software and licensed under the terms of the GNU
Public License version 2. The current version can be obtained
from https://bugs.debian.org/debbugs-source/.
Copyright © 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson,
2005-2017 Don Armstrong, and many other contributors.