Why GNU/Linux Rocks

[sgreger1]

sda. Case makes a difference in Linux. sDA, SdA, SDA are all different files, and that applies to commands also. It's actually pretty easy to install, and it takes care of everything. The EasyBCD is what gummed up the works I think.

Edit:
Ya think this is a PITA? Try installing XP after you've installed Win7 :^D

Oh I didn't know case mattered, thanks for the heads up. I undid what EasyBCD did though and reinstalled the whole thing, I think shiki is right and it's a UEFI thing. I am not familiar with how the BIOS works so I didn't know it was that new.

[sgreger1]

It's on /dev/sda. I can guarantee you that you didn't manage to install to an NTFS partition. Ubuntu is on /dev/sda5-9. Try running df -h /dev/sda5 in order to figure out which partition's are which. Just do df -h for each of those linux partitions, and it'll tell you your size so you can figure out which are which.

Also, you're not going to be able to install grub to the disks without mounting them. That was part of the purpose of the chroot I suggested to you earlier. When you chroot, you'll be mounting the necessary parts of the partitions you installed to, and then changing to those partitions as your new root, rather than the liveCD. Also, since your install is on /dev/sda, that's probably where you wan to install grub to. Still, like I said before, a typical grub install will NOT work with a UEFI boot. One way or another, you're going to need to grab the grub2-uefi package and get it installed on your system if you want to be able to boot to Ubuntu. lx should be able to confirm this for me.



And no, not every user has to do this. You're getting extra fun because you've got all sorts of things with your system that are relatively new. UEFI boots have only been implemented since last spring, so this is pretty much the first wave of efforts to work with it in linux. Also, you may as well use grub2-uefi rather than the corresponding grub-uefi package, if such a package even exists. Grub will be deprecated sooner or later, and it'll be easier to just set GRUB2 up once now.

Okay I will do this now and figure out which partition is which. I will have to figure out how to get a copy of gub2-uefi somehow.

[lxskllr]

sda. Case makes a difference in Linux. sDA, SdA, SDA are all different files, and that applies to commands also. It's actually pretty easy to install, and it takes care of everything. The EasyBCD is what gummed up the works I think.

Edit:
Ya think this is a PITA? Try installing XP after you've installed Win7 :^D

Edit2:
For the grub version, you need grub-efi-amd64 which should be on the cd.

[sgreger1]

I tried writing it to Sda but it says cannot find device. Glad it didn't work since I don't want to delete my windows.

So is this what every user has to do to install Ubuntu? Jesus Christ I can see why this isn't more widely used lol.

Almost 3 days now and I still don't have it running

[shikitohno]

It's on /dev/sda. I can guarantee you that you didn't manage to install to an NTFS partition. Ubuntu is on /dev/sda5-9. Try running df -h /dev/sda5 in order to figure out which partition's are which. Just do df -h for each of those linux partitions, and it'll tell you your size so you can figure out which are which.

Also, you're not going to be able to install grub to the disks without mounting them. That was part of the purpose of the chroot I suggested to you earlier. When you chroot, you'll be mounting the necessary parts of the partitions you installed to, and then changing to those partitions as your new root, rather than the liveCD. Also, since your install is on /dev/sda, that's probably where you wan to install grub to. Still, like I said before, a typical grub install will NOT work with a UEFI boot. One way or another, you're going to need to grab the grub2-uefi package and get it installed on your system if you want to be able to boot to Ubuntu. lx should be able to confirm this for me.

And no, not every user has to do this. You're getting extra fun because you've got all sorts of things with your system that are relatively new. UEFI boots have only been implemented since last spring, so this is pretty much the first wave of efforts to work with it in linux. Also, you may as well use grub2-uefi rather than the corresponding grub-uefi package, if such a package even exists. Grub will be deprecated sooner or later, and it'll be easier to just set GRUB2 up once now.

[lxskllr]

Ok. You'd have to write grub to sda, and it would overwrite the Windows bootloader. The problem is if you want the Windows loader back, you don't have an install disc to do it. I /think/ you can do it from the Windows recovery console when you start up, but I never have.

I'm not confident enough with YOUR machine to tell you to go ahead and do it(write to sda). Shikitohno is more experienced. I wouldn't mind hearing his input.

Regarding the gpt partition... That's the format needed to deal with disks of that size. The old standby was mbr, but it's only good up to 2tb. If you were booting from sdb it would make a difference, but it doesn't for your purposes.

[sgreger1]

Also it says "the fdisk tool has detected a GPT partition on the drive and says that it does not support GPT". What should I do about this? And why does sda6 and sda9 both say "Linux Swap / Solaris"? Did it somehow make two different swap partitions? So it looks like all the partitions at least are on sda, not sure how to tell if ubuntu is on them or not but the partitions are definately on sda (it can't even read my second hard drive, sdb). Edit: Tried this:

sudo grub-install /dev/sdb

Get this error:

/usr/sbin/grub-probe: error: Cannot find a device for /boot/grub (is /dev mounted?)

I get the same error if I try /dev/sda.

[sgreger1]

Oh okay. That doesn't work either but it works if I put "sudo" before it.

Here is what it says. Looks like maye it's on /sdb?

[lxskllr]

That's fdisk -L except lower case, and from the live environment, not the limited grub console you get when trying to boot.

[sgreger1]

Fdisk -| does nothing. I entered it into the terminal and it just starts on a new line. "> "

[lxskllr]

From the "Try Ubuntu" selection when you boot to the cd. Get into the live environment, and open up your terminal. It'll be in accessories, wherever that is in Unity, and it'll look like my screenshot above.

[sgreger1]

Yea, that's normal. What does fdisk -l give you?

Edit:
from the liveCD terminal

Edit2:
You can likely rescue grub from your prompt above, but I've never done that. Google should help.

Okay explain real quick what you mean by "liveCD terminal". The only terminal I can get to is by pressing "C" which takes me to the grub command prompt.

Should I first load ubuntu from the disc or go straight to the grub command prompt by pressing "C"?

Note: I may be AFK for about an hour and will return then. Thank you so much for all of your help guys.

[lxskllr]

Is it normal that I can access the files on my c: drive from here? Have I done something wrong?

Yea, that's normal. What does fdisk -l give you?

Edit:
from the liveCD terminal

Edit2:
You can likely rescue grub from your prompt above, but I've never done that. Google should help.

[sgreger1]

I tried pressing "C" when it first booted which took me to the command line where it says "GRUB>" I tried typing fdisk -| but it said invalid syntax.

[sgreger1]

Okay posting from my phone now.

I loaded Ubuntu install disc.
Chose "try without installing"

Ubuntu loads up.

Screen turns black a few times, system freezes. I retry.


I need to clarify here if I should be choosing to "try Ubuntu without installing" or of I should press c which takes me to the command line and says "grub>"

If I choose try without installing:

I go to the file explorer and it lists the following:

Data drive: this seems to hold the contents of my second hard drive

SYSTEM: This has the folders "boot" And some log files. another folder labeled "system volume information"

OS: this seems to be all my widows c: drive

/boot: folders grub and lost+found

/ root: Has many folders, one of which is "boot" but unlike the one under "system" it's contents are empty.

/Home: this one has lost+found and my computers username


Is it normal that I can access the files on my c: drive from here? Have I done something wrong? And should I have two boot folders? The one in "system" is filled with lots of folders but the one in /root is empty.