Thanks for trying! On Tue, Jun 11, 2024 at 12:53 PM Arun Khan 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 does the job for me). > > HTH > -- > Arun Khan > -- :-)~MIKE~(-: