Welcome to every day's Dutra forensics. I'm your host, your Sunday said, and I'll be guiding you through today's file system. The fact power system.
In today's video, we're going to define the fat file system.
Review some of the basic concepts off the fat follow system,
gain some understanding of the basic structure and functionality of the system itself.
So what is the foul allocation table? Also noticed? Effect
It's a simple fall system originally designed for small just on simple file structures. The name is just based around its organization,
and this allocation table is that at a fixed location at the beginning of the volume,
two copies of the file allocation tables are kept,
and this is a way to check the integrity off the
system itself. If one becomes corrupt or damage, you're able to determine based on the copy
the fat system structure. If you look at the top right portions video, it's split into the partition boots sectors. Your first copy of a fat system, your Dubica, copy that root folder and then everything else. This is other folders and files.
The root folder and the file allocation tables are set in a fixed location.
Its opinion on which fat system you're using. You see at the bottom, right?
There's three separate fat systems. There's fat. 12 5 16 fat 32.
A fat file system is allocated by clusters,
the closer sizes based on which system we're using. Each system has its own default values. Size, as you can tell by the table
for the fat fall system of cluster number must fit within a 16 bits and must be a power of two.
So to understand how fouls are allocated,
not understand how files are allocated within a fat file system.
As seen from this image,
zeros are the memory spaces.
F f f f tends to determine the end of a file. So if you see any,
if you see these four Hexi decimal values,
the last that determines the last cluster of a file.
So the table allocation, as we said, is resized at the beginning of the volume.
Two copies are kept to protect the volume and their store in a fixed location.
The root folder, which is located after the duplicate file system, contains an entry for each file is just
This is very specific location, the disk, and it's a fix sized
within the fact file system. We have folders, and these are structured differently. Each folder, as you see on the right, has the following information stored about folder itself.
It's the name of the folder.
The Attribute bits Creation, time creation date, Last Access, Last Modified Time, Last Modified Date,
which is just starting cluster of that file
and the final size itself.
The folders have a scent of 32 bit folder entries for each folder and some folder.
There's no organization to the fat folder structure.
That folder is given the first available location on the body.
The starting cluster number is the address of the first cluster to used, so you'll determine its spot. So think of cluster numbers as your address,
so you may be address upon to three and then you're straight name.
That is the beginning portion of your clusters, so that is where you be able to find it,
and then each cluster towards the end of file will have a pointer to the fallen cluster. So if a file takes up multiple spaces, your first closer would say OK, the next portion off. This file is located. Cluster 1235
you goto Location one truth
1235 At the end, you'll have a pointer to next. 1236
At the end of that cluster, you'll have an indication of F f f f, which is the end of that file.
So you're looking at the screen shot from this illegal profile until that could be used for forensics analysis of an image
of a virtual hardest contest.
The image that you're showing is the beginning
sections of a fat ball system.
It's important to note that the
virtual hard this file begins with a master boot record, this master boot record can locate the ended individual partitions. So to you, this might not seem like information or anything that you can relate it to your languages.
using tools that we have learned earlier were earlier, like the conversions
from Hexi decimal to binary or decimal can help us understand what these numbers need.
So this is also format it.
This information is actually structured. So
these three these four bites may mean something these additional four bites might mean something
these four bites might mean something and so on
this information to you looks like
Alien nine. Which however,
once you go down into bites by bites, you can understand what it is. And that's what we're gonna be doing in the next video.
Not going to start you off with anything right now,
but for your own time. Go look at the pdf. Find this screenshot. You could even go to the site where I got the screenshots from
including the next videos
and see if you can yourself
breakdown may be the 1st 34 lines of this to determine what it ISS. This is the master boot record of a fat ball system.
I also want to note that as you can see on the right, if you're looking at eight times, this may be showing actual date time, so it
it eases your eyes and your conversions
sound. Here is you can see data content data when you're looking at a file shows the information in this format.
So in summary in today's lecture, we review the fat follows systems system structure
the Allah, the way files are located quickly touched upon the root folder.
How folders are structured within fat file system and reviewed the partition. Boot information wasn't shared about the master boot record, but we'll go into more details on that and then later videos. So I hope you enjoyed today's video and I'll catch you on the next one.