Results 1 to 4 of 4

Thread: Fixing initrd.img and vmlinuz symbolic links after R1 > R2 upgrade

Hybrid View

  1. #1
    Just burned his ISO
    Join Date
    May 2011
    Posts
    24

    Default Fixing initrd.img and vmlinuz symbolic links after R1 > R2 upgrade

    After recently performing the R1 > R2 upgrade process I noticed that the symbolic links to the kernel for initrd.img and vmlinuz are not updated and will still point to the older 2.6.39.4 kernel. This is not a show stopping issue, however it does mean that certain scripts that update boot related actions will automatically go for the older kernel rather than the new kernel which can be a tad annoying. The fix is to remove and recreate the symbolic links manually:

    1. cd onto the root of your filesystem:

    Code:
    cd /
    Use ls -l to confirm you are on the root of the filesystem. You will see folders like /etc /home /usr etc. All were interested in is the initrd.img and vmlinuz symbolic links which are signified with an -> symbol. These two files are pointing to the boot initrd and vmlinuz files. They will look like this at this point from a R1 > R2 upgrade:

    initrd.img -> boot/initrd.img-2.6.39.4
    vmlinuz -> boot/vmlinuz-2.6.39.4
    These need to be updated to default to the new kernel.

    2. Remove the symbolic links with rm:

    Code:
    rm initrd.img && rm vmlinuz
    3. Recreate the symbolic links with the following commands:

    Code:
    ln -s boot/initrd.img-3.2.6 initrd.img
    ln -s boot/vmlinuz-3.2.6 vmlinuz
    4. Re run ls -l to confirm the symbolic links were correctly created. They should now look like this:

    initrd.img -> boot/initrd.img-3.2.6
    vmlinuz -> boot/vmlinuz-3.2.6
    Now the symbolic links point to the newer kernel and running scripts like: update-initramfs -u will automatically select the latest kernel.

    Note: This change does not affect the use of the older kernel. Providing you leave the older kernel packages alone you will still be able to boot it with no problem.
    Last edited by James2k; 03-24-2012 at 05:56 AM.

  2. #2
    Just burned his ISO
    Join Date
    Mar 2012
    Posts
    1

    Default Re: Fixing initrd.img and vmlinuz symbolic links after R1 > R2 upgrade

    Thank you very much Its Work
    Solved the problem I was having them since 3 days
    شكراً

  3. #3
    Just burned his ISO
    Join Date
    May 2011
    Posts
    24

    Default Re: Fixing initrd.img and vmlinuz symbolic links after R1 > R2 upgrade

    No problem !

  4. #4
    Just burned his ISO m3onh0x84's Avatar
    Join Date
    Apr 2011
    Posts
    3

    Default Re: Fixing initrd.img and vmlinuz symbolic links after R1 > R2 upgrade

    thanks a lot, I'm fix this problem. Good job

Similar Threads

  1. Fatal: open /boot/vmlinuz: No such file or directory
    By InvoluntaryRebellion in forum OLD Newbie Area
    Replies: 5
    Last Post: 05-19-2009, 12:03 AM
  2. Basic Linux Question about Symbolic Links
    By JibberingJ in forum OLD Newbie Area
    Replies: 0
    Last Post: 10-11-2008, 03:25 AM
  3. Persistent changes via symbolic link?
    By rob356 in forum OLD Newbie Area
    Replies: 1
    Last Post: 07-27-2008, 05:50 PM
  4. Replies: 2
    Last Post: 04-14-2008, 05:39 PM
  5. Bootsplash,lilo.conf & /boot/vmlinuz problems
    By Krailon in forum OLD Newbie Area
    Replies: 14
    Last Post: 01-31-2008, 02:36 PM

Tags for this Thread

Posting Permissions

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