Results 1 to 6 of 6

Thread: Fatal: open /boot/vmlinuz: No such file or directory

  1. #1
    Just burned his ISO
    Join Date
    Aug 2008
    Posts
    2

    Default Fatal: open /boot/vmlinuz: No such file or directory

    First off I apologize if this has been asked and answered already... searching the line above returned 20+ pages of results, none of which seemed to be relevant. I have used linux casually for quite a while, but this is my first time using LILO as a bootloader.

    I followed the instructions on the RE Wiki video for dual booting Backtrack/Windows XP. I'd like to edit my lilo.conf to shorten the timeout and increase boot speed, but typing lilo -v after editing returns the following:

    LILO version 22.8, Copyright (C) 1992-1998 Werner Almesberger
    Development beyond version 21 Copyright (C) 1999-2006 John Coffman
    Released 19-Feb-2007 and compiled at 01:09:42 on Jun 10 2007.

    Reading boot sector from /dev/sda
    Warning: bypassing VolumeID scan of drive flagged INACCESSIBLE: /dev/sdc
    Using MENU secondary loader
    Calling map_insert_data

    Boot image: /boot/vmlinuz
    Fatal: open /boot/vmlinuz: No such file or directory



    What am I doing wrong? This lilo.conf worked when I installed BT3.



    ba32 # Allow booting past 1024th cylinder with a recent BIOS
    boot = /dev/sda
    # message = /boot/boot_message.txt
    prompt
    timeout = 50
    change-rules
    reset
    vga=791

    disk = /dev/sdc inaccessible

    # Linux bootable partition config begins
    image = /boot/vmlinuz
    root = /dev/sda4
    label = backtrack3
    read-only
    initrd = /boot/splash.initrd
    # Linux bootable partition config ends

    other = /dev/sda1
    label = WindowsXP
    table = /dev/sda

  2. #2
    Developer
    Join Date
    Mar 2007
    Posts
    6,126

    Default

    If you followed the dual boot video on the wiki that means you created a /boot partition so your problem is /boot is not mounted when you run the lilo -v command. You have a few options...
    1) edit /etc/fstab to allow /boot to be mount automatically at boot time. (This is generally frowned on a defeats the purpose of a /boot partition.)

    2) Mount boot by command line whenever needed. For example if /boot is at sda2 like in the video one would do this..

    purehate@pwnsauce ~ $ mount /dev/sda2 /boot

    Then just make sure your kernel is in the boot directory...

    purehate@pwnsauce ~ $ cd /boot
    purehate@pwnsauce /boot $ ls
    boot config.bak grub kernel-2.6.25-gentoo-r6 lost+found memtest86
    purehate@pwnsauce /boot $

    Your looking for vmlinuz which is the name of the backtrack kernel by default.
    *note Obviously I'm using another OS but the commands are the same.

  3. #3
    Just burned his ISO
    Join Date
    Aug 2008
    Posts
    2

    Default

    Ah, I had forgotten that there was a seperate boot partition made in the install process... I thought for some reason my files had moved somewhere else. Considering I only needed to edit lilo.conf once, I just mounted and unmounted /boot.

    Thank you for the answer... I don't know how long it would have taken me to remember that without it.

  4. #4
    Member
    Join Date
    Mar 2008
    Posts
    111

    Default

    Pureh@te, I have installed BT3 with root/boot/swap partition like the tutorial said and just root/boot and just a root partition

    1) edit /etc/fstab to allow /boot to be mount automatically at boot time. (This is generally frowned on a defeats the purpose of a /boot partition.)
    What are the advantages of having a boot and swap partition and why is the boot partition not supposed to be mounted?

    Calypso

  5. #5
    Developer
    Join Date
    Mar 2007
    Posts
    6,126

    Default

    Quote Originally Posted by calypso View Post
    Pureh@te, I have installed BT3 with root/boot/swap partition like the tutorial said and just root/boot and just a root partition



    What are the advantages of having a boot and swap partition and why is the boot partition not supposed to be mounted?

    Calypso
    Calypso the theory is that if your kernel is on a separate /boot partition then it is safe from harm. For example if your whole system were to be corrupted in some way beyond repair then your kernel would be safe on a another partition. In order for this to work right I believe the partition has to be unmounted.
    Its also a security measure because on someone with root access should be able to mount anything.
    Swap is a cheap way to gain more memory. This was generally used on older machines with less memory than we have to day but in the world of 300+ gig hard drives, who cares to give a few gigs up to swap.

  6. #6
    Just burned his ISO
    Join Date
    May 2009
    Posts
    3

    Default lilo -v not correct , installed bt4 beta to hdd

    *EDIT*

    im a we todd , thats what happens when i spend everywaking second working on this laptop ,
    i mistakenly though it mean hdc , and though it was the cdrom that was keeping me from moving forward
    i just yanked all the usb sticks out and it worked


    my bad ,



    i've installed to my internal laptop hdd and i get all the way to lilo -v and get this

    root@bt:/mnt/bt/etc# lilo -v
    LILO version 22.8, Copyright (C) 1992-1998 Werner Almesberger
    Development beyond version 21 Copyright (C) 1999-2006 John Coffman
    Released 19-Feb-2007, and compiled at 14:08:06 on May 15 2008
    Ubuntu

    Reading boot sector from /dev/hda
    Cannot proceed. Maybe you need to add this to your lilo.conf:
    disk=/dev/sdc inaccessible
    (real error shown below)
    Fatal: open /dev/sdc: Read-only file system

    im doing this off the live cd , no idea whats wrong ,

    lilo.conf


    lba32
    compact
    boot=/dev/hda
    root=/dev/hda3
    # disk=/dev/sdc inaccessible
    # bitmap=/boot/sarge.bmp
    # bmp-colors=1,,0,2,,0
    # bmp-table=120p,173p,1,15,17
    # bmp-timer=254p,432p,1,0,0
    # install=bmp
    # delay=20
    prompt
    timeout=50
    # map=/boot/map
    vga=0x317
    image=/boot/vmlinuz
    label="BT4"
    read-only
    initrd=/boot/splash.initrd


    fstab

    GNU nano 2.0.7 File: /etc/fstab

    /dev/hda3 / reiserfs defaults 0 0 # AutoUpdate
    /dev/hda2 none swap sw 0 0
    proc /proc proc defaults 0 0 # AutoUpdate
    sysfs /sys sysfs defaults 0 0 # AutoUpdate
    devpts /dev/pts devpts gid=5,mode=620 0 0 # AutoUpdate
    tmpfs /dev/shm tmpfs defaults 0 0 # AutoUpdate


    it says add the hdc inacess , but that doesnt work , cause ive done that so ive done something wrong , followed the bt4 beta pdf ,

    any ideas , im stuck ...

Posting Permissions

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