reboot after install failed with Error 15: file not found

I had a similar problem on install of Dapper from Live CD. I beleive it was caused by having a seperate /boot partition. Other users have reported the same problem

I had a similar error when reinstalling a fresh copy of Ubuntu Dapper the other day. My drive configuration is as follows:

/dev/hda: DVD-RW drive

Disk /dev/hdd: 20.0 GB, 20000000000 bytes
255 heads, 63 sectors/track, 2431 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot Start End Blocks Id System
/dev/hdd1 * 1 2430 19518943+ 7 HPFS/NTFS

Disk /dev/sda: 80.0 GB, 80032038912 bytes
255 heads, 63 sectors/track, 9730 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot Start End Blocks Id System
/dev/sda1 * 1 2117 17004771 83 Linux
/dev/sda2 2118 2367 2008125 82 Linux swap / Solaris
/dev/sda3 2368 9730 59143297+ 83 Linux

Currently, grub, when run from the LiveCD or the install, reports the following configuration:

grub> geometry (hd0,0)
drive 0x80: C/H/S = 2431/255/63, The number of sectors = 39062500, /dev/hdd
   Partition num: 0, Filesystem type unknown, partition type 0x7

grub> geometry (hd1,0)
drive 0x81: C/H/S = 9730/255/63, The number of sectors = 156312576, /dev/sda
   Partition num: 0, Filesystem type is ext2fs, partition type 0x83
   Partition num: 1, Filesystem type unknown, partition type 0x82
   Partition num: 2, Filesystem type is ext2fs, partition type 0x83

The default groot was (hd1,0), as reported by the LiveCD and my filesystem, but I had to change this manually to (hd0,0) in order to be mapped to the same drive at boot.

Why does grub at boot report different disk order than grub after booting?

i have this same problem with edgy Desktop install and alternate installer.

I have this same problem on an Intel Q965FEKR motherboard w/ two Seagate 250g SATA II HD's configured as software RAID w/ Alternate 7.04 Ubuntu CD.

Partitioning worked great, setting up RAID arrays worked great. I had one 3G Swap (Raid 0) and two other RAID 1 (/var and /)

The software installed just fine, and told me I had to reboot to finish up. I rebooted and got the Error 15: file not found.

Just did a clean install with the latest Gutsy desktop CD and this still happens. After install grub root is set to (hd2,0) and boot fails requiring me to manually change it to (hd0,0).

Is this symptom still reproducible in 8.10 alpha?

Recurring issue, grub writing incorrect drive designations in 8.10 as of 11/15/2008. Sqame issue in 8.04.

I have 4 HDD's:[QUOTE]
 sudo blkid
