MultiDrive – free backup, clone & wipe disk utility from Atola Technology

All times are UTC - 5 hours [ DST ]




Post new topic Reply to topic  [ 12 posts ] 
Author Message
 Post subject: DLT - Data Logic Tools - Recovery Suite
PostPosted: November 6th, 2026, 7:28 
Offline
User avatar

Joined: October 20th, 2017, 7:29
Posts: 23
Location: Turkey
DLT - Data Logic Tools - Recovery Suite 3.2.0 (Windows) - recovery, photo/video repair, disk clone & secure wipe (free scan)

DLT - Data Logic Tools - Recovery Suite 3.2.0 (Windows 10/11 x64)
Recovery · photo/video repair · disk imaging · secure wipe - free scan and preview

Hi HDDGuru,

I am the developer of DLT - Data Logic Tools - Recovery Suite. This is a vendor post, so I will keep it factual: what the software does, how it does it, what it does not do, and how to evaluate it. The suite is commercial. Scanning and preview are free; saving recovered files, cloning, repair output and wiping require a licence. Feedback, bug reports and technical criticism are welcome in this thread.

One Windows application, eight tools

1. Drive Recovery
  • Intact-first pass: reads the NTFS Master File Table ($MFT) directly, decodes $DATA attributes and VCN->LCN data runs, and walks $INDEX_ROOT / $INDEX_ALLOC folders, so deleted files come back with original names and paths.
  • FAT32 and exFAT cluster-chain recovery, including fragmented files; exFAT is prioritised for modern SD/microSD cards.
  • Signature-based deep scan when metadata is gone: JPEG, MP4, RIFF, ZIP and hundreds of other headers/footers are carved from raw sectors.
  • Sources: logical drives, whole physical disks, and raw images (.img, .dd, .raw).
  • Recycle Bin recovery: deleted $R* user files are listed; only $I* index records and desktop.ini are hidden.
  • Scan area: restrict Deep Scan to a start/end offset in GB (or a preset), useful on large or failing drives.
  • Resilient scanning: slow or unreadable blocks are retried, then skipped in growing steps so the scan continues instead of appearing frozen. The finish message lists skipped byte ranges.
  • Honest status: a truncated image, unplugged drive or unreadable area is reported as "Scan incomplete" with the byte reached - not as success.
  • File-backed images are read end-to-end in Deep/Auto mode; filesystem extents are not skipped, so data past the first gigabyte is not missed.
  • Scanning is read-only; nothing is written to the source.

2. Partition Recovery
  • Searches for surviving metadata: NTFS boot-sector mirrors, FAT backup sectors, and the GPT backup header at the end of the disk.
  • Rebuilds a lost partition table from 0x55AA boot-sector signatures; quick scan for intact tables, deep scan sector by sector for damaged ones.
  • Partition tools included: Initialize Disk (MBR/GPT) and in-place MBR<->GPT conversion, with the existing table backed up first, explicit confirmation, and Administrator rights required.

3. Photo Repairing Lab
  • JPEG repair: DQT (quantisation) and DHT (Huffman) tables transplanted from a healthy reference image; SOI/EOI and restart markers re-synced.
  • "Beheaded" JPEGs: valid entropy-coded scan data re-spliced onto a rebuilt frame header.
  • RAW structure repair: TIFF/IFD chain validation and pointer repair for CR2/CR3, NEF, ARW, DNG, ORF, RW2, RAF, PEF, SRW, X3F and more.
  • When RAW image data is damaged, the embedded full-resolution JPEG preview is extracted directly from the RAW container. EXIF thumbnails are also recovered.
  • Every output is checked with a full decoder pass; "100% Healthy" is only reported when the repaired file decodes cleanly.

4. Video Repairing Lab
  • Containers: MP4, MOV, M4V, 3GP/3G2, AVI, MKV, MTS/M2TS, WMV, FLV, WEBM, MXF.
  • Repairs missing/broken moov, stco/co64 chunk offsets, truncated mdat, empty stsz/stsc sample tables, fragmented headers, AVI idx1 loss and MKV EBML damage.
  • Rebuilds the index from the media stream by NAL-unit scanning (H.264/AVC and H.265/HEVC), transplants SPS/PPS codec configuration, recomputes chunk offsets and re-syncs AAC/ADTS audio.
  • Handles action-camera and drone telemetry metadata interleaved inside mdat, so it is not mistaken for video frames.
  • AUTO REPAIR works on beheaded or containerless raw streams: codec sniffing, full frame + audio scan, clean MP4 rebuild.
  • Every repair ends in a full-decode verification gate.

5. Camera Card Rescue
  • Built around camera-specific erase behaviour: detects low-level formats and TRIM on Sony Alpha, Canon and Nikon cards, then switches to EXIF-based cluster carving.
  • Reads GPS, lens and timestamp metadata to rebuild photos that lost their headers.
  • Per-extension detection with counts and a plain verdict before committing: recoverable, quick format, or TRIM-erased.

