No boot after upgrade

Toshiba notebook is set up to triple boot win7, mepis 8.5 and os 11.3.
sda1,2,3 win7
sda4 extended
sda5 os11.3 root
sda6 swap
sda7 os11.3 home
sda8 mepis root
sda9 mepis home
sda10 fat32
all systems 64 bit.
os11.3 installed recently (few weeks) but was working fine.
Prior to installing os11.3, sda5&7 were mepis 32 bit.
Os11.3 installed from live cd.

Recent update of os11.3 left system with boot failure, “file not found”.
I booted mepis and used utility to reinstall grub, but no joy.
Appeared to install ok but on reboot, sda5 identified as ‘mepis’ not os11.3 and would not boot. Win7 & mepis boot ok.

Next, booted live Parted Magic and repaired as per another thread here, but again, no joy.
NONE of the systems will boot.

Rebooted mepis live cd and reinstalled grub again. Sda5 still identified as mepis and will not boot. Win7 & mepis boot ok.

Running mepis, I can see sda5 & 7. Both appear ok.

Any suggestions to fix without reinstalling os11.3?

So what I might suggest is to visit the following thread, look at message #59 and download the most recent version of findgrub and run it in mepis and post the output here in a message:

Looking for Grub and Windows bootloader in all partitions.

If possible, run the following terminal command:

su -
fdisk -l

Finally, if possible, post the informatgion listed in your present grub menu.lst file:

cat /boot/grub/menu.lst

This all presumes you can get mepis to run for you.

Thank You,

Fixed, but I don’t understand all I know about it.
Apparently, os11.3 upgrade installed new kernel as kernel in sda5 /boot/grub now identified as 2.6.34.7-0.5-desktop.
Howevere, upgrade did not complete and new file was not extracted but remained as compressed only.

System boots using grub on sda8 (mepis) and thus was not upgraded with os11.3 upgrade. Kernel there still identified as 2.6.34.7-0.4-default.
Fortunately, was able to boot mepis and access os11.3 root partition. Finally recognized difference in file names and was able to manually update mepis grub to latest designation. Also had to maunally extract compressed file in os11.3 /boot/grub/.
But at last it booted andall appears ok.

Can’t understand why reinstalling grub with mepis identified os11.3 partition as previously installed mepis 32 bit and why Parted Magic created new grub that would not boot any of the 3 systems.

Ability to reinstall grubfrom mepis live cd is a real bonus!

Fixed, but I don’t understand all I know about it.
Apparently, os11.3 upgrade installed new kernel as kernel in sda5 /boot/grub now identified as 2.6.34.7-0.5-desktop.
Howevere, upgrade did not complete and new file was not extracted but remained as compressed only.

System boots using grub on sda8 (mepis) and thus was not upgraded with os11.3 upgrade. Kernel there still identified as 2.6.34.7-0.4-default.
Fortunately, was able to boot mepis and access os11.3 root partition. Finally recognized difference in file names and was able to manually update mepis grub to latest designation. Also had to manually extract compressed file in os11.3 /boot/grub/.
But at last it booted and all appears ok.

Can’t understand why reinstalling grub with mepis identified os11.3 partition as previously installed mepis 32 bit and why Parted Magic created new grub that would not boot any of the 3 systems.

Ability to reinstall grubfrom mepis live cd is a real bonus!
First off, I want to congratulate you for figuring out the problem and fixing it. You should pat yourself on the back for that one. Many users would have been unable to figure it all out. I can only say that something went wrong during the install. Packages are kept on the disk in images and the files are compressed to save room. Just what went wrong is anyone’s guess, but you got to the bottom of it and made it all work, so good for you.

Thank You,