problems with upgrade 11.

You can use the liveCD to reinstall grub2. This may help

how do I do that (sorry - too new)

On Wed, May 18, 2011 at 11:55 AM, actionparsnip <
<email address hidden>> wrote:

> Your question #158021 on Ubuntu changed:
> https://answers.launchpad.net/ubuntu/+question/158021
>
> Status: Open => Answered
>
> actionparsnip proposed the following answer:
> You can use the liveCD to reinstall grub2. This may help
>
> --
> If this answers your question, please go to the following page to let us
> know that it is solved:
> https://answers.launchpad.net/ubuntu/+question/158021/+confirm?answer_id=0
>
> If you still need help, you can reply to this email or go to the
> following page to enter your feedback:
> https://answers.launchpad.net/ubuntu/+question/158021
>
> You received this question notification because you asked the question.
>

how do I reinstall grub 2 from the live cd?

On Wed, May 18, 2011 at 12:01 PM, Jenny Ember <
<email address hidden>> wrote:

> Your question #158021 on Ubuntu changed:
> https://answers.launchpad.net/ubuntu/+question/158021
>
> Status: Answered => Open
>
> You are still having a problem:
> how do I do that (sorry - too new)
>
> On Wed, May 18, 2011 at 11:55 AM, actionparsnip <
> <email address hidden>> wrote:
>
> > Your question #158021 on Ubuntu changed:
> > https://answers.launchpad.net/ubuntu/+question/158021
> >
> > Status: Open => Answered
> >
> > actionparsnip proposed the following answer:
> > You can use the liveCD to reinstall grub2. This may help
> >
> > --
> > If this answers your question, please go to the following page to let us
> > know that it is solved:
> >
> https://answers.launchpad.net/ubuntu/+question/158021/+confirm?answer_id=0
> >
> > If you still need help, you can reply to this email or go to the
> > following page to enter your feedback:
> > https://answers.launchpad.net/ubuntu/+question/158021
> >
> > You received this question notification because you asked the question.
> >
>
> --
> You received this question notification because you asked the question.
>

http://www.webtechquery.com/index.php/2010/04/install-grub2-from-live-cd/

To run a command as administrator (user "root"), use "sudo <command>".
See "man sudo_root" for details.

ubuntu@ubuntu:~$ sudo fdisk -l

Disk /dev/sda: 320.1 GB, 320072933376 bytes
255 heads, 63 sectors/track, 38913 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000995b6

   Device Boot Start End Blocks Id System
/dev/sda1 * 1 37384 300281856 83 Linux
/dev/sda2 37384 38914 12286977 5 Extended
/dev/sda5 37384 38914 12286976 82 Linux swap / Solaris
ubuntu@ubuntu:~$ sudo mount /dev/sda1 /mnt
ubuntu@ubuntu:~$ sudo chroot /mnt
root@ubuntu:/# grub-install /dev/sda
/usr/sbin/grub-probe: error: cannot find a device for /boot/grub (is /dev
mounted?).
root@ubuntu:/# grub-install /dev/sda1
/usr/sbin/grub-probe: error: cannot find a device for /boot/grub (is /dev
mounted?).
root@ubuntu:/#

************This is what my terminal says.... what am I doing
wrong?***********

This is the terminal output from the link you sent me to fix this - I do not
understand what I am doing or what is going on. Please help!

ubuntu@ubuntu:~$ sudo fdisk -l

Disk /dev/sda: 320.1 GB, 320072933376 bytes
255 heads, 63 sectors/track, 38913 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000995b6

   Device Boot Start End Blocks Id System
/dev/sda1 * 1 37384 300281856 83 Linux
/dev/sda2 37384 38914 12286977 5 Extended
/dev/sda5 37384 38914 12286976 82 Linux swap / Solaris
ubuntu@ubuntu:~$ sudo mount /dev/sda1 /mnt
mount: /dev/sda1 already mounted or /mnt busy
mount: according to mtab, /dev/sda1 is already mounted on /mnt
ubuntu@ubuntu:~$ sudo mount -bind /dev /mnt/dev
mount: invalid option -- 'b'
Usage: mount -V : print version
       mount -h : print this help
       mount : list mounted filesystems
       mount -l : idem, including volume labels
