boot partition probs on RH9->FC2 upgrade

[will81]

I finally got around to upgrading my redhat 9 system to FC2. However, after I installed FC2 and booted, grub wouldn't boot properly.

this is the error it gives me:

booting 'fedora core (2.6.5-1.358)'

root (hd0,0)
filesystem type is ext2fs, partition type 0x83
kernel /vmlinuz-2.6.5-1.358 ro root=LABEL=/

Error 25: Disk read error


so I booted from the FC2 rescue disk and poked around a little bit. I noticed that a number of files on my boot partition somehow became corrupted. The corrupted files are: boot.b, initrd-2.6.5-1.358.img, module-info, System.map, vmlinuz, and vmlinuz-2.6.5-1.358. Also, I ran 'sfdisk -l --force' and got some interesting results:

Disk /dev/hda: 116301 cylinders, 16 heads, 63 sectors/track
read: Input/output error

sfdisk: read error on /dev/hda - cannot read sector 0
/dev/hda: unrecognized partition
No partitions found

Disk /dev/hda1: 207 cylinders, 16 heads, 63 sectors/track

sfdisk: ERROR: sector 0 does not have an msdos signature
/dev/hda1: unrecognized partition
No partitions found


Disk /dev/hda2: 114016 cylinders, 16 heads, 63 sectors/track

sfdisk: ERROR: sector 0 does not have an msdos signature
/dev/hda2: unrecognized partition
No partitions found

Disk /dev/hda3: 2071 cylinders, 16 heads, 63 sectors/track

sfdisk: ERROR: sector 0 does not have an msdos signature
/dev/hda3: unrecognized partition
No partitions found


where hda1 is the boot partition, hda2 is the root partition, and hda3 is swap.

the interesting thing is that I can access all the files in my root partition from the rescue disk and none of them seem to be corrupted. Therefore, I'd like to restore my system without having to format the drive and start from scratch. However, I'm not sure how to replace the corrupted boot files (perhaps just reinstall the kernel rpm?) or what to do about my apparently corrupted partition table. Suggestions would be very much appreciated.

Thanks.

[imdeemvp]

your files may not be not be corrected but what about your hd?...it could be going bad...if you have a third party software check for any red partitions (=damage partition) you may need to save your vip data and reformat you hd.... i usually do that when i get disk read errors.....