6. Disk Clone
  • Sector-by-sector copy in four modes: disk->disk, disk->image, partition->partition, partition->image.
  • Bad-sector handling: configurable read retries, then skip and log, so the copy keeps reading where other tools stop.
  • Multi-pass salvage: pass 1 copies at full speed and zero-fills unreadable blocks; later passes retry only those ranges with progressively smaller reads, down to 512 bytes. Choose 1-6 passes (3 recommended; 1 = single pass). Pause/resume and cancel work during salvage, and a resumed clone continues at the pass where it stopped.
  • Pause & resume: every checkpoint is written twice (primary + backup); the backup is used automatically if the primary is unreadable. Auto-resume continues a matching clone on the next start after checking the target position.
  • Live settings while copying: block size, retries, salvage passes, ignore-bad-sectors, verify, auto-save interval, stall timeout and after-completion action. A saved-clone list lets you pause and switch jobs safely.
  • Source health panel: read errors, retries, slow reads, bad regions and S.M.A.R.T. warnings where the drive reports them.
  • Verify After Copy (Read-Back) is ON by default. Verification compares the target against a block-by-block SHA-256 fingerprint taken during the copy, so a source that is in use or disconnects cannot turn a perfect copy into a failure, while a damaged target is still caught and the first differing block is named.
  • A finished copy writes a plain-text <name>.dltmap sector map of readable and unreadable ranges.
  • A verified image clone writes a <name>.dltverify check file next to the image, holding every block fingerprint, so the image can be re-checked later on another PC without the source drive.

7. Image Explorer (Clone / Full Suite licence)
  • Opens .img, .raw, .dd, .vhd and .vhdx images; lists MBR and GPT partitions, including 4K-sector disks and backup-GPT recovery.
  • Handles images whose disk data starts after a small tool-specific header at any byte offset (for example, a 30-byte header written by some imaging tools).
  • Folder-tree browsing with filters, extraction of selected files or everything, and a Verify Image button that re-checks the image against its .dltverify file.
  • Honest container detection: proprietary compressed images, QCOW2, VMDK, VDI, WIM, ISO, DMG and archives are identified with conversion advice. BitLocker, Linux and macOS whole-disk images are identified but marked not browsable (no ext4/APFS/BitLocker parsers).

8. Wipe (Erase Sectors)
  • Overwrite patterns: zeros, ones, random, and DoD 5220.22-M 3-pass, written through raw device handles.
  • A verification pass confirms every sector after writing.
  • Multi-drive batch wiping with per-drive progress, speed and percentage.
  • Optional automatic Shut Down / Restart / Standby / Hibernate when the job completes.

What is new in 3.2.0
  • Scan area control for Deep Scan.
  • Resilient scan retries/skips and an explicit "Scan incomplete" status.
  • Multi-pass clone salvage with 1-6 passes and resume-at-pass.
  • Plain-text .dltmap sector map output (readable and unreadable ranges).
  • .dltverify check file is now written after a salvaged image clone as well, so Verify Image works for those images.
  • Image Explorer Files list now resizes Name/Size/Status to the pane, so Status is no longer clipped at the default window size.
  • A finished image clone can open directly in Image Explorer, even while the live Cloning monitor is open.

Honest limitations
  • Windows 10/11 64-bit only; Administrator rights are required for raw disk access; activation needs an internet connection.
  • Metadata-aware recovery covers NTFS, FAT32 and exFAT. Deep signature carving is filesystem-independent, but original names/paths are not available once metadata is gone.
  • No software can recover data that the drive or controller has already overwritten or TRIM-erased. The app reports that condition instead of pretending otherwise.
  • A physically failing drive should be imaged first; drives that click, spin down or are not detected need hardware-level work, not software.
  • Recovery success depends on the device, the damage and what was written after deletion. Test on a copy and never write recovered output to the source drive.
  • A resumed clone may not have a .dltverify file, because earlier blocks were copied in a previous session without fingerprints.

Requirements, trial and licensing
  • Windows 10 or 11, 64-bit; Administrator rights; internet for activation.
  • Free: scan and preview on any connected drive, card or image.
  • Licence required for: saving recovered files, clone, photo/video repair output, and wipe.
  • Tiers: Professional (1 PC), Technician (5 PCs), Corporate (10 PCs). Terms: 30 days, 90 days, 1 year or Lifetime. Licences activate online and can be moved between computers.
  • Official download only: https://datalogictools.com
  • Version: 3.2.0
  • Installer SHA-256: fad00f775b0ef07d0d0efc0928d0a0eacaf5e41d6580e025762921a10c3b90cb

The installer contains no third-party bundles. As a new publisher, your browser or Windows SmartScreen may show a reputation warning ("not commonly downloaded"); that is not a malware detection. Verify the SHA-256 above and use "Keep" / "More info -> Run anyway". Only official builds are supported.

If you are working on a failing drive
  • Image the drive before scanning it, then recover from the image.
  • Save recovered files to a different physical drive, never to the source.
  • Stop and reassess if the drive makes unusual noises or keeps dropping offline.

