Dual Boot: Windows: Grub Hard Disk Error

[tyho]

Hey guys,

I have a dual boot System with Ubuntu 10.04 Netbook Remix and Windows XP SP3 on an Asus eeePC 1000HE. I had some troubles with updating kernels etc. and I ended up with following problem:

After grub reinstall, I am able to boot Ubuntu, also I can mount the windows partition properly. Trying to boot into Windows, I get the error:

Grub Hard Disk Error

It's all on one hard drive which doesn't show any errors:

# fdisk -l
Disk /dev/sda: 160.0 GB, 160041885696 bytes
214 heads, 54 sectors/track, 27049 cylinders
Units = cylinders of 11556 * 512 = 5916672 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x9358c633

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *           1       13078    75564657    7  HPFS/NTFS
/dev/sda2           13079       13112      196452   83  Linux
/dev/sda3           13113       27049    80527933    5  Extended
/dev/sda5           13640       14791     6656229   83  Linux
/dev/sda6           14792       15358     3276099   83  Linux
/dev/sda7           15359       15447      514215   83  Linux
/dev/sda8           15448       27049    67036329   83  Linux
/dev/sda9           13113       13545     2501820   83  Linux
/dev/sda10          13546       13639      543105   83  Linux

Partition table entries are not in disk order

# parted /dev/sda unit s print
Model: ATA ST9160310AS (scsi)
Disk /dev/sda: 312581808s
Sector size (logical/physical): 512B/512B
Partition Table: msdos

Number  Start       End         Size        Type      File system  Flags
 1      54s         151129367s  151129314s  primary   ntfs         boot
 2      151129368s  151522271s  392904s     primary   ext2
 3      151522378s  312578243s  161055866s  extended
 9      151522380s  156526019s  5003640s    logical
10      156526074s  157612283s  1086210s    logical   ext4
 5      157612338s  170924795s  13312458s   logical   ext4
 6      170924850s  177477047s  6552198s    logical
 7      177477102s  178505531s  1028430s    logical
 8      178505586s  312578243s  134072658s  logical

Some partitions don't show a file system because they are luks-encrypted.

As I mentioned earlier, I am able to mount sda1.
I think the problem is that the Partition Boot Sector is corrupted, even though I am not sure if the ntfs partition is damaged at all or if GRUB is the problem.

As I said I had problems with a kernel update and therefore had to reinstall GRUB. I think, but I am not sure, that I accidentally installed GRUB on sda1 (the windows partition) instead of on sda. After I installed GRUB on sda again, I was able to boot linux and fixed sda1 with testdisk. Before, sda1 showed as four partitions (sda1p1, ... , sda1p4). I was not able to mount sda1 till I fixed it with testdisk.
testdisk says the Boot Sector of sda1 is OK, so does ntfsfix.

Finally, an extract from my /boot/grub/menu.lst:

...
## ## End Default Options ##

title		Ubuntu 10.04.1 LTS, kernel 2.6.32-24-generic
uuid		110aba5e-2aba-4bab-9eab-921591c653b0
kernel		/vmlinuz-2.6.32-24-generic root=UUID=fc167932-c5ce-4f8e-a700-66652b8d52ba ro quiet splash 
initrd		/initrd.img-2.6.32-24-generic
quiet

title		Ubuntu 10.04.1 LTS, kernel 2.6.32-24-generic (recovery mode)
uuid		110aba5e-2aba-4bab-9eab-921591c653b0
kernel		/vmlinuz-2.6.32-24-generic root=UUID=fc167932-c5ce-4f8e-a700-66652b8d52ba ro  single
initrd		/initrd.img-2.6.32-24-generic

title		Ubuntu 10.04.1 LTS, kernel 2.6.32-23-generic
uuid		110aba5e-2aba-4bab-9eab-921591c653b0
kernel		/vmlinuz-2.6.32-23-generic root=UUID=fc167932-c5ce-4f8e-a700-66652b8d52ba ro quiet splash 
initrd		/initrd.img-2.6.32-23-generic
quiet

title		Ubuntu 10.04.1 LTS, kernel 2.6.32-23-generic (recovery mode)
uuid		110aba5e-2aba-4bab-9eab-921591c653b0
kernel		/vmlinuz-2.6.32-23-generic root=UUID=fc167932-c5ce-4f8e-a700-66652b8d52ba ro  single
initrd		/initrd.img-2.6.32-23-generic

