XPost: aus.computers   
   From: not@telling.you.invalid   
      
   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.   
      
   >>   In the former case, he should stop messing around   
   >> looking at SMART data   
   >   
   > I've been doing what others suggested   
   >   
   >> and make a disk image.   
   >   
   > how can I make an image of a disk that can't be read?   
      
   It can be read, otherwise you wouldn't see that there's an NTFS   
   filesystem on it. The filesystem is corrupt so it can't be   
   _mounted_. That might be due to the drive failing or the OS messed   
   it up. Either way if you've got another drive big enough to store   
   it, make an image using "dd" or "ddrescue" as Paul suggested. I   
   haven't used the latter, but for dd:   
      
     sudo dd if=/dev/sde bs=4096 noerror status=progress of=~/broken_disk.img   
      
   WARNING:   
   Messing up that command can overwrite other drives. You might need   
   to change of=~/broken_disk.img to point somewhere else if there   
   isn't enough space on the drive where you home directory is kept   
   (1TB required), but don't use "of=/dev/[something]".   
      
   You can then either run recovery programs on the image, or run them   
   on the drive if you think it's not dying, but either way you have a   
   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   
      
   >>   In the latter case run a self-test as I suggested   
   >   
   > doing that now   
      
   Again I would've done that after I got the data off the drive if   
   that mattered. Although I think in theory you can do both at the   
   same time.   
      
   --   
   __          __   
   #_ < |\| |< _#   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)