Hmm.  I could have sworn that the NTFS utilities in Linux had a chkdsk
function.  Yeah:

ntfsfix (8)          - fix common errors and force Windows to check NTFS


(found using 'man -k ntfs')


Man page for ntfsfix says, in part:

DESCRIPTION
        ntfsfix  is  a utility that fixes some common NTFS problems. 
ntfsfix is NOT a Linux version of chkdsk.  It only re‐
        pairs some fundamental NTFS inconsistencies, resets the NTFS
journal file and schedules an  NTFS  consistency  check
        for the first boot into Windows.

        You  may  run  ntfsfix  on  an NTFS volume if you think it was
damaged by Windows or some other way and it cannot be
        mounted.


So, ntfsfix might help.  There is also an ntfsclone that says:

ntfsclone (8)        - Efficiently clone, image, restore or rescue an NTFS


Can Linux mount your ntfs stick?  (You might have to do it readonly. and
you've probably said something about this, but it has been a while and
I've not been as focused on the issue as I probably should be...)


On 6/11/24 10:30, Michael via PLUG-discuss wrote:
> Thanks for trying!
>
> On Tue, Jun 11, 2024 at 12:53 PM Arun Khan <knura9@gmail.com> wrote:
>
>>
>> On Tue, Jun 11, 2024 at 8:59 AM Michael via PLUG-discuss <
>> plug-discuss@lists.phxlinux.org> wrote:
>>
>>> well, the drive may be ntfs but the files written were jpg written from a
>>> linux machine.... hmmmm. I guess it should be able to read from windows
>>> seeing as it us a JPG and not some exotic open source file:!) I guess it
>>> just got corrupted. The question still remains, is there a way to recover
>>> the files on the drive? I hope so, There were pictures on that drive. My
>>> entire south carolina trip!
>>>
>>> The directions that were given were to run:
>>>
>>>       chkdsk /f
>>>
>>> on the drive. Have two problems with those directions though: 1. that
>>> requires admin privileges and I don't know how to do that. 2. when I stick
>>> the drive in it gives me the insert drive tone and then the disconnect
>>> drive tone and never assigns a drive letter to it. Then it repeats that
>>> until I pull the drive. And if I've kept the drive in there long enough it
>>> keeps doing that after I've pulled the drive. 3.
>>>
>> Based on the responses so far, you have the following options  (IMO):
>>
>> 1. Keep plugging for a solution.  There is no way around it; you will need
>> a Windows desktop to repair the NTFS file system.  I suggest that you lean
>> on your family/friends who have Windows admin privileges on their systems.
>> 2. Seek professional help to recover your files (e.g. Data Doctors have
>> retail stores in many shopping malls)
>>
>> Regardless of what you do, to avoid future mishaps, invest in a couple of
>> high-capacity storage and backup your important files to *two* different
>> drives (rsync -aP <original files> <target dir> does the job for me).
>>
>> HTH
>> --
>> Arun Khan
>>
>
>
> ---------------------------------------------------
> PLUG-discuss mailing list: PLUG-discuss@lists.phxlinux.org
> To subscribe, unsubscribe, or to change your mail settings:
> https://lists.phxlinux.org/mailman/listinfo/plug-discuss
---------------------------------------------------
PLUG-discuss mailing list: PLUG-discuss@lists.phxlinux.org
To subscribe, unsubscribe, or to change your mail settings:
https://lists.phxlinux.org/mailman/listinfo/plug-discuss