Hello,
I want to find the address of a free space in HDD. For example, I want to know that at which address "/home" started and finished.
The "filefrag" command can work for files.
Thank you.
Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230
How to find the physical address of a specific HDD space?
-
- Global Moderator
- Posts: 3049
- Joined: 2017-09-17 07:12
- Has thanked: 5 times
- Been thanked: 132 times
Re: How to find the physical address of a specific HDD space
filefrag works on directories too. Directories are just special files.
But what is the relationship between the blocks allocated to a directory, "specific space" (what specific space ?) and "free space" (what free space ?) ?
But what is the relationship between the blocks allocated to a directory, "specific space" (what specific space ?) and "free space" (what free space ?) ?
-
- Global Moderator
- Posts: 2678
- Joined: 2018-06-20 15:16
- Location: Colorado
- Has thanked: 41 times
- Been thanked: 196 times
Re: How to find the physical address of a specific HDD space
I've used a hex editor to directly view the disk, paid work using windows tools long ago... The files within /home will not be in a region recognizable as /home since they are not. As p.H. stated the directory is a special file and not analogous to a partition. The files can be anywhere within the partition mixed with files from other directories within the same partition. Recovery relies on the file headers and a little magic to recognize the last sector, the next header -1. I would copy and paste from the disk editor to a file with the proper extension and attempt to open it, success or failure then obvious. Certain file types can have extra cruft or be clipped and still open, some need the exact real length.
I can list what I use if needed. I still have the functionality in an XP vm. I still occasionally need it for a data logger that barfs every so often by incorrectly closing the log file. The telltale is a 2k file that should be MB's. So I pull out all the data between headers to a file, open the file, and it is a tolerant format that I can trim back to clean and resave.
Foremost may be useful, it can decipher the headers of common file types and automate the process. Or some hex editor and do it manually. In a disk/hex editor you will see the structure and the addresses.
I can list what I use if needed. I still have the functionality in an XP vm. I still occasionally need it for a data logger that barfs every so often by incorrectly closing the log file. The telltale is a 2k file that should be MB's. So I pull out all the data between headers to a file, open the file, and it is a tolerant format that I can trim back to clean and resave.
Foremost may be useful, it can decipher the headers of common file types and automate the process. Or some hex editor and do it manually. In a disk/hex editor you will see the structure and the addresses.