PDA

View Full Version : [ubuntu] Ubuntu won't boot after installation



kbutcher5
May 21st, 2011, 07:04 PM
So I installed Ubuntu server x86 on a via box with a cf card.
At the grub menu, if I choose the regular bootup I get a black screen and 2-3 seconds later a reboot, if I choose recovery it says loading kernel then loading ramdisk and then a reboot.

So basically no matter what I do, I am in an endless hell of reboots. I tried noacpi to no avail, I even tried to use the recovery CD/USB to check if for some odd reason the disk name should be wrong.

So here is the tricky part, nothing is wrong, except that Ubuntu won't start.

So I come to you to ask if any of you have any good ideas as to what I could do to make the damn thing boot?

For anyone who would want the exact hardware details:
Via Epia SN-18000G with a Kingston CF Elite Pro 133x 16GB

Rubi1200
May 21st, 2011, 08:05 PM
Hi,

please do the following so we can get a better overview of the current state of the system:

Boot the Ubuntu Live CD/USB. Choose the option "Try Ubuntu without any changes." Once the desktop loads come back here and do the following:

1. Download the boot info script. There is a link in my signature.
2. Once downloaded, move the boot info script to the desktop.
3. Open a terminal and run the command


sudo bash ~/Desktop/boot_info_script*.shThis will create a RESULTS.txt file on the desktop. Paste the entire contents of that file back here in a new post. Once pasted highlight all text and click the # sign on the toolbar to place code tags around the text.

kbutcher5
May 21st, 2011, 08:20 PM
There we go:

Boot Info Script 0.60 from 17 May 2011


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

=> Grub2 (v1.99) is installed in the MBR of /dev/sda and looks at sector 1 of
the same hard drive for core.img. core.img is at this location and looks
for ?? on this drive.
=> Syslinux MBR (3.61-4.03) is installed in the MBR of /dev/sdc.

sda1: __________________________________________________ ________________________

File system: ext4
Boot sector type: -
Boot sector info:
Operating System: Ubuntu 11.04
Boot files: /boot/grub/grub.cfg /etc/fstab /boot/grub/core.img

sdc1: __________________________________________________ ________________________

File system: vfat
Boot sector type: SYSLINUX 4.03 2010-10-22 ........>..sr>.......;..:...0...~.....~...f...M.f.f....f..0~....>E}.u......
Boot sector info: Syslinux looks at sector 8200 of /dev/sdc1 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: 16.0 GB, 15988654080 bytes
255 heads, 63 sectors/track, 1943 cylinders, total 31227840 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 * 8,128 31,227,839 31,219,712 83 Linux


Drive: sdc __________________________________________________ ___________________

Disk /dev/sdc: 2021 MB, 2021654528 bytes
255 heads, 63 sectors/track, 245 cylinders, total 3948544 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/sdc1 * 63 3,948,543 3,948,481 b W95 FAT32


"blkid" output: __________________________________________________ ______________

Device UUID TYPE LABEL

/dev/sda1 73199790-dac6-4cc1-93e7-d2bc6a67cf3e ext4
/dev/sdc1 7E32-03C5 vfat PENDRIVE

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

Device Mount_Point Type Options

