Bug#495949: grub-common: grub-probe segfaults
Hi Félix Well: grub install (md0)' leads to the same error message grub-install /dev/sda then grun-install /dev/sdb leads to other problems: the device naming is not consistant from one boot to another. Sometimes I've md0 with /dev/sda1 and /dev/sdb1 and sometimes with sdb1 and adc1 while they are the same phisycal disks. So /boot/grub/device.map doesnt reflects always the real (logcal) configuration of the system. This can produce erroror. As I've seen there is a new version, I've tried again: sudo grub-install '(md0)' ... and it failed with the following message [jean-...@tangerine] % sudo grub-install '(md0)' grub-setup: warn: Attempting to install GRUB to a partitionless disk. This is a BAD idea. grub-setup: error: Embedding is not possible, but this is required when the root device is on a RAID array or LVM volume. I had a look in my raid configuration: The devices.map files has (hd0) /dev/sda (hd1) /dev/sdb But depending the way the system start, the device name is not consistant from a session to an other one. This time md0 was /dev/sdb1, /dev/sdc1 Today /dev/sda was grabbed by an external USB disk… I edited devices.map: (hd0) /dev/sdb (hd1) /dev/sdc And this time everything went fine. jean-...@tangerine] % sudo grub-install '(md0)' Installation finished. No error reported. This is the contents of the device map /boot/grub/device.map. Check if this is correct or not. If any of the lines is incorrect, fix it and re-run the script `grub-install'. (hd0) /dev/sdb (hd1) /dev/sdc Is there a mean not to have to edit by hand devices.map each time the system is rebooted? Maybe a warning as when the result is successful about possibly wrong devices.map? Regards Jean-Luc pgpws4Dj7SEOO.pgp Description: PGP signature
Bug#495949: grub-common: grub-probe segfaults
Hi Felix, Le 24/07/2009 22:52:42, Felix Zielcke a écrit : Please test if the attached patch solves it. No more segfault now but the following messages: [jean-...@tangerine] % sudo grub-install /dev/md0 ~ grub-setup: warn: Attempting to install GRUB to a partitionless disk. This is a BAD idea. grub-setup: error: Embedding is not possible, but this is required when the root device is on a RAID array or LVM volume. --- J-L pgplw94MpFANx.pgp Description: PGP signature
Bug#495949: grub-common: grub-probe segfaults
Am Samstag, den 25.07.2009, 08:43 +0200 schrieb Jean-Luc Coulon (f5ibh): Hi Felix, Le 24/07/2009 22:52:42, Felix Zielcke a écrit : Please test if the attached patch solves it. No more segfault now but the following messages: [jean-...@tangerine] % sudo grub-install /dev/md0 ~ grub-setup: warn: Attempting to install GRUB to a partitionless disk. This is a BAD idea. grub-setup: error: Embedding is not possible, but this is required when the root device is on a RAID array or LVM volume. That patch is now commited upstream so good that this is now fixed. [jean-...@tangerine] % sudo grub-install /dev/md0 You can't install to /dev/md0, either use grub-install '(md0)' or the old way with grub-install /dev/sda etc. That should work. -- Felix Zielcke Proud Debian Maintainer -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#495949: grub-common: grub-probe segfaults
Le 25/07/2009 08:50:10, Felix Zielcke a écrit : That patch is now commited upstream so good that this is now fixed. Fine [jean-...@tangerine] % sudo grub-install /dev/md0 You can't install to /dev/md0, either use grub-install '(md0)' or the old way with grub-install /dev/sda etc. That should work. Well: grub install (md0)' leads to the same error message grub-install /dev/sda then grun-install /dev/sdb leads to other problems: the device naming is not consistant from one boot to another. Sometimes I've md0 with /dev/sda1 and /dev/sdb1 and sometimes with sdb1 and adc1 while they are the same phisycal disks. So /boot/grub/device.map doesnt reflects always the real (logcal) configuration of the system. This can produce erroror. Regards Jean-Luc pgpYzsfC0rgRP.pgp Description: PGP signature
Bug#495949: grub-common: grub-probe segfaults
Am Samstag, den 25.07.2009, 10:06 +0200 schrieb Jean-Luc Coulon (f5ibh): Le 25/07/2009 08:50:10, Felix Zielcke a écrit : That patch is now commited upstream so good that this is now fixed. Fine [jean-...@tangerine] % sudo grub-install /dev/md0 You can't install to /dev/md0, either use grub-install '(md0)' or the old way with grub-install /dev/sda etc. That should work. Well: grub install (md0)' leads to the same error message Strange. That patch should only fix an uninitialised variable to fix the segfault. For me it works fine. Seems like there is somewhere else a bug. Maybe the output of grub-setup helps when you run grub-install --debug '(md0)' grub-install /dev/sda then grun-install /dev/sdb leads to other problems: the device naming is not consistant from one boot to another. Sometimes I've md0 with /dev/sda1 and /dev/sdb1 and sometimes with sdb1 and adc1 while they are the same phisycal disks. So /boot/grub/device.map doesnt reflects always the real (logcal) configuration of the system. This can produce erroror. This doestn't lucky matter. On RAID grub always reads the superblocks of all disks to assemble it. -- Felix Zielcke Proud Debian Maintainer -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#495949: grub-common: grub-probe segfaults
Am Donnerstag, den 21.08.2008, 16:48 +0200 schrieb Jean-Luc Coulon (f5ibh): Hi, While using update-grub in the kernel update, an error 130 was reported. It appears that there is a segfault in grub-probe. --8- [jean-...@tangerine] % sudo dpkg --configure -a Setting up linux-image-2.6.26-k8-3 (20080820) ... Running depmod. Finding valid ramdisk creators. Using mkinitramfs-kpkg to build the ramdisk. cryptsetup: WARNING: found more than one resume device candidate: /dev/mapper/vg0-swap_lv swap:/dev/mapper/vg0-swap_lv Running postinst hook script update-grub. Searching for GRUB installation directory ... found: /boot/grub grub-probe[8856]: segfault at 0003 ip 405881 sp 7fff0fa14130 error 4 in grub-probe[40+21000] User postinst hook script [update-grub] exited with value 139 dpkg: error processing linux-image-2.6.26-k8-3 (--configure): subprocess post-installation script returned error exit status 139 Errors were encountered while processing: linux-image-2.6.26-k8-3 --8- System is X86_64. /boot is ext3 over a raid1. The other parts of the system are xfs over lvm over raid1. I've got older versions to test. These version works on the system: 1.96+20080413-1 1.96+20080426-1 1.96+20080429-1 These don't: 1.96+20080724-7 1.96+20080724-8 But 1.96+20080724-7 has been updated on the system on august, 11th without any problem since this update. Regards Jean-Luc Hi Jean-Luc, did this ever happen again to you? -- Felix Zielcke -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#495949: grub-common: grub-probe segfaults
Hi,
I use now grub-pc 1.96+20090721-4
I've no more *this* error.
Here is the log of an update-grub command:
[jean-...@tangerine] % sudo update-grub
Generating grub.cfg ...
Found Debian background: moreblue-orbit-grub.png
Found linux image: /boot/vmlinuz-2.6.31-rc4-k8-1
Found initrd image: /boot/initrd.img-2.6.31-rc4-k8-1
Found linux image: /boot/vmlinuz-2.6.30-k8-3
Found initrd image: /boot/initrd.img-2.6.30-k8-3
Warning: update-grub_lib is deprecated, use grub-mkconfig_lib instead
Found memtest86+ image: /memtest86+.bin
done
But now, a simple grun-install command sergfaults:
[jean-...@tangerine] % sudo grub-install /dev/md0
/usr/sbin/grub-install: line 323: 17949 Erreur de segmentation
$grub_setup ${setup_verbose} ${setup_force} --directory=${grubdir} --
device-map=${device_map} ${install_device}
Regards
Jean-Luc
Le 24/07/2009 17:28:37, Felix Zielcke a écrit :
Am Donnerstag, den 21.08.2008, 16:48 +0200 schrieb Jean-Luc Coulon
(f5ibh):
Hi,
While using update-grub in the kernel update, an error 130 was
reported.
It appears that there is a segfault in grub-probe.
--8-
[jean-...@tangerine] % sudo dpkg --configure -a
Setting up linux-image-2.6.26-k8-3 (20080820) ...
Running depmod.
Finding valid ramdisk creators.
Using mkinitramfs-kpkg to build the ramdisk.
cryptsetup: WARNING: found more than one resume device candidate:
/dev/mapper/vg0-swap_lv
swap:/dev/mapper/vg0-swap_lv
Running postinst hook script update-grub.
Searching for GRUB installation directory ... found: /boot/grub
grub-probe[8856]: segfault at 0003 ip 405881 sp
7fff0fa14130 error 4
in grub-probe[40+21000]
User postinst hook script [update-grub] exited with value 139
dpkg: error processing linux-image-2.6.26-k8-3 (--configure):
subprocess post-installation script returned error exit status 139
Errors were encountered while processing:
linux-image-2.6.26-k8-3
--8-
System is X86_64.
/boot is ext3 over a raid1.
The other parts of the system are xfs over lvm over raid1.
I've got older versions to test.
These version works on the system:
1.96+20080413-1
1.96+20080426-1
1.96+20080429-1
These don't:
1.96+20080724-7
1.96+20080724-8
But 1.96+20080724-7 has been updated on the system on august, 11th
without any
problem since this update.
Regards
Jean-Luc
Hi Jean-Luc,
did this ever happen again to you?
--
Felix Zielcke
pgpzDBtLK6TdI.pgp
Description: PGP signature
Bug#495949: grub-common: grub-probe segfaults
Am Freitag, den 24.07.2009, 18:31 +0200 schrieb Jean-Luc Coulon (f5ibh):
Hi,
I use now grub-pc 1.96+20090721-4
I've no more *this* error.
Here is the log of an update-grub command:
[jean-...@tangerine] % sudo update-grub
Generating grub.cfg ...
Found Debian background: moreblue-orbit-grub.png
Found linux image: /boot/vmlinuz-2.6.31-rc4-k8-1
Found initrd image: /boot/initrd.img-2.6.31-rc4-k8-1
Found linux image: /boot/vmlinuz-2.6.30-k8-3
Found initrd image: /boot/initrd.img-2.6.30-k8-3
Warning: update-grub_lib is deprecated, use grub-mkconfig_lib instead
Found memtest86+ image: /memtest86+.bin
done
But now, a simple grun-install command sergfaults:
[jean-...@tangerine] % sudo grub-install /dev/md0
/usr/sbin/grub-install: line 323: 17949 Erreur de segmentation
$grub_setup ${setup_verbose} ${setup_force} --directory=${grubdir} --
device-map=${device_map} ${install_device}
Regards
Jean-Luc
Oh not good.
Then please do again a debug compile with `DEB_BUILD_OPTIONS=nostrip noopt
debug dpkg-buildpackage -b'
and get a backtrace with gdb.
See [0] for my previous mail but note the spaces now in
DEB_BUILD_OPTIONS instead of the commas. I was wrong.
[0] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=495949#30
--
Felix Zielcke
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#495949: grub-common: grub-probe segfaults
Hi Felix,
Jean-Luc
Oh not good.
Then please do again a debug compile with `DEB_BUILD_OPTIONS=nostrip
noopt debug dpkg-buildpackage -b'
and get a backtrace with gdb.
See [0] for my previous mail but note the spaces now in
DEB_BUILD_OPTIONS instead of the commas. I was wrong.
[0] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=495949#30
So, I rebuilt grub.
Then as I don't know how to debug directly the shell script (grub-
install), I laaunched it with set -x and got the failing line:
---8--8-8---88--
...
+ /usr/bin/grub-mkimage --output=/boot/grub/core.img '--prefix=(md0)/
grub' biosdisk ext2 pc raid mdraid
+ /usr/sbin/grub-setup --force --directory=/boot/grub --device-map=/
boot/grub/device.map /dev/md0
./grub-install: line 323: 4663 Erreur de segmentation $grub_setup
${setup_verbose} ${setup_force} --directory=${grubdir} --device-map=
${device_map} ${install_device}
+ exit 1
---8--8-8---88--
So I launched gdb as follos, I don't know if it is the right process...
but I got a (small) backtrace):
---8--8-8---88--
[jean-...@tangerine] % sudio gdb --args /usr/sbin/grub-setup --force --
directory=/boot/grub --device-map=/boot/grub/device.map /dev/md0
GNU gdb (GDB) 6.8.50.20090628-cvs-debian
Copyright (C) 2009 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/
gpl.html
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type show
copying
and show warranty for details.
This GDB was configured as x86_64-linux-gnu.
For bug reporting instructions, please see:
http://www.gnu.org/software/gdb/bugs/...
(gdb) run
Starting program: /usr/sbin/grub-setup --force --directory=/boot/grub
--device-map=/boot/grub/device.map /dev/md0
Program received signal SIGSEGV, Segmentation fault.
0x77b08c60 in strcmp () from /lib/libc.so.6
(gdb) bt
#0 0x77b08c60 in strcmp () from /lib/libc.so.6
#1 0x00401cb1 in setup (dir=0x63e010 /boot/grub,
boot_file=0x4279f4 boot.img, core_file=0x4279eb core.img,
root=0x64b9c0 md0, dest=0x0, must_embed=1, force=1)
at /usr/local/src/tmp/grub/grub2-1.96+20090721/util/i386/pc/grub-
setup.c:335
#2 0x00402cea in main (argc=5, argv=0x7fffe8a8)
at /usr/local/src/tmp/grub/grub2-1.96+20090721/util/i386/pc/grub-
setup.c:774
(gdb)
---8--8-8---88--
Best regards
Jean-Luc
pgpUEr7SN00QG.pgp
Description: PGP signature
Bug#495949: grub-common: grub-probe segfaults
Am Freitag, den 24.07.2009, 20:40 +0200 schrieb Jean-Luc Coulon (f5ibh):
Hi Felix,
Jean-Luc
Oh not good.
Then please do again a debug compile with `DEB_BUILD_OPTIONS=nostrip
noopt debug dpkg-buildpackage -b'
and get a backtrace with gdb.
See [0] for my previous mail but note the spaces now in
DEB_BUILD_OPTIONS instead of the commas. I was wrong.
[0] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=495949#30
So, I rebuilt grub.
Then as I don't know how to debug directly the shell script (grub-
install), I laaunched it with set -x and got the failing line:
---8--8-8---88--
...
+ /usr/bin/grub-mkimage --output=/boot/grub/core.img '--prefix=(md0)/
grub' biosdisk ext2 pc raid mdraid
+ /usr/sbin/grub-setup --force --directory=/boot/grub --device-map=/
boot/grub/device.map /dev/md0
./grub-install: line 323: 4663 Erreur de segmentation $grub_setup
${setup_verbose} ${setup_force} --directory=${grubdir} --device-map=
${device_map} ${install_device}
+ exit 1
---8--8-8---88--
So I launched gdb as follos, I don't know if it is the right process...
but I got a (small) backtrace):
---8--8-8---88--
[jean-...@tangerine] % sudio gdb --args /usr/sbin/grub-setup --force --
directory=/boot/grub --device-map=/boot/grub/device.map /dev/md0
GNU gdb (GDB) 6.8.50.20090628-cvs-debian
Copyright (C) 2009 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/
gpl.html
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type show
copying
and show warranty for details.
This GDB was configured as x86_64-linux-gnu.
For bug reporting instructions, please see:
http://www.gnu.org/software/gdb/bugs/...
(gdb) run
Starting program: /usr/sbin/grub-setup --force --directory=/boot/grub
--device-map=/boot/grub/device.map /dev/md0
Program received signal SIGSEGV, Segmentation fault.
0x77b08c60 in strcmp () from /lib/libc.so.6
(gdb) bt
#0 0x77b08c60 in strcmp () from /lib/libc.so.6
#1 0x00401cb1 in setup (dir=0x63e010 /boot/grub,
boot_file=0x4279f4 boot.img, core_file=0x4279eb core.img,
root=0x64b9c0 md0, dest=0x0, must_embed=1, force=1)
at /usr/local/src/tmp/grub/grub2-1.96+20090721/util/i386/pc/grub-
setup.c:335
#2 0x00402cea in main (argc=5, argv=0x7fffe8a8)
at /usr/local/src/tmp/grub/grub2-1.96+20090721/util/i386/pc/grub-
setup.c:774
(gdb)
---8--8-8---88--
Best regards
Jean-Luc
Please test if the attached patch solves it.
--
Felix Zielcke
Index: util/i386/pc/grub-setup.c
===
--- util/i386/pc/grub-setup.c (Revision 2441)
+++ util/i386/pc/grub-setup.c (Revision 2442)
@@ -329,10 +329,18 @@
dest_partmap = p-partmap-name;
return 1;
}
+ dest_partmap = 0;
grub_partition_iterate (dest_dev-disk, identify_partmap);
+ if (! dest_partmap)
+{
+ grub_util_warn (Attempting to install GRUB to a partitionless disk. This is a BAD idea.);
+ goto unable_to_embed;
+}
+
grub_partition_iterate (dest_dev-disk, (strcmp (dest_partmap, pc_partition_map) ?
find_usable_region_gpt : find_usable_region_msdos));
+
if (embed_region.end == embed_region.start)
{
if (! strcmp (dest_partmap, pc_partition_map))
Bug#495949: grub-common: grub-probe segfaults
Hi Felix Le 21.08.2008 17:29:57, Felix Zielcke a écrit : There is no disk *removed*. BUT the device name of the disks allocated by the system to the disks is not consistant from one boot to the other. Well I mean something like that in `mdadm -Q --detail /dev/md0' output: Today, the disks where affected an other way: - sda and sdb for the raid1 and sdc for the other disk This way, the latest available version of grub-common (20080724) works. Attached the output of mdadm -Q -D for each of the arrays. Regards Jean-Luc /dev/md0: Version : 00.90 Creation Time : Sun Feb 17 17:50:51 2008 Raid Level : raid1 Array Size : 232832 (227.41 MiB 238.42 MB) Used Dev Size : 232832 (227.41 MiB 238.42 MB) Raid Devices : 2 Total Devices : 2 Preferred Minor : 0 Persistence : Superblock is persistent Update Time : Sun Aug 24 10:22:47 2008 State : clean Active Devices : 2 Working Devices : 2 Failed Devices : 0 Spare Devices : 0 UUID : 19628d78:d50fb284:cc328929:8db8e0da Events : 0.199 Number Major Minor RaidDevice State 0 810 active sync /dev/sda1 1 8 171 active sync /dev/sdb1 /dev/md0: Version : 00.90 Creation Time : Sun Feb 17 17:50:51 2008 Raid Level : raid1 Array Size : 232832 (227.41 MiB 238.42 MB) Used Dev Size : 232832 (227.41 MiB 238.42 MB) Raid Devices : 2 Total Devices : 2 Preferred Minor : 0 Persistence : Superblock is persistent Update Time : Sun Aug 24 10:22:53 2008 State : clean Active Devices : 2 Working Devices : 2 Failed Devices : 0 Spare Devices : 0 UUID : 19628d78:d50fb284:cc328929:8db8e0da Events : 0.198 Number Major Minor RaidDevice State 0 810 active sync /dev/sda1 1 8 171 active sync /dev/sdb1 /dev/md0: Version : 00.90 Creation Time : Sun Feb 17 17:50:51 2008 Raid Level : raid1 Array Size : 232832 (227.41 MiB 238.42 MB) Used Dev Size : 232832 (227.41 MiB 238.42 MB) Raid Devices : 2 Total Devices : 2 Preferred Minor : 0 Persistence : Superblock is persistent Update Time : Sun Aug 24 10:22:54 2008 State : clean Active Devices : 2 Working Devices : 2 Failed Devices : 0 Spare Devices : 0 UUID : 19628d78:d50fb284:cc328929:8db8e0da Events : 0.198 Number Major Minor RaidDevice State 0 810 active sync /dev/sda1 1 8 171 active sync /dev/sdb1 pgpSxCPXQpGPL.pgp Description: PGP signature
Bug#495949: grub-common: grub-probe segfaults
Package: grub-common Version: 1.96+20080724-8 Severity: important -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, While using update-grub in the kernel update, an error 130 was reported. It appears that there is a segfault in grub-probe. - --8- [EMAIL PROTECTED] % sudo dpkg --configure -a Setting up linux-image-2.6.26-k8-3 (20080820) ... Running depmod. Finding valid ramdisk creators. Using mkinitramfs-kpkg to build the ramdisk. cryptsetup: WARNING: found more than one resume device candidate: /dev/mapper/vg0-swap_lv swap:/dev/mapper/vg0-swap_lv Running postinst hook script update-grub. Searching for GRUB installation directory ... found: /boot/grub grub-probe[8856]: segfault at 0003 ip 405881 sp 7fff0fa14130 error 4 in grub-probe[40+21000] User postinst hook script [update-grub] exited with value 139 dpkg: error processing linux-image-2.6.26-k8-3 (--configure): subprocess post-installation script returned error exit status 139 Errors were encountered while processing: linux-image-2.6.26-k8-3 - --8- System is X86_64. /boot is ext3 over a raid1. The other parts of the system are xfs over lvm over raid1. I've got older versions to test. These version works on the system: 1.96+20080413-1 1.96+20080426-1 1.96+20080429-1 These don't: 1.96+20080724-7 1.96+20080724-8 But 1.96+20080724-7 has been updated on the system on august, 11th without any problem since this update. Regards Jean-Luc - -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (900, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.26-k8-3 (SMP w/2 CPU cores; PREEMPT) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages grub-common depends on: ii base-files4.0.5 Debian base system miscellaneous f ii libc6 2.7-13 GNU C Library: Shared libraries grub-common recommends no packages. Versions of packages grub-common suggests: ii multiboot-doc 0.97-46The Multiboot specification - -- no debconf information -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iD8DBQFIrYAoUdGGXzzGnNARAmygAJ4x5pFcT5TckC8GPFSlUA/ZY29C8ACcDgJP Cdke+sUEpXSmGYwdlAIa+60= =FjRk -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#495949: grub-common: grub-probe segfaults
Am Donnerstag, den 21.08.2008, 16:48 +0200 schrieb Jean-Luc Coulon (f5ibh): Hi, Hello, While using update-grub in the kernel update, an error 130 was reported. It appears that there is a segfault in grub-probe. There's one which is not yet fixed upstream and because you're using raid1 I suspect it's the one you have. Please do `mdadm -Q --detail /dev/md0' for all your md devices you have. If there's one disk removed then grub-probe segfaults. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#495949: grub-common: grub-probe segfaults
Hello Felix, Le 21.08.2008 17:02:07, Felix Zielcke a écrit : There's one which is not yet fixed upstream and because you're using raid1 I suspect it's the one you have. Please do `mdadm -Q --detail /dev/md0' for all your md devices you have. If there's one disk removed then grub-probe segfaults. There is no disk *removed*. BUT the device name of the disks allocated by the system to the disks is not consistant from one boot to the other. Yesterday, the main disks (raid) was on /dev/sda and /dev/sdb, with an other disk with data /dev/sdc. Today, the disk of data is /dev/sda and the raid disks are /dev/sdb and /dev/sdc They are all sata disks. Bests Jean-Luc pgpvmD2prkTQE.pgp Description: PGP signature
Bug#495949: grub-common: grub-probe segfaults
Am Donnerstag, den 21.08.2008, 17:14 +0200 schrieb Jean-Luc Coulon (f5ibh): Hello Felix, Le 21.08.2008 17:02:07, Felix Zielcke a écrit : There's one which is not yet fixed upstream and because you're using raid1 I suspect it's the one you have. Please do `mdadm -Q --detail /dev/md0' for all your md devices you have. If there's one disk removed then grub-probe segfaults. There is no disk *removed*. BUT the device name of the disks allocated by the system to the disks is not consistant from one boot to the other. Well I mean something like that in `mdadm -Q --detail /dev/md0' output: (Don't worry about it, this is from a bugreport I did on mdadm) Number Major Minor RaidDevice State 0 000 removed 1 001 removed 2 002 removed 3 8 813 active sync /dev/sdf1 4 8 65- spare /dev/sde1 5 8 49- spare /dev/sdd1 6 8 33- spare /dev/sdc1 This is the only segfault in grub-probe I know of, which is already fixed in a patch from one of the upstream developers. It's just not yet commited. If this is not the problem you have then I don't have a single clue why there's another reason for a segfault in it :( -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#495949: grub-common: grub-probe segfaults
Le 21.08.2008 17:29:57, Felix Zielcke a écrit : There is no disk *removed*. BUT the device name of the disks allocated by the system to the disks is not consistant from one boot to the other. Well I mean something like that in `mdadm -Q --detail /dev/md0' output: (Don't worry about it, this is from a bugreport I did on mdadm) Number Major Minor RaidDevice State 0 000 removed 1 001 removed 2 002 removed 3 8 813 active sync /dev/sdf1 4 8 65- spare /dev/sde1 5 8 49- spare /dev/sdd1 6 8 33- spare /dev/sdc1 This is the only segfault in grub-probe I know of, which is already fixed in a patch from one of the upstream developers. It's just not yet commited. If this is not the problem you have then I don't have a single clue why there's another reason for a segfault in it :( As I old, I've nothing removed: /dev/md0 Number Major Minor RaidDevice State 0 8 170 active sync /dev/sdb1 1 8 331 active sync /dev/sdc1 /dev/md1 Number Major Minor RaidDevice State 0 8 180 active sync /dev/sdb2 1 8 341 active sync /dev/sdc2 /dev/md2 Number Major Minor RaidDevice State 0 8 190 active sync /dev/sdb3 1 8 351 active sync /dev/sdc3 Regards Jean-Luc pgpCy2b0fL1cT.pgp Description: PGP signature
Bug#495949: grub-common: grub-probe segfaults
Am Donnerstag, den 21.08.2008, 17:35 +0200 schrieb Jean-Luc Coulon (f5ibh): As I old, I've nothing removed: Ok just though you misunderstood me, well I even hoped that. Do you have maybe other mdraid super blocks lying around on other partitions `mdadm --zero-superblock /dev/sdxy' would get rid of them. GRUB and grub-probe use the superblock directly they find on the disk. Even grub-probe doestn't use at all the informations from the assembled RAIDs it could get from kernel (for example /proc/mdstat) If this doestn't solve your problem then please do a debug compile with: apt-get build-dep grub2 apt-get source grub2 DEB_BUILD_OPTIONS=nostrip,noopt,debug dpkg-buildpackage -b You may need a `deb-src' line in /etc/apt/sources.list for this. It's just the same as the `deb' one, just with `-src' grub-probe is in grub-common To get the core file you need to do `ulimit -c unlimited' first. I don't know where the core file then be placed but maybe it just segfaults ifyou just run `grub-probe /' Then you should have a `core' file in your current directory. Else do `find / -name *core*' Would be very good if you would forward this to [EMAIL PROTECTED] (but you need to subscribe first) and the /usr/sbin/grub-probe else the corefile is useless. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#495949: grub-common: grub-probe segfaults
Le 21.08.2008 17:52:46, Felix Zielcke a écrit : Am Donnerstag, den 21.08.2008, 17:35 +0200 schrieb Jean-Luc Coulon (f5ibh): As I told, I've nothing removed: Ok just though you misunderstood me, well I even hoped that. Do you have maybe other mdraid super blocks lying around on other partitions `mdadm --zero-superblock /dev/sdxy' would get rid of them. All the raid disks I have are used, active and clean. The disk which is out of the raid doesnt have a syperblock [EMAIL PROTECTED] % sudo mdadm -E /dev/sda1 mdadm: No md superblock detected on /dev/sda1. GRUB and grub-probe use the superblock directly they find on the disk. Even grub-probe doestn't use at all the informations from the assembled RAIDs it could get from kernel (for example /proc/mdstat) If this doestn't solve your problem then please do a debug compile with: apt-get build-dep grub2 apt-get source grub2 DEB_BUILD_OPTIONS=nostrip,noopt,debug dpkg-buildpackage -b You may need a `deb-src' line in /etc/apt/sources.list for this. It's just the same as the `deb' one, just with `-src' Ok, done. grub-probe is in grub-common To get the core file you need to do `ulimit -c unlimited' first. I don't know where the core file then be placed but maybe it just segfaults ifyou just run `grub-probe /' Then you should have a `core' file in your current directory. Else do `find / -name *core*' Would be very good if you would forward this to [EMAIL PROTECTED] (but you need to subscribe first) and the /usr/sbin/grub-probe else the corefile is useless. Please find attached the core and the backtrace of a gdb session. Regards Jean-Luc core.bz2 Description: application/bzip Program received signal SIGSEGV, Segmentation fault. 0x00406ac7 in grub_strlen ( s=0x0003 Address 0x0003 out of bounds) at /usr/local/src/tmp/grub2/grub2-1.96+20080724/kern/misc.c:531 531 while (*p) (gdb) bt #0 0x00406ac7 in grub_strlen ( s=0x0003 Address 0x0003 out of bounds) at /usr/local/src/tmp/grub2/grub2-1.96+20080724/kern/misc.c:531 #1 0x004069ad in grub_strdup ( s=0x0003 Address 0x0003 out of bounds) at /usr/local/src/tmp/grub2/grub2-1.96+20080724/kern/misc.c:487 #2 0x00404f5e in grub_disk_open ( name=0x0003 Address 0x0003 out of bounds) at /usr/local/src/tmp/grub2/grub2-1.96+20080724/kern/disk.c:230 #3 0x00423992 in grub_raid_scan_device ( name=0x0003 Address 0x0003 out of bounds) at /usr/local/src/tmp/grub2/grub2-1.96+20080724/disk/raid.c:363 #4 0x004049e6 in iterate_disk ( disk_name=0x0003 Address 0x0003 out of bounds) at /usr/local/src/tmp/grub2/grub2-1.96+20080724/kern/device.c:93 #5 0x00421ddf in grub_lvm_iterate (hook=0x7fff40743608) at /usr/local/src/tmp/grub2/grub2-1.96+20080724/disk/lvm.c:53 #6 0x00404e9e in grub_disk_dev_iterate (hook=0x7fff40743608) at /usr/local/src/tmp/grub2/grub2-1.96+20080724/kern/disk.c:205 #7 0x00404900 in grub_device_iterate ( hook=0x42394d grub_raid_scan_device) at /usr/local/src/tmp/grub2/grub2-1.96+20080724/kern/device.c:138 #8 0x00423fe4 in grub_mod_init (mod=0x0) ---Type return to continue, or q return to quit--- at /usr/local/src/tmp/grub2/grub2-1.96+20080724/disk/raid.c:582 #9 0x00423fcc in grub_raid_init () at /usr/local/src/tmp/grub2/grub2-1.96+20080724/disk/raid.c:580 #10 0x00424096 in grub_init_all () at grub_probe_init.c:46 #11 0x00401d80 in main (argc=2, argv=0x7fff407437b8) at /usr/local/src/tmp/grub2/grub2-1.96+20080724/util/grub-probe.c:366 (gdb) (gdb) quit pgppAJzuTGWCr.pgp Description: PGP signature
Bug#495949: grub-common: grub-probe segfaults
Am Donnerstag, den 21.08.2008, 18:40 +0200 schrieb Jean-Luc Coulon (f5ibh): Hi, Would be very good if you would forward this to [EMAIL PROTECTED] (but you need to subscribe first) and the /usr/sbin/grub-probe else the corefile is useless. Please find attached the core and the backtrace of a gdb session. Thanks very much, but as you can see from my sentence above the core file alone is unfortunately not that helpful. And I have assumed that you didn't know about gdb, else I would have told you to use `bt full' that gives a bit more useful output :) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#495949: grub-common: grub-probe segfaults
Am Donnerstag, den 21.08.2008, 19:12 +0200 schrieb Jean-Luc Coulon (f5ibh): So, attached the bt full output and the grub-probe binary (bzip2, warning, it is built for X86_64). That's what I'm using too I have now even compiled myself the 24-8 and used that grub-probe binary with your core file. I haven't thought that this would work. It's very weird, I really don't understand the backtrace. It looks like really severe memory corruption. Seems like it has something to do with your LVM or RAID so maybe output of: lvdisplay vgdisplay pvdisplay mdadm -Q --detail /dev/md0 mdadm -Q --detail /dev/md1 mdadm -Q --detail /dev/md2 helps. Remark, I subscribe grub-devel list but my message was rejeted :-o The list mail erver has unfortunately sometimes problems, I noticed this myself :( would be very nice of you if you send another mail to grub-devel after you made sure you get the `welcome to grub-devel' mail, else I just forward it but I think it's better to have the discussion with you :) And on grub-devel there's not only Robert and me but the others too. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#495949: grub-common: grub-probe segfaults
Le 21.08.2008 19:31:04, Felix Zielcke a écrit : Am Donnerstag, den 21.08.2008, 19:12 +0200 schrieb Jean-Luc Coulon (f5ibh): So, attached the bt full output and the grub-probe binary (bzip2, warning, it is built for X86_64). That's what I'm using too I have now even compiled myself the 24-8 and used that grub-probe binary with your core file. I haven't thought that this would work. It's very weird, I really don't understand the backtrace. It looks like really severe memory corruption. Seems like it has something to do with your LVM or RAID so maybe output of: lvdisplay vgdisplay pvdisplay mdadm -Q --detail /dev/md0 mdadm -Q --detail /dev/md1 mdadm -Q --detail /dev/md2 Ok. Attached the output of each command. (/dev/md2 is encrypted with luks). helps. Remark, I subscribe grub-devel list but my message was rejeted :-o The list mail erver has unfortunately sometimes problems, I noticed this myself :( would be very nice of you if you send another mail to grub-devel after you made sure you get the `welcome to grub-devel' mail, else I just forward it but I think it's better to have the discussion with you :) And on grub-devel there's not only Robert and me but the others too. J-L --- Logical volume --- LV Name/dev/cryptvg0/opt_lv VG Namecryptvg0 LV UUIDopnuev-fu0Z-pW1K-8qMB-vZnY-KCPx-juG5zQ LV Write Accessread/write LV Status available # open 1 LV Size3.17 GB Current LE 812 Segments 3 Allocation inherit Read ahead sectors auto - currently set to 256 Block device 253:5 --- Logical volume --- LV Name/dev/cryptvg0/local_lv VG Namecryptvg0 LV UUIDcWKbtN-KTTr-kTiv-wZUs-y5oE-svJ1-FNy6E0 LV Write Accessread/write LV Status available # open 1 LV Size3.88 GB Current LE 993 Segments 3 Allocation inherit Read ahead sectors auto - currently set to 256 Block device 253:6 --- Logical volume --- LV Name/dev/cryptvg0/tmp_lv VG Namecryptvg0 LV UUIDjfBWUN-97E3-7430-QXv5-rzqe-CKFj-Fucqa6 LV Write Accessread/write LV Status available # open 1 LV Size6.00 GB Current LE 1536 Segments 1 Allocation inherit Read ahead sectors auto - currently set to 256 Block device 253:7 --- Logical volume --- LV Name/dev/cryptvg0/photos_lv VG Namecryptvg0 LV UUIDsyYrHg-zvse-wRkr-9ae5-PoCG-0cl8-KNhyXY LV Write Accessread/write LV Status available # open 1 LV Size11.50 GB Current LE 2944 Segments 2 Allocation inherit Read ahead sectors auto - currently set to 256 Block device 253:8 --- Logical volume --- LV Name/dev/cryptvg0/music_lv VG Namecryptvg0 LV UUID5C3fYQ-5Snq-dM2Q-L4nX-Obkb-ZI1B-2lTIDE LV Write Accessread/write LV Status available # open 1 LV Size3.15 GB Current LE 806 Segments 3 Allocation inherit Read ahead sectors auto - currently set to 256 Block device 253:9 --- Logical volume --- LV Name/dev/cryptvg0/iso_lv VG Namecryptvg0 LV UUIDQIQ1r4-FqEL-at2b-qeZo-Fik0-939G-g4cJuh LV Write Accessread/write LV Status available # open 0 LV Size5.00 GB Current LE 1280 Segments 1 Allocation inherit Read ahead sectors auto - currently set to 256 Block device 253:10 --- Logical volume --- LV Name/dev/cryptvg0/mail_lv VG Namecryptvg0 LV UUIDnXn8gJ-v4zn-qQi5-xLFc-znav-q6uS-hfJur9 LV Write Accessread/write LV Status available # open 1 LV Size1.00 GB Current LE 256 Segments 1 Allocation inherit Read ahead sectors auto - currently set to 256 Block device 253:11 --- Logical volume --- LV Name/dev/cryptvg0/home_lv VG Namecryptvg0 LV UUIDkoR32q-Wi3i-TrMB-nufP-Bcc8-acx2-3AtfaO LV Write Accessread/write LV Status available # open 1 LV Size4.68 GB Current LE 1199 Segments 2 Allocation inherit
