Okay so I went to scale the partitions on this computer with gparted on a live CD one day. I left it overnight and rebooted the computer after my changing of the resolution borked my display. Somehow this messed things up. See here:

ubuntu@ubuntu:~$ sudo fdisk -l
omitting empty partition (5)

Disk /dev/sda: 80.0 GB, 80026361856 bytes
255 heads, 63 sectors/track, 9729 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x000ed65f

Device Boot Start End Blocks Id System
/dev/sda1 * 1 9729 78148161 5 Extended
/dev/sda2 9400 9729 2650693+ 82 Linux swap / Solaris
/dev/sda5 1 2432 19534945+ 83 Linux
/dev/sda6 2433 6752 34700368+ 83 Linux
/dev/sda7 6753 9399 21261996 e W95 FAT16 (LBA)


sda6 = root of ubuntu, sda7 = home directory, sda7 = the new partition I had made for a to-be windows install (not sure why its fat16...).

Anyways, ubuntu boots fine as is, but the boot flag is on sda1. How can I fix my partitions so gparted will work again? (gparted wont show partitions if they are screwed up like this)

Mount externally with a rescue CD or create a rescue CD in Ubuntu with the tools needed.
Use the shell to run ext2/3 programs and fat/ntfs progs.
After that, gparted should work.

I believe you can change the flag with fdisk or cfdisk. parted might also work for you.

The flags will make it show in gparted again? I don't know how else to fix this. The fat16 partition was deleted a little while ago. Is the problem that the ordering is wrong in the list? What programs would I use to fix this Mr bisquit?

Use testdisk to recover the partitions it can find. I'm surprised gparted did that - I've seen Partition Magic do similar.
Windows won't install to a disk like that. You have an extended spanning the entire disk (not a problem of itself), but you have a (nominally) primary partition (sda2) embedded in the extended.
Any attempt at resolving this would be guess-work.

parted can reorder the partition table entries. Look at man parted for details.

you could try out the Greatest Debian rescue CD?
it has all the recovery tools basically
its got lots of things...
http://www.linuxquestions.org/questi...art-1--779053/

about a week ago I booted up and it said one of my data partitions(80GB) was "unallocated"
oh s^&%

I used testdisk and it found the partition and fixed it
dont format anything whatever you do

Thanks guys, should I delete that extended one taking up the whole disk? I used testdisk but that confused me because it got rid of that extended one taking up the whole disk.

Okay big problem. I ran testdisk, it found my swap and 1 ext3 FS. After I proceeded, it showed swap, an ext3, and an extended ext3 (I have my home folder on a different partition than the root OS). After seeing all 3 partitions there (swap, root, home), I proceeded. After rebooting it showed 1 ext3 FS, and the swap.

I am unable to mount it with a live CD because of the superblock. I am running e2fsck on it right now and have weights holding down the "Y" key because its all messed up and its been doing this for 10 minutes or so...


Am I screwed? Did I lose my home folder?

bummppp

Quite likely.
fsck is designed to get the filesystem back into a consistent state. With little (no) regard to what you as the user might construe that to be. Especially if you park a weight on the <Enter> key.
File truncation is the most common - but you will (usually) have no indication of which files have been "fixed".
If I have a f/s that need "fixing" to that extent, I restore it - in full.