/dev/sda1 / ext4 (rw,relatime,errors=remount-ro,barrier=1,data=ordered)
/dev/sdb1 /media/cdrom vfat (ro,relatime,fmask=0022,dmask=0022,codepage=cp437, iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
/dev/sdc1 /mnt vfat (rw)


=========================== sda1/boot/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='(/dev/sda,msdos1)'
search --no-floppy --fs-uuid --set=root 73199790-dac6-4cc1-93e7-d2bc6a67cf3e
if loadfont /usr/share/grub/unicode.pf2 ; then
set gfxmode=auto
load_video
insmod gfxterm
fi
terminal_output gfxterm
insmod part_msdos
insmod ext2
set root='(/dev/sda,msdos1)'
search --no-floppy --fs-uuid --set=root 73199790-dac6-4cc1-93e7-d2bc6a67cf3e
set locale_dir=($root)/boot/grub/locale
set lang=en_US
insmod gettext
if [ "${recordfail}" = 1 ]; then
set timeout=-1
else
set timeout=2
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
### 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 2.6.38-8-generic-pae' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
set gfxpayload=$linux_gfx_mode
insmod part_msdos
insmod ext2
set root='(/dev/sda,msdos1)'
search --no-floppy --fs-uuid --set=root 73199790-dac6-4cc1-93e7-d2bc6a67cf3e
linux /boot/vmlinuz-2.6.38-8-generic-pae root=UUID=73199790-dac6-4cc1-93e7-d2bc6a67cf3e ro quiet
initrd /boot/initrd.img-2.6.38-8-generic-pae
}
menuentry 'Ubuntu, with Linux 2.6.38-8-generic-pae (recovery mode)' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
set gfxpayload=$linux_gfx_mode
insmod part_msdos
insmod ext2
set root='(/dev/sda,msdos1)'
search --no-floppy --fs-uuid --set=root 73199790-dac6-4cc1-93e7-d2bc6a67cf3e
echo 'Loading Linux 2.6.38-8-generic-pae ...'
linux /boot/vmlinuz-2.6.38-8-generic-pae root=UUID=73199790-dac6-4cc1-93e7-d2bc6a67cf3e ro single
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-2.6.38-8-generic-pae
}
### 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='(/dev/sda,msdos1)'
search --no-floppy --fs-uuid --set=root 73199790-dac6-4cc1-93e7-d2bc6a67cf3e
linux16 /boot/memtest86+.bin
}
menuentry "Memory test (memtest86+, serial console 115200)" {
insmod part_msdos
insmod ext2
set root='(/dev/sda,msdos1)'
search --no-floppy --fs-uuid --set=root 73199790-dac6-4cc1-93e7-d2bc6a67cf3e
linux16 /boot/memtest86+.bin console=ttyS0,115200n8
}
### END /etc/grub.d/20_memtest86+ ###

### BEGIN /etc/grub.d/30_os-prober ###
### 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/etc/fstab: ================================

--------------------------------------------------------------------------------
# /etc/fstab: static file system information.
#
# Use 'blkid -o value -s UUID' to print the universally unique identifier
# for a device; this may be used with UUID= as a more robust way to name
# devices that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc nodev,noexec,nosuid 0 0
/dev/sda1 / ext4 errors=remount-ro 0 1
--------------------------------------------------------------------------------

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

GiB - GB File Fragment(s)

8.129875183 = 8.729387008 boot/grub/core.img 1
12.309535980 = 13.217263616 boot/grub/grub.cfg 1
12.523605347 = 13.447118848 boot/initrd.img-2.6.38-8-generic-pae 2
12.172271729 = 13.069877248 boot/vmlinuz-2.6.38-8-generic-pae 2
12.523605347 = 13.447118848 initrd.img 2
12.172271729 = 13.069877248 vmlinuz 2

========================= sdc1/syslinux/syslinux.cfg: ==========================

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

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

GiB - GB File Fragment(s)

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

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

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

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