/dev/sda1: UUID="32dd3252-53b9-4647-b538-95793e7a55e2" TYPE="ext3"
/dev/sda5: TYPE="swap" UUID="d81a0c0e-1b88-40fb-abed-2c9b15d0db6f"
/dev/sdc1: UUID="30F70D6E790F4174" LABEL="Backups" TYPE="ntfs"
/dev/sdd1: UUID="25610e0c-64f0-4512-a31c-49ddf2a9c1ff" TYPE="ext2"
/dev/sdb3: UUID="4f92449d-38a5-4453-b22e-9e3785987a02" SEC_TYPE="ext2" TYPE="ext3"
/dev/sdb4: TYPE="swap" UUID="67e9932c-9bf7-4186-b147-0b534ed4080f"
/dev/sdf1: SEC_TYPE="msdos" UUID="48F4-EAEE" TYPE="vfat"
/dev/sde1: SEC_TYPE="msdos" UUID="48EA-8696" TYPE="vfat"
/dev/sdd5: TYPE="swap" UUID="bf5881cf-1674-4f8e-a1b7-96083c9f0dd2"
/dev/sdg1: UUID="48F4-EAEE" TYPE="vfat" SEC_TYPE="msdos"
/dev/sdd2: UUID="1306a0e0-da49-4c2a-bc75-87a7c682aba3" SEC_TYPE="ext2" TYPE="ext3"
/dev/sdg: LABEL="NEW VOLUME" UUID="E4B5-EDFE" TYPE="vfat"
/dev/sdh1: UUID="0000-0000" TYPE="vfat" SEC_TYPE="msdos"
/dev/sdi1: SEC_TYPE="msdos" UUID="0000-0000" TYPE="vfat"
/dev/sdi: LABEL="NEW VOLUME" UUID="E4B5-EDFE" TYPE="vfat"
/dev/sdb5: TYPE="swap" UUID="4e1e2438-4522-4134-95c5-af5de6d4b796"
/dev/sdc3: UUID="4f92449d-38a5-4453-b22e-9e3785987a02" SEC_TYPE="ext2" TYPE="ext3"
/dev/sdc4: TYPE="swap" UUID="67e9932c-9bf7-4186-b147-0b534ed4080f"
/dev/sdc5: TYPE="swap" UUID="4e1e2438-4522-4134-95c5-af5de6d4b796"
/dev/sdb1: UUID="ce6c2aec-04dd-4729-aeb8-0ea4fec8ca5d" SEC_TYPE="ext2" TYPE="ext3" [/QUOTE]

I have Ubuntu 8.10 on hd0,0/sda1.
I just installed Kubuntu 8.10 on hd1,0/sdb1

The grub was written to hd1,0 but is incorrect. This is the grub menu.lst that comes up upon start-up and was created after Kubuntu unstall:

[QUOTE]title Ubuntu 8.10, kernel 2.6.27-7-generic
uuid ce6c2aec-04dd-4729-aeb8-0ea4fec8ca5d
kernel /boot/vmlinuz-2.6.27-7-generic root=UUID=ce6c2aec-04dd-4729-aeb8-0ea4fec8ca5d ro quiet splash
initrd /boot/initrd.img-2.6.27-7-generic
quiet

title Ubuntu 8.10, kernel 2.6.27-7-generic (recovery mode)
uuid ce6c2aec-04dd-4729-aeb8-0ea4fec8ca5d
kernel /boot/vmlinuz-2.6.27-7-generic root=UUID=ce6c2aec-04dd-4729-aeb8-0ea4fec8ca5d ro single
initrd /boot/initrd.img-2.6.27-7-generic

title Ubuntu 8.10, memtest86+
uuid ce6c2aec-04dd-4729-aeb8-0ea4fec8ca5d
kernel /boot/memtest86+.bin
quiet

### END DEBIAN AUTOMAGIC KERNELS LIST

# This is a divider, added to separate the menu items below from the Debian
# ones.
title Other operating systems:
root

# This entry automatically added by the Debian installer for an existing
# linux installation on /dev/sda1.
title Ubuntu 8.10, kernel 2.6.27-7-generic (on /dev/sda1)
root (hd0,0)
kernel /boot/vmlinuz-2.6.27-7-generic root=UUID=32dd3252-53b9-4647-b538-95793e7a55e2 ro quiet splash
initrd /boot/initrd.img-2.6.27-7-generic
savedefault
boot

# This entry automatically added by the Debian installer for an existing
# linux installation on /dev/sda1.
title Ubuntu 8.10, kernel 2.6.27-7-generic (recovery mode) (on /dev/sda1)
root (hd0,0)
kernel /boot/vmlinuz-2.6.27-7-generic root=UUID=32dd3252-53b9-4647-b538-95793e...

Thank you for reporting this bug.

Does this still occur in Lucid?

This looks like it may have been an issue in grub legacy rather than grub-installer, but it is not clear from the report. Given this and that grub legacy is no longer being developed, and this has been incomplete for a very long time, I'm going to go ahead and close it out. Grub2 now uses UUIDs to identify drives, so using a recent release that uses grub2 should not have this issue. If it does, please file a new bug against grub2.