title		Chainload into GRUB 2
root		110aba5e-2aba-4bab-9eab-921591c653b0
kernel		/boot/grub/core.img

title		Ubuntu 10.04.1 LTS, memtest86+
uuid		110aba5e-2aba-4bab-9eab-921591c653b0
kernel		/memtest86+.bin
quiet

title		Windows XP
root		(hd0,0)
makeactive
chainloader +1

### END DEBIAN AUTOMAGIC KERNELS LIST

The Windows XP entry is added by myself. I don't know much about grub, so there might be the error.


I tried to keep it as short as possible (this is only the end of the story), I hope I didn't forget anything important. Please ask if there is something not clear.

I am in Tanzania with this netbook, so it is not possible to boot Windows CD and fix the windows partition with it, also I don't have a very fast Internet connection.

Is there a way to fix this without a Windows CD? Maybe it is just a dumb mistake in the menu.lst? Any help is highly appreciated.

[devils casper]

Before, sda1 showed as four partitions (sda1p1, ... , sda1p4). I was not able to mount sda1 till I fixed it with testdisk.

Did you create partitions inside /dev/sda1? In that case, Windows XP might be corrupted.
Mount /dev/sda1 and check its contents. Are all files intact?
If everything is fine, download SuperGRUB CD or USB and boot up from it. SuperGRUB has an option to Fix Windows OS Boot. If Windows OS boot up fine, we will re-install GRUB to setup dual boot again.

[tyho]

Ok, somehow it didn't post my first reply, must be the internet connection.

Well thanks for help. I never (purposely) created partitions on /dev/sda1 but there were 4 partitions, maybe created during grub install?

The windows partition (dev/sda1) works properly, all files are intact as far as I can see.

I tried Super Grub, it is indeed a great tool. Unfortunately, it didn't help me either.
I tried Windows -> Fix Boot to Windows. It did remove GRUB but I still get Grub Hard Disk Error.
Also, I tried to uninstall GRUB (after I reinstalled it), same result (no surprise).

It seems like there is a GRUB on /dev/sda1 altough I don't know how to prove that.
Super Grub unfortunately only offers to remove GRUB from MBR.

My guess is:
When I choose Fix Boot to Windows, it copies the GRUB installed on /dev/sda1 to the MBR. This version of GRUB is obviously not working at all.

The more I work on it the more I am surprised that I can mount /dev/sda1, read it and also write on it properly.

Is my guess right or am I completely wrong? Anything else doesn't make sense to me.

How can I remove GRUB from a partition?


I thought about copying the header of a bootable NTFS to /dev/sda1 with dd. This idea seemed crazy at first, but I think it might work, or at least, Super Grub could fix it afterwards.

What do you say?


Thanks for your help

[devils casper]

When I choose Fix Boot to Windows, it copies the GRUB installed on /dev/sda1 to the MBR. This version of GRUB is obviously not working at all.

I wondering if you have used Fix Boot to Windows option of SuperGRUB, why GRUB even appear at startup. Fix Boot to Windows doesn't copy GRUB. It just rewrite Boot Area of MBR. GRUB is in no way connected to Windows OS and SuperGRUB doesn't use it to fix Windows OS.

Linux support NTFS read/write access out of box now and that's why you are able to read/write in Windows OS partition.

Is it possible for you to use Floppy?

[Lostfarmer]

Both fdisk and parted outputs indicate the hdd has 54 sectors/track , that as far as I know is not comman . Could that be causing a problem (?).

title Windows XP
root (hd0,0)
makeactive
chainloader +1

Try
rootnoverify (hd0,0) NOTE: only 1 space between 'y' and '(hd0'
chainloader +1

[tyho]

I wondering if you have used Fix Boot to Windows option of SuperGRUB, why GRUB even appear at startup. Fix Boot to Windows doesn't copy GRUB. It just rewrite Boot Area of MBR. GRUB is in no way connected to Windows OS and SuperGRUB doesn't use it to fix Windows OS.

As far as I see it, SuperGRUB copies some part of the windows partition header (probably where it usually keeps the MBR) to the MBR. If that's true and there is really a GRUB on there, it copies GRUB instead of a working MBR. I don't think it writes a MBR "out of his memory".
Also when I choose Fix Boot to Windows, it asks about what OS is supposed to be on the partition. The only choice I get is "Syslinux".
Moreover, if I check for menu.lst with SuperGRUB, it shows me one on /dev/sda1. That's not normal is it?