/mnt/boot_info_script.sh: line 1579: [: 2.73495e+09: integer expression expected



As far as I can see, there is nothing "wrong", but that might just be my limited knowledge of how Grub2 works?

In case anyone would want to do this at a later time, and they only have the server dist available, this can also be done by downloading the script and transferring it to the USB pen and then running it through the recovery option in the USB pen menu.

Rubi1200
May 21st, 2011, 08:30 PM
Thanks for the results.

I am a bit confused about the script reporting this:

Grub2 (v1.99) is installed in the MBR of /dev/sda...and looks for ?? on this drive.Usually, it would say partition 1 or mdsos 1, something similar.

Have you tried reinstalling GRUB?

This is what you can do from the live medium:


sudo mount /dev/sda1 /mnt
sudo grub-install --boot-directory=/mnt/boot /dev/sdaReboot and run
sudo update-grub back in Ubuntu.

kbutcher5
May 21st, 2011, 08:54 PM
Yeah, I have tried it three times with the recovery option, and now with the console option you suggested, still no dice.

Could it be a firmware related issue in regards to the CF card?

Rubi1200
May 21st, 2011, 08:59 PM
Hmm, that is odd. To be honest, I don't know enough about your hardware setup to comment accurately on this.

I will ask some other users to take a look and offer their perspectives so please be patient.

Thanks.

kbutcher5
May 21st, 2011, 09:11 PM
Thanks, much appreciated.

drs305
May 21st, 2011, 09:24 PM
I would have thought the grub-install command might have solved the ?? as well, since where it looks is normally embedded in core.img and that is rewritten when G2 is installed.

You could try another method of doing the same thing to refresh G2's 'memory' of the installation with:

sudo dpkg reconfigure grub-pc
However, from your posts I gather you are still unable to boot into a normal installation and are doing so from the LiveCD (or posting from another OS). If that is the case, you would have to run the above command via the 'chroot' process.

If you have to go to that length, I 'd just do a full purge/reinstall of Grub2. Simply reinstalling may not be enough. (You could just try reconfiguring if you wish.)

The details of how to chroot and purge/reinstall are in this thread:
HOWTO: Purge and Reinstall Grub 2 from the Live CD (http://ubuntuforums.org/showthread.php?t=1581099)
Note: Since you have Grub 1.99 installed (Natty) you will need to use a Natty CD since earlier versions of G2 don't play nice with 1.99 (jealousy I suspect).

kbutcher5
May 21st, 2011, 09:41 PM
It says that grub-pc is not installed, when I do a dpkg-reconfigure. Any apt- commands just gives me a segmentation fault, probably because the pc has no network and aptitude is not up to date.

My biggest problem here is that I need to make this work without an internet connection.

kbutcher5
May 22nd, 2011, 02:16 PM
I made it work by reinstalling the system completely, the problem now though, is that I updated the system and rebooted it.
This had the successful result of a kernel panic:

Kernel Panic - not syncing: VFS: Unable to mount root fs on unkown-block(0,0)

So I have no clue as to why it does this?

Hedgehog1
May 22nd, 2011, 03:01 PM
Could you give us a fresh bootinfoscript output, please? This will tell us the layout of your new install.

Boot off the LiveCD/LiveUSB, select 'TRY', and then:

http://bootinfoscript.sourceforge.net/
Follow the instruction on the website and post the results here.

Please press the '#' button when posting and place the the script results between the
& tags.

The Hedge

:KS

kbutcher5
May 22nd, 2011, 08:55 PM
Here ya go:

Boot Info Script 0.60 from 17 May 2011


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

=> Grub2 (v1.99) is installed in the MBR of /dev/sda and looks at sector 1 of
the same hard drive for core.img. core.img is at this location and looks
for ?? on this drive.
=> Syslinux MBR (3.61-4.03) is installed in the MBR of /dev/sdc.

sda1: __________________________________________________ ________________________

File system: ext4
Boot sector type: -
Boot sector info:
Operating System: Ubuntu 11.04
Boot files: /boot/grub/grub.cfg /etc/fstab /boot/grub/core.img

sdc1: __________________________________________________ ________________________

File system: vfat
Boot sector type: SYSLINUX 4.03 2010-10-22 ........>..sr>.......;..:...0...~.....~...f...M.f.f....f..0~....>E}.u......
Boot sector info: Syslinux looks at sector 8200 of /dev/sdc1 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: 16.0 GB, 15988654080 bytes
255 heads, 63 sectors/track, 1943 cylinders, total 31227840 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 31,225,855 31,223,808 83 Linux


Drive: sdc __________________________________________________ ___________________

Disk /dev/sdc: 2021 MB, 2021654528 bytes
255 heads, 63 sectors/track, 245 cylinders, total 3948544 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/sdc1 * 63 3,948,543 3,948,481 b W95 FAT32


"blkid" output: __________________________________________________ ______________

Device UUID TYPE LABEL

/dev/sda1 e4c52c39-be50-4826-9acd-855e5cc6affa ext4
/dev/sdc1 7E32-03C5 vfat PENDRIVE

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

Device Mount_Point Type Options

/dev/sda1 / ext4 (rw,errors=remount-ro)
/dev/sdc1 /mnt vfat (rw)


=========================== sda1/boot/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='(/dev/sda,msdos1)'
search --no-floppy --fs-uuid --set=root e4c52c39-be50-4826-9acd-855e5cc6affa
if loadfont /usr/share/grub/unicode.pf2 ; then
set gfxmode=auto
load_video
insmod gfxterm
fi
terminal_output gfxterm
insmod part_msdos
insmod ext2
set root='(/dev/sda,msdos1)'
search --no-floppy --fs-uuid --set=root e4c52c39-be50-4826-9acd-855e5cc6affa
set locale_dir=($root)/boot/grub/locale
set lang=en_US
insmod gettext
if [ "${recordfail}" = 1 ]; then
set timeout=-1
else
set timeout=2
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
### 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 2.6.38-8-generic-pae' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
set gfxpayload=$linux_gfx_mode
insmod part_msdos
insmod ext2
set root='(/dev/sda,msdos1)'
search --no-floppy --fs-uuid --set=root e4c52c39-be50-4826-9acd-855e5cc6affa
linux /boot/vmlinuz-2.6.38-8-generic-pae root=UUID=e4c52c39-be50-4826-9acd-855e5cc6affa ro quiet
initrd /boot/initrd.img-2.6.38-8-generic-pae
}
menuentry 'Ubuntu, with Linux 2.6.38-8-generic-pae (recovery mode)' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
set gfxpayload=$linux_gfx_mode
insmod part_msdos
insmod ext2
set root='(/dev/sda,msdos1)'
search --no-floppy --fs-uuid --set=root e4c52c39-be50-4826-9acd-855e5cc6affa
echo 'Loading Linux 2.6.38-8-generic-pae ...'
linux /boot/vmlinuz-2.6.38-8-generic-pae root=UUID=e4c52c39-be50-4826-9acd-855e5cc6affa ro single
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-2.6.38-8-generic-pae
}
### 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='(/dev/sda,msdos1)'
search --no-floppy --fs-uuid --set=root e4c52c39-be50-4826-9acd-855e5cc6affa
linux16 /boot/memtest86+.bin
}
menuentry "Memory test (memtest86+, serial console 115200)" {
insmod part_msdos
insmod ext2
set root='(/dev/sda,msdos1)'
search --no-floppy --fs-uuid --set=root e4c52c39-be50-4826-9acd-855e5cc6affa
linux16 /boot/memtest86+.bin console=ttyS0,115200n8
}
### END /etc/grub.d/20_memtest86+ ###

