Power shut off lead to endless loop Startup Repair

Hello. I am so happy to have found this forum. Thank you in advance to all who help those of us in need. I have read many of the posts about my issue but keep hitting dead ends or questions so feel it is time to ask for some specific help. I apologize in advance if my questions seem redundant.

Computer: HP Pavilion dv6-1350us Entertainment Notebook running Windows 7 Home Premium 64 bit. 250GB HD. Intel Core Duo Processor.

History: Hard drive is pretty well maxed with only a few gigabytes free. Laptop does not have a battery so it shut down when power cord was bumped. On restart it went into a repair mode that displayed files being fixed as it scrolled. When I went to remove the external devices while this was processing, I accidentally disconnected the power cord causing another shut down. This time when I rebooted, it went into Startup Repair with the box on the screen showing the blue box that travels across. After numerous hours I thought maybe it was hung up so shut it down and rebooted. This time I saw it gave an option for normal start or the repair so I tried the normal option twice and both times it came back to the same screen, leaving just the repair as an option so I started it once again. Paying more attention this time, I could see the hard drive light flickering so waited patiently as it ran....for over 4 days! I finally started searching the internet for how long it would run and found the endless loop issue. So last night, after I think 5 days, I again shut it down.

Trying to follow the Troubleshooting steps I found here, I:

Booted into F8 and chose Last known good configuration. Tried it twice with no luck.

Ran chkdsk c: /f which was pretty quick and said the following:

It is an NTFS system.
It showed 256 file records processed in stage 1 with 0 large, bad, EA, and reparse records processed. Stage 2 330 index entries processed with 0 unindexed files scanned or recovered. Stage 3 256 file SDs/SIDs processed Security descriptors verification complete with 38 data files processed. Usn journal 948080 USN bytes processed and complete. Windows checked the file system and found no problems.
203775 kb total disk space
26100 kb in 43 files
24 kb in 39 indexes
0 kb in bad sectors
3751 kb in use by system
2048 kb occupied by the log file
173900 kb available on disk

4096 bytes in each allocation unit
50943 total allocation units on disk
43475 allocation units available on disk
Failed to transfer logged messages to the event log with status 50.

I then ran chkdsk d: /f and that is where I am at. It said it was checking 5 stages. #1 and 2 went quickly then it just sat with a flashing dash for a long time...maybe upwards of an hour, enough I thought it had hit an issue that was stopping it from finishing then suddenly started scrolling like it did following the original shut down. It says recovering orphaned files. Not sure where it started but when I first noticed a percentage listed as it scrolls past it was 50%. Now after running some 5+ hours it is only at 51% so at this rate it could run until Christmas.

So can anyone give me advice at this point? Is there a quicker way to fix these files without losing my data? Is my data even savable? I hope the answer to the last question is yes. Sorry this is so long, but tried to cover the most info I could. Any help appreciated!

So chkdsk d:/r is still running. When I first noticed a percentage as it scrolled on the screen yesterday is was 50% and today, 24 hours later it just turned to 53% so at this rate it could take another +/- 3 weeks to get through this stage. Has anyone ever had it run that long? Did it repair it to a usable state? My fingers are still crossed because there is a lot of info on it that I really want.

Well, it was at 54% when I went to bed and back to the Starup Repair screen this morning.

Disappointed about no feedback from this site. Had hoped someone had some ideas.

There has been no positive feedback because there isn't one direct answer.

Killing the power could do a few things, It may now be corrupted or a bad hdd, you could have damaged other H/W as well.

Step 1.
I'd probably run a hdd diagnosis

Step 2.
Can you boot into safe mode?
if yes open CMD as admin and run sfc /scannow

If no

Step 3.
Boot into startup repair and open recovery console
you should be able to execute a cmd line interface

run sfc /scannow

Step 4.

If it still doesn't work run a diag on rest of computer.

Usually with cases like this you may spend hours or days troubleshooting when it may just be quicker to reload windows.

Do you see any sort of blue screen when restarting,

when you're booting up hit F8 like you're going into safe mode and disable automatic restart on system failure.

Another thing you can try to is to rebuild bcd

In the command prompt under the startup repair

bcdedit /export C:\BCD_Backup
c:
cd boot
attrib bcd -s -h -r
ren c:\boot\bcd bcd.old
bootrec /RebuildBcd

bootrec /FixBoot

Bootrec /FixMbr



Check the clock in your BIOS if it is way off it could indicate bios reverting back to default, which could cause you hdd to have been changed to read as AHCI vs IDE vs ATA

Sorry I didn't see this thread earlier. Working on the hard drive is the wrong thing to do at this point. Instead you should be copying your data from it. Working on it may be making it worse. Either pull the drive and attach it to another machine, or boot this machine to a Linux live CD, and copy your data to another hard drive.

Once that is done you can do anything to the drive. SMART diagnostics on the drive is a good idea. The first thing I would do is get rid of at least 20 GB of data so the drive can breathe. As it is, everything you do is going to be in slow motion.