The first ntfs boot sector is unreadable or corrupt

Decryption of partition prospered and it composed decrypted data on partition D. now when I ran the command"chkdsk D: /f"it gave adhering to message(s):

The kind of file mechanism is NTFS.

You watching: The first ntfs boot sector is unreadable or corrupt

The first boot sector is unreadable or corrupted

Reading second boot sector instead

Unable to determine the version and volume state. CHKDSK aborted.


I have actually developed .img file as recovery from that partition however .img file has corrupt header. so no routine opens up it or resolve it.. Its dimension is exceptionally huge around 150 GB.

Note that D is not obtainable in this case....

I have reextended an other partition named C properly that was likewise little locker encrypted...

if you need more details, i am below and I have the right to provide you further details...

Please vivaworldcup.info Engineers and also technical are asked for...

Note: Some indevelopment has actually been rerelocated from my first write-up as a result of some factors. It will be ago soon after some check/correction/evaluation.


This thread is locked. You have the right to follow the question or vote as advantageous, but you cannot reply to this threview.
I have the exact same question (309)
Subscribe Subscribe Subscribe to RSS feed

Replies (19) 


* Please attempt a lower web page number.

* Please enter just numbers.


1 2 Next

* Please attempt a lower page number.

* Please enter only numbers.


Previous Next

Sh_of_Pakistan
Replied on December 2, 2014
In reply to Sh_of_Pakistan's short article on November 30, 2014

Please reply anyone... I have been waiting for your response....

Please Professionals from vivaworldcup.info....


Was this reply helpful?
Yes No

Sorry this didn't assist.


Great! Thanks for your feedago.

See more: Destiny 2 Pc Memory Leak Fix Is Coming Via Patch, Memory Leak Issue

How satisfied are you through this reply?


Thanks for your feedearlier, it helps us improve the site.

How satisfied are you via this reply?


Thanks for your feedearlier.


*

A. User
Replied on December 3, 2014
In reply to Sh_of_Pakistan's write-up on December 2, 2014

Hello,

Thank you for your reply.

I am sorry for late response.

I appreciate your time and also patience.

As you discussed that you are trying to retrieve data from an encrypted drive or volume, I would imply you to try using procedures gave in this post and also examine if it helps.

Refer:Scenario 16: Using the BitLocker Repair Tool to Recover a Drivehttp://technet.vivaworldcup.info.com/en-us/library/ee523219

I hope this helps.

Thank you


1 perkid found this reply advantageous

·

Was this reply helpful?
Yes No

Sorry this didn't assist.


Great! Thanks for your feedago.

How satisfied are you via this reply?


Thanks for your feedback, it helps us improve the website.

How satisfied are you through this reply?


Thanks for your feedearlier.



Sh_of_Pakistan
Replied on December 3, 2014
In reply to A. User's write-up on December 3, 2014

Thank you for your reply.

I have actually tried this option already and also through the help of this I have recovered Partition-II (C Drive, 75 GB).

I got recovery.img (or I might obtain D or any kind of various other Drive as output as in complying with command also ) as output file and also then placed that got my required files.

But difficulty with the last partition is that it cannot be mounted. (Header of this file is corrupt, various programs say. Here I would like to point out that I produced recoexceptionally.rar as outptut, or .zip papers yet these all have actually very same error saying header is corrupted)

I acquire D as output but that D Drive is not being opened. It shows the error "CHKDSK aborted" as discussed previously in my write-up...

See more: Inwin A1 Front Panel Usb Not Working : Buildapc, Front Panel Usb Ports Not Working

furthereven more i would certainly favor to include this I had actually stated Rip Linux. I ran that aobtain and also that method created D as output (in this case D is encrypted , in earlier instances it was not encrypted) So it decrypted and as result I got E as output yet that E drive shows the exact same error (CHKDSK aborted).