Is it possible for you to use Floppy?

No, unfortunately I can use USB and SD only.

Both fdisk and parted outputs indicate the hdd has 54 sectors/track , that as far as I know is not comman . Could that be causing a problem (?).

That might be a good hint, altough I can boot Ubuntu. If that was causing the problem, wouldn't Ubuntu be unbootable, too?

Try
rootnoverify (hd0,0) NOTE: only 1 space between 'y' and '(hd0'
chainloader +1

I tried, it didn't make any difference (Same error: Grub Hard Disk Error)

I have another question:

fdisk -l /dev/sda1

Disk /dev/sda1: 77.4 GB, 77378208768 bytes
255 heads, 63 sectors/track, 9407 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x444c544e

This doesn't look like a partition table
Probably you selected the wrong device.

     Device Boot      Start         End      Blocks   Id  System
/dev/sda1p1   ?      110102      110577     3815730+  6b  Unknown
Partition 1 does not end on cylinder boundary.
/dev/sda1p2   ?      113965      200777   697317940+  75  PC/IX
Partition 2 does not end on cylinder boundary.
/dev/sda1p3   ?      106997      106998        1286+  41  PPC PReP Boot
Partition 3 does not end on cylinder boundary.
/dev/sda1p4          175983      175986       26459    0  Empty
Partition 4 does not end on cylinder boundary.

Partition table entries are not in disk order

There seems to be 4 partitions within the partition. Is this normal for NTFS?
I thought I fixed that (as I said in the first post), but apparently, it's still like that.

[Lostfarmer]

I notice the menu.lst has an entrie for grub2, that might indicate that grub 2 is being used not grub lagacy. Check if you have /boot/grub/grub.cfg, if so post it.

fdisk -l /dev/sda1 will give garbage output and that is ok. That command will look at the first sector of partition which does have the boot record information for a NTFS partition and will miss interpet the data.

[tyho]

OK, you're right:

# /boot/grub/grub.cfg
# DO NOT EDIT THIS FILE
#
# It is automatically generated by /usr/sbin/grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#

### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
  load_env
fi
set default="0"
if [ ${prev_saved_entry} ]; then
  set saved_entry=${prev_saved_entry}
  save_env saved_entry
  set prev_saved_entry=
  save_env prev_saved_entry
  set boot_once=true
fi

function savedefault {
  if [ -z ${boot_once} ]; then
    saved_entry=${chosen}
    save_env saved_entry
  fi
}

function recordfail {
  set recordfail=1
  if [ -n ${have_grubenv} ]; then if [ -z ${boot_once} ]; then save_env recordfail; fi; fi
}
insmod ext2
set root='(hd0,5)'
search --no-floppy --fs-uuid --set 3be2be0d-2dbf-4cbc-97b6-5c294ef61396
if loadfont /share/grub/unicode.pf2 ; then
  set gfxmode=640x480
  insmod gfxterm
  insmod vbe
  if terminal_output gfxterm ; then true ; else
    # For backward compatibility with versions of terminal.mod that don't
    # understand terminal_output
    terminal gfxterm
  fi
fi
insmod ext2
set root='(hd0,2)'
search --no-floppy --fs-uuid --set 110aba5e-2aba-4bab-9eab-921591c653b0
set locale_dir=($root)/grub/locale
set lang=en
insmod gettext
if [ ${recordfail} = 1 ]; then
  set timeout=-1
else
  set timeout=10
fi
### END /etc/grub.d/00_header ###

### BEGIN /etc/grub.d/05_debian_theme ###
set menu_color_normal=white/black
set menu_color_highlight=black/light-gray
### END /etc/grub.d/05_debian_theme ###

