PDA

View Full Version : Ubuntu 11.10 BusyBox on boot.



vks.itbhu
December 4th, 2011, 04:38 PM
having same problem. in the morning i forced shutdown my ubuntu 11.10 and when i tried booting, it's showing grub menu in which if i select any option it comes to initramfs, busybox black screen. i am just using ubuntu from the last 15 days and have no idea how to solve this issue. I am attaching my result.txt file which i got from running boot info script. Also since this is my first post here if i am missing something i m sorry for that


# Boot Info Script 0.60 from 17 May 2011


============================= Boot Info Summary: ===============================

=> Windows is installed in the MBR of /dev/sda.
=> Syslinux MBR (4.04 and higher) is installed in the MBR of /dev/sdb.

sda1: __________________________________________________ ________________________

File system: ext4
Boot sector type: Grub2 (v1.99)
Boot sector info: Grub2 (v1.99) is installed in the boot sector of sda1
and looks at sector 8656896 of the same hard drive for
core.img. core.img is at this location and looks for
on this drive.
Operating System:
Boot files: /grub/grub.cfg /grub/core.img

sda2: __________________________________________________ ________________________

File system: swap
Boot sector type: -
Boot sector info:

sda3: __________________________________________________ ________________________

File system: ext4
Boot sector type: -
Boot sector info:
Mounting failed: mount: wrong fs type, bad option, bad superblock on /dev/sda3,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so


sdb1: __________________________________________________ ________________________

File system: vfat
Boot sector type: SYSLINUX 4.04 2011-04-18
Boot sector info: Syslinux looks at sector 30470 of /dev/sdb1 for its
second stage. SYSLINUX is installed in the directory.
The integrity check of the ADV area failed. No errors
found in the Boot Parameter Block.
Operating System:
Boot files: /syslinux/syslinux.cfg /ldlinux.sys

============================ Drive/Partition Info: =============================

Drive: sda __________________________________________________ ___________________

Disk /dev/sda: 250.1 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders, total 488397168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes

Partition Boot Start Sector End Sector # of Sectors Id System

/dev/sda1 * 2,048 58,710,015 58,707,968 83 Linux
/dev/sda2 58,710,016 62,615,551 3,905,536 82 Linux swap / Solaris
/dev/sda3 62,615,552 488,396,799 425,781,248 83 Linux


Drive: sdb __________________________________________________ ___________________

Disk /dev/sdb: 4004 MB, 4004511744 bytes
255 heads, 63 sectors/track, 486 cylinders, total 7821312 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes

Partition Boot Start Sector End Sector # of Sectors Id System

/dev/sdb1 * 128 7,821,311 7,821,184 c W95 FAT32 (LBA)


"blkid" output: __________________________________________________ ______________

Device UUID TYPE LABEL

/dev/loop0 squashfs
/dev/sda1 0e2f79e2-5c0c-46ab-857c-5b146fc8599f ext4
/dev/sda2 bf1a4521-4e1f-48f7-96be-1a9a086de083 swap
/dev/sda3 30876ceb-4a67-4a1d-b544-e47a0b375867 ext4
/dev/sdb1 160B-3F5F vfat PENDRIVE

================================ Mount points: =================================

Device Mount_Point Type Options

/dev/loop0 /rofs squashfs (ro,noatime)
/dev/sdb1 /cdrom vfat (rw,relatime,fmask=0022,dmask=0022,codepage=cp437, iocharset=iso8859-1,shortname=mixed,errors=remount-ro)


============================= sda1/grub/grub.cfg: ==============================

--------------------------------------------------------------------------------
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#

### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
set have_grubenv=true
load_env
fi
set default="0"
if [ "${prev_saved_entry}" ]; then
set saved_entry="${prev_saved_entry}"
save_env saved_entry
set prev_saved_entry=
save_env prev_saved_entry
set boot_once=true
fi

