Grub problem - Lilo to the rescue!

[gseaman]

I have a brand new install of 64-bit test 5 with kde and lxde desktops installed. I added a new kernel and edited grub in pcc and now grub won't install. There are two partitions on this machine, but this one was the last to update the mbr. So, I am stuck with boot from a liveusb. But, I noticed PCC had to option to boot with lilo, and it actually still works. (Don't try it unless you visual reminders of the early '90's. )

Whether I edit it in pcc or with a text editor it grub complains that it can't execute a binary file on line 1. I googled and can't figure out what it is complaining about. Any ideas?

Galen

[gseaman]

That was fast. Some times you really do get lucky.

The first line of /boot/grub/install.sh ends with <<EOF, and it needed to be quoted as <<"EOF". I don't know exactly how I knew to try this, must have been a faint memory of one of Old-Polack's old posts. Anyway, it worked without a hitch. Let's hope that it stays fine. By the way, I did not edit install.sh before, so it appears to be a bug that hasn't surfaced until now. 

Galen

[Just17]

Maybe you should post the contents of install.sh

I suspect there is some other corruption in the file as I have never heard of quoting that EOF previously.

[gseaman]

Here is /boot/grub/install.sh

Code: [Select]

grub --device-map=/boot/grub/device.map --batch <<EOF
root (hd0,5)
setup --stage2=/boot/grub/stage2 (hd0)
quit
EOF

Code: [Select]

timeout 10
color black/cyan yellow/cyan
gfxmenu (hd0,5)/boot/gfxmenu
default 0

title linux
kernel (hd0,5)/boot/vmlinuz BOOT_IMAGE=linux root=UUID=6ec0b308-6734-4f24-83be-9ff1bd1201b8 quiet vmalloc=256M acpi=on resume=/dev/sda6 splash=silent init=/sbin/e4rat-preload vga=791
initrd (hd0,5)/boot/initrd.img

title linux-nonfb
kernel (hd0,5)/boot/vmlinuz BOOT_IMAGE=linux-nonfb root=UUID=6ec0b308-6734-4f24-83be-9ff1bd1201b8 quiet vmalloc=256M acpi=on resume=UUID=9966d5dd-5b86-4dc8-a71e-6bfa8e40c702
initrd (hd0,5)/boot/initrd.img

title 3.2.18-pclos2.bfs
kernel (hd0,5)/boot/vmlinuz-3.2.18-pclos2.bfs BOOT_IMAGE=3.2.18-pclos2.bfs root=UUID=6ec0b308-6734-4f24-83be-9ff1bd1201b8 quiet vmalloc=256M acpi=on resume=UUID=9966d5dd-5b86-4dc8-a71e-6bfa8e40c702 splash=silent init=/usr/sbin/e4rat-preload vga=791
initrd (hd0,5)/boot/initrd-3.2.18-pclos2.bfs.img

title failsafe
kernel (hd0,5)/boot/vmlinuz BOOT_IMAGE=failsafe root=UUID=6ec0b308-6734-4f24-83be-9ff1bd1201b8 quiet failsafe vmalloc=256M acpi=on
initrd (hd0,5)/boot/initrd.img

title PCLinuxOS 32 (/dev/sda1)
root (hd0,0)
configfile /boot/grub/menu.lst
I added "init=/usr/sbin/e4rat-preload" to the first boot option. This has worked without fault before. But to trouble shoot, I remove the line and it still caused an error. Eventually I move /boot/grub to /boot/grub2 and reinstalled grub. Still didn't work. I added the quotes and it worked and e4rat-preload also ran. But, somehow, the quotes are not there anymore, but booting works. Strange

Galen

[gseaman]

grub must have recreated device.map and install.sh. I try to be very careful so that I can re-trace my steps to reproduce a problem and a fix, but I am confused by this one. I am assuming PCC calls grub-install and grub-install calls install.sh which opens device map. But what would overwrite my edit to install.sh? This is solved, but I hope to understand this better.

Galen

[Just17]

grub must have recreated device.map and install.sh. I try to be very careful so that I can re-trace my steps to reproduce a problem and a fix, but I am confused by this one. I am assuming PCC calls grub-install and grub-install calls install.sh which opens device map. But what would overwrite my edit to install.sh? This is solved, but I hope to understand this better.

Galen

I don't know what writes this file.