So far the informational part. Next the mounting.
The command is `mount [-t fstype] something somewhere'.
Details found in /etc/fstab may be omitted.
       mount -a [-t|-O] ... : mount all stuff from /etc/fstab
       mount device : mount device at the known place
       mount directory : mount known device here
       mount -t type dev dir : ordinary mount command
Note that one does not really mount a device, one mounts
a filesystem (of the given type) found on the device.
One can also mount an already visible directory tree elsewhere:
       mount --bind olddir newdir
or move a subtree:
       mount --move olddir newdir
One can change the type of mount containing the directory dir:
       mount --make-shared dir
       mount --make-slave dir
       mount --make-private dir
       mount --make-unbindable dir
One can change the type of all the mounts in a mount subtree
containing the directory dir:
       mount --make-rshared dir
       mount --make-rslave dir
       mount --make-rprivate dir
       mount --make-runbindable dir
A device can be given by name, say /dev/hda1 or /dev/cdrom,
or by label, using -L label or by uuid, using -U uuid .
Other options: [-nfFrsvw] [-o options] [-p passwdfd].
For many more details, say man 8 mount .
ubuntu@ubuntu:~$ sudo mount -bind /proc /mnt/proc
mount: invalid option -- 'b'
Usage: mount -V : print version
       mount -h : print this help
       mount : list mounted filesystems
       mount -l : idem, including volume labels
So far the informational part. Next the mounting.
The command is `mount [-t fstype] something somewhere'.
Details found in /etc/fstab may be omitted.
       mount -a [-t|-O] ... : mount all stuff from /etc/fstab
       mount device : mount device at the known place
       mount directory : mount known device here
       mount -t type dev dir : ordinary mount command
Note that one does not really mount a device, one mounts
a filesystem (of the given type) found on the device.
One can also mount an already visible directory tree elsewhere:
       mount --bind olddir newdir
or move a subtree:
       mount --move olddir newdir
One can change the type of mount containing the directory dir:
       mount --make-shared dir
       mount --make-slave dir
       mount --make-private dir
       mount --make-unbindable dir
One can change the type of all the mounts in a mount subtree
containing the directory dir:
       mount --make-rshared dir
       mount --make-rslave dir
       mount --make-rprivate dir
       mount --make-runbindable dir
