Originally Posted by chem_og
im 90% sure i installed ubuntu onto my C drive without making a separate partition.
But the information you posted says otherwise.
It very much implies the question: What does Windows see on the D: partition?
the results i got from the fdisk command u mentioned:
Did you retype all that? (You don't know how to copy/paste in Linux into a browser accessing this forum?)
It looked like it had at least one typo, so I'm not sure what to trust.
Not entirely sure what any of this means. The Hard drive its installed on is 500GB without any partitions.
It means you have a second 500GB hard drive. It means that while installing Linux, you reduced the size of a Windows partition on the second hard drive and installed Linux into new partitions there.
My guess from looking at this is you once had a single Windows partition C: mirrored on two physical drives. The Linux installer did not recognize the Windows fake RAID, so it modified the two drives independently, installing most of itself on the second drive, but installing into the MBR of the first drive.
If you're lucky, Windows then recognized the RAID was broken and continued operating on just the first physical drive. If that is correct then on D: Windows will see a frozen copy of what had been on C: before you installed Linux.
If you're unlucky, then Windows has been using a broken RAID ever since and gradually corrupting things.
Or maybe I'm guessing entirely wrong and you never had a RAID and D: is something else entirely.
Before fixing anything you need to verify what D: is.
But I'm not really even certain D: is the right name for the partition that needs explanation. In Linux that is sdb1. In Windows it might be D: or E: or maybe something else.
If you never had a RAID, or if Windows understands the RAID is broken and
you don't want to repair the RAID, then my original advice remains correct. You need to repair the MBR in Windows and then verify Windows boots directly (without the Linux boot menu appearing first). Then you can use the Windows disk management software to clean the Linux stuff off of the second drive and reuse that space for data.
But if you want to repair the RAID, that gets a lot more specific based on details of what brand computer you have, what BIOS you have and what type of fake RAID you have. It still starts with repairing the Windows MBR.
Your C: partition is the thing listed by fdisk as sda2.
You have a recovery partition listed by fdisk as sda1. There is a BIOS hot key (One of the F buttons, but I don't know which one) that will boot into the recover partition. Many recovery partitions when booted start by fixing the MBR for Windows without even asking if you want to. That might be a good way to fix this, but I prefer having more control, so I would find a program for fixing the MBR and run that inside Windows itself.