This error is returned if the device part of a device- or full filename refers to a diskor BIOS device that is not present or not recognized by the BIOS in the system.•
"Disk read error"
This error is returned if there is a disk read error when trying to probe or read datafrom a particular disk.•
"Disk write error"
This error is returned if there is a disk write error when trying to write to aparticular disk. This would generally only occur during an install of set activepartition command.•
"Disk geometry error"
This error is returned when a read is attempted at a linear block address beyond theend of the BIOS translated area. This generally happens if your disk is larger thanthe BIOS can handle (512MB for (E)IDE disks on older machines or larger than 8GBin general).•
"Attempt to access block outside partition"
This error is returned if a linear block address is outside of the disk partition. Thisgenerally happens because of a corrupt filesystem on the disk or a bug in the codehandling it in GRUB (it's a great debugging tool).•
"Partition table invalid or corrupt"
This error is returned if the sanity checks on the integrity of the partition table fail.This is a bad sign.•
"No such partition"
This error is returned if a partition is requested in the device part of a device- or fullfilename which isn't on the selected disk.•
"Bad filename (must be absolute pathname or blocklist)"
This error is returned if a filename is requested which doesn't fit the syntax/ruleslisted in theFilesystem Description.•
"Bad file or directory type"
This error is returned if a file requested is not a regular file, but something like asymbolic link, directory, or FIFO.•
"File not found"
This error is returned if the specified filename cannot be found, but everything else(like the disk/partition info) is OK.•
"Cannot mount selected partition"
This error is returned if the partition requested exists, but the filesystem typecannot be recognized by GRUB.•
"Inconsistent filesystem structure"
This error is returned by the filesystem code to denote an internal error caused bythe sanity checks of the filesystem structure on disk not matching what it expects.This is usually caused by a corrupt filesystem or bugs in the code handling it inGRUB.•
"Filesystem compatibility error, can\'t read whole file"
Some of the filesystem reading code in GRUB has limits on the length of the files itcan read. This error is returned when the user runs into such a limit.•
"Error while parsing number"
This error is returned if GRUB was expecting to read a numbur and encountered baddata.•
"Device string unrecognizable"
This error is returned if a device string was expected, and the string encountereddidn't fit the syntax/rules listed in theFilesystem Description.•
"Invalid device requested"
This error is returned if a device string is recognizable but does not fall under theother device errors.•
"Invalid or unsupported executable format"