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.
IIRC, exFAT is still a fuse module, but FAT32 is kernel native, if thatâs a thing that matters (in case youâre ever on a Linux where you canât install fuse+exFAT).
Thereâs been an exFAT driver in the kernel for a couple of years now (merged after Microsoftâs patent pact added ExFAT), it works fine. Same driver gets used on Android for SD card support.