function savedefault {
if [ -z "${boot_once}" ]; then
saved_entry="${chosen}"
save_env saved_entry
fi
}

function recordfail {
set recordfail=1
if [ -n "${have_grubenv}" ]; then if [ -z "${boot_once}" ]; then save_env recordfail; fi; fi
}

function load_video {
insmod vbe
insmod vga
insmod video_bochs
insmod video_cirrus
}

insmod part_msdos
insmod ext2
set root='(hd0,msdos3)'
search --no-floppy --fs-uuid --set=root 30876ceb-4a67-4a1d-b544-e47a0b375867
if loadfont /usr/share/grub/unicode.pf2 ; then
set gfxmode=auto
load_video
insmod gfxterm
insmod part_msdos
insmod ext2
set root='(hd0,msdos1)'
search --no-floppy --fs-uuid --set=root 0e2f79e2-5c0c-46ab-857c-5b146fc8599f
set locale_dir=($root)/grub/locale
set lang=en_IN
insmod gettext
fi
terminal_output gfxterm
if [ "${recordfail}" = 1 ]; then
set timeout=-1
else
set timeout=10
fi
### END /etc/grub.d/00_header ###

### BEGIN /etc/grub.d/05_debian_theme ###
set menu_color_normal=white/black
set menu_color_highlight=black/light-gray
if background_color 44,0,30; then
clear
fi
### END /etc/grub.d/05_debian_theme ###

### BEGIN /etc/grub.d/10_linux ###
if [ ${recordfail} != 1 ]; then
if [ -e ${prefix}/gfxblacklist.txt ]; then
if hwmatch ${prefix}/gfxblacklist.txt 3; then
if [ ${match} = 0 ]; then
set linux_gfx_mode=keep
else
set linux_gfx_mode=text
fi
else
set linux_gfx_mode=text
fi
else
set linux_gfx_mode=keep
fi
else
set linux_gfx_mode=text
fi
export linux_gfx_mode
if [ "$linux_gfx_mode" != "text" ]; then load_video; fi
menuentry 'Ubuntu, with Linux 3.0.0-13-generic' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
set gfxpayload=$linux_gfx_mode
insmod gzio
insmod part_msdos
insmod ext2
set root='(hd0,msdos1)'
search --no-floppy --fs-uuid --set=root 0e2f79e2-5c0c-46ab-857c-5b146fc8599f
linux /vmlinuz-3.0.0-13-generic root=UUID=30876ceb-4a67-4a1d-b544-e47a0b375867 ro quiet splash vt.handoff=7
initrd /initrd.img-3.0.0-13-generic
}
menuentry 'Ubuntu, with Linux 3.0.0-13-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
insmod gzio
insmod part_msdos
insmod ext2
set root='(hd0,msdos1)'
search --no-floppy --fs-uuid --set=root 0e2f79e2-5c0c-46ab-857c-5b146fc8599f
echo 'Loading Linux 3.0.0-13-generic ...'
linux /vmlinuz-3.0.0-13-generic root=UUID=30876ceb-4a67-4a1d-b544-e47a0b375867 ro recovery nomodeset
echo 'Loading initial ramdisk ...'
initrd /initrd.img-3.0.0-13-generic
}
submenu "Previous Linux versions" {
menuentry 'Ubuntu, with Linux 3.0.0-12-generic' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
set gfxpayload=$linux_gfx_mode
insmod gzio
insmod part_msdos
insmod ext2
set root='(hd0,msdos1)'
search --no-floppy --fs-uuid --set=root 0e2f79e2-5c0c-46ab-857c-5b146fc8599f
linux /vmlinuz-3.0.0-12-generic root=UUID=30876ceb-4a67-4a1d-b544-e47a0b375867 ro quiet splash vt.handoff=7
initrd /initrd.img-3.0.0-12-generic
}
menuentry 'Ubuntu, with Linux 3.0.0-12-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
insmod gzio
insmod part_msdos
insmod ext2
set root='(hd0,msdos1)'
search --no-floppy --fs-uuid --set=root 0e2f79e2-5c0c-46ab-857c-5b146fc8599f
echo 'Loading Linux 3.0.0-12-generic ...'
linux /vmlinuz-3.0.0-12-generic root=UUID=30876ceb-4a67-4a1d-b544-e47a0b375867 ro recovery nomodeset
echo 'Loading initial ramdisk ...'
initrd /initrd.img-3.0.0-12-generic
}
}
### END /etc/grub.d/10_linux ###

