Ubuntu Installation Summary

The ultimate solution that busybox cannot be installed on Ubuntu

After Ubuntu is installed from the CD (the official CD), the following message is displayed: busybox v1.1.3 (Debian. 1.3-5ubuntu7) built-in Shell (Ash) Enter 'help' for a list of built-in commands. (initramfs) The solution is as follows: After the installation interface is displayed on the CD, select the installation language, move the keyboard down to the line of installation (I), and then press the F6 option, You can see a string of parameter lines below, and change quiet to all_generic_ide and press enter to install it normally, It is also feasible to add all_generic_idefloppy = off irqpoll at the end. After the installation and restart, the busybox prompt screen may still be displayed. The solution is similar to the previous startup Item :---------------------- 1 Ubuntu 8.04kernl.2.6.22-16-generic 2 Ubuntu 8.04kernl.2.6.22-16-generic (creovery. Mode) 3 ubuntu.8.04 memtes86 + 4 other operating systems ---------------------- Select the above 1st "ubuntu 8.04kernl.2.6.22-16-generic" and press e to enter the editing status :---------------------- 1 root (hd0, 4) 2 kernel/boot/vmlinuz-2.6.22-16-generic root = UUID = _ Ro quiet splash3 initrd/boot/initrd. img-2.6.22-16-generic4 quiet ---------------------- Select item 2nd "kernel/boot/vmlinuz-2.6.22-16-generic root = UUID = _ Ro quiet Splash" and press e to enter the editing status. Replace quiet splash with all_generic_ide as follows: ---------------------- Kernel/boot/vmlinuz-2.6.22-16-generic root = UUID = _ all_generic_ide ---------------------- Press enter to confirm the modification, and then press B to start the desktop. Modify the/boot/GRUB/menu. LST file immediately, find the kernel line, and delete quiet splash and add all_generic_ide. This problem is completely solved. ------------------------------------------------------------------------- After ubuntu8.10, busybox is enabled When I started Ubuntu 8.10, the damn Ubuntu busybox appeared again. I have encountered this problem several times before, but it only appeared when I installed Ubuntu 8.04. I wanted to upgrade it to Ubuntu 8.10. The problem should be solved officially. I didn't expect it to still exist. In the long run, it was not good. It severely cracked down on the enthusiasm of cainiao for using Ubuntu, which is quite unfavorable for promoting ubuntu. But why didn't it attract official attention? If I put it in the past, I may try to reinstall Ubuntu 8.10 to solve the problem. But now that I have encountered a problem, I have to come up with a solution to solve it. Today, by chance, I successfully wiped out this annoying busybox and made it no longer busy. In fact, to solve the problem that busybox cannot enter the system when Ubuntu is started, the method is very simple, just a few simple steps are OK. The procedure is as follows: 1. When Ubuntu is started, "press 'esc 'to enter the menu..." appears ......" Then, Press ESC to go To the Startup menu and select Ubuntu 8.10, kernel 2.6.27-7-generic (recovery mode) to repair the system mode. 2. After more than a dozen seconds, a dialog box "recovery menu" will appear. The general content is as follows: Resume resume normal boot Clean try to make free space Dpkg repair broken packages Fsck File System check Root drop to root shell prompt Xfix try to fix X Server (repair cannot enter image window mode) 3. Select the first item to fix startup faults caused by various reasons. OK, then you will be surprised to find that you have entered the familiar Ubuntu interface. Prove that the effort was not in vain. 4. restart the system to verify that the judgment is correct. Okay. You can use Ubuntu 8.10 without busybox. It turned out that ubuntu was still aware of the busybox issue. Currently, the recovery mode of ubuntu 8.10 is no longer a weakness and can finally be used, rather than the reinstallation mode of previous versions. In this regard, I took back my remarks at the beginning of the article. Original Web site: http://www.hongmop.cn/article.asp? Id = 260

 

 

Grub failure during startup:

1. Start with live CD
2. Open a terminal and run $ sudo grub. You will see a prompt like 'grub> '.
3. enter find/boot/GRUB/stage1 at the prompt, and you will get a running result. For example, the result on my machine is (hd0, 5) (This command is actually used to find the partition where/boot is located)
4. Run grub> root (hd0, 5) (enter the running result on your machine)
5. Run grub> setup (hd0). A few lines of text are displayed, and "... succeeded" is fixed successfully!
6. Run quit
7. restart the computer and retrieve the live CD.
Hd0 refers to the first hard disk (no serial port SATA or parallel port pata). X is the Partition Number of the Linux main directory "/". The serial number starts from 0, 1 is smaller than the partition number displayed in Linux. For example, if the hard disk partition number is hda5 in Linux, X is 4. The partition number can be used in the menu. If you do not know the number of disks, try it one by one. When grub prompts that the partition format is ex2fs. Note that root (hd0, x) must have spaces behind root. The root command specifies the boot partition, And the setup command writes the boot information to the hard disk MBR.

 

The machine is Lenovo m8000t, so I suspect it is the cause of hardware. I asked 800, but it was fruitless. I checked a successful online case that I entered the bios and set the SATA ahci mode to enabled. After saving, ah ~~ Since then, the grub error 25 problem that has plagued me for many years has been completely solved.

 

 

Deleting Linux and restoring grub are two common problems for new users. If I feel that Linux is not good and want to quit, I need to delete Linux and overwrite grub. If I have installed Windows and Linux, grub will be overwritten when Windows is reinstalled, and grub needs to be restored. This is a back path. We need to consider it before doing things.

