Files are constantly missing from the mobile SSD drive.

[TheGoodGoodMan]

Hi. I have this problem, I have SSD Samsung 850Pro 512 and using it between two computers. One is running win 8 and SSD is connected with normal internal SATA port. Another one is running Win10 and SSD connects through external eSATA. The problem is that when i for example, export JPEGs in LightRoom on Win8 machine to SSD drive when i connect it back to Win10 exported files are not visible, or there is a folder but i can't access it. It says that files are missing. Both drives have the same letter on both computers and i know that SSD is not broken because i got a new one and the problem is still here.
Is there some way that SSD uses some kind of system bound file indexing system that make them invisible when drive is connected to another system?
I will do some experimenting tomorrow because today i have no access to two computers, but in the meantime, I hope that someone can put some light on this problem. Thanks in advance.

 

[USAFRet]

Are any files 'missing'?
This might be a function of the Lightroom catalog. Where does that live?

 

[TheGoodGoodMan]

They are missing in normal windows file explorer. The Even weirder thing is that when i connect SSD back to win8 the files are still missing, but they were there accessible before disconnecting SSD and connecting it to win10 computer then connecting it back to win8.
In plain English: after exporting JPEGs on win8 i can access them without any problems. When i connect drive to win10 files are missing or ae not accessible. When i connect it back to win8 files are still missing or are inaccessible.

 

[USAFRet]

Any other files missing? Or just those associated with Lightroom?

 

[TheGoodGoodMan]

AfterEffects files are missing as well. This drive is for LightRoom and AfterEffects only. I will do more testing tommorow when i am back home.

 

[USAFRet]

I know of nothing specific to an SSD that might cause that. At that level, it's just another drive.

 

[TheGoodGoodMan]

I recently switched on RAPID mode on my system SSD on win8. You think that it might have something to do with it?

 

[USAFRet]

I recently switched on RAPID mode on my system SSD on win8. You think that it might have something to do with it?

No, it shouldn't. That's just a proprietary name for RAMDisk.
If the files exist in File Explorer in one system, they should exist when you move that drive to a different PC.

Does the folder exist?
How is the drive connected on each system? Internally on one, and eSATA on the other?

 

[TheGoodGoodMan]

Yes. SATA on Win8 and eSATA on Win10.

 

[TheGoodGoodMan]

I know it's not SSD because i just got new one. After i couldn't access files this time on new SSD i thought maybe i would change drive letter. After i dit it drive as a whole is inaccessible.

 

[TheGoodGoodMan]

You think it might be SSD case fault? But why only recent files are corrupted?

 

[USAFRet]

You think it might be SSD case fault? But why only recent files are corrupted?

Doubtful, but check its health with the Samsung Magician tool.

 

[TheGoodGoodMan]

I meant SSD case/cover thing i put SSD in to, to connect through eSATA.

 

[USAFRet]

I meant SSD case/cover thing i put SSD in to, to connect through eSATA.

Again, doubtful. What happens if you do it without the case?
Can you do it without the case?

 

[TheGoodGoodMan]

I will do some experimenting tomorrow and will post my findings. Thanks a lot for response!

 

[TheGoodGoodMan]

Ok.
So i exported some photos in LightRoom ion Win8. Few sessions into few folders. Before exporting my free space was 98GB and after 92GB but when i change computers to Win10 free space was 98GB again on the new computer.Out of 9 folders, one was invisible(gone), one was inaccessible and 7 was accessible with no problem. Win10 asked me to restart computer to fix drive errors, so i did. After repairing free space was normal 92GB and all data was accessible. Any idea what is going on?

 

[TheGoodGoodMan]

Another test.
I copied around 22GB back on Win8 from another drive. Space before 92GB after 69GB, same after i connected SSD to Win10. No problems, no errors. I deleted this copied folder on Win10 and connected disk back to Win8. It shows 69GB of free space and deleted folder still there but not accessible. What is going on?!
Win8 asked me to restart computer to fix drive error, after i did it free size shows 92GB but deleted folder is still there not accessible and i can't delete it.

 

[USAFRet]

Another test.
I copied around 22GB back on Win8 from another drive. Space before 92GB after 69GB, same after i connected SSD to Win10. No problems, no errors. I deleted this copied folder on Win10 and connected disk back to Win8. It shows 69GB of free space and deleted folder still there but not accessible. What is going on?!
Win8 asked me to restart computer to fix drive error, after i did it free size shows 92GB but deleted folder is still there not accessible and i can't delete it.

Different Recycle Bins.
When you delete something, it still exists, just marked as usable space, and invisible to that OS.
Move it to a different system, and it is kinda, sorta still there.

 

[TheGoodGoodMan]

On both systems i have Samsung SSD drives for OS. I have it set to maximum performance. This option have an extra file indexing. I changed it to maximum reliability to eliminate extra indexing. After trying second test, when i am deleting files on Win10, files remain deleted on Win8 as well. Now i will try to export photos through LightRoom.
I REALLY hope that's it...

 

[TheGoodGoodMan]

After last import all files are accessible and free disk size is correct. It seems that extra indexing done by Samsung Magician was the reason for all of this mess. Let's hope so. You would think that they will inform you that it can mess up mobile SSD drives. Och well.
Thanks for sticking with me.

 

[USAFRet]

After last import all files are accessible and free disk size is correct. It seems that extra indexing done by Samsung Magician was the reason for all of this mess. Let's hope so. You would think that they will inform you that it can mess up mobile SSD drives. Och well.
Thanks for sticking with me.

Indexing on an SSD is generally not needed. They are already fast enough.
Glad you got it figured out, though.