XPost: aus.computers   
   From: nospam@needed.invalid   
      
   On Mon, 11/24/2025 5:37 PM, Felix wrote:   
   >   
   > I noticed a second drive in a Win7 PC was not in File Exploiter, and didn't   
   appear in file management, so I tried it in a couple of other PC's, same   
   thing. When I put it in my Linux 22 box it appears unmounted but LM tries to   
   mount it viz:   
   >   
   > https://auslink.info/files/disk1.png   
   > https://auslink.info/files/disk2.png   
   >   
   > The motor is running since I can feel the vibrations from the platters   
   spinning. What could be the problem? What can I do/use to diagnose/remedy it?   
   thanks   
   >   
   > p.s. just another reason Linux is better than Windoze. Win boxes couldn't   
   even see the drive!   
   >   
      
   sudo apt install smartmontools    # Most likely, already installed   
      
     sudo smartctl -a /dev/sde         # Check drive-reported health   
      
   sudo apt install gddrescue        # Need a place to put the data (use a spare   
   disk) ... ddrescue   
      
     sudo ddrescue -f -n     /dev/sde /def/sdf /root/rescue.log    # Drive to   
   drive rescue (same sized drive)   
      
     sudo xed /root/rescue.log  # Examine transfer record, for extent of damage   
      
     sudo ddrescue -d -f -r3 /dev/sde /def/sdf /root/rescue.log    # Try to   
   recover the remaining damaged sectors   
      
   sudo apt install disktype   
      
     sudo disktype /dev/sdf           # See if the good-quality backup drive, is   
   recognizable.   
                                      # Should report the partition setup.   
      
   Sometimes, a disk partition, the "envelope" the file system is in   
   and the file system, are not the same size. It's even possible for   
   a file system to hang over the end of the drive (which is not good).   
   Should an OS mount a mis-shaped partition ? IDK. Bad karma.   
      
   There is more to disk drives than pretty pictures,   
   and lots of cool ways it can fail.   
      
   I can show you a drive, that has a firmware problem where   
   the UEFI BIOS issues some sort of command... that causes UEFI   
   to freeze, with a Seagate 4TB drive. There is some sort of   
   erroneous response from the drive, that UEFI does not like.   
   However, if you remove the OS on the 4TB drive, such that   
   the UEFI "analyze" code is not triggered, the computer starts   
   fine. This means the drive can only be used as a data drive,   
   not as an OS drive.   
      
   You can use "gnome-disks", to do a read-benchmark of a drive.   
   There is a menu somewhere in the upper right of gnome-disks,   
   with the benchmark option. Remember to UNTICK the write-test   
   option as you do not want gnome-disks to attempt writing while   
   it benches. The read benchmark is an attempt to see how   
   sick the drive is (whether it has any "slow-spots" on it).   
      
      Paul   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)