I just installed OpenSuse 11.1 followed by Linux Mint 7. The latter produced a boot loader for all 8 operating systems on my system. All worked including SUSE. I just ran all the updates on SUSE, but immediately after reboot the loader failed to reboot SUSE. Obviously, I can no longer get into SUSE. The message was, “file not found.” Is there any solution to this dilemma short of a re-installation of SUSE. Any comments would be much appreciated.
Its unlikely I can help, but I do have a suspicion as to the problem. It reads to me that the grub boot manager setup by Mint 7 calls your openSUSE boot in such a way that openSUSE does not boot.
Speculating (and unfortunately this is only speculation on my part) its possible your Mint 7 calls your openSUSE with something like:
title openSUSE 11.1 - 2.6.27.23-0.1
root (hd0,3)
kernel /boot/vmlinuz-2.6.27.23-0.1-default root=/dev/disk/by-id/ata-ST31500341AS_9VS14DG6-part2 resume=/dev/disk/by-id/ata-ST31500341AS_9VS14DG6-part3 splash=silent showopts vga=0x346
initrd /boot/initrd-2.6.27.23-0.1-default
But you probably now have instead vmlinuz-2.6.27.25-0.1-default instead of vmlinuz-2.6.27.23-0.1-default and you probably now have instead initrd-2.6.27.25-0.1-default instead of initrd-2.6.27.23-0.1-default.
ie I am guessing (and I do not know for certain) that your Mint may be calling specific files in openSUSE?
Alternatively, if you had generic calls for vmlinux and initrd, it might work … ? :
title openSUSE 11.1
root (hd0,3)
kernel /boot/vmlinuz root=/dev/disk/by-id/ata-ST31500341AS_9VS14DG6-part2 resume=/dev/disk/by-id/ata-ST31500341AS_9VS14DG6-part3 splash=silent showopts vga=0x346
initrd /boot/initrd
Note I am speculating rather wildly here. … One need to post your /boot/grub/menu.lst files from both Mint and openSUSE.
And again, someone more skilled than I needs to answer this. Hopefully my ideas to consider don’t waste your time.
oldcpu is probably on the money. Normally a kernel upgrade on SUSE will update its menu.lst as part of the process. However as you are using a different bootloader, it didn’t update the Mint menu.lst so that was left referring to an older kernel version which would have been deleted by the upgrade.
Is there any way you can run the Mint bootloader setup to redetect the SUSE partition? Or if you know what to change in menu.lst you can follow oldcpu’s suggestion.
In future you could install SUSE’s bootloader in the partition MBR and have Mint’s bootloader chain to that.
Thanks for the replies. If a kernel upgrade on any given version of Linux only updates its own menu.lst, how can I ever hope to maintain a single bootloader for all my Linux distros? I don’t know if there is any way I can run the Mint bootloader setup to redetect the SUSE partition? I was hoping this procedure would have been fairly similar in all Linux distros and someone on this forum would know that. Is there a way, for example, to run the SUSE bootloader setup to detect other operating systems (i.e. without a full re-installation)? When I installed SUSE the first time, I made the mistake of leaving all drives disconnected except the one on which I was installing SUSE. I didn’t fully trust either distro not to block access to my existing Operating Systems, and access to WinXP was most critical. I was delighted, though, when Mint detected everything, including SUSE. This only change after updating. The bootloader was saved to that single drive but quickly ceased to open on that drive for no apparent reason. I would just go straight into the Windows on that drive. It wouldn’t have booted SUSE after reconnecting the drives anyway, unless I kept disconnected my drive cables each time I wanted to load SUSE. If there is no solution but to completely reinstall SUSE and overwrite the Mint bootloader, I intend to make a copy of the present menu.1st on a floppy so that I can copy any needed portions from the Mint bootloader to the new bootloader that hopefully will be generated by SUSE. If I don’t receive any further replies on this topic, I will assume that reinstalling SUSE with all drives connected is my only recourse. Thanks again.
No, all is not lost!
All you have to do is to either use the suse install disc and select the recover option, or boot to any of the other linux distros and use its equivalent of opensuse’s boot loader options to recover your opensuse installation. This will automate the recovery.
No, nothing so drastic required. All that is needed is probably just a edit of a couple of lines in Mint’s menu.lst. Just bring up a text editor and edit it in Mint. Much faster than a total reinstall for sure.
There is another way to avoid the problem in future. openSUSE maintains a couple of symlinks in /boot, vmlinuz points to the current kernel and initrd points to the corresponding initrd. If you edit menu.lst to use those names instead of the versioned filenames, it should stay up to date with openSUSE updates.
Thanks for the further clarification.
Here is the part for SUSE:
This entry automatically added by the Debian installer for an existing
linux installation on /dev/sdb6.
title openSUSE 11.1 (on /dev/sdb6)
root (hd1,5)
kernel /boot/vmlinuz-2.6.27.7-9-default root=/dev/disk/by-id/ata-WDC_WD10EADS-00L5B1_WD-WCAU48401505-part6 resume=/dev/disk/by-id/ata-WDC_WD10EADS-00L5B1_WD-WCAU48401505-part5 splash=silent showopts vga=0x317
initrd /boot/initrd-2.6.27.7-9-default
savedefault
boot
Do I need to edit the vmlinuz part? How to I ascertain what it should be changed to?
Regarding the Suse install disc and the recover option, specifically how do I access that option? It is the 11.1 64-bit KDE 4 Live CD that I have. What specifically does the SUSE recover option do? Does it create a new menu.lst or update the existing Mint menu.lst? If so, will it copy to the same location as my present bootloader?
It seems that there are two options here. Which is the simpler one?
Change this:
kernel /boot/vmlinuz-2.6.27.7-9-default root=/dev/disk/by-id/ata-WDC_WD10EADS-00L5B1_WD-WCAU48401505-part6 resume=/dev/disk/by-id/ata-WDC_WD10EADS-00L5B1_WD-WCAU48401505-part5 splash=silent showopts vga=0x317
initrd /boot/initrd-2.6.27.7-9-default
To this:
kernel /boot/vmlinuz root=/dev/disk/by-id/ata-WDC_WD10EADS-00L5B1_WD-WCAU48401505-part6 resume=/dev/disk/by-id/ata-WDC_WD10EADS-00L5B1_WD-WCAU48401505-part5 splash=silent showopts vga=0x317
initrd /boot/initrd
That should get you going and should be future-proof against kernel updates, provided the symlinks are there.
I would not recommend using the openSUSE Repair option at this point, as it doesn’t have a complete menu.lst, unlike Mint.
FWIW here is a more general and a lasting solution. It’s based on the fact that there exists in /boot symlinks to the real vmlinuz and the real initrd. These symlinks are automagically upgraded each time the kernel gets upgraded. So all you need is for the entry in Mint t point to the symlinks in Suse and it will stay forever current. I have a machine with that in place on the Ubuntu loader because I’ve stayed with the Ubuntu grub. It looks like this:
# Swerdna's entry to boot the openSUSE installation on /dev/sda5 by symlinks
title openSUSE 11.1 (on /dev/sda5) by symlinks
root (hd0,4)
kernel /boot/vmlinuz root=/dev/sda5
initrd /boot/initrd
boot
Works like a charm and doesn’t need updating when Suse changes.
Reference: HowTo Multiboot openSUSE from Ubuntu using the GRUB bootloader
It works! Great! Thanks so much. How did you figure out that? I’m into SUSE now! Could I ask you about a second issue. I get a message in the top right of my screen at startup about not supporting some aspect of my audio and falling back to default. Is that a concern? I have integrated Audio. There is a SoundMax ADI1988 Audio Linux Driver V1.0.11 for my MOBO for kernel 2.4 and 2.6 at the Asus site but I have no idea how to install it or if I should.
We SUSErs have our guild secrets. 
Could I ask you about a second issue.
Please start a new thread for this or people might not see your question from the title. It’s not as if we need to economise on forum threads.
I think thats a bug. … and I believe a number of users have reported this. There are a more than a fewthreads here, where users have posted solutions that worked for them:
- Sound Problem - openSUSE Forums
-
Phonon error - openSUSE Forums
*]openSUSE Forums - View Single Post - openSUSE 11.1 display and audio problems
I think I’ve seen other “solutions” as well, but a quick search did not reveal it (I probably had the wrong search parameters).
OK - I’ve been using SuSE Linux for about 6 years and have always been impressed with it until recently.
I’ll say flat out that X.org sucks when it comes to hadling computers with Intel mother boards. That’s a big market. Secondly - the new KDE4 sucks royal. I never liked Gnome and WM is for people that don’t want their GUI’s - why have it other then to allow X apps to run. So I now have no good choises in Linux and a lot of unnecessary B.S. ahead of me.
To put it this way - right now I’m in Netbsd - not very easy to use - but at least I know its going to work. Its a pain in the but - I had to compile KDE myself using pkgsrc. I had to muck through vi for a bit - but in the end it worked. But you know what? If I had a choice I’d pick that over SuSE because I know I can use KDE. I’d still go with SuSE even with the sucky KDE 4 if I got an x-Window.
I’m very annoyed at whatever x.org did to screw my i810 video drivers. Online upgrades are a very bad idea - I am/was experienced enough to make sense of the nonsense explanation for using Zypper - that’s the only thing saving you guys from a large influx of angry users. Zypper is broken in 11.0 and you have to change some configs to get it to actually do the upgrade.
For one reason or another - I can guarantee that things that used to work will enevitably be broken by something during the “upgrade.” If that something is the X-window - you have to be experienced as a user to fix it - and nothing short of a being a programmer - which I am not - to fix the situation I find myself in - by changing some source code. That’s beyond my skill level. In SuSE 11.0 with the X.org crap in there - there was a memory leak. No bad move going in the X.org direction - except that when it did work - it was easier to get an X window, when it worked. I’ll give X.org that much.
So with X broken - Zipper is your free kiss of death to most users and you are giving it away. Good thing its broken too. But what happened to the very good printer setup scheme you guys had from before? (I’ll leave that for another rant).
Why - OH WHY - can’t the community in general build upon and keep what already works working, and not do things like KDE 4 (the look and feel sucks and the good apps are gone.) KDE 3 was fine. Yast was fine. Xfree86 was fine.
Why is everyone trying to turn their installer into Knoppix? Its A SLOW INSTALL METHOD. Then add all the wasted time every time you want to install a program - the refresh button just goes and goes forever. This is on DSL at 150KB download per second its still slow. NOT A GOOD DEMO AT ALL.
So after many years of being very happy with SuSE - I’m pretty sure I’m going to be moving away from it.
Zypper accomplished nothing - I see no way to get my less then SuSE 11 back.
SuSE 7 - 9 was nice. Very nice. If I could run the applications I wanted in there I would. But I can’t because of the steep and rapid upgrade pace of glibc that forces an upgrade like every 6 months if you want to be able to install software you should be able to - like flash - etc.
Tired of this.
COULDN’T MODIFY SO YOU GET IT AGAIN.
OK - I’ve been using SuSE Linux for about 6 years and have always been impressed with it until recently. Now it just sucks like the rest of the distributions. I don’t like saying that - but its true - and what’s really sad is that even though Windows Vista, is now without a doubt, really sucky - we aren’t giving developers a platform that is reliable to be user friendly and if it worked before it will work later kind of situation - to move their products to. Consumers now have no way out. No good choices. SuSE used to be a good choice - SuSe 7 - 9 was ready, in my mind - to fill these requirements. Now I’m thinking it could be FreeBSD.
I’ll say flat out that X.org sucks when it comes to handling computers with Intel mother boards. That’s a big market.
Secondly - the new KDE4 sucks royal. Someone fork the **** thing and take it out of its misery. Bring KDE 3 back. I never liked Gnome and WM is for people that don’t want their GUI’s - why have it other then to allow X apps to run. So I now have no good choises in Linux and a lot of unnecessary B.S. ahead of me.
To put it this way - right now I’m in Netbsd - using a gui in Netbsd. That seems a tad ass backwards. But that’s the situation. Netbsd is not very easy to use - but at least I know X is going to work. Because at the end of the day I’m a point and click kind of guy. I’ll do the monkey dance if I have to, to get it to work.
Yeah, NetBSD is a pain in the but - to get X working - unless you know VI - which I hate. And yeah - I had to compile KDE myself using pkgsrc. I had to muck through vi for a bit - but in the end it worked. But you know what? If I had a choice I’d pick that over SuSE because I know I can use KDE. I’d still go with SuSE even with the sucky KDE 4 if I got an x-Window. No I can’t use Adobe Flash.
I’m very annoyed at whatever X.org did to screw my i810 video drivers. Why did anyone leave Xfree86???
With the way things break from version to version so reliably using Linux - online upgrades are a very bad idea. Zypper being broken is you saving grace. The idea of an online update is very cool - but make sure the **** thing works. Test it.
I am/was experienced enough to make sense of the nonsense explanation for using Zypper - that’s the only thing saving you guys from a large influx of angry users. Zypper is broken in 11.0 and you have to change some configs to get it to actually do the upgrade.
I fixed my Zipper and that broke my X. So I’m one of the few pissed off people.
For one reason or another - I can guarantee that things that used to work will inevitably be broken by something during the “upgrade.” If that something is the X-window - you have to be experienced as a user to fix it - and nothing short of a being a programmer - in this situation - which I am not - to fix the situation I find myself in - AKA I’m screwed - I have to reinstall a downgrade. Fixing the source code to get X.org to work in SuSE 11.1 - that’s beyond my skill level. Even if I got it to work - it still sucks - in SuSE 11.0 with the X.org crap in there - there was a memory leak in X. Made my system slow as Vista. It was a bad move going in the X.org direction - except that when it did work - it was easier to get an X window, when it worked. I’ll give X.org that much.
So with X broken - Zipper is your free kiss of death to most users and you are giving it away. Good thing its broken too. But what happened to the very good printer setup scheme you guys had from before? (I’ll leave that for another rant).
Why - OH WHY - can’t the community in general build upon and keep what already works working, and not do things like KDE 4 (the look and feel sucks and the good apps are gone.) KDE 3 was fine. Yast was fine. Xfree86 was fine.
Why is everyone trying to turn their installer into Knoppix? Its A SLOW INSTALL METHOD. Then add all the wasted time every time you want to install a program - the refresh button just goes and goes forever. This is on DSL at 150KB download per second its still slow. NOT A GOOD DEMO AT ALL.
So after many years of being very happy with SuSE - I’m pretty sure I’m going to be moving away from it.
Zypper accomplished nothing - I see no way to get my less then satisfactory SuSE 11 back.
So how is this any better then apt-rpm? No its not - now there are a billion commands - I just want to install something.
SuSE 7 - 9 was nice. Very nice. If I could run current applications I want to run in any of those SuSE versions - I would. But I can’t because of the steep and rapid upgrade pace of glibc that forces an upgrade like every 6 months if you want to be able to install software you should be able to - like flash - etc.
I’m tired of this.
Hey NOT-AGAIN, this thread is for archp2008 who was looking for help.
Please also note this is an openSUSE support forum. We don’t package openSUSE. We dont make the decisions that go in openSUSE. We just provide support.
But if there is any thing specific we can help you on wrt openSUSE, please advise, and I’m confident many of our users will jump in and try to give you help.
We also try to accomodate our users by creating a Soap Box forum, where rants are commonly placed Soapbox - openSUSE Forums . the “Install/Boot/Login” area is not our location for rants. 
If you are unsure as to where to put a post, please go to the top level page and look: http://forums.opensuse.org/ There is a description there to help guide you. Or simply PM one of our moderators and ask where the best place might be to put a post.
But please do post any specific technical questions/problems on openSUSE where you would like assistence because it does not work for you, and as noted, our membership will likely jump in and help.
So welcome to our forum, and please post specific questions on areas where we can try help. Again, note this is a support forum where we try to help users.
p.s. If you have no objections, I’ll delete your first (duplicate - almost) post.
I had SUSE booting from the main disk menu (along with 7 other OS’s) for the past couple of months, and have been completing regular updates, but since yesterday I’m getting “file not found” for SUSE. All other OS’s are OK at this moment. What’s the simplest fix to get SUSE back?
The simplest? I have no idea.
If you had multiple entries in the grub menu, its quite possible the rpm script for a kernel update failed to manage the multiple entries. You could 1st backup the /boot/grub/menu.lst and try to boot the to the openSUSE rescue CD and restore grub entry for openSUSE. You might lose your other grub entries in the process, which is why the backup is important.
Alternatively you could just boot from a live CD (or from another Linux OS that can access the boot menu, if grub) and post here the content of the grub menu.lst (typically located under /boot/grub directory) and with root permissions the output of:
fdisk -l
and then explain which partition belongs to which OS… and maybe someone can answer.
Please say in detail how you were booting the “SUSE” that no longer boots.
Thanks for the reply. I was out of town for the past couple of days and couldn’t get back until today.
I tried both menu options regular and failsafe - same result
This is from Linux Mint which is the OS that I used to reinstall because it finds all the other OS’s. I just had to enter the correct name of some of the listings and comment out the ones I didn’t want to show.
menu.lst - See: grub(8), info grub, update-grub(8)
grub-install(8), grub-floppy(8),
grub-md5-crypt, /usr/share/doc/grub
and /usr/share/doc/grub-legacy-doc/.
default num
Set the default entry to the entry number NUM. Numbering starts from 0, and
the entry number 0 is the default if the command is not used.
You can specify ‘saved’ instead of a number. In this case, the default entry
is the entry saved with the command ‘savedefault’.
WARNING: If you are using dmraid do not change this entry to ‘saved’ or your
array will desync and will not let you boot your system.
default 0
Graphical boot menu location
gfxmenu=/boot/gfxmenu/linuxmint.message
timeout sec
Set a timeout, in SEC seconds, before automatically booting the default entry
(normally the first entry defined).
timeout 5
Pretty colours
color cyan/blue white/blue
password ‘–md5’] passwd
If used in the first section of a menu file, disable all interactive editing
control (menu entry editor and command-line) and entries protected by the
command ‘lock’
e.g. password topsecret
password --md5 $1$gLhU0/$aW78kHK1QfV3P2b2znUoe/
password topsecret
examples
title Windows 95/98/NT/2000
root (hd0,0)
makeactive
chainloader +1
title Linux
root (hd0,1)
kernel /vmlinuz root=/dev/hda2 ro
Put static boot stanzas before and/or after AUTOMAGIC KERNEL LIST
BEGIN AUTOMAGIC KERNELS LIST
lines between the AUTOMAGIC KERNELS LIST markers will be modified
by the debian update-grub script except for the default options below
DO NOT UNCOMMENT THEM, Just edit them to your needs
## Start Default Options
default kernel options
default kernel options for automagic boot options
If you want special options for specific kernels use kopt_x_y_z
where x.y.z is kernel version. Minor versions can be omitted.
e.g. kopt=root=/dev/hda1 ro
kopt_2_6_8=root=/dev/hdc1 ro
kopt_2_6_8_2_686=root=/dev/hdc2 ro
kopt=root=/dev/sde5 ro
default grub root device
e.g. groot=(hd0,0)
groot=(hd4,4)
should update-grub create alternative automagic boot options
e.g. alternative=true
alternative=false
alternative=true
should update-grub lock alternative automagic boot options
e.g. lockalternative=true
lockalternative=false
lockalternative=false
additional options to use with the default boot option, but not with the
alternatives
e.g. defoptions=vga=791 resume=/dev/hda5
defoptions=quiet splash
should update-grub lock old automagic boot options
e.g. lockold=false
lockold=true
lockold=false
Xen hypervisor options to use with the default Xen boot option
xenhopt=
Xen Linux kernel options to use with the default Xen boot option
xenkopt=console=tty0
altoption boot targets option
multiple altoptions lines are allowed
e.g. altoptions=(extra menu suffix) extra boot options
altoptions=(single-user) single
altoptions=(recovery mode) single
controls how many kernels should be put into the menu.lst
only counts the first occurence of a kernel, not the
alternative kernel options
e.g. howmany=all
howmany=7
howmany=all
specify if running in Xen domU or have grub detect automatically
update-grub will ignore non-xen kernels when running in domU and vice versa
e.g. indomU=detect
indomU=true
indomU=false
indomU=detect
should update-grub create memtest86 boot option
e.g. memtest86=true
memtest86=false
memtest86=true
should update-grub adjust the value of the default booted system
can be true or false
updatedefaultentry=false
should update-grub add savedefault to the default options
can be true or false
savedefault=false
## End Default Options
This is a divider, added to separate the menu items below from the Debian
ones.
title Windows Operating Systems ----------------------------------------
root
This entry automatically added by the Debian installer for a non-linux OS
on /dev/sda1
title Windows XP Pro (32-bit)
rootnoverify (hd0,0)
savedefault
makeactive
chainloader +1
This entry automatically added by the Debian installer for a non-linux OS
on /dev/sdb1
title Windows XP Pro (64-bit)
rootnoverify (hd1,0)
savedefault
makeactive
map (hd0) (hd1)
map (hd1) (hd0)
chainloader +1
This entry automatically added by the Debian installer for a non-linux OS
on /dev/sdd2
title WinVista Boot Pro (WinVista 32 or Windows 7)
rootnoverify (hd3,1)
savedefault
makeactive
map (hd0) (hd3)
map (hd3) (hd0)
chainloader +1
This entry automatically added by the Debian installer for a non-linux OS
on /dev/sde1
title Windows Vista (64-bit)
rootnoverify (hd4,0)
savedefault
makeactive
map (hd0) (hd4)
map (hd4) (hd0)
chainloader +1
This is a divider, added to separate the menu items below from the Debian
ones.
title Linux Operating Systems ----------------------------------------
root
title Linux Mint 7 Gloria x64
kernel 2.6.28-11-generic
root (hd4,4)
kernel /boot/vmlinuz-2.6.28-11-generic root=/dev/sde5 ro quiet splash
initrd /boot/initrd.img-2.6.28-11-generic
quiet
title Linux Mint 7 Gloria x64
kernel 2.6.28-11-generic (recovery mode)
root (hd4,4)
kernel /boot/vmlinuz-2.6.28-11-generic root=/dev/sde5 ro single
initrd /boot/initrd.img-2.6.28-11-generic
title Linux Mint 7 Gloria x64, memtest86+
root (hd4,4)
kernel /boot/memtest86+.bin
quiet
END DEBIAN AUTOMAGIC KERNELS LIST
This entry automatically added by the Debian installer for an existing
linux installation on /dev/sda6.
title Linux Ubuntu 9.04
(on /dev/sda6)
root (hd0,4)
kernel /vmlinuz-2.6.27-9-generic root=UUID=d23f4423-71f5-4588-a9d3-2845cacce7d2 ro quiet splash
initrd /initrd.img-2.6.27-9-generic
savedefault
boot
This entry automatically added by the Debian installer for an existing
linux installation on /dev/sda6.
title Linux Ubuntu (recovery mode) (on /dev/sda6)
root (hd0,4)
kernel /vmlinuz-2.6.27-9-generic root=UUID=d23f4423-71f5-4588-a9d3-2845cacce7d2 ro single
initrd /initrd.img-2.6.27-9-generic
savedefault
boot
This entry automatically added by the Debian installer for an existing
linux installation on /dev/sdb6.
title Linux openSUSE 11.1
- 2.6.27.25-0.1 (on /dev/sdb6)
root (hd1,5)
kernel /boot/vmlinuz-2.6.27.25-0.1-default root=/dev/disk/by-id/ata-WDC_WD10EADS-00L5B1_WD-WCAU48401505-part6 resume=/dev/disk/by-id/ata-WDC_WD10EADS-00L5B1_WD-WCAU48401505-part5 splash=silent showopts vga=0x317
initrd /boot/initrd-2.6.27.25-0.1-default
savedefault
boot
This entry automatically added by the Debian installer for an existing
linux installation on /dev/sdb6.
title Failsafe – openSUSE 11.1 - 2.6.27.25-0.1 (on /dev/sdb6)
root (hd1,5)
kernel /boot/vmlinuz-2.6.27.25-0.1-default root=/dev/disk/by-id/ata-WDC_WD10EADS-00L5B1_WD-WCAU48401505-part6 showopts ide=nodma apm=off noresume edd=off powersaved=off nohz=off highres=off processor.max_cstate=1 x11failsafe vga=0x317
initrd /boot/initrd-2.6.27.25-0.1-default
savedefault
boot
title Mandriva grub
root (hd2,5)
chainloader +1
This entry automatically added by the Debian installer for an existing
linux installation on /dev/sdc6.
title Linux Mandriva One i586 KDE4
(on /dev/sdc6)
root (hd2,5)
kernel /boot/vmlinuz BOOT_IMAGE=linux root=UUID=15a961f4-90a9-4905-b392-20fff44da061 resume=UUID=dd58cd60-4923-494f-80d9-73525b53675d splash=silent vga=788
initrd (hd2,5)/boot/initrd.img
savedefault
boot
This entry automatically added by the Debian installer for an existing
Mandriva installation on /dev/sdc6.
title Mandriva-nonfb (on /dev/sdc6)
root (hd2,5)
kernel /boot/vmlinuz BOOT_IMAGE=linux-nonfb root=UUID=15a961f4-90a9-4905-b392-20fff44da061
resume=UUID=dd58cd60-4923-494f-80d9-73525b53675d
initrd (hd2,5)/boot/initrd.img
savedefault
boot
This entry automatically added by the Debian installer for an existing
linux installation on /dev/sdc6.
title Mandriva failsafe (on /dev/sdc6)
root (hd2,5)
kernel /boot/vmlinuz BOOT_IMAGE=failsafe root=UUID=15a961f4-90a9-4905-b392-20fff44da061 failsafe
initrd (hd2,5)/boot/initrd.img
savedefault
boot
This entry automatically added by the Debian installer for an existing
linux installation on /dev/sdc6.
title Mandriva desktop586 2.6.29.1-4mnb (on /dev/sdc6)
root (hd2,5)
kernel /boot/vmlinuz-2.6.29.1-desktop586-4mnb BOOT_IMAGE=desktop586_2.6.29.1-4mnb root=UUID=15a961f4-90a9-4905-b392-20fff44da061
resume=UUID=dd58cd60-4923-494f-80d9-73525b53675d splash=silent vga=788
initrd (hd2,5)/boot/initrd-2.6.29.1-desktop586-4mnb.img
savedefault
boot
This entry automatically added by the Debian installer for an existing
linux installation on /dev/sdc6.
title Mandriva desktop586 2.6.29.6-1mnb (on /dev/sdc6)
root (hd2,5)
kernel /boot/vmlinuz-2.6.29.6-desktop586-1mnb BOOT_IMAGE=desktop586_2.6.29.6-1mnb root=UUID=15a961f4-90a9-4905-b392-20fff44da061
resume=UUID=dd58cd60-4923-494f-80d9-73525b53675d splash=silent vga=788
initrd (hd2,5)/boot/initrd-2.6.29.6-desktop586-1mnb.img
savedefault
boot
arch@arch-desktop ~ $ sudo fdisk -l
Disk /dev/sda: 320.0 GB, 320072933376 bytes
255 heads, 63 sectors/track, 38913 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x07510751
Device Boot Start End Blocks Id System
/dev/sda1 * 1 35120 282101368+ 7 HPFS/NTFS
/dev/sda2 35121 35125 40162+ 7 HPFS/NTFS
/dev/sda3 35126 35368 1951897+ 82 Linux swap / Solaris
/dev/sda4 35369 38913 28475212+ 5 Extended
/dev/sda5 35369 35639 2176776 83 Linux
/dev/sda6 35640 38913 26298372+ 83 Linux
Disk /dev/sdb: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x09490dc5
Device Boot Start End Blocks Id System
/dev/sdb1 * 1 2550 20480000 7 HPFS/NTFS
Partition 1 does not end on cylinder boundary.
/dev/sdb2 2550 66291 512000000 7 HPFS/NTFS
Partition 2 does not end on cylinder boundary.
/dev/sdb3 88286 121602 267612864 7 HPFS/NTFS
Partition 3 does not end on cylinder boundary.
/dev/sdb4 82864 88286 43548672 5 Extended
Partition 4 does not end on cylinder boundary.
/dev/sdb5 82864 83125 2097144 82 Linux swap / Solaris
/dev/sdb6 83125 85736 20971512 83 Linux
/dev/sdb7 85736 88286 20479944 83 Linux
Partition table entries are not in disk order
Disk /dev/sdc: 640.1 GB, 640135028736 bytes
255 heads, 63 sectors/track, 77825 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x500b9b3f
Device Boot Start End Blocks Id System
/dev/sdc1 * 1 987 7928046 7 HPFS/NTFS
/dev/sdc2 988 16773 126801045 5 Extended
/dev/sdc3 16774 77826 490400253 7 HPFS/NTFS
/dev/sdc5 989 9912 71682030 7 HPFS/NTFS
/dev/sdc6 9913 11480 12594928+ 83 Linux
/dev/sdc7 11481 11989 4088511 82 Linux swap / Solaris
/dev/sdc8 11990 16773 38427448+ 83 Linux
Disk /dev/sdd: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x5d7d47e1
Device Boot Start End Blocks Id System
/dev/sdd1 1 3942 31662080 7 HPFS/NTFS
/dev/sdd2 * 3943 6667 21888562+ 7 HPFS/NTFS
/dev/sdd3 6668 48441 335548631 7 HPFS/NTFS
/dev/sdd4 48442 121601 587657700 7 HPFS/NTFS
Disk /dev/sde: 80.0 GB, 80026361856 bytes
255 heads, 63 sectors/track, 9729 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0xba1a5abd
Device Boot Start End Blocks Id System
/dev/sde1 * 1 7817 62788156 7 HPFS/NTFS
/dev/sde2 7817 7843 204800 83 Linux
/dev/sde3 7844 9301 11711385 5 Extended
/dev/sde5 7844 9301 11711353+ 83 Linux
arch@arch-desktop ~ $
Likely what happened is the kernel versions listed in the Mint Grub entires has changed during a Suse online update so you get “file not found”.
Try commenting out / backing up / diabling this obsolete entry by adding hash (#) marks to the start of lines:
# This entry automatically added by the Debian installer for an existing
# linux installation on /dev/sdb6.
title Linux openSUSE 11.1
# - 2.6.27.25-0.1 (on /dev/sdb6)
root (hd1,5)
kernel /boot/vmlinuz-2.6.27.25-0.1-default root=/dev/disk/by-id/ata-WDC_WD10EADS-00L5B1_WD-WCAU48401505-part6 resume=/dev/disk/by-id/ata-WDC_WD10EADS-00L5B1_WD-WCAU48401505-part5 splash=silent showopts vga=0x317
initrd /boot/initrd-2.6.27.25-0.1-default
savedefault
boot
And editing in this symlink-follower version:
# Swerdna's entry to boot the openSUSE installation on /dev/sda6 by symlinks
title openSUSE 11.1 (on /dev/sda6) by symlinks
root (hd0,5)
kernel /boot/vmlinuz root=/dev/sda6
initrd /boot/initrd
savedefault
boot
Reference: HowTo Multiboot openSUSE from Ubuntu using the GRUB bootloader