Page 1 of 1

usb disk problem

Posted: Sun Oct 14, 2012 1:43 pm
by sventrax
Hi to all,
this is my very first post in this Forum.
I've just configured one of my raspberry pi with raspbian to handle my web server (nginx) and mldonkey.
Mlnet was configure with two symbolic links to a folde that is on an ext4 usb external disk.
At the beginning of the test everything was fine, but now, every time I get this error:

Oct 14 15:09:48 raspberrypi kernel: [148591.416145] EXT4-fs error (device sdb1): ext4_find_entry:935: inode #2: comm mlnet: reading directory lblock 0

And this is message log

Oct 14 06:25:07 raspberrypi rsyslogd: [origin software="rsyslogd" swVersion="5.8.11" x-pid="1695" x-info="http://www.rsyslog.com"] rsyslogd was HUPed
Oct 14 15:09:18 raspberrypi kernel: [148561.433141] ERROR::dwc_otg_hcd_urb_enqueue:477: Not connected
Oct 14 15:09:18 raspberrypi kernel: [148561.433153]
Oct 14 15:09:18 raspberrypi kernel: [148561.433239] ERROR::dwc_otg_hcd_urb_enqueue:477: Not connected
Oct 14 15:09:18 raspberrypi kernel: [148561.433247]
Oct 14 15:09:18 raspberrypi kernel: [148561.433270] ERROR::dwc_otg_hcd_urb_enqueue:477: Not connected
Oct 14 15:09:18 raspberrypi kernel: [148561.433277]
Oct 14 15:09:18 raspberrypi kernel: [148561.433297] ERROR::dwc_otg_hcd_urb_enqueue:477: Not connected
Oct 14 15:09:18 raspberrypi kernel: [148561.433305]
Oct 14 15:09:18 raspberrypi kernel: [148561.487409] usb 1-1: USB disconnect, device number 7
Oct 14 15:09:18 raspberrypi kernel: [148561.487434] usb 1-1.1: USB disconnect, device number 8
Oct 14 15:09:18 raspberrypi kernel: [148561.487635] smsc95xx 1-1.1:1.0: eth0: unregister 'smsc95xx' usb-bcm2708_usb-1.1, smsc95xx USB 2.0 Ethernet
Oct 14 15:09:19 raspberrypi kernel: [148562.357473] sd 1:0:0:0: [sdb] Unhandled error code
Oct 14 15:09:19 raspberrypi kernel: [148562.357518] sd 1:0:0:0: [sdb] Result: hostbyte=0x07 driverbyte=0x00
Oct 14 15:09:19 raspberrypi kernel: [148562.357539] sd 1:0:0:0: [sdb] CDB: cdb[0]=0x2a: 2a 00 02 44 01 a7 00 00 50 00
Oct 14 15:09:19 raspberrypi kernel: [148562.457463] sd 1:0:0:0: [sdb] Unhandled error code
Oct 14 15:09:19 raspberrypi kernel: [148562.457491] sd 1:0:0:0: [sdb] Result: hostbyte=0x07 driverbyte=0x00
Oct 14 15:09:19 raspberrypi kernel: [148562.457528] sd 1:0:0:0: [sdb] CDB: cdb[0]=0x2a: 2a 00 02 44 00 3f 00 00 08 00
Oct 14 15:09:19 raspberrypi kernel: [148562.457601] lost page write due to I/O error on sdb1
Oct 14 15:09:19 raspberrypi kernel: [148562.557449] sd 1:0:0:0: [sdb] Unhandled error code
Oct 14 15:09:19 raspberrypi kernel: [148562.557477] sd 1:0:0:0: [sdb] Result: hostbyte=0x07 driverbyte=0x00
Oct 14 15:09:19 raspberrypi kernel: [148562.557496] sd 1:0:0:0: [sdb] CDB: cdb[0]=0x2a: 2a 00 00 00 21 47 00 00 08 00
Oct 14 15:09:19 raspberrypi kernel: [148562.557564] lost page write due to I/O error on sdb1
Oct 14 15:09:19 raspberrypi kernel: [148562.798108] usb 1-1.3: USB disconnect, device number 9
Oct 14 15:09:19 raspberrypi kernel: [148562.798131] usb 1-1.3.2: USB disconnect, device number 10
Oct 14 15:09:20 raspberrypi kernel: [148563.424359] usb 1-1.3.3: USB disconnect, device number 11
Oct 14 15:09:20 raspberrypi kernel: [148563.597619] Indeed it is in host mode hprt0 = 00021501
Oct 14 15:09:20 raspberrypi kernel: [148563.887395] usb 1-1: new high-speed USB device number 12 using dwc_otg
Oct 14 15:09:20 raspberrypi kernel: [148563.887555] Indeed it is in host mode hprt0 = 00001101
Oct 14 15:09:21 raspberrypi kernel: [148564.137696] usb 1-1: New USB device found, idVendor=0424, idProduct=9512
Oct 14 15:09:21 raspberrypi kernel: [148564.137724] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Oct 14 15:09:21 raspberrypi kernel: [148564.142114] hub 1-1:1.0: USB hub found
Oct 14 15:09:21 raspberrypi kernel: [148564.142288] hub 1-1:1.0: 3 ports detected
Oct 14 15:09:21 raspberrypi kernel: [148564.417486] usb 1-1.1: new high-speed USB device number 13 using dwc_otg
Oct 14 15:09:21 raspberrypi kernel: [148564.517763] usb 1-1.1: New USB device found, idVendor=0424, idProduct=ec00

