Welcome, Guest. Please login or register.
Did you miss your activation email?
May 25, 2013, 08:32:33 AM
Home Help Search Login Register
News: When requesting a refund, do NOT post order ID in forum!

+  DIY DataRecovery.nl Support forum
|-+  Support
| |-+  DiskPatch (Moderators: Tom, Joep)
| | |-+  Disaster Struck ...
0 Members and 1 Guest are viewing this topic. « previous next »
Pages: 1 [2] Go Down Print
Author Topic: Disaster Struck ...  (Read 2333 times)
Tom
Developer and Support Tech
Administrator
member
*****
Posts: 1148


WWW
« Reply #15 on: January 31, 2012, 03:55:10 PM »

Quote
Its reported to be 30 Gb (correct) with 10,2 Gb free
What does this mean? A disk is not the same as a volume, your description is confusing.

The DP analysis log says there should be a 30Gb volume on the disk. I'm not sure what you mean by 10,2 Gb free: unpartitioned disk space or free space in the volume? From your description I can't determine whether you are actually looking at the contents of the volume (meaning you can access it) or you are looking at an empty disk. If you are looking at the contents of the volume (is there a drive letter?) but are not seeing anything, something catastrophic happened and repairs are not possible. I'm kind of assuming that that is what you meant, and if so, it's over (unless perhaps if the disk has read problems and cloning overcomes that particular problem). The only thing to do then is what I said earlier: re-install and rebuild the situation by hand.

So, what exactly did you mean?
Logged

wabe
member

Posts: 13


« Reply #16 on: January 31, 2012, 04:03:34 PM »

Quote
Its reported to be 30 Gb (correct) with 10,2 Gb free
What does this mean? A disk is not the same as a volume, your description is confusing.


So, what exactly did you mean?
A ran a Live CD and used the file manager to inspect the "volume" which reports the above number when selecting "properties". The disk just contain one partition so disk is sort of the same as volume or partition at least in a layman's perspective.
I tried running partition repair and refresh MBR but no difference. The disk is most likely toast. I noticed one strange thing in DP when trying to activate after repair. The data disk (the one with only data) was set as "active".
Logged
Tom
Developer and Support Tech
Administrator
member
*****
Posts: 1148


WWW
« Reply #17 on: January 31, 2012, 04:44:45 PM »

Quote
I noticed one strange thing in DP when trying to activate after repair. The data disk (the one with only data) was set as "active".
Yes we saw that too, no biggy, but it might be clever to reset that. Look here for info:
http://www.diydatarecovery.nl/dp_manual/guide_partattr.htm
Quote
I tried running partition repair and refresh MBR but no difference.
Yes, as expected.

Okay, then I was right. You CAN see what's on the volume (you can access it) but nothing's there. Like I said, that's bad. My previous post applies.
Logged

wabe
member

Posts: 13


« Reply #18 on: February 01, 2012, 12:43:11 PM »

I replaced the drive and installed a basic XP installation it. Hooked up the old disk as an USB-drive it is now completely unreadable.
Next step is to figure out how to boot into the important OS i.e recreate the dual-boot possibility
Logged
Joep
Developer and Support Tech
Administrator
member
*****
Posts: 1162


WWW
« Reply #19 on: February 01, 2012, 08:18:55 PM »

Quote
Hooked up the old disk as an USB-drive it is now completely unreadable.

I don't know what that means (eg. Windows doesn't show it, throws an (error) message?), but if it contains important data you can try recovering that with iRecover.
Logged

--
Kind regards,
Joep
wabe
member

Posts: 13


« Reply #20 on: February 02, 2012, 09:46:44 AM »


I don't know what that means (eg. Windows doesn't show it, throws an (error) message?), but if it contains important data you can try recovering that with iRecover.
The drive shows up in file manager but cannot be opened.
Doesn't really matter since it's not the currently used OS - scrapped now

More importantly I got my system up running again after quite a struggle which involved, disconnecting all drives except the "win2008r2 OS-drive", using the recovery console on the Windows setup disk, reconstructing the  Bootmgr and finnally running a utility on the setup disk that do a "startup reparation".
It's seems there was some kind of data corruption on this drive not detected by DP. But all's well that end well!
Logged
Tom
Developer and Support Tech
Administrator
member
*****
Posts: 1148


WWW
« Reply #21 on: February 02, 2012, 10:33:04 AM »

Yes, pretty much as I expected this to go. Excellent.
Logged

Pages: 1 [2] Go Up Print 
« previous next »
Jump to:  


Login with username, password and session length

Powered by MySQL Powered by PHP Powered by SMF 1.1.18 | SMF © 2013, Simple Machines Valid XHTML 1.0! Valid CSS!