AbstractIntroductionMethodologyInitial ComparisonReFS MBRReFS VBRFSRSMACE TimesReFS Metadata BlockReFS MFTReFS Folder Naming ProcessDrive LabelsRecycle BinDesktop.ini FileSecurity IdentifierFolder Analysis.doc Analysis.txt Analysis.exe AnalysisReferencesAboutMisc ForensicsCPU Reballing StencilsItems For Sale

Master File Table (MFT) Comparison

NTFS has an MFT (Master File Table). Every file on an NTFS drive has at least one entry in the MFT and information such as file size, MACE times, permissions and content can be stored inside the entry. Each entry is usually 1024 bytes in size and starts with "FILE" or "FILE0". The 16 reserved MFT entries are in the table below with a brief description (Ntfs.com, n.d.b).  

Name

MFT Record No.

Purpose

$MFT

0

Contains one record for each file and folder on the volume.

$MFTMirr

1

Duplicate of the first four records of the MFT - in the case of a sector failure.

$LogFile

2

Contains a list of transaction steps for NTFS recoverability.

$Volume

3

Volume information.

$AttrDef

4

Contains a table of attribute names, numbers and descriptions.

$

5

Root folder.

$Bitmap

6

Representation of the volume, showing which clusters are in use (e.g. a map).

$Boot

7

Includes the Boot Partition Block which is used to mount the volume and bootstrap loader code.

$BadClus  

8

Contains bad clusters for the volume.

$Secure

9

Security descriptors for all files in the volume.

$Upcase

10

Used for lower to uppercase character conversion.

$Extend  

11

Used for optional extensions such as object identifiers and quotas.

 

12-15

Reserved for future use.

$Quota  

24

User assigned quota limits on the volume space.

$ObjId

25

Contains file object IDs.

$Reparse  

26

Information about files/folders reparse points.

 

In ReFS there is no MFT and subsequently no MFT entries. Having searched through the file system, there are no instances of "FILE0" or "FILE" which signifies the beginning of a MFT entry. FAT file systems do not use a Master File Table either.

UpCase Table

In ReFS there is an UpCase table, which is a system file (MFT entry number 10) in NTFS, found on the clean drive at offset 0x0103000. The size of the UpCase table is 128KB and contains each uppercase character in the Unicode alphabet. It is used for converting lowercase characters to the matching uppercase Unicode characters. On the blank ReFS drive, the $UpCase table was found at offset 0x0720000. Having extracted and compared both UpCase tables, it can be seen that they are identical. This was the expected result, as the Unicode characters are independent of file system and do not change between file systems. No UpCase table was found in the FAT file system.

UpCase Table

 

NTFS

ReFS

FAT32

Offset

0x0103000

0x0720000

n/a

 

Part of the UpCase can be seen below.

Offset(h)  00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F 10 11 12 13 14 15 16 17 18 19 1A 1B 1C 1D 1E 1F

000728180  C0 40 C1 40 C2 40 C3 40 C4 40 C5 40 C6 40 C7 40 C8 40 C9 40 CA 40 CB 40 CC 40 CD 40 CE 40 CF 40  À@á@Â@â@Ä@Å@æ@ç@È@É@ê@Ë@Ì@˜@Î@ï@

0007281A0  D0 40 D1 40 D2 40 D3 40 D4 40 D5 40 D6 40 D7 40 D8 40 D9 40 DA 40 DB 40 DC 40 DD 40 DE 40 DF 40  Ɖ@ñ@Ò@Ó@Ô@Õ@Ö@×@ø@Ù@ú@û@Ü@Ý@þ@ß@

0007281C0  E0 40 E1 40 E2 40 E3 40 E4 40 E5 40 E6 40 E7 40 E8 40 E9 40 EA 40 EB 40 EC 40 ED 40 EE 40 EF 40  À@á@Â@â@Ä@Å@æ@ç@È@É@ê@Ë@Ì@˜@Î@ï@

0007281E0  F0 40 F1 40 F2 40 F3 40 F4 40 F5 40 F6 40 F7 40 F8 40 F9 40 FA 40 FB 40 FC 40 FD 40 FE 40 FF 40  Ɖ@ñ@Ò@Ó@Ô@Õ@Ö@÷@ø@Ù@ú@û@Ü@Ý@þ@Ÿ@

000728200  00 41 01 41 02 41 03 41 04 41 05 41 06 41 07 41 08 41 09 41 0A 41 0B 41 0C 41 0D 41 0E 41 0F 41  .A.A.A.A.A.A.A.A.A.A.A.A.A.A.A.A

000728220  10 41 11 41 12 41 13 41 14 41 15 41 16 41 17 41 18 41 19 41 1A 41 1B 41 1C 41 1D 41 1E 41 1F 41  .A.A.A.A.A.A.A.A.A.A.A.A.A.A.A.A

