Thanks for the info.
bharadwajtke wrote:
I hope I answered to all your questions.
Actually no - e.g. the SMART data that I asked for earlier is still missing - but you have given enough answers that I can make some comments, with a reasonable confidence.
bharadwajtke wrote:
Hard disk which was in my laptop, accidentally corrupted the OS
I don't believe that the drive "corrupted the OS" - the drive almost certainly has a fault, due to some of the symptoms which you mention later. That is why your laptop failed to boot.
bharadwajtke wrote:
I opened the connected drive and it shown some 'X' drive in the laptop and shown 100MB external device and free space of few KB....
Then I concluded its FAT corrupted...
It was NTFS partitioned hard disk in Windows 7 Home basic Genuine with my Vaio Laptop.
It cannot have a corrupted
FAT, if it was an
NTFS partition / filesystem! This part of your story was very confusing because you mentioned both FAT and NTFS. Now it is clear that your descriptions about FAT are a mistake. I cannot give any analysis of what you saw as you would need to supply more detail, but from the later information, the problems with the filesystem information are likely a result of another underlying problem with the drive - this is not just a corrupt NTFS filesystem.
bharadwajtke wrote:
I used stellar phoenix software for retriving the Photos...I successfully recovered few GB of photos which are not that important...It took 4days for recovering from around 100GB of the hard disk...
That tells you that there is a deeper problem with this drive. If the drive was behaving correctly, then the recovery of 100GB data would not take 4 days. Also note that it is generally
not a good plan to try to recover files directly from a failing / problem drive - and the indirect evidence is that your drive does have a problem.
bharadwajtke wrote:
Then later I thought of creating Image of Hard disk, even it took 3days for just copuing 120GB ofhard disk raw data image....
Same comment as above - there is some other, underlying, problem which is causing this "problem" drive to be so slow.
bharadwajtke wrote:
I bugged up
That did not translate well into English.

I guess you mean that you stopped the process of creating a raw image file, after 120GB of the "problem" drive had been read. But perhaps you mean that a bug (or error? or something similar?) occurred?
bharadwajtke wrote:
HDD Imaging i was doing just to fasten the recovery process
No, you have misunderstood how DIY recovery should be done. Making an image file (or raw clone) of a "problem" drive is
not just to make the recovery process faster - this is an important part of the process which reduces the risk of doing DIY recovery (remember what I said before - everything you are doing has risks, and you might destroy the drive totally because of what you are doing).
bharadwajtke wrote:
I was copying to another External HDD which is in good condition which I borrowed from my friend
I need to give it back....
Either you need to keep that friend's drive for longer, or you need to buy or borrow another external drive, with enough space to hold a full image of the whole 320GB from your "problem" drive, if you are going to continue with your risky DIY recovery attempts. Personally I would not use Stellar Phoenix to create an image file - it runs on Windows and that often does not cope well with failing drives. DIY recovery attempts from failing drives are usually best done with non-Windows cloning (or image file creation) utilities, with control of retries and the ability to be restarted (but you should expect that the drive might fail catastrophically at any time, so everything is done at your risk). Search the previous posts on this forum for discussions about cloning. However based on your questions, I do not believe that you have the experience to perform this part of the process without big risks.
bharadwajtke wrote:
AS I was copied the and recoverd the Photos which is in the first 120GB of the HDD, so i wnated to partition the 120GB of HDD for my Laptop, to make it up and running,
later I can scan and recover the remaining 200GB data photos and save to other external HDD.
[...]
I forgot to mention it had single partition(320GB) as c drive only....
Oh - that is a crazy plan.

Now that you have explained the "problem" drive has only 1 partition (drive C), and explained the other details above, you
must not follow your plan to repartition this drive, before you have recovered your remaining 200GB of photos. Otherwise you will lose vital filesystem information which will be needed to help to recover those photos.
In summary: Your original plan is not sensible.
If the photos are not worth any money, and if you are therefore happy taking big risks that you might destroy them, then study, research and practice (using other unimportant drives) about how to make a raw clone (or make a raw image file) of the whole of the 320GB "problem" drive, using non-Windows utilities. Then assuming you are successful in doing that (which I doubt), you will need more unused disk space to hold any photos which can be recovered
later from your clone (or image file). Only after you have decided that you have given-up trying to recover any more from the clone (or image file) of the "problem" drive,
then you can re-partition it, or do any other writing to that "problem" drive, because you don't care about it any more.
However if the photos are worth any money to you, then you should carefully consider using a professional DR company, as it is clear from the slow copying from the "problem" drive there there is some kind of (not yet diagnosed) underlying problem - and you don't have the experience to reduce the risks of any DIY recovery attempt.
If you have any more questions, then you must supply the full SMART data from the "problem" drive (including raw attribute values), otherwise I might not spend any time replying - that information is
required. One of the easiest Windows utilities that can gather that information, is HDDScan (but do
not use it to scan that drive - just gather the SMART data). You can either save the SMART data as a file onto another drive, or you can take a Windows screendump, or you can take a photo of the screen. All of the SMART data must be visible. Hopefully the USB enclosure where you put the "problem" drive does support gathering SMART data (most do, but some older ones do not).
Good luck with whatever you choose to do - your data, your risk
