Well, I got this very nice aspire one 110, the problem is that Linpus quickly becomes boring, I'm half in search of the installation of Mandriva 2009, the worry is that after a impec installation, it gives me an error 2 in the top left in the boot.
Printable View
Well, I got this very nice aspire one 110, the problem is that Linpus quickly becomes boring, I'm half in search of the installation of Mandriva 2009, the worry is that after a impec installation, it gives me an error 2 in the top left in the boot.
Error 2 or 22?
Errors by Stage 1
Errors by Stage 1.5Quote:
Stage 1 handles errors by displaying an error message and stops. Keys <CTRL> - <ALT> - <DEL> restart the machine.
Following is a list of error messages for Stage 1:
Hard Disk Error
stage2 or stage1.5 is about to be read, but determining the size and geometry of the hard drive has failed.
Floppy Error
stage2 or stage1.5 is about to be read from a diskette, but determining the size and geometry of the disk has failed. The error is differentiated because of the previous determination of the sequence is different.
Read Error
A drive error occurred while playing stage2 or stage1.5.
Geom Error
The location of stage2 or stage1.5 is not on a portion of the disk supported directly by the BIOS. This error occurs when the translation mode BIOS geometry was changed by the user or when the disc was changed from machine or controller after installation, or GRUB was not installed by itself (if so, the version of Stage 2 would have been read and the installation failed .
Errors by Stage 2Quote:
Stage 1.5 handles errors by displaying an error code of the form Error num and then stops. Keys <CTRL> - <ALT> - <DEL> restart the machine.
Quote:
Stage 2 cancels the current operation when it encounters an error, displays an error message, and (if possible) continues as if no error occurred, or is awaiting user intervention.
Following is a list of error messages for Stage 2 (error codes for Stage 1.5 are listed before the colon):
1: Filename must be either an absolute filename or Blocklist
This error is returned if a file name does not meet the rules listed in the section see File System.
2: Bad file or directory type
This error is returned if a file is not a regular file, but something like a symbolic link, directory, or FIFO pipe.
3: Bad or corrupt data while decompressing file
This error is returned when the decompression code encounters an internal error. It is usually due to a corrupted file.
4: Bad or incompatible header in compressed file
This error is returned if the header of a compressed file is supposed bad.
5: Partition table invalid or corrupt
This error is returned if the checks of the integrity of the partition table fail. This is a bad sign.
6: Mismatched or corrupt version of stage1/stage2
This error is returned if the install command are incompatible or corrupt versions of stage1 and stage2. GRUB does not generally the corruption of a file, but it is a check on the version numbers, which should be correct.
7: Loading below 1MB is not supported
This error is returned if the lowest address in a kernel is below the limit of one megabyte. The Linux zImage format is a special case and can be administered as a loading address and maximum size fixed.
8: Kernel must be loaded before booting
This error is returned if you ask Grub to execute the boot sequence without having clarified kernel to run.
9: Unknown boot failure
This error is returned if the boot process failed for an unknown reason.
10: Unsupported Multiboot features requested
This error is returned when the kernel uses a feature Multiboot unrecognized. The core probably requires special treatment that GRUB is probably unable to provide.
11: Unrecognized device string
This error is returned if a device string was expected and that the input string does not match the syntax described in File System.
12: Invalid device requested
This error is returned if the channel device is valid but that the error does not correspond to any other device error.
13: Invalid or unsupported executable format
This error is returned if the kernel image to load is not recognized as Multiboot or is not a native formats (Linux zImage or bzImage, FreeBSD, NetBSD).
14: Filesystem compatibility error, can not read whole file
Some codes of reading the file system in GRUB has limits on the size of files they can read. This error is returned when the user exceeds this limit.
15: File not found
This error is returned if the file is not found, but the rest is correct (as the disc information and the score).
16: Inconsistent filesystem structure
This error is returned by the code of the file system to report an internal error caused by the failure of verification of file system structure. This error is usually caused by a corrupted filesystem or bugs in the code of GRUB which supports it.
17: Can not mount selected partition
This error is returned if the partition requested exists, but the type of file system is not recognized by GRUB.
18: Selected cylinder exceeds maximum supported by BIOS
This error is returned when an attempt is made to read a block beyond those managed by BIOS. It usually happens if your disk is larger than the limits of the BIOS (for 512MB disks (E) IDE on old machines, or more generally 8GO).
19: Linux kernel must be loaded before initrd
This error is returned if the initrd command is used before loading a Linux kernel. As the following error, this error has meaning only in this case.
20: Multiboot kernel must be loaded before modules
This error is returned if the command to load a module is used before loading a Multiboot kernel. It did anyway signfication of that in this case, since GRUB does not know how to communicate the location of such modules to a non-Multiboot kernel.
21: Selected disk does not exist
This error is returned if a chain means a disk or BIOS device that is not present or is not recognized by the BIOS.
22: No such partition
This error is returned if the partition requested does not exist on the selected disk.
23: Error while parsing number
This error is returned if GRUB was expecting a number and read incorrect data.
24: Attempt to access block outside partition
This error is returned if a linear block address is beyond the disk partition. This error usually occurs because of a corrupted file system or a bug in the code that runs GRUB (it'sa great debugging tool).
25: Disk read error
This error is returned if a read error occurs when attempting to test or reading from a disc.
26: Too many symbolic links
This error is returned if the number of links exceeds the maximum allowed (currently 5), probably due to a loop in the links.
27: Unrecognized command
This error is returned if an unrecognized command is entered on the command line or in the boot of a configuration file where the entry is entered.
28: Selected item can not fit into memory
This error is returned if a kernel, a module, or an uploaded file can not fit in memory, or is simply too big.
29: Disk write error
This error is returned if a disk write error occurs on a particular disk. It should occur only during the installation of a partition setactive.
30: Invalid argument
This error is returned if an argument passed to a command is invalid.
31: File is not sector aligned
This error can occur only during access to a ReiserFS partition with lists of blocks (eg the command install). In this case, you need to mount the partition with the-o option notail.
32: Must be authenticated
This error is returned if you try to run a locked entry. You must enter a correct password before running such entries.
33: Serial device not configured
This error is returned if you try to go on a serial terminal to be initialized before a serial port.
34: No spare sectors on the disk
This error is returned if a disk does not have enough free space. It occurs when you try to write Stage 1.5 in the unused sectors after the MBR, but the first partition starts right after the MBR or they are used by EZ-BIOS.
This is the error 2 of 2: Bad file or directory type
This error is returned if a file is not a regular file, but something like a symbolic link, directory, or FIFO pipe.
So I installed incorrectly?
In principle yes, but I am not a specialist in grub ..
Perhaps that other contributors will inform you further.
On the installation mandriva CD, there is an option to restore/repair the mbr: it takes five minute