On Mon, 2022-04-25 at 10:41 -0500, Roger Heflin wrote:
On Mon, Apr 25, 2022 at 10:11 AM Lily White
<lilywhite2005(a)outlook.com>
wrote:
> I got a spare drive and it does work (at least for now, this drive
> worked for a while before everything broke). So I sent my old drive
> back
> to Sandisk and I'll see if it was with that specific model.
>
> I'll also wait for some time and see if wear and tear may cause
> problems.
>
> What's interesting is that the broken drive works on both Fedora
> and
> macOS, but not Windows. That's why I didn't speculate the drive
> itself
> was broken before.
>
>
I am going to bet that the NTFS code is very similar on Fedora and
MacOS.
So likely it is a code bug or a usage bug (see comments below).
you did make sure to umount it on Linux/BSD before removing it right?
And if you hibernate the machine(any os) and remove the usb device
while
hibernated the filesystem may not be consistent, it has to be
explicitly
unmounted on both windows and fedora before removal so that all data
is
fully written.
In the past it was suggested to not use NTFS as a transfer drive and
to use
something simpler like FAT32 as that fs's format is better documented
and
simpler than NTFS. That may or may not still be the case.
Most NTFS installation on Linux use a user-space implementation via
Fuse, which is known to have some limitations (IIRC it's fine for
reading but might be problematic when writing). A new kernel-based
implementation is apparently on the way and is said to have a higher
degree of compatibility.
poc