Hello Hazardous,
i'll try to put some order to the data, you gave us. Please correct me, if I'm wrong.
Your "GParted" screenshot:
sda is a 298.09 GiB (SATA?)-Harddisk with
first partition sda1 as Extended Partition, containing
logical partitions:
sda5 (18.63 GiB, ext3, UBUNTU, not mounted, because you use a LiveCD),
sda6 (39.86 GiB, NTFS, Windows 7, mounted as /media/disk by LiveCD?)
sda7 (224,72 GiB, NTFS, Data, mounted as /media/disk-1 by LiveCD?)
second primary partition sda2 (14.88GiB, boot, NTFS, Win XP, mounted as /media/disk-3)
No unallocated space
What's evident : Partitions are in unusual order. It depends on the boot process, the size of the harddisk and the BIOS, whether this is a problem for the bootable partition sda2 or not. Anyway, it's not ideal. What Bootmanager do you use : Linux (Grub, syslinux) or Windows (NTLDR or BOOTMGR; on what partition do they reside ? sda2 = C: (Win XP)?) . Where does the Master Boot Record code come from (Windows or Linux) ? I assume, you use a Linux Bootmanager, because Windows is not able to boot Linux distros.
I shrinked the fourth partition (sda7?) and increased XP(sda2) ant 7 partitions (???).
What resizing operations did you exactly do with "GParted" ? Were they successful due to the "details" ? Are you aware of the fact, that you cannot work with "GParted" on mounted partitions ?
If you had no unallocated space, you would have done it that way :
1. Shrink sda7 by the intended amount.
2. Shrink sda1 by the same amount.
3. Grow sda2 to the left.
Did you do so?
Crash analysis most often needs very detailed information to be able to give a good recovery advice.
Regards
cmdr