Welcome! Log In Create A New Profile

Advanced

USB CF adapter fails to read

Posted by metric 
USB CF adapter fails to read
October 14, 2015 01:30AM
I have been using usb CF adapter (14cd:8168 Super Top) and a CF card as my boot drive for a long time on my dockstar (few years) . Recent upgrade to Jessie screwed up the audio so I shutdown the sysem to remove the hardware. The system was up 24x7 for months, just reboots for kernel updates but powered on. Now the U-Boot or the rescue system cannot see the usb adapter or the card. I cannot boot from the adapter. lsusb does not show the hardware on the rescue system either.

I have tried few other cards and the same adapter. They all fail on the dockstar.

The same card in another usb adapter on the dockstar works.

But the adapter and any card works on my desktop and the laptop. The rescue system and the u-boot has not been changed for a long time. What could have gone bad in the dockstar?
Re: USB CF adapter fails to read
October 14, 2015 02:07AM
metric Wrote:
-------------------------------------------------------
> I have been using usb CF adapter (14cd:8168 Super
> Top) and a CF card as my boot drive for a long
> time on my dockstar (few years) . Recent upgrade
> to Jessie screwed up the audio so I shutdown the
> sysem to remove the hardware. The system was up
> 24x7 for months, just reboots for kernel updates
> but powered on. Now the U-Boot or the rescue
> system cannot see the usb adapter or the card. I
> cannot boot from the adapter. lsusb does not show
> the hardware on the rescue system either.
>
> I have tried few other cards and the same
> adapter. They all fail on the dockstar.
>
> The same card in another usb adapter on the
> dockstar works.
>
> But the adapter and any card works on my desktop
> and the laptop. The rescue system and the u-boot
> has not been changed for a long time. What could
> have gone bad in the dockstar?

Do you have netconsole or serial console? what's the boot log look like? without the boot log, we'll be just guessing what the problem is, no way to be sure.

It sounds like the Jessie upgrade might have caused some problem in the USB enumeration. After you've upgraded to jessie, do you run systemd now or do you still have sysvinit?

-bodhi
===========================
Forum Wiki
bodhi's corner
Re: USB CF adapter fails to read
October 18, 2015 05:21PM
Bodhi,

I did a brand new wheezy installation from rescue boot using Jeff's script to a working CF adapter. Then inserted that CF card in the failing adapter, connected the serial console to my dockstar and tried to boot. It failed again. Here is the output. The rescue system does not see the boot CF card/USB adapter as I said before, the failing adapter works on the other systems and my dockstar works with the other adapter. Yes, I can use that as replacement now, but I am trying to understand what is going on. If it was working for last two years, what changed now? I also see

Bad eraseblock 808 at 0x000006500000 Is this of any concern?


U-Boot 2011.12 (Feb 12 2012 - 21:33:07)
Seagate FreeAgent DockStar

SoC:   Kirkwood 88F6281_A0
DRAM:  128 MiB
WARNING: Caches not enabled
NAND:  256 MiB
In:    serial
Out:   serial
Err:   serial
Net:   egiga0
88E1116 Initialized on egiga0
No link on egiga0
Hit any key to stop autoboot:  0 
(Re)start USB...
USB:   Register 10011 NbrPorts 1
USB EHCI 1.00
scanning bus for devices... EHCI timed out on TD - token=0x80008c80
3 USB Device(s) found
       scanning bus for storage devices... 0 Storage Device(s) found
** Block device usb 0 not supported

** Invalid boot device **
Creating 1 MTD partitions on "nand0":
0x000002500000-0x000010000000 : "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: fixable bit-flip detected at PEB 1746
UBI: fixable bit-flip detected at PEB 1749
UBI: attached mtd1 to ubi0
UBI: MTD device name:            "mtd=3"
UBI: MTD device size:            219 MiB
UBI: number of good PEBs:        1751
UBI: number of bad PEBs:         1
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:             1730
UBI: total number of reserved PEBs: 21
UBI: number of PEBs reserved for bad PEB handling: 17
UBI: max/mean erase counter: 8193/29
UBIFS error (pid 0): ubifs_get_sb: cannot open "ubi:rootfs", error -19
Error reading superblock on volume 'ubi:rootfs'!
** Block device usb 0 not supported
** Block device usb 1 not supported
** Block device usb 2 not supported
** Block device usb 3 not supported
** Block device usb 0 not supported
** Block device usb 0 not supported
Wrong Image Format for bootm command
ERROR: can't get kernel image!
stopping USB..

