XPost: aus.computers   
   From: none@not.here   
      
   Computer Nerd Kev wrote:   
   > In aus.computers Felix  wrote:   
   >> Computer Nerd Kev wrote:   
   >>> In aus.computers Felix  wrote:   
   >>>> Computer Nerd Kev wrote:   
   >>>>> But then he hasn't expressed whether he's interested in the data   
   >>>>> or wants to re-use the drive.   
   >>>> both. if I can access it I'll get the data of, and if the disk is ok   
   >>>> I'll keep it for non critical use   
   >>> Best focus on getting the data off first then because if the drive   
   >>> is dying it might suddenly stop working entirely after being left   
   >>> on much longer.   
   >>>   
   >> I don't have another drive to copy to atm   
   > Well if you value the data then leave it alone until you do.   
      
   that's the plan   
      
   >   
   >>> backup image that you can restore if it goes wrong. You can also   
   >>> compress the backup to avoid needing a full 1TB of space if you're   
   >>> going to run the recovery software on the drive:   
   >>>   
   >>>     sudo dd if=/dev/sde bs=4096 noerror status=progress | gzip -c >   
   ~/broken_disk.img.gz   
   >>>   
   >> I'm not comfortable using the terminal. I'll try the freezing method   
   >> when I have access to another drive to copy to   
   > That's silly when there's nothing to tell you that the drive is at   
   > fault and it could just be that the OS stuffed it up. Freezing might   
   > stuff up a perfectly good drive.   
   >   
   > Anyway why ask about getting data off before you had a place to put   
   > it?   
      
   I've been asking about getting the drive working.   
      
   >   If you _don't_ really care about the data and are willing to   
   > risk losing it, 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.   
   > Though I've had Windows CHKDSK delete lots of stuff from a drive   
   > before so I'd still recommend making a backup image of it first if   
   > the data is more than curiosity value. If Windows won't run CHKDSK   
   > then you could try using fixntfs on Linux first to mark it "dirty",   
   > but since that's a command-line tool I guess you won't want to.   
   >   
      
      
   --   
   Linux Mint 22.2   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)