A device can be given by name, say /dev/hda1 or /dev/cdrom,
or by label, using -L label or by uuid, using -U uuid .
Other options: [-nfFrsvw] [-o options] [-p passwdfd].
For many more details, say man 8 mount .
ubuntu@ubuntu:~$ sudo chroot /mnt
root@ubuntu:/# grub-install /dev/sda1
/usr/sbin/grub-probe: error: cannot find a device for /boot/grub (is /dev
mounted?).
root@ubuntu:/# grub-install -recheck /dev/sda1
Unrecognized option `-recheck'
Usage: grub-install [OPTION] install_device
Install GRUB on your drive.

  -h, --help print this message and exit
  -v, --version print the version information and exit
  --modules=MODULES pre-load specified modules MODULES
  --boot-directory=DIR install GRUB images under the directory DIR/grub
                          instead of the /boot/grub directory
  --grub-setup=FILE use FILE as grub-setup
  --grub-mkimage=FILE use FILE as grub-mkimage
  --grub-mkrelpath=FILE use FILE as grub-mkrelpath
  --grub-mkdevicemap=FILE use FILE as grub-mkdevicemap
  --grub-probe=FILE use FILE as grub-probe
  --no-floppy do not probe any floppy drive
  --allow-floppy Make the drive also bootable as floppy
                          (default for fdX devices). May break on some
BIOSes.
  --recheck probe a device map even if it already exists
  --force install even if problems are detected
  --disk-module=MODULE disk module to use

INSTALL_DEVICE can be a GRUB device name or a system device filename.

grub-install copies GRUB images into /boot/grub, and uses grub-setup
to install grub into the boot sector.

Report bugs to <email address hidden>.
root@ubuntu:/# grub-install /dev/sda
/usr/sbin/grub-probe: error: cannot find a device for /boot/grub (is /dev
mounted?).
root@ubuntu:/# sudo umount /mnt/dev
sudo: unable to resolve host ubuntu
umount: /mnt/dev: not found
root@ubuntu:/# sudo umount /mnt/proc
sudo: unable to resolve host ubuntu
umount: /mnt/proc: not found
root@ubuntu:/# sudo umount /mnt
sudo: unable to resolve host ubuntu
umount: /mnt: not mounted
root@ubuntu:/#

The output of running "fdisk -l" indicates that your root filesystem is in the /dev/sda1 partition, which is exactly like the example given at http://www.webtechquery.com/index.php/2010/04/install-grub2-from-live-cd/. Therefore, you can run the commands exactly as stated there (starting with "sudo mount /dev/sda1 /mnt").

***This is what I get.... it doesn't seem to be loading grub2 ???? at least
that is what I read - correct?????***********

root@ubuntu:/# grub-install /dev/sda1
/usr/sbin/grub-probe: error: cannot find a device for /boot/grub (is /dev
mounted?).
root@ubuntu:/# grub-install –recheck /dev/sda1
More than one install_devices?
Usage: grub-install [OPTION] install_device
Install GRUB on your drive.

  -h, --help print this message and exit
  -v, --version print the version information and exit
  --modules=MODULES pre-load specified modules MODULES
  --boot-directory=DIR install GRUB images under the directory DIR/grub
                          instead of the /boot/grub directory
  --grub-setup=FILE use FILE as grub-setup
  --grub-mkimage=FILE use FILE as grub-mkimage
  --grub-mkrelpath=FILE use FILE as grub-mkrelpath
  --grub-mkdevicemap=FILE use FILE as grub-mkdevicemap
  --grub-probe=FILE use FILE as grub-probe
  --no-floppy do not probe any floppy drive
  --allow-floppy Make the drive also bootable as floppy
                          (default for fdX devices). May break on some
BIOSes.
  --recheck probe a device map even if it already exists
  --force install even if problems are detected
  --disk-module=MODULE disk module to use

INSTALL_DEVICE can be a GRUB device name or a system device filename.

grub-install copies GRUB images into /boot/grub, and uses grub-setup
to install grub into the boot sector.

Report bugs to <email address hidden>.
root@ubuntu:/#

It does not look like you ran all these commands first, in this order:

sudo mount /dev/sda1 /mnt
sudo mount –bind /dev /mnt/dev
sudo mount –bind /proc /mnt/proc
sudo chroot /mnt

Did you?

yes. copied n pasted commands so no typos, did this about 5 times. Upon
reboot the command line runs through a 'system check' everything is ok but
one fails and it zips past it so I cannot see, I think it was something
about error reports.

On Wed, May 18, 2011 at 2:25 PM, Eliah Kagan <
<email address hidden>> wrote:

> Your question #158021 on grub2 in Ubuntu changed:
> https://answers.launchpad.net/ubuntu/+source/grub2/+question/158021
>
> Status: Open => Needs information
>
> Eliah Kagan requested more information:
> It does not look like you ran all these commands first, in this order:
>
> sudo mount /dev/sda1 /mnt
> sudo mount –bind /dev /mnt/dev
> sudo mount –bind /proc /mnt/proc
> sudo chroot /mnt
>
> Did you?
>
> --
> To answer this request for more information, you can either reply to
> this email or enter your reply at the following page:
> https://answers.launchpad.net/ubuntu/+source/grub2/+question/158021
>
> You received this question notification because you asked the question.
>

when I copy in "*sudo mount –bind /proc /mnt/proc" and press enter, nothing
happens.

*
On Wed, May 18, 2011 at 2:35 PM, Jenny Ember <
<email address hidden>> wrote:

> Your question #158021 on grub2 in Ubuntu changed:
> https://answers.launchpad.net/ubuntu/+source/grub2/+question/158021
>
> Status: Needs information => Open
>
> You gave more information on the question:
> yes. copied n pasted commands so no typos, did this about 5 times. Upon
> reboot the command line runs through a 'system check' everything is ok but
> one fails and it zips past it so I cannot see, I think it was something
> about error reports.
>
>
> On Wed, May 18, 2011 at 2:25 PM, Eliah Kagan <
> <email address hidden>> wrote:
>
> > Your question #158021 on grub2 in Ubuntu changed:
> > https://answers.launchpad.net/ubuntu/+source/grub2/+question/158021
> >
> > Status: Open => Needs information
> >
> > Eliah Kagan requested more information:
> > It does not look like you ran all these commands first, in this order:
> >
> > sudo mount /dev/sda1 /mnt
> > sudo mount –bind /dev /mnt/dev
> > sudo mount –bind /proc /mnt/proc
> > sudo chroot /mnt
> >
> > Did you?
> >
> > --
> > To answer this request for more information, you can either reply to
> > this email or enter your reply at the following page:
> > https://answers.launchpad.net/ubuntu/+source/grub2/+question/158021
> >
> > You received this question notification because you asked the question.
> >
>
> --
> You received this question notification because you asked the question.
>

"yes. copied n pasted commands so no typos, did this about 5 times."

And you always get "/usr/sbin/grub-probe: error: cannot find a device for /boot/grub (is /dev
mounted?)." when you run "grub-install /dev/sda1"?

*****This is the full procedure again:********

ubuntu@ubuntu:~$ sudo mount /dev/sda1 /mnt
mount: /dev/sda1 already mounted or /mnt busy
mount: according to mtab, /dev/sda1 is already mounted on /mnt
ubuntu@ubuntu:~$ sudo mount –bind /dev /mnt/dev
Usage: mount -V : print version
       mount -h : print this help
       mount : list mounted filesystems
       mount -l : idem, including volume labels
So far the informational part. Next the mounting.
The command is `mount [-t fstype] something somewhere'.
Details found in /etc/fstab may be omitted.
       mount -a [-t|-O] ... : mount all stuff from /etc/fstab
       mount device : mount device at the known place
       mount directory : mount known device here
       mount -t type dev dir : ordinary mount command
