[SOLVED] Debian 8.1 Fresh Install Grub Rescue

Ztcoracat · 07-05-2015, 12:00 AM

After a fresh install I'm stuck at the grub rescue> prompt.

Code:

error file '/boot/grub/i386-pc/normal.mod' not found
Entering rescue mode
grub rescue>

I didn't want Grub installed to the MBR of my first 500 GB HDD /dev/sda/ which is Slackware. Instead I told the installer to install Grub to my second 1 TB HDD which is /dev/sdb/.

I tried grub-install with the Live Debian DVD it only returns the grub rescue prompt again.

I tried ls and it shows me:

Code:

(hdo) (hdo,msdos2) (hdo,msdos1) (hd1) (hd1,msdos2) (hd1,msdos1)

I shouldn't assume but I think hd1,msdos2 is the 1TB drive?

I tried:

Code:

set prefix="(hd1,msdos2)/boot/grub"

That only returned me to the grub rescue prompt again.

I booted into Slackware to run fdisk -l and check on the partions's that I created for Debian. They are there and ok.

How do I fix this?

Ztcoracat · 07-05-2015, 12:39 AM

I tried Rescue Mode with the Live Debian DVD.

I tried:

Code:

grub install /dev/sdb1

Evidently I can't install Grub to the 1TB HDD / partition.

Code:

Warning File system 'ext2' doesn't support embedding

Warning Embedding is not possible. Grub can only be installed in this setup by using blocklist's.

However blocklists are unreliable and their use is discouraged

If I install Grub to the MBR which is Slackware's bootloader LILo isn't that going to create a mess?

descendant_command · 07-05-2015, 12:48 AM

If you're already using lilo why install grub?
Just adjust your existing lilo conf to boot Debian as well.

Ztcoracat · 07-05-2015, 12:51 AM

Quote:

Originally Posted by descendant_command

If you're already using lilo why install grub?
Just adjust your existing lilo conf to boot Debian as well.

Do you mean make a menu entry in the lilo.config file?

If so, I have forgotten how:-

descendant_command · 07-05-2015, 12:54 AM

Well, yes - you only need one bootloader.
As to how ... can't help sorry, I've never used lilo, but i'm sure it's documented somewhere.

Ztcoracat · 07-05-2015, 01:00 AM

Quote:

Originally Posted by descendant_command

Well, yes - you only need one bootloader.
As to how ... can't help sorry, I've never used lilo, but i'm sure it's documented somewhere.

I did it once before and forgot-jeeeeez:-

I think it's something like:
other=/dev/sdb
lablel=debian

but I'm not chances it I could be wrong.
I'll look online and see if I can find how to make a Menu Entry in Lilo-

astrogeek · 07-05-2015, 01:01 AM

Quote:

Originally Posted by Ztcoracat

Do you mean make a menu entry in the lilo.config file?

If so, I have forgotten how:-

What you need to do is chain load from Lilo.

First, since you have grub installed under Debian, just have it install to the root partition of the Debian install - /dev/sdb1 if I read your post correctly.

Then, boot to Slackware, and add this to the lilo.conf:

Code:

other = /dev/sdb1
label = Debian_1TB

...then run lilo.

"Assuming" (dangerous word) the device paths are correct and the same under both Slackware and Debian, that should do it. When you boot to the MBR of the first disk, you will have an option to go to the Debian partition of the second disk, from which grub will take over and boot Debian.

You can improve on this by replacing all /dev/sdx paths with UUIDs of the actual devices, then it won't matter if drive order changes (much - you may need to reset boot device in the BIOS).

*** Ah! We cross posted...

If grub installed to the MBR of the second drive then it will be other=/dev/sdb as you said. But it hurts nothing to add "other" stanzas for both then keep the one that works.

Note also that there is no guarantee that drive order as represented by /dev/sdx will be the same under different distros - although it usually is. If you get a boot failure post the message here.

Ztcoracat · 07-05-2015, 01:06 AM

Quote:

Originally Posted by astrogeek

What you need to do is chain load from Lilo.

First, since you have grub installed under Debian, just have it install to the root partition of the Debian install - /dev/sdb1 if I read your post correctly.

Then, boot to Slackware, and add this to the lilo.conf:

Code:

other = /dev/sdb1
label = Debian_1TB

...then run lilo.

"Assuming" (dangerous word) the device paths are correct and the same under both Slackware and Debian, that should do it. When you boot to the MBR of the first disk, you will have an option to go to the Debian partition of the second disk, from which grub will take over and boot Debian.

You can improve on this by replacing all /dev/sdx paths with UUIDs of the actual devices, then it won't matter if drive order changes (much - you may need to reset boot device in the BIOS).

I don't have grub installed.
I tried to install it 3 times in rescue mode and it failed during the Debian install as well.

I'll make the menu entry you typed for me in the lilo.conf file.
Thank you, astrogeek I forgot how.

bb to let you know how it went.

astrogeek · 07-05-2015, 01:23 AM

Quote:

Originally Posted by Ztcoracat

I don't have grub installed.
I tried to install it 3 times in rescue mode and it failed during the Debian install as well.

I'll make the menu entry you typed for me in the lilo.conf file.
Thank you, astrogeek I forgot how.

bb to let you know how it went.

OK, it did not sink in that grub failed to install... duh...

I do not use grub at all so cannot help you with that part of it, and grub needs to be there for chain loading to work...

But let me anticipate you a little and see if we can't mount the Debian partitions under Slackware and create a full bootable lilo stanza for Debian.

