Neither / nor /boot are on raid. I have the folowing layout:
sda1, sdb1, sdc1 are on md1, raid 1, not mounted
sda2, sdb2, sdc2 are on md0, raid 5, which form lvm vg jupiter in this
vg is /var, /tmp and other data partitions
sdd1 is /boot
sdd2 is lvm vg jupisdd, in this vg is /root, /usr
Here is t
Am Sonntag, den 12.04.2009, 14:27 +0200 schrieb Felix Koop:
> Here is the backtrace:
>
> (gdb) file grub-probe
> Reading symbols from /usr/src/grub2-1.96
> +20090317/build/grub-common/grub-probe...done.
> (gdb) run --target=device /
> Starting program: /usr/src/grub2-1.96
> +20090317/build/grub-co
Here is the backtrace:
(gdb) file grub-probe
Reading symbols from /usr/src/grub2-1.96
+20090317/build/grub-common/grub-probe...done.
(gdb) run --target=device /
Starting program: /usr/src/grub2-1.96
+20090317/build/grub-common/grub-probe --target=device /
/dev/mapper/jupisdd-root
Program received
Am Sonntag, den 12.04.2009, 13:29 +0200 schrieb Felix Koop:
> When running the following command
>
> grub-probe --target=device /
>
> it returns the correct result, but produces a floating point exception
> afterwards. This has as a consequence that I cannot install any new
> kernels any more.
Package: grub-common
Version: 1.96+20090317-1
Severity: important
When running the following command
grub-probe --target=device /
it returns the correct result, but produces a floating point exception
afterwards. This has as a consequence that I cannot install any new
kernels any more. Going
5 matches
Mail list logo
