A specific USB cable for an external hard drive seems to offer nothing else than to conduct power for the external hdd when plugged into the Mac, as the hdd powers on but no signal appears to be transferred as nothing appears in Disk Utility or third-party recovery apps. Changing USB ports didn't help. But when I switch the cable for another of the same type the hdd is then identified and works.
However, the cable that isn't being picked up on the Mac works perfectly on the PC, making me wonder whether the cable is actually damaged or something in the "settings" associated with that cable is incorrect, if that's even possible.
The hard drives in question are NTFS-formatted and I'm using Paragon NTFS for Mac to access NTFS drives. The issue started occurring not long after the hard drives encountered constant freezing/crashing of the Chrome OS Files app on a Chromebook when trying to browse files on them, and at one point the hard drives kept shutting down within seconds of inactivity while connected to the Chromebook due to an apparent issue with the OS. However, I think on at least one occasion the cord in question still worked on the Mac after said Chrome OS issue, although maybe I misremembered. Anyway I'm not implying Google's poor OS is the cause of the Mac-unreadable-cord. Any advice on what's happening and how to rectify this is appreciated.
However, the cable that isn't being picked up on the Mac works perfectly on the PC, making me wonder whether the cable is actually damaged or something in the "settings" associated with that cable is incorrect, if that's even possible.
The hard drives in question are NTFS-formatted and I'm using Paragon NTFS for Mac to access NTFS drives. The issue started occurring not long after the hard drives encountered constant freezing/crashing of the Chrome OS Files app on a Chromebook when trying to browse files on them, and at one point the hard drives kept shutting down within seconds of inactivity while connected to the Chromebook due to an apparent issue with the OS. However, I think on at least one occasion the cord in question still worked on the Mac after said Chrome OS issue, although maybe I misremembered. Anyway I'm not implying Google's poor OS is the cause of the Mac-unreadable-cord. Any advice on what's happening and how to rectify this is appreciated.