I will answer technical questions in this thread. When reporting a problem, please include the DLT version, Windows build, exact drive/card model, connection type (SATA/USB/NVMe), the mode used, and the exact message shown. If the moderators prefer this thread in another section, please move it.

_________________
DLT - https://datalogictools.com - Recovery · Photo/Video Repair · Disk Imaging · Secure Wipe


Top
 Profile  
 
 Post subject: Re: DLT - Data Logic Tools - Recovery Suite
PostPosted: November 11th, 2026, 15:24 
Offline
User avatar

Joined: October 20th, 2017, 7:29
Posts: 23
Location: Turkey
DLT - Data Logic Tools - Recovery Suite: what changed since 3.2.0

Posting a compact changelog for the thread, since several builds went out after 3.2.2. Hints only - full release notes are on the site. Same vendor disclosure as before: I am the developer, scanning and preview are free, saving/clone/repair/wipe/hex edits need a licence.

Changes since 3.2.0
  • 3.2.1 - Scan Area now really limits Quick/Auto/Deep filesystem results (no files outside the selected byte range). Final clone salvage pass fixed at 4 KB, so one bad sector leaves a 4 KB hole instead of 256 KB.
  • 3.2.2 - Tools area: Hex Viewer/Editor (offset jump, text/hex/?? search, 8/16/24/32-byte rows, licence-gated image byte or 512-byte sector edits, physical drives stay read-only). Visual sector map in clone monitor and Image Explorer with click-to-open at the byte offset. Image Explorer reads VMDK, VDI, DMG, EWF/E01 and ISO 9660, and writes fixed VHD files.
  • 3.3.0 - More filesystems with real metadata recovery: ext2/3/4, HFS+/HFSX, XFS, UFS1/UFS2 (names, folders, fragmentation). ISO 9660 (Joliet/Rock Ridge) and UDF optical browsing, including multi-extent files and surviving deleted entries. 4K-sector GPT. Virtual-disk readers and fixed-VHD export.
  • 3.4.0 - Array assembly: rebuild Linux md RAID 0/1/4/5/10 (every RAID 5 layout, degraded set missing one member), LVM2 linear/striped and Windows dynamic simple/spanned/striped/mirrored into one read-only virtual disk. RAID 6 detected and reported only. Verify and VHD export disabled for assembled volumes.
  • 3.5.0 - NTFS links: symbolic links and junctions listed with their target path and never extracted as empty files. Copy Wizard: guided disk-to-disk, disk-to-image and image-to-disk setup that uses the normal Clone tab and all of its safety checks. Full Hex Editor for any file type with Undo/Redo/Revert, Save/Save As and one byte / hex string / 512 or 4096-byte sector edits.
  • 3.5.1 - Single-instance launch (a second launch focuses the running window instead of opening a copy). Licensing: status stays in sync and a clock rollback can no longer lengthen a trial. Contextual Hex Editor from a recovery result, Image Explorer file or sector-map cell, opening at that file's first data byte; the tab appears only when used. Disk Clone renders as its own tab, with Clone Image Explorer on the tools row. Live clone monitor layout and sector-map rendering fixed.
  • 3.5.2 - One-click Clone presets: Normal (Balanced), Sector by Sector -> Disk, Sector by Sector -> Image, Bad Sector Source -> Disk, Bad Sector Source -> Image. Each preset sets mode and every option in one step and switches back to Custom on any manual change.
  • 3.6.0 - BitLocker read-only unlock: recovery-password unlock of BitLocker volumes in Image Explorer, then browse and extract like any other image. AES-XTS and AES-CBC, current and older Vista-style headers. The image is never modified and the key exists only in memory. Startup-key, TPM-only and diffuser volumes are named but not unlocked, and a wrong password fails closed.

Currently available
  • Version: 3.6.0
  • Installer: DLT-DataLogicTools-3.6.0-Setup.exe
  • SHA-256: 61ED40562EC3B27573BF7F21E297F925E5F39956B759E636D0C310CCE11C1C5F
  • Download: https://datalogictools.com

Same honest limits as before: Windows 10/11 64-bit, Administrator rights for raw disk access, internet for activation. Metadata recovery covers NTFS, FAT32, exFAT, ext2/3/4, HFS+/HFSX, XFS and UFS; ISO 9660 and UDF for optical. APFS is not parsed, RAID 6 and Windows dynamic parity are detected only, and no software recovers data the drive or controller already overwrote or TRIM-erased.

Questions and bug reports welcome in this thread. Please include the DLT version, Windows build, exact drive/card model, connection type (SATA/USB/NVMe), the mode used and the exact message shown.

_________________
DLT - https://datalogictools.com - Recovery · Photo/Video Repair · Disk Imaging · Secure Wipe


Top
 Profile  
 
 Post subject: Re: DLT - Data Logic Tools - Recovery Suite
PostPosted: November 12th, 2026, 6:17 
Offline
User avatar

