Solved Drive C partition unallocated

[Kaktussoft]

You can extend D now using disk management ... so add the 3GB space to it.
Afterwards you can add the 9GB in front of C to C using PW.

used space of C+D is about 200GB. But pagefile and hibernation file and some other temp files won't be backupped. And it will be compressed. Resulting image file will be about 160GB (depends on if files are compressable)

I see. That will be good. After that, I suppose the system will be working as usual?

You can extend D now using disk management ... so add the 3GB space to it. You can do it now... it's without risk.

Afterwards you can add the 9GB in front of C to C using PW. Also without risk. But do it by booting from PW bootCD. Adding space in front of partition is a little bit risky. In case of power failure... C is damaged. But PW does it very safe! Best thing to do is make backup first

 

[zirch]

You can extend D now using disk management ... so add the 3GB space to it.
Afterwards you can add the 9GB in front of C to C using PW.

used space of C+D is about 200GB. But pagefile and hibernation file and some other temp files won't be backupped. And it will be compressed. Resulting image file will be about 160GB (depends on if files are compressable)

I see. That will be good. After that, I suppose the system will be working as usual?

You can extend D now using disk management ... so add the 3GB space to it. You can do it now... it's without risk.

Afterwards you can add the 9GB in front of C to C using PW. Also without risk. But do it by booting from PW bootCD. Adding space in front of partition is a little bit risky. In case of power failure... C is damaged. But PW does it very safe! Best thing to do is make backup first

Alright. Going to make a backup now. Thank you very much. You're the hero.

 

[Kaktussoft]

Make a backup asap. I still don't trust the harddrive 100%.

• Why was PQSERVICE 9GB, then 600MB, then 1.1GB? Don't know exactly what you did.
• Why did testdisk deep search find C finally? You tried that before! Was it because WD Data Lifeguard Diagnostic did fix a problem?
• Why did you get a blinking cursor on boot? Was it because MBR was faulty (you did rewrite MBR already!) or was volume boot sector of C corrupt? It is located in sector 0 of C itself! So should be recovered by testdisk automatically.

So strange things did happen. Don't know why. BACKUP!

 

[zirch]

Make a backup asap. I still don't trust the harddrive 100%.

• Why was PQSERVICE 9GB, then 600MB, then 1.1GB? Don't know exactly what you did.
• Why did testdisk deep search find C finally? You tried that before! Was it because WD Data Lifeguard Diagnostic did fix a problem?
• Why did you get a blinking cursor on boot? Was it because MBR was faulty (you did rewrite MBR already!) or was volume boot sector of C corrupt? It is located in sector 0 of C itself! So should be recovered by testdisk automatically.

So strange things did happen. Don't know why. BACKUP!

Yeah, me neither. Yup, of course. Not going to underestimate the importance of backing up.

 

[zirch]

I have backed up and been using my laptop for more than a week now. So far there aren't any problems. Looks good. So I'm going to mark this thread as solved. Thanks to everyone who helped, especially Kaktussoft.http://www.sevenforums.com/member.php?u=162084