-
Notifications
You must be signed in to change notification settings - Fork 46
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TSKVolumeSystem bytes_per_sector #45
Comments
Not at the moment. I would also need to check if and how that can be propagated in pytsk and TSK.
Since Python os does not support Hence try: import pysmdev
smdev_handle = pysmdev.handle()
smdev_handle.open('\\\\.\\PHYSICALDRIVE1')
print(smdev_handle.bytes_per_sector)
smdev_handle.close() |
Generated a 4k MBR test image
By default mmls (and therefore assuming libtsk/pytsk as well) this as 512 bytes per sector. With a manual override:
To consider:
|
Looks like sleuthkit has a long standing issue about this sleuthkit/sleuthkit#752 |
I have a drive that has geometry with 4096 bytes per sector.
When I create a TSKVolumeSystem, and feed it the volume_system_path_spec of TYPE_INDICATOR_TSK_PARTITION, it shows that the TSKVolumeSystem.bytes_per_sector attribute as 512. This interns shows the incorrect offset for the partitions.
Is there a way to find and set the bytes per sector for a TSKVolumeSystem?
Here is what FTK Imager shows for the drive:
Partition Start Sector [2048]:
Offset then to partition is 2048 * 4096 = 8388608
I see in dfvfs TSKVolumeSystem._Parse() there is:
self.bytes_per_sector = tsk_partition.TSKVolumeGetBytesPerSector(tsk_volume)
Am I not passing something or are the BytesPerSector not being found correctly?
Here is output and an example code I used.
The text was updated successfully, but these errors were encountered: