Welcome! Log In Create A New Profile

Advanced

iConnect starting from scratch

Posted by cr2013 
iConnect starting from scratch
December 17, 2014 01:18PM
To make a long story short I have an iConnect in my posession collecting dust. I think at one point I did try running ALARM on it but no longer have the rootfs drive so whatever NAND/uboot changes made are likely all that is intact. At this point I am simply considering grabbing the stock recovery and going back to square 0 and start from scratch. I have been trying to read over this forum as much as I can but am running around in circles trying to figure out where to start. Any simple cliffnotes suggestions on where I need to begin and go to get a basic running Debian install on this thing?

My intent as this point is to replace an old power hungry P4 box which is running as my glorified NAS. The biggest catch here and a problem I do remember running into previously is having multiple drives attached and being able to get it booting off the correct drive every time when they are all connected. Didn't really figure out how to accomplish that one at the time. env variable to have uboot look for a specific UUID?

Thanks guys! Again, willing to read and learn. Just need a starting point though. I do have a working serial adapter wired up and ready to go on that front.
Re: iConnect starting from scratch
December 18, 2014 01:04AM
cr2013,

You can do all that with new u-boot and new Debian rootfs. But the first step is to connect serial console and get the listing of your u-boot envs:

Interrupt serial console at countdown, and then
> printenv

Steps:
1. Try to boot the new Debian rootfs first
2. Update u-boot
3. Modify u-boot envs to boot correct drive in multiple drives configuration.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Re: iConnect starting from scratch
December 18, 2014 07:06AM
Thanks again. That's exactly what I was looking for. I won't have access to work on it until tomorrow morning but I'll definitely give a progress report. Feels like it should be relatively straightforward now.
Re: iConnect starting from scratch
December 20, 2014 06:51AM
Ran into a small wrinkle right off the bat. Checked the uboot envs right off the bat and they seemed relatively unharmed. I have that output attached. Immediately used the iomega imager to go back to stock and start from the beginning. Used the ALARM install script just enough to modify the uboot config to allow usb booting and ignore creating a bootable drive. From there I went through the process in the first thread linked in your signature which seemed simple enough. Took my 2GB flash drive, partitioned it (Only thing I did differently was added a 256MB swap as part #2 at the end of the disk and filled the rest of the space with an Ext3, #1, labelled rootfs. Not sure how much that changes things but am taking a wild guess of not much), and untar'd the rootfs to it. Tried to boot both that alone and going through the zImage creation and both end up at least booting the kernel but not going much farther:

[    2.707616] Waiting 10 sec before mounting root device...
[    2.954152] usb 1-1: new high-speed USB device number 2 using orion-ehci
[    3.104643] usb 1-1: New USB device found, idVendor=058f, idProduct=6254
[    3.111396] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[    3.119508] hub 1-1:1.0: USB hub found
[    3.123386] hub 1-1:1.0: 4 ports detected
[    3.404388] usb 1-1.1: new high-speed USB device number 3 using orion-ehci
[    3.535135] usb 1-1.1: New USB device found, idVendor=1908, idProduct=0222
[    3.542066] usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[    3.549449] usb 1-1.1: Product: USB2.0 Device
[    3.553831] usb 1-1.1: Manufacturer: Generic
[    3.558144] usb 1-1.1: SerialNumber: 20101227120006
[   12.714310] VFS: Cannot open root device "sda1" or unknown-block(0,0): error -6
[   12.721661] Please append a correct "root=" boot option; here are the available partitions:
[   12.730124] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
[   12.738436] CPU: 0 PID: 1 Comm: swapper Not tainted 3.17.0-kirkwood-tld-1 #4
[   12.745552] [<c0014960>] (unwind_backtrace) from [<c00110e0>] (show_stack+0x10/0x14)
[   12.753352] [<c00110e0>] (show_stack) from [<c053a1cc>] (panic+0x80/0x208)
[   12.760273] [<c053a1cc>] (panic) from [<c074f160>] (mount_block_root+0x200/0x248)
[   12.767801] [<c074f160>] (mount_block_root) from [<c074f28c>] (mount_root+0xe4/0x10c)
[   12.775675] [<c074f28c>] (mount_root) from [<c074f3d8>] (prepare_namespace+0x124/0x184)
[   12.783723] [<c074f3d8>] (prepare_namespace) from [<c074ed8c>] (kernel_init_freeable+0x1f8/0x240)
[   12.792645] [<c074ed8c>] (kernel_init_freeable) from [<c0539278>] (kernel_init+0x8/0xe4)
[   12.800780] [<c0539278>] (kernel_init) from [<c000e270>] (ret_from_fork+0x14/0x24)
[   12.808388] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)

The next thing that ran through my head was trying to get the update uBoot installed to see if that got debian booting. All barring the install script works either in the stock iConnect OS or booting ALARM temporarily to do so. But reading that over ended up with two gotchas: 1) Figuring out the flash offsets for the iConnect which just gets a deer in the headlights look from me. And 2) determining if my bad blocks are inside that 1M area I need to worry about. I pulled this from the

root@storage:/# dmesg | grep -i 'bad'
Scanning device for bad blocks
Bad eraseblock 651 at 0x000005160000
Bad eraseblock 1717 at 0x00000d6a0000
Bad eraseblock 1719 at 0x00000d6e0000
Bad eraseblock 2373 at 0x0000128a0000
Bad eraseblock 3077 at 0x0000180a0000
Bad eraseblock 3081 at 0x000018120000
Bad eraseblock 3093 at 0x0000182a0000
Bad eraseblock 3097 at 0x000018320000
Bad eraseblock 3109 at 0x0000184a0000
Bad eraseblock 3113 at 0x000018520000
Bad eraseblock 3117 at 0x0000185a0000
Bad eraseblock 3125 at 0x0000186a0000
Bad eraseblock 3129 at 0x000018720000
UBI: number of bad PEBs:         13
UBI: number of PEBs reserved for bad PEB handling: 39
Attachments:
open | download - uboot.env (2.2 KB)
Re: iConnect starting from scratch
December 20, 2014 04:06PM
1. Booting problem:

Quote