Delete Linux, overwrite grub, and restore it to the boot guide of XP. This is very simple, as long as you have a Windows XP disk (not a ghost), use it to start it, exit and restart from the installation location. You can also use it to start the fault recovery platform and run fixboot or fixmbr.

To restore grub, you can use live CD (desktop CD or DVD for Ubuntu) to start the terminal (Applications> accessory> terminal) and run the following code: code:
Sudo grub
Find/boot/GRUB/stage1
Root (hdx, Y)
Setup (hdx)
Quit

Note: X and Y are prompted after the find/boot/GRUB/stage1 command is executed. For example: code:
Grub> Find/boot/GRUB/menu. lst
(Hd0, 7)

Note: grub> here is the prompt obtained after executing the sudo grub command and entering the grub environment. You do not need to enter it. In this case, X is 0, and Y is 7.

The following commands are explained in detail:

Sudo grub starts GRUB as the root user. Otherwise, an error occurs. For the error, see the following figure.
Find/boot/GRUB/stage1 find the partition where/boot is located. In fact, the same applies to find/boot/GRUB/menu. lst.
This step can also be skipped. When executing root (hdx, you can press two tabs to list available partitions and determine which partition is used.
If/boot is partitioned separately, see the description.
Root (hdx, Y) sets the root file system (root device) of hdx on the hard disk, which is actually the partition where/boot is located.
Setup (hdx) automatically installs grub to hdx.
Quit exits grub

There are spaces after the root and Setup Commands. If there is no space, an error will occur.
What kind of error will occur if the root user is not used? Reference:
Ubuntu @ Ubuntu :~ $ Grub

[Minimal bash-like line editing is supported.
The first word, tab lists possible command
Completions. Anywhere else tab lists the possible
Completions of a device/filename.]

Grub> Find/boot/GRUB/stage1

Error 15: file not found

Grub> Find/boot/GRUB/menu. lst

Error 15: file not found

Grub> root (hd0, 7)

Error 27: Unrecognized command

Grub> root (hd0, 7)

Error 21: Selected disk does not exist
Grub> setup (hd0)

Error 12: Invalid device requested

A successful example: Reference:
Ubuntu @ Ubuntu :~ $ Sudo grub
[Minimal bash-like line editing is supported.
The first word, tab lists possible command
Completions. Anywhere else tab lists the possible
Completions of a device/filename.]

Grub> Find/boot/GRUB/menu. lst
(Hd0, 7)

Grub> root (hd0, 7)

Grub> setup (hd0)
Checking if "/boot/GRUB/stage1" exists... Yes
Checking if "/boot/GRUB/stage2" exists... Yes
Checking if "/boot/GRUB/e2fs_stage1_5" exists... Yes
Running "embed/boot/GRUB/e2fs_stage1_5 (hd0 )"... 15 sectors are embedded.
Succeeded
Running "Install/boot/GRUB/stage1 (hd0) (hd0) 1 + 15 p (hd0, 7)/boot/GRUB/stage2/boot/GRUB/menu. lst "... Succeeded
Done.
Grub> quit

This is the simplest method, and there are several other methods to find/boot partitions, but it is a little troublesome:
Use the LS/dev/SD * and LS/HD * commands on the terminal to find the system's external settings, use the sudo mkdir command to create a mount directory, and use the sudo mount command to mount the directory, run the LS command to check whether/boot is in the partition.

You can also use sudo fdisk-L to locate the boot partition (this does not involve the case where/boot is partitioned separately, because I have not tried it and it is not clear), such as reference:
Ubuntu @ Ubuntu :~ $ Sudo fdisk-l

Disk/dev/SDA: 160.0 GB, 160041885696 bytes
255 heads, 63 sectors/track, 19457 Cylinders
Units = cylinders of 16065*512 = 8225280 bytes

Device boot start end blocks ID system
/Dev/sda1*1 2295 18434556 7 HPFs/NTFS
/Dev/sda2 2296 19456 137845732 + F w95 ext 'd (LBA)
/Dev/sda5 2296 4845 20482843 + 7 HPFs/NTFS
/Dev/sda6 4846 8669 30716248 + 7 HPFs/NTFS
/Dev/sda7 8670 16557 63360328 + 7 HPFs/NTFS
/Dev/sda8*16558 17361 6458098 + 83 Linux
/Dev/sda9 17362 19393 16322008 + 83 Linux
/Dev/sda10 19394 19456 506016 82 Linux swap/Solaris

The START partition is/dev/sda8.

Some people may have doubts that in Linux, sda8 is used to represent the startup partition, while grub is represented by (hd0, 7, this is because in the new Ubuntu system, both the serial and parallel hard disks are identified as SD. A indicates the first hard disk, and 8 indicates the first logical partition (1-4 is allocated to the primary partition, the logical partitions in the extended partition are calculated from 5 ). In grub, HD is used to represent the hard disk. Both the hard disk number and partition number are calculated from 0.
This part is written based on memory and may be inaccurate. For details, refer to Wikipedia.

PS:
I have seen some posts saying that alterate CD can input Linux rescue after boot to start the rescue disk, and the subsequent operations are the same. I cannot verify because I have no alterate cd at hand. Although the alterate CD and desktop cd are integrated with the DVD, the rescue disk cannot be started when it is installed on the Character interface.

In addition, all the items under/boot are in good condition, but if RP fails and/boot is finished, try again:
Generate the/etc/mtab code:
Sudo grep-V rootfs/proc/mounts> sudo tee/etc/mtab

Install grub to MBR code:
Grub-install-no-floppy/dev/hda

Then we can fix menu. LST by ourselves.