Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I have a set-up with a RocketRaid 3120 (HighPoint) controller with its two HDDs in RAID 0 for media files. My MOBO is a Gigabyte with the AMD 770 chipset. I had Ubuntu 9.10 installed on a lone SATA HDD without issues, and had tried Fedora 11, also no problem. I had attempted a fresh install of Ubuntu 10.10 - formatting the OS HDD - and everything seemed to go OK until I tried booting off the HDD after the installation. I got "error no such device: 6a176be7-3399-47f5-be16-042a5de3aa64. grub rescue>". The same thing happened when I tried installing Fedora 14. There must be something new with GRUB that isn't happy with my hardware combination.
This is the UUID of the boot partition identified in grub. To know what UUID's are set for your system, have a look at /dev/disk/by-uuid. You should see a relationship there between partition and the uuid's.
You can look at /boot/grub/menu.lst to see what is in grub.
What is in grub may not point at the correct partition now that you have done some more installing. If you know what partition the /boot is on, and you can identify the correct uuid for that, you can manually edit menu.lst to point at the correct partition. If you get it right, it should at least start booting.
Camorri is right: you need to identify the UUID for your hard drive, and edit Grub accordingly.
I believe Fedora 14 still uses "legacy Grub" (the good old fashioned one, instead of the new, over-engineered Grub2 ). In that case, these two links are both applicable:
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.