Solution to crcerror, systemhalted, and error15 problems in Ubuntu9.04

I got Ubuntu 9.04 in Ubuntu's Chinese community. I wanted to install and play it. I used to play it before, but it was just a classmate's "Guide". I thought it was boring. So after a long time, I suddenly wanted to play with myself. I thought that was what I really wanted. I had installed WindowsXP and FedoraCore9 on the local machine. I used the WindowsXP Boot Program (I didn't want to use grub to write it into MBR, maybe it's the reason for being preemptible), so grub is not installed on both FC and Ubuntu,

I had a Ubuntu 9.04 in the Chinese community of Ubuntu and wanted to install it for fun. I used to play it before, but it was a "Guide" of my classmates. I felt boring, after a long time, I suddenly wanted to play with myself and thought that was what I really wanted.

Windows XP and Fedora Core 9 have been installed on the local machine, and the boot program of Windows XP is used (you do not want to use grub to write MBR, maybe it is the reason for being preemptible ), therefore, grub is not installed in FC and Ubuntu. Instead, you can use the common method to install grub from the hard disk to boot the linux system. Of course, the menu. write it by yourself! I will not repeat the installation of linux from the hard disk here. I will try to find the information on the Internet. I want to talk about some changes in the grub boot system of ubuntu. If you have installed fc before, you may know that you are writing the grub boot file menu. lst. You can use the code similar to the following to successfully guide.

Title Fedora Core 9 (2.6.25-14. fc9.i686)
Root (hd0, 2)
Kernel/vmlinuz-2.6.25-14.fc9.i686 ro root = LABEL =/rhgb quiet vga = 792
Initrd/initrd-2.6.25-14.fc9.i686.img

However, after I installed Ubuntu9.04 and wrote the file as before, I thought I could enjoy the excitement of the new system, but the problem happened to me unexpectedly.
. The boot will always fail. The crc error, system halted, or error15 file not find error occurs. Why? I didn't know at the time, so I went to the east to find the West. I couldn't solve the problem. As long as it was written like root (hd0, x), the problem would always occur, it is called a depressing one, so the menu is taken out from the partition where ubuntu has been installed using javase2fs. lst file, which is used to write the menu. lst, So I accidentally saw the ubuntu boot screen when I started it next time. It's a good idea to post a file for you to see.

Default = 0
Timeout = 3
Splashimage = (hd0, 2)/grub/splash.xpm.gz
Title Fedora Core 9 (2.6.25-14. fc9.i686)
Root (hd0, 2)
Kernel/vmlinuz-2.6.25-14.fc9.i686 ro root = LABEL =/rhgb quiet vga = 792
Initrd/initrd-2.6.25-14.fc9.i686.img
Title Ubuntu 9.04, kernel 2.6.28-11-generic
Uuid 289be983-3504-473d-84d1-492bbeb4a291
Kernel (hd0, 7)/vmlinuz-2.6.28-11-generic root = UUID = 7be913c8-a80e-4321-b291-fdc81b885152 ro quiet splash vga = 792
Initrd (hd0, 7)/initrd. img-2.6.28-11-generic
Quiet
Title Other
Rootnoverify (hd0, 0)
Chainloader + 1

The reason is clear at first glance. ubuntu no longer uses the sda or hda mark to identify the partition, but uses the uuid to mark it. This will certainly better mark the location of the partition, for more information on https://help.ubuntu.com/community/usinguid, refer to Linux now prefers to use UUID (Universally Unique Identifier), LABEL, or symlinks to identify media storage devices on a system. directly using/dev/hd * # or/dev/sd * # is no longer preferred since these device assignments can change between system boots:

I hope that comrades who have the same questions as me can get the answer from my experience and avoid detours!