From: me@privacy.invalid
On 21 Dec 2025 18:29:01 GMT, Frank Slootweg wrote:
> The error on Windows is probably because the SSD was not properly
> ejected from the Android device (for the simple reason you couldn't
> eject it, because it wasn't recognized).
>
> If that was the case, a 'chkdsk :' should fix it. Or is
> the SSD not even recognized in Disk Management?
Oh, man, I should have known this earlier. )-: I did it the hard way: I
copied about 500 GB to another drive, deleted the rest and then did
quick format of the SSD to exFAT. It runs fine now. (I'm not in the
process of copying everything back.)
The SSD ran fine under W11, after the scan, so I think Disk Management
wasn't a problem either. I didn't look at it.
I will make of note of
chkdsk :
because I did exactly what you suggested: I didn't safely unmount the
SSD from my smartphone. Could this also be the cause of the problem?
> I had a somewhat similar problem with my test with the exFAT USB
> memory stick. On the Samsung A51 there was some kind of Eject function,
> so I used that and all was fine. But on the A56 I could not find such a
> function, so I just unplugged the USB stick and then the A56 complained
> about it not being ejected properly (Duh!) and advised to reboot to
> prevent any possible crashes.
I just learned 2 ways to safely unmount the SSD. There was a
notification giving me this option and it should also be possible with
the Files app. I assume it's also possible with Total Commander.
> If Windows' Disk Management, chkdsk and File Explorer don't complain,
> I don't see a reason to suspect the SSD, but perhaps Paul over there -->
> :-) has other/better ideas.
Well, it's working now. I had no chance to try chkdsk, so if it happens
again I'll certainly try that. For now, I blame the problem on me not
safely unmounting the SSD.
--
s|b
--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)
|
