[Ham-Computers] RE: error performing inpage operation on hard drive

[Hsu, Aaron (NBC Universal)]

Hi all,

Get Data Back is a great utility, but it's not always the easiest to use.  Also realize that although it is designed as a data recovery tool, it is not a data "repair" tool - it can find files and data structures, but it is agnostic as to the "type" of file it's recovering.  So, if a file is damaged, it will recover the file, but the file will still be "damaged".  What it does, finding an recovering data, it does very well.  And, be forwarned that if you have the "deleted files" and/or the "excessive search" options enabled, then it's possible to find more data than the size of the drive itself.  This is due to the way most operating systems "delete" files - most just alter the file's directory entry and then re-claim the file's allocated space.  Until the directory entry itself is deleted, a recovery program will find the entry and attempt to rebuild the file based on it's directory listing.  This "recovered" data may no longer be from the original deleted file, but because the directory entry is there, recovery programs will "recover" the file.  But, many times, doing a "deleted file" or "excessive search" will yield results when the "normal" search comes up empty.

Now as to Jonathan's problem, an "inpage error" is usually memory related - often relating to the paging file.  Since the external drive was once the internal drive, I have a few questions.  Does the new "internal" drive have one or two partitions?  Was there a paging file configured on the "second" partition of the original 320GB drive?  Was Windows re-installed with the new computer/motherboard or was it "cloned" to the new drive?  What are the current drive letter assignments?

In the mean time, it sounds like there's logical drive corruption that needs to be fixed - hopefully, it's not a physical problem.  The first thing I'd do is to run a CHKDSK of the USB drive (both partitions).  You can do this by entering the following at a Command Prompt:

  chkdsk x: /f

where "x" is the drive letter of the external drive partitions.  If for some reason CHKDSK responds that it can't gain exclusive access to the drive, then say "no" to the reboot check, dismount/eject the drive, re-mount/insert the drive and run CHKDSK /F again.  This time, it should run - remember to run it on both partitions.  It will report any errors it finds, so don't close the Command Prompt until you've read them - this is also why you don't run it from the "Run" line (the "run" box opens and closes automatically).  After CHKDSK finishes, run it again just to be sure.  Then, dismount/eject the drive, re-mount/insert it and check the contents.  If there was any logical corruption, CHKDSK should have been able to fix it.  However, depending on the severity of the corruption, some files may be lost or data may be corrupted - you'll need to open files individually to check this.

With NTFS, logical drive structure problems usually don't cause data corruption.  However, with FAT/FAT32, logical problems can definitely lead to data corruption and loss.  The most common logical FAT/FAT32 problem is corruption with the FAT table.  If the FAT table has errors, then programs may start using occupied drive space causing what's known as "cross-linked" files - this is where two or more files are using the same data sector(s).  The more you use a FAT-based drive with logical problems, the more likely data corruption will occur.  I feel that this is what happened in Jim's case as he was moving/deleting many files when the problem occured.  Unfortunately, there's no forwarning to this type of problem occuring - preventitive maintenance is the best solution - run CHKDSK /F every once in a while.

*** BUT ***

Remember that CHKDSK can cause some data loss if errors are found and repaired - this is the nature of the beast - therefore, it's best practice to backup your data prior to performing any type of drive maintenance.  Not absolutely necessary, but just good CYA.

So, Jonathan, try the CHKDSK and if it doesn't work, post the results and the answers to the questions I posed above.


73,

  - Aaron, NN6O



-----Original Message-----
Sent: Thursday, July 31, 2008 5:19 PM
Subject: Re: [Ham-Computers] error performing inpage operation on hard drive

Hi Jonathan:
If you don't receive some easier ideas, you might try GetDataBack, which Aaron uses at work for bad hard drives.  You can use the free evaluation version, which allows you to view the repaired files, but not copy them.   I'm not sure what the view options should display, as it didn't repair any of my files I checked.  However, you can open the documents with the application that created them (Word, for example), and maybe save using Word.  It would be a slow process without the paid version, as you would need to process each file individually.  However the price, around $70, isn't bad for this type application.  Aside from it not helping me, the only complaint is separate applications are required for NTFS and FAT32 (plus Apple, etc) and I needed the FAT32 version.

Should you decide to try it out, I have some detailed notes I could send you.  I'm getting forgetful, so these notes will be handy if I decide to use it next year.

Jim


At 09:30 AM 7/29/2008, you wrote:
>I have an external USB 320GB SATA hard drive split into two
>partitions... the first one is where all my programs are installed and
>the 2nd one is where all my data is stored (this was my main drive
>until my motherboard and power supply went in my other computer hence
>why it's in a usb enclosure)... wellll i just my computer off last
>night before i went to work and when i came in this morning about 7AM
>and turned everything on I can see the first partition fine and when i
>try to open the first partition I get the following error: Error
>Performing Inpage Operation. another thing i notice is that the drive
>label is now changed to Local Disk.  Any ideas how i can get my data
>back before I have reformat the drive and loose it all?  I tried
>reading some info on google but it made me more confused... i read
>something to the effect that I need to hook it up to a linux machine 
>and extract the data that way.
>
>Anyone have any ideas on how to solve this problem?
>
>Thanks,
>
>Jonathan