I have Mandriva and Ubuntu on my second hard disk with Windows 7 on the first but..
Mandriva and Ubunt bootloaders ( Grub ) did not detect each other while windows based bootloader detects all three so I went to Ubuntu and updated grub and now it does detect Mandriva but will not load it.
I get a Mandriva splash screen with text messages that freezes after which I have to pull the plug and restart. I can only reproduce these messages by photo.
Also I tried to get Mandriva ( 2011.2 ) to detect Ubuntu but I think I went about it in the wrong way because nothing happened.

Attached Thumbnails

 

Hello, and welcome to LQ.

I'm no professional in this matters,
but from the errors displayed on screen, it seems like you don't have your root partition defined correctly for kernel. Which version of Grub do you use? Could you post output of "fdisk -l" and your grub.cfg file?


Skyer

You did not tell us what steps you took to make grub work. If you can boot ubuntu now, go to terminal and use these commands

sudo update-grub /dev/sda


If you want to use a graphical interface follow these directions

Grub2 graphical

Both can be done with a ubuntu live cd also.

Hi there,

I'm not sure and I can't produce a ready solution, but I think this line of your startup messages is the key:
To me, that looks like your /etc/fstab is referencing the partitions by UUID, and the partition that should become the root filesystem has a wrong UUID. Is it possible that the partitions have become new UUIDs by reinstalling grub? If so, the /etc/fstab in Ubuntu, from where you started the grub installation, has been updated, but not that of Mandriva.

Here's what I would try:

• Boot Ubuntu.
• Be root.
• Find out the actual UUID of Mandriva's root partition (Here's how to do that).
• Temporarily mount the partition that should be the Mandriva root file system.
• Open Mandriva's /etc/fstab in an editor and check if the UUIDs match the ones you found out before.
• If not, fix them.
• Check the other partitions, too (if there are more)
• Try booting Mandriva again. Good luck.

How did you do that? Didn't you say you can't boot Mandriva any more?

By the way: Are you from Thailand? The books that are visible an the left side of your screen photo look like Thai script. I can't read it, of course, but I once noticed that it looks different from most other Asian scripts ...

[X] Doc CPU

Sorry for the delay in replying but I had to make a suddent trip to hospital

The roots are all defined ok ie both ubuntu and mandriva boot ok when, I think it's called chainloaded, from the
Windows based boot loader. The problem arises when I try to boot Mandriva from the Ubuntu Grub. will post
the files shortly

I used sudo update-grub to get the Ubuntu grub to detect the Mandriva installation. I don't want to put it on /dev/sda
because it will overwrite the Windows 7 bootloader ( Acronis OS Selector )

Well spotted there. I'm Uk ex pat living in Thailand and I too get a caffeine fix first thing every day. And I had the same idea about the UUIDs but they are kind of long and made me squint. I'm going to print them in larger text and pin them up and have a good frown although I have a sneaky suspicion something about the Mandriva grub not accepting boot parameters from the Ubuntu grub or something similar, it's a Mandriva splash screen so Mandriva bootloader must be the culprit, but it works ok when I chainload from Windows. It's basically just me being pig headed enough to want to be able to boot everything from every bootloader.
I will try your suggestions and get back but meanwhile how would I update grub in Mandriva 2010.2? sudo update-grub and su (password) update-grub get me command not found type error messages

If you installed Ubuntu after Mandriva, the Ubuntu Grub should have detected the Mandriva installation.
You will need to manually edit the Mandriva boot menu file to get Ubuntu in it (Mandriva still uses Grub Legacy as far as I know).
If you really want to do this, the best way to get the information you need is to go to the site below and download the bootinfoscript and run it and review the results.txt file. You could also post the info here

http://bootinfoscript.sourceforge.net