### BEGIN /etc/grub.d/20_linux_xen ###
### END /etc/grub.d/20_linux_xen ###

### BEGIN /etc/grub.d/20_memtest86+ ###
menuentry "Memory test (memtest86+)" {
insmod part_msdos
insmod ext2
set root='(hd0,msdos1)'
search --no-floppy --fs-uuid --set=root 0e2f79e2-5c0c-46ab-857c-5b146fc8599f
linux16 /memtest86+.bin
}
menuentry "Memory test (memtest86+, serial console 115200)" {
insmod part_msdos
insmod ext2
set root='(hd0,msdos1)'
search --no-floppy --fs-uuid --set=root 0e2f79e2-5c0c-46ab-857c-5b146fc8599f
linux16 /memtest86+.bin console=ttyS0,115200n8
}
### END /etc/grub.d/20_memtest86+ ###

### BEGIN /etc/grub.d/30_os-prober ###
if [ "x${timeout}" != "x-1" ]; then
if keystatus; then
if keystatus --shift; then
set timeout=-1
else
set timeout=0
fi
else
if sleep --interruptible 3 ; then
set timeout=0
fi
fi
fi
### END /etc/grub.d/30_os-prober ###

### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.
### END /etc/grub.d/40_custom ###

### BEGIN /etc/grub.d/41_custom ###
if [ -f $prefix/custom.cfg ]; then
source $prefix/custom.cfg;
fi
### END /etc/grub.d/41_custom ###
--------------------------------------------------------------------------------

=================== sda1: Location of files loaded by Grub: ====================

GiB - GB File Fragment(s)

= grub/core.img 1
= grub/grub.cfg 1
= initrd.img-3.0.0-12-generic 1
= initrd.img-3.0.0-13-generic 1
= vmlinuz-3.0.0-12-generic 1
= vmlinuz-3.0.0-13-generic 1

========================= sdb1/syslinux/syslinux.cfg: ==========================

--------------------------------------------------------------------------------
# D-I config version 2.0
include menu.cfg
default vesamenu.c32
prompt 0
timeout 50

# If you would like to use the new menu and be presented with the option to install or run from USB at startup, remove # from the following line. This line was commented out (by request of many) to allow the old menu to be presented and to enable booting straight into the Live Environment!
# ui gfxboot bootlogo
--------------------------------------------------------------------------------

================= sdb1: Location of files loaded by Syslinux: ==================

GiB - GB File Fragment(s)

?? = ?? ldlinux.sys 1
?? = ?? syslinux/chain.c32 1
?? = ?? syslinux/gfxboot.c32 1
?? = ?? syslinux/syslinux.cfg 1
?? = ?? syslinux/vesamenu.c32 1

============== sdb1: Version of COM32(R) files used by Syslinux: ===============

syslinux/chain.c32 : COM32R module (v4.xx)
syslinux/gfxboot.c32 : COM32R module (v4.xx)
syslinux/vesamenu.c32 : COM32R module (v4.xx)

=============================== StdErr Messages: ===============================