Joined: December 7th, 2023, 8:14
Posts: 16
Location: Ukraine
rlsturk wrote:
3.4.0 - Array assembly: rebuild Linux md RAID 0/1/4/5/10 (every RAID 5 layout, degraded set missing one member), LVM2 linear/striped and Windows dynamic simple/spanned/striped/mirrored into one read-only virtual disk.


Does DLT automatically detect and reconstruct RAID configurations by reading metadata directly from the member disks or disk images?

A few technical questions:

  • Which RAID metadata formats are currently implemented? For example, Linux MD superblocks (0.90, 1.0, 1.1, 1.2), LVM2, Windows LDM, Intel RST, AMD RAIDXpert2, SNIA DDF, LSI MegaRAID, Adaptec, etc.
  • Can the software automatically determine disk order, stripe/chunk size, parity layout and data offset from the available metadata?
  • Does it automatically identify and assemble degraded RAID 5 arrays when one member is missing?
  • If RAID metadata is missing or damaged, is there a manual RAID reconstruction tool or an automatic RAID parameter search based on filesystem structures?

It would be interesting to know which metadata formats are already supported and whether additional controller-specific formats are planned.

_________________
Michael Miroshnichenko — Data Recovery Software Developer at Hetman Software
RAID • NAS • File Systems • Virtual Disks • https://hetmanrecovery.com/


Top
 Profile  
 
 Post subject: Re: DLT - Data Logic Tools - Recovery Suite
PostPosted: November 12th, 2026, 12:45 
Offline
User avatar

Joined: September 8th, 2009, 18:21
Posts: 17375
Location: Australia
Quote:
detects low-level formats and TRIM on Sony Alpha, Canon and Nikon cards, then switches to EXIF-based cluster carving.

If sectors have been unmapped (TRIM-ed), how can this tool recover anything?

_________________
A backup a day keeps DR away.


Top
 Profile  
 
 Post subject: Re: DLT - Data Logic Tools - Recovery Suite
PostPosted: November 12th, 2026, 20:13 
Offline
User avatar

Joined: May 13th, 2019, 7:50
Posts: 1226
Location: Nederland
Quote:
then switches to EXIF-based cluster carving.


And what does this even mean.

FWIW I tried your demo, and it's the most un-useful demo I ever tried.

_________________
Joep - http://www.disktuna.com - video & photo repair & recovery service


Top
 Profile  
 
 Post subject: Re: DLT - Data Logic Tools - Recovery Suite
PostPosted: November 13th, 2026, 8:20 
Offline
User avatar

Joined: July 10th, 2022, 15:11
Posts: 172
Location: Poland
hetmansoftware wrote:
Which RAID metadata formats are currently implemented? For example, Linux MD superblocks (0.90, 1.0, 1.1, 1.2), LVM2, Windows LDM, Intel RST, AMD RAIDXpert2, SNIA DDF, LSI MegaRAID, Adaptec, etc.

I don’t see an option to work with RAID in the demo version, and image loading only works one file at a time.

fzabkar wrote:
If sectors have been unmapped (TRIM-ed), how can this tool recover anything?

Because he can’t.
Attachment:
DLT.jpg
DLT.jpg [ 191.17 KiB | Viewed 2817 times ]


Arch Stanton wrote:
FWIW I tried your demo, and it's the most un-useful demo I ever tried.

Of course, this is just another piece of AI slop, likely created by someone who has never performed data recovery.

_________________
Data recovery Poland (RAID, HDD, SSD) - https://hex-serwis.pl


Top
 Profile  
 
 Post subject: Re: DLT - Data Logic Tools - Recovery Suite
PostPosted: November 13th, 2026, 15:22 
Offline
User avatar

Joined: October 20th, 2017, 7:29
Posts: 23
Location: Turkey
DLT - Data Logic Tools - Recovery Suite 3.6.2
Thread update: documentation and product claims corrected

Vendor disclosure as before: I am the developer. Scanning and preview are free. Saving recovered files, cloning, photo/video repair output and wiping need a licence.

This is not a feature release. 3.6.2 changes documentation and store copy only. No recovery, clone, wipe or licensing behaviour changed. I am posting it because several lines in the original post, and on the site until yesterday, described things the build does not actually do. Those lines are wrong and I have removed them.

What was wrong

1. Camera Card Rescue
  • The old text said the tool "detects low-level formats and TRIM" and then uses "EXIF-based cluster carving", and that it reads GPS, lens and timestamp data to rebuild photos. None of that is in the code.
  • What it does: reads the card surface in 8 MB chunks, scores each region on zero/0xFF ratio and signature density, and returns one of three verdicts: recoverable (quick format), partial (surviving regions), or unrecoverable (full format / TRIM erase).
  • On a partial card it carves only the surviving regions, with a 64 KB margin so files are not cut at a boundary. On an erased card it produces an HTML lab-handoff report instead of a fake file list.
  • It does not read a card's TRIM command history, and it cannot recover blocks the controller has unmapped. No software can.
  • EXIF is used for camera make/model and capture-date naming, RAW+JPEG pairing and thumbnail rescue. It is not used to find erased data.

