Hi All

I had recently installed ubuntu 7.04 on my computer (pentium4 ). It was working well untill last morning when i deleted some files with .rec extension on my c: system drive of win xp . Dont really know whether that is the real problem with the booting..

it loads all the drives and then when it comes to sda2 it stops all of a sudden .This were the diagonistics that were generated when booted up.

/dev/sdb6:3 files,3/1599189 cluster
dosfsck 2.11 ,12 Mar 2205 Fat32 LCN

/dev/sdb7:3 files,1/1276669 cluster
dosfsck 2.11 ,12 Mar 2205 Fat32 LCN

/dev/sdb9:3 files,3/1918827 cluster
dosfsck 2.11 ,12 Mar 2205 Fat32 LCN

and then i get this........

there are differences between boot sector and its backup
Differencesoffsetrginal/backup)
430:4e/52


and many comma seperated variables...

Not automatically fixing this.


/dev/sda1:19941 files,938361/1278924 cluster
dosfsck 2.11 ,12 Mar 2205 Fat32 LCN

/dev/sda2:26902 files,1092864/1163574 cluster

it hangs after this point..

Seeing this problem i found it fit to reinstall ubuntu and i did that ..
Well there seems to be no end to this problem..
Please help
Thanks in advance
-Sam

Since it thinks there is a problem with your Windows partition I would boot into Windows and schedule a diskchk (with the /R option) and then reboot back into Windows to perform the check.

If that doesn't work maybe you need to manually tell dosfsck to do repairs. Check the man pages for more info.

I waited for about two hours at the place it got hanged and then it show some message which i dont remember now and then i restarted my comp and it worked well..

I think it repaired on those neccessary files..
I noticed one more thing... it generated some fsck****.rec files ... do u know what they are????

Thank you for replying

I'm pretty sure those are files that were jacked up previously. You may have to figure out what they are or just delete them. I found a thread using Google talking about a similar issue- http://forum.notebookreview.com/showthread.php?t=96264.

If I were you I would still boot into Windows and schedule a chkdsk (with /r), reboot, and see if it does anything. If you had done that previously instead of letting fsck do it the results might have been better.

You might want to check your logs to see if it gives you any idea of what files were lost. Hopefully if anything important was lost you have a backup.