Grub common error 2

Grub common error 2-Linux general technology-Linux technology and application information. For details, refer to the following section. Solution (Case 2 ):

First, check that the configuration of the root and setup lines of grub. conf is correct. If you confirm that the method you are using is correct, the Grub version you are using may have a bug (for example, 0.93.20031222 ), use the released software tool to install or upgrade the Grub you used ).

Gentoo users can use the following command:

(Execute this command in the chroot environment)

# Echo "= sys-boot/grub-0.93.20031222">/etc/portage/package. mask

# Emerge grub-p

Then you can use the Grub-install script recommended by grub developers to install Grub in MBR:

(-- Root-directory is required when you use a separate/boot partition)

# Grub-install -- root-directory =/boot/dev/hda

If you have tried the above methods but still cannot solve the problem, please check your/boot partition. It may be that your/boot partition has a problem:

(Confirm that the fsck partition you are going to perform is in the unmount state, And/dev/hda1 is used in the example given .)

# Fsck-y/dev/hda1

4. Grub error 16

Symptoms:

Error 16: Inconsistent filesystem structure

Converting to Chinese means an incompatible file system, that is, your/boot cannot be recognized by Grub (it may be a file system that cannot be identified by Grub but can be recognized by linux ), if your/boot is not a separate partition, it indicates that your root partition is/and cannot be recognized by Grub.

Solution:

Use the rescue disk, livecd, or the second linux system that can be used. Do not mount the/or/boot of the original system after the disk is started, you can use fdisk to check the file system and then use fsck-y.

5. Grub Error 17

Symptoms:

Root (hd0, 0)

Filesystem type unknown partition type 0x7

Error 17: Cannot mount selected partition

Solution:

It means that the partition cannot be mounted, that is, Grub can confirm that the used partition exists, but the file system used on the partition cannot be recognized by Grub.

Check whether the root (x, y) settings in grub. conf are correct.

If the above error occurs when you choose to start Windows, check grub. whether the configuration of conf in Windows contains root (hdX, Y) (or rootnoverify (hdX, Y) and chainloader (hdX, Y) + 1.

6. Grub error 18

Kernel (hd1, 4)/bzImage root =/dev/hdb7

Error 18: Selected cylinder exceeds max supported by BIOS

Solution:

This error often occurs when the old hardware and the new hard disk are connected, when you try to access an address that cannot be converted from the BIOS (in other words, the address that Grub tries to read has exceeded the accessible limit of the BIOS ). Try to upgrade the BIOS or move the/boot partition to the front of the available hard disk space. It is estimated that no one is still using a hard disk of less than 8 GB.

7. GRUB...

Symptoms:

GRUB

GRUB

...

Solution:

One possibility is that you have set the AUTO check HDD in the BIOS. You can try to change the BIOS entry to User Type HDD.

Another possibility is that Grub has been installed in MBR, but Grub has been re-installed to modify the partition or increase the hard disk, but some errors have been made during re-installation. In this case, re-installing Grub is easier to solve than finding out where an error has been made.

8. Probing Devices to Guess BIOS Drives. This May Take a Long Time.

Symptoms:

When Grub is installed, the system hangs after the following text is displayed:

# Grub

Probing devices to guess BIOS drives. This may take a long time.

Solution:

Check the hardware configuration. You may connect both the Ultra DMA device and the device that does not support Ultra DMA on the same IDE connection line.

9. The system hangs when Grub is installed.

Symptoms:

After the grub command is run, the system hangs when no other display is displayed on the screen.

# Grub (the system is suspended at this time)

Solution:

The grub command checks floopy first. If no floopy is available, use the following additional parameters to skip the floopy check.

# Grub -- no-floppy

10. Uncompressing Linux... OK, booting the kernel.

Symptoms:

The system suspends after the following content is displayed.

Uncompressing Linux... OK, booting the kernel.

Solution:

To be exact, this error is not a Grub error. The possible cause is that ACPI is used in the kernel or compiled kernel, but ACPI is not working properly. You can disable the ACPI In the BIOS or add the no acpi parameter when starting the kernel.

11. Grub only displays one Grub prompt

Symptoms:

Each boot entry that should have appeared during computer boot is replaced by a Grub prompt.

Solution:

Start and mount the/boot partition with the livecd or rescue disk, and check whether grub. conf is lost.

# Mount/dev/hda1/mnt/someplace/boot

# Cat/mnt/someplace/boot/grub. conf

In addition, check whether the symbolic connection of menu. lst exists.

# Ls-l/mnt/gentoo/boot/grub/menu. lst

Lrwxrwxrwx 1 root 9 Mar 7/mnt/gentoo/boot/grub/menu. lst-> grub. conf

If the symbolic connection is not found, create it.

# Cd/mnt/gentoo/boot/grub

# Ln-snf grub. conf menu. lst

Then reinstall Grub.

(Run the following command in the chroot environment)

# Grub-install -- root-directory =/boot/dev/hda