### BEGIN /etc/grub.d/30_os-prober ###
### 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/etc/fstab: ================================

--------------------------------------------------------------------------------
# /etc/fstab: static file system information.
#
# Use 'blkid -o value -s UUID' to print the universally unique identifier
# for a device; this may be used with UUID= as a more robust way to name
# devices that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc nodev,noexec,nosuid 0 0
# / was on /dev/sda1 during installation
UUID=e4c52c39-be50-4826-9acd-855e5cc6affa / ext4 errors=remount-ro 0 1
--------------------------------------------------------------------------------

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

GiB - GB File Fragment(s)

12.177619934 = 13.075619840 boot/grub/core.img 1
10.315196991 = 11.075858432 boot/grub/grub.cfg 1
0.383621216 = 0.411910144 boot/initrd.img-2.6.38-8-generic-pae 2
10.204528809 = 10.957029376 boot/vmlinuz-2.6.38-8-generic-pae 2
0.383621216 = 0.411910144 initrd.img 2
10.204528809 = 10.957029376 vmlinuz 2

========================= sdc1/syslinux/syslinux.cfg: ==========================

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

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

GiB - GB File Fragment(s)

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

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

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

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

/mnt/boot_info_script.sh: line 1579: [: 2.73495e+09: integer expression expected

drs305
May 22nd, 2011, 09:02 PM
I don't know anything about via boxes. Is it possible the BIOS only recognizes the first 8GB of your drive? That would explain things.

If it's a standard BIOS, you can enter it during boot and check the reported disk size. If it says your drive is only 8GB, that's the problem as your /boot files are beyond that part of the disk. You'll have some options but it's odd that the BIOS would be so limited. Most BIOS's haven't been this limited for a very long time, but since your drive is so small perhaps the manufacturer didn't think it was a big deal.

kbutcher5
May 22nd, 2011, 09:07 PM
Well the BIOS reads it as a 16.0GB IDE compatible device, that is running through the PATA controller, so as far as I know, it should be working properly.

The thing is, shouldn't the boot directory automatically be one of the first things that is put on a drive? Why would it be placed at the end of it?

Seeing as it is an SSD drive with wear leveling though, it is a very plausible posibility, but still, the wear leveling should be transparent and only visible to the device itself.

Edit:
Is it just me or are A LOT of people having problems with Grub2?

kbutcher5
May 22nd, 2011, 10:58 PM
This was taken from a system I could repeatedly reboot, and it would still start:

Boot Info Script 0.60 from 17 May 2011


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

=> Grub2 (v1.99) is installed in the MBR of /dev/sda and looks at sector 1 of
the same hard drive for core.img. core.img is at this location and looks
for ?? on this drive.
=> Syslinux MBR (3.61-4.03) is installed in the MBR of /dev/sdb.

sda1: __________________________________________________ ________________________

File system: ext4
Boot sector type: -
Boot sector info:
Operating System: Ubuntu 11.04
Boot files: /boot/grub/grub.cfg /etc/fstab /boot/grub/core.img

sdb1: __________________________________________________ ________________________

File system: vfat
Boot sector type: SYSLINUX 4.03 2010-10-22 ........>..sr>.......;..:...0...~.....~...f...M.f.f....f..0~....>E}.u......
Boot sector info: Syslinux looks at sector 8200 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: 16.0 GB, 15988654080 bytes
255 heads, 63 sectors/track, 1943 cylinders, total 31227840 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 31,225,855 31,223,808 83 Linux


