Using debootstrap: haven't installed grub and can't complete installation

I have used debootstrap and installed Ubuntu onto /dev/sda3.
However, I have a slight problem.

I didn't use the OP's suggestion on modifying the command when installing the base system.
As a result, I simply used the following command:

root@host# debootstrap --arch amd64 saucy /mnt/deboot http://archive.ubuntu.com/ubuntu

As a result, I have not installed GRUB and configured it for the new install.
So when I reboot, Ubuntu on /dev/sda3 is not shown by the bootloader.

I also had a problem with putting the UUID of /dev/sda3 onto /etc/fstab.
I was uncertain whether to put the correct UUID (for sda3) into /etc/fstab of the host system I was in (i.e sda1), or to put the UUID into /etc/fstab which existed on /mnt/deboot. (At least, I think such a directory may exist - but as I say, I am uncertain).
I'd like to know how to sort out this particular issue.

After completing the tutorial, I ran:

osprober
update-grub

Both commands said they could see Ubuntu in sda3.
However when I reboot, GRUB will not offer sda3 as an option.

I think I may need to add sda3 into /etc/fstab of my host system (sda1) or possibly add GRUB into sda3 in some way.

OP has advised there will be an update to the debootstrap tutorial, and I will be looking forward to it.
But I wonder if someone can please say how I can activate this new install which I have on sda3?
I've started a new thread because I don't want to complicate the debootstrap tutorial thread.

Originally Posted by Higgsboson I have used debootstrap and installed Ubuntu onto /dev/sda3. However, I have a slight problem. I didn't use the OP's suggestion on modifying the command when installing the base system. As a result, I simply used the following command: root@host# debootstrap --arch amd64 saucy /mnt/deboot http://archive.ubuntu.com/ubuntu As a result, I have not installed GRUB and configured it for the new install. So when I reboot, Ubuntu on /dev/sda3 is not shown by the bootloader. I also had a problem with putting the UUID of /dev/sda3 onto /etc/fstab. I was uncertain whether to put the correct UUID (for sda3) into /etc/fstab of the host system I was in (i.e sda1), or to put the UUID into /etc/fstab which existed on /mnt/deboot. (At least, I think such a directory may exist - but as I say, I am uncertain). I'd like to know how to sort out this particular issue. After completing the tutorial, I ran: osprober update-grub Both commands said they could see Ubuntu in sda3. However when I reboot, GRUB will not offer sda3 as an option. I think I may need to add sda3 into /etc/fstab of my host system (sda1) or possibly add GRUB into sda3 in some way. OP has advised there will be an update to the debootstrap tutorial, and I will be looking forward to it. But I wonder if someone can please say how I can activate this new install which I have on sda3? I've started a new thread because I don't want to complicate the debootstrap tutorial thread.

It was updated a about a week ago. When you installed Ubuntu via debootstrap, did you install a kernel before exiting the install?
For the UUID of /dev/sda3:

blkid /dev/sda3

you need to chroot back into the installation install a kernel as to step 6 of this http://www.thegeekstuff.com/2010/01/...-installation/

Originally Posted by replica9000 It was updated a about a week ago.

I see. That explains the additional information which I thought I had previously overlooked!
I've just noticed the update timestamp. That's good to see.

The tutorial says:

debootstrap can also be used to install Ubuntu (ex. Raring Ringtail):
root@host# debootstrap --arch amd64 raring /mnt/deboot http://archive.ubuntu.com/ubuntu

The system can't find 'Raring' on the ubuntu archive website. I think they've taken it off.

I found Debootstrap has script files or something in its directory (/usr/share/debootstrap/scripts).
For ubuntu, the script files seem to be identical.
So I copied the file for Raring and renamed it 'saucy'.
I then ran:

root@host# debootstrap --arch amd64 saucy /mnt/deboot http://archive.ubuntu.com/ubuntu

and the system was able to download all the files for saucy.

I didn't rename it 'utopic' for the latest ubuntu stable release because I wasn't sure if the correct script file for utopic had been amended in some way.

When you installed Ubuntu via debootstrap, did you install a kernel before exiting the install?

No, I'm afraid I didn't. That's probably where I went wrong.
If I wanted to use debootstrap to install a stable version of Ubuntu saucy, would the command be:

root@host# debootstrap --include linux-image-amd64,grub-pc,locales --arch amd64 saucy /mnt/deboot http://archive.ubuntu.com/ubuntu

Also, if I wanted to install Ubuntu utopic, could I do this?:

root@host# cp /usr/share/debootstrap/scripts/raring /usr/share/debootstrap/scripts/utopic
root@host# debootstrap --include linux-image-amd64,grub-pc,locales --arch amd64 utopic /mnt/deboot http://archive.ubuntu.com/ubuntu

Finally, I think the link to the archives has changed from 'http://archive.ubuntu.com/ubuntu' to 'http://archive.ubuntu.com/ubuntu/dists'

For the UUID of /dev/sda3: blkid /dev/sda3

Yes, where is the /etc/fstab located for inputting the UUID?
I'm getting confused between the /etc/fstab of the host system, and the /etc/fstab presumably being created in the mounted 'deboot' directory.

Originally Posted by colorpurple21859 you need to chroot back into the installation install a kernel as to step 6 of this http://www.thegeekstuff.com/2010/01/...-installation/

I'm not sure how to chroot back into the installation.
I think everything was extracted into sda3.
I'm wondering if it's easier to delete everything on the sda3 partition and redo the install.