2. Deep scan
  • Deep scan carves by file signature. Blocks already erased by TRIM or a full format are gone, and the app reports that instead of listing empty files.

3. Array assembly
  • Supported metadata: Linux md superblocks 0.90, 1.0, 1.1 and 1.2; LVM2 linear and striped; Windows LDM simple, spanned, striped and mirrored.
  • md levels 0, 1, 4, 5 and 10. Every RAID 5 parity layout. RAID 5 with one member missing assembles degraded; two missing members are refused.
  • RAID 6 is detected and reported but not read. RAID 10 works for the near layout; far and offset layouts are refused.
  • Not supported: Intel RST/Matrix, AMD RAIDXpert2, SNIA DDF, LSI MegaRAID and Adaptec controller metadata. Those arrays will not assemble.
  • Members are image files (a clone of each disk), selected several at a time in one dialog. There is no manual parameter entry and no brute-force search; if the metadata is gone the array is not assembled.
  • Assembly needs a Clone or Full Suite licence. It is not part of the free trial.

4. Partition recovery
  • It restores deleted, formatted and orphaned partitions that are still on the disk. It does not recover data that has been overwritten.
  • The existing partition table is backed up before any change.

5. Tool count
  • The suite is eight tools plus the Full Suite Licence. Hex Editor and Clone Image Explorer are documented on the site now; they were missing from the older text.

Current build
  • Version: 3.6.2
  • Installer: DLT-DataLogicTools-3.6.2-Setup.exe
  • SHA-256: 03020E620F82E8A15AE9282EDFDC007E3DF81EE897D38ECD3381C4FF38F33D22
  • Download: https://datalogictools.com

The first post in this thread is from 3.2.0 and still contains the old wording. Where it differs from this reply, this reply and the 3.6.2 documentation are correct.

The installer contains no third-party bundles. SmartScreen may still show a reputation warning for a new publisher. Verify the SHA-256 above and use "Keep" / "More info -> Run anyway".

Technical questions and bug reports are welcome. Please include the DLT version, Windows build, exact drive or card model, connection type (SATA/USB/NVMe), the mode used and the exact message shown.

_________________
DLT - https://datalogictools.com - Recovery · Photo/Video Repair · Disk Imaging · Secure Wipe


Top
 Profile  
 
 Post subject: Re: DLT - Data Logic Tools - Recovery Suite
PostPosted: November 13th, 2026, 15:24 
Offline
User avatar

Joined: October 20th, 2017, 7:29
Posts: 23
Location: Turkey
hetmansoftware wrote:
rlsturk wrote:
3.4.0 - Array assembly: rebuild Linux md RAID 0/1/4/5/10 (every RAID 5 layout, degraded set missing one member), LVM2 linear/striped and Windows dynamic simple/spanned/striped/mirrored into one read-only virtual disk.


Does DLT automatically detect and reconstruct RAID configurations by reading metadata directly from the member disks or disk images?

A few technical questions:

  • Which RAID metadata formats are currently implemented? For example, Linux MD superblocks (0.90, 1.0, 1.1, 1.2), LVM2, Windows LDM, Intel RST, AMD RAIDXpert2, SNIA DDF, LSI MegaRAID, Adaptec, etc.
  • Can the software automatically determine disk order, stripe/chunk size, parity layout and data offset from the available metadata?
  • Does it automatically identify and assemble degraded RAID 5 arrays when one member is missing?
  • If RAID metadata is missing or damaged, is there a manual RAID reconstruction tool or an automatic RAID parameter search based on filesystem structures?

It would be interesting to know which metadata formats are already supported and whether additional controller-specific formats are planned.


The array tools read the metadata from the members themselves. You add one image per member (a clone of each disk, not a live disk), the scanner reads the superblocks in those images, and it builds one read-only virtual volume that opens in Image Explorer.

What is implemented now

Linux md superblocks 0.90, 1.0, 1.1 and 1.2. Level, chunk size, layout, member role and data offset all come from the superblock. 1.1 keeps the superblock at the start and 1.2 at 4 KB, both carry data_offset. 0.90 and 1.0 keep it at the end and the data starts at 0.
md levels 0, 1, 4, 5 and 10. Every RAID 5 parity layout is handled.
LVM2 linear and striped.
Windows LDM simple, spanned, striped and mirrored.
Not implemented: Intel RST/Matrix, AMD RAIDXpert2, SNIA DDF, LSI MegaRAID and Adaptec. Those arrays will not assemble. I would rather tell you that than produce a volume that reads as garbage.

Disk order, chunk size, parity layout and data offset are all detected automatically. RAID 5 with one member missing assembles degraded; two missing members are refused. RAID 6 is detected and reported but not read. RAID 10 works for the near layout, far and offset layouts are refused.

