How to solve boot problems with Grub in linux

[mewlyo]

Just about anyone how to solve the grub problem in the Ubuntu 9.0. When I tried dual booting or an additional unusual boot setup has, at some end, made their system unbootable. I found out “GRUB Error 2″ or “No suitable System Disk Found” it makes me shatter into a cold sweat, and then fear no more. I also tried the SGD to work with Linux or Windows systems to go about or fix the broken boot loaders that have reserved many of us aware at night, and all in fewer than 2MB.

[Dolsy_bendal]

To need to download the updated grubs form the websites. Download these onto your computer (or any computer for that subject) and perform the rawrite program to copy the grub.img file onto a pre-formatted live CD (remind that, once this has been completed, you will not be able to read that CD contain during booting. This is how it should be).

Now, boot your PC with the CD You will get a text based screen looking something like this :-


GRUB edition 0.92 (640K lower / 3072K upper memory)

[ Minimal BASH-like line editing is supporting. For the first word, TAB
lists probable command completions. Wherever besides TAB lists the probable
Completions of a device/filename.]

grub>

Now we require finding out wherever your Grub files live. Do this by incoming the "find /boot/grub/stage1" command.

grub> find /boot/grub/stage1
(hd1,1)

[Aleksandra]

If you’re secure go back into Linux, you'll desire to get Grub back onto your hard disk's MBR so you will require to reinstall the Grub properly. This is just done by logging a terminal window as root (or as your usual user and incoming 'su -' to become the root/super user) and enter the "grub-install " command. This control takes a single constraint, which is the forename of the hard disk that you desire Grub to be installed on. currently that we are in Linux, the tough disk naming meeting is no longer the (hd0,1) arrangement that we used in grub, but the one that Linux uses. This begin with /dev/ and is go behind by 'hd' and then a dispatch from 'a' to 'd'.

[SalVatore]

You will require to normally boot from your first (and possibly only) hard disk, you will use "/dev/hda". If you usually boot off your following hard disk you will exercise either "/dev/hdb" or "/dev/hdc" or /dev/hdd" depending ahead which IDE wire it is plug into and whether it is the master or slave on that wire (a and b are master as well as slave on IDE1, though c and d are master and slave on IDE2).

[root@localhost nerderello]# /sbin/grub-install /dev/hda
Installation completed. No mistake reported.
This is the stuffing of the device map /boot/grub1/device.map.
Check if this is right or not. If any of the lines is incorrect,
attach it and re-run the script `grub-install'.

# this device map was produce by anaconda
(fd0)     /dev/fd0
(hd0)     /dev/hda
(hd1)     /dev/hdc

[Candace]

First you will require to discover out where the kernel isd currently present(find command again), then we need to locate through "root" to its correct device, then most of us require to tell Grub which kernel to craft exercise of and then (optionally) which initrd to use (note. the statement "root" here is used to mean the initial point, somewhat than anything to do with the root user). The make convinced your root will be on the similar hard disk as well as partition that you require originate the Grub file /boot/grub/stage1 on. So, in the examples we have been liability so far, the "root" (i.e. the hard drive that has the "/boot/" index on it) would be on (hd1,1). To set this we go through the root command :-

grub> root (hd1,1)
 Filesystem type is ext1fs, division type 0x83