I know, I know. I really shouldn’t use NTFS with Linux if I plan to write to it, especially not my only backup drive, which is my external media drive for libreELEC as well.

So I was moving/copying/renaming stuff through SMB on my libreELEC machine. And then suddenly I noticed 50 episodes of old-school Sonic animated series just… disappeared. Strange, but I continued renaming files, and those too poof nonexistent anymore.

Okay, maybe a Dolphin bug - I thought, since I was using Dolphin for SMB. But same from Android (I’m using Solid Explorer)

Then, Ghost In The Shell Stand Alone Complex too disappeared. Then some episode of Serial Experiments Lain.

Star Trek Discovery? Fucking gone, tho I didn’t mind that one. All of the files are 0B. Then Regular Show.

Now, this was the point where I needed to step in. Linux just didn’t see the files.

Oh well, I have a Windows 10 PC I use for work so it was a time for bringing the drive “home” and give it some chkdsk, in the meantime I was really hoping it wouldn’t just destroy my 4TB backup drive. Wasn’t sure it would work, but that was pretty much my only hope and idea. Trying to access those folders and files from Windows gave me error messages before the check.

The check and fix dialog of chkdsk was also kinda fucked, the progressbar jumped around, didn’t make any sense BUT it restored my files. Hooray!

Except SAC, it was still unreadable from Windows, but! Linux does see all the episodes so I guess it’s a win… of some sort. It sill bothers me there is some - from Windows’s point of view - invalid files and folders on my BACKUP disk, but this will be another story.

It turned out, libreELEC is using ntfs-3 (and not 3g), which is famous for this kind of errors - files disappearing and the filesystem becoming funky.

So, I ordered a drive just for my media and media PC, tho no idea how to format it (to be readable from anywhere else - maybe exFAT?)

But this scared me like hell 😅

Just wanted to share this with you guys, there’s no moral of the story, except do not use ntfs heavily under Linux, or at least do not write it a lot, which is a known thing since forever, I was just a lazy ass, don’t be like me, please, unless you have a Windows machine around and some luck. But relying on these two, well…

Cheers!

Update: I formatted my new media drive to ext4. In the end, it’ll be a fixed disk under my TV in a linux box, this seemed to be the best choice. I don’t think I’ll pick it out and use it elsewhere that much or at all.

  • Lupec@lemm.ee
    71·
    4 months ago

    Ah, now that’s a scare! Glad you mostly managed to recover at any rate.

    As for the fs to use, exfat is probably a safer bet but btrfs is also an option. I’ve used winbtrfs in the past and it works surprisingly well.

    • ProgrammingSocks
      6·
      4 months ago

      DO NOT USE WIN BTRFS. Recently I used a current version and it fucked up my btrfs filesystem in a way that was almost impossible to diagnose and fix.

      • Lupec@lemm.ee
        2·
        4 months ago

        Right, thanks for the input. I used to use it for unimportant stuff like game storage so it’s entirely possible errors just went unnoticed 😅

      • Lupec@lemm.ee
        2·
        4 months ago

        Said drive is a new one for media and regular everyday usage, not the existing backup drive according to the OP. Btrfs is more than stable enough barring specific RAID configurations, at any rate.

    • kuneho@lemmy.worldOP
      1·
      4 months ago

      Thanks for the tip. Though I wouldn’t mind if it would work on almost anything - even like Android or some older systems. Not a real need, just would be nice if I could plug mymedia drive into anything and watxh stuff from it (maybe even from older, not smart TVs if it’s possible)

      • Lupec@lemm.ee
        3·
        4 months ago

        Yeah I guess exfat is the way to go then, it’s how I handle my external SSD rn as well

        Edit: Also, I’m not sure how well btrfs handles external drives. Didn’t realize that when I suggested it.