Note that one does not really mount a device, one mounts
a filesystem (of the given type) found on the device.
One can also mount an already visible directory tree elsewhere:
       mount --bind olddir newdir
or move a subtree:
       mount --move olddir newdir
One can change the type of mount containing the directory dir:
       mount --make-shared dir
       mount --make-slave dir
       mount --make-private dir
       mount --make-unbindable dir
One can change the type of all the mounts in a mount subtree
containing the directory dir:
       mount --make-rshared dir
       mount --make-rslave dir
       mount --make-rprivate dir
       mount --make-runbindable dir
A device can be given by name, say /dev/hda1 or /dev/cdrom,
or by label, using -L label or by uuid, using -U uuid .
Other options: [-nfFrsvw] [-o options] [-p passwdfd].
For many more details, say man 8 mount .
ubuntu@ubuntu:~$ sudo mount –bind /proc /mnt/proc
Usage: mount -V : print version
       mount -h : print this help
       mount : list mounted filesystems
       mount -l : idem, including volume labels
So far the informational part. Next the mounting.
The command is `mount [-t fstype] something somewhere'.
Details found in /etc/fstab may be omitted.
       mount -a [-t|-O] ... : mount all stuff from /etc/fstab
       mount device : mount device at the known place
       mount directory : mount known device here
       mount -t type dev dir : ordinary mount command
Note that one does not really mount a device, one mounts
a filesystem (of the given type) found on the device.
One can also mount an already visible directory tree elsewhere:
       mount --bind olddir newdir
or move a subtree:
       mount --move olddir newdir
One can change the type of mount containing the directory dir:
       mount --make-shared dir
       mount --make-slave dir
       mount --make-private dir
       mount --make-unbindable dir
One can change the type of all the mounts in a mount subtree
containing the directory dir:
       mount --make-rshared dir
       mount --make-rslave dir
       mount --make-rprivate dir
       mount --make-runbindable dir
A device can be given by name, say /dev/hda1 or /dev/cdrom,
or by label, using -L label or by uuid, using -U uuid .
Other options: [-nfFrsvw] [-o options] [-p passwdfd].
For many more details, say man 8 mount .
ubuntu@ubuntu:~$ sudo mount –bind /proc /mnt/proc
Usage: mount -V : print version
       mount -h : print this help
       mount : list mounted filesystems
       mount -l : idem, including volume labels
So far the informational part. Next the mounting.
The command is `mount [-t fstype] something somewhere'.
Details found in /etc/fstab may be omitted.
       mount -a [-t|-O] ... : mount all stuff from /etc/fstab
       mount device : mount device at the known place
       mount directory : mount known device here
       mount -t type dev dir : ordinary mount command
Note that one does not really mount a device, one mounts
a filesystem (of the given type) found on the device.
One can also mount an already visible directory tree elsewhere:
       mount --bind olddir newdir
or move a subtree:
       mount --move olddir newdir
One can change the type of mount containing the directory dir:
       mount --make-shared dir
       mount --make-slave dir
       mount --make-private dir
       mount --make-unbindable dir
One can change the type of all the mounts in a mount subtree
containing the directory dir:
       mount --make-rshared dir
       mount --make-rslave dir
       mount --make-rprivate dir
       mount --make-runbindable dir
