I solved one problem only to get a follow-up problem.
I have Win 7 and I tried loading 32-bit Ubuntu 11 on the system. It kept failing. I figured out due to another post here that it was because my 3TB drive was too much for it. After repartitioning the HD my friend and I managed to load it onto the system, but it was buggy when it came to updates, so I tried upgrading to Ubuntu 12 (32 bit), but I was still having the too many bits problem.
Plus now it seems like something is wrong with loading anything. Both Win 7 and Ubuntu are there, but neither will load. I get a mostly blank screen with the words:
**error: no such device: 3a0d062c-5f69-4635-9c79-3814c7d5bbed
grub rescue>**
(with what appears to be a command prompt)
I loaded U12, 64 bit version, in the hopes it would repair the boot issue. Everything appeared to install much more smoothly this time and update nicely, but there was no luck in the boot department. Again, all the data is there, but I'm still getting the black screen when I boot up. I've also tried the repair function in Win 7 with the install disk and no love. I can run from a liveCD, but that's still not getting me Win 7 or an installed version of Ubuntu.
I have confirmed both OS are there. Whatever prompts them to actually start seems to be the missing element.
Thank you in advance.
I've tried the terminal commands mentioned below. I get to the third command and:
ubuntu@ubuntu:~$ sudo mount /dev/sdb3 /mnt ubuntu@ubuntu:~$ sudo mount ~bind/ dev/mnt/dev mount: mount point dev/mnt/dev does not exist
...
ubuntu@ubuntu:~$ sudo mount /dev/sdb3 /mnt mount: /dev/sdb3 already mounted or /mnt busy mount: according to mtab, /dev/sdb3 is already mounted on /mnt
...
ubuntu@ubuntu:~$ sudo mount ~bind dev /mnt/sdb3 Usage: mount -V : print version
...
ubuntu@ubuntu:~$ sudo mount --bind/proc/mnt/sdb3 mount: unrecognized option '--bind/proc/mnt/sdb3' Usage: mount -V : print version
...
ubuntu@ubuntu:~$ sudo mount --bind/proc /mnt/proc mount: unrecognized option '--bind/proc' Usage: mount -V : print version
...
sudo update-grub
This should solve the problem, or if it doesn't use Boot-Customizer to make windows detectable.
Thanks for trying though.
– atenz May 16 '12 at 12:37