grub error 15 on clean install

pickarooney

I reformatted my root partition and boot partitions and installed ,averick but zhen I boot I get a grub 15 error. I might have made a mistake on the partitioning screen zhen I selected /dev/dsa6 for the GRUB bootloader - this is my dedicated /boot partition - and don't know how to fix it now

my current fstab is

# /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/sda3 during installation
UUID=94e510c4-b762-460f-9a65-27e68887966d /               ext3    errors=remount-ro 0       1
# /boot was on /dev/sda1 during installation
UUID=c3111ca5-13cc-4042-bcc4-9a31aef7622c /boot           ext3    defaults        0       2
# /home was on /dev/sda4 during installation
UUID=6aca9cac-5354-4183-bf88-68e9e62bed9a /home           ext3    defaults        0       2
# /media/backup was on /dev/sdc2 during installation
UUID=D6F8-0339  /media/backup   vfat    utf8,umask=007,gid=46 0       1
# /media/bigbastard was on /dev/sdb1 during installation
UUID=403e1522-05cc-4cd7-9d16-0a00e8b2409b /media/bigbastard ext3    defaults        0       2
# /media/supersize was on /dev/sdc1 during installation
UUID=a138972b-a839-4285-b048-77660796538f /media/supersize ext3    defaults        0       2
# swap was on /dev/sda5 during installation
UUID=fad2fdc5-26da-4080-ba6b-048f80f7cec9 none            swap    sw              0       0
/dev/fd0        /media/floppy0  auto    rw,user,noauto,exec,utf8 0       0

I can't access my home folder to see the copy of fstab from before the reinstall.

By mounting all partitions one by one I can see now that everything has moved around so that

sda is the bigbastard drive - 500GB - that was sdb previously
sdb is supersize/basckup and was sdc before
the paritions on sda have moved to sdc

I have no idea hot to put everything back

help please!

croo

I've had this happen to me. I think I resolved it by specifying the UUID instead of the device (/dev/sda?).

It was a couple of years ago but I think I needed to
boot from a live cd
chroot into the linux partition on the HD
then make the changes re-install/update grub

This was the type of process I followed http://ubuntuforums.org/showthread.php?t=644773
But I know grub2 has changed since I did this last but I think you can use the first part to boot from a live cd into the linux install on your hard disk. Then you need to change the grub configuration ... this might help there
http://ubuntuforums.org/showthread.php?t=1285897&highlight=grub2

Note the piece about 40_custom... trying putting the UUIDs in there and do an update-grub to regenerate the /boot/grub/grub.cfg then try boot from the HD again.

pickarooney

I've been messing around and probbly making it worse. I managed to install TWO GRUB2s now, one on sda and one on sdc. I'd like to remove the one on sda completely and get the one on sdc pointing to the right place but no matter what I do (and I've tried about 5 tutorials at this stage) I can't get beyond the grub prompt (a slight improvement on earlier as there's no error 15 now, but still useless to me).

croo

Don't forget that your bios will determine which disk boots first!
If you installed multiple MBRs then I which one actually boots will be determined by that (i.e. it's be the MBR on the first boot disk from the BIOS)

Did you do the chroot trick to load the existing setup and change the grub install that way?

pickarooney

I did! I had to get a bit of hand-holding from the ubuntu forums but I/we got it sorted via chroot and mucking about a bit with the menu.lst or whatever it's called these days

croo

I/we got it sorted via chroot and mucking about a bit with the menu.lst or whatever it's called these days

So you are sorted now?
Or you did that and still have issues?
ps. IRC is a better place to get help with something like this ok!

pickarooney

Sorry, forgot to come back here the other day. I got it all sorted using chroot. Now I have a whole new set of problems, but that's a story for another day