A device can be given by name, say /dev/hda1 or /dev/cdrom,
or by label, using -L label or by uuid, using -U uuid .
Other options: [-nfFrsvw] [-o options] [-p passwdfd].
For many more details, say man 8 mount .
ubuntu@ubuntu:~$ sudo mount –bind /proc /mnt/proc
Usage: mount -V : print version
       mount -h : print this help
       mount : list mounted filesystems
       mount -l : idem, including volume labels
So far the informational part. Next the mounting.
The command is `mount [-t fstype] something somewhere'.
Details found in /etc/fstab may be omitted.
       mount -a [-t|-O] ... : mount all stuff from /etc/fstab
       mount device : mount device at the known place
       mount directory : mount known device here
       mount -t type dev dir : ordinary mount command
Note that one does not really mount a device, one mounts
a filesystem (of the given type) found on the device.
One can also mount an already visible directory tree elsewhere:
       mount --bind olddir newdir
or move a subtree:
       mount --move olddir newdir
One can change the type of mount containing the directory dir:
       mount --make-shared dir
       mount --make-slave dir
       mount --make-private dir
       mount --make-unbindable dir
One can change the type of all the mounts in a mount subtree
containing the directory dir:
       mount --make-rshared dir
       mount --make-rslave dir
       mount --make-rprivate dir
       mount --make-runbindable dir
A device can be given by name, say /dev/hda1 or /dev/cdrom,
or by label, using -L label or by uuid, using -U uuid .
Other options: [-nfFrsvw] [-o options] [-p passwdfd].
For many more details, say man 8 mount .
ubuntu@ubuntu:~$
ubuntu@ubuntu:~$ sudo mount –bind /proc /mnt/proc
Usage: mount -V : print version
       mount -h : print this help
       mount : list mounted filesystems
       mount -l : idem, including volume labels
So far the informational part. Next the mounting.
The command is `mount [-t fstype] something somewhere'.
Details found in /etc/fstab may be omitted.
       mount -a [-t|-O] ... : mount all stuff from /etc/fstab
       mount device : mount device at the known place
       mount directory : mount known device here
       mount -t type dev dir : ordinary mount command
Note that one does not really mount a device, one mounts
a filesystem (of the given type) found on the device.
One can also mount an already visible directory tree elsewhere:
       mount --bind olddir newdir
or move a subtree:
       mount --move olddir newdir
One can change the type of mount containing the directory dir:
       mount --make-shared dir
       mount --make-slave dir
       mount --make-private dir
       mount --make-unbindable dir
One can change the type of all the mounts in a mount subtree
containing the directory dir:
       mount --make-rshared dir
       mount --make-rslave dir
       mount --make-rprivate dir
       mount --make-runbindable dir
A device can be given by name, say /dev/hda1 or /dev/cdrom,
or by label, using -L label or by uuid, using -U uuid .
Other options: [-nfFrsvw] [-o options] [-p passwdfd].
For many more details, say man 8 mount .
ubuntu@ubuntu:~$ sudo chroot /mnt
root@ubuntu:/# sudo chroot /mnt
sudo: unable to resolve host ubuntu
chroot: failed to run command `/bin/bash': No such file or directory
root@ubuntu:/# grub-install -recheck /dev/sda1
Unrecognized option `-recheck'
Usage: grub-install [OPTION] install_device
Install GRUB on your drive.

  -h, --help print this message and exit
  -v, --version print the version information and exit
  --modules=MODULES pre-load specified modules MODULES
  --boot-directory=DIR install GRUB images under the directory DIR/grub
                          instead of the /boot/grub directory
  --grub-setup=FILE use FILE as grub-setup
  --grub-mkimage=FILE use FILE as grub-mkimage
  --grub-mkrelpath=FILE use FILE as grub-mkrelpath
  --grub-mkdevicemap=FILE use FILE as grub-mkdevicemap
  --grub-probe=FILE use FILE as grub-probe
  --no-floppy do not probe any floppy drive
  --allow-floppy Make the drive also bootable as floppy
                          (default for fdX devices). May break on some
BIOSes.
  --recheck probe a device map even if it already exists
  --force install even if problems are detected
  --disk-module=MODULE disk module to use

INSTALL_DEVICE can be a GRUB device name or a system device filename.

grub-install copies GRUB images into /boot/grub, and uses grub-setup
to install grub into the boot sector.

Report bugs to <email address hidden>.
root@ubuntu:/# sudo umount /mnt dev
sudo: unable to resolve host ubuntu
umount: /mnt: not mounted
umount: /dev: not mounted
root@ubuntu:/# sudo umount /mnt proc
sudo: unable to resolve host ubuntu
umount: /mnt: not mounted
umount: /proc: not mounted
root@ubuntu:/# sudo umount /mnt
sudo: unable to resolve host ubuntu
umount: /mnt: not mounted
root@ubuntu:/#

