PDA

View Full Version : [kubuntu] "operating system not found" after fresh install



nhaskins
May 14th, 2011, 08:54 PM
I've just received my new Lenovo X120e. After running the installer for Kubuntu Natty 64bit when I go to start the computer I get an error "operating system not found". What do I do?

I partitioned the system as
sda 1 - ext2 - /boot - 256MB
sda2 - swap - 4000MB
sda3 - ext4 - / - 15000MB
sda4 - ext4 - /home / (all the space left)

Any help is most apreciated

Hedgehog1
May 14th, 2011, 09:28 PM
We need to get a look at your install to get an idea what is going on.

Please 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

nhaskins
May 14th, 2011, 09:49 PM
Thanks. I tried again with different partitioning, so it's not like I said above, but it still doesn't work so I'll post the script result.


Boot Info Script 0.55 dated February 15th, 2010

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

=> No boot loader is installed in the MBR of /dev/sda
=> Syslinux 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/dirs: /boot/grub/grub.cfg /etc/fstab

sda2: __________________________________________________ _______________________

File system: ext4
Boot sector type: -
Boot sector info:
Operating System:
Boot files/dirs:

sda3: __________________________________________________ _______________________

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

sdb1: __________________________________________________ _______________________

File system: vfat
Boot sector type: Unknown
Boot sector info: According to the info in the boot sector, sdb1 starts
at sector 0. But according to the info from fdisk,
sdb1 starts at sector 62.
Operating System:
Boot files/dirs: /boot/grub/grub.cfg

=========================== 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 End Size Id System

/dev/sda1 1 488,397,167 488,397,167 ee GPT


GUID Partition Table detected.

Partition Start End Size System
/dev/sda1 34 29,296,909 29,296,876 Linux or Data
/dev/sda2 29,296,910 480,584,019 451,287,110 Linux or Data
/dev/sda3 480,584,020 488,396,520 7,812,501 Linux Swap

Drive: sdb ___________________ __________________________________________________ ___

Disk /dev/sdb: 8061 MB, 8061451776 bytes
248 heads, 62 sectors/track, 1023 cylinders, total 15745023 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes

Partition Boot Start End Size Id System

/dev/sdb1 * 62 15,729,647 15,729,586 c W95 FAT32 (LBA)


blkid -c /dev/null: __________________________________________________ __________

Device UUID TYPE LABEL

/dev/loop0 squashfs
/dev/sda1 9d277abf-8368-4ac8-90b3-9ae475f170f8 ext4
/dev/sda2 baed4450-727a-49a2-bea1-2ce227542896 ext4
/dev/sda3 cc91a000-06f8-44bd-89de-5c7ff4c79ba5 swap
/dev/sda: PTTYPE="gpt"
/dev/sdb1 F68B-A0C3 vfat
/dev/sdb: PTTYPE="dos"
error: /dev/sdc: No medium found

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

Device Mount_Point Type Options

aufs / aufs (rw)
/dev/sdb1 /cdrom vfat (ro,noatime,fmask=0022,dmask=0022,codepage=cp437,i ocharset=iso8859-1,shortname=mixed,errors=remount-ro)
/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 efi_gop
insmod efi_uga
insmod video_bochs
insmod video_cirrus
}

