Grub install f up

widget · 12-14-2011, 11:46 PM

Quote:

Originally Posted by shravankumar

What is LDAP?
Which directory we are accessing through LDAP?
Why the LDAP used

Try opening a thread of your very own on this subject. I am sure it will be appreciated here and also get the kind of attention that it needs.

sdfi · 12-15-2011, 02:35 PM

OK.. big progress.

The following (for the benefit of those from google in the future) WORKS;

Code:

First, copy the /boot/grub/i386-pc folder contents from the floppy, to /i386 on /dev/sda5

insmod part_msdos
insmod ext2
set prefix=(hd0,msdos5)/i386

NOW, 'insmod linux' or 'insmod configfile' work sucessfully
[edit: 'insmod ata' is not needed, and 'set root=...' is not essential]

I can boot debian as described in post #76.
If i do 'configfile /boot/grub/grub.cfg' (@ sda5), then the grub boot menu comes up, with debian and my various voyage kernels. NOT like here with options like 'detect any OS'. Do we need the grub.cfg from the floppy??

EDIT: by not using 'insmod ata' I can now load the floppy's boot.cfg, and get the menu shown.

NOW WHAT?

[note: this site needs --strikethrough--]

hurry_hui · 12-15-2011, 07:50 PM

If you can boot debian just redownload and reinstall grub2 from within debian.

(If you want to use/try the menu like shown in supergrubdisk.org you need to copy everything in floppy to /dev/sda5 and pay attention to folder hierarchy.)

'set root=' is not needed if you have set it in 'set prefix='. If 'root=' is different from 'prefix=', then you need to set it.

'insmod ata' is needed to bypass BIOS (like when you are in floppy or CD).

colorpurple21859 · 12-15-2011, 09:54 PM

@ hurry_hui This thread has really been informative and you know grub2 really well, I have learned a few things while following this thread, however how can the op install grub2 to the mbr if they still have this problem:

Quote:

grub-setup: warn: This msdos-style partition label has no post-MBR gap; embedding won't be possible!

Did I miss something? Just wondering.

I came across a problem with grub legacy a few years ago where sometimes it would not boot if the partition it was installed from is not flagged bootable. I have been wondering if when debian installed, if it moved the boot flag from the voyage partition to the debian partition and maybe that is why the reinstall of grub legacy didn't work. just a thought

hurry_hui · 12-16-2011, 06:27 PM

There are other problems, IIRC from RESULTS-1.txt apart from

('grub-setup: warn: This msdos-style partition label has no post-MBR gap; embedding won't be possible!'):

1. Grub2 cannot find its files. (It seems because grub2 cannot run with --force during debian setup.)

2. Grub1 does not have its file (or cannot detect its files--stage1, stage2, menu.lst).

3. Bootable flag which may be needed.

Solution to the above problems:

(1 & 2). (Although some attempts have been made within chrooted environment) Reinstall grub2 with --recheck, if failed, try again with --force. To see if it is installed properly recheck with boot_info_script.sh.

Run (instead of 'update-grub')

Code:

grub-mkconfig -o file_name

to check whether it can pick both voyage and debian kernels. If successful, run 'update-grub' or

Code:

grub-mkconfig -o /boot/grub/grub.cfg

If failed, try no.(3).

(Btw, there are some discussions on internet on making custom (smaller?) core.img by grub-mkimage -o name_of_grub_image -0 [some_options].)

(3). Copy files (from voyage cd or another distro) needed by grub1, to its folder /boot/grub/.

Boot to voyage, reinstall grub1 by running grub. on grub prompt (grub>) type this:

Code:

find /boot/grub/stage1

If grub generates (hd0,0) continue with

Code:

root (hd0,0)
setup (hd0)
quit

To see if it is installed properly recheck with boot_info_script.sh.

(4). Set the boot flag.

Last attempt is to boot from supergrub2 disk.

HTH

sdfi · 12-17-2011, 11:32 AM

It detected both distros, but 1&2 failed.

I haven't run the script yet but 3 did not give me normal booting.

4- how?

sdfi · 12-17-2011, 12:22 PM

OK, i'm pretty sure no one has any idea how to fix this. I'm throwing in the towel now and formatting.

And none of that had anything to do with supergrub2disk, so wasting all that time on that was pretty shitty.

colorpurple21859 · 12-17-2011, 04:41 PM

if you haven't formatted your hard drive yet, you still might be able to get grub legacy to work. First go to voyage /boot/grub folder and make it sure it has a stage1 and stage2 file, a menu.lst, a devicemap file, and about seven more stage files with different names. If they are missing the files can be copied from the /usr/lib/grub/x386 folder.
With a partition manager, such as gparted, parted, cfdisk or any one that you can use flag the voyage partition bootable. To install grub legacy manually, boot into voyage and issue the following commands

Quote:

grub
root (hd0,0)
setup (hd0)
quit

as suggested in post 58