Разгонял проц и системную шину, разогнал, тест памяти прошел, с виндой проблем не возникло. Загрузил Linux. Запустил с правами рута cpuburn (burnK7), Ksysguard. Через некоторое время вылетел Ksysguard. Дальше убиваю burnK7, далее reboot. При остановке демонов система надолго зависает, причем что-то происходит с жестким ибо HDD_LED непрерывно горит, не нашел лучшего выхода как нажать резет.

В итоге не грузится GRUB.

Сейчас пишу из Knoppix'a.

Попытки монтирования и проверки дали следующее:

root@1[knoppix]# mount /dev/hdb2 /mnt/hdb2/
mount: wrong fs type, bad option, bad superblock on /dev/hdb2,
       missing codepage or other error
       In some cases useful info is found in syslog - try
       dmesg | tail  or so
root@1[knoppix]# dmesg | tail
end_request: I/O error, dev hdb, sector 1030020
Buffer I/O error on device hdb2, logical block 465
EFS: 1.0a - http://aeschi.ch.eu.org/efs/
ReiserFS: hdb2: found reiserfs format "3.6" with standard journal
hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdb: dma_intr: error=0x40 { UncorrectableError }, LBAsect=14921792, sector=14921792
ide: failed opcode was: unknown
end_request: I/O error, dev hdb, sector 14921792
ReiserFS: hdb2: warning: sh-2029: reiserfs read_bitmaps: bitmap block (#1736704) reading failed
ReiserFS: hdb2: warning: jmacd-8: reiserfs_fill_super: unable to read bitmap
root@1[knoppix]# fsck /dev/hdb2
###########
reiserfsck --check started at Mon Dec 26 16:39:01 2005
###########
Replaying journal..
The problem has occurred looks like a hardware problem. If you have
bad blocks, we advise you to get a new hard drive, because once you
get one bad block  that the disk  drive internals  cannot hide from
your sight,the chances of getting more are generally said to become
much higher  (precise statistics are unknown to us), and  this disk
drive is probably not expensive enough  for you to you to risk your
time and  data on it.  If you don't want to follow that follow that
advice then  if you have just a few bad blocks,  try writing to the
bad blocks  and see if the drive remaps  the bad blocks (that means
it takes a block  it has  in reserve  and allocates  it for use for
of that block number).  If it cannot remap the block,  use badblock
option (-B) with  reiserfs utils to handle this block correctly.
bread: Cannot read the block (232): (Input/output error).
Warning... fsck.reiserfs for device /dev/hdb2 exited with signal 6.

Чем можно помочь в данной ситуации? Как восстановить?