Just having a play around, this turned out to be not as clear cut as expected.

so I created a file and entered some text, used xxd to get the hex values, and then opened the device /dev/sdb1 in wxhexeditor and tried to find my file, but it’s not finding it. Inode is 19, so it should be right at the start of the first block group, but after several minutes, no joy. (drive is ext4.)

I thought this was going to be an easy task, just multiply the inode by the block size, open the device with wxhexeditor, and scroll to the line corresponding to the calculated byte, copy out the hex values and convert to ascii and voila, there’s the ‘hello world’… except no.

What am I missing here? Drive isn’t encrypted, nothing silly like that.

Ok, I managed to do it with dd:

sudo dd if=/dev/sdb1 bs=8M skip=$((4660742*4096)) iflag=skip_bytes | head -c 4096

hello

but why can I not find it using wxhexeditor??

EDIT:

Duh, I didn’t click that offset needed to be multiplied by the block size.

If I go to offset 4660742*4096=19090399232 in wxhexeditor, indeed I see the file contents:

Final conclusion:

After some more testing, I have concluded: you cannot easily calculate the offset using the inode. Finding files across the disk requires using the inode tables to get the offset and actual file location. So an inode does not correlate with a physical/logical sequential disk location.

I created a new file, it received inode 21, but the offset was smaller than inode 19.

Was that a good use of 3 hours of my life? Well… I still have no idea what’s up with the Kardashians, so… I guess?

  • @[email protected]
    link
    fedilink
    117 months ago

    Luthis, you’re doing God’s work here. You are learning by experimentation and then, importantly, documenting and sharing what you’ve learned. There is absolutely zero wrong and only good to be had in either of those and in combining them, you’re doing service to our entire community.

  • SaltyIceteaMaker
    link
    fedilink
    57 months ago

    Of course that was worth 3 hours. Every tinkering/experimenting is worth it. In the worst case you gain experience

    • ∟⊔⊤∦∣≶OP
      link
      37 months ago

      Yeah now I stand a better chance of recovering files if something catastrophic happens

    • ∟⊔⊤∦∣≶OP
      link
      37 months ago

      True, now you have the power to find your files manually!

  • Dario
    link
    fedilink
    37 months ago

    Not much related, but I want to chime in to express my gratitude for what I consider the most underrated piece of software in the FOSS ecosystem. Better known hex editors pale in comparison to wxHexEditor in terms of features and user interface. I suggest you to tweak the colors for better viewing (I can share my configuration file) and to upgrade to the latest unstable revision because many important fixes landed since the last stable version.

    • ∟⊔⊤∦∣≶OP
      link
      17 months ago

      Yeah definitely share your config! I’ve only just scratched the surface with wxHexEditor

      • Dario
        link
        fedilink
        1
        edit-2
        7 months ago
        Language=English
        UpdateCheck=1
        LastUpdateCheckTime=1.698e+09
        ColourHexForeground=#DEDDDA
        ColourHexBackground=#000000
        ColourHexBackgroundZebra=#3D3846
        ColourHexSelectionForeground=#000000
        ColourHexSelectionBackground=#613583
        UseCustomHexFormat=0
        CustomHexFormat=xx 
        UseBytesPerLineLimit=1
        BytesPerLineLimit=16
        CharacterEncodingFamily=DOS
        CharacterEncoding=OEM - IBM PC/DOS CP437 - MS-DOS Latin US
        FontSize=10
        AutoShowTagPanel=1
        ScreenX=26
        ScreenY=23
        ScreenW=618
        ScreenH=716
        ScreenFullScreen=0
        FakeBlockLines=0
        FakeBlockSize=8k
        SingleInstance=0
        ZebraStriping=1
        SelectedChecksumFunctions=32648
        CompareOptions=0
        CompareOptionStopAfter=0
        CompareOptionMergeSection=0
        
  • ∟⊔⊤∦∣≶OP
    link
    3
    edit-2
    7 months ago

    Tried a different way:

     filefrag -v testfile 
    Filesystem type is: ef53
    File size of testfile is 6 (1 block of 4096 bytes)
     ext:     logical_offset:        physical_offset: length:   expected: flags:
       0:        0..       0:    4660742..   4660742:      1:             last,eof
    

    Went to offset 4660742 in wxhexeditor, but still when I copy out the hex and convert to ascii, it’s nonsense

    • ∟⊔⊤∦∣≶OP
      link
      17 months ago

      I just made a file with a single word in it, and now I’m trying to read that file directly from the device by opening /dev/sdb1, so I can test my understanding of inodes and blocks etc.