PDA

View Full Version : [SOLVED] Out of Range on boot



darkreaction
May 1st, 2011, 01:35 AM
Got the problem where after the Bios loads my screen just says "out of range" and I cant do anything else. Running on a live cd.

Hedgehog1
May 1st, 2011, 01:49 AM
We need to get a look at what shape your system is in.

From the LiveCD/LiveUSB (which you are working from):

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 two 'CODE' tags.

The Hedge

:KS

darkreaction
May 1st, 2011, 02:08 AM
Here it is.


Boot Info Script 0.55 dated February 15th, 2010

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

=> Grub 2 is installed in the MBR of /dev/sda and looks on the same drive in
partition #1 for /boot/grub.

sda1: __________________________________________________ _______________________

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

sda2: __________________________________________________ _______________________

File system: Extended Partition
Boot sector type: -
Boot sector info:

sda5: __________________________________________________ _______________________

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

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

Drive: sda ___________________ __________________________________________________ ___

Disk /dev/sda: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes

Partition Boot Start End Size Id System

/dev/sda1 * 63 1,669,635,449 1,669,635,387 83 Linux
/dev/sda2 1,941,439,185 1,953,520,064 12,080,880 5 Extended
/dev/sda5 1,941,439,248 1,953,520,064 12,080,817 82 Linux swap / Solaris


blkid -c /dev/null: __________________________________________________ __________

Device UUID TYPE LABEL

/dev/loop0 squashfs
/dev/sda1 5c5fe566-4e95-4193-bb72-dce043456c19 ext4
/dev/sda2: PTTYPE="dos"
/dev/sda5 78a5453c-fd7a-49cb-b544-893d42499e37 swap
/dev/sda: PTTYPE="dos"

============================ "mount | grep ^/dev output: ===========================

Device Mount_Point Type Options

aufs / aufs (rw)
/dev/sr0 /cdrom iso9660 (ro,noatime)
/dev/loop0 /rofs squashfs (ro,noatime)


