On 2022-01-30 21:08, Alan Stern wrote:
On Sun, Jan 30, 2022 at 01:55:35PM -0500, James wrote: It's not easy to tell why the command timed out. Maybe the drive encountered a problem and therefore wasn't able to execute the command. Or maybe it did execute the command but the response message going back to the computer got lost.
Can I increase the timeout? The error is always exactly the same. Could there be a bad sector on the drive?
