Find the answer to your Linux question:
Results 1 to 3 of 3
Let me explain: I installed Ubuntu 8.10 on this here Toshiba Satellite PRO L300 Laptop, 1.86Ghz dual core CPU, 1 GB RAM... lots of hard drive space. It all worked ...
  1. #1
    Just Joined!
    Join Date
    Sep 2008
    Posts
    38

    Stuck at BusyBox after a kernel reconfigure and migration to EXT4...?

    Let me explain:

    I installed Ubuntu 8.10 on this here Toshiba Satellite PRO L300 Laptop, 1.86Ghz dual core CPU, 1 GB RAM... lots of hard drive space.

    It all worked fine until I decided to reconfigure my Linux Kernel (and upgrade to the latest 2.6.28 kernel instead of the .27 one.) I also migrated to EXT4 using a very simple guide and that worked fine.

    I think somehow, I messed something up though. I think it might have something to do with their being so many different kernel sources in the /usr/src and /usr/src/linux folders from various attempts at configuring the kernel so that it is 'just right.'

    Normally, I have never had any problems configuring the kernel, but this is different. I used this thread Master Kernel Thread - Ubuntu Forums

    And it did bring up a couple errors after I did cd .. && dpkg -i linux*2.6.28*.deb, but I do not remember what it said.

    Anyhow, when I try to load the latest kernel I have, it goes to BusyBox and says

    Loading, please wait...
    Gave up waiting for root device. Common problems:
    - Boot Args (cat /proc/cmdline)
    - Check rootdelay= (did the system wait long enough?)
    - Check root= (did the system wait for the right device?)
    - Missing modules (cat /proc/modules; ls /dev)
    ALERT! /dev/disk/by-uuid/5ba5e6e9-b227-4a41-be06-e0ea9e550531 does not exist. Dropping to a shell!

    BusyBox v1.10.2 (Ubuntu...... blah blah blah.


    Also, I am able to chroot into my system from a LIVE CD...

    Any help would be appreciated.

  2. #2
    Linux Guru Jonathan183's Avatar
    Join Date
    Oct 2007
    Posts
    2,941
    Have you checked uuid for partitions match entries in /etc/fstab and /boot/grub/menu.lst ...
    Code:
    ls /dev/disk/by-uuid -l

  3. #3
    Just Joined!
    Join Date
    Apr 2009
    Posts
    1
    I did something similar, but was able to fix it.
    (btw /dev/disk doesn't exist in this case.)

    boot up a livecd of jaunty,
    mount your root device,
    chroot to your root device
    mount proc
    recreate initramfs
    reboot

    applications.. accessories.. terminal..
    sudo su -
    mkdir /mnt/sda1
    mount /dev/sda1 /mnt/sda1
    chroot /mnt/sda1
    mount /proc
    update-initramfs -u
    reboot

Posting Permissions

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