XPost: aus.computers   
   From: none@not.here   
      
   Rod Speed wrote:   
   > On Thu, 27 Nov 2025 19:08:33 +1100, Felix  wrote:   
   >   
   >> Computer Nerd Kev wrote:   
   >>> In aus.computers Paul  wrote:   
   >>>> On Wed, 11/26/2025 5:58 PM, Computer Nerd Kev wrote:   
   >>>>> then leave it connected to a Windows PC while it   
   >>>>> boots up so it should automatically CHKDSK it during start-up.   
   >>>> No.   
   >>> Umm, you snipped:   
   >>>   
   >>>>> run the drive's self-test (no "mounting" involved) and if it   
   >>>>> passes ^^^^^^^^^   
   >>>     ^^^^^^   
   >>>>> then leave it connected to a Windows PC while it boots up so   
   >>>>> it should automatically CHKDSK it during start-up.   
   >>>> I've already explained at some point, that in-place repair   
   >>>> of a sick disk with CHKDSK is wrong.   
   >>> The disk's not sick if SMART shows no failures and it's and passed   
   >>> the built-in self-test IMHO. The OS might have messed up the data   
   >>> on it, or power was cut during a write.   
   >>   
   >> if it's just an OS stuff up, why isn't there some program I can run   
   >> to fix it?   
   >   
   > There may well be but you want to recover the data   
   > so you cant try wiping the drive to see if that makes   
   > it visible   
   >   
      
   yes   
      
   >>>   
   >>>> You clone the disk over to known-good materials.   
   >>>> That's your golden copy.   
   >>>>   
   >>>> That is your only priority right now. Cloning the   
   >>>> bad disk to a good disk. That's the first step.   
   >>>> The idea is to make sure, before absolutely anything   
   >>>> else happens, you have that copy.   
   >>> Agreed, but he doesn't want to do that so...   
   >>>   
   >>   
      
      
   --   
   Linux Mint 22.2   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)