There is no manual parameter tool and no brute-force search. If the metadata is gone, the array will not assemble, and the members have to be carved as raw disks. Assembly needs a Clone or Full Suite licence.

_________________
DLT - https://datalogictools.com - Recovery · Photo/Video Repair · Disk Imaging · Secure Wipe


Top
 Profile  
 
 Post subject: Re: DLT - Data Logic Tools - Recovery Suite
PostPosted: November 13th, 2026, 15:25 
Offline
User avatar

Joined: October 20th, 2017, 7:29
Posts: 23
Location: Turkey
fzabkar wrote:
Quote:
detects low-level formats and TRIM on Sony Alpha, Canon and Nikon cards, then switches to EXIF-based cluster carving.

If sectors have been unmapped (TRIM-ed), how can this tool recover anything?


You are right, and that line was wrong. Once the controller has unmapped the blocks after TRIM there is nothing left to read, and no carving method changes that.

What the tool actually does with a card is a surface pass first. It reads the card in chunks and scores each region on zero/0xFF ratio and signature density, then returns one of three verdicts: recoverable (quick format), partial (some regions still hold data), or unrecoverable (full format or TRIM erase). On a partial card it carves only the surviving regions, with a 64 KB margin so files are not cut at the boundary. On an erased card it produces a report instead of a file list.

The "detects TRIM and switches to EXIF-based cluster carving" wording did not match the code. I removed it from the site and the in-app README. 3.6.2 is live with the corrected text. EXIF is used for camera naming, RAW+JPEG pairing and thumbnails, not to find erased data.

_________________
DLT - https://datalogictools.com - Recovery · Photo/Video Repair · Disk Imaging · Secure Wipe


Top
 Profile  
 
 Post subject: Re: DLT - Data Logic Tools - Recovery Suite
PostPosted: November 13th, 2026, 15:27 
Offline
User avatar

Joined: October 20th, 2017, 7:29
Posts: 23
Location: Turkey
Arch Stanton wrote:
Quote:
then switches to EXIF-based cluster carving.


And what does this even mean.

FWIW I tried your demo, and it's the most un-useful demo I ever tried.


That is a fair hit. There is no "EXIF-based cluster carving" in the code. EXIF is read after carving to name files by camera make/model and capture date, pair RAW+JPEG shots and pull embedded previews. It is not used to locate data.

That sentence was written for the store page and did not match what the tool does. It is gone from the website and the in-app README as of 3.6.2.

On the demo: the trial is the full program, with scan and preview free and saving/clone/repair/wipe licensed. If you tell me what you tried (drive or image, mode, what the window showed), I will look at that case. "Un-useful" does not give me anything to fix, and I would rather have the specific failure.

_________________
DLT - https://datalogictools.com - Recovery · Photo/Video Repair · Disk Imaging · Secure Wipe


Top
 Profile  
 
 Post subject: Re: DLT - Data Logic Tools - Recovery Suite
PostPosted: November 13th, 2026, 15:28 
Offline
User avatar

Joined: October 20th, 2017, 7:29
Posts: 23
Location: Turkey
Lukas wrote:
hetmansoftware wrote:
Which RAID metadata formats are currently implemented? For example, Linux MD superblocks (0.90, 1.0, 1.1, 1.2), LVM2, Windows LDM, Intel RST, AMD RAIDXpert2, SNIA DDF, LSI MegaRAID, Adaptec, etc.

I don’t see an option to work with RAID in the demo version, and image loading only works one file at a time.

fzabkar wrote:
If sectors have been unmapped (TRIM-ed), how can this tool recover anything?

Because he can’t.
Attachment:
DLT.jpg


Arch Stanton wrote:
FWIW I tried your demo, and it's the most un-useful demo I ever tried.

Of course, this is just another piece of AI slop, likely created by someone who has never performed data recovery.


Both observations are correct.

RAID/LVM assembly lives inside Clone Image Explorer, and Image Explorer is a licensed tool (Clone or Full Suite). In the 7-day trial scanning and preview work, but that window does not open, so there is no Assemble button to find. It is the same gate as saving and cloning, not something hidden for the demo.

Image Explorer opens one image per window; that is the intended flow. The Assemble dialog is the one place that takes multiple files, because the members are one array, not separate images.

On TRIM, I agree with you and fzabkar. Unmapped blocks cannot be recovered. The old site line saying otherwise was removed in 3.6.2, which is live now.

I cannot prove authorship in a forum post, so judge the tools on output. Scan a card or drive in the trial, compare the preview against what you know is on it, and if the preview is wrong, post the details and I will fix that first.

_________________
DLT - https://datalogictools.com - Recovery · Photo/Video Repair · Disk Imaging · Secure Wipe


Top
 Profile  
 
 Post subject: Re: DLT - Data Logic Tools - Recovery Suite
PostPosted: Yesterday, 8:01 
Offline
User avatar

Joined: October 20th, 2017, 7:29
Posts: 23
Location: Turkey
DLT - Data Logic Tools - Recovery Suite 3.18.0
Highlights of everything since the 3.6.2 reply

