<---- template headericclude ----->
Upgrade F9 -> F10 - unable to boot - bad initrd
FedoraForum.org - Fedora Support Forums and Community
Results 1 to 5 of 5
  1. #1
    Malbrouck Guest

    Upgrade F9 -> F10 - unable to boot - bad initrd

    Hello everybody,


    It's become a tradition since I've installed FC6 on my machine: after each Fedora upgrade, the PC hangs at reboot because of a badly make initrd !

    I found this post a while ago that helped me to solve the problem by rebuilding the initrd with the right librairies in it: http://www.nabble.com/a-Thanksgiving...d13901156.html
    So for each upgrade I've done the last 2 years I had to follow again these instructions to rebuild the initrd.

    I've just finished the upgrade from F9 to F10 and I faced the following friendly message:

    Code:
    acpiphp_glue: failed to register interrupt notify handler
    /bin/nash: error while loading shared libraries: libm.so.6: cannot open shared object file: No such file or directory
    Kernel panic - not syncing: attempted to kill init!
    Allright, not a surprise in fact. While rebuilding the initrd I discovered there's no more /lib/i686/nosegneg/ directory in Fedora10's initrd.
    Therefore I reinstalled the libm-2.9.so library as follows:

    Code:
    cd /tmp/myinitrd/lib/
    cp /lib/libm-2.9.so .
    ln -s /lib/libm-2.9.so libm.so.6
    Once the initrd rebuilt, I rebooted and faced a second friendly message:

    Code:
    acpiphp_glue: failed to register interrupt notify handler
    init[1]: segfault at 0 ip 00000000 sp bf9ed71c error 4 in ld-2.9.so[110000+20000]
    Kernel panic - not syncing: attempted to kill init!
    I searched for posts reporting problems with segfault in ld-2.9.so but didn't find anything. So now I'm with a successfully upgraded fedora 10 system that refuses to boot.

    By the way, I've done the upgrade using the netinstall CD, all the packages have been retreived online without errors and I think I've therefore the latest versions.


    Do you have any idea or suggestion to help me making this F10 box to start ?

    Thanks.

  2. #2
    Seve's Avatar
    Seve is offline Retired Community Manager
    Join Date
    Oct 2004
    Location
    The GTA, Ontario, Canada
    Age
    65
    Posts
    12,371
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Hello:

    Have you tried making a new initrd with mkinitrd for the default F10 kernel ?

    Seve
    Registered Linux User: #384977
    .................................................. ............
    See the Links below for more Help and those much wanted extras ... :)


  3. #3
    Malbrouck Guest
    Hi Seve,


    I tried to make a new initrd but not with the default F10 kernel I guess.

    The netinstall CD took the kernel version 2.6.27.9-159.fc10.i686. The new initrd is 100Ko bigger than the initial one. It may hold more modules/librairies which isn't a so bad thing.

    Then, as the message acpiphp_glue failed was worrying me, I tried the famous "acpi=off" kernel option at boot time. I got the following messages at boot time:

    Code:
    cpufreq: change to state 1 failed with new_state 0 and status 2
    init[1]: segfault at 0 ip 00000000 sp bfac2fec error 4 in ld-2.9.so[110000+20000]
    Kernel panic - not syncing: attempted to kill init!
    So at least the first line changed... :-(

    Do you think using the original kernel (and initrd rebuilt by mkinitrd using this original kernel drivers) might help, Seve ?


    I'm still unable to boot my F10 box. Any help is more than welcomed.

    Unfortunately if I can't start my system in the next 8 hours I'll have to roll-back and restore the / partition. Then I'll have no other choice than starting to move to another Linux distribution like CentOS or so...

  4. #4
    Seve's Avatar
    Seve is offline Retired Community Manager
    Join Date
    Oct 2004
    Location
    The GTA, Ontario, Canada
    Age
    65
    Posts
    12,371
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Hello:
    At this point you have very little to lose from what I can see?

    mkinitrd -f /boot/2.6.27.9-159.fc10.i686.img 2.6.27.9-159.fc10.i686

    or since you can boot fine, then download a different kernel
    http://mirrors.kernel.org/fedora/rel...6/os/Packages/
    Which you will have to force to be installed as it is older than the kernel you currently have and see if you can successfully boot from that?

    Seve
    Registered Linux User: #384977
    .................................................. ............
    See the Links below for more Help and those much wanted extras ... :)


  5. #5
    Malbrouck Guest
    Hi Seve,

    I've downgraded my machine back to Fedora9. I restored my / and /var/ partitions (previously backuped using partimage) and it started allright.

    Now I think I'm going to sleep, the last 2 days have been terrible because of this failed F10 upgrade. I think I'll move my system to CentOS or so... I need to find a linux distribution that fully supports system upgrade.


    Thank you for your support.

    Cheers,
    Malbrouck.

Similar Threads

  1. Unable to acquire IP address at boot after upgrade to Fedora 9
    By openSauce in forum Servers & Networking
    Replies: 0
    Last Post: 5th October 2008, 11:46 AM
  2. FC9 unable to boot after upgrade ("VolGroup00" not found)
    By mina86 in forum Installation, Upgrades and Live Media
    Replies: 20
    Last Post: 22nd July 2008, 06:53 PM
  3. chroot'ed mkinitrd after yum upgrade builds nonfunctional initrd
    By DonWaugaman in forum Installation, Upgrades and Live Media
    Replies: 1
    Last Post: 16th January 2007, 02:38 PM
  4. Boot to initrd.img/vmlinuz under Windows Boot Loader
    By Guess_Who in forum Installation, Upgrades and Live Media
    Replies: 0
    Last Post: 22nd June 2006, 01:15 AM

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
  •  
[[template footer(Guest)]]