Drive: sdb __________________________________________________ ___________________

Disk /dev/sdb: 2021 MB, 2021654528 bytes
255 heads, 63 sectors/track, 245 cylinders, total 3948544 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 * 63 3,948,543 3,948,481 b W95 FAT32


"blkid" output: __________________________________________________ ______________

Device UUID TYPE LABEL

/dev/sda1 68117681-b32c-4337-b335-202dadb49acd ext4
/dev/sdb1 7E32-03C5 vfat PENDRIVE

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

Device Mount_Point Type Options

/dev/sda1 / ext4 (rw,errors=remount-ro)
/dev/sdb1 /mnt vfat (rw)


=========================== sda1/boot/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='(/dev/sda,msdos1)'
search --no-floppy --fs-uuid --set=root 68117681-b32c-4337-b335-202dadb49acd
if loadfont /usr/share/grub/unicode.pf2 ; then
set gfxmode=auto
load_video
insmod gfxterm
fi
terminal_output gfxterm
insmod part_msdos
insmod ext2
set root='(/dev/sda,msdos1)'
search --no-floppy --fs-uuid --set=root 68117681-b32c-4337-b335-202dadb49acd
set locale_dir=($root)/boot/grub/locale
set lang=en_US
insmod gettext
if [ "${recordfail}" = 1 ]; then
set timeout=-1
else
set timeout=2
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
### 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 2.6.38-8-generic-pae' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
set gfxpayload=$linux_gfx_mode
insmod part_msdos
insmod ext2
set root='(/dev/sda,msdos1)'
search --no-floppy --fs-uuid --set=root 68117681-b32c-4337-b335-202dadb49acd
linux /boot/vmlinuz-2.6.38-8-generic-pae root=UUID=68117681-b32c-4337-b335-202dadb49acd ro quiet
initrd /boot/initrd.img-2.6.38-8-generic-pae
}
menuentry 'Ubuntu, with Linux 2.6.38-8-generic-pae (recovery mode)' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
set gfxpayload=$linux_gfx_mode
insmod part_msdos
insmod ext2
set root='(/dev/sda,msdos1)'
search --no-floppy --fs-uuid --set=root 68117681-b32c-4337-b335-202dadb49acd
echo 'Loading Linux 2.6.38-8-generic-pae ...'
linux /boot/vmlinuz-2.6.38-8-generic-pae root=UUID=68117681-b32c-4337-b335-202dadb49acd ro single
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-2.6.38-8-generic-pae
}
### 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='(/dev/sda,msdos1)'
search --no-floppy --fs-uuid --set=root 68117681-b32c-4337-b335-202dadb49acd
linux16 /boot/memtest86+.bin
}
menuentry "Memory test (memtest86+, serial console 115200)" {
insmod part_msdos
insmod ext2
set root='(/dev/sda,msdos1)'
search --no-floppy --fs-uuid --set=root 68117681-b32c-4337-b335-202dadb49acd
linux16 /boot/memtest86+.bin console=ttyS0,115200n8
}
### END /etc/grub.d/20_memtest86+ ###

### BEGIN /etc/grub.d/30_os-prober ###
### 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/etc/fstab: ================================

--------------------------------------------------------------------------------
# /etc/fstab: static file system information.
#
# Use 'blkid -o value -s UUID' to print the universally unique identifier
# for a device; this may be used with UUID= as a more robust way to name
# devices that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc nodev,noexec,nosuid 0 0
# / was on /dev/sda1 during installation
UUID=68117681-b32c-4337-b335-202dadb49acd / ext4 errors=remount-ro 0 1
--------------------------------------------------------------------------------

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

GiB - GB File Fragment(s)