000728240  20 41 21 41 22 41 23 41 24 41 25 41 26 41 27 41 28 41 29 41 2A 41 2B 41 2C 41 2D 41 2E 41 2F 41  A!A"A#A$A%A&A'A(A)A*A+A,A-A.A/A

000728260  30 41 31 41 32 41 33 41 34 41 35 41 36 41 37 41 38 41 39 41 3A 41 3B 41 3C 41 3D 41 3E 41 3F 41  0A1A2A3A4A5A6A7A8A9A:A;A<A=A>A?A

 

Attributes

Attributes are how files are represented in NTFS. Information about each file is stored in attributes, this includes the file name ($FILE_NAME) and security information ($SECURITY_DESCRIPTOR). When analysing the hexadecimal of the NTFS drive these can be found throughout the file system at different offsets (see the block below). When analysing the ReFS drive though, there are few that can be found and while being similar they aren't direct matches to the NTFS counterpart.  

Offset(h)  00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F 10 11 12 13 14 15 16 17 18 19 1A 1B 1C 1D 1E 1F

000123000  24 00 53 00 54 00 41 00 4E 00 44 00 41 00 52 00 44 00 5F 00 49 00 4E 00 46 00 4F 00 52 00 4D 00  $.S.T.A.N.D.A.R.D._.I.N.F.O.R.M.

000123020  41 00 54 00 49 00 4F 00 4E 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  A.T.I.O.N.......................

000123040  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................................

000123060  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................................

000123080  10 00 00 00 00 00 00 00 00 00 00 00 40 00 00 00 30 00 00 00 00 00 00 00 30 00 00 00 00 00 00 00  ............@...0.......0.......

0001230A0  24 00 41 00 54 00 54 00 52 00 49 00 42 00 55 00 54 00 45 00 5F 00 4C 00 49 00 53 00 54 00 00 00  $.A.T.T.R.I.B.U.T.E._.L.I.S.T...

0001230C0  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................................

0001230E0  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................................

000123100  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................................

000123120  20 00 00 00 00 00 00 00 00 00 00 00 80 00 00 00 00 00 00 00 00 00 00 00 FF FF FF FF FF FF FF FF  ...........€...........ŸŸŸŸŸŸŸŸ

000123140  24 00 46 00 49 00 4C 00 45 00 5F 00 4E 00 41 00 4D 00 45 00 00 00 00 00 00 00 00 00 00 00 00 00  $.F.I.L.E._.N.A.M.E.............

000123160  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................................

000123180  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................................

0001231A0  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................................

0001231C0  30 00 00 00 00 00 00 00 00 00 00 00 42 00 00 00 44 00 00 00 00 00 00 00 42 02 00 00 00 00 00 00  0...........B...D.......B.......

0001231E0  24 00 56 00 4F 00 4C 00 55 00 4D 00 45 00 5F 00 56 00 45 00 52 00 53 00 49 00 4F 00 4E 00 00 00  $.V.O.L.U.M.E._.V.E.R.S.I.O.N...

 

One that is found is the Security Descriptor. In NTFS this is $SECURITY_DESCRIPTOR and in ReFS it is Security Descriptor Stream (hexadecimal shown below). In NTFS this attribute describes who owns and can access the file (ntfs.com, n.d.b). It is very likely that ReFS utilises it for a similar purpose.

Offset(h)  00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F 10 11 12 13 14 15 16 17 18 19 1A 1B 1C 1D 1E 1F

