Hello!I just installed Sabayon 5.1r1 onto a new partition, but when I try to boot into it I immediately receive a text message, "Error 15: File not found". (I mean there is just no other text on a black screen.) I'm not sure what file it can't find. I've confirmed its menu.lst appears to be a 'short-cut' to grub.conf, and that grub.conf appears to contain the appropriate entires.Note Sabayon was installed on a multi-boot system as:sda1 = swapsda2 = openSUSE 11.2 (12GB partition)sda3 = mirrored (n/a)sda4 = Sabayon 5.1r1 (12GB partition)sda5 = Mandriva 2010 (12GB partition)Notes: All systems are reiserfs. Suse currently holds a main grub menu on the MBR. All other systems work just fine, and they were installed specifying placing each OS' grub on its root partition. (I may consolidate these later.) openMepis used to be on sda4 until I trashed it -wiped it as a part of running a manually partitioned Sabayon installation via its own install menus.Here's my grub.conf: ----------------------------------------# grub.conf generated by the Sabayon Linux Installer## Note that you do not have to rerun grub after making changes to this file# NOTICE: You do not have a /boot partition. This means that# all kernel and initrd paths are relative to /, eg.# root (hd0,3)# kernel /boot/kernel-genkernel real_root=/dev/sda4# initrd /boot/initramfs-genkernel### AUTOMAGIC BOOT DEVICE DETECTION -- DO NOT REMOVE ####boot=sda4### AUTOMAGIC BOOT DEVICE DETECTION END ###default=0timeout=5splashimage=(hd0,3)/boot/grub/splash.xpm.gz

title openSUSE 11.2 root (hd0,1) configfile /boot/grub/menu.lst ----------------------------------------I do see the above 'grub.conf' note re. "no /boot partition" but not sure if this is a part of the issue if an issue at all, although I do recall simply specifying only "/" as the mounting point during the install. (I'm a linux newbie -trying to convert from MS, so currently loaded a few distro's...) Either way, I'm not sure where to go from here.

"Wolfden",Yes, it's not booting anything. Not even sure if this is a "grub" per se specific error. I was hoping you could explain it to me, AND/OR tell me if there was something wrong with my grub.conf -after all., I am a newbie to this.Note: I had already tried the grub-only reinstall before posting. (Nice menu option, but this had same results.) I even then tried substituting the 'pointer' menu.lst with a copy of grub.conf as I hadn't ever seen a pointer used for this.Meanwhile, I just (this morning) completed as regular install to another- this time isolated -drive (installing w/ all the defaults- incl. MBR-based boot menu -with no other OS partitions). This regular install looks healthy, so I suspect there may be something awry with the multi-partition installation 'track'. -I'll actually re-do the multi-partition install today to essentially test it again for you.*** I'll leave a little time (2hours?) before re-installing multi-partition style if you have any recommendations for this.Al

So, I know it's reading the partitions and boot menu (grub.conf), but then what ??? -I can only suspect that something is effectively hard-coded (re. boot path to necessary files) when it should have been 'flexible' or made to follow the manual installation choices.fyi: My general steps through manual installation included: 1) Choosing manual partitioning and assigning "/" as the mount point (not "/boot") as done with all installs here. 2) Formatting to use "reiserfs" and not the default "ext4". Note: distro's like Clonezilla currently, apparently do not recognized or correctly handle "ext4", so all our installs are reiserfs. 3) Configuration, Advanced Boot Loader options were toggled to "/dev/sda4 First sector of boot partition"I believe nothing else significant was involved here.

"Wolfden",Perhaps one add'l diagnostic: I just attempted to use Sabayon's install boot menu to choose actually- the already installed -Mandriva on my sda5, and I receive this error:"Booting 'Other Operating System - Mandriva 2010'

rootnoverify (hd0,4)chainloader +1savedefault

Error 15: File not found

Press any key to continue"

Pressing any key brings me back to the Sabayon boot menu.NOTE: Then choosing openSUSE (instead of Mandriva) does allow openSUSE to boot.

The significance? Perhaps this is an indication how "up front" the issue is. i.e.: It's probably not a bad Sabayon OS install otherwise, but there is just one 'stop-gap' at a bad file/path reference re. boot loader activity. Or, perhaps the boot menu (and immediate code) wasn't compiled correctly under this kind of multi-boot and/or boot-to-partition (instead of MBR) installation (?)

I think this is all yours now as I'm not sure what else could be done here. Please let us know once this is remedied.Thanks.Al

Here's my grub.conf: ----------------------------------------# grub.conf generated by the Sabayon Linux Installer## Note that you do not have to rerun grub after making changes to this file# NOTICE: You do not have a /boot partition. This means that# all kernel and initrd paths are relative to /, eg.# root (hd0,3)# kernel /boot/kernel-genkernel real_root=/dev/sda4# initrd /boot/initramfs-genkernel### AUTOMAGIC BOOT DEVICE DETECTION -- DO NOT REMOVE ####boot=sda4### AUTOMAGIC BOOT DEVICE DETECTION END ###default=0timeout=5splashimage=(hd0,3)/boot/grub/splash.xpm.gz

1) what does "sda3 = mirrored (n/a)" mean? Al - I believe sda3 may be taken by an 'extended' reference. (?)

2) what is partitioning scheme in relation to primary/logical partitions? Al - Are you referring to hda #s? i.e.: hda0 = sda1, hda1 = sda2, ... Here's where my expertise is limited. Might you be looking for something like... Ranish displays (w/ my OS note):Pri 1 = swap 1GB (swap sda1)Pri 2 = Linux ext2fs 18GB (openSUSE sda2)Pri 3 = Extended --------Log 3 = Linux ext2fs 12GB (Mandriva sda5)Pri 4 = Linux ext2fs 12GB (Sabayon sda4)Notes:1) I just restarted the manually partioned Sabayon install, and see that Mandriva is listed as sda5 under Extended whereas Sabayon's sda4 is not under Extended. Should I be installing Sabayon in this multi-boot situation under extended? If so, why hadn't it defaulted to that? Note: I had not checked the "Force to be a primary partition" box.2) I believe "ext2fs" is just Ranish's way of interpreting "reiserfs".3) Other than Ranish, looking at the partitions from a booted Mandriva, while I can see the Sabayon partition it had no mount point displayed. Although attempting to add a "/" mount point did say it recognized one was already there.

Based on your inquiry, I took notice to Sabayon's manual install constructed a new partition after my old sda4 was deleted. I see that when I create a new partition (for yet another install of Sabayon) it automatically forces it as a Primary partition. However, I am not checking the "Force to be a primary partition" box. -Isn't this a critical issue, whther related or not to my "Error 15" issue?

The number of cylinders for this disk is set to 9729.There is nothing wrong with that, but this is larger than 1024,and could in certain setups cause problems with:1) software that runs at boot time (e.g., old versions of LILO)2) booting and partitioning software from other OSs (e.g., DOS FDISK, OS/2 FDISK)

I believe this is what I would expect if Sabayon's install wouldn't simply force it as a Primary. However, even with "Force to be a primary partition" left unchecked during the install, it makes it a primary (sda4, or hd0,3) anyway. I've tried to work around this several ways, including create the extended, logical sda6(empty) with another app. -However, then Sabayon's install can't even read any of the partitions unless I return and delete the new sda6(empty). (Duh!)

I'm not sure what you mean by miscounting partitions as, for example, simplyMepis had no problem installing as, and running on, sda4 anyway prior to Sabayon.

So, what can be done? btw: Both openSuse (MBR grub) and Mandriva (sda5 partition grub) still boot just fine.Al

Neumann wrote:"Wolfden",Perhaps one add'l diagnostic: I just attempted to use Sabayon's install boot menu to choose actually- the already installed -Mandriva on my sda5, and I receive this error:"Booting 'Other Operating System - Mandriva 2010'

rootnoverify (hd0,4)chainloader +1savedefault

Error 15: File not found

Press any key to continue"

Pressing any key brings me back to the Sabayon boot menu.NOTE: Then choosing openSUSE (instead of Mandriva) does allow openSUSE to boot.Al

well I understood that mandriva does not boot as well, but it comes out it was via SL install boot menu, my bad.

Anyways, how about you boot into bootable system and post that fdisk output just to satisfy my curiosity Honestly I am so used to pri/ext/log/log/... partition scheme that I think I never tried pri/ext/pri/?