Filesystem errors
 

/: Duplicate or bad block in use!
/: Multiply-claimed block(s) in inode 8: 25454
/: Multiply-claimed block(s) in inode 393228: 7173740
/: Multiply-claimed block(s) in inode 393229: 25454 7173740
/: (There are 2 inodes containing multiply-claimed blocks.)

/: File <The journal inode> (inode #8, mod time Sat Feb 4 14:42:07 2006)
has 1 multiply-claimed block(s), shared with 1 file(s):
/: /home/s/PS2 games/tekken5.iso (inode #393229, mod time Fri Jan 11 17:53:45 2008)
/:

/: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
(i.e., without -a or -p options)
fsck died with exit status 4

am using ubuntu feisty

HD problem, change a new one .

maybe bad sector. You should buy the new

Boot into single user mode or command line, issue a command similar to the one below:
Providing the root partition is /dev/sda1, if it is something else, change the command to do the file system check in the appropriate partition. Give it some time and re-boot when the prompt comes back.

After using 'fsck', if your HDD has SMART capability, you can use 'smartctl' to run some tests (the long test is recommended), and see if indeed your HDD is starting to fail. No, don't change your HDD just yet.

by root partition do you mean the partition that hold my installation of linux?

The error occurs when I boot into linux. It boots up dosfsck and the only fat partition i have is on /dev/sdb3

Yes, that would be the root partition. You can also run fsck on the /boot partition if you have a separate partition for it. With command: fdisk -l you should be able to figure out which is which. The / and /boot partitions should have a 83 in the file system type, swap should be 82.
You probably have a command prompt after the errors during boot up where you can issue commands to manually run fsck.

You may also be able to do all of this by booting into a live session with the Ubuntu installation disk.

I tried that and it seems to have done something because it said 2.5% non-continuous or something like that can't quite remember. But I still get the same thing. I tried it again, it just give me number of clusters.

Are you hitting "enter" or "y" at every one of them, because fsck will ask for confirmation to make necessary changes to every error it finds, and there are usually many of them.

Normally when I encounter a similar situation and told to run fsck manually I get to a root prompt or use sudo and run the command previously posted and go through countless confirmations to block errors, then when a prompt returns I issue command: reboot, it shuts down properly and usually re-boots properly.

EDIT
Some live CD's only mount hard drives in read only mode preventing changes to the drive by default, it is sometimes necessary to unmount the drive and re-mount in read write mode to repair a file system from a live CD.

you need to figure out which filesystem is failing. once you figured out run this

fsck -y /dev/sda?

if using LVM do this

fsck -y /dev/VolGroup00/LogVol??

? Running fsck is much safer when filesystem is not mounted!