### BEGIN /etc/grub.d/10_linux ###
menuentry 'Ubuntu, with Linux 2.6.32-22-generic' --class ubuntu --class gnu-linux --class gnu --class os {
	recordfail
	insmod ext2
	set root='(hd0,2)'
	search --no-floppy --fs-uuid --set 110aba5e-2aba-4bab-9eab-921591c653b0
	linux	/vmlinuz-2.6.32-22-generic root=UUID=fc167932-c5ce-4f8e-a700-66652b8d52ba ro   quiet splash acpi_osi=Linux
	initrd	/initrd.img-2.6.32-22-generic
}
menuentry 'Ubuntu, with Linux 2.6.32-22-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu --class os {
	recordfail
	insmod ext2
	set root='(hd0,2)'
	search --no-floppy --fs-uuid --set 110aba5e-2aba-4bab-9eab-921591c653b0
	echo	'Loading Linux 2.6.32-22-generic ...'
	linux	/vmlinuz-2.6.32-22-generic root=UUID=fc167932-c5ce-4f8e-a700-66652b8d52ba ro single 
	echo	'Loading initial ramdisk ...'
	initrd	/initrd.img-2.6.32-22-generic
}
menuentry 'Ubuntu, with Linux 2.6.32-21-generic' --class ubuntu --class gnu-linux --class gnu --class os {
	recordfail
	insmod ext2
	set root='(hd0,2)'
	search --no-floppy --fs-uuid --set 110aba5e-2aba-4bab-9eab-921591c653b0
	linux	/vmlinuz-2.6.32-21-generic root=UUID=fc167932-c5ce-4f8e-a700-66652b8d52ba ro   quiet splash acpi_osi=Linux
	initrd	/initrd.img-2.6.32-21-generic
}
menuentry 'Ubuntu, with Linux 2.6.32-21-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu --class os {
	recordfail
	insmod ext2
	set root='(hd0,2)'
	search --no-floppy --fs-uuid --set 110aba5e-2aba-4bab-9eab-921591c653b0
	echo	'Loading Linux 2.6.32-21-generic ...'
	linux	/vmlinuz-2.6.32-21-generic root=UUID=fc167932-c5ce-4f8e-a700-66652b8d52ba ro single 
	echo	'Loading initial ramdisk ...'
	initrd	/initrd.img-2.6.32-21-generic
}
### END /etc/grub.d/10_linux ###

### BEGIN /etc/grub.d/20_memtest86+ ###
menuentry "Memory test (memtest86+)" {
	insmod ext2
	set root='(hd0,2)'
	search --no-floppy --fs-uuid --set 110aba5e-2aba-4bab-9eab-921591c653b0
	linux16	/memtest86+.bin
}
menuentry "Memory test (memtest86+, serial console 115200)" {
	insmod ext2
	set root='(hd0,2)'
	search --no-floppy --fs-uuid --set 110aba5e-2aba-4bab-9eab-921591c653b0
	linux16	/memtest86+.bin console=ttyS0,115200n8
}
### END /etc/grub.d/20_memtest86+ ###

### BEGIN /etc/grub.d/30_os-prober ###
menuentry "Microsoft Windows XP Home Edition (on /dev/sda1)" {
	insmod ntfs
	set root='(hd0,1)'
	search --no-floppy --fs-uuid --set ee64d0dc64d0a91b
	drivemap -s (hd0) ${root}
	chainloader +1
}
### END /etc/grub.d/30_os-prober ###

### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries.  Simply type the
# menu entries you want to add after this comment.  Be careful not to change
# the 'exec tail' line above.
### END /etc/grub.d/40_custom ###

I guess I gotta explain something I haven't said yet (it didn't seem important until now):
My trouble started, when I removed linux-image-2.6.32-21-generic and linux-image-2.6.32-22-generic. Since my root partition is very small, there is not enough space for more than four kernels. Unfortunately, I didn't realize grub wasn't updated until I rebooted. Then of course it was complaining about the missing kernels. The menu was the above. No problem, I changed it manually to 2.6.32-24 and it booted properly. Since i couldn't get it updated, I thought I'd just reinstall grub. That's when I did the horrible mistake to install grub on /dev/sda1. Also, I thought I had grub and not grub2, altough this seemed weird since this is a clean 10.04 installation, and as far as I know, they usually come with grub2. But grub2 wasn't installed, so I thought it was grub. Apparently, I was wrong.

Enough of story telling, does this help at all? I think it doesn't change the fact I accidentally installed grub on /dev/sda1, altough I could try to install grub2 instead of grub. Could doing this help?

There are some boot options in the Windows entry which I don't have in my menu.lst of grub so installing grub2 might indeed fix the problem... Still not sure and therefore waiting for your answer.

Meanwhile, I kept googling and found this:
josephhall.org/grub_install_hda1.html

