Page 1 of 3 123 LastLast
Results 1 to 10 of 25

Thread: error 15 :file not found on booting suse linux 10

  1. #1

    Default error 15 :file not found on booting suse linux 10

    we have suse linux 10 and ubuntu os in our system

    in suse linux enterprise desktop 10 ,whan i do online updates , knowingly or unknowingly i checked the kernel version.
    after rebooting the message displayed is error 15: file not found .{and also in the recovery mode }
    then i go to use another OS ubuntu 8.04kerrnel 2.6.24-16.In this, when we updates online or using package manager or add or remove program it shows depackage error and we maually correct the problem .then we rebooting the computer it shows four versions of ubuntu os ubuntu 8.04.1 kernel 2.6.24-22 , 2.6.24-.21 , 2.6.24-19 , 2.6.24-16, and suse linux 10 .OS not seen .
    how can i use the suse linux os without reinstallation.?(and in ubuntu after updating online updates now the ubuntu is ubuntu 8.04.3 LTS kernel 2.6.24-24.)

  2. #2
    Join Date
    Jun 2008
    Location
    Berlin, Germany
    Posts
    363

    Default Re: error 15 :file not found on booting suse linux 10

    Hi. We had this problem before. Is the following link helpful to you? "error 15: File not found" - openSUSE Forums. Good luck!

  3. #3
    Join Date
    Mar 2008
    Location
    Oz
    Posts
    10,844
    Blog Entries
    2

    Default Re: error 15 :file not found on booting suse linux 10

    If you are habitually booting from Ubuntu's bootloader and you do an online update in Suse, the pointer to Suse in Ubu's menu.lst becomes obsolete and you get "file not found". You can inoculate the menu.lst for Grub in Ubuntu by using a generic pointer that is not dependent on the kernel version that exists in Suse. For more on that see this tutorial:
    HowTo Boot / Multiboot openSUSE from the Grub Bootloader in Ubuntu

    On the other hand, if you prefer to boot habitually from Suse's bootloader, and not have it fail whenever you have a kernel upgrade in Ubuntu, you can do much the same thing (slight variations) and inoculate Suse's menu.lst against changes to Ubu's kernel. There's a tutorial for that here:
    HowTo Boot / Multiboot Ubuntu from the Grub Bootloader in openSUSE

    This all applies equally to openSUSE as to SLED/SLES 10.0

  4. #4

    Default Re: error 15 :file not found on booting suse linux 10

    hai swerdna,
    how can i know am i booting from suse's boot loader or from ubuntu's boot loader.

    and ubuntu's menu.lst shows the following
    # 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-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 use 'savedefault' or your
    # array will desync and will not let you boot your system.
    default 0

    ## timeout sec
    # Set a timeout, in SEC seconds, before automatically booting the default entry
    # (normally the first entry defined).
    timeout 10

    ## hiddenmenu
    # Hides the menu by default (press ESC to see the menu)
    #hiddenmenu

    # 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,5)
    # 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=UUID=232d9e4c-48f8-474d-83c5-a559530a9679 ro

    ## Setup crashdump menu entries
    ## e.g. crashdump=1
    # crashdump=0

    ## default grub root device
    ## e.g. groot=(hd0,0)
    # groot=(hd0,6)

    ## 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 access=v3

    ## 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=(recovery) 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

    ## 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

    howmany=2
    color cyan/blue white/blue

    ## ## End Default Options ##

    title Ubuntu 8.04.3 LTS, kernel 2.6.24-24-generic
    root (hd0,6)
    kernel /boot/vmlinuz-2.6.24-24-generic root=UUID=232d9e4c-48f8-474d-83c5-a559530a9679 ro quiet splash access=v3
    initrd /boot/initrd.img-2.6.24-24-generic
    quiet

    title Ubuntu 8.04.3 LTS, kernel 2.6.24-24-generic (recovery mode)
    root (hd0,6)
    kernel /boot/vmlinuz-2.6.24-24-generic root=UUID=232d9e4c-48f8-474d-83c5-a559530a9679 ro single
    initrd /boot/initrd.img-2.6.24-24-generic

    title Ubuntu 8.04.3 LTS, memtest86+
    root (hd0,6)
    kernel /boot/memtest86+.bin
    quiet

    ### END DEBIAN AUTOMAGIC KERNELS LIST
    elcot@elcot-laptop:~$

    and another thing is that i want step by step instructions for booting suse linux enterprise desktop 10 .where can i add suse's entry.
    please help.

  5. #5
    Join Date
    Jun 2008
    Location
    The English Lake District. UK - GMT/BST
    Posts
    36,776
    Blog Entries
    16

    Default Re: error 15 :file not found on booting suse linux 10

    You should know which grub you were using.
    I guess you were/are using Ub*ntu's

    In the menu.lst directory in ubuntu, is there a menu.lst.old or a ~menu.lst ?
    My openSUSE 13.1 KDE Box
    My Articles
    Was I any help? If yes: Click the star below

  6. #6
    Join Date
    Mar 2008
    Location
    Oz
    Posts
    10,844
    Blog Entries
    2

    Default Re: error 15 :file not found on booting suse linux 10

    Quote Originally Posted by vijay2009 View Post
    hai swerdna,
    how can i know am i booting from suse's boot loader or from ubuntu's boot loader
    If you are using Ubuntu's loader, Ubuntu will appear at the top of the list.
    If you are using SLED's loader, SLED will appear at the top of the list.
    Quote Originally Posted by vijay2009 View Post
    and another thing is that i want step by step instructions for booting suse linux enterprise desktop 10 .where can i add suse's entry.
    please help.
    Edit these lines into the menu.lst that lives in Ubuntu:
    Code:
    # Swerdna's entry to boot the SLED installation on /dev/sdaX by symlinks
    title SLED 10 (on /dev/sdaX) by symlinks
    root (hd0,Y)
    kernel /boot/vmlinuz root=/dev/sdaX
    initrd /boot/initrd
    savedefault
    boot
    You can open the file for editing in Ubuntu by running this command:
    Code:
    gksu gedit /boot/grub/menu.lst
    Replace X by your partition number for the root partition of SLED as seen from Ubuntu. You can deduce X by running this command in Ubuntu:
    Code:
     sudo fdisk -l
    Replace Y by the number you get when you subtract one from X.

    Reference: HowTo Boot / Multiboot openSUSE from the Grub Bootloader in Ubuntu

  7. #7

    Default Re: error 15 :file not found on booting suse linux 10

    Hai Swerdna,
    sudo fdisk -l shows the following

    Disk /dev/sda: 320.0 GB, 320072933376 bytes
    255 heads, 63 sectors/track, 38913 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
    Disk identifier: 0x0006fbd2

    Device Boot Start End Blocks Id System
    /dev/sda1 1 13055 104864256 83 Linux
    /dev/sda2 13056 26110 104864287+ 83 Linux
    /dev/sda3 * 26111 26241 1052257+ 83 Linux
    /dev/sda4 26242 38913 101787840 f W95 Ext'd (LBA)
    /dev/sda5 26242 26764 4200966 82 Linux swap / Solaris
    /dev/sda6 26765 31985 41937651 c W95 FAT32 (LBA)
    /dev/sda7 31986 35632 29294496 83 Linux
    /dev/sda8 35633 38913 26354601 83 Linux
    elcot@elcot-laptop:~$

    I think that the boot loader is present in the sda3.Shall I proceed?
    Then in which place, Should I edit "Swerdna Entries And those lines" in the Menu lst of Ubuntu?

  8. #8
    Join Date
    Mar 2008
    Location
    Oz
    Posts
    10,844
    Blog Entries
    2

    Default Re: error 15 :file not found on booting suse linux 10

    You can proceed.

    use the gksu gedit command to open it. Right under this line:
    Code:
    ### END DEBIAN AUTOMAGIC KERNELS LIST
    put one space/empty line then these lines:
    Code:
    # Swerdna's entry to boot the SLED installation on /dev/sda3 by symlinks
    title SLED 10 (on /dev/sda3) by symlinks
    root (hd0,2)
    kernel /boot/vmlinuz root=/dev/sda3
    initrd /boot/initrd
    savedefault
    boot
    If sda3 is SLED's root partition, it should work.

  9. #9

    Default Re: error 15 :file not found on booting suse linux 10

    hai swerdna,

    yes. we done what you said above. Then booting into SLED 10 (on /dev/sda3) by symlinks , it goes many lines up and finally shows the following

    loading reiserfs
    waiting for device /dev/sda3 to appear: OK
    rootfs:major=8 minor=3 devn=2051
    fsck 1.38 (30 june 2005)
    (here there are 3 lines seen we did not take down notes)
    file syestem is clean
    replaying journal : done
    reiserfs journal '/dev/sda 3'in blocks [18..8211]: o transactions replayed
    checking internal tree .. finished
    fsck succeeded . mounting root device read- write.
    mounting root /dev/sda3
    RieserFS:sda3:found reiserfs farmat "3.6" with standard journal
    RieserFS:sda3:using ordered data mode
    reiserfs:sda3:using jlush barriers
    RieserFS:sda3:journal params:device sda3,size 8192,journal first block 18,max trans len 1024,max batch 900,max commit age 30,max trans age 30.
    RieserFS:sda3:checking transaction log (sda3)
    RieserFS:sda3:using r5hash to sort names
    No init found.try passing init=option to the kernel
    umount: /dev/ device is busy
    umount: /dev/ device is busy
    kernel panic - not syncing: Attempted to kill init!

    (here we press and hold down the computer power button to shutdown the computer)
    then what is the problem?
    then what we will do?

  10. #10
    Join Date
    Mar 2008
    Location
    Oz
    Posts
    10,844
    Blog Entries
    2

    Default Re: error 15 :file not found on booting suse linux 10

    The boot succeeded in that Grub found then /boot/symlinks -- but there is an additional problem, perhaps with the reiserfs partition as illustrtaed by the fsck dialogue. So two things to do now:
    No 1: can you explain more of this statement:
    in suse linux enterprise desktop 10 ,whan i do online updates , knowingly or unknowingly i checked the kernel version.
    No 2: boot into Ubuntu. Make a directory sda3 in /mnt and then mount sda3 into the directory /mnt/sda3. And then run these commands:
    1. cat /mnt/sda3/etc/SuSE-release
    2. ls -l /mnt/sda3/boot | egrep "initrd|vmlinuz"
    And post the results back.

    Post Script: this is very telling but I don't know how to interpret it -- maybe someone else does:
    No init found.try passing init=option to the kernel
    umount: /dev/ device is busy
    umount: /dev/ device is busy

Page 1 of 3 123 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •