The external hard drive that I use to back up (SuperDuper!) my laptop is behaving oddly. Very capricious about mounting, and if successfully mounted, in being persuaded to unmount again. Twice when I tried to make a smart copy, the copy failed (the second time it got right to the end but failed at making the disk bootable), at the third attempt the SD! icon started bouncing up and down non-stop in the Dock and I kept getting coloured beachballs all the time.
I ran Disk Utility First Aid twice (when the HD eventually mounted, which was after a struggle) but that went through without indicating a problem.
I got the similar (older version) external that I use for the iMac and it mounted/unmounted without difficulty, so I assume not a fault with the laptop/app (I didnt want to try making a copy on the disk as I didn't want both machines backed up on the same disk, but SD! seemed to behave perfectly normally, finding the new HD).
Could the troublesome disk have a hardware fault without Disk Utility finding it? I would find it hard to imagine physical damage, as it only moves a few feet away from the machine, occasionally put in a drawer. I didn't want to try it on the iMac in case it mucked that up. Any ideas where the fault would be? Will erasing the whole disk work?
I ran Disk Utility First Aid twice (when the HD eventually mounted, which was after a struggle) but that went through without indicating a problem.
I got the similar (older version) external that I use for the iMac and it mounted/unmounted without difficulty, so I assume not a fault with the laptop/app (I didnt want to try making a copy on the disk as I didn't want both machines backed up on the same disk, but SD! seemed to behave perfectly normally, finding the new HD).
Could the troublesome disk have a hardware fault without Disk Utility finding it? I would find it hard to imagine physical damage, as it only moves a few feet away from the machine, occasionally put in a drawer. I didn't want to try it on the iMac in case it mucked that up. Any ideas where the fault would be? Will erasing the whole disk work?
Comment