Won't boot when USB hard drive is attached at boot time

[tjtv]

Hi

I just installed arch linux on my pogoplug E02. It boots fine if only the usb stick where the rootfs is installed is connected at boot time. However, if both the usb stick and a USB hard drive are connected at boot time, it fails to boot. I've attached netconsole outputs from both the successful and failed boot attempts. Does anyone know what the "EHCI timed out on TD" messages mean?

Here is the netconsole output when only the usb stick is connected and it boots properly:
$this->bbcode_second_pass_code('', 'Pogoplug E02
Hit any key to stop autoboot: 0
(Re)start USB...
USB: Register 10011 NbrPorts 1
USB EHCI 1.00
scanning bus for devices... 3 USB Device(s) found
scanning bus for storage devices... 1 Storage Device(s) found
Loading file "/rescueme" from usb device 0:1 (usbda1)
** File not found /rescueme
reading /rescueme.txt

** Unable to read "/rescueme.txt" from usb 0:1 **
Creating 1 MTD partitions on "nand0":
0x000002500000-0x000008000000 : "mtd=3"
UBI: attaching mtd1 to ubi0
UBI: physical eraseblock size: 131072 bytes (128 KiB)
UBI: logical eraseblock size: 129024 bytes
UBI: smallest flash I/O unit: 2048
UBI: sub-page size: 512
UBI: VID header offset: 512 (aligned 512)
UBI: data offset: 2048
UBI: attached mtd1 to ubi0
UBI: MTD device name: "mtd=3"
UBI: MTD device size: 91 MiB
UBI: number of good PEBs: 728
UBI: number of bad PEBs: 0
UBI: max. allowed volumes: 128
UBI: wear-leveling threshold: 4096
UBI: number of internal volumes: 1
UBI: number of user volumes: 0
UBI: available PEBs: 717
UBI: total number of reserved PEBs: 11
UBI: number of PEBs reserved for bad PEB handling: 7
UBI: max/mean erase counter: 1/1
UBIFS error (pid 0): ubifs_get_sb: cannot open "ubi:rootfs", error -19
Error reading superblock on volume 'ubi:rootfs'!
Loading file "/boot/uImage" from usb device 0:1 (usbda1)
1 bytes read
Found bootable drive on usb 0:1
Loading file "/boot/uImage" from usb device 0:1 (usbda1)
2869736 bytes read
Loading file "/boot/uInitrd" from usb device 0:1 (usbda1)
** File not found /boot/uInitrd
## Booting kernel from Legacy Image at 00800000 ...
Image Name: Linux-3.1.10-16-ARCH
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 2869672 Bytes = 2.7 MiB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK

Starting kernel ...
')

Here is the netconsole output when both the usb stick and the USB hard drive are connected.
$this->bbcode_second_pass_code('', 'Pogoplug E02
Hit any key to stop autoboot: 0
(Re)start USB...
USB: Register 10011 NbrPorts 1
USB EHCI 1.00
scanning bus for devices... 4 USB Device(s) found
scanning bus for storage devices... EHCI timed out on TD - token=0x10008d80
EHCI timed out on TD - token=0x128d80
READ_CAP ERROR
3 Storage Device(s) found
Loading file "/rescueme" from usb device 0:1 (usbda1)
** File not found /rescueme
reading /rescueme.txt

** Unable to read "/rescueme.txt" from usb 0:1 **
')

[moonman]

Try attaching your boot device to the very bottom USB port. See if that helps. Also I haven't seen READ_CAP ERROR before on my device, I did see all other messages and usually they just repeat until it times out and just boots. So for me it just delays the boot process.

[tjtv]

I do have my boot device attached to the very bottom USB port. In fact, I've tried every combination of locations for boot device/USB hard drive and I always get the same netconsole error messages. I've let it try to boot for over an hour, but it never gets past the point in the netconsole log shown below.

[Socaltom]

What happens if you boot the flash drive, then hook up the hard drive? Run dmesg and post the output. I suspect something with the USB hard drive is conflicting.
Tom

[tjtv]

When I boot with just the flash drive, and attach the hard drive after bootup the hard drive gets automounted without any trouble. Attached dmesg log below:

$this->bbcode_second_pass_code('', '[69003.616239] usb 1-1.3: new high speed USB device number 4 using orion-ehci
[69003.731019] scsi1 : usb-storage 1-1.3:1.0
[69004.726542] scsi 1:0:0:0: Direct-Access WD My Book 1140 1012 PQ: 0 ANSI: 6
[69004.728289] sd 1:0:0:0: Attached scsi generic sg1 type 0
[69004.729426] scsi 1:0:0:1: Enclosure WD SES Device 1012 PQ: 0 ANSI: 6
[69004.730529] scsi 1:0:0:1: Attached scsi generic sg2 type 13
[69004.732887] sd 1:0:0:0: [sdb] 732558336 4096-byte logical blocks: (3.00 TB/2.72 TiB)
[69004.733623] sd 1:0:0:0: [sdb] Write Protect is off
[69004.733641] sd 1:0:0:0: [sdb] Mode Sense: 47 00 10 08
[69004.734370] sd 1:0:0:0: [sdb] No Caching mode page present
[69004.744624] sd 1:0:0:0: [sdb] Assuming drive cache: write through
[69004.759141] sd 1:0:0:0: [sdb] 732558336 4096-byte logical blocks: (3.00 TB/2.72 TiB)
[69004.760631] sd 1:0:0:0: [sdb] No Caching mode page present
[69004.773741] sd 1:0:0:0: [sdb] Assuming drive cache: write through
[69018.036066] sdb: sdb1
[69018.039632] sd 1:0:0:0: [sdb] 732558336 4096-byte logical blocks: (3.00 TB/2.72 TiB)
[69018.041123] sd 1:0:0:0: [sdb] No Caching mode page present
[69018.048613] sd 1:0:0:0: [sdb] Assuming drive cache: write through
[69018.054809] sd 1:0:0:0: [sdb] Attached SCSI disk
[69018.113678] ses 1:0:0:1: Attached Enclosure device
[69018.539242] EXT4-fs (sdb1): mounting ext3 file system using the ext4 subsystem
[69027.691977] EXT4-fs (sdb1): recovery complete
[69027.692637] EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null)
')

[ejblom]

See my post in v3 forum, that will work.