NAND read: device 0 offset 0x100000, size 0x400000
 4194304 bytes read: OK
## Booting kernel from Legacy Image at 00800000 ...
   Image Name:   Linux-2.6.32.18-dockstar
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    3236180 Bytes = 3.1 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux............................................................................................................................................................................................................. done, booting the kernel.
[    0.000000] Initializing cgroup subsys cpuset
[    0.000000] Initializing cgroup subsys cpu
[    0.000000] Linux version 2.6.32.18-dockstar (root@stfu.tcbnet) (gcc version 4.3.5 (Buildroot 2010.08) ) #1 Thu Feb 17 03:09:57 EST 2011
[    0.000000] CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=00053977
[    0.000000] CPU: VIVT data cache, VIVT instruction cache
[    0.000000] Machine: Seagate FreeAgent DockStar
[    0.000000] Memory policy: ECC disabled, Data cache writeback
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 32512
[    0.000000] Kernel command line: console=ttyS0,115200 ubi.mtd=2 root=ubi0:rootfs ro rootfstype=ubifs mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)
[    0.000000] PID hash table entries: 512 (order: -1, 2048 bytes)
[    0.000000] Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
[    0.000000] Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
[    0.000000] Memory: 128MB = 128MB total
[    0.000000] Memory: 122836KB available (5968K code, 708K data, 128K init, 0K highmem)
[    0.000000] SLUB: Genslabs=11, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
[    0.000000] Hierarchical RCU implementation.
[    0.000000] NR_IRQS:114
[    0.000000] Console: colour dummy device 80x30
[   21.474972] Calibrating delay loop... 1192.75 BogoMIPS (lpj=5963776)
[   21.714931] Security Framework initialized
[   21.714953] SELinux:  Disabled at boot.
[   21.714982] Mount-cache hash table entries: 512
[   21.715295] Initializing cgroup subsys ns
[   21.715312] Initializing cgroup subsys cpuacct
[   21.715322] Initializing cgroup subsys devices
[   21.715331] Initializing cgroup subsys freezer
[   21.715339] Initializing cgroup subsys net_cls
[   21.715384] CPU: Testing write buffer coherency: ok
[   21.716188] devtmpfs: initialized
[   21.717928] regulator: core version 0.5
[   21.718155] NET: Registered protocol family 16
[   21.718688] Kirkwood: MV88F6281-A0, TCLK=200000000.
[   21.718702] Feroceon L2: Enabling L2
[   21.718737] Feroceon L2: Cache support initialised.
[   21.721787] bio: create slab <bio-0> at 0
[   21.722063] vgaarb: loaded
[   21.722340] SCSI subsystem initialized
[   21.722590] usbcore: registered new interface driver usbfs
[   21.722650] usbcore: registered new interface driver hub
[   21.722744] usbcore: registered new device driver usb
[   21.723181] Switching to clocksource orion_clocksource
[   21.728500] NET: Registered protocol family 2
[   21.728762] IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
[   21.729578] TCP established hash table entries: 4096 (order: 3, 32768 bytes)
[   21.729677] TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
[   21.729730] TCP: Hash tables configured (established 4096 bind 4096)
[   21.729739] TCP reno registered
[   21.729900] NET: Registered protocol family 1
[   21.730194] RPC: Registered udp transport module.
[   21.730204] RPC: Registered tcp transport module.
[   21.730212] RPC: Registered tcp NFSv4.1 backchannel transport module.
[   21.730353] NetWinder Floating Point Emulator V0.97 (double precision)
[   21.730604] audit: initializing netlink socket (disabled)
[   21.730636] type=2000 audit(0.241:1): initialized
[   21.737418] VFS: Disk quotas dquot_6.5.2
[   21.737676] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[   21.740261] Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
[   21.741868] Registering the dns_resolver key type
[   21.741919] Slow work thread pool: Starting up
[   21.742038] Slow work thread pool: Ready
[   21.742048] JFFS2 version 2.2. (NAND) (SUMMARY)  © 2001-2006 Red Hat, Inc.
[   21.742810] fuse init (API version 7.13)
[   21.743301] SGI XFS with security attributes, large block/inode numbers, no debug enabled
[   21.744836] msgmni has been set to 240
[   21.746924] alg: No test for stdrng (krng)
[   21.747080] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 254)
[   21.747094] io scheduler noop registered
[   21.747101] io scheduler anticipatory registered
[   21.747109] io scheduler deadline registered
[   21.747369] io scheduler cfq registered (default)
[   21.753398] Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
[   21.753863] serial8250.0: ttyS0 at MMIO 0xf1012000 (irq = 33) is a 16550A
[   22.138760] console [ttyS0] enabled
[   22.142845] NAND device: Manufacturer ID: 0x2c, Chip ID: 0xda (Micron NAND 256MiB 3,3V 8-bit)
[   22.151468] Scanning device for bad blocks
[   22.185579] Bad eraseblock 808 at 0x000006500000
[   22.236150] 4 cmdlinepart partitions found on MTD device orion_nand
[   22.242449] Creating 4 MTD partitions on "orion_nand":
[   22.247634] 0x000000000000-0x000000100000 : "u-boot"
[   22.253186] 0x000000100000-0x000000500000 : "uImage"
[   22.258635] 0x000000500000-0x000002500000 : "rootfs"
[   22.264110] 0x000002500000-0x000010000000 : "data"
[   22.269795] UBI: attaching mtd2 to ubi0
[   22.273673] UBI: physical eraseblock size:   131072 bytes (128 KiB)
[   22.279971] UBI: logical eraseblock size:    129024 bytes
[   22.285404] UBI: smallest flash I/O unit:    2048
[   22.290129] UBI: sub-page size:              512
[   22.294777] UBI: VID header offset:          512 (aligned 512)
[   22.300637] UBI: data offset:                2048
[   22.365082] UBI: attached mtd2 to ubi0
[   22.368854] UBI: MTD device name:            "rootfs"
[   22.373949] UBI: MTD device size:            32 MiB
[   22.378846] UBI: number of good PEBs:        256
[   22.383495] UBI: number of bad PEBs:         0
[   22.387959] UBI: max. allowed volumes:       128
[   22.392598] UBI: wear-leveling threshold:    4096
[   22.397332] UBI: number of internal volumes: 1
[   22.401797] UBI: number of user volumes:     1
[   22.406269] UBI: available PEBs:             0
[   22.410736] UBI: total number of reserved PEBs: 256
[   22.415644] UBI: number of PEBs reserved for bad PEB handling: 2
[   22.421679] UBI: max/mean erase counter: 2/0
[   22.425978] UBI: image sequence number: 1653365787
[   22.430800] UBI: background thread "ubi_bgt0d" started, PID 38
[   22.436836] MV-643xx 10/100/1000 ethernet driver version 1.4
[   22.442591] mv643xx_eth smi: probed
[   22.447930] net eth0: port 0 with MAC address 00:10:75:12:34:45
[   22.453976] console [netcon0] enabled
[   22.457658] netconsole: network logging started
[   22.462210] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[   22.468820] orion-ehci orion-ehci.0: Marvell Orion EHCI
[   22.474134] orion-ehci orion-ehci.0: new USB bus registered, assigned bus number 1
[   22.503232] orion-ehci orion-ehci.0: irq 19, io mem 0xf1050000
[   22.523218] orion-ehci orion-ehci.0: USB 2.0 started, EHCI 1.00
[   22.529218] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[   22.536050] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[   22.543317] usb usb1: Product: Marvell Orion EHCI
[   22.548042] usb usb1: Manufacturer: Linux 2.6.32.18-dockstar ehci_hcd
[   22.554521] usb usb1: SerialNumber: orion-ehci.0
[   22.559432] usb usb1: configuration #1 chosen from 1 choice
[   22.565165] hub 1-0:1.0: USB hub found
[   22.568963] hub 1-0:1.0: 1 port detected
[   22.573132] Initializing USB Mass Storage driver...
[   22.578127] usbcore: registered new interface driver usb-storage
[   22.584188] USB Mass Storage support registered.
[   22.589025] mice: PS/2 mouse device common for all mice
[   22.594352] i2c /dev entries driver
[   22.598628] device-mapper: uevent: version 1.0.3
[   22.603674] device-mapper: ioctl: 4.15.0-ioctl (2009-04-01) initialised: dm-devel@redhat.com
[   22.612234] cpuidle: using governor ladder
[   22.616497] cpuidle: using governor menu
[   22.620544] Registered led device: dockstar:green:health
[   22.625968] Registered led device: dockstar:orange:misc
[   22.631276] mv_xor_shared mv_xor_shared.0: Marvell shared XOR driver
[   22.637689] mv_xor_shared mv_xor_shared.1: Marvell shared XOR driver
[   22.683252] mv_xor mv_xor.0: Marvell XOR: ( xor cpy )
[   22.723249] mv_xor mv_xor.1: Marvell XOR: ( xor fill cpy )
[   22.763301] mv_xor mv_xor.2: Marvell XOR: ( xor cpy )
[   22.803247] mv_xor mv_xor.3: Marvell XOR: ( xor fill cpy )
[   22.809059] Netfilter messages via NETLINK v0.30.
[   22.813853] nf_conntrack version 0.5.0 (1921 buckets, 7684 max)
[   22.820292] CONFIG_NF_CT_ACCT is deprecated and will be removed soon. Please use
[   22.827750] nf_conntrack.acct=1 kernel parameter, acct=1 nf_conntrack module option or
[   22.835716] sysctl net.netfilter.nf_conntrack_acct=1 to enable it.
[   22.844253] ip_tables: (C) 2000-2006 Netfilter Core Team
[   22.849637] TCP cubic registered
[   22.852876] NET: Registered protocol family 17
[   22.857738] registered taskstats version 1
[   22.862552] Initalizing network drop monitor service
[   22.867640] md: Waiting for all devices to be available before autodetect
[   22.874478] md: If you don't use raid, use raid=noautodetect
[   22.880549] md: Autodetecting RAID arrays.
[   22.884688] md: Scanned 0 and added 0 devices.
[   22.889148] md: autorun ...
[   22.891948] md: ... autorun DONE.
[   22.895310] usb 1-1: new high speed USB device using orion-ehci and address 2
[   23.030437] UBIFS: mounted UBI device 0, volume 0, name "rootfs"
[   23.036494] UBIFS: mounted read-only
[   23.040088] UBIFS: file system size:   30836736 bytes (30114 KiB, 29 MiB, 239 LEBs)
[   23.047788] UBIFS: journal size:       9033728 bytes (8822 KiB, 8 MiB, 71 LEBs)
[   23.055136] UBIFS: media format:       w4/r0 (latest is w4/r0)
[   23.060995] UBIFS: default compressor: lzo
[   23.065125] UBIFS: reserved for root:  0 bytes (0 KiB)
[   23.070970] VFS: Mounted root (ubifs filesystem) readonly on device 0:16.
[   23.077868] Freeing init memory: 128K
[   23.096639] usb 1-1: New USB device found, idVendor=05e3, idProduct=0608
[   23.103398] usb 1-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[   23.110570] usb 1-1: Product: USB2.0 Hub
[   23.131460] usb 1-1: configuration #1 chosen from 1 choice
INIT: [   23.144140] hub 1-1:1.0: USB hub found
[   23.148618] hub 1-1:1.0: 4 ports detected
version 2.86 booting
mdev: /sys/class: No such file or directory
Starting heartbeat LED...
Populating /dev using udev: [   23.433557] usb 1-1.4: new full speed USB device using orion-ehci and address 3
done
Initializing random number generator... read-only file system detected...done
Starting network...
Starting Network Interface Plugging Daemon:[   23.534284] usb 1-1.4: device descriptor read/64, error -32
 eth0.