insmod part_gpt
insmod ext2
set root='(/dev/sda,gpt1)'
search --no-floppy --fs-uuid --set=root 9d277abf-8368-4ac8-90b3-9ae475f170f8
if loadfont /usr/share/grub/unicode.pf2 ; then
set gfxmode=auto
load_video
insmod gfxterm
fi
terminal_output gfxterm
insmod part_gpt
insmod ext2
set root='(/dev/sda,gpt1)'
search --no-floppy --fs-uuid --set=root 9d277abf-8368-4ac8-90b3-9ae475f170f8
set locale_dir=($root)/boot/grub/locale
set lang=en_CA
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 0,71,115; 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_gpt
insmod ext2
set root='(/dev/sda,gpt1)'
search --no-floppy --fs-uuid --set=root 9d277abf-8368-4ac8-90b3-9ae475f170f8
linux /boot/vmlinuz-2.6.38-8-generic root=UUID=9d277abf-8368-4ac8-90b3-9ae475f170f8 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_gpt
insmod ext2
set root='(/dev/sda,gpt1)'
search --no-floppy --fs-uuid --set=root 9d277abf-8368-4ac8-90b3-9ae475f170f8
echo 'Loading Linux 2.6.38-8-generic ...'
linux /boot/vmlinuz-2.6.38-8-generic root=UUID=9d277abf-8368-4ac8-90b3-9ae475f170f8 ro single
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-2.6.38-8-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_gpt
insmod ext2
set root='(/dev/sda,gpt1)'
search --no-floppy --fs-uuid --set=root 9d277abf-8368-4ac8-90b3-9ae475f170f8
linux16 /boot/memtest86+.bin
}
menuentry "Memory test (memtest86+, serial console 115200)" {
insmod part_gpt
insmod ext2
set root='(/dev/sda,gpt1)'
search --no-floppy --fs-uuid --set=root 9d277abf-8368-4ac8-90b3-9ae475f170f8
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 nodev,noexec,nosuid 0 0
/dev/sda1 / ext4 errors=remount-ro 0 1
/dev/sda2 /home ext4 defaults 0 2
/dev/sda3 none swap sw 0 0

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


2.5GB: boot/grub/grub.cfg
1.6GB: boot/initrd.img-2.6.38-8-generic
2.5GB: boot/vmlinuz-2.6.38-8-generic
1.6GB: initrd.img
2.5GB: vmlinuz

=========================== sdb1/boot/grub/grub.cfg: ===========================


if loadfont /boot/grub/font.pf2 ; then
set gfxmode=auto
insmod efi_gop
insmod efi_uga
insmod gfxterm
terminal_output gfxterm
fi

set menu_color_normal=white/black
set menu_color_highlight=black/light-gray

menuentry "Start Kubuntu" {
set gfxpayload=keep
linux /casper/vmlinuz file=/cdrom/preseed/kubuntu.seed boot=casper maybe-ubiquity quiet splash --
initrd /casper/initrd.lz
}
menuentry "Check disc for defects" {
set gfxpayload=keep
linux /casper/vmlinuz boot=casper integrity-check quiet splash --
initrd /casper/initrd.lz
}

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


??GB: boot/grub/grub.cfg
=========================== Unknown MBRs/Boot Sectors/etc =======================

Unknown BootLoader on sdb1

00000000 eb 58 90 53 59 53 4c 49 4e 55 58 00 02 08 20 00 |.X.SYSLINUX... .|
00000010 02 00 00 00 00 f8 00 00 3e 00 f8 00 00 00 00 00 |........>.......|
00000020 b2 03 f0 00 e8 3b 00 00 00 00 00 00 02 00 00 00 |.....;..........|
00000030 01 00 06 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
00000040 00 00 29 c3 a0 8b f6 20 20 20 20 20 20 20 20 20 |..).... |
00000050 20 20 46 41 54 33 32 20 20 20 fa fc 31 c9 8e d1 | FAT32 ..1...|
00000060 bc 76 7b 52 06 57 8e c1 b1 26 bf 78 7b f3 a5 8e |.v{R.W...&.x{...|
00000070 d9 bb 78 00 0f b4 37 0f a0 56 20 d2 78 1b 31 c0 |..x...7..V .x.1.|
00000080 b1 06 89 3f 89 47 02 f3 64 a5 8a 0e 18 7c 88 4d |...?.G..d....|.M|
00000090 bc 50 50 50 50 cd 13 eb 4b f6 45 b4 7f 75 25 38 |.PPPP...K.E..u%8|
000000a0 4d b8 74 20 66 3d 21 47 50 54 75 10 80 7d b8 ed |M.t f=!GPTu..}..|
000000b0 75 0a 66 ff 75 ec 66 ff 75 e8 eb 0f 51 51 66 ff |u.f.u.f.u...QQf.|
000000c0 75 bc eb 07 51 51 66 ff 36 1c 7c b4 08 cd 13 72 |u...QQf.6.|....r|
000000d0 13 20 e4 75 0f c1 ea 08 42 89 16 1a 7c 83 e1 3f |. .u....B...|..?|
000000e0 89 0e 18 7c fb bb aa 55 b4 41 8a 16 74 7b cd 13 |...|...U.A..t{..|
000000f0 72 10 81 fb 55 aa 75 0a f6 c1 01 74 05 c6 06 32 |r...U.u....t...2|
00000100 7d 00 66 b8 58 24 16 00 66 ba 00 00 00 00 bb 00 |}.f.X$..f.......|
00000110 7e e8 10 00 66 81 3e 2c 7e d2 1d 08 72 75 76 ea |~...f.>,~...ruv.|
00000120 40 7e 00 00 66 03 06 64 7b 66 13 16 68 7b b9 10 |@~..f..d{f..h{..|
00000130 00 eb 2b 66 52 66 50 06 53 6a 01 6a 10 89 e6 66 |..+fRfP.Sj.j...f|
00000140 60 b4 42 e8 7f 00 66 61 8d 64 10 72 01 c3 66 60 |`.B...fa.d.r..f`|
00000150 31 c0 e8 70 00 66 61 e2 da c6 06 32 7d 2b 66 60 |1..p.fa....2}+f`|
00000160 66 0f b7 36 18 7c 66 0f b7 3e 1a 7c 66 f7 f6 31 |f..6.|f..>.|f..1|
00000170 c9 87 ca 66 f7 f7 66 3d ff 03 00 00 77 17 c0 e4 |...f..f=....w...|
00000180 06 41 08 e1 88 c5 88 d6 b8 01 02 e8 37 00 66 61 |.A..........7.fa|
00000190 72 01 c3 e2 c9 31 f6 8e d6 bc 6c 7b 8e de 66 8f |r....1....l{..f.|
000001a0 06 78 00 be cc 7d e8 09 00 31 c0 cd 16 cd 19 f4 |.x...}...1......|
000001b0 eb fd 66 60 ac 20 c0 74 09 b4 0e bb 07 00 cd 10 |..f`. .t........|
000001c0 eb f2 66 61 c3 8a 16 74 7b cd 13 c3 42 6f 6f 74 |..fa...t{...Boot|
000001d0 20 65 72 72 6f 72 0d 0a 00 00 00 00 00 00 00 00 | error..........|
000001e0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
000001f0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 55 aa |..............U.|
00000200


=======Devices which don't seem to have a corresponding hard drive==============

sdc


Thanks

nhaskins
May 14th, 2011, 09:51 PM
Obviously I'm missing my bootloader, but why???
Sorry, *nix newb :)

srs5694
May 14th, 2011, 10:18 PM
I notice that you're using a GUID Partition Table (GPT), but your disk is only 250 GB in size. This is OK, but Ubuntu normally uses GPT only if the disk was already set up with GPT, on disks over 1-2 TB in size, or on computers that use a (U)EFI firmware rather than a BIOS. In any event, you'll probably need to add a special partition that's of one of two types to boot:



A BIOS Boot Partition (http://en.wikipedia.org/wiki/BIOS_Boot_partition) -- This partition is used by GRUB on BIOS-based computers, but is not used on (U)EFI systems. It takes the place of an unallocated chunk of disk space on the older Master Boot Record (MBR) disks in which GRUB would stash some of its code. A BIOS Boot Partition can be tiny (as small as 32 KiB, although 1 MiB is a more common size with modern partitioning tools).
An EFI System Partition (ESP) (http://en.wikipedia.org/wiki/EFI_System_partition) -- This is a partition that holds a FAT filesystem and is used to store (U)EFI drivers and boot loaders, including GRUB code. It's used on (U)EFI-based computers. It's normally 100-200 MiB in size. In the Ubuntu installer, IIRC you've got to flag the partition as being an "EFI boot partition" or some such (the installer doesn't use the standard term for this partition, unfortunately).



You can create both partitions, if you like; the presence of the one that's not needed won't do any harm, other than consuming a bit of disk space. You can do this prior to installation by using GNU Parted, GParted, gdisk, or some other tool. In GNU Parted or GParted, you identify a BIOS Boot Partition by setting the "bios_grub flag," and an ESP by setting the "boot flag" (unfortunately the same flag name used to identify a bootable MBR partition, although the MBR and GPT concepts are entirely unrelated). In gdisk, you'd set a BIOS Boot Partition to use type EF02, and an ESP to use type EF00.

If you set up a BIOS Boot Partition ahead of time and have a BIOS-based computer, then GRUB should detect and use the partition just fine. (You don't need to create a filesystem on the partition or identify it in the installer.) You should install GRUB normally to the MBR (/dev/sda).

If you set up an ESP ahead of time and you have a (U)EFI-based computer, then you must ensure it has a FAT filesystem on it, and you must identify it as such to the installer, as noted earlier. I believe the user interface option of where to install GRUB remains in the installer, but I don't know if it has any effect. (I've only done a couple of Ubuntu installs to UEFI-based systems, and this support is new with Ubuntu 11.04, so I don't recall the details of what it does.)

Most PCs sold to date use BIOSes. Intel-based Apple Macs, a few PCs sold in the last couple of years, and more very recent PCs are (U)EFI-based. Most of the (U)EFI-based computers include a BIOS compatibility option. If you're unsure what you've got, please post product details, including computer's age, the computer manufacturer and model number and, if you have it, the manufacturer and model number of the motherboard. There are likely to be clues in your motherboard's pre-boot setup tools (often accessed by pressing Delete or a function key early in the boot process). Look for a boot option relating to EFI or UEFI.

If you've got a BIOS-based computer and you plan to dual-boot with Windows, it's best to convert from GPT to MBR, since Windows can't boot from GPT on a BIOS-based computer. GPT offers some minor advantages to more capable OSes, though, so if you plan to run a Linux-only installation, or perhaps even dual-boot with another OS like FreeBSD, sticking with GPT is probably better (although not by a lot). You can do a non-destructive GPT-to-MBR conversion with gdisk, or you can start fresh by using parted or GParted to create a fresh partition table.

nhaskins
May 14th, 2011, 10:38 PM
OK, here's hoping.
Doing a reinstall, under manual partitioning one of the partition types is "efi boot partition" so I set up sda1 as that with 256MB of space. The only thing I didn't know was the option at the bottom "device to install boot loader" (or something like that). By default it's set to sda, but I figured it should be sda1. Installer is running now, and we'll see how it goes.

nhaskins
May 14th, 2011, 11:02 PM
It's up and running. Thanks for your help.:KS