6.256336212 = 6.717689856 boot/grub/core.img 1
10.221485138 = 10.975236096 boot/grub/grub.cfg 1
0.505077362 = 0.542322688 boot/initrd.img-2.6.38-8-generic-pae 2
0.204528809 = 0.219611136 boot/vmlinuz-2.6.38-8-generic-pae 1
0.505077362 = 0.542322688 initrd.img 2
0.204528809 = 0.219611136 vmlinuz 1

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

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

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

GiB - GB File Fragment(s)

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

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

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

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

./boot_info_script.sh: line 1579: [: 2.73495e+09: integer expression expected
".



Seeing as there is no difference, and every time I reinstall the system I get a completely different set of errors, I think it is safe to assume that Ubuntu 11.04 is somehow either incompatible or extremely bugged in regards to CF cards.

MAFoElffen
May 22nd, 2011, 11:23 PM
I made it work by reinstalling the system completely, the problem now though, is that I updated the system and rebooted it.
This had the successful result of a kernel panic:

Kernel Panic - not syncing: VFS: Unable to mount root fs on unkown-block(0,0)So I have no clue as to why it does this?
Just a sidenote on this > when you do get backed-off from your kernel panic (these guys are helping you with that), get grub to load and get a kernel booting... (at least into a tty text console)

Look at the Video chip he's running:
"VIA Chrome9™ HC IGP"
Which is not commonly supported, used to be proprietary drivers, but now is opensource. He should be running this driver with Ubuntu:
https://help.ubuntu.com/community/OpenChrome
Which is not in a .deb package and has to be compiled on his current kernel. Not as important on the server edition, but may explain some of the why he was getting a black screen.

kbutcher5
May 22nd, 2011, 11:32 PM
Not as important on the server edition, but may explain some of the why he was getting a black screen.
The black screen emanates from the fact that the geniouses that design grub2, has it defaultly set to quiet, which means black screen until you enter the system. In case of a reboot issue that would just be a black screen and then reboot and in case of a freeze problem like a kernel panic, that would mean permanent black screen.

MAFoElffen
May 22nd, 2011, 11:42 PM
My ideas on getting Grub to ignore the graphics calls to this chipset are:

Mount the drive from the LiveCD and chroot while mounted to that directory to mount that sys...

Edit the /etc/defaulte/grub/ with root previledges. Go to the line


# GRUB_GFXMODE=640x480
Change that line to


GRUB_GFXMODE=640x480x24
Go the the line starting with


GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
And changed to


GRUB_CMDLINE_LINUX_DEFAULT="nosplash --verbose nomodeset text"
And add a line that says


GRUB_GFXPAYLOAD_LINUX=text

Which should set grub and the kernel up on a mode "Not to quesry" the graphics, "Not to" pass on any graphics calls, Ignore any graphics calls that are being passed. That should try to let the graphics video chipset boot into any mode it "wants" to. (which should be the mode it boots during POST.) But to display verbose messaging so that you can see what is going on...

Just an idea...

One afterthought for my reference-- Is the kernel 64bit or 32bit?

MAFoElffen
May 22nd, 2011, 11:59 PM
The black screen emanates from the fact that the geniouses that design grub2, has it defaultly set to quiet, which means black screen until you enter the system. In case of a reboot issue that would just be a black screen and then reboot and in case of a freeze problem like a kernel panic, that would mean permanent black screen.
LOL-- Okay. Understand now. Hey, current "server edition" install has the "timer" default set to "1" second on the Grub Menu display... You might want to change that in 05_debian defaults.

kbutcher5
May 23rd, 2011, 12:16 AM
Neither of those things would be able to alleviate the problem anyway, the problem is just that it simply doesn't play nice with anything that is not a real harddrive.

I had similar problems with pendrives and other flash memory types.
I get errors like: syntax error, corrupt dpkg, kernel panic, block not found and drive doesn't exist.

Whether it is the hardware manufacturers that **** stuff up, with their at times odd firmware or if it is Ubuntu that just doesn't want to play ball, I really have no clue.

kbutcher5
May 23rd, 2011, 05:42 PM
To update this to a conclusion, with the facts that I have gathered, should anyone ever need this article again.
I tried installing Windows XP on it as a test, even such an old system runs perfectly fine through the CF card. By this I have determined that it is not a problem with the hardware or firmware in any way, but rather some sort of compatability issue with Ubuntu or Linux in general.