Starting sshd: OK
INIT: Entering runleve[   23.723542] usb 1-1.4: device descriptor read/64, error -32
l: 2
[   23.913530] usb 1-1.4: new full speed USB device using orion-ehci and address 4
[   23.993526] usb 1-1.4: device descriptor read/64, error -32
[   24.183524] usb 1-1.4: device descriptor read/64, error -32
[   24.373526] usb 1-1.4: new full speed USB device using orion-ehci and address 5


          Jeff Doozan's
Dockstar/Pogoplug Recovery System

rescue login: [   24.793215] usb 1-1.4: device not accepting address 5, error -32
[   24.873527] usb 1-1.4: new full speed USB device using orion-ehci and address 6
[   25.293214] usb 1-1.4: device not accepting address 6, error -32
[   25.299681] hub 1-1:1.0: unable to enumerate USB device on port 4

Re: USB CF adapter fails to read
October 18, 2015 07:21PM
There was no change in your u-boot so that's not the problem. But apparently the jessie upgrade afected the file system. If you have a backup then just restore it. Otherwise, consider upgrade u-boot so it can be more reliably detecting the adapter.

You also did not say if you have upgrade to jessie fully by changing apt sources and which init system it supposes to boot now?

-bodhi
===========================
Forum Wiki
bodhi's corner
Re: USB CF adapter fails to read
October 20, 2015 09:28AM
I did the upgrade by changing apt sources. I followed your instructions to revert systemd back to init. But this could be a red herring. I used another CF card and did a brand new install (on a new CF card reader) using Jeff's script from http://projects.doozan.com/debian/kirkwood.debian-wheezy.sh This time I did not upgrade to Jessie. This new install also fails with the suspect CF card reader but works on a new CF card reader. Is it possible that the upgrade somehow change the bootenv or uboot? I will try to upgrade the uboot but what about the Bad eraseblock 808 at 0x000006500000, Is this of any concern?