Vendor disclosure as before: I am the developer. Scanning and preview are free. Saving recovered files, cloning, photo/video repair output, RAID output, Hex Editor saving and wiping need a licence.

This is a short update, not the full changelog. Since 3.6.2 the big additions are the RAID Recovery tab, RAID 6, Intel IMSM / JMicron / SNIA DDF metadata, physical disks as RAID members, Manual Build and Find Parameters, three read-only file systems (APFS, Btrfs, ReFS) with FileVault unlock, and a new results browser and light theme. Full text is on the site changelog.

Four things my 3.6.2 reply said were not supported are supported now. Where the two posts disagree, this post is correct.

What changed, release by release

Results browsing
  • 3.6.3 - Results tree rebuilt from file-system metadata: Existing Files and Lost Files, a file count per folder, folder tick boxes, and a file list with Type, Size, Date, Fragments, Status and Original Path. Search matches names, folders and extensions with wildcards and jumps to the file; Advanced Filter adds type, size, date and category with a live count; a PATH / TYPE switch groups by folder or by real file type. Large result sets load in chunks.
  • 3.6.4 - Cleaner results layout: location bar, folder count in its own column, preview card with Name, Path, Date, Size, Type and Status.
  • 3.6.5 - Extend View: a full-window browser during or after a scan, with a compact scan strip along the top and one click back.
  • 3.6.6 and 3.6.7 - Light Mode / Dark Mode switch in the top-right bar. The app still starts in Dark Mode; the switch changes the current session.
  • 3.18.0 - Light Mode finish: one deep-navy title ink on every page and tool header, one slate body ink, warning and error text keep their own colour, and inputs, tabs and buttons share one tinted style. Dark Mode is unchanged.

RAID Recovery
  • 3.7.0 - RAID Recovery is its own main tab. Add one member per array and scan: Linux md, LVM2 and Windows dynamic disks are listed with status and missing members. That release is also where RAID 6 stopped being "detected only": md RAID 6 is read, and an array missing one or two members is rebuilt from P and Q. Manual Build places members in slot order with level, chunk, parity layout and data offset; Find Parameters ranks combinations that reveal a real file-system signature; Save Project keeps the setup in a .dltraid file; Member Diagnostics explains counter and role problems.
  • 3.8.0 - Zero-fill unreadable member blocks, and Verify Array, which samples stripes and compares them with stored parity or mirrors before a long rebuild.
  • 3.9.0 - Write to Disk: the rebuilt volume goes straight onto a replacement disk. The system disk, undersized disks and any disk holding a member image are refused, an optional read-back pass verifies, and the job needs a typed WRITE.
  • 3.10.0 - Vendor metadata: Intel RST / Matrix (IMSM) RAID 0, 1, 5 and 10, and JMicron ATARAID RAID 0, 1, 10 and JBOD, are assembled from the metadata. When IMSM images share one size and the data cannot separate them, the volume is built and labelled "member order assumed".
  • 3.11.0 - Members can be whole physical disks, read directly and read-only; the boot disk is marked and refused. Browse & Recover opens the assembled volume inside the RAID tab with filters and Extract Selected / Extract All.
  • 3.12.0 - RAID Hex View opens a member locked read-only (the read-only switch is disabled, so a member can never be written there), Create Images copies physical members to verified images, and every RAID dialog opens centred. Layout fixes: md RAID 10 far/offset refused, md linear with a missing member refused, and a non-standard md parity layout value 4 or 5 refused instead of masked.
  • 3.13.0 - SNIA Common RAID DDF: both header copies are CRC-checked and a damaged primary falls back to the secondary; DDF RAID 0, 1, 4, 5 and concatenated volumes are assembled from the metadata anchor. RAID 6, RAID 10 / BVD, RAID 1E, RAID 5E / 5EE and JBOD were named but not assembled at that point (RAID 6 follows in 3.18.0).
  • 3.18.0 - DDF RAID 6: all three rotating parity layouts, each with its own Q coefficients over GF(2^8), one or two missing members rebuilt from P and Q, and Verify Array checks P and Q. JMicron RAID 5 is assembled too: the parity order is read from the volume (boot sector fixes the rotation, an NTFS backup boot sector or ext4 group-1 superblock separates the two data orders); when the volume carries neither, the set opens with the lower layout and is labelled "not confirmed by the file system", with a note pointing at Manual Build for the other order. One missing member is rebuilt; two is refused.