Anyone has got an idea of what was going wrong with my system ?
Disk is connected to a powered hub from which raspberry pi takes power.
The hub is a belkin that works fine with pi as stated in http://elinux.org/RPi_VerifiedPeripherals
Thanks a lot to everyone, bye,
Stefano

Re: usb disk problem

Posted: Sun Oct 14, 2012 8:56 pm
by rpifreeze
Yea, yea, yea...
Same symptoms as in my example, but no solution for now.
Sorry for being too rude, but seems we're left without working software :(
First, it was "power issue" and suggestion to power Pi from hub, but now I see again some comments/suggestions to buy "better adapter".
For christ sake, what means better adapter ?
We (1,2nd world have money for better PSU, but will you save the same to 3rd world for which these "computers" were aimed to ?
"Hey, buy better psu, because it's not working. Which one ? Oh, better one, yours is bad. What paramters shall it have ? Hmm, you really should buy better one. Your is is the one of worse ones"
Guess, we're not told the truth about chips used in RPi. Who knowns...he knows :)

Could you give me some details, voltage between TP1 and TP2 and on USB output ?
Did you leave Pi untouched or were you doing some heavy disk operations (above 1 MB/s?)

Re: usb disk problem

Posted: Sun Oct 14, 2012 9:26 pm
by elatllat

Re: usb disk problem

Posted: Sun Oct 14, 2012 10:11 pm
by Lob0426
Your hub shows three ports. What is the rating of the power supply for the hub? In my experience you need at least 800ma (4 watts) just for the USB HDD, plus what ever else you have plugged into the hub. I recommend at least a 4 port USB hub with a 2A PSU.
Help us out a little by providing a little more information;
info on your hub and its PSU
info on your USB HDD (USB to SATA adapter, USB HDD in enclosure etc.)

Re: usb disk problem

Posted: Mon Oct 15, 2012 6:28 am
by sventrax
my hub is 4 ports, 2A, and disk is connected with an Y cable to two ports .... so I don't believe it is a power problem.
Anyway I will try to connect the power usb of the Y cable to the usb port of the router.
Thanks,
ste

Re: usb disk problem

Posted: Mon Oct 15, 2012 7:08 am
by sventrax
To be correct, my hub is belkin F5U404PerBLK
I will try the solution offered on elinux.org
Thanks again,
ste

Re: usb disk problem

Posted: Mon Oct 15, 2012 8:03 pm
by sventrax
Here I am.
Just to say, with a fat32 8gb pen everything works fine.
I've just tested the proposed solution with the usual 60GB usb2 sata hardisk.
So changed

vm.min_free_kbytes = 32768 in /etc/sysctl.conf
smsc95xx.turbo_mode=N in /boot/cmdline.txt

Connected Y cable to router usb to avoid power problems.
Changed cable that connects hub and mini usb in RPI.
then increased memory using 32MB for video and 224 for system.

This is the result:


[email protected]:/home/pi# cat /var/log/messages | grep -i erro
Oct 14 15:09:18 raspberrypi kernel: [148561.433141] ERROR::dwc_otg_hcd_urb_enqueue:477: Not connected
Oct 14 15:09:18 raspberrypi kernel: [148561.433239] ERROR::dwc_otg_hcd_urb_enqueue:477: Not connected
Oct 14 15:09:18 raspberrypi kernel: [148561.433270] ERROR::dwc_otg_hcd_urb_enqueue:477: Not connected
Oct 14 15:09:18 raspberrypi kernel: [148561.433297] ERROR::dwc_otg_hcd_urb_enqueue:477: Not connected
Oct 14 15:09:19 raspberrypi kernel: [148562.357473] sd 1:0:0:0: [sdb] Unhandled error code
Oct 14 15:09:19 raspberrypi kernel: [148562.457463] sd 1:0:0:0: [sdb] Unhandled error code
Oct 14 15:09:19 raspberrypi kernel: [148562.457601] lost page write due to I/O error on sdb1
Oct 14 15:09:19 raspberrypi kernel: [148562.557449] sd 1:0:0:0: [sdb] Unhandled error code
Oct 14 15:09:19 raspberrypi kernel: [148562.557564] lost page write due to I/O error on sdb1
Oct 15 21:48:54 raspberrypi kernel: [ 4308.835089] ERROR::dwc_otg_hcd_urb_enqueue:477: Not connected
Oct 15 21:48:54 raspberrypi kernel: [ 4308.835501] ERROR::dwc_otg_hcd_urb_enqueue:477: Not connected
Oct 15 21:48:54 raspberrypi kernel: [ 4308.835534] ERROR::dwc_otg_hcd_urb_enqueue:477: Not connected
Oct 15 21:48:54 raspberrypi kernel: [ 4308.835563] ERROR::dwc_otg_hcd_urb_enqueue:477: Not connected
Oct 15 21:48:55 raspberrypi kernel: [ 4310.181327] EXT4-fs warning (device sdb1): ext4_end_bio:251: I/O error writing to inode 524294 (offset 80220160 size 4096 starting block 66697)
Oct 15 21:48:55 raspberrypi kernel: [ 4310.181722] JBD2: Detected IO errors while flushing file data on sdb1-8

Oct 15 21:48:54 raspberrypi kernel: [ 4308.835089] ERROR::dwc_otg_hcd_urb_enqueue:477: Not connected
Oct 15 21:48:54 raspberrypi kernel: [ 4308.835501] ERROR::dwc_otg_hcd_urb_enqueue:477: Not connected
Oct 15 21:48:54 raspberrypi kernel: [ 4308.835534] ERROR::dwc_otg_hcd_urb_enqueue:477: Not connected
Oct 15 21:48:54 raspberrypi kernel: [ 4308.835563] ERROR::dwc_otg_hcd_urb_enqueue:477: Not connected
Oct 15 21:48:55 raspberrypi kernel: [ 4310.181327] EXT4-fs warning (device sdb1): ext4_end_bio:251: I/O error writing to inode 524294 (offset 80220160 size 4096 starting block 66697)
Oct 15 21:48:55 raspberrypi kernel: [ 4310.181722] JBD2: Detected IO errors while flushing file data on sdb1-8



[email protected]:/home/pi# cat /var/log/syslog | grep -i erro
Oct 15 20:37:13 raspberrypi ntpd[2033]: restrict: error in address '::' on line 38. Ignoring...
Oct 15 20:37:13 raspberrypi ntpd[2033]: restrict: error in address '::1' on line 42. Ignoring...
Oct 15 21:48:54 raspberrypi kernel: [ 4308.835089] ERROR::dwc_otg_hcd_urb_enqueue:477: Not connected
Oct 15 21:48:54 raspberrypi kernel: [ 4308.835501] ERROR::dwc_otg_hcd_urb_enqueue:477: Not connected
Oct 15 21:48:54 raspberrypi kernel: [ 4308.835534] ERROR::dwc_otg_hcd_urb_enqueue:477: Not connected
Oct 15 21:48:54 raspberrypi kernel: [ 4308.835563] ERROR::dwc_otg_hcd_urb_enqueue:477: Not connected
Oct 15 21:48:55 raspberrypi kernel: [ 4310.181289] Buffer I/O error on device sdb1, logical block 66689
Oct 15 21:48:55 raspberrypi kernel: [ 4310.181327] EXT4-fs warning (device sdb1): ext4_end_bio:251: I/O error writing to inode 524294 (offset 80220160 size 4096 starting block 66697)
Oct 15 21:48:55 raspberrypi kernel: [ 4310.181494] JBD2: I/O error detected when updating journal superblock for sdb1-8.
Oct 15 21:48:55 raspberrypi kernel: [ 4310.181722] JBD2: Detected IO errors while flushing file data on sdb1-8
Oct 15 21:48:55 raspberrypi kernel: [ 4310.181838] JBD2: I/O error detected when updating journal superblock for sdb1-8.
Oct 15 21:49:22 raspberrypi kernel: [ 4337.351179] EXT4-fs error (device sdb1): ext4_find_entry:935: inode #524289: comm mlnet: reading directory lblock 0
Oct 15 21:49:22 raspberrypi kernel: [ 4337.386202] EXT4-fs error (device sdb1): ext4_journal_start_sb:327: Detected aborted journal
Oct 15 21:49:24 raspberrypi kernel: [ 4338.946361] EXT4-fs error (device sdb1): ext4_read_block_bitmap:394: comm mlnet: Cannot read block bitmap - block_group = 2, block_bitmap = 1027
Oct 15 21:49:24 raspberrypi kernel: [ 4338.965416] EXT4-fs error (device sdb1): ext4_discard_preallocations:3892: comm mlnet: Error reading block bitmap for 2

Any help appreciated, bye,
Ste

Re: usb disk problem

Posted: Tue Oct 16, 2012 8:01 pm
by rpifreeze
For me, it seems like a usb hub issue, so please try replacing hub first.
It's all about power or other device corrupting/interfering with your disk.

Re: usb disk problem

Posted: Tue Oct 16, 2012 8:15 pm
by notarat
In general. the F5U404PerBLK USB Hub and Power supply are fine.

Stop saying the problem is the hub. It's not.

I've been using it for over a month with USB DVD Players, USB SSDs, and USB HDDs for over a month had not a single problem related to the Hub or it's power supply.

Re: usb disk problem

Posted: Tue Oct 16, 2012 8:37 pm
by Lob0426
It is likely a keyboard/hdd problem. I would try a differrent keyboard.

Re: (SOLVED) usb disk problem

Posted: Wed Oct 17, 2012 6:31 am
by sventrax
Issu solved.
Asking in

https://github.com/raspberrypi/linux/issues/136

they driven me to the solution.
The problem was that I was using the powered hub to power the pi, but with a simple cable, so I was giving the pi only 500mA ... too less.
Using a different power source (1A, connecting disk to the powered hub) everything works fine now.
Bye,
Ste

Re: usb disk problem

Posted: Wed Oct 17, 2012 9:09 pm
by rpifreeze
@sventrax - dont be so fast :)
Let it run for a day/two without manual restarts and tell us if it worked.