(Only thing I did differently was added a 256MB swap as part #2 at the end of the disk and filled the rest of the space with an Ext3, #1, labelled rootfs. Not sure how much that changes things but am taking a wild guess of not much), and untar'd the rootfs to it.

Of course it did! the error you have below is with mounting rootfs.
[   12.714310] VFS: Cannot open root device "sda1" or unknown-block(0,0): error -6

To boot with stock u-boot, you should use single partition, and label it rootfs.The are quite a few u-boot envs that should be added to ensure you are always booting successfully with stock u-boot and new Debian/Arch kernel. But you got far enough that just using a single partition is going to work.

2. Your bad blocks are way out of 1M, so no problem.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Re: iConnect starting from scratch
December 22, 2014 09:37AM
So this is getting really perplexing then. At this point I am almost certain it is something painfully obvious because I have re-ran the iconnect imager numerous times to reset the uboot envs followed by the ALARM install script just to enable usb booting (which is basically just these lines: https://github.com/igors/iconnect_usb_boot/blob/master/iconnect_install.sh#L223 which I have eventually broke down and started running by hand in uboot rather than running the script every time in the booted iconnect OS) and did some cross comparison between of the stock OS and ALARM trying to figure out if something is not matching. All while I should note that both boot just happily. In fact ALARM boots off the same disk (a USB-microSD adapter and 2GB transcend disk) as I am trying with Debian.

Full procedure I am running to get the disk built all in a Debian x64 VM (Vmware Player with the USB disk directly attached to the guest OS):

Fdisk /dev/sdb, o, n, 1st partition using full disk, w
mkfs.ext2 /dev/sdb1 (tried both ext2 and ext3 with no change)
e2label /dev/sdb1 rootfs
mount /dev/sdb1 /meda/sdb1
cd /media/sdb1
tar -xjf /home/user/Debian-3.17.0-kirkwood-tld-1-rootfs-bodhi.tar.bz2

<insert whole FDT mkimage procedure here, placing iconnect DTB in the right spot>

sync, umount

Tried also modifying the fstab every which way, either /dev/root, /dev/sda1, or even LABEL=rootfs. Even played around with the uboot env's tweaking specifically the root and rootfstype options (hence me doing repeated resets) with no luck.

Uncompressing Linux... done, booting the kernel.
[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Initializing cgroup subsys cpuset
[    0.000000] Initializing cgroup subsys cpu
[    0.000000] Initializing cgroup subsys cpuacct
[    0.000000] Linux version 3.17.0-kirkwood-tld-1 (root@tldDebian) (gcc version 4.6.3 (Debian 4.6.3-14) ) #4 PREEMPT Wed Oct 22 00:55:17 PDT 2014
[    0.000000] CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=0005397f
[    0.000000] CPU: VIVT data cache, VIVT instruction cache
[    0.000000] Machine model: Iomega Iconnect
[    0.000000] Memory policy: Data cache writeback
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 65024
[    0.000000] Kernel command line: console=ttyS0,115200 mtdparts=orion_nand:0xc0000@0x0(uboot),0x20000@0xa0000(env),0x300000@0x100000(zImage),0x300000@0x540000(initrd),0x1f400000@0x980000(boot) root=/dev/sda1 rootdelay=10
[    0.000000] PID hash table entries: 1024 (order: 0, 4096 bytes)
[    0.000000] Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
[    0.000000] Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
[    0.000000] Memory: 248332K/262144K available (5553K kernel code, 358K rwdata, 1892K rodata, 262K init, 302K bss, 13812K reserved)
[    0.000000] Virtual kernel memory layout:
[    0.000000]     vector  : 0xffff0000 - 0xffff1000   (   4 kB)
[    0.000000]     fixmap  : 0xffc00000 - 0xffe00000   (2048 kB)
[    0.000000]     vmalloc : 0xd0800000 - 0xff000000   ( 744 MB)
[    0.000000]     lowmem  : 0xc0000000 - 0xd0000000   ( 256 MB)
[    0.000000]     modules : 0xbf000000 - 0xc0000000   (  16 MB)
[    0.000000]       .text : 0xc0008000 - 0xc074d83c   (7447 kB)
[    0.000000]       .init : 0xc074e000 - 0xc078f90c   ( 263 kB)
[    0.000000]       .data : 0xc0790000 - 0xc07e998c   ( 359 kB)
[    0.000000]        .bss : 0xc07e998c - 0xc08352dc   ( 303 kB)
[    0.000000] Preemptible hierarchical RCU implementation.
[    0.000000] NR_IRQS:16 nr_irqs:16 16
[    0.000016] sched_clock: 32 bits at 200MHz, resolution 5ns, wraps every 21474836475ns
[    0.000402] Console: colour dummy device 80x30
[    0.000434] Calibrating delay loop... 990.41 BogoMIPS (lpj=4952064)
[    0.090110] pid_max: default: 32768 minimum: 301
[    0.090248] Security Framework initialized
[    0.090325] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.090347] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.091156] Initializing cgroup subsys devices
[    0.091193] Initializing cgroup subsys freezer
[    0.091220] Initializing cgroup subsys net_cls
[    0.091244] Initializing cgroup subsys blkio
[    0.091350] CPU: Testing write buffer coherency: ok
[    0.091852] Setting up static identity map for 0x542138 - 0x542190
[    0.092181] mvebu-soc-id: MVEBU SoC ID=0x6281, Rev=0x2
[    0.094774] devtmpfs: initialized
[    0.097519] prandom: seed boundary self test passed
[    0.102444] prandom: 100 self tests passed
[    0.102482] pinctrl core: initialized pinctrl subsystem
[    0.103065] regulator-dummy: no parameters
[    0.108333] NET: Registered protocol family 16
[    0.108812] DMA: preallocated 256 KiB pool for atomic coherent allocations
[    0.110146] cpuidle: using governor ladder
[    0.110175] cpuidle: using governor menu
[    0.110631] Feroceon L2: Enabling L2
[    0.110682] Feroceon L2: Cache support initialised.
[    0.111137] [Firmware Info]: /ocp@f1000000/ethernet-controller@72000/ethernet0-port@0: local-mac-address is not set
[    0.116352] No ATAGs?
[    0.152043] vgaarb: loaded
[    0.152515] usbcore: registered new interface driver usbfs
[    0.152613] usbcore: registered new interface driver hub
[    0.152769] usbcore: registered new device driver usb
[    0.154089] Switched to clocksource orion_clocksource
[    0.200544] NET: Registered protocol family 2
[    0.201713] TCP established hash table entries: 2048 (order: 1, 8192 bytes)
[    0.201758] TCP bind hash table entries: 2048 (order: 1, 8192 bytes)
[    0.201796] TCP: Hash tables configured (established 2048 bind 2048)
[    0.201874] TCP: reno registered
[    0.201891] UDP hash table entries: 256 (order: 0, 4096 bytes)
[    0.201918] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
[    0.202167] NET: Registered protocol family 1
[    0.202566] RPC: Registered named UNIX socket transport module.
[    0.202580] RPC: Registered udp transport module.
[    0.202589] RPC: Registered tcp transport module.
[    0.202598] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    0.202958] Unpacking initramfs...
[    0.202976] Initramfs unpacking failed: junk in compressed archive
[    0.213403] Freeing initrd memory: 3068K (c4501000 - c4800000)
[    0.213532] NetWinder Floating Point Emulator V0.97 (double precision)
[    0.215132] futex hash table entries: 256 (order: -1, 3072 bytes)
[    0.215173] Initialise system trusted keyring
[    0.215294] audit: initializing netlink subsys (disabled)
[    0.215357] audit: type=2000 audit(0.210:1): initialized
[    0.216270] zpool: loaded
[    0.216292] zbud: loaded
[    0.216631] VFS: Disk quotas dquot_6.5.2
[    0.216692] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[    0.217354] NFS: Registering the id_resolver key type
[    0.217417] Key type id_resolver registered
[    0.217428] Key type id_legacy registered
[    0.217462] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
[    0.217482] Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
[    0.217686] jffs2: version 2.2. (NAND) (SUMMARY)  © 2001-2006 Red Hat, Inc.
[    0.218072] msgmni has been set to 491
[    0.218263] Key type big_key registered
[    0.220993] alg: No test for stdrng (krng)
[    0.221125] bounce: pool size: 64 pages
[    0.221198] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
[    0.221218] io scheduler noop registered
[    0.221234] io scheduler deadline registered
[    0.221278] io scheduler cfq registered (default)
[    0.222785] kirkwood-pinctrl f1010000.pin-controller: registered pinctrl driver
[    0.223556] irq: Cannot allocate irq_descs @ IRQ33, assuming pre-allocated
[    0.224037] irq: Cannot allocate irq_descs @ IRQ65, assuming pre-allocated
[    0.225211] mvebu-pcie mbus:pcie-controller: PCI host bridge to bus 0000:00
[    0.225235] pci_bus 0000:00: root bus resource [io  0x1000-0xfffff]
[    0.225251] pci_bus 0000:00: root bus resource [mem 0xe0000000-0xefffffff]
[    0.225266] pci_bus 0000:00: root bus resource [bus 00-ff]
[    0.225640] PCI: bus0: Fast back to back transfers disabled
[    0.225661] pci 0000:00:01.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[    0.226350] PCI: bus1: Fast back to back transfers disabled
[    0.226468] pci 0000:00:01.0: BAR 14: assigned [mem 0xe0000000-0xe00fffff]
[    0.226492] pci 0000:01:00.0: BAR 0: assigned [mem 0xe0000000-0xe000ffff]
[    0.226513] pci 0000:00:01.0: PCI bridge to [bus 01]
[    0.226531] pci 0000:00:01.0:   bridge window [mem 0xe0000000-0xe00fffff]
[    0.226882] mv_xor f1060800.xor: Marvell shared XOR driver
[    0.264186] mv_xor f1060800.xor: Marvell XOR: ( xor cpy )
[    0.304186] mv_xor f1060800.xor: Marvell XOR: ( xor cpy )
[    0.304417] mv_xor f1060900.xor: Marvell shared XOR driver
[    0.344164] mv_xor f1060900.xor: Marvell XOR: ( xor cpy )
[    0.384161] mv_xor f1060900.xor: Marvell XOR: ( xor cpy )
[    0.384690] Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
[    0.386349] console [ttyS0] disabled
[    0.386419] f1012000.serial: ttyS0 at MMIO 0xf1012000 (irq = 27, base_baud = 12500000) is a 16550A
[    1.061017] console [ttyS0] enabled
[    1.066388] nand: Could not find valid ONFI parameter page; aborting
[    1.072808] nand: device found, Manufacturer ID: 0xad, Chip ID: 0xdc
[    1.079230] nand: Hynix NAND 512MiB 3,3V 8-bit
[    1.083697] nand: 512MiB, SLC, page size: 2048, OOB size: 64
[    1.089421] Scanning device for bad blocks
[    1.133604] Bad eraseblock 651 at 0x000005160000
[    1.203495] Bad eraseblock 1717 at 0x00000d6a0000
[    1.208340] Bad eraseblock 1719 at 0x00000d6e0000
[    1.253047] Bad eraseblock 2373 at 0x0000128a0000
[    1.300827] Bad eraseblock 3077 at 0x0000180a0000
[    1.305787] Bad eraseblock 3081 at 0x000018120000
[    1.311215] Bad eraseblock 3093 at 0x0000182a0000
[    1.316182] Bad eraseblock 3097 at 0x000018320000
[    1.321610] Bad eraseblock 3109 at 0x0000184a0000
[    1.326576] Bad eraseblock 3113 at 0x000018520000
[    1.331514] Bad eraseblock 3117 at 0x0000185a0000
[    1.336716] Bad eraseblock 3125 at 0x0000186a0000
[    1.341656] Bad eraseblock 3129 at 0x000018720000
[    1.405516] 5 cmdlinepart partitions found on MTD device orion_nand
[    1.411812] Creating 5 MTD partitions on "orion_nand":
[    1.417003] 0x000000000000-0x0000000c0000 : "uboot"
[    1.422379] 0x0000000a0000-0x0000000c0000 : "env"
[    1.427607] 0x000000100000-0x000000400000 : "zImage"
[    1.433052] 0x000000540000-0x000000840000 : "initrd"
[    1.438523] 0x000000980000-0x00001fd80000 : "boot"
[    1.445806] libphy: Fixed MDIO Bus: probed
[    1.450293] libphy: orion_mdio_bus: probed
[    1.455519] mv643xx_eth: MV-643xx 10/100/1000 ethernet driver version 1.4
[    2.532870] mv643xx_eth_port mv643xx_eth_port.0 eth0: port 0 with MAC address 00:50:43:9a:11:18
[    2.541930] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    2.548530] ehci-pci: EHCI PCI platform driver
[    2.553085] ehci-orion: EHCI orion driver
[    2.557341] orion-ehci f1050000.ehci: EHCI Host Controller
[    2.562882] orion-ehci f1050000.ehci: new USB bus registered, assigned bus number 1
[    2.570824] orion-ehci f1050000.ehci: irq 30, io mem 0xf1050000
[    2.594132] orion-ehci f1050000.ehci: USB 2.0 started, EHCI 1.00
[    2.600391] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[    2.607244] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    2.614525] usb usb1: Product: EHCI Host Controller
[    2.619431] usb usb1: Manufacturer: Linux 3.17.0-kirkwood-tld-1 ehci_hcd
[    2.626183] usb usb1: SerialNumber: f1050000.ehci
[    2.631797] hub 1-0:1.0: USB hub found
[    2.635668] hub 1-0:1.0: 1 port detected
[    2.640691] mousedev: PS/2 mouse device common for all mice
[    2.647122] rtc-mv f1010300.rtc: rtc core: registered f1010300.rtc as rtc0
[    2.654305] i2c /dev entries driver
[    2.661374] hidraw: raw HID events driver (C) Jiri Kosina
[    2.667347] drop_monitor: Initializing network drop monitor service
[    2.673912] TCP: cubic registered
[    2.677325] NET: Registered protocol family 17
[    2.681942] Key type dns_resolver registered
[    2.687126] Loading compiled-in X.509 certificates
[    2.691977] registered taskstats version 1
[    2.697390] rtc-mv f1010300.rtc: setting system clock to 2014-12-22 14:33:35 UTC (1419258815)
[    2.707617] Waiting 10 sec before mounting root device...
[    2.954165] usb 1-1: new high-speed USB device number 2 using orion-ehci
[    3.104594] usb 1-1: New USB device found, idVendor=058f, idProduct=6254
[    3.111352] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[    3.119461] hub 1-1:1.0: USB hub found
[    3.123336] hub 1-1:1.0: 4 ports detected
[    3.404339] usb 1-1.3: new high-speed USB device number 3 using orion-ehci
[    3.547836] usb 1-1.3: New USB device found, idVendor=0b95, idProduct=772a
[    3.554779] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[    3.562147] usb 1-1.3: Product: AX88x72A
[    3.566114] usb 1-1.3: Manufacturer: ASIX Elec. Corp.
[    3.571192] usb 1-1.3: SerialNumber: 000002
[    3.674339] usb 1-1.4: new high-speed USB device number 4 using orion-ehci
[    3.805085] usb 1-1.4: New USB device found, idVendor=1908, idProduct=0222
[    3.812012] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[    3.819395] usb 1-1.4: Product: USB2.0 Device
[    3.823775] usb 1-1.4: Manufacturer: Generic
[    3.828088] usb 1-1.4: SerialNumber: 20101227120006
[   12.714321] VFS: Cannot open root device "sda1" or unknown-block(0,0): error -6
[   12.721670] Please append a correct "root=" boot option; here are the available partitions:
[   12.730132] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
[   12.738444] CPU: 0 PID: 1 Comm: swapper Not tainted 3.17.0-kirkwood-tld-1 #4
[   12.745561] [<c0014960>] (unwind_backtrace) from [<c00110e0>] (show_stack+0x10/0x14)
[   12.753361] [<c00110e0>] (show_stack) from [<c053a1cc>] (panic+0x80/0x208)
[   12.760282] [<c053a1cc>] (panic) from [<c074f160>] (mount_block_root+0x200/0x248)
[   12.767809] [<c074f160>] (mount_block_root) from [<c074f28c>] (mount_root+0xe4/0x10c)
[   12.775684] [<c074f28c>] (mount_root) from [<c074f3d8>] (prepare_namespace+0x124/0x184)
[   12.783732] [<c074f3d8>] (prepare_namespace) from [<c074ed8c>] (kernel_init_freeable+0x1f8/0x240)
[   12.792654] [<c074ed8c>] (kernel_init_freeable) from [<c0539278>] (kernel_init+0x8/0xe4)
[   12.800788] [<c0539278>] (kernel_init) from [<c000e270>] (ret_from_fork+0x14/0x24)
[   12.808397] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
[   79.188140] random: nonblocking pool is initialized

The ONLY thing I think I can really say that MAY have made any progress (as little as it may be in my situation going here) is going by root=LABEL=rootfs I was getting an error of -19 instead of -6 if that means anything.
Re: iConnect starting from scratch
December 22, 2014 03:13PM
>
> Fdisk /dev/sdb, o, n, 1st partition using full
> disk, w
> mkfs.ext2 /dev/sdb1 (tried both ext2 and ext3 with
> no change)
> e2label /dev/sdb1 rootfs
> mount /dev/sdb1 /meda/sdb1
> cd /media/sdb1
> tar -xjf
> /home/user/Debian-3.17.0-kirkwood-tld-1-rootfs-bod
> hi.tar.bz2
> 
> <insert whole FDT mkimage procedure here, placing
> iconnect DTB in the right spot>
> 
> sync, umount

Was the above done as root user, not sudo? if it was, the next thing is: can you post your u-boot envs here? there might be adjustment needed.

And have you tried a different USB drive?

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Re: iConnect starting from scratch
December 23, 2014 03:33AM
Sure, here's the env's:
Marvell>> printenv
loads_echo=0
ipaddr=10.4.50.165
serverip=10.4.50.5
rootpath=/mnt/ARM_FS/
netmask=255.255.255.0
ethprime=egiga0
serverip=192.168.100.70
ipaddr=192.168.100.71
usbstart=usb start
run_diag=yes
console=console=ttyS0,115200 mtdparts=nand_mtd:0xc0000@0(uboot)ro,0x1ff00000@0x100000(root)
CASset=min
MALLOC_len=1
bootargs_root=root=/dev/nfs rw
bootargs_end=:::orion:eth0:none
image_name=uImage
standalone=fsload 0x2000000 $(image_name);setenv bootargs $(console) root=/dev/mtdblock0 rw ip=$(ipaddr):$(serverip)$(bootargs_end) $(mvPhoneConfig); bootm 0x2000000;
ethaddr=00:50:43:9a:11:18
ethmtu=1500
eth1addr=00:50:43:01:11:18
eth1mtu=1500
mvPhoneConfig=mv_phone_config=dev0:fxs,dev1:fxs
mvNetConfig=mv_net_config=(00:11:88:0f:62:81,0:1:2:3),mtu=1500
usb0Mode=host
yuk_ethaddr=00:00:00:EE:51:81
netretry=no
rcvrip=169.254.100.100
loadaddr=0x02000000
autoload=no
uboot_start=0x0
uboot_size=0xc0000
env_start=0xa0000
env_size=0x20000
kernel_start=0x100000
kernel_size=0x300000
initrd_start=0x540000
initrd_size=0x300000
flash_load=run make_boot_args load1 load2 boot
load1=nand read.e 0x2000000 $(kernel_start) $(kernel_size)
load2=nand read.e 0x4500000 $(initrd_start) $(initrd_size)
boot=bootm 0x2000000 0x4500000
nandEcc=1bit
iomega=123
baudrate==15200
bootargs_setenv=bootcmd setenv bootargs console=ttyS0,115200 mtdparts=nand_mtd:0xc0000@0(uboot)ro,0x1ff00000@0x100000(root) root=/dev/nfs rw
bootdelaysetenv=console console=ttyS0,115200
ethact=egiga0
kernel=/boot/uImage
mtdids=nand0=orion_nand
mtdparts=mtdparts=orion_nand:0x80000@0x0(uboot),0x20000@0x80000(uboot_env),-@0xa0000(rootfs)
usb_s=setenv usb_scan_5 setenv usb 0:1; setenv dev sda2
bootargs=console=ttyS0,115200 ramdisk=32768 mtdparts=orion_nand:0xc0000@0x0(uboot),0x20000@0xa0000(env),0x300000@0x100000(zImage),0x300000@0x540000(initrd),0x1f400000@0x980000(boot) root=LABEL=rootfs rootfstype=ext3 rootdelay=10 root=LABEL=rootfs rootfstype=ext2 rootdelay=100xc0000@0x0(uboot),0x20000@0xa0000(env),0x300000@0x100000(zImage),0x300000@0x540000(initrd),0x1f400000@0x980000(boot)
bootc=setenv bootcmd_usb_3 run usb_scan_3;run make_usb_bootargs;ext2load usb $(usb) 0x00080000 /boot/uImage;bootm 0x00080000
make_boot_args=setenv bootargs console=ttyS0,115200 mtdparts=orion_nand:;setenv bootargs $(bootargs)$(uboot_size)@$(uboot_start)(uboot),;setenv bootargs $(bootargs)$(env_size)@$(env_start)(env),;setenv bootargs $(bootargs)$(kernel_size)@$(kernel_start)(zImage),;setenv bootargs $(bootargs)$(initrd_size)@$(initrd_start)(initrd),;setenv bootargs $(bootargs)$(boot_size)@$(boot_start)(boot)
boot_start=0x980000
boot_size=0x1f400000
usb_scan_1=setenv usb 0:1; setenv dev sda1
usb_scan_2=setenv usb 1:1; setenv dev sdb1
usb_scan_3=setenv usb 2:1; setenv dev sdc1
usb_scan_4=setenv usb 3:1; setenv dev sdd1
usb_scan_5=setenv usb 0:1; setenv dev sda2
usb_scan_6=setenv usb 1:1; setenv dev sdb2
usb_scan_7=setenv usb 2:1; setenv dev sdc2
usb_scan_8=setenv usb 3:1; setenv dev sdd2
bootcmd_usb_1=run usb_scan_1;run make_usb_bootargs;ext2load usb $(usb) 0x00800000 /boot/uImage;bootm 0x00800000
bootcmd_usb_2=run usb_scan_2;run make_usb_bootargs;ext2load usb $(usb) 0x00800000 /boot/uImage;bootm 0x00800000
bootcmd_usb_3=run usb_scan_3;run make_usb_bootargs;ext2load usb $(usb) 0x00800000 /boot/uImage;bootm 0x00800000
bootcmd_usb_4=run usb_scan_4;run make_usb_bootargs;ext2load usb $(usb) 0x00800000 /boot/uImage;bootm 0x00800000
bootcmd_usb_5=run usb_scan_5;run make_usb_bootargs;ext2load usb $(usb) 0x00800000 /uImage;bootm 0x00800000
bootcmd_usb_6=run usb_scan_6;run make_usb_bootargs;ext2load usb $(usb) 0x00800000 /uImage;bootm 0x00800000
bootcmd_usb_7=run usb_scan_7;run make_usb_bootargs;ext2load usb $(usb) 0x00800000 /uImage;bootm 0x00800000
bootcmd_usb_8=run usb_scan_8;run make_usb_bootargs;ext2load usb $(usb) 0x00800000 /uImage;bootm 0x00800000
make_usb_bootargs=run make_boot_args;setenv bootargs $(bootargs) root=/dev/$(dev) rootdelay=10
bootcmd_usb=usb start;run bootcmd_usb_1;run bootcmd_usb_2;run bootcmd_usb_3;run bootcmd_usb_4;run bootcmd_usb_5;run bootcmd_usb_6;run bootcmd_usb_7;run bootcmd_usb_8
bootcmd=run bootcmd_usb; run flash_load
arcNumber=2870
stdin=serial
stdout=serial
stderr=serial
mainlineLinux=yes
enaMonExt=no
enaCpuStream=no
enaWrAllo=no
pexMode=RC
disL2Cache=no
setL2CacheWT=yes
disL2Prefetch=yes
enaICPref=yes
enaDCPref=yes
sata_dma_mode=yes
netbsd_en=no
vxworks_en=no
bootdelay=3
disaMvPnp=no
hddPowerCtrl=no
enaAutoRecovery=yes
pcieTune=no