=========================== 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 part_msdos
insmod ext2
set root='(hd0,msdos1)'
search --no-floppy --fs-uuid --set=root 5c5fe566-4e95-4193-bb72-dce043456c19
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='(hd0,msdos1)'
search --no-floppy --fs-uuid --set=root 5c5fe566-4e95-4193-bb72-dce043456c19
set locale_dir=($root)/boot/grub/locale
set lang=en_US
insmod gettext
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 2.6.38-8-generic' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
set gfxpayload=$linux_gfx_mode
insmod part_msdos
insmod ext2
set root='(hd0,msdos1)'
search --no-floppy --fs-uuid --set=root 5c5fe566-4e95-4193-bb72-dce043456c19
linux /boot/vmlinuz-2.6.38-8-generic root=UUID=5c5fe566-4e95-4193-bb72-dce043456c19 ro quiet splash vt.handoff=7
initrd /boot/initrd.img-2.6.38-8-generic
}
menuentry 'Ubuntu, with Linux 2.6.38-8-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
set gfxpayload=$linux_gfx_mode
insmod part_msdos
insmod ext2
set root='(hd0,msdos1)'
search --no-floppy --fs-uuid --set=root 5c5fe566-4e95-4193-bb72-dce043456c19
echo 'Loading Linux 2.6.38-8-generic ...'
linux /boot/vmlinuz-2.6.38-8-generic root=UUID=5c5fe566-4e95-4193-bb72-dce043456c19 ro single
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-2.6.38-8-generic
}
submenu "Previous Linux versions" {
menuentry 'Ubuntu, with Linux 2.6.35-28-generic' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
set gfxpayload=$linux_gfx_mode
insmod part_msdos
insmod ext2
set root='(hd0,msdos1)'
search --no-floppy --fs-uuid --set=root 5c5fe566-4e95-4193-bb72-dce043456c19
linux /boot/vmlinuz-2.6.35-28-generic root=UUID=5c5fe566-4e95-4193-bb72-dce043456c19 ro quiet splash vt.handoff=7
initrd /boot/initrd.img-2.6.35-28-generic
}
menuentry 'Ubuntu, with Linux 2.6.35-28-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
set gfxpayload=$linux_gfx_mode
insmod part_msdos
insmod ext2
set root='(hd0,msdos1)'
search --no-floppy --fs-uuid --set=root 5c5fe566-4e95-4193-bb72-dce043456c19
echo 'Loading Linux 2.6.35-28-generic ...'
linux /boot/vmlinuz-2.6.35-28-generic root=UUID=5c5fe566-4e95-4193-bb72-dce043456c19 ro single
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-2.6.35-28-generic
}
menuentry 'Ubuntu, with Linux 2.6.32-25-generic' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
set gfxpayload=$linux_gfx_mode
insmod part_msdos
insmod ext2
set root='(hd0,msdos1)'
search --no-floppy --fs-uuid --set=root 5c5fe566-4e95-4193-bb72-dce043456c19
linux /boot/vmlinuz-2.6.32-25-generic root=UUID=5c5fe566-4e95-4193-bb72-dce043456c19 ro quiet splash vt.handoff=7
initrd /boot/initrd.img-2.6.32-25-generic
}
menuentry 'Ubuntu, with Linux 2.6.32-25-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
set gfxpayload=$linux_gfx_mode
insmod part_msdos
insmod ext2
set root='(hd0,msdos1)'
search --no-floppy --fs-uuid --set=root 5c5fe566-4e95-4193-bb72-dce043456c19
echo 'Loading Linux 2.6.32-25-generic ...'
linux /boot/vmlinuz-2.6.32-25-generic root=UUID=5c5fe566-4e95-4193-bb72-dce043456c19 ro single
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-2.6.32-25-generic
}
menuentry 'Ubuntu, with Linux 2.6.32-24-generic' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
set gfxpayload=$linux_gfx_mode
insmod part_msdos
insmod ext2
set root='(hd0,msdos1)'
search --no-floppy --fs-uuid --set=root 5c5fe566-4e95-4193-bb72-dce043456c19
linux /boot/vmlinuz-2.6.32-24-generic root=UUID=5c5fe566-4e95-4193-bb72-dce043456c19 ro quiet splash vt.handoff=7
initrd /boot/initrd.img-2.6.32-24-generic
}
menuentry 'Ubuntu, with Linux 2.6.32-24-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
set gfxpayload=$linux_gfx_mode
insmod part_msdos
insmod ext2
set root='(hd0,msdos1)'
search --no-floppy --fs-uuid --set=root 5c5fe566-4e95-4193-bb72-dce043456c19
echo 'Loading Linux 2.6.32-24-generic ...'
linux /boot/vmlinuz-2.6.32-24-generic root=UUID=5c5fe566-4e95-4193-bb72-dce043456c19 ro single
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-2.6.32-24-generic
}
menuentry 'Ubuntu, with Linux 2.6.32-22-generic' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
set gfxpayload=$linux_gfx_mode
insmod part_msdos
insmod ext2
set root='(hd0,msdos1)'
search --no-floppy --fs-uuid --set=root 5c5fe566-4e95-4193-bb72-dce043456c19
linux /boot/vmlinuz-2.6.32-22-generic root=UUID=5c5fe566-4e95-4193-bb72-dce043456c19 ro quiet splash vt.handoff=7
initrd /boot/initrd.img-2.6.32-22-generic
}
menuentry 'Ubuntu, with Linux 2.6.32-22-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
set gfxpayload=$linux_gfx_mode
insmod part_msdos
insmod ext2
set root='(hd0,msdos1)'
search --no-floppy --fs-uuid --set=root 5c5fe566-4e95-4193-bb72-dce043456c19
echo 'Loading Linux 2.6.32-22-generic ...'
linux /boot/vmlinuz-2.6.32-22-generic root=UUID=5c5fe566-4e95-4193-bb72-dce043456c19 ro single
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-2.6.32-22-generic
}
menuentry 'Ubuntu, with Linux 2.6.32-21-generic' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
set gfxpayload=$linux_gfx_mode
insmod part_msdos
insmod ext2
set root='(hd0,msdos1)'
search --no-floppy --fs-uuid --set=root 5c5fe566-4e95-4193-bb72-dce043456c19
linux /boot/vmlinuz-2.6.32-21-generic root=UUID=5c5fe566-4e95-4193-bb72-dce043456c19 ro quiet splash vt.handoff=7
initrd /boot/initrd.img-2.6.32-21-generic
}
menuentry 'Ubuntu, with Linux 2.6.32-21-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
set gfxpayload=$linux_gfx_mode
insmod part_msdos
insmod ext2
set root='(hd0,msdos1)'
search --no-floppy --fs-uuid --set=root 5c5fe566-4e95-4193-bb72-dce043456c19
echo 'Loading Linux 2.6.32-21-generic ...'
linux /boot/vmlinuz-2.6.32-21-generic root=UUID=5c5fe566-4e95-4193-bb72-dce043456c19 ro single
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-2.6.32-21-generic
}
menuentry 'Ubuntu, with Linux 2.6.31-20-generic' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
set gfxpayload=$linux_gfx_mode
insmod part_msdos
insmod ext2
set root='(hd0,msdos1)'
search --no-floppy --fs-uuid --set=root 5c5fe566-4e95-4193-bb72-dce043456c19
linux /boot/vmlinuz-2.6.31-20-generic root=UUID=5c5fe566-4e95-4193-bb72-dce043456c19 ro quiet splash vt.handoff=7
initrd /boot/initrd.img-2.6.31-20-generic
}
menuentry 'Ubuntu, with Linux 2.6.31-20-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
set gfxpayload=$linux_gfx_mode
insmod part_msdos
insmod ext2
set root='(hd0,msdos1)'
search --no-floppy --fs-uuid --set=root 5c5fe566-4e95-4193-bb72-dce043456c19
echo 'Loading Linux 2.6.31-20-generic ...'
linux /boot/vmlinuz-2.6.31-20-generic root=UUID=5c5fe566-4e95-4193-bb72-dce043456c19 ro single
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-2.6.31-20-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 5c5fe566-4e95-4193-bb72-dce043456c19
linux16 /boot/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 5c5fe566-4e95-4193-bb72-dce043456c19
linux16 /boot/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/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 defaults 0 0
# / was on /dev/sda1 during installation
UUID=5c5fe566-4e95-4193-bb72-dce043456c19 / ext4 errors=remount-ro 0 1
# swap was on /dev/sda5 during installation
UUID=78a5453c-fd7a-49cb-b544-893d42499e37 none swap sw 0 0
/dev/scd0 /media/cdrom0 udf,iso9660 user,noauto,exec,utf8 0 0
/dev/fd0 /media/floppy0 auto rw,user,noauto,exec,utf8 0 0

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


.1GB: boot/grub/core.img
.9GB: boot/grub/grub.cfg
.1GB: boot/grub/stage2
42.9GB: boot/initrd.img-2.6.31-20-generic
42.8GB: boot/initrd.img-2.6.32-21-generic
60.1GB: boot/initrd.img-2.6.32-22-generic
60.1GB: boot/initrd.img-2.6.32-24-generic
231.4GB: boot/initrd.img-2.6.32-25-generic
277.0GB: boot/initrd.img-2.6.35-28-generic
278.4GB: boot/initrd.img-2.6.38-8-generic
.9GB: boot/vmlinuz-2.6.31-20-generic
42.7GB: boot/vmlinuz-2.6.32-21-generic
42.5GB: boot/vmlinuz-2.6.32-22-generic
43.0GB: boot/vmlinuz-2.6.32-24-generic
43.0GB: boot/vmlinuz-2.6.32-25-generic
48.0GB: boot/vmlinuz-2.6.35-28-generic
372.8GB: boot/vmlinuz-2.6.38-8-generic
278.4GB: initrd.img
277.0GB: initrd.img.old
372.8GB: vmlinuz
48.0GB: vmlinuz.old

Hedgehog1
May 1st, 2011, 02:28 AM
This appears to be an upgrade (based on the previous Kernels listed).

My first inclination after looking at the script output is to have you reinstall grub FROM THE NATTY LIVECD. There is is newer grub carried with Natty - you don't want to be trying to update grub on a Natty install from a pre-Natty LiveCD.

In case your LiveCD is not a Natty one, please download the Natty ISO (to your hard drive) and make a Natty LiveCD or LiveUSB.

Once you are running from a Natty LiveCD/LiveUSB, do these two steps:



sudo mount /dev/sda1 /mnt


sudo grub-install --root-directory=/mnt /dev/sda

Then reboot and see if this gets you running.


The Hedge

:KS

drs305
May 1st, 2011, 02:44 AM
All of your newer kernels are well into the disk, raising the possibility that your BIOS may only see the first 137GB of the disk. Once you boot, your OS may allow you to see all the files, but the BIOS/Grub may not be able to see past the 137GB limit.

You can check in a couple of ways. The best is probably to enter BIOS during boot. Look at the reported disk size. Does it show the drive as being 137GB or less? If so, see if there is an LBA or large disk option which you can select.

Another way to check is at the Grub menu/prompt. Get to the prompt, then type:

ls (hd0,1)/vmlinuz
or
ls (hd0,1)/boot/vmlinuz # TAB to see which ones it locates; compare them to the locations at the end of RESULTS.txt

This file is currently located at the 278GB portion of the disk. If you BIOS can't see that far, it won't find the file.

If you do have a BIOS limit, your options are:

Enable the large disk option of your BIOS, if available.
Update BIOS.
Shrink your Ubuntu partition to less than 137GB (if space/data permits).
Create a /boot partition within the first XXXGB (probably 137GB).
Put /boot on a removable drive/other drive

darkreaction
May 1st, 2011, 03:49 AM
Thanks Hedgehog1 fixed it!

Hedgehog1
May 1st, 2011, 03:57 AM
All of your newer kernels are well into the disk, raising the possibility that your BIOS may only see the first 137GB of the disk. Once you boot, your OS may allow you to see all the files, but the BIOS/Grub may not be able to see past the 137GB limit.

drs305 - Dog gone, I forgot about this again as another thing to check. Thanks for the reminder.

darkreaction - glad you are up and running! :P

The Hedge

:KS

drs305
May 1st, 2011, 04:08 AM
drs305 - Dog gone, I forgot about this again as another thing to check. Thanks for the reminder.

Since the simple install worked, perhaps rather than explaining the BIOS boot limitation I should wait to see what happens first. ;-)

There can be some clues, such as mention of an old system, a very small hard drive, etc, but as older systems fade away this solution will become less common.

To the OP: You might run the boot info script once more to see where your files are now located, just in case they were placed in vacated areas and are now early on the disk. If they are, G2 could fail on an update where they are once again moved beyond the limit. Not likely, just something to tuck in the recesses of your brain.