Date Time issues

[Bostjan]

I've took 32GB USB 3.0 key, formatted it in NTFS in Windows, put it on about 25GB of content and plug it into Q5Pro without network connectivity.
Then I did following steps:
1. played all the content at least once with Himedia player and Kodi
2. removed the key and checked it on Windows - all the content was there, even access time attribute of files didn't change to 1.1.2015 but it stayed as it was
3. then I deleted a lot of content, maybe 24GB and copy it again to key
4. repeated again the 1st step
5. checked files again on Windows and there was nothing wrong with them. What was strange, that last access file attribute was not set on Android - could be normal if FS is NTFS

In short, I was definitely not able to reproduce file corruption just because date was wrong as 1.1.2015 (btw, technically speaking it is perfectly valid date).
Can you please give us a little bit more info, specially:
- how quick does corruption occurs, after single insertion, after weeks of heavy usage with writing,...
- can you give us shortest possible step-by-step process with details which leads to corruption - possibly in 100% cases
- have you used drive only on Q10 Pro or have you moved it around and connect it to different devices, computers, etc?
- on which of those different devices have you done any writing to the drives

As I already said, I would be very amazed if having wrong (but technically correct) date of 1.1.2015 would lead to corruption of files.

[velo]

[Bostjan]

I'll try some other test based on your reply. To do that, please be so nice and give me some other details and explanation:
1. You say that modify and/or also sometimes create date changes when files are copied to or from Q10. How exactly do you copy/move files? Using Total commander on Q10Pro which is accessing SAMBA shares on your laptop? Some other way?
2. With which application do you play your files on Q10? As I already said I couldn't even get even last access property of file to be changed to 1.1.2015 with Kodi and Himedia player. So which player/app do you use?
3. What other apps/utilities are you running or have you installed on Q10 Pro (side of already mentioned Total commander). Issue might also be there...

[velo]

[Bostjan]

I did few more test these days and I can say that something weird is indeed happening.
Test involved two 32GB USB keys formatted as FAT32 - one was almost full, while the other was empty and I did copying all the content from one to the other. Then I played the content from both, followed by deleting almost everything (25GB) from destination drive and try to copy exactly the same content back to if from source drive. This is where I got the message that there was no room on destination drive - that is obviously where things started to go wrong as there should be room as I just deleted almost whole drive.
Then I plugged the drive to Windows PC which shows that drive was almost full, but deleted files were not there?!? Running chkdsk revealed error that BITMAP file attribute is missing/corrupted. After running it with /f, drive was fixed and missing place was reclaimed.

That is what I founded so far which confirms that there is something indeed wrong with Q5/Q10 Pro and file system operations. So far it looks like the problem is only there when you have two locally connected drives. However, at least few last steps in my case were done when connected to internet and having correct date and time so date and time is probably not to blame, problems is elsewhere.

I'll do some more test trying to find 100% reproducible and short as possible procedure to demonstrate the problem. Help from anyone else would be appreciated.

[mondomedia]

[velo]

[Bostjan]

The problem is very elusive as I can't get a procedure to be 100% reproducible. I did however found some parts that may help to get us to the finals.
After deleting most of files and trying to copy them back I got error there is no space to do that - this is the root/start of the FS corruptions:
- if I turn the unit OFF and back ON without pulling the USB out (or safely remove it first via software), the corruptions became permanent.
- if I safely remove the USB via software first and then turn unit OFF and ON again, corruptions seems to disappear

I'm not sure if my findings above are always true, but at first they do - I'll try more in upcoming days.

BTW, in my case corruption can be fixed by chkdsk in Windows 10, this is how errors always looks like:

C:\Windows\System32>chkdsk f:
The type of the file system is NTFS.

WARNING!  /F parameter not specified.
Running CHKDSK in read-only mode.

Stage 1: Examining basic file system structure ...
  256 file records processed.
File verification completed.
  0 large file records processed.
  0 bad file records processed.

Stage 2: Examining file name linkage ...
  3 reparse records processed.
  308 index entries processed.
Index verification completed.
  0 unindexed files scanned.
  0 unindexed files recovered to lost and found.
  3 reparse records processed.

Stage 3: Examining security descriptors ...
Security descriptor verification completed.
  27 data files processed.
CHKDSK is verifying Usn Journal...
  2480 USN bytes processed.
Usn Journal verification completed.
The master file table's (MFT) BITMAP attribute is incorrect.
The Volume Bitmap is incorrect.
Windows has checked the file system and found problems.
Please run chkdsk /scan to find the problems and queue them for repair.

  31265605 KB total disk space.
    533380 KB in 40 files.
        80 KB in 28 indexes.
         0 KB in bad sectors.
     44805 KB in use by the system.
     42672 KB occupied by the log file.
  30687340 KB available on disk.

      4096 bytes in each allocation unit.
   7816401 total allocation units on disk.
   7671835 allocation units available on disk.

[Bostjan]

Actually this is the same thing as http://www.futeko.com/newforum/index.php?topic=2646.0

[velo]