Environment size: 4429/131068 bytes
And I did try another USB drive. This one a U3 Cruzer Micro. Tried both dd'ing from the first and building it from scratch. Same situation.
Re: iConnect starting from scratch
December 23, 2014 04:44AM
cr2013,

The envs look quite ugly :) I know people have set it up this way long time ago to get it working with stock u-boot. Now it is no longer necessary when you install new u-boot.

Back to the problem. This is suspected:
bootargs=console=ttyS0,115200 ramdisk=32768 mtdparts=orion_nand:0xc0000@0x0(uboot),0x20000@0xa0000(env),0x300000@0x100000(zImage),0x300000@0x540000(initrd),0x1f400000@0x980000(boot) root=LABEL=rootfs rootfstype=ext3 rootdelay=10 root=LABEL=rootfs rootfstype=ext2 rootdelay=100xc0000@0x0(uboot),0x20000@0xa0000(env),0x300000@0x100000(zImage),0x300000@0x540000(initrd),0x1f400000@0x980000(boot)

In the middle of the bootargs env, there are extra stuff:
root=LABEL=rootfs rootfstype=ext3 rootdelay=10 root=LABEL=rootfs rootfstype=ext2

Try take out the extra parameters, and use Ext2 for the USB drive (start from a newly formatted ext2, and untar the rootfs as root user).
root=LABEL=rootfs rootfstype=ext2 rootdelay=10

You could also skip all this and install new u-boot (if you can boot to any older rootfs). This is really an extra precaution in case you don't want to install new u-boot.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Re: iConnect starting from scratch
January 07, 2015 12:50PM
Sorry for not getting back sooner. Been busy with holiday travel and such. At this point I think I have possibly bricked the thing. I went ahead and tried to update the U-boot and got no errors. Output was identical in the uboot thread. But for some reason I am now stuck with a dead box. No light, no serial response. Tried UART booting instructions on the long shot it'd work but no dice there.

As an alternative I did pick up a Pogoplug v4 and it has went flawlessly. Updated U-Boot, threw the rootfs on a 20GB SATA disk and booting it off the SATA port and it is fully functioning at this state.

So with that said I do greatly appreciate the help up to this point and sorry to have wasted your time on this. With my luck I probably fat-fingered something somewhere. :p But the v4 at this point seems to be as painless as can be and I'm going to give it a whirl as my replacement NAS. A -LOT- less power consumption than an ancient P4 x86 box.
Re: iConnect starting from scratch
January 08, 2015 04:49AM
Cr2013,

Not at all! Glad you found a good solution. As a NAS, Pogo v4 is good enough. Especially in a Gbit network.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
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: