Shulou(Shulou.com)06/01 Report--

This article mainly introduces "how to solve LINUX system grub errors". In daily operation, I believe many people have doubts about how to solve LINUX system grub errors. The editor consulted all kinds of materials and sorted out simple and easy-to-use operation methods. I hope it will be helpful for you to answer the doubts of "how to solve LINUX system grub errors"! Next, please follow the editor to study!

1: Filename must be either an absolute filename or blocklist

Explanation: error 1 indicates that the file name is in the wrong format. In GRUB, either the file is given in an absolute path

Example:

Grub > kernel vmlinuz root=label=/

Error 1: Filename must be either an absolute pathname or blocklist

Grub >

Reference:

2: Bad file or directory type

Explanation: error 2 indicates that the command expects a normal file, but the object of the corresponding file name is a symbolic link, directory, FIFO

Example:

Grub > kernel / testdir root=LABEL=/

Error 2: Bad file or directory type

Grub >

Reference:

3: Bad or corrupt data while decompressing file

Explanation: error 3 indicates that an error occurred while decompressing the file. Maybe it's because the file was corrupted.

Reference:

4: Bad or incompatible header in compressed file

Explanation: error 4 indicates that the header format of the compressed file is not compatible or incorrect

Reference:

5: Partition table invalid or corrupt

Explanation: error 5 indicates that the partition table is invalid or corrupted. This is a bad omen.

Reference:

6: Mismatched or corrupt version of stage1/stage2

Explanation: error 6 indicates that the install order found that the promulgation numbers of stage1 and stage2 are not compatible.

Reference:

7: Loading below 1MB is not supported

Explanation: This error is returned if the lowest address in a kernel is below

The 1MB boundary. The Linux zImage format is a special case and

Can be handled since it has a fixed loading address and maximum size

Reference:

8: Kernel must be loaded before booting

Explanation: error 8 indicates that the boot command was not executed before the kernel command was executed.

Reference:

9: Unknown boot failure

Explanation: error 9 indicates an unknown boot error

Reference:

10: Unsupported Multiboot features requested

Explanation: error 10 indicates that the function required by the request Multiboot header is not supported by GRUB.

Reference:

11: Unrecognized device string

Explanation: error 11 indicates an unrecognized device string.

Example:

Grub > root hd0

Error 11: Unrecognized device string

Grub >

Reference:

12: Invalid device requested

Explanation: error 12 indicates that the requested device is invalid

Example:

Grub > root (hd2)

Error 21: Selected disk does not exist

Grub > kernel / grub/grub.conf root=LABEL=/

Error 12: Invalid device requested

Grub >

Reference:

13: Invalid or unsupported executable format

Explanation: error 13 indicates an invalid or unrecognized executable format

Example:

Grub > kernel / grub/grub.conf root=LABEL=/

Error 13: Invalid or unsupported executable format

Grub >

Reference:

14: Filesystem compatibility error, cannot read whole file

Explanation: error 14 indicates a file system compatibility error and cannot read the entire file

Reference:

15: File not found

Explanation: the requested file could not be found

Example:

Grub > find / grub-noexist/grub.conf

Error 15: File not found

Grub >

Reference:

16: Inconsistent filesystem structure

Explanation: error 16 indicates an inconsistent file system structure. Maybe the file system structure has been corrupted.

Reference:

17: Cannot mount selected partition

Explanation: error 17 indicates that the specified partition cannot be mounted. For example, swap partition

Example:

Grub > root (hd0,2) this is a swap partition

Filesystem type unknown, partition type 0x82

Grub > kernel / vmlinuz

Error 17: Cannot mount selected partition

Grub >

Reference:

18: Selected cylinder exceeds maximum supported by BIOS

Explanation: error 18 indicates that the selected cylinder exceeds the maximum capacity supported by BIOS. This usually happens when the LBA mode is not supported

On Donovan's hard drive.

Reference:

19: Linux kernel must be loaded before initrd

Explanation: error 19 indicates that the initrd command must be executed before the kernel command can be executed

Reference:

20: Multiboot kernel must be loaded before modules

Explanation: error 20 indicates that the kernel command must be executed before the module or moduleunzip command is executed

Reference:

21: Selected disk does not exist

Explanation: error 21 indicates that the selected disk does not exist

Example:

Grub > root (hd2)

Error 21: Selected disk does not exist

Grub >

Reference:

22: No such partition

Explanation: error 22 indicates that the partition does not exist

Example:

Grub > root (hd0,10)

Error 22: No such partition

Grub >

Reference:

23: Error while parsing number

Explanation: error 23 indicates an error in the interpretation of the parameter. I hope it is a numerical value, but the parameter is of another type.

Example:

Grub > root (hda,0)

Error 23: Error while parsing number

Grub >

Reference:

24: Attempt to access block outside partition

Explanation: error 24 indicates that the block you are trying to access exceeds the partition

Reference:

25: Disk read error

Explanation: error 25 indicates a disk read error

Reference:

26: Too many symbolic links

Explanation: error 26 indicates too many symbolic links (a maximum of 5 are allowed by default)

Reference:

27: Unrecognized command

Explanation: unrecognized command

Reference:

28: Selected item cannot fit into memory

Explanation: the selected object cannot be loaded into memory.

Example:

[root@monitor boot] # dd if=/dev/zero of=vmlinuz-2.4.20-31.9bs=1024 count=1 seek=1

Read 1-0 blocks

One million blocks are output.

[root@monitor boot] # grub

Grub > kernel / vmlinuz-2.4.20-31.9root=label=/

[Linux-bzImage, setup=0x1400, size=0xfffff200]

Error 28: Selected item cannot fit into memory

Grub >

Reference:

29: Disk write error

Explanation: disk write error

Reference:

30: Invalid argument

Explanation: invalid parameter

Example:

Grub > serial-- noarg=0

Error 30: Invalid argument

Grub >

Reference:

31: File is not sector aligned

Explanation: This error may occur only when you access a ReiserFS partition by

Block-lists (e.g. The command `install'). In this case, you should

Mount the partition with the `- o notail' option.

Reference:

32: Must be authenticated

Explanation: a password is required to continue with the following operations. For example, there are password or lock commands in the configuration file

Example:

Password root1234

Title DOS

Lock

Rootnoverify (hd0,0)

Chainloader + 1

Reference:

33: Serial device not configured

Explanation: error 33 indicates that the serial port has not been configured yet. This usually happens when you perform a terminal serial.

Reference:

34: No spare sectors on the disk

Explanation: there is not enough free disk space. It can happen when you embed stage 1.5 into the space behind MBR. But this part of the space may have been used by the partition table so far, the study on "how to solve the grub error of LINUX system" is over. I hope to be able to solve your doubts. The collocation of theory and practice can better help you learn, go and try it! If you want to continue to learn more related knowledge, please continue to follow the website, the editor will continue to work hard to bring you more practical articles!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.