I have industrial CF cards with hardware error correction. I prefer to use those as boot drives. Very few multi-card readers can be used as USB boot devices using CF on a dockstar. (It is not a first drive for most of them). Hence I am trying to keep this one alive.
Re: USB CF adapter fails to read
October 20, 2015 11:20PM
metric,

> This new install also fails with the suspect CF
> card reader but works on a new CF card reader.

The reader could go bad any time.

> it possible that the upgrade somehow change the
> bootenv or uboot?

No. Kernel update does not change u-boot env.

> I will try to upgrade the uboot
> but what about the Bad eraseblock 808 at
> 0x000006500000, Is this of any concern?
>

No. The bad block is not in u-boot area.

-bodhi
===========================
Forum Wiki
bodhi's corner
Re: USB CF adapter fails to read
October 21, 2015 12:45AM
Good to know the bad block is not in U-boot. I will update the uboot now.

I understand that electronics can go bad any time but the same supposedly bad reader works fine in two different PCs, a desktop and a laptop. Just the dockstar has stopped reading it. Now I am suspecting that the there is some newly introduced low resistance in the reader circuit (not exactly a short but close to it, may be a bad capacitor) and the dockstar is not able to provide the required power but the desktop or the laptop can.
Re: USB CF adapter fails to read
October 21, 2015 12:23PM
metric,

> the dockstar has stopped reading it. Now I am
> suspecting that the there is some newly introduced
> low resistance in the reader circuit (not exactly
> a short but close to it, may be a bad capacitor)
> and the dockstar is not able to provide the
> required power but the desktop or the laptop can.

Please try the new u-boot usb_ready_retry env. It will allow a longer period (as long as you need) to wait for the reader to initialize. For certain HDDs such as WD USB drives, the period need to be set to some high number such as 30 seconds. The same would be apply to your reader, set it to a really long interval such as 60 seconds and see if it will help.

-bodhi
===========================
Forum Wiki
bodhi's corner
Author:

Your Email:


Subject:


Spam prevention:
Please, enter the code that you see below in the input field. This is for blocking bots that try to post this form automatically. If the code is hard to read, then just try to guess it right. If you enter the wrong code, a new image is created and you get another chance to enter it right.
Message: