Bug#487565: grub-pc: Chainloading fails even without LVM

2008-08-03 Thread Kai Wasserbäch
Hello Robert, hello Felix
Robert Millan wrote:
 I see that Felix suspects this is a false positive when checking for 
 cross-disk
 install.  If you run sh -x grub-install and send us the output, we could
 make sure about that.

You'll find the output of the following command in the attachment of this e-mail
(only stderr):
# sh -x grub-install --no-floppy --grub-setup=/bin/true (hd0)
The »--no-floppy --grub-setup=«-part is taken from Felix first e-mail, as I do
not want to install GrUB2 into my MBR until I'm not sure it works.

 HOWEVER, even if it's a false positive, the UUID boot path is supposed to 
 work;
 So please check the 32-bit (actually 16-byte) code you mentioned above.  Is it
 the same as deed8901-3bdc-4912-a2c3-cff34ddeb147 ?

Sorry for messing up the size, I tried to recollect that from memory and wasn't
sure about the value anymore. ;)
The UUID you've given should be shown on the rescue console in that error
message, right? If that was the question, yes it is shown as the UUID value.

Felix Zielcke wrote:
 Please type on the rescue prompt of grub set
 and then tell us the value of prefix and root

»rescue set« yielded:
prefix=(hd1,5)(UUID=deed8901-3bdc-4912-a2c3-cff34ddeb147)/grub/
root=(hd1,5)

I hope, this helps in solving the problem.

Thank you for your replys,
Kai



-- 

Kai Wasserbäch (Kai Wasserbaech)

