Home | Blog | Software | Reviews and Features | Forum | Help | Donate | About us
topbanner_forum
  *

avatar image

Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
  • March 30, 2017, 05:51:44 AM
  • Proudly celebrating 10 years online.
  • Donate now to become a lifetime supporting member of the site and get a non-expiring license key for all of our programs.
  • donate

Author Topic: SeqBox - A file container that can be restored after total loss of FS structures  (Read 192 times)

Mark0

  • Charter Honorary Member
  • Joined in 2005
  • ***
  • Posts: 623
    • View Profile
    • Mark's home
    • Donate to Member
https://github.com/MarcoPon/SeqBox

Quote
A SeqBox container have a blocksize sub/equal to that of a sector, so can survive any level of fragmentation. Each block have a minimal header that include a unique file identifier, block sequence number, checksum, version. Additional, non critical info/metadata are contained in block 0 (like name, file size, crypto-hash, other attributes, etc.).

If disaster strikes, recovery can be performed simply scanning a volume/image, reading sector sized slices and checking blocks signatures and then CRCs to detect valid SBX blocks. Then the blocks can be grouped by UIDs, sorted by sequence number and reassembled to form the original SeqBox containers.


Tools are in Python 3.x, so they should work just about anywhere. I tried on a server with Linux, Win 10 PC, Raspberry Pi, Android.

Mark0

  • Charter Honorary Member
  • Joined in 2005
  • ***
  • Posts: 623
    • View Profile
    • Mark's home
    • Donate to Member
I have updated the readme adding a sort of guide tour / demo to illustrate how the tools can be used:

https://github.com/M...lob/master/readme.md

Quote


Pretty nightmarish! Now on to SBXScan to search for pieces of SBX files around, and SBXReco to get a report of the collected data:



How is that for a fragmented floppy image?  ;D