from the howto you initially followed.

Binding the virtual filesystems. Until your new install is booting on it's own, we'll borrow these from the host. Code: root@host# mount -o bind /dev /mnt/deboot/dev root@host# mount -o bind /proc /mnt/deboot/proc root@host# mount -o bind /sys /mnt/deboot/sys Continuing the installation within chroot Entering the chroot environment: Code: root@host# chroot /mnt/deboot /bin/bash

Originally Posted by Higgsboson I see. That explains the additional information which I thought I had previously overlooked! I've just noticed the update timestamp. That's good to see. The tutorial says: debootstrap can also be used to install Ubuntu (ex. Raring Ringtail): root@host# debootstrap --arch amd64 raring /mnt/deboot http://archive.ubuntu.com/ubuntu The system can't find 'Raring' on the ubuntu archive website. I think they've taken it off. I found Debootstrap has script files or something in its directory (/usr/share/debootstrap/scripts). For ubuntu, the script files seem to be identical. So I copied the file for Raring and renamed it 'saucy'. I then ran: root@host# debootstrap --arch amd64 saucy /mnt/deboot http://archive.ubuntu.com/ubuntu and the system was able to download all the files for saucy. I didn't rename it 'utopic' for the latest ubuntu stable release because I wasn't sure if the correct script file for utopic had been amended in some way.

You shouldn't have to rename any of the scripts. Most of them are just symlinks to the gutsy script. I'm assuming that script should allow you to install any of the Ubuntu versions available at http://archive.ubuntu.com/ubuntu/. I haven't spent a lot of time using debootstrap to install Ubuntu. I know the latest version is utopic, and the latest LTS is trusty, soon to be vivid.

Originally Posted by Higgsboson No, I'm afraid I didn't. That's probably where I went wrong. If I wanted to use debootstrap to install a stable version of Ubuntu saucy, would the command be: root@host# debootstrap --include linux-image-amd64,grub-pc,locales --arch amd64 saucy /mnt/deboot http://archive.ubuntu.com/ubuntu Also, if I wanted to install Ubuntu utopic, could I do this?: root@host# cp /usr/share/debootstrap/scripts/raring /usr/share/debootstrap/scripts/utopic root@host# debootstrap --include linux-image-amd64,grub-pc,locales --arch amd64 utopic /mnt/deboot http://archive.ubuntu.com/ubuntu

Debian uses linux-image-amd64 as a meta-package name for it's latest kernel. Ubuntu uses linux-image-generic instead.

Originally Posted by Higgsboson Finally, I think the link to the archives has changed from 'http://archive.ubuntu.com/ubuntu' to 'http://archive.ubuntu.com/ubuntu/dists'

You should always use http://archive.ubuntu.com/ubuntu as the repository for Ubuntu, at least for current releases. I'm not sure what Ubuntu does with older releases. With Debian, you can use branch names instead of code names. If you weren't sure if wheezy or jessie was Debian's current stable release, you could simply specify stable instead.

Originally Posted by Higgsboson Yes, where is the /etc/fstab located for inputting the UUID? I'm getting confused between the /etc/fstab of the host system, and the /etc/fstab presumably being created in the mounted 'deboot' directory.

Assuming you've mounted /dev/sda3 on /mnt/deboot, then you'll want to add the UUID of /dev/sda3 to /mnt/deboot/etc/fstab

Originally Posted by colorpurple21859 from the howto you initially followed. Binding the virtual filesystems. Until your new install is booting on it's own, we'll borrow these from the host. Code: root@host# mount -o bind /dev /mnt/deboot/dev root@host# mount -o bind /proc /mnt/deboot/proc root@host# mount -o bind /sys /mnt/deboot/sys Continuing the installation within chroot Entering the chroot environment: Code: root@host# chroot /mnt/deboot /bin/bash

I'm going to do a re-install with the kernel included this time.
This way I can download the latest utopic version. Thank you.

Originally Posted by replica9000 You shouldn't have to rename any of the scripts. Most of them are just symlinks to the gutsy script. I'm assuming that script should allow you to install any of the Ubuntu versions available at http://archive.ubuntu.com/ubuntu/. I haven't spent a lot of time using debootstrap to install Ubuntu. I know the latest version is utopic, and the latest LTS is trusty, soon to be vivid.

Ok, in that case I'll try and install utopic using debootstrap.

Debian uses linux-image-amd64 as a meta-package name for it's latest kernel. Ubuntu uses linux-image-generic instead.

Excellent. I'll try that.

You should always use http://archive.ubuntu.com/ubuntu as the repository for Ubuntu, at least for current releases. I'm not sure what Ubuntu does with older releases. With Debian, you can use branch names instead of code names. If you weren't sure if wheezy or jessie was Debian's current stable release, you could simply specify stable instead.

I'll try the link as you say for the current release.

Assuming you've mounted /dev/sda3 on /mnt/deboot, then you'll want to add the UUID of /dev/sda3 to /mnt/deboot/etc/fstab

That's exactly what I wanted to know. Thank you very much.
Will let you know how I get on!

The problem that you're eperiencing is due to the fact that you are trying to install packages that are from a different repo when you chroot into system it already has it's sources.list. You don't need to tell the system which repo to install from.
You can do

apt-cache search linux-image apt-get install linux-image

That command does depend on how ubuntu lists it's kernel.