[SOLVED] usb-storage: Status code -121 error
I am having a strange external-usb-hdd problem. Every time I want to copy data over several mb, transfer stops every couple of megabytes or so for 20-30 secss and then goes on. This makes transfers veeery slow on larger files.
Every time somthing like that happens i get in my dmesg:
My lsusb shows:
My kernel is 184.108.40.206, as a part from Linux from scratch is self-copmiled (I may paste config file if necesary).
/calls on his days as a kernel developer's guinea pig
You can use the following in /etc/modprobe.d/usb.conf or the like
Do you think that although i am using externaly powered hub to connect it, it still might be a current issue?
I also thought that it might be a power issue, but every time this happens, it shows exatly "transferred 64525/65536" (always the same number was transfered), and as far as i understand it, power problems would result in more random distribution of transfered amount of data.
Perhaps it is problem with cables (one package was not sent because of transfer error?)
I played with max_sectors parameter file.
max_secotrs - error at
128 - 64525/65536
64 - 32768/31757
32 - 15373/16384
The difference is always the same and equals 1011 bytes. I am starting to think that this is usb-transfer problem. I will try to experiment with different cables.
I exchanged cables between hub and pc, and between hub and disk and also tried both exchanged - in each case errors were the same. Changing usb port on pc also didn't help.
I think at this point it's immaterial if the port is switching off or not.
Ports give enough to power usb disks, unless this disk is some strange and unusual concoction we have yet to hear about. Yours requires too much current, indicating a fault condition.
Internally these things have chains of transistors (connected source - drain, i.e. end to end) and if they all turn on, there is 'shoot through' or positive is connected to negative.
If any one transistor is blown, there comes a decision inside the chip which provides this effect, and current skyrockets. You can imagine how this might be fairly repeatable until more transistors blow, which usually doesn't take too long.
Wouldn't that cause the same error pattern on the same files? Anyway, i tested it on another computer and it works prfectly there, so it cannot be the reason.
Perhaps i will still try on another computer throught my hub? Perhaps that's source of the problem?
Or perhaps my mainboard has some fault in its usb ports already?
I rearanged cables and now it works without problems - perhaps it is faulty cable after all?
Or perhaps the reason was some induction (cable was a bit too long so it was going several times aroud hub in circles), and after rearangning there are no such trouble? No idea, but since it's working i don't want to break it again, so i will not experiment.
|All times are GMT -5. The time now is 01:30 AM.|