Busybox/Initramfs prevents launch of Ubuntu Server 8.04.3
Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Busybox/Initramfs prevents launch of Ubuntu Server 8.04.3
Hi, Prior to posting this I entered search arguments, "Busybox," then "initramfs" to attempt to find another user who may have experienced the same thing; if the solution is imbedded in the message threads, I must have missed it.
Thank you for letting me join the LinuxQuestions.org web site.
On hand is a Ubuntu Server 8.04.3 installer CD.
What works: Installs to a Mac Pro under both Parallels, and then under Fusion both were successful first try.
The problem:
Install to a newly purchased 2 gig Acer Aspire One seems to have succeeded, but upon launching from Grub, Busybox/initramfs intercepts and halts the launch with an error I don't understand:
Starting up ...
Loading, please wait ...
Check root = bootary cat /proc/cmdline
or missing modules, devices: cat /proc/modules 1s /dev
ALERT! /dev/disk/by-uuid/1258703c-d29c-4bda-9d42-fa696e28bd82 does not exist. Dropping to a shell!
Busybox v1.1.3 (Debian 1:1.1.3-5ubuntu12) Built-in shell (ash)
Enter 'help' for a list of built-in commands.
(initramfs)
In this condition, "help" under Busybox/initramfs provides a list of commands; I have no idea which command would cause the boot to proceed, so I tried "exit." Results were:
(initramfs) exit
Check root= bootarg cat /proc/cmdline
or missing modules, devices: cat /proc/modules 1s /dev
ALERT! /dev/disk/by-uuid/1258703c-d29c-4bda-9d42-fa696e28bd82 does not exist. Dropping to a shell!
The new Acer-PC Aspire One was partitioned into four 80 gig partitions using the Paragon software to do the partitioning. XP is on the first, and Ubuntu Server on the next 80 gig partition. Install was "successfully" done from a Lite-On external CD/DVD over USB.
During the install I changed the default name from Ubuntu to something else (probably a bad idea), and I naively entered "/" root to answer the mount question (finding nothing to tell me what to do).
Ubuntu required a disk driver choice from a long list - finding no reference or guidance as to what to enter, I naively entered IDE Generic, and it took (I guess it "took").
FWIW the Ubuntu installer didn't require me to indentify the mount entry or the disk driver during installs on my Mac (Fusion/Parallels).
I did connect the Internet during the install. I did checkoff/install LAMP during the install from CD.
Goal: To use Joomla in a mock server environment.
I look forward to your guidance, and thank you for taking time to read through all this.
Ubuntu required a disk driver choice from a long list...
This means the installer could not find an existing driver to match the hardware that it found. You may be able to get around this by trying a later version of Ubuntu (e.g. 8.10 or 9.04).
If you want more detailed help, download the latest System Rescue CD and boot from that. That should have a really recent kernel, which should have support for your hardware. When you get to a command line, run "lspci" and "lspci -n" and see what it reports as your disk drive interface. Also, if it recognized your disk drive interface, you should be able to see what driver was loaded by running "lsmod".
(do NOT change the root=UUID bit as yours will be different from above (as it's the drive's id))
then save the file.
__________________
Regards
Problem partially solved; I can now make Ubuntu Server work, if I edit the GRUB each time I boot into it. Attempting to edit the menu.1st file is tough so far, 'cause I don't know what i'm doing.
I get into the boot directory and type gedit /boot/grub/menu.1st
and ubuntu returns this error: "The program 'gedit' is currently not installed. To run 'gedit' please ask your administrator to install the package 'gedit'
-bash: gedit: command not found"
OK, I need to suffer embarrassment 'cause I am the administrator.
Any ideas on how to obtain gedit, and how to put it where it belongs?
Problems with Busybox/initramfs are massive, affecting users who are trying to install from CD, and users who are trying to run Ubuntu; the message thread is up to 40 pages over on the Ubuntu website.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.