TSK_LOADDB(1)
π TSK_LOADDB β ok bestie, let's get you a database β¨
So like, tsk_loaddb is a lil command from the General Commands Manual (section 1, obvi) and it does one job and it does it gorgeously: it scoops all the metadata out of a disk image and drops it into a SQLite database. π«Ά
β¨ NAME β¨
tsk_loaddb β populate a SQLite database with metadata from a disk image π
πΈ SYNOPSIS πΈ
tsk_loaddb [-ahkvV] [ -i imgtype ] [ -b dev_sector_size ] [ -i imgtype ]
[ -d database ] image [images]
(Yes, -i imgtype shows up twice in there. We don't ask questions, we just report it faithfully. π)
π DESCRIPTION π
tsk_loaddb loads disk information from an image into a SQLite database. And then? Other languages' tools can come through and do analysis on it. It's giving interoperability. π
By default, the database lives in the same directory as the image, with ".db" appended to the name. OR you can pick your own name with -d, because you're the main character and you get choices. π
Here's the whole cast of arguments, no cap:
-aβ Adds the image to an existing database instead of creating a brand new one. It requires that-dalso be specified, so don't try it alone bestie, it will not work. π-ddatabase β Path for the database. Default is the same directory as the image, with the name derived from the image name.-vβ verbose output tostderrπ£οΈ-Vβ Print version β-kβ Don't create the block data table. That table maps each block to the file that allocated it. Skipping it makes this program run faster. πββοΈπ¨-hβ Calculate the MD5 hash value for each file and store it in a table. Heads up: this makes the program run slower. π-iimgtype β The format of the image file, likeraw. Use-i listto list all the supported types. If you don't give it, autodetection methods are used. π-bdev_sector_size β The size (in bytes) of the device sectors. If you don't give it, autodetection methods are used.image [images]β The disk or partition image to read, whose format you gave with-i. You can hand over multiple image file names if the image is split into multiple segments. And get this: if you only give one image file and its name is the first in a sequence (like, as indicated by ending in'.001'), the subsequent image segments will be included automatically. πͺβ¨
π EXAMPLES π
To load image data from image.dd to image.dd.db:
# tsk_loaddb ./image.dd
That's it. That's the whole vibe. π
π¦ AUTHOR π¦
Brian Carrier <carrier at sleuthkit dot org> β an absolute icon, no notes. π
Send documentation updates to <doc-updates at sleuthkit dot org> β they want your feedback fr fr. π«Ά
And that's a wrap on the tsk_loaddb(1) page from the General Commands Manual (TSK_LOADDB 1), bestie. It's from the Sleuth Kit, and you already know it ate. π
β¨
π¦ where this page comes from
- arch rolling: sleuthkit 4.15.0-1 Β· CPL-1.0 AND GPL-2.0-or-later AND IPL-1.0
- epel 10: sleuthkit 4.15.0-2.el10_3 Β· CPL-1.0 AND IPL-1.0 AND GPL-2.0-or-later
- epel 9: sleuthkit 4.15.0-2.el9 Β· CPL-1.0 AND IPL-1.0 AND GPL-2.0-or-later
- fedora 43: sleuthkit 4.14.0-4.fc43 Β· CPL-1.0 AND IPL-1.0 AND GPL-2.0-or-later
- fedora 43: sleuthkit 4.15.0-2.fc43 Β· CPL-1.0 AND IPL-1.0 AND GPL-2.0-or-later
- fedora 44: sleuthkit 4.14.0-5.fc44 Β· CPL-1.0 AND IPL-1.0 AND GPL-2.0-or-later
- fedora 44: sleuthkit 4.15.0-2.fc44 Β· CPL-1.0 AND IPL-1.0 AND GPL-2.0-or-later
- nixos 26.05: sleuthkit 4.14.0
- nixpkgs unstable: sleuthkit 4.15.0
- opensuse-leap 16.0: sleuthkit 4.12.1-bp160.1.13 Β· CPL-1.0 AND IPL-1.0 AND GPL-2.0-or-later
- opensuse-leap 16.0: sleuthkit 4.12.1-bp160.1.13 Β· CPL-1.0 AND IPL-1.0 AND GPL-2.0-or-later
- opensuse-leap 16.0: sleuthkit 4.12.1-bp160.1.13 Β· CPL-1.0 AND IPL-1.0 AND GPL-2.0-or-later
- opensuse-leap 16.0: sleuthkit 4.12.1-bp160.1.13 Β· CPL-1.0 AND IPL-1.0 AND GPL-2.0-or-later
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms