I am experiencing the same issue when I plugged my seagate backup plus in USB 3.0 port and not issue if plugged in usb 2.0. OS: Scientific Linux, kernel 2.6.32 .
And other important observation is the issue is same in windows 7.
From my observations I infer the issue is related with USB controllers/firmware which might have been set right by vendors through some control on chipsets/mother boards which is being reset with usbreset mentioned above or by something else by users and going in to trouble.
Hope these observations lead to solution.
( I already used the work-around : umount before googling the issue and is working fine ).
I am experiencing the same issue when I plugged my seagate backup plus in USB 3.0 port and not issue if plugged in usb 2.0. OS: Scientific Linux, kernel 2.6.32 .
And other important observation is the issue is same in windows 7.
Other important observation which may be helpful to trouble shooters is that I experience this issue after I compiled and used the usbreset (usbreset.c) program from unix.stackexcha nge.com/ questions/ 7051/how- to-re-mount- a-usb-stick- after-unmountin g-from- nautilus- without- disconnecting
http://
( I used this program on USB 3.0 port only )
Before that there is no such issue.
My mother board is GIGABYTE 970A-DS3P
From my observations I infer the issue is related with USB controllers/ firmware which might have been set right by vendors through some control on chipsets/mother boards which is being reset with usbreset mentioned above or by something else by users and going in to trouble.
Hope these observations lead to solution.
( I already used the work-around : umount before googling the issue and is working fine ).