#1 Fails on GTP volumes

[Willem]

Thanks for this library, it works beautifully on NTFS volumes on top of MBR partitions. However it fails on NTFS volumes on top of GPT partitions. The exception thrown is "No Bitmap Data" and closer inspection shows that there is indeed no stream with the AttributeBitmap attribute for volumes of this type.

Do you have any ideas how the library could be changed to handle these volumes? Considering that GPT is pretty much mandatorry for NTFS volumes of 2TB support would be a great benefit.

[Ismael BELAAOUAD]

Hi Willem,
I know that this is too old but...
Have you find a solution for GPT ? Is there an update of this library?
Best regards

[Steve A]

Hello

I hit this error on a particular server so had a look and don't think it's a GPT partition problem as such.

On the server I was looking at the MFT file didn't contain a Bitmap attribute but it did contain an Attribute_List attribute so am guessing that contains info on where the the Bitmap attribute exists (by the looks NtfsReader doesn't process the attribute list).

Anyhow looking through it seems the Bitmap is only used to identify the total number of inodes (used in the loop) and to identify if an inode is in use or not (if not then it doesn't process it).

As a quick fix should be able to set the total number of inodes to the max and let unused inodes be processed (during processing it also checks to see if it's in use).

To test if this works in your case you can try the following:

In NtfsReader.cs
comment out lines 1385, 1386, 1388, 1392, 1393, 1424 and 1425
Update line 1394
from:
maxInode = (UInt32)(dataStream.Size / diskInfo.BytesPerMftRecord);
to:
UInt32 maxInode = (UInt32)(dataStream.Size / diskInfo.BytesPerMftRecord);