000764560  68 00 00 00 10 00 18 00 00 00 28 00 40 00 00 00 20 00 00 80 00 00 00 00 20 05 00 00 00 00 00 00  h.........(.@... ..€.... .......

000764580  00 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0C 00 34 00 53 00 65 00 63 00 75 00 72 00 69 00  ..................4.S.e.c.u.r.i.

0007645A0  74 00 79 00 20 00 44 00 65 00 73 00 63 00 72 00 69 00 70 00 74 00 6F 00 72 00 20 00 53 00 74 00  t.y. .D.e.s.c.r.i.p.t.o.r. .S.t.

0007645C0  72 00 65 00 61 00 6D 00 58 04 00 00 10 00 38 00 08 00 48 00 10 04 00 00 30 00 01 00 53 00 65 00  r.e.a.m.X.....8...H.....0...S.e.

0007645E0  63 00 75 00 72 00 69 00 74 00 79 00 20 00 44 00 65 00 73 00 63 00 72 00 69 00 70 00 74 00 6F 00  c.u.r.i.t.y. .D.e.s.c.r.i.p.t.o.

000764600  72 00 20 00 53 00 74 00 72 00 65 00 61 00 6D 00 A8 00 00 00 28 00 01 00 00 00 00 00 10 01 00 00  r. .S.t.r.e.a.m.¨...(...........

000764620  10 01 00 00 02 00 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 F9 D2 2B 55 33 24 D0 01  ........................ÙÒ+U3$Ɖ.

000764640  F9 D2 2B 55 33 24 D0 01 F9 D2 2B 55 33 24 D0 01 F9 D2 2B 55 33 24 D0 01 20 00 00 00 00 00 00 00  ÙÒ+U3$Ɖ.ÙÒ+U3$Ɖ.ÙÒ+U3$Ɖ. .......

 

Another that is similar between the two drives is to do with the volume information. In NTFS there are three volume related attributes, these being $VOLUME_VERSION, $VOLUME_NAME and $VOLUME_INFORMATION. Each one of these attributes has a different purpose, while being relatively self-explanatory. The first one ($VOLUME_VERSION) before becoming obsolete, was the version of the volume. As can be guessed $VOLUME_NAME was the name/label of the volume and the final one would include the version (taking over from the $VOLUME_VERSION attribute) and the state of the volume. In ReFS the similar attribute is Volume Direct IO File (hexadecimal shown below). Like the example of Security Descriptor Stream it is likely that this is used in a similar way to how it is in NTFS.

Offset(h)  00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F 10 11 12 13 14 15 16 17 18 19 1A 1B 1C 1D 1E 1F

000764A20  60 00 00 00 10 00 18 00 00 00 28 00 38 00 00 00 20 00 00 80 00 00 00 00 20 05 00 00 00 00 00 00  `.........(.8... ..€.... .......

000764A40  00 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0C 00 2A 00 56 00 6F 00 6C 00 75 00 6D 00 65 00  ..................*.V.o.l.u.m.e.

000764A60  20 00 44 00 69 00 72 00 65 00 63 00 74 00 20 00 49 00 4F 00 20 00 46 00 69 00 6C 00 65 00 FF FF  .D.i.r.e.c.t. .I.O. .F.i.l.e.ŸŸ

000764A80  50 04 00 00 10 00 2E 00 08 00 40 00 10 04 00 00 30 00 01 00 56 00 6F 00 6C 00 75 00 6D 00 65 00  P.........@.....0...V.o.l.u.m.e.

000764AA0  20 00 44 00 69 00 72 00 65 00 63 00 74 00 20 00 49 00 4F 00 20 00 46 00 69 00 6C 00 65 00 00 00  .D.i.r.e.c.t. .I.O. .F.i.l.e...

000764AC0  A8 00 00 00 28 00 01 00 00 00 00 00 10 01 00 00 10 01 00 00 02 00 00 00 00 00 00 00 00 00 00 00  ¨...(...........................

000764AE0  00 00 00 00 00 00 00 00 F9 D2 2B 55 33 24 D0 01 F9 D2 2B 55 33 24 D0 01 F9 D2 2B 55 33 24 D0 01  ........ÙÒ+U3$Ɖ.ÙÒ+U3$Ɖ.ÙÒ+U3$Ɖ.

000764B00  F9 D2 2B 55 33 24 D0 01 20 00 00 00 00 00 00 00 20 05 00 00 00 00 00 00 00 01 00 00 00 00 00 00  ÙÒ+U3$Ɖ. ....... ...............

 

 

ReFS Metadata Block Template

Each of the similar attribute-style entries mentioned above appear in the same metadata block as some other descriptive information too. They appear to be structured into the metadata block in the same way that files and folders are when added to the file system. For example, where the volume is mentioned is where the filename would appear, and where the security descriptor appears is where the folder the file is present in would appear. This points to the possible conclusion that this block is a template metadata block, which the others (when files etc. are added to the file system) will be based on.

Within this block, which we will assume is a template from here on in, is a mention for File System Metadata as well as the two previously mentioned items. This is another reason that this block could be an example one, because File System Metadata is a generic term for the contents that would appear in the part of the block that this phrase appears in.

 

$I30 Index Attribute

When searching through the hexadecimal of the blank ReFS drive, the only instances of "$ "(the start of the name of any attributes in NTFS) that are found are the instances of "$I30" (not including Recycle Bin). This is the Windows Index Attribute. Every single directory in the file system has am $I30 attribute and when any change occur to the directories the changes must also occur in the $I30 attribute. Through analysing the $I30 Index Attribute, it is possible that forensic investigators can find evidence of files that have been deleted or overwritten (Tilbury, 2011).

 


 

File Contents in ReFS

When analysing the hexadecimal of drives, the way ReFS stores files appears to have more similarities with FAT32 than it does with NTFS.

ReFS stores the file's contents at particular offsets with no other data tied to it. For example, in the tests, the file's contents has been stored at offset 0x07B0000, with no other data attached to it, or physically near it in the hexadecimal. This is the same as FAT32.

This is very different to NTFS however, as the data (in the example below) is stored within a MFT entry, with the file name and file size in the same entry. Examples of all three are below.

NTFS drive:

Offset(h)  00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F 10 11 12 13 14 15 16 17 18 19 1A 1B 1C 1D 1E 1F

04010A000  46 49 4C 45 30 00 03 00 B9 48 80 01 00 00 00 00 02 00 01 00 38 00 01 00 A0 01 00 00 00 04 00 00  FILE0...¹H€.........8... .......

04010A020  00 00 00 00 00 00 00 00 04 00 00 00 28 00 00 00 04 00 00 00 00 00 00 00 10 00 00 00 60 00 00 00  ............(...............`...

04010A040  00 00 00 00 00 00 00 00 48 00 00 00 18 00 00 00 CE E5 1D 83 7F 2B D0 01 B4 D2 56 A1 65 41 D0 01  ........H.......ÎÅ.ƒ.+Ɖ.´ÒV¡eAƉ.

04010A060  B4 D2 56 A1 65 41 D0 01 CE E5 1D 83 7F 2B D0 01 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ´ÒV¡eAƉ.ÎÅ.ƒ.+Ɖ. ...............

04010A080  00 00 00 00 0C 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30 00 00 00 78 00 00 00  ........................0...x...

04010A0A0  00 00 00 00 00 00 02 00 5E 00 00 00 18 00 01 00 05 00 00 00 00 00 05 00 CE E5 1D 83 7F 2B D0 01  ........^...............ÎÅ.ƒ.+Ɖ.

04010A0C0  CE E5 1D 83 7F 2B D0 01 CE E5 1D 83 7F 2B D0 01 CE E5 1D 83 7F 2B D0 01 00 00 00 00 00 00 00 00  ÎÅ.ƒ.+Ɖ.ÎÅ.ƒ.+Ɖ.ÎÅ.ƒ.+Ɖ.........

04010A0E0  00 00 00 00 00 00 00 00 20 00 00 00 00 00 00 00 0E 00 68 00 65 00 6C 00 6C 00 6F 00 77 00 6F 00  ........ .........h.e.l.l.o.w.o.

04010A100  72 00 6C 00 64 00 2E 00 64 00 6F 00 63 00 00 00 40 00 00 00 28 00 00 00 00 00 00 00 00 00 03 00  r.l.d...d.o.c...@...(...........

04010A120  10 00 00 00 18 00 00 00 16 77 09 C1 55 AD E4 11 94 17 E4 66 86 94 ED AA 80 00 00 00 60 00 00 00  .........w.áU.Ä.".Äf†"˜ª€...`...

04010A140  00 00 18 00 00 00 01 00 43 00 00 00 18 00 00 00 49 20 6C 69 6B 65 20 64 69 6E 6F 73 61 75 72 73  ........C.......I like dinosaurs

04010A160  2E 20 4D 79 20 66 61 76 6F 75 72 69 74 65 20 69 73 20 61 20 56 65 6C 6F 63 69 72 61 70 74 6F 72  . My favourite is a Velociraptor

04010A180  20 61 6E 64 20 61 20 70 74 65 72 6F 64 61 63 74 79 6C 2E 00 00 00 00 00 FF FF FF FF 82 79 47 11  and a pterodactyl......ŸŸŸŸ‚yG.

 

FAT32 drive:

Offset(h)  00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F 10 11 12 13 14 15 16 17 18 19 1A 1B 1C 1D 1E 1F

000D02FC0  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................................

000D02FE0  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................................

000D03000  49 20 6C 69 6B 65 20 64 69 6E 6F 73 61 75 72 73 2E 20 4D 79 20 66 61 76 6F 75 72 69 74 65 20 69  I like dinosaurs. My favourite i

000D03020  73 20 61 20 56 65 6C 6F 63 69 72 61 70 74 6F 72 20 61 6E 64 20 61 20 70 74 65 72 6F 64 61 63 74  s a Velociraptor and a pterodact

000D03040  79 6C 2E 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  yl..............................

000D03060  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................................

000D03080  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................................

 

ReFS drive:

Offset(h)  00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F 10 11 12 13 14 15 16 17 18 19 1A 1B 1C 1D 1E 1F

0007AFFC0  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................................

0007AFFE0  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................................

0007B0000  49 20 6C 69 6B 65 20 64 69 6E 6F 73 61 75 72 73 2E 20 4D 79 20 66 61 76 6F 75 72 69 74 65 20 69  I like dinosaurs. My favourite i

0007B0020  73 20 61 20 56 65 6C 6F 63 69 72 61 70 74 6F 72 20 61 6E 64 20 61 20 70 74 65 72 6F 64 61 63 74  s a Velociraptor and a pterodact

0007B0040  79 6C 2E 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  yl..............................

0007B0060  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................................

0007B0080  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................................