(can't post links yet since I am a newbie )

As it says on there, I would try to do step 2 and 4 only, zero out the boot sector of the Windows partition and then copy Windows system files. What do you think about this?

Sorry for those lengthy posts...

[Lostfarmer]

As it says on there, I would try to do step 2 and 4 only, zero out the boot sector of the Windows partition and then copy Windows system files. What do you think about this?

NO, do not do that. It is for Win98 fat32 partition not XP with NTFS. I do not think it would work any way 'have not verified' . Step #2 would not only zero out the boot code but also the Bios Parameter Block (BPB). The BPB is very important and is only written by format and no other MS program writes it. There is the primary BPB 'first sector' and its backup 'last sector'. Testdisk will rewrite the primary with it backup when the advanced option is selected. Should fix the grub install problem on sda1. Fat32 partitions are a little different.
NTFS.com Partition Boot Sector on PC hard drives.

You must find out which grub is in use. When you boot into the menu do you see 'Window XP' grub legacy or "Microsoft Windows XP Home Edition (on /dev/sda1)" grub 2 ?

Did you resize or move the NTFS partition ? Some programs do not update the backup BPB so testdisk might have rewritten the primary with bad data, but due to you being able to read the partition the BPB seems to be correct.

[tyho]

Testdisk will rewrite the primary with it backup when the advanced option is selected. Should fix the grub install problem on sda1.

It says the boot sectors are identical. I dumped the boot sector, maybe it helps you any. This is an extract of testdisk.log:

Boot sector                        Backup boot sector
0000 eb48904e 54465320   .H.NTFS   eb48904e 54465320   .H.NTFS 
0008 20202000 02080000      .....  20202000 02080000      .....
0010 00000000 00f80000   ........  00000000 00f80000   ........
0018 3f00ff00 36000000   ?...6...  3f00ff00 36000000   ?...6...
0020 00000000 80008000   ........  00000000 80008000   ........
0028 e10c0209 00000000   ........  e10c0209 00000000   ........
0030 00000c00 00000000   ........  00000c00 00000000   ........
0038 10000000 00000000   ........  10000000 00000000   ........
0040 f6000000 01000000   ........  f6000000 01000000   ........
0048 0008fa90 90f6c280   ........  0008fa90 90f6c280   ........
0050 00000000 ea597c00   .....Y|.  00000000 ea597c00   .....Y|.
0058 0031c08e d88ed0bc   .1......  0031c08e d88ed0bc   .1......
0060 0020fba0 407c3cff   . ..@|<.  0020fba0 407c3cff   . ..@|<.
0068 740288c2 52be7f7d   t...R..}  740288c2 52be7f7d   t...R..}
0070 e83401f6 c2807454   .4....tT  e83401f6 c2807454   .4....tT
0078 b441bbaa 55cd135a   .A..U..Z  b441bbaa 55cd135a   .A..U..Z
0080 52724981 fb55aa75   RrI..U.u  52724981 fb55aa75   RrI..U.u
0088 43a0417c 84c07505   C.A|..u.  43a0417c 84c07505   C.A|..u.
0090 83e10174 37668b4c   ...t7f.L  83e10174 37668b4c   ...t7f.L
0098 10be057c c644ff01   ...|.D..  10be057c c644ff01   ...|.D..
00A0 668b1e44 7cc70410   f..D|...  668b1e44 7cc70410   f..D|...
00A8 00c74402 01006689   ..D...f.  00c74402 01006689   ..D...f.
00B0 5c08c744 06007066   \..D..pf  5c08c744 06007066   \..D..pf
00B8 31c08944 04668944   1..D.f.D  31c08944 04668944   1..D.f.D
00C0 0cb442cd 137205bb   ..B..r..  0cb442cd 137205bb   ..B..r..
00C8 0070eb7d b408cd13   .p.}....  0070eb7d b408cd13   .p.}....
00D0 730af6c2 800f84ea   s.......  730af6c2 800f84ea   s.......
00D8 00e98d00 be057cc6   ......|.  00e98d00 be057cc6   ......|.
00E0 44ff0066 31c088f0   D..f1...  44ff0066 31c088f0   D..f1...
00E8 40668944 0431d288   @f.D.1..  40668944 0431d288   @f.D.1..
00F0 cac1e202 88e888f4   ........  cac1e202 88e888f4   ........
00F8 40894408 31c088d0   @.D.1...  40894408 31c088d0   @.D.1...
0100 c0e80266 890466a1   ...f..f.  c0e80266 890466a1   ...f..f.
0108 447c6631 d266f734   D|f1.f.4  447c6631 d266f734   D|f1.f.4
0110 88540a66 31d266f7   .T.f1.f.  88540a66 31d266f7   .T.f1.f.
0118 74048854 0b89440c   t..T..D.  74048854 0b89440c   t..T..D.
0120 3b44087d 3c8a540d   ;D.}<.T.  3b44087d 3c8a540d   ;D.}<.T.
0128 c0e2068a 4c0afec1   ....L...  c0e2068a 4c0afec1   ....L...
0130 08d18a6c 0c5a8a74   ...l.Z.t  08d18a6c 0c5a8a74   ...l.Z.t
0138 0bbb0070 8ec331db   ...p..1.  0bbb0070 8ec331db   ...p..1.
0140 b80102cd 13722a8c   .....r*.  b80102cd 13722a8c   .....r*.
0148 c38e0648 7c601eb9   ...H|`..  c38e0648 7c601eb9   ...H|`..
0150 00018edb 31f631ff   ....1.1.  00018edb 31f631ff   ....1.1.
0158 fcf3a51f 61ff2642   ....a.&B  fcf3a51f 61ff2642   ....a.&B
0160 7cbe857d e84000eb   |..}.@..  7cbe857d e84000eb   |..}.@..
0168 0ebe8a7d e83800eb   ...}.8..  0ebe8a7d e83800eb   ...}.8..
0170 06be947d e83000be   ...}.0..  06be947d e83000be   ...}.0..
0178 997de82a 00ebfe47   .}.*...G  997de82a 00ebfe47   .}.*...G
0180 52554220 0047656f   RUB .Geo  52554220 0047656f   RUB .Geo
0188 6d004861 72642044   m.Hard D  6d004861 72642044   m.Hard D
0190 69736b00 52656164   isk.Read  69736b00 52656164   isk.Read
0198 00204572 726f7200   . Error.  00204572 726f7200   . Error.
01A0 bb0100b4 0ecd10ac   ........  bb0100b4 0ecd10ac   ........
01A8 3c0075f4 c3000000   <.u.....  3c0075f4 c3000000   <.u.....
01B0 00000000 00000000   ........  00000000 00000000   ........
01B8 4e544c44 52206973   NTLDR is  4e544c44 52206973   NTLDR is
01C0 74206b6f 6d707269   t kompri  74206b6f 6d707269   t kompri
01C8 6d696572 74000d0a   miert...  6d696572 74000d0a   miert...
01D0 4e657573 74617274   Neustart  4e657573 74617274   Neustart
01D8 206d6974 20537472    mit Str  206d6974 20537472    mit Str
01E0 672b416c 742b456e   g+Alt+En  672b416c 742b456e   g+Alt+En
01E8 74660d0a 00000000   tf......  74660d0a 00000000   tf......
01F0 00000000 00000000   ........  00000000 00000000   ........
01F8 83a8b6ce 000055aa   ......U.  83a8b6ce 000055aa   ......U.

ntfs_boot_sector
 1 * HPFS - NTFS              0   0 55  9407  93 54  151129314
     NTFS, 77 GB / 72 GiB
NTFS at 0/0/55
NTFS at 0/0/55
filesystem size           151129314
sectors_per_cluster       8
mft_lcn                   786432
mftmirr_lcn               16
clusters_per_mft_record   -10
clusters_per_index_record 1
Boot sector
Status: OK

Backup boot sector
Status: OK

Sectors are identical.

A valid NTFS Boot sector must be present in order to access
any data; even if the partition is not bootable.

You must find out which grub is in use. When you boot into the menu do you see 'Window XP' grub legacy or "Microsoft Windows XP Home Edition (on /dev/sda1)" grub 2 ?

Before all this, grub2 was in use. Now, it is grub.

Did you resize or move the NTFS partition ? Some programs do not update the backup BPB so testdisk might have rewritten the primary with bad data, but due to you being able to read the partition the BPB seems to be correct.

No, I didn't.

I think I will try to reinstall grub2, maybe it helps....


EDIT:
I stopped being a coward an reinstalled grub2. Different menu, so I am using grub2 now. I still get the same error though...