Now, I also do not run Debian so I don't know if it uses an initrd, but lets assume not in these days of 64 bit monster kernels... so a starting point would be like this...

First mount the debian root partition under Slackware...

Code:

mkdir /mnt/deb
mount /dev/sdb1 /mnt/deb
ls /mnt/deb just to be sure it is what you expect...

Then add to lilo.conf

Code:

image = /mnt/deb/boot/vmlinuz !! This is the lilo-runtime-mounted path !!
root = /dev/sdb1 !! This is the boot-runtime device path !!
label = Debian

Then run lilo and see if it gives any warnings - if not see if it will boot!

Ztcoracat · 07-05-2015, 01:24 AM

Editing the lilo.conf file was a success.

F11 while the machine boots gives me a GNU Menu to choose between Slackware and Debian.

UUID's should already be assigned to the 500 GB HDD and the 1 TB HDD, right?

Ztcoracat · 07-05-2015, 01:32 AM

descendant_command & astrogeek Thank you both for your help.-

Debian 8 is really nice! ! !

I have to install the firmware-realtek_0.43_all.deb to get the wifi working.
I tried setting up the wifi/dhcp during the fresh installation but it was unsuccessful.

Debain will keep me busy at least for the next hour or so:-

Ztcoracat · 07-05-2015, 01:36 AM

Quote:

Originally Posted by astrogeek

OK, it did not sink in that grub failed to install... duh...

I do not use grub at all so cannot help you with that part of it, and grub needs to be there for chain loading to work...

But let me anticipate you a little and see if we can't mount the Debian partitions under Slackware and create a full bootable lilo stanza for Debian.

Now, I also do not run Debian so I don't know if it uses an initrd, but lets assume not in these days of 64 bit monster kernels... so a starting point would be like this...

First mount the debian root partition under Slackware...

Code:

mkdir /mnt/deb
mount /dev/sdb1 /mnt/deb
ls /mnt/deb just to be sure it is what you expect...

Then add to lilo.conf

Code:

image = /mnt/deb/boot/vmlinuz !! This is the lilo-runtime-mounted path !!
root = /dev/sdb1 !! This is the boot-runtime device path !!
label = Debian

Then run lilo and see if it gives any warnings - if not see if it will boot!

I know Slackware very well so I'll give your proposal a go.
It's late so I'll let you know tomorrow, THANKS-

astrogeek · 07-05-2015, 01:37 AM

Quote:

Originally Posted by Ztcoracat

Editing the lilo.conf file was a success.

F11 while the machine boots gives me a GNU Menu to choose between Slackware and Debian.

UUID's should already be assigned to the 500 GB HDD and the 1 TB HDD, right?

Ah great! Did you actually boot to the Debian drive - just to be sure?

Yes, the UUIDs are generated by the filesystem creation process. You can find them under /dev/disk/by-uuid/...

Code:

ls -l /dev/disk/by-uuid/

The syntax is a little different for each use, as follows...

Code:

First, the image path must be mounted and accessible when you run lilo, for example:
image = /boot/vmlinuz
image = /mnt/deb/boot/vmlinuz

The boot device must be accessible via device path...

boot = /dev/disk/by-id/SOME-UNIQUE-ID-SYMLINK-TO-DISK for MBR installation...
boot = /dev/disk/by-uuid/SOME-UNIQUE-UUID-SYMLINK-TO-PARTITION for boot partition installation...

The root partition should be referenced by quoted UUID only (i.e., no path)

root = "SOME-UNIQUE-UUID-FOR-ROOT-PARTITION"

Also, to make the drives order independent in multi-drive machines, change the references in /etc/fstab to also use UUIDs for all partitions. Then if your drives are reordered it will still boot!

descendant_command · 07-05-2015, 02:30 AM

Just as a final step, if you really are booting Debian via lilo and NOT chainloading grub, then make sure the grub packages are removed from Debian, otherwise future kernel upgrades will try to reinstall grub and possibly bork your current setup.

edit: actually, no it won't - it will rewrite the grub config but not reinstall the actual bootloader...

Ztcoracat · 07-05-2015, 02:37 PM

Quote:

Originally Posted by descendant_command

Just as a final step, if you really are booting Debian via lilo and NOT chainloading grub, then make sure the grub packages are removed from Debian, otherwise future kernel upgrades will try to reinstall grub and possibly bork your current setup.

edit: actually, no it won't - it will rewrite the grub config but not reinstall the actual bootloader...

To clarify booting into Debian......
When I boot up this desktop w/o tapping F11 it boot's directly into Slackware.
F11 takes me to a GNU Menu that boots me directly as a first choice into Debian with the choice of arrowing down to choose Slack from there. All attempts at installing Grub during the install failed. Several attempts to install Grub using the Debian DVD in Rescue Mode failed as well.

How can I be certain that LILO isn't chainloading grub?

-:-...-:-...-:-

astrogeek-

Quote:

Also, to make the drives order independent in multi-drive machines, change the references in /etc/fstab to also use UUIDs for all partitions. Then if your drives are reordered it will still boot!

I'm not familiar with changing the references in the /etc/fstab file but I'd like to change this to avoid misboots in the future. I'll pull the /etc/fstab file up in the terminal to view it to get what your saying:-

I have what looks to me as 4 uuid's-
By id I can tell the 1TB HDD from the 500 GB HDD but by looking at the uuid's by uuid; all 4 signatures are different and can not tell the difference.