64-bit grub

[gseaman]

I've been getting strange errors when I make changes to my boot setup in pcc. This is on my 64-bit install. Here's the error.

Code: [Select]

Installation of bootloader failed. The following error occurred:
:/boot/grub/install.sh: line 1:/sbin/grub: cannot execute binary file
When I google this error, it is usually associated with trying to run a 32-bit app in a 64-bit environment or vice-versa. So, I enter this code

file `which grub`

and to my surprise grub is 32-bit! The command gave this message.

[galen@localhost ~]$ file `which grub`
/sbin/grub: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.9, stripped

It is possible that I've messed something up, but this is a very recent install and I haven't built or re-installed grub before. I tested some other programs to see if the file command was working and they were all 64-bit programs. I re-installed grub, no change. I've tried to build grub, but there are multiple errors. Any clues?

Galen

[pinoc]

is it possible to re-package/re-compile grub on 64bit?

[gseaman]

is it possible to re-package/re-compile grub on 64bit?

I tried and it won't build. Surprisingly, the spec from mandriva's cooker did build, but I still get the same result. Unless I am missing something, it seems as if the specs are cross-compiling grub. I didn't read the spec yet, to see if there was something like that going on, but probably when I get this figured out, I'm going to be very embarrassed for bringing it up. Did you try the file command on /boot/grub on a 64-bit install?

Galen

[pinoc]

Did you try the file command on /boot/grub on a 64-bit install?

yes, it is a 32bit binary 

[gseaman]

Did you try the file command on /boot/grub on a 64-bit install?

yes, it is a 32bit binary 

"Curiouser and curiouser!"

Galen

[kjpetrie]

Thanks for introducing me to the file command. This has helped me identify a broken package in the 64-bit repo as a 32-bit binary dynamically linked to 32-bit dependencies masquerading as a noarch rpm.

32-bit grub runs here on my 64-bit system.

[JohnW_57]

Comes here Grub2 in picture ?

JohnW

[kjpetrie]

Paste /boot/grub/install.sh here, in case there's something really weird in there.

Also what do you get if you open a terminal and type "grub"? (Type quit to exit if you get a grub prompt.)

[gseaman]

Paste /boot/grub/install.sh here, in case there's something really weird in there.

Also what do you get if you open a terminal and type "grub"? (Type quit to exit if you get a grub prompt.)

Code: [Select]

[galen@localhost ~]$ cat /boot/grub/install.sh
grub --device-map=/boot/grub/device.map --batch <<EOF
root (hd0,4)
setup --stage2=/boot/grub/stage2 (hd0)
quit
EOF
[galen@localhost ~]$
I got a grub prompt. 

Galen

[Old-Polack]

Paste /boot/grub/install.sh here, in case there's something really weird in there.

Also what do you get if you open a terminal and type "grub"? (Type quit to exit if you get a grub prompt.)

Code: [Select]

[galen@localhost ~]$ cat /boot/grub/install.sh
grub --device-map=/boot/grub/device.map --batch <<EOF
root (hd0,4)
setup --stage2=/boot/grub/stage2 (hd0)
quit
EOF
[galen@localhost ~]$
I got a grub prompt. 

Galen

Which indicates that grub itself is working as it should, so the problem is elsewhere.

Just as an exercise in logic, grub has to work on both 32 and 64 bit systems. A 32 bit application will run on a 64 bit system, but a 64 bit application won't run on a 32 bit system, therefore it makes perfect sense that grub should be compiled only as a 32 bit application.

[wedgetail]

gseaman
Just for my own education, what is in your device.map? 

[gseaman]

[galen@localhost ~]$ cat /boot/grub/device.map
(hd0) /dev/sda
[galen@localhost ~]$

[wedgetail]

When I saw your  topic I was and still am checking out a livecd KDE 2012.12
I run a desktop system at the moment and my device.map

(fd0) /dev/fd0
(hd0) /dev/sda

I seem to recall that fd0 = floppy disk drive but I am not sure. I have no floppy installed, but then again I have at least 3 hard drives, so I am not sure of the importance of device.map.

Could it be that above is expected?  Now I am getting a bit curious and will see if I can find my 64 bit livecd