E-Mail: [EMAIL PROTECTED]
Jabber (debianforum.de): Drizzt
URL: http://wiki.debianforum.de/Drizzt_Do%27Urden
GnuPG: 0xE1DE59D2  0600 96CE F3C8 E733 E5B6 1587 A309 D76C E1DE 59D2
(http://pgpkeys.pca.dfn.de/pks/lookup?search=0xE1DE59D2fingerprint=onhash=onop=vindex)

+ transform=s,x,x,
+ prefix=/usr
+ exec_prefix=/usr
+ sbindir=/usr/sbin
+ bindir=/usr/bin
+ libdir=/usr/lib
+ PACKAGE_NAME=GRUB
+ PACKAGE_TARNAME=grub
+ PACKAGE_VERSION=1.96
+ target_cpu=i386
+ platform=pc
++ sed s,x,x,
+ pkglibdir=/usr/lib/grub/i386-pc
++ echo grub-setup
++ sed s,x,x,
+ grub_setup=/usr/sbin/grub-setup
++ echo grub-mkimage
++ sed s,x,x,
+ grub_mkimage=/usr/bin/grub-mkimage
++ echo grub-mkdevicemap
++ sed s,x,x,
+ grub_mkdevicemap=/usr/sbin/grub-mkdevicemap
++ echo grub-probe
++ sed s,x,x,
+ grub_probe=/usr/sbin/grub-probe
+ rootdir=
++ echo /boot/grub
++ sed s,x,x,
+ grub_prefix=/boot/grub
+ modules=
+ install_device=
+ no_floppy=
+ force_lba=
+ recheck=no
+ debug=no
+ for option in '$@'
+ case $option in
+ no_floppy=--no-floppy
+ for option in '$@'
+ case $option in
++ echo --grub-setup=/bin/true
++ sed s/--grub-setup=//
+ grub_setup=/bin/true
+ for option in '$@'
+ case $option in
+ test x '!=' x
+ install_device='(hd0)'
+ . /usr/lib/grub/update-grub_lib
++ transform=s,x,x,
++ prefix=/usr
++ exec_prefix=/usr
++ datarootdir=/usr/share
++ datadir=/usr/share
++ sbindir=/usr/sbin
+++ echo grub
+++ sed s,x,x,
++ pkgdatadir=/usr/share/grub
+++ echo grub-probe
+++ sed s,x,x,
++ grub_probe=/usr/sbin/grub-probe
+ test 'x(hd0)' = x
+ test no = yes
+ case $host_os in
+ bootdir=/boot
++ echo grub
++ sed s,x,x,
+ grubdir=/boot/grub
+ device_map=/boot/grub/device.map
+ grub_probe='/usr/sbin/grub-probe --device-map=/boot/grub/device.map'
+ set /bin/true dummy
+ test -f /bin/true
+ :
+ set /usr/bin/grub-mkimage dummy
+ test -f /usr/bin/grub-mkimage
+ :
+ set /usr/sbin/grub-mkdevicemap dummy
+ test -f /usr/sbin/grub-mkdevicemap
+ :
+ test -d /boot
+ test -d /boot/grub
+ test no = yes
+ test -f /boot/grub/device.map
+ :
++ sed -n '/^([fh]d[0-9]*)/s/\(^(.*)\).*/\1/p' /boot/grub/device.map
++ sort
++ uniq -d
++ sed -n 1p
+ tmp=
+ test -n ''
+ for file in '${grubdir}/*.mod' '${grubdir}/*.lst' '${grubdir}/*.img'
+ test -f /boot/grub/acorn.mod
++ basename /boot/grub/acorn.mod
+ '[' acorn.mod '!=' menu.lst ']'
+ rm -f /boot/grub/acorn.mod
+ for file in '${grubdir}/*.mod' '${grubdir}/*.lst' '${grubdir}/*.img'
+ test -f /boot/grub/affs.mod
++ basename /boot/grub/affs.mod
+ '[' affs.mod '!=' menu.lst ']'
+ rm -f /boot/grub/affs.mod
+ for file in '${grubdir}/*.mod' '${grubdir}/*.lst' '${grubdir}/*.img'
+ test -f /boot/grub/afs.mod
++ basename /boot/grub/afs.mod
+ '[' afs.mod '!=' menu.lst ']'
+ rm -f /boot/grub/afs.mod
+ for file in '${grubdir}/*.mod' '${grubdir}/*.lst' '${grubdir}/*.img'
+ test -f /boot/grub/amiga.mod
++ basename /boot/grub/amiga.mod
+ '[' amiga.mod '!=' menu.lst ']'
+ rm -f /boot/grub/amiga.mod
+ for file in '${grubdir}/*.mod' '${grubdir}/*.lst' '${grubdir}/*.img'
+ test -f /boot/grub/aout.mod
++ basename /boot/grub/aout.mod
+ '[' aout.mod '!=' menu.lst ']'
+ rm -f /boot/grub/aout.mod
+ for file in '${grubdir}/*.mod' '${grubdir}/*.lst' '${grubdir}/*.img'
+ test -f /boot/grub/apple.mod
++ basename /boot/grub/apple.mod
+ '[' apple.mod '!=' menu.lst ']'
+ rm -f /boot/grub/apple.mod
+ for file in '${grubdir}/*.mod' '${grubdir}/*.lst' '${grubdir}/*.img'
+ test -f /boot/grub/ata.mod
++ basename /boot/grub/ata.mod
+ '[' ata.mod '!=' menu.lst ']'
+ rm -f /boot/grub/ata.mod
+ for file in '${grubdir}/*.mod' '${grubdir}/*.lst' '${grubdir}/*.img'
+ test -f /boot/grub/biosdisk.mod
++ basename /boot/grub/biosdisk.mod
+ '[' 

Bug#487565: grub-pc: Chainloading fails even without LVM

2008-08-03 Thread Felix Zielcke
Hello,

Am Sonntag, den 03.08.2008, 08:49 +0200 schrieb Kai Wasserbäch:
 Hello Robert, hello Felix
 Robert Millan wrote:
  I see that Felix suspects this is a false positive when checking for 
  cross-disk
  install.  If you run sh -x grub-install and send us the output, we could
  make sure about that.

As I already told him privately in german the problem is
device.map says
(hd0) /dev/hdc
(hd1) /dev/hdd

But /proc/mounts says everything inclusive /boot is on /dev/hdd

I don't know if this should be changed, but better not discuss this in
this report ;)

 I hope, this helps in solving the problem.


Thanks this double prefix issue is now solved with the ..24-5 upload we
made this night and Robert uploaded :)


As soon as you got the new ..24-5 version, please do
grub-install --grub-setup=/bin/true (hd0) so core.img gets recreated,
if you still want to chainload it.
Or for the Linux mdraid guys you can use (md0) if your /boot is
on /dev/md0

This issue doestn't exist with grub2 in mbr and so core.img gets
directly loaded by it.




--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#487565: grub-pc: Chainloading fails even without LVM

2008-08-02 Thread Felix Zielcke
retitle 487565 multibooting core.img leads to double prefix
thanks

Am Samstag, den 02.08.2008, 06:06 +0200 schrieb Kai Wasserbäch:
 Followup-For: Bug #487565
 Package: grub-pc
 Version: 1.96+20080724-2
 
 Hello,

Hello,

 I'm not using an LVM on this machine and still get the error that the file
 normal.mod can not be found and in the error message there is an doubleslash
 displayed (something along the lines UUID={32Bit-Code}/boot/grub//normal.mod).
 
 I installed GRUB2 yesterday, updating from a GRUB1. I installed it in
 chainloader mode as was advised in the Debconf message (per pre-selection).
 
 As I'm not quite sure which kind of additional/further information you may 
 need,
 please feel free to ask me for any.

Please type on the rescue prompt of grub set
and then tell us the value of prefix and root

You use only /dev/hdd on your linux but it's (hd1) in device.map
If you're BIOS directly boots from hdd then change your device.map
please, it will only be regenerated if it doestn't exist or is clearly
wrong i.e. missing devices.
Or do you have grub-legacy somehow on (hd0) sdc installed and loading
grub2 from (hd1) sdd?




--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#487565: grub-pc: Chainloading fails even without LVM

2008-08-02 Thread Felix Zielcke
Am Samstag, den 02.08.2008, 11:31 +0200 schrieb Felix Zielcke:

 You use only /dev/hdd on your linux but it's (hd1) in device.map
 If you're BIOS directly boots from hdd then change your device.map
 please, it will only be regenerated if it doestn't exist or is clearly
 wrong i.e. missing devices.


Bah, again something which I should do in one email and not 2.
Because you have an UUID prefix, I think your device.map order is the
problem.
grub2 is thinking you want a cross install i.e. have the mbr code on hd0
but /boot on hd1
So if that's the case please change device.map and then do

grub-install --no-floppy --grub-setup=/bin/true (hd0)

That's what postinst does to generate the core.img
with --grub-setup=/bin/true your MBR won't change.




-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#487565: grub-pc: Chainloading fails even without LVM

2008-08-02 Thread Robert Millan
On Sat, Aug 02, 2008 at 06:06:22AM +0200, Kai Wasserbäch wrote:
 Followup-For: Bug #487565
 Package: grub-pc
 Version: 1.96+20080724-2
 
 Hello,
 I'm not using an LVM on this machine and still get the error that the file
 normal.mod can not be found and in the error message there is an doubleslash
 displayed (something along the lines UUID={32Bit-Code}/boot/grub//normal.mod).

The doubleslash is merely a distraction.  I fixed it in upstream, but I don't
think it's the cause of your problem.

I see that Felix suspects this is a false positive when checking for cross-disk
install.  If you run sh -x grub-install and send us the output, we could
make sure about that.

HOWEVER, even if it's a false positive, the UUID boot path is supposed to work;
So please check the 32-bit (actually 16-byte) code you mentioned above.  Is it
the same as deed8901-3bdc-4912-a2c3-cff34ddeb147 ?

Thanks

-- 
Robert Millan

  The DRM opt-in fallacy: Your data belongs to us. We will decide when (and
  how) you may access your data; but nobody's threatening your freedom: we
  still allow you to remove your data and not access it at all.



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#487565: grub-pc: Chainloading fails even without LVM

2008-08-01 Thread Kai Wasserbäch
Followup-For: Bug #487565
Package: grub-pc
Version: 1.96+20080724-2

Hello,
I'm not using an LVM on this machine and still get the error that the file
normal.mod can not be found and in the error message there is an doubleslash
displayed (something along the lines UUID={32Bit-Code}/boot/grub//normal.mod).

I installed GRUB2 yesterday, updating from a GRUB1. I installed it in
chainloader mode as was advised in the Debconf message (per pre-selection).

As I'm not quite sure which kind of additional/further information you may need,
please feel free to ask me for any.

Thank you,
Kai Wasserbäch


-- Package-specific info:

*** BEGIN /proc/mounts
/dev/hdd1 / ext3 rw,data=ordered 0 0
/dev/hdd1 /dev/.static/dev ext3 rw,data=ordered 0 0
/dev/hdd5 /boot ext3 ro,data=ordered 0 0
/dev/hdd2 /home ext3 rw,data=ordered 0 0
/dev/hdd6 /opt ext3 rw,data=ordered 0 0
/dev/hdd7 /tmp ext3 rw,data=ordered 0 0
/dev/hdd8 /usr ext3 rw,data=ordered 0 0
/dev/hdd10 /var ext3 rw,data=ordered 0 0
*** END /proc/mounts

*** BEGIN /boot/grub/device.map
(hd0)   /dev/hdc
(hd1)   /dev/hdd
*** END /boot/grub/device.map

*** BEGIN /boot/grub/grub.cfg
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by /usr/sbin/update-grub using templates
# from /etc/grub.d and settings from /etc/default/grub
#

### BEGIN /etc/grub.d/00_header ###
set default=0
set timeout=5
set root=(hd1,8)
earch --fs-uuid --set aa7505a7-ed6b-49cd-807d-25434a2f28c0
if font /share/grub/ascii.pff ; then
  set gfxmode=640x480
  insmod gfxterm
  insmod vbe
  terminal gfxterm
fi
### END /etc/grub.d/00_header ###

### BEGIN /etc/grub.d/05_debian_theme ###
set menu_color_normal=cyan/blue
set menu_color_highlight=white/blue
### END /etc/grub.d/05_debian_theme ###

### BEGIN /etc/grub.d/10_hurd ###
### END /etc/grub.d/10_hurd ###

### BEGIN /etc/grub.d/10_linux ###
set root=(hd1,5)
search --fs-uuid --set deed8901-3bdc-4912-a2c3-cff34ddeb147
menuentry Debian GNU/Linux, linux 2.6.22.18-cabal {
linux   /vmlinuz-2.6.22.18-cabal root=/dev/hdd1 ro
initrd  /initrd.img-2.6.22.18-cabal
}
menuentry Debian GNU/Linux, linux 2.6.22.18-cabal (single-user mode) {
linux   /vmlinuz-2.6.22.18-cabal root=/dev/hdd1 ro single
initrd  /initrd.img-2.6.22.18-cabal
}
### 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 is an example on how to add custom entries
### END /etc/grub.d/40_custom ###
*** END /boot/grub/grub.cfg

-- System Information:
Debian Release: lenny
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 2.6.22.18-cabal
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) (ignored: LC_ALL
set to de_DE.UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages grub-pc depends on:
ii  debconf [debconf-2.0]1.5.22  Debian configuration management sy
ii  grub-common  1.96+20080724-2 GRand Unified Bootloader, version
ii  libc62.7-10  GNU C Library: Shared libraries
ii  liblzo2-22.03-1  data compression library
ii  libncurses5  5.6+20080713-1  shared libraries for terminal hand

grub-pc recommends no packages.

Versions of packages grub-pc suggests:
pn  desktop-base  none (no description available)
pn  os-prober none (no description available)

-- debconf information:
* grub-pc/linux_cmdline:
* grub-pc/chainload_from_menu.lst: true



-- 

Kai Wasserbäch (Kai Wasserbaech)

E-Mail: [EMAIL PROTECTED]
Jabber (debianforum.de): Drizzt
URL: http://wiki.debianforum.de/Drizzt_Do%27Urden
GnuPG: 0xE1DE59D2  0600 96CE F3C8 E733 E5B6 1587 A309 D76C E1DE 59D2
(http://pgpkeys.pca.dfn.de/pks/lookup?search=0xE1DE59D2fingerprint=onhash=onop=vindex)



signature.asc
Description: OpenPGP digital signature