Where is the command fsck.ntfs

[Tiago Araujo da Costa]

I can't find it in any Core 13.0 x86_64 TCZ package.

[gadget42]

perhaps future readers will enjoy:
https://superuser.com/questions/233700/fsck-an-ntfs-drive-in-linux

sharing is caring

[curaga]

I don't believe any useful fsck.ntfs exists. The one from ntfsprogs is very limited. If you want to use ntfs, use windows to fix it.

[gadget42]

a snippet from the earlier link(https://superuser.com/questions/233700/fsck-an-ntfs-drive-in-linux):

Take care using Windows 'chkdsk /f' on an NTFS used by Linux. I just followed this advice to fix errors on my external 2TB backup drive. It deleted the names of 268 files and directories (incl. all my incr. backups) due to invalid characters (from NTFS viewpoint - most often ':' used in timestamps). I reverted it all using the log file, but it took half a day of coding. Some but not all Linux system-calls block writing such invalid names on an NTFS. I use rsync for backups, which silently copies such invalid filenames - normally useful, until you need to fix other problems on the disk... - Bob Briscoe - Jun 15, 2020 at 11:30

have had "invalid characters" issues in the past...
seem to recall vfat formatted external media not playing well with "timestamp filenames containing colons"...

sharing is caring

[Rich]

Hi gadget42
The issue of invalid characters came up while I was developing grabber.tcz (selective screenshots):
http://forum.tinycorelinux.net/index.php/topic,18412.msg113562.html#msg113562

The original format used for the filenames was:

Code: [Select]

grabber-YYYYmonthDD-HH:MM:SS.pngA user reported that Firefox was choking on the filenames due to the colons in the time field.