File systems
  • 3.12.0 - Drive Recovery File System step: Auto-detect on by default, or choose NTFS, FAT12/16/32, exFAT, ext2/3/4, HFS+/HFSX, XFS, UFS1/UFS2, ISO 9660 and UDF (APFS, Btrfs and ReFS were added to this list with their own releases).
  • 3.14.0 - APFS, read-only: containers read through checkpoints and B-trees, one row per volume with its real name, zlib and raw-compressed files unpacked on save, LZVN / LZFSE / LZBITMAP files listed with the compression named, Fusion containers explained but not opened.
  • 3.15.0 - Btrfs, read-only: every subvolume read and placed under its own name (Synology folders included), snapshot roots skipped, zlib and zstd unpacked on save, lzo named, sparse holes saved as zeros, multi-disk volumes refused with a message to assemble the array first.
  • 3.16.0 - FileVault unlock for APFS in Clone Image Explorer: password or recovery key, checked against the volume's own file-system checksum before anything is listed, key in memory only, image never modified. Needs a Clone or Full Suite licence.
  • 3.17.0 - ReFS, read-only: both checkpoints with automatic fallback to the older one, files stored inside the directory record and files in clusters, sparse files saved with their gaps, format version 3 read; a version 1 volume is named and refused, and a Storage Spaces volume that spans containers is refused with "assemble the pool first". Recognised by RAID Find Parameters too.

Corrections to my 3.6.2 reply
  • "RAID 6 is detected and reported but not read" - no longer true. md RAID 6 (3.7.0) and DDF RAID 6 (3.18.0) are read, including two missing members.
  • "Not supported: Intel RST/Matrix, SNIA DDF, JMicron" - IMSM, JMicron and DDF metadata are all parsed now (3.10.0, 3.13.0, 3.18.0).
  • "Members are image files, selected in one dialog" - the RAID tab also takes whole physical disks, read-only (3.11.0).
  • "There is no manual parameter entry and no brute-force search" - Manual Build and Find Parameters were added in 3.7.0, and both still work on DDF members whose layout is not assembled.

What is still not supported (so nobody buys on a wrong assumption)
  • AMD RAIDXpert2, Marvell, LSI MegaRAID and Adaptec metadata is still not parsed. Those arrays will not assemble.
  • DDF RAID 10 / BVD, RAID 1E, RAID 5E / 5EE and JBOD are recognised and named but not assembled. Manual Build and Find Parameters still work on their members.
  • md RAID 10 is read for the near layout only; far and offset are refused. A non-standard md parity layout value (4 or 5) is refused instead of guessed. md linear with a missing member is refused.
  • RAID 6 with three or more missing members is refused, and JMicron RAID 5 with two missing members is refused. One parity disk cannot rebuild two disks.
  • APFS, Btrfs and ReFS browsing shows live files. All three keep no deleted-file name table, so deleted data is found with Deep Scan signature carving. ReFS version 1 and multi-container ReFS volumes are refused; Btrfs multi-device volumes are refused; APFS Fusion containers are not opened; FileVault needs the password or recovery key and a Clone/Full Suite licence.
  • ZFS is not supported at all in 3.18.0.
  • No software recovers blocks a drive or controller has already overwritten or TRIM-erased. Camera Card Rescue measures the card surface first and reports an erased card instead of listing empty files.

Licensing, unchanged
  • Free: scan and preview on any drive, card or image, and scan the metadata of an array's members. The trial is 7 days.
  • A licence is needed to save recovered files, clone, write RAID output to disk, save photo/video repair output, save Hex Editor edits and wipe.
  • RAID rules: scanning member metadata and adding physical disks read-only is free. Cloning members to images, browsing or extracting a rebuilt volume, and saving it (image or Write to Disk) need a Clone or Full Suite licence.

What was actually tested
  • The file-system engines and RAID layouts are exercised by test images built byte by byte in the test suite. For DDF RAID 6, P and Q are computed independently of the product code, so the checks do not just agree with themselves: every layout, one missing member, two missing members, a refused layout qualifier, and Verify Array on clean arrays.
  • JMicron RAID 5: all four parity layouts, one missing member, a volume with no backup header (the "not confirmed" path), and a two-missing case refused.
  • I have not yet had a real DDF controller array, a real JMicron RAID 5 set, a real Storage Spaces ReFS volume or a real FileVault Mac drive from a customer on this build. If one fails, the detail line now names the layout and whether it was confirmed, which is exactly what I need to check it.

Current build
  • Version: 3.18.0
  • Installer: DLT-DataLogicTools-3.18.0-Setup.exe
  • SHA-256: CA3E1D386416849F2A5087D76FAB52E46C2972945D71383CAA78358F788ADAC7
  • Download: https://datalogictools.com

The installer contains no third-party bundles. SmartScreen may still show a reputation warning for a new publisher. Verify the SHA-256 above and use "Keep" / "More info -> Run anyway".

Technical questions and bug reports are welcome. Please include the DLT version, Windows build, the array type (md, LVM, Intel IMSM, JMicron, SNIA DDF, LDM), the controller or motherboard model, the member count, the chunk size if known, and the exact message shown.

_________________
DLT - https://datalogictools.com - Recovery · Photo/Video Repair · Disk Imaging · Secure Wipe


Top
 Profile  
 
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 12 posts ] 

All times are UTC - 5 hours [ DST ]


Who is online

Users browsing this forum: No registered users and 29 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group