From: this@ddress.is.invalid   
      
   s|b  wrote:   
   > On Fri, 19 Dec 2025 11:10:26 +0000, Andy Burns wrote:   
   >   
   > > I took a 128GB NVMe, inserted into a USB-C caddy, plugged into Win11   
   > > laptop, deleted old partitions, created single new partition, formatted   
   > > as exFAT, created one folder and one .txt file, ejected it, plugged into   
   > > Pixel8a, got a toast that said "USB available", went into Files by   
   > > Google app, the folder and text file were present.   
   >   
   > When I reconnect the SSD to my PC (W11 25H2), after it was connect to my   
   > Pixel 10, I get a message telling me I have to scan the drive for   
   > errors. When I do the scan doesn't find anything. No errors to be   
   > repaired.   
      
     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?   
      
     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.   
      
   > So maybe the SSD is to blame? I don't have any other drives to test and   
   > I don't feel like formatting the drive again...   
      
     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.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)