Re: usb disk problem

Posted: Thu Oct 18, 2012 7:23 am
by sventrax
Till now it's up and runnig for 40h
http://duddu.no-ip.org

It works fine .... If something goes wrong I'll let you know.
Bye,
Ste

Re: usb disk problem

Posted: Thu Nov 01, 2012 7:49 pm
by BrianM
Got a dreaded
error dwc_otg_hcd_urb_enqueue:477 not connected
Had assumed everything but the power supply, as it had been working fine for several days with several different versions of OS
However, replacing PSU solved the error and the boot process (and installation) carried on fine...

Re: usb disk problem

Posted: Tue Jun 24, 2014 8:25 pm
by [OvO]wl
No this error has nothing at all to do with power. NOTHING.

I have 2 raspberry pis, one i used at work as a thin client, and one i kept at home.

At work some dickhead ran passwd on it, and it had a 6 month uptime, i rebooted it when the wifi networking access point changed details, i had to reboot the system to sort out the mess my dodgy script made of the network configuration.

I boot up only to find a can't login, because someone thought it was funny to change the password. So anyway, to cut a long story short, i took the SD card home, had issues with SD card corruption.

I was able to boot up my backup rpi with keyboard and mouse fine, but then when i took the same sd card and put it into the one at work that had SD card corruption, it boots up with these error messages and i am unable to login because there's no keyboard and mouse. There's also no networking lights. It makes me wonder if the USB hub with the ethernet, and 2x usb adapters has somehow been fried.

But this is NOT a power issue, it's clearly a hardware / firmware issue.

Re: usb disk problem

Posted: Tue Jun 24, 2014 11:10 pm
by DougieLawson
if you have password troubles use single user mode (edit /boot/cmdline.txt add init=/bin/sh). When that boots you get a root shell running and can update any/every password with passwd (for the root password) and passwd pi (or whatever userid) for others.

Last thing you do in the shell is update /boot/cmdline.txt to remove the init= parm then shutdown and reboot (or exec init)

Re: usb disk problem

Posted: Wed Jun 25, 2014 11:17 am
by [OvO]wl
Hi,

Yes the first thing i tried was init=/bin/sh. However my raspberry pi just ignored any enters or returns i pressed (this was before the keyboard stopped working) so i am skeptical that this advice works, especially considering several other people also found that it didn't work either ;)

Cheers for the advice - it's worth trying, but don't get your hopes up.

Re: usb disk problem

Posted: Wed Jun 25, 2014 12:05 pm
by RaTTuS
please use a new thread and not a 2 year old one