unlzma: Decoder error
awk: cmd. line:36: Math support is not compiled in
awk: cmd. line:36: Math support is not compiled in
awk: cmd. line:36: Math support is not compiled in
awk: cmd. line:36: Math support is not compiled in
awk: cmd. line:36: Math support is not compiled in
awk: cmd. line:36: Math support is not compiled in
/home/ubuntu/Downloads/boot_info_script.sh: line 1579: [: 2.73495e+09: integer expression expected
#

drs305
December 4th, 2011, 05:59 PM
vks.itbhu,

Welcome to the Ubuntu Forums.

I've moved your post to it's own thread. You are using a different release than the OP, and it's best to keep problems separate when possible.

Also you'll note I've changed the formatting by adding "code" tags. You generate them by highlighting the output while creating the post and pressing the # icon in the post's menubar.

As to your problem...

You have two issues here:

1. It appears you had Windows on this machine at one point as it's still in the sda MBR. You installed Grub to the sda1 partition. This is not normally a good idea, as it can break as files are moved around.

To get the sda to point to your Ubuntu installation, boot a 11.10 LiveCD, mount the Ubuntu partition (sda1) and then install Grub. Do NOT use the partition number in the install command.


sudo mount /dev/sda1 /mnt
sudo grub-install --boot-directory=/mnt/boot /dev/sda


2. The boot info script did not find an fstab file. This file must exist in the /etc/ folder. It also may indicate other important system files are missing. While the terminal above it still open, use Nautilus to look in /etc and see if an fstab file or backup exists:

gksu nautilus /mnt/etc/
If you find the file, you can try to boot and see if it works. However, there is a reason the boot info script didn't report it so the boot will probably fail.

If you find a fstab backup but not an fstab file in /mnt/etc, rename the fstab backup to fstab and try booting.

Reboot, making sure the BIOS is booting your sda/Ubuntu drive first.

vks.itbhu
December 4th, 2011, 08:30 PM
thanx for answering drs but still i m not able to get to know how i can fix this, i am pasting here the output which i got from the terminal while using ubuntu from live usb.


sudo grub-install --boot-directory=/mnt/boot /dev/sda1
sudo: grub-install: command not found

gksu nautilas /mnt/etc

(gksu:7095): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",


plzz help...

drs305
December 4th, 2011, 09:08 PM
This error message means that a needed package is missing. You can install it with the following command:


sudo apt-get install gtk2-engines-pixbuf

vks.itbhu
December 7th, 2011, 10:19 AM
thanx for help drs ...... i formatted my laptop again as it was really frustating after some time trying to find out how to fix that issue.
but really thanx for your help. Is there any book or website you would like to suggest me so that in future i am able to solve this type of problem by myself....
thanx for ur help..

drs305
December 7th, 2011, 03:30 PM
thanx for help drs ...... i formatted my laptop again as it was really frustating after some time trying to find out how to fix that issue.
but really thanx for your help. Is there any book or website you would like to suggest me so that in future i am able to solve this type of problem by myself....
thanx for ur help..

It can be hard to identify the cause of a busybox error.

I am self-taught when it comes to Ubuntu/Linux, as are many on this forum. The way I learned was by necessity. When I had a problem, I came onto the forums or the Internet in general and searched for the answers. The good thing is I can learn about things that affect me. The bad is that it leaves very large gaps in my knowledge about Ubuntu/Linux which limits my ability to help others. If I personally haven't had a problem with an issue, or don't use it (RAID, etc), I still haven't learned about it.

One thing that helps is searching for the exact error message if one is displayed in a terminal. If it's a GUI app, launching it via a terminal command may display the error message.

I don't have a general reference book I refer to. For someone who has never used Linux the following is a good introduction, although it probably needs a little updating. It isn't good for troubleshooting but gives a good overview of Ubuntu and how it operates. Free PDF:
http://www.ubuntupocketguide.com/index_main.html

For specific Ubuntu searches:
https://help.ubuntu.com/community

http://askubuntu.com/
There is a tiny 'search' box at the upper right.

Or just include "Ubuntu" in the Internet search terms.

Part of the enjoyment of Ubuntu for me is that there are always new things to learn about and explore.

Happy Ubuntu-ing !