An inpage operation is performed when any data had been removed from RAM to the swap file and is later needed again. Before the process in need of that data can access it, the system loads it again from the swap file into RAM and directs the process to that data. This did not work here. There might be several reasons. Your hardware might be faulty. Most probably it is the hard disk. Perform a backup of your system! Let windows check the hard disk (UNCHECK search for bad sectors!). You may also perform a defragmentation, but this is more a means to speed up the access rather than clearing any faults. A last resort (Caution, may take several hours!) is a check with checked 'search for bad sectors).
2/2007 I had this problem with my external hard drive. (60gb maxter slim) It connects with just a usb for transfer and power. It was plugged into my laptop and then it got unplugged while I was in the middle of something. I tried to plug it back in and it would do anything, I went to my computer and it wasnt there. After awhile the icon came up and i clicked on it; the window seized up and the drive started making grinding sounds. I searched the net and nothing helped, most sites gave no help or said the drive went bad and all info was lost. This bummed me out, so I plugged it into my desktop and left the system and the hd running for about three weeks. The grinding sounds got louder until i was almost going to unplug it, since it sounded like it was damn near about to disassemble itself, but I didnt. When the noise stopped I went to look and everything worked fine and i got all my information no problem.
3/2007 I had exactly the same error on my hd (an old Quantum 40GB disk). Windows XP would not even access the drive and showed it as empty after about 3 months of not using the drive. It was full of data which I hadn't backed up. I mounted it onto my linux pc (running Fedora Core 5 with NTFS read support) and could pull all the data off of it onto my windows pc over the network without problems. Hope this is of help to someone.
3/2007 Just found this thread - I had just imaged a failing hdd (win2000 os) to a new one and rec'd the error when I tried to connect the new drive in an external usb case.
Fitted it into a PC and used the win2000 recovery console, did a FIXMBR then put it back in the usb case and now I can see it again. Might help someone...
3/2007 It works perfectly. This is what the guy says to do:
1. Start Run type in cmd then click OK to get a command prompt.
2. Type in chkdsk e: /r (replace e: with the drive letter of your external hard drive).
This won't do any harm, it will fix errors on the disk and try to recover data from bad sectors. It might not solve the problem but it's worth a try.
First, booting from a Linux Primary IDE, and dead disk as a secondary IDE, save a copy of what's on the disk, first 512MB (1M sectors times 512 byte sectors).
Disk /dev/hdb: 200.0 GB, 200049647616 bytes 255 heads, 63 sectors/track, 24321 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x313bf923 Device Boot Start End Blocks Id System /dev/hdb1 1 24321 195358401 7 HPFS/NTFS Disk /dev/hdb: 200.0 GB, 200049647616 bytes 255 heads, 63 sectors/track, 24321 cylinders, total 390721968 sectors Units = sectors of 1 * 512 = 512 bytes Disk identifier: 0x313bf923 Device Boot Start End Blocks Id System /dev/hdb1 63 390716864 195358401 7 HPFS/NTFS dd if=/dev/hdb of=didak1.bin count=1M -rw-rw-rw- 1 brian users 536870912 2009-03-08 15:18 didak1.bin -rw-rw-rw- 1 brian users 512M 2009-03-08 15:18 didak1.bin dd if=/dev/hdb of=didak3.bin count=1M skip=2M 1048576+0 records in 1048576+0 records out 536870912 bytes (537 MB) copied, 28.1656 s, 19.1 MB/s dd if=/dev/hdb of=didak6.bin count=1M skip=5M dd: reading `/dev/hdb': Input/output error 1048560+0 records in 1048560+0 records out 536862720 bytes (537 MB) copied, 102.125 s, 5.3 MB/s dd if=/dev/hdb of=didak6-retry.bin count=1M skip=5M dd: reading `/dev/hdb': Input/output error 1048552+0 records in 1048552+0 records out 536858624 bytes (537 MB) copied, 122.931 s, 4.4 MB/s