Windows 7 SOS:Misused mke2fs and cannot boot into system

[surlogics]

I installed ubuntu with wubi in windows7 64bit, and I had installed Mandriva 2011 with a disk. I tried to learn linux with Ubuntu and misused mke2fs; after I reboot my computer, windows7 and ubuntu has crashed. As I have mandriva, I boot into mandriva and found
# df -h

/dev/sda7 12G 9.8G 1.5G 88% /
/dev/sda2 15G 165M 14G 2% /media/logical
/dev/sda6 119G 88G 32G 74% /media/2C9E85319E84F51C
/dev/sda5 118G 59G 60G 50% /media/D25A6DDE5A6DBFB9
/dev/sda9 100G 188M 100G 1% /media/ae69134a-a65e-488f-ae7f-150d1b5e36a6
/dev/sda1 100M 122K 100M 1% /media/DELLUTILITY
/dev/sda3 98G 81G 17G 83% /media/OS


# fdisk /dev/sda
Command (m for help): p
Disk /dev/sda: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders, total 976773168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xd24f801e

Device Boot Start End Blocks Id System
/dev/sda1 2048 206847 102400 6 FAT16
/dev/sda2 * 206848 30926847 15360000 7 HPFS/NTFS/exFAT
/dev/sda3 30926848 235726847 102400000 7 HPFS/NTFS/exFAT
/dev/sda4 235728864 976771071 370521104 f W95 Ext'd (LBA)
/dev/sda5 235728896 481488895 122880000 7 HPFS/NTFS/exFAT
/dev/sda6 727252992 976771071 124759040 7 HPFS/NTFS/exFAT
/dev/sda7 481500243 506674034 12586896 83 Linux
/dev/sda8 506674098 514851119 4088511 82 Linux swap / Solaris
/dev/sda9 514851183 727246484 106197651 83 Linux

Partition table entries are not in disk order
I think I may used the following command

mke2fs -j -L "logical"/dev/sda2

but I had forgotten what kind of partition it was before I transfered it into ext3
Data was not lost, and I can view my files as I could in Windows In Mandriva, there are following disks; 117.2G hard disk, files in it is the same as my Windows D:, and ubuntu was installed in it；119.0G hard disk is my G:, with my personal files in it;12.0G is the same with mandriva / (with means root), 101.3G hard disk with nothing but lost+found;DELLUTILITY should be Dell computer utilities preinstalled in my computer ;logical is the disk which I had spoiled；and OS is the C: in my Windows.
After I boot, grub let me choose Mandriva or Windows. I chose windows and it tells me:FILE system type unknown, partition type 0x7 Error 13: Invalid or unsupported executable format I doubt something wrong with ubuntu grub


# cat /boot/grub/menu.lst
timeout 5
color black/cyan yellow/cyan
gfxmenu (hd0,6)/boot/gfxmenu
default 0

title linux
kernel (hd0,6)/boot/vmlinuz BOOT_IMAGE=linux root=UUID=199581b7-ac7e-4c5f-9888-24c4f213cad8 nokmsboot logo.nologo quiet resume=UUID=34c546e4-9c42-4526-aa64-bbdc0e9d64fd splash=silent vga=788
initrd (hd0,6)/boot/initrd.img

title linux-nonfb
kernel (hd0,6)/boot/vmlinuz BOOT_IMAGE=linux-nonfb root=UUID=199581b7-ac7e-4c5f-9888-24c4f213cad8 nokmsboot resume=UUID=34c546e4-9c42-4526-aa64-bbdc0e9d64fd
initrd (hd0,6)/boot/initrd.img

title failsafe
kernel (hd0,6)/boot/vmlinuz BOOT_IMAGE=failsafe root=UUID=199581b7-ac7e-4c5f-9888-24c4f213cad8 nokmsboot failsafe
initrd (hd0,6)/boot/initrd.img

title windows
root (hd0,1)
makeactive
chainloader +1
I can boot into linux, but not ubuntu, it boot into Mandriva
I dont have a boot disk
Help me find a way to make it work again, Thanks in advance.

 

[Saltgrass]

So, sda 1 seems to be your system reserved partition, although in this instance a Dell partition. Sda 2 seems to be a 15 G, possibility recovery partition, which you changed to logical. Sda 3 seems to be your Windows 7 OS partition.

I can only guess which partition might have been the System (active) partitition. If sda2 was your system partition and you changed it to a logical partition, it would have messed up the Boot process for Windows 7.

Guessing in such a situation, is not a good thing to do. If you can get GParted running, you could take a picture of your partitions and attach using the paperclip on the advanced replies.

But I would suggest downloading and burning the Home bootable version of Partition Wizard to check your drive and get a clear picture of what is going on. A picture from a camera works almost as well as a screen capture.

It might help to sort things out to see if you can find the bootmgr file. Where that file is usually means that is the system partition. You should be able to see it from offline, and even in Partition Wizard, using the Explore option on the partitions.

 

[surlogics]

Thank you Saltgrass,I had checked my harddisk with bootsector, and results are here: Link Removed due to 404 Error
There is no camera or something available for me at hand

Hope could provide you some information

 

[Saltgrass]

Do you have bootable media you can use to change the active partition if you were to loose your Linux boot?

It looks like the active partition is sd2. Nothing appears to be in there, but the Windows 7 boot files do appear to be in sd3, the Windows 7 OS partition.

I am not such a Linux expert that I can tell you how to set up a Windows 7 boot from your current situation. I am not even sure if hd0,1 us the first or second partition on the drive.

But if you want to get Windows 7 back, I might try making sd3 active (boot flag) and do a startup repair to set the MBR back to a Windows 7 boot.

If you don't want that, you should be able to set up grub to look at the 3rd partition to chainload Windows 7. I just can't help with that.

If you have moved the leading edge of any partitions, it may have caused the system to loose track of where the Windows 7 partition was. Windows also doesn't like more than 4 primary partitions on a drive. But if it was booting normally before you changed sd2, it was probably the partition was the System partition, but cannot be used to boot if it is now a logical partition and may no longer have the boot files.

I will also assume you have lost your ability to restore the system to a factory default, but you can download a Windows 7 Install DVD from the following link, if you decide to start over.

Link Removed - Not Found

 

[surlogics]

Thanks Saltgrass, I had indeed start over again. Fortunately no data lost