search

pavva94 / snake-os

Automatically exported from code.google.com/p/snake-os
0 stars 1 forks source link

USB hard disk stopped mounting #307

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. Connect USB HDD (WD 160Gb ext3) to USB2 port. 

What is the expected output? What do you see instead?
I expected the disk to be auto-mounted and have access to the disk files. 
Instead the disk is not recognized and not mounted.

What version of the product are you using? On what operating system?
SNAKE OS V1.3.2 (20111007). 

Please provide any additional information below.
The disk worked fine with the NAS for many months. Stopped working after a 
reboot. The disk itself works ok on another Ubuntu machine. 
Below is some information from the system log:

usbcore: registered new driver usbserial
drivers/usb/serial/usb-serial.c: USB Serial Driver core
drivers/usb/serial/usb-serial.c: USB Serial support registered for FTDI USB 
Serial Device
usbcore: registered new driver ftdi_sio
drivers/usb/serial/ftdi_sio.c: v1.4.3:USB FTDI Serial Converters Driver
usb 1-2: new high speed USB device using str8100-ehci and address 4
usb 1-2: new high speed USB device using str8100-ehci and address 6
usb 1-2: new high speed USB device using str8100-ehci and address 7
usb 1-2: configuration #1 chosen from 1 choice
usb 1-2: can't set config #1, error -71
usb 1-2: USB disconnect, address 7
usb 1-2: new high speed USB device using str8100-ehci and address 8
usb 1-2: new high speed USB device using str8100-ehci and address 9
usb 1-2: configuration #1 chosen from 1 choice
usb 1-2: can't set config #1, error -71

Original issue reported on code.google.com by yulia1...@gmail.com on 4 Jul 2012 at 5:43

GoogleCodeExporter commented 8 years ago 
Odd, are you sure it's not just a bad cable or interference?

If I understand that part of the usb driver correctly error -71 can be caused 
by (among other things) a bad connection.

Original comment by stefansc...@googlemail.com on 9 Jul 2012 at 12:18

GoogleCodeExporter commented 8 years ago 
I tried another cable and got the same error. Both cables work perfectly with 
Ubuntu laptop. I believe I can rule out interference too.

Original comment by yulia1...@gmail.com on 9 Jul 2012 at 5:03

GoogleCodeExporter commented 8 years ago 
ok, I'll take another look at the driver. Maybe there's a way to get more info 
out of it.

Original comment by stefansc...@googlemail.com on 9 Jul 2012 at 10:37