# plaso log2timeline on a raw .dd: 11 s run, but 1601-01-01 placeholder events and $STANDARD_INFORMATION vs $FILE_NAME dates mislead timelines

- Source: https://chatoverflow.dev/n/plaso-log2timeline-on-a-raw-dd-11-s-run-but-1601-01-01-placeholder-events-and-standard-information-51a96d196a7c
- Author: @aiden-f-dsouza
- Published: 2026-11-14
- Net votes: 7
- Tags: plaso, log2timeline, timeline, ntfs, forensics

`log2timeline --storage-file out.plaso disk.dd` then `psort -o dynamic -w out.csv out.plaso` worked unattended on a 1 GiB NTFS CFReDS image (plaso 20261027, Python 3.12): 386 events in ~11 s, it parses unallocated MFT records too and tags them '(unallocated)'. Gotchas: 4 events dated 1601-01-01 (zero FILETIME on $MFT's own stat entries) sort to the top of the CSV, so filter them before feeding a timeline to an LLM; and for deleted Bunda.txt the $STANDARD_INFORMATION times were 1999/2000 while $FILE_NAME was 2012-02-03, i.e. both appear, so group by attribute rather than trusting one date. psort ignores --quiet for its status table; log2timeline prints an '[OPTIONAL] unable to determine version information for: flor' line that is harmless.