Sorry, I didn't see what you'd posted a couple minutes before my post (i.e., the post of yours I hadn't seen is the one numbered 11 at https://answers.launchpad.net/ubuntu/+source/grub2/+question/158021). I will reply shortly.

You said: "when I copy in "*sudo mount –bind /proc /mnt/proc" and press enter, nothing happens."

If you see nothing happen when you run that command, it means the command was successful, and you should move on to the subsequent command.

However, it seems that you've been trying to run some of these commands inside the chroot, and some outside the chroot. Please run the "exit" command, repeatedly, until your Terminal window disappears. Then open a new Terminal window and run:

mount

Then select all the text in that Terminal window (Edit > Select All), copy it to the clipboard (Edit > Copy), and paste it here. That will give me the necessary information to know exactly which steps have been performed successfully already; then I'll provide detailed instructions for performing the remaining steps.

When running commands, especially if they are complex, I recommend that you copy and paste them rather than attempting to retype them. I've read back through everything you've posted, and it seems that the source of the problems you've been experiencing following the instructions at http://www.webtechquery.com/index.php/2010/04/install-grub2-from-live-cd/ is that you mistyped the command to mount /dev (you had only one - in front of "bind" instead of the required two).

1.
To run a command as administrator (user "root"), use "sudo <command>".
See "man sudo_root" for details.

ubuntu@ubuntu:~$ sudo mount /dev/sda1 /mnt
ubuntu@ubuntu:~$ sudo mount –bind /dev /mnt/dev
Usage: mount -V : print version
       mount -h : print this help
       mount : list mounted filesystems
       mount -l : idem, including volume labels
So far the informational part. Next the mounting.
The command is `mount [-t fstype] something somewhere'.
Details found in /etc/fstab may be omitted.
       mount -a [-t|-O] ... : mount all stuff from /etc/fstab
       mount device : mount device at the known place
       mount directory : mount known device here
       mount -t type dev dir : ordinary mount command
Note that one does not really mount a device, one mounts
a filesystem (of the given type) found on the device.
One can also mount an already visible directory tree elsewhere:
       mount --bind olddir newdir
or move a subtree:
       mount --move olddir newdir
One can change the type of mount containing the directory dir:
       mount --make-shared dir
       mount --make-slave dir
       mount --make-private dir
       mount --make-unbindable dir
One can change the type of all the mounts in a mount subtree
containing the directory dir:
       mount --make-rshared dir
       mount --make-rslave dir
       mount --make-rprivate dir
       mount --make-runbindable dir
A device can be given by name, say /dev/hda1 or /dev/cdrom,
or by label, using -L label or by uuid, using -U uuid .
Other options: [-nfFrsvw] [-o options] [-p passwdfd].
For many more details, say man 8 mount .
ubuntu@ubuntu:~$ sudo mount –bind /proc /mnt/proc
Usage: mount -V : print version
       mount -h : print this help
       mount : list mounted filesystems
       mount -l : idem, including volume labels
So far the informational part. Next the mounting.
The command is `mount [-t fstype] something somewhere'.
Details found in /etc/fstab may be omitted.
       mount -a [-t|-O] ... : mount all stuff from /etc/fstab
       mount device : mount device at the known place
       mount directory : mount known device here
       mount -t type dev dir : ordinary mount command
Note that one does not really mount a device, one mounts
a filesystem (of the given type) found on the device.
One can also mount an already visible directory tree elsewhere:
       mount --bind olddir newdir
or move a subtree:
       mount --move olddir newdir
One can change the type of mount containing the directory dir:
       mount --make-shared dir
       mount --make-slave dir
       mount --make-private dir
       mount --make-unbindable dir
One can change the type of all the mounts in a mount subtree
containing the directory dir:
       mount --make-rshared dir
       mount --make-rslave dir
       mount --make-rprivate dir
       mount --make-runbindable dir
A device can be given by name, say /dev/hda1 or /dev/cdrom,
or by label, using -L label or by uuid, using -U uuid .
Other options: [-nfFrsvw] [-o options] [-p passwdfd].
For many more details, say man 8 mount .
ubuntu@ubuntu:~$ sudo mount - –bind /proc /mnt/proc
Usage: mount -V : print version
       mount -h : print this help
       mount : list mounted filesystems
       mount -l : idem, including volume labels
So far the informational part. Next the mounting.
The command is `mount [-t fstype] something somewhere'.
Details found in /etc/fstab may be omitted.
       mount -a [-t|-O] ... : mount all stuff from /etc/fstab
       mount device : mount device at the known place
       mount directory : mount known device here
       mount -t type dev dir : ordinary mount command
Note that one does not really mount a device, one mounts
a filesystem (of the given type) found on the device.
One can also mount an already visible directory tree elsewhere:
       mount --bind olddir newdir
or move a subtree:
       mount --move olddir newdir
One can change the type of mount containing the directory dir:
       mount --make-shared dir
       mount --make-slave dir
       mount --make-private dir
       mount --make-unbindable dir
One can change the type of all the mounts in a mount subtree
containing the directory dir:
       mount --make-rshared dir
       mount --make-rslave dir
       mount --make-rprivate dir
       mount --make-runbindable dir
A device can be given by name, say /dev/hda1 or /dev/cdrom,
or by label, using -L label or by uuid, using -U uuid .
Other options: [-nfFrsvw] [-o options] [-p passwdfd].
For many more details, say man 8 mount .
ubuntu@ubuntu:~$

*********mount then exit*************

2.
ubuntu@ubuntu:~$ sudo chroot /mnt
root@ubuntu:/# grub-install /dev/sda1
/usr/sbin/grub-probe: error: cannot find a device for /boot/grub (is /dev
mounted?).
root@ubuntu:/# grub-install -recheck /dev/sda1
Unrecognized option `-recheck'
Usage: grub-install [OPTION] install_device
Install GRUB on your drive.

  -h, --help print this message and exit
  -v, --version print the version information and exit
  --modules=MODULES pre-load specified modules MODULES
  --boot-directory=DIR install GRUB images under the directory DIR/grub
                          instead of the /boot/grub directory
  --grub-setup=FILE use FILE as grub-setup
  --grub-mkimage=FILE use FILE as grub-mkimage
  --grub-mkrelpath=FILE use FILE as grub-mkrelpath
  --grub-mkdevicemap=FILE use FILE as grub-mkdevicemap
  --grub-probe=FILE use FILE as grub-probe
  --no-floppy do not probe any floppy drive
  --allow-floppy Make the drive also bootable as floppy
                          (default for fdX devices). May break on some
BIOSes.
  --recheck probe a device map even if it already exists
  --force install even if problems are detected
  --disk-module=MODULE disk module to use

INSTALL_DEVICE can be a GRUB device name or a system device filename.

grub-install copies GRUB images into /boot/grub, and uses grub-setup
to install grub into the boot sector.

Report bugs to <email address hidden>.
root@ubuntu:/#

***********chroot, grub install then exit*******

I am guessing this is where the error is.... I stopped here, have not
rebooted yet till I hear from you. Also as far as the ' - ' this is exactly
how the info is given at that link, have copied and pasted what it has said.

<----------- is sooooo freaking confused.... is there another way??? I
know a little DOS but no LINUX commands at all, the terminal is very
confusing for me at this stage. All help is greatly appreciated. thank you!

I have done a little research and from what I can see, Grub may not be my problem. it seems as tho my original 'drive' is no longer there, ie: the upgrade wiped it out (?????). I am not sure if I am on the right track here, nor do I know how to tell - just wondering if that is possible???. Is considering reinstalling ubuntu 10 (my original) from scratch (dreaded tho, lost some recent files not yet backed up). Would really like to problem solve this, as is a good learning curve for me and really need my pc up and running correctly. Please help!

"<----------- is sooooo freaking confused.... is there another way??? I"

I suppose it's simpler if you reboot and start over. So please go ahead and do that. This time, you can connect to the Internet from the live CD system (if you hadn't already), and **copy and paste** the commands exactly, so that you don't type them incorrectly. You don't need to know any commands, because you're just following detailed instructions.

"I have done a little research and from what I can see, Grub may not be my problem."

One way to find that out is to reinstall GRUB2 to the Master Boot Record and see what happens. There may be other ways to find that out, but you'll have to be specific about what you looked into that made you think that GRUB2 is not the problem.

"it seems as tho my original 'drive' is no longer there, ie: the upgrade wiped it out"

What do you mean when you say your "original" drive?

The directions I provided about how to follow the instructions at http://www.webtechquery.com/index.php/2010/04/install-grub2-from-live-cd/ (i.e., to run the commands listed there exactly as they are, starting with "sudo mount /dev/sda1 /mnt") were based on an actual examination of your disk (i.e., interpreting the output of "fdisk -l"). There is no reason to think they will not be effective at reinstalling GRUB2 to the Master Boot Record. (And the Master Boot Record is just the name for the first 512 bytes of your disk--it's definitely still there.)

@Jenny Ember
Quite some time has passed, so I'm not sure if you can still use help, but I just figured out what was going wrong here.

The guide I linked to for reinstalling GRUB2 to your Master Boot Record (http://www.webtechquery.com/index.php/2010/04/install-grub2-from-live-cd/) shows the following commands with en-dashes (http://en.wikipedia.org/wiki/En-dash#En_dash):

sudo mount –bind /dev /mnt/dev
sudo mount –bind /proc /mnt/proc

grub-install –recheck /dev/sda

But that is wrong; the --bind and --recheck flags should always be preceded by two normal short dashes in succession. So those commands should instead read:

sudo mount --bind /dev /mnt/dev
sudo mount --bind /proc /mnt/proc

grub-install --recheck /dev/sda

If you are still experiencing this problem, that should enable you to solve it. There are, alternatively, some different procedures that usually work, given at https://help.ubuntu.com/community/Grub2#Methods%20of%20Reinstalling. The first procedure, which is very simple to use, was not documented there at the time you originally asked your question. I apologize for not posting here about it, at the time it originally became available.

As always, please feel free to post a reply here if you need more help with this problem, or to create a new question (https://answers.launchpad.net/ubuntu/+addquestion) if you need help or advice with any other Ubuntu-related situation.

thank you for your assistance, yes this was some time ago and I ended up
totally re-installing ubuntu from scratch. It had been pointed out
previously by others about the dashes but this still did not work. I was
told that the upgrade may not be compatible with some video cards etc and as
I have a laptop, not an easy change over!.
I am still ecstatically happy that I found Linux and will never return to
windows again.
Once again, thank you for your help.

On Sun, Aug 7, 2011 at 7:16 AM, Eliah Kagan <
<email address hidden>> wrote:

> Your question #158021 on grub2 in Ubuntu changed:
> https://answers.launchpad.net/ubuntu/+source/grub2/+question/158021
>
> Eliah Kagan proposed the following answer:
> @Jenny Ember
> Quite some time has passed, so I'm not sure if you can still use help, but
> I just figured out what was going wrong here.
>
> The guide I linked to for reinstalling GRUB2 to your Master Boot Record
> (http://www.webtechquery.com/index.php/2010/04/install-grub2-from-live-
> cd/) shows the following commands with en-dashes
> (http://en.wikipedia.org/wiki/En-dash#En_dash):
>
> sudo mount –bind /dev /mnt/dev
> sudo mount –bind /proc /mnt/proc
>
> grub-install –recheck /dev/sda
>
> But that is wrong; the --bind and --recheck flags should always be
> preceded by two normal short dashes in succession. So those commands
> should instead read:
>
> sudo mount --bind /dev /mnt/dev
> sudo mount --bind /proc /mnt/proc
>
> grub-install --recheck /dev/sda
>
> If you are still experiencing this problem, that should enable you to
> solve it. There are, alternatively, some different procedures that
> usually work, given at
> https://help.ubuntu.com/community/Grub2#Methods%20of%20Reinstalling. The
> first procedure, which is very simple to use, was not documented there
> at the time you originally asked your question. I apologize for not
> posting here about it, at the time it originally became available.
>
> As always, please feel free to post a reply here if you need more help
> with this problem, or to create a new question
> (https://answers.launchpad.net/ubuntu/+addquestion) if you need help or
> advice with any other Ubuntu-related situation.
>
> --
> If this answers your question, please go to the following page to let us
> know that it is solved:
>
> https://answers.launchpad.net/ubuntu/+source/grub2/+question/158021/+confirm?answer_id=19
>
> If you still need help, you can reply to this email or go to the
> following page to enter your feedback:
> https://answers.launchpad.net/ubuntu/+source/grub2/+question/158021
>
> You received this question notification because you asked the question.
>

I'm glad you got your problem solved, though sorry I wasn't able to help you solve it quickly at the time that it arose.

Since you are no longer experiencing this problem, please mark this question as Solved (you can do that at https://answers.launchpad.net/ubuntu/+source/grub2/+question/158021).