Welcome! Log In Create A New Profile

Advanced

Do I have the correct uBoot installed?

Posted by jfharper 
Do I have the correct uBoot installed?
September 04, 2014 05:17PM
Using a GoFlex Home base, I ran this procedure:
cd /tmp
wget http://projects.doozan.com/uboot/install_uboot_mtd0.sh
chmod +x install_uboot_mtd0.sh
./install_uboot_mtd0.sh
I have a USB stick plugged in to the base with ArchLinux installed. I can boot and login via putty from a Windows machine.
The following command gives this output:
grep -a --null-data U-Boot /dev/mtd0ro
U-Boot 2011.12 (Apr 18 2012 - 23:08:20)
Seagate GoFlexNetU-Boot
** Invalid partition type "%.32s" (expect "U-Boot")
U-Boot BUG at %s:%d!
I've been trying some things in the meantime, trying to see if I can get uBoot back to original so I can flash OEM firmware back on it.
I tried this:
wget http://goflex.scottn.us/uboot-mtd0-orig-goflexhome.kwb
flash_erase /dev/mtd0 0 4
nandwrite /dev/mtd0 uboot-mtd0-orig-goflexhome.kwb
But now I'm lost and don't know what I got.

Is the above uBoot the one I got from Jeffs tutorial? Also, did I fail to put the kernal on the device...I did Jeff's tutorial wrong, and only did the bootloader. Should I try putting the kernal on the device, unplugging the USB stick and try to get th resuce system loaded so I can boot to device instead of USB stick...or does that not matter?
Re: Do I have the correct uBoot installed?
September 04, 2014 06:08PM
jfharper,

Have you rebooted? or still in Arch?

> flash_erase /dev/mtd0 0 4
> nandwrite /dev/mtd0
> uboot-mtd0-orig-goflexhome.kwb
If your above flashing of the original U-Boot was successful, then you're back to stock upon reboot. What the ouput of these comands look like? you can post the log here.

Quote

> Is the above uBoot the one I got from Jeffs
> tutorial?

No, iirc, some user hosted the original image making it available for people looking for it.

Quote

> Should I try putting the
> kernal on the device, unplugging the USB stick and
> try to get th resuce system loaded so I can boot
> to device instead of USB stick...or does that not
> matter?

Because it's back to stock FW already (presumably you have rebooted), you can follow Arch installation instruction to SSH back into the box and run the installation procedure.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Re: Do I have the correct uBoot installed?
September 04, 2014 06:42PM
Hi bodhi,

Thanks for your reply. I warm rebooted with arch usb plugged in and was able to login via putty. I also tried power off, then unplug usb stick and powering back on...I got a green blinking followed by red blinking. This would continue cycling...so I powered off. I tried the OEM firmware instructions to load firmware to USB stick and power on holding the reset button, but the above green blinking then red blinking happens. So I plugged ARchlinux stick back in and could login via putty again.

My assumption is I don't have a filesystem on the GF base, so the red blinking occurs...is it looking fo boot files and cannot find them?

Here is my output

flash_erase /dev/mtd0 0 4
flash_erase: Skipping bad block at 00000000
flash_erase: Skipping bad block at 00020000
flash_erase: Skipping bad block at 00040000
flash_erase: Skipping bad block at 00060000
Erasing 128 Kibyte @ 60000 -- 100 % complete

nandwrite /dev/mtd0 uboot-mtd0-orig-goflexhome.kwb

Writing data to block 0 at offset 0x0
Bad block at 0, 1 block(s) from 0 will be skipped
Writing data to block 1 at offset 0x20000
Bad block at 20000, 1 block(s) from 20000 will be skipped
Writing data to block 2 at offset 0x40000
Bad block at 40000, 1 block(s) from 40000 will be skipped
Writing data to block 3 at offset 0x60000
Bad block at 60000, 1 block(s) from 60000 will be skipped
Writing data to block 4 at offset 0x80000
Bad block at 80000, 1 block(s) from 80000 will be skipped
Writing data to block 5 at offset 0xa0000
Bad block at a0000, 1 block(s) from a0000 will be skipped
Writing data to block 6 at offset 0xc0000
Bad block at c0000, 1 block(s) from c0000 will be skipped
Writing data to block 7 at offset 0xe0000
Bad block at e0000, 1 block(s) from e0000 will be skipped
Writing data to block 8 at offset 0x100000
libmtd: error!: bad eraseblock number 8, mtd0 has 8 eraseblocks
nandwrite: error!: /dev/mtd0: MTD get bad block failed
           error 22 (Invalid argument)
nandwrite: error!: Data was only partially written due to error
           error 22 (Invalid argument)

Re: Do I have the correct uBoot installed?
September 04, 2014 08:33PM
@jfharper,

You're lucky the flashing did not mess up mtd0 too badly:) you got 4 bad blocks on mtd0 !!! There is no space left for envs. For now, you can boot into Arch, this is the best you can hope for. Don't try anything else, it might brick it for good :)

Let me think about it a bit and get back to you.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Re: Do I have the correct uBoot installed?
September 04, 2014 10:20PM
@jfharper,

Quote

My assumption is I don't have a filesystem on the GF base, so the red blinking occurs...is it looking fo boot files and cannot find them?

No, the blinking red in this case means your envs are not define properly (due to bad blocks). The end result is, yes, u-boot could not find the boot files, but likely not because they are not there, it probably just searching in the wrong place.

Please post your output of
dmesg
fw_printenv
cat /proc/mtd
cat /etc/fw_env.config

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Re: Do I have the correct uBoot installed?
September 05, 2014 12:29PM
Hi bodhi,
I'm trying to output dmesg, but it is quite long...I'm trying to see if I can output to a file and post that, or was there something specific in the dmesg output you were looking for that I could reduce the output to?

EDIT: OK, here is what I have so far...
dmesg

[    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.15.8-1-ARCH (nobody@root-armv5-copy) (gcc version 4.8.2 20131219 (prerelease) (GCC) ) #1 PREEMPT Wed Aug 6 03:20:19 MDT 2014
[    0.000000] CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=00053977
[    0.000000] CPU: VIVT data cache, VIVT instruction cache
[    0.000000] Machine: Marvell SheevaPlug Reference Board
[    0.000000] Memory policy: Data cache writeback
[    0.000000] On node 0 totalpages: 32768
[    0.000000] free_area_init_node: node 0, pgdat c07aba5c, node_mem_map c7efb000
[    0.000000]   Normal zone: 256 pages used for memmap
[    0.000000]   Normal zone: 0 pages reserved
[    0.000000]   Normal zone: 32768 pages, LIFO batch:7
[    0.000000] pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768
[    0.000000] pcpu-alloc: [0] 0
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 32512
[    0.000000] Kernel command line: console=ttyS0,115200 root=/dev/sda1 rootdelay=10 rootfstype=ext2 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: 121192K/131072K available (5547K kernel code, 341K rwdata, 1700K rodata, 260K init, 833K bss, 9880K reserved)
[    0.000000] Virtual kernel memory layout:
    vector  : 0xffff0000 - 0xffff1000   (   4 kB)
    fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
    vmalloc : 0xc8800000 - 0xff000000   ( 872 MB)
    lowmem  : 0xc0000000 - 0xc8000000   ( 128 MB)
    modules : 0xbf000000 - 0xc0000000   (  16 MB)
      .text : 0xc0008000 - 0xc071bf40   (7248 kB)
      .init : 0xc071c000 - 0xc075d364   ( 261 kB)
      .data : 0xc075e000 - 0xc07b35dc   ( 342 kB)
       .bss : 0xc07b35dc - 0xc0883b2c   ( 834 kB)
[    0.000000] SLUB: HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
[    0.000000] Preemptible hierarchical RCU implementation.
[    0.000000] NR_IRQS:114
[    0.000011] sched_clock: 32 bits at 200MHz, resolution 5ns, wraps every 21474836475ns
[    4.186029] Console: colour dummy device 80x30
[    4.186055] Calibrating delay loop... 1191.11 BogoMIPS (lpj=5955584)
[    4.275932] pid_max: default: 32768 minimum: 301
[    4.276015] Security Framework initialized
[    4.276041] AppArmor: AppArmor disabled by boot time parameter
[    4.276092] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    4.276109] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    4.276731] Initializing cgroup subsys devices
[    4.276756] Initializing cgroup subsys freezer
[    4.276770] Initializing cgroup subsys net_cls
[    4.276781] Initializing cgroup subsys blkio
[    4.276791] Initializing cgroup subsys bfqio
[    4.276802] Initializing cgroup subsys perf_event
[    4.276816] Initializing cgroup subsys net_prio
[    4.276894] CPU: Testing write buffer coherency: ok
[    4.277282] Setting up static identity map for 0x5470f8 - 0x547150
[    4.279056] devtmpfs: initialized
[    4.282375] pinctrl core: initialized pinctrl subsystem
[    4.282711] NET: Registered protocol family 16
[    4.283143] DMA: preallocated 256 KiB pool for atomic coherent allocations
[    4.284126] cpuidle: using governor ladder
[    4.284145] cpuidle: using governor menu
[    4.284272] Kirkwood: MV88F6281-A1, TCLK=200000000.
[    4.284292] Feroceon L2: Enabling L2
[    4.284331] Feroceon L2: Cache support initialised.
[    4.285033] initial MPP regs: 01111111 11113322 00001111 00100000 00000000 00000000 00000000
[    4.285061]   final MPP regs: 01111111 11113322 00001111 00000000 00000000 00000000 00000000
[    4.294710] vgaarb: loaded
[    4.295034] SCSI subsystem initialized
[    4.295196] libata version 3.00 loaded.
[    4.295504] usbcore: registered new interface driver usbfs
[    4.295580] usbcore: registered new interface driver hub
[    4.295694] usbcore: registered new device driver usb
[    4.295837] pps_core: LinuxPPS API ver. 1 registered
[    4.295847] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[    4.295902] PTP clock support registered
[    4.296794] Switched to clocksource orion_clocksource
[    4.316453] FS-Cache: Loaded
[    4.329414] NET: Registered protocol family 2
[    4.330044] TCP established hash table entries: 1024 (order: 0, 4096 bytes)
[    4.330068] TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
[    4.330088] TCP: Hash tables configured (established 1024 bind 1024)
[    4.330157] TCP: reno registered
[    4.330169] UDP hash table entries: 256 (order: 0, 4096 bytes)
[    4.330190] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
[    4.330367] NET: Registered protocol family 1
[    4.330404] PCI: CLS 0 bytes, default 32
[    4.331754] futex hash table entries: 256 (order: -1, 3072 bytes)
[    4.331806] audit: initializing netlink subsys (disabled)
[    4.331868] audit: type=2000 audit(0.140:1): initialized
[    4.441742] VFS: Disk quotas dquot_6.5.2
[    4.442018] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[    4.444208] jffs2: version 2.2. (NAND) \xffffffc2\xffffffa9 2001-2006 Red Hat, Inc.
[    4.446003] aufs 3.15-20140804
[    4.446027] msgmni has been set to 236
[    4.447876] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 250)
[    4.447891] io scheduler noop registered
[    4.447898] io scheduler deadline registered
[    4.448328] io scheduler cfq registered
[    4.448367] io scheduler bfq registered (default)
[    4.448375] BFQ I/O-scheduler version: v7r5
[    4.448542] mv_xor mv_xor.0: Marvell shared XOR driver
[    4.486873] mv_xor mv_xor.0: Marvell XOR: ( xor cpy )
[    4.526865] mv_xor mv_xor.0: Marvell XOR: ( xor cpy )
[    4.527068] mv_xor mv_xor.1: Marvell shared XOR driver
[    4.566871] mv_xor mv_xor.1: Marvell XOR: ( xor cpy )
[    4.606871] mv_xor mv_xor.1: Marvell XOR: ( xor cpy )
[    4.612370] Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
[    4.613420] console [ttyS0] disabled
[    4.633473] serial8250.0: ttyS0 at MMIO 0xf1012000 (irq = 33, base_baud = 12500000) is a 16550A
[    5.151862] console [ttyS0] enabled
[    5.164600] brd: module loaded
[    5.172316] loop: module loaded
[    5.176580] nand: device found, Manufacturer ID: 0x98, Chip ID: 0xda
[    5.182997] nand: Toshiba NAND 256MiB 3,3V 8-bit
[    5.187652] nand: 256MiB, SLC, page size: 2048, OOB size: 64
[    5.193349] Scanning device for bad blocks
[    5.197563] Bad eraseblock 0 at 0x000000000000
[    5.202061] Bad eraseblock 1 at 0x000000020000
[    5.206560] Bad eraseblock 2 at 0x000000040000
[    5.211114] Bad eraseblock 3 at 0x000000060000
[    5.215611] Bad eraseblock 4 at 0x000000080000
[    5.220125] Bad eraseblock 5 at 0x0000000a0000
[    5.224628] Bad eraseblock 6 at 0x0000000c0000
[    5.229179] Bad eraseblock 7 at 0x0000000e0000
[    5.233679] Bad eraseblock 8 at 0x000000100000
...and so on...
[   14.861728] Bad eraseblock 2046 at 0x00000ffc0000
[   14.866489] Bad eraseblock 2047 at 0x00000ffe0000
[   14.871243] 4 cmdlinepart partitions found on MTD device orion_nand
[   14.877549] Creating 4 MTD partitions on "orion_nand":
[   14.882711] 0x000000000000-0x000000100000 : "u-boot"
[   14.888172] 0x000000100000-0x000000500000 : "uImage"
[   14.893564] 0x000000500000-0x000002500000 : "rootfs"
[   14.898985] 0x000002500000-0x000010000000 : "data"
[   14.911211] libphy: orion_mdio_bus: probed
[   14.915416] mv643xx_eth: MV-643xx 10/100/1000 ethernet driver version 1.4
[   15.997717] mv643xx_eth_port mv643xx_eth_port.0 eth0: port 0 with MAC address 02:50:43:34:c3:f3
[   16.006586] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[   16.013163] ehci-pci: EHCI PCI platform driver
[   16.017717] ehci-orion: EHCI orion driver
[   16.021818] orion-ehci orion-ehci.0: EHCI Host Controller
[   16.027285] orion-ehci orion-ehci.0: new USB bus registered, assigned bus number 1
[   16.035087] orion-ehci orion-ehci.0: irq 19, io mem 0xf1050000
[   16.056827] orion-ehci orion-ehci.0: USB 2.0 started, EHCI 1.00
[   16.063716] hub 1-0:1.0: USB hub found
[   16.067555] hub 1-0:1.0: 1 port detected
[   16.072223] usbcore: registered new interface driver usb-storage
[   16.078737] mousedev: PS/2 mouse device common for all mice
[   16.084737] rtc-mv rtc-mv: rtc core: registered rtc-mv as rtc0
[   16.090744] i2c /dev entries driver
[   16.094761] orion_wdt: Initial timeout 21 sec
[   16.099545] sdhci: Secure Digital Host Controller Interface driver
[   16.105753] sdhci: Copyright(c) Pierre Ossman
[   16.110212] mvsdio mvsdio: no pins associated
[   16.146828] mvsdio mvsdio: lacking card detect (fall back to polling)
[   16.153371] sdhci-pltfm: SDHCI platform and OF driver helper
[   16.162779] ledtrig-cpu: registered to indicate activity on CPUs
[   16.169050] usbcore: registered new interface driver r8712u
[   16.174824] gre: GRE over IPv4 demultiplexor driver
[   16.179779] TCP: cubic registered
[   16.183130] NET: Registered protocol family 17
[   16.187749] Key type dns_resolver registered
[   16.192801] registered taskstats version 1
[   16.199193] console [netcon0] enabled
[   16.202877] netconsole: network logging started
[   16.207552] rtc-mv rtc-mv: setting system clock to 2014-09-05 16:42:29 UTC (1409935349)
[   16.216608] Waiting 10 sec before mounting root device...
[   16.386850] usb 1-1: new high-speed USB device number 2 using orion-ehci
[   16.538705] usb-storage 1-1:1.0: USB Mass Storage device detected
[   16.545109] scsi0 : usb-storage 1-1:1.0
[   17.547698] scsi 0:0:0:0: Direct-Access     SanDisk  U3 Cruzer Micro  8.02 PQ: 0 ANSI: 0 CCS
[   17.557519] sd 0:0:0:0: [sda] 15695871 512-byte logical blocks: (8.03 GB/7.48 GiB)
[   17.565237] sd 0:0:0:0: Attached scsi generic sg0 type 0
[   17.570882] sd 0:0:0:0: [sda] Write Protect is off
[   17.575710] sd 0:0:0:0: [sda] Mode Sense: 45 00 00 08
[   17.576195] sd 0:0:0:0: [sda] No Caching mode page found
[   17.581571] sd 0:0:0:0: [sda] Assuming drive cache: write through
[   17.594312]  sda: sda1 sda2
[   17.600127] sd 0:0:0:0: [sda] Attached SCSI removable disk
[   26.230382] EXT2-fs (sda1): warning: mounting ext3 filesystem as ext2
[   26.237905] VFS: Mounted root (ext2 filesystem) on device 8:1.
[   26.245529] devtmpfs: mounted
[   26.249352] Freeing unused kernel memory: 260K (c071c000 - c075d000)
[   26.435968] random: systemd urandom read with 45 bits of entropy available
[   26.450456] systemd[1]: systemd 215 running in system mode. (+PAM -AUDIT -SELINUX -IMA -SYSVINIT +LIBCRYPTSETUP +GCRYPT +ACL +XZ +SECCOMP -APPARMOR)
[   26.464223] systemd[1]: Detected architecture 'arm'.
[   26.525438] systemd[1]: Inserted module 'autofs4'
[   26.566690] NET: Registered protocol family 10
[   26.572309] systemd[1]: Inserted module 'ipv6'
[   26.579239] systemd[1]: Set hostname to <alarm>.
[   26.969652] systemd[1]: Cannot add dependency job for unit display-manager.service, ignoring: Unit display-manager.service failed to load: No such file or directory.
[   26.987343] systemd[1]: Expecting device dev-ttyS0.device...
[   27.016973] systemd[1]: Starting Forward Password Requests to Wall Directory Watch.
[   27.025005] systemd[1]: Started Forward Password Requests to Wall Directory Watch.
[   27.032744] systemd[1]: Starting Remote File Systems.
[   27.056937] systemd[1]: Reached target Remote File Systems.
[   27.062681] systemd[1]: Starting Dispatch Password Requests to Console Directory Watch.
[   27.071003] systemd[1]: Started Dispatch Password Requests to Console Directory Watch.
[   27.079096] systemd[1]: Starting Paths.
[   27.096936] systemd[1]: Reached target Paths.
[   27.101413] systemd[1]: Starting Encrypted Volumes.
[   27.126934] systemd[1]: Reached target Encrypted Volumes.
[   27.132525] systemd[1]: Starting Arbitrary Executable File Formats File System Automount Point.
[   27.166942] systemd[1]: Set up automount Arbitrary Executable File Formats File System Automount Point.
[   27.176503] systemd[1]: Starting Swap.
[   27.196935] systemd[1]: Reached target Swap.
[   27.201316] systemd[1]: Starting Root Slice.
[   27.246977] systemd[1]: Created slice Root Slice.
[   27.251813] systemd[1]: Starting User and Session Slice.
[   27.276952] systemd[1]: Created slice User and Session Slice.
[   27.282830] systemd[1]: Starting Delayed Shutdown Socket.
[   27.306943] systemd[1]: Listening on Delayed Shutdown Socket.
[   27.312815] systemd[1]: Starting Device-mapper event daemon FIFOs.
[   27.336940] systemd[1]: Listening on Device-mapper event daemon FIFOs.
[   27.343594] systemd[1]: Starting /dev/initctl Compatibility Named Pipe.
[   27.366939] systemd[1]: Listening on /dev/initctl Compatibility Named Pipe.
[   27.374027] systemd[1]: Starting Journal Socket (/dev/log).
[   27.396941] systemd[1]: Listening on Journal Socket (/dev/log).
[   27.403007] systemd[1]: Starting udev Control Socket.
[   27.426940] systemd[1]: Listening on udev Control Socket.
[   27.432487] systemd[1]: Starting udev Kernel Socket.
[   27.456938] systemd[1]: Listening on udev Kernel Socket.
[   27.462371] systemd[1]: Starting LVM2 metadata daemon socket.
[   27.486940] systemd[1]: Listening on LVM2 metadata daemon socket.
[   27.493172] systemd[1]: Starting Journal Socket.
[   27.516940] systemd[1]: Listening on Journal Socket.
[   27.522089] systemd[1]: Starting System Slice.
[   27.546949] systemd[1]: Created slice System Slice.
[   27.551974] systemd[1]: Starting system-getty.slice.
[   27.576952] systemd[1]: Created slice system-getty.slice.
[   27.582475] systemd[1]: Starting system-serial\x2dgetty.slice.
[   27.606952] systemd[1]: Created slice system-serial\x2dgetty.slice.
[   27.616654] systemd[1]: Started Set Up Additional Binary Formats.
[   27.623288] systemd[1]: Starting Create list of required static device nodes for the current kernel...
[   27.660057] systemd[1]: Starting udev Coldplug all Devices...
[   27.690597] systemd[1]: Mounting Debug File System...
[   27.708003] systemd[1]: Mounted Huge Pages File System.
[   27.720096] systemd[1]: Starting Setup Virtual Console...
[   27.761595] systemd[1]: Started Load Kernel Modules.
[   27.771747] systemd[1]: Mounted Configuration File System.
[   27.777709] systemd[1]: Starting Apply Kernel Variables...
[   27.810391] systemd[1]: Mounted FUSE Control File System.
[   27.816053] systemd[1]: Mounting POSIX Message Queue File System...
[   27.846763] systemd[1]: Starting Journal Service...
[   27.907021] systemd[1]: Started Journal Service.
[   29.810106] random: nonblocking pool is initialized
[   29.848726] systemd-journald[70]: Received request to flush runtime journal from PID 1
[   37.785040] systemd-udevd[98]: starting version 215
[   42.083745] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[   44.578348] mv643xx_eth_port mv643xx_eth_port.0 eth0: link up, 1000 Mb/s, full duplex, flow control disabled
[   44.589276] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[  742.681227] __nand_correct_data: uncorrectable ECC error
[  742.686416] __nand_correct_data: uncorrectable ECC error
[  742.693283] __nand_correct_data: uncorrectable ECC error
[  742.697967] __nand_correct_data: uncorrectable ECC error
[  742.704200] __nand_correct_data: uncorrectable ECC error
[  742.708111] __nand_correct_data: uncorrectable ECC error
...and so on...
[  749.220028] __nand_correct_data: uncorrectable ECC error
[  749.225386] __nand_correct_data: uncorrectable ECC error
[ 1783.323672] systemd-journald[70]: Received SIGTERM from PID 1 (systemd).
[ 1789.120618] systemd-journald[243]: Received request to flush runtime journal from PID 1

fw_printenv

command not found
I googled how to get this installed, and found that I need to reinstall the install_uboot_mtd0.sh or somethin like that? I did not do that because I didn't want to mess anything up. Let me know if that is OK and I'll do it.

cat /proc/mtd

dev:    size   erasesize  name
mtd0: 00100000 00020000 "u-boot"
mtd1: 00400000 00020000 "uImage"
mtd2: 02000000 00020000 "rootfs"
mtd3: 0db00000 00020000 "data"

cat /etc/fw_env.config

cat: /etc/fw_env.config: No such file or directory
is this also setup after installing the uboot file again mentioned above?



Edited 1 time(s). Last edit at 09/05/2014 01:14PM by jfharper.
Re: Do I have the correct uBoot installed?
September 05, 2014 04:04PM
Very puzzled, your entire mtd0 is bad.

I'm looking for this section:

[    5.197563] Bad eraseblock 0 at 0x000000000000
[    5.202061] Bad eraseblock 1 at 0x000000020000
[    5.206560] Bad eraseblock 2 at 0x000000040000
[    5.211114] Bad eraseblock 3 at 0x000000060000
[    5.215611] Bad eraseblock 4 at 0x000000080000
[    5.220125] Bad eraseblock 5 at 0x0000000a0000
[    5.224628] Bad eraseblock 6 at 0x0000000c0000
[    5.229179] Bad eraseblock 7 at 0x0000000e0000
[    5.233679] Bad eraseblock 8 at 0x000000100000

...and so on...

[   14.861728] Bad eraseblock 2046 at 0x00000ffc0000
[   14.866489] Bad eraseblock 2047 at 0x00000ffe0000

…and so on… you meant there are more bad blocks in that listing? if so, your entire NAND might be bad. But I would doubt that because you still can boot, meaning u-boot was loaded successfully :)

And do you keep the log of the installation? I want to see how the u-boot image flashing to NAND was done, and what the errors look like.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Re: Do I have the correct uBoot installed?
September 05, 2014 05:24PM
Yes, there were alot more numbers in the ...and so on... section...pages of numbers.

Was there a log generated automatically? If so, I could try and find it, otherwise I didn't specifically make a log of the install...I do remember something about uBoot was installed successfully after this command.

./install_uboot_mtd0.sh
Re: Do I have the correct uBoot installed?
September 05, 2014 05:42PM
jfharper,

No, there is no log from the install script. Usually we just copy/paste the screen to a text file. Without that log, I could not figure out when your entire mtd0 went bad! So my suggestion is you should keep this U-boot and continue using Arch rootfs. That would be the easiest and safest way.

If you really want to install newer u-boot, then I would get a serial console connected first. Someting must have happened for the entire first 8 blocks to be marked as bad like that.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Re: Do I have the correct uBoot installed?
September 05, 2014 06:25PM
Is there anyway to reset or fix the bad blocks?
Re: Do I have the correct uBoot installed?
September 05, 2014 06:30PM
jfharper Wrote:
-------------------------------------------------------
> Is there anyway to reset or fix the bad blocks?

Not without serial console. I've heard of cases when people scrubbing and let the HW recollect bad blocks. But that might make things worse. Currently you can boot into Arch Linux, and that's is pretty decent given that many blocks were marked as bad.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Re: Do I have the correct uBoot installed?
September 05, 2014 06:40PM
Yeah, it works as a linux box right now...I'm tempted to keep messing with it, just to see if I can get it fixed, because it is kind of fun to mess with..besides, it wouldn't be a very big loss...these bases are pretty cheap.

So the serial console would be to solder in a serial cable I get off ebay, then attach it to my computer and open a telnet or some other console to read what the serial sends? I remember some people posting serials off ebay...have to find those posts again.
Re: Do I have the correct uBoot installed?
September 05, 2014 06:47PM
jfharper Wrote:
-------------------------------------------------------
> Yeah, it works as a linux box right now...I'm
> tempted to keep messing with it, just to see if I
> can get it fixed, because it is kind of fun to
> mess with..besides, it wouldn't be a very big
> loss...these bases are pretty cheap.

That's cool :) It would be a great example if you can work it out, I'll help. But get serial console first and do UART booting to make sure you can mess with NAND all you like.

> So the serial console would be to solder in a
> serial cable I get off ebay, then attach it to my
> computer and open a telnet or some other console
> to read what the serial sends? I remember some
> people posting serials off ebay...have to find
> those posts again.

No need to solder. There should be a serial header already in the GFHome. See this thread for parts:
http://forum.doozan.com/read.php?8,13263

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Re: Do I have the correct uBoot installed?
September 16, 2014 02:10PM
Hi bodhi,
I got the usb thing from ebay and had to actually solder in some pins, my GFH did not have a header. I got the console readout below. I found a thread here that discussed recovering bad blocks, but cannot find it (edit: I think this is it http://forum.doozan.com/read.php?3,7852)...I'll see if I can review that thread to get myself a little more familiar with what to expect. Thanks for your help on this. Should I follow that thread or follow your guidence?


U-Boot 2011.12 (Apr 18 2012 - 23:08:20)
Seagate GoFlexNet

SoC:   Kirkwood 88F6281_A1
DRAM:  128 MiB
WARNING: Caches not enabled
NAND:  256 MiB
In:    serial
Out:   serial
Err:   serial
Net:   egiga0
88E1116 Initialized 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... 1 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 error: validate_ec_hdr: bad VID header offset 2048, expected 512
UBI error: validate_ec_hdr: bad EC header
UBI error: ubi_io_read_ec_hdr: validation failed for PEB 0
UBI error: ubi_init: cannot attach mtd1
UBI error: ubi_init: UBI error: cannot initialize UBI, error -22
UBI init error 22
** 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..
### JFFS2 loading 'uboot-original-mtd0.kwb' to 0x800000
Scanning JFFS2 FS:  done.
find_inode failed for name=uboot-original-mtd0.kwb
load: Failed to find inode
### JFFS2 LOAD ERROR<0> for uboot-original-mtd0.kwb!
### JFFS2 loading 'uboot-original-mtd0.kwb' to 0x800000
Scanning JFFS2 FS:  done.
find_inode failed for name=uboot-original-mtd0.kwb
load: Failed to find inode
### JFFS2 LOAD ERROR<0> for uboot-original-mtd0.kwb!
resetting ...

edit 2

GoFlexNet> printenv
arcNumber=2097
baudrate=115200
bootcmd=usb start; run force_rescue_bootcmd; run ubifs_bootcmd; run usb_bootcmd; usb stop; run rescue_bootcmd; run pogo_bootcmd; reset
bootdelay=3
console=ttyS0,115200
ethact=egiga0
ethaddr=02:50:43:b1:34:a3
force_rescue=0
force_rescue_bootcmd=if test $force_rescue -eq 1 || ext2load usb 0:1 0x1700000 /rescueme 1 || fatload usb 0:1 0x1700000 /rescueme.txt 1; then run rescue_bootcmd; fi
led_error=orange blinking
led_exit=green off
led_init=green blinking
mainlineLinux=yes
mtdids=nand0=orion_nand
mtdparts=mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)
partition=nand0,2
pogo_bootcmd=if fsload uboot-original-mtd0.kwb; then go 0x800200; fi
rescue_bootcmd=if test $rescue_installed -eq 1; then run rescue_set_bootargs; nand read.e 0x800000 0x100000 0x400000; bootm 0x800000; else run pogo_bootcmd; fi
rescue_installed=0
rescue_set_bootargs=setenv bootargs console=$console ubi.mtd=2 root=ubi0:rootfs ro rootfstype=ubifs $mtdparts $rescue_custom_params
stderr=serial
stdin=serial
stdout=serial
ubifs_bootcmd=run ubifs_set_bootargs; if ubi part data && ubifsmount rootfs && ubifsload 0x800000 /boot/uImage && ubifsload 0x1100000 /boot/uInitrd; then bootm 0x800000 0x1100000; fi
ubifs_mtd=3
ubifs_set_bootargs=setenv bootargs console=$console ubi.mtd=$ubifs_mtd root=ubi0:rootfs rootfstype=ubifs $mtdparts $ubifs_custom_params
usb_boot=mw 0x800000 0 1; ext2load usb $usb_device 0x800000 /boot/uImage; if ext2load usb $usb_device 0x1100000 /boot/uInitrd; then bootm 0x800000 0x1100000; else bootm 0x800000; fi
usb_bootcmd=run usb_init; run usb_set_bootargs; run usb_boot
usb_device=0:1
usb_init=run usb_scan
usb_root=/dev/sda1
usb_rootdelay=10
usb_rootfstype=ext2
usb_scan=usb_scan_done=0;for scan in $usb_scan_list; do run usb_scan_$scan; if test $usb_scan_done -eq 0 && ext2load usb $usb 0x800000 /boot/uImage 1; then usb_scan_done=1; echo "Found bootable drive on usb $usb"; setenv usb_device $usb; setenv usb_root /dev/$dev; fi; done
usb_scan_1=usb=0:1 dev=sda1
usb_scan_2=usb=1:1 dev=sdb1
usb_scan_3=usb=2:1 dev=sdc1
usb_scan_4=usb=3:1 dev=sdd1
usb_scan_list=1 2 3 4
usb_set_bootargs=setenv bootargs console=$console root=$usb_root rootdelay=$usb_rootdelay rootfstype=$usb_rootfstype $mtdparts $usb_custom_params

Environment size: 2342/131068 bytes
GoFlexNet>

edit 3

GoFlexNet> <INTERRUPT>
GoFlexNet> md ff00003c
ff00003c: 00000121 e3a00000 e59f222c e5921000    !.......,"......
ff00004c: e2013008 e3530000 1a000002 e3811008    .0....S.........
ff00005c: e5821000 e5921000 e3a03000 ee2f3f1b    .........0...?/.
ff00006c: e59f2208 e5921000 e3c11cff e3c110ff    ."..............
ff00007c: e3710801 1a000003 e5921000 e3c114ff    ..q.............
ff00008c: e3c118ff e5821000 e59f21e0 e5922000    .........!... ..
ff00009c: e3a01902 e0112002 0a00000b e59f21d0    ..... .......!..
ff0000ac: e5921000 e3c11080 e5821000 e59f21c4    .............!..
ff0000bc: e5921000 e3c11080 e5821000 e59f21b8    .............!..
ff0000cc: e5921000 e3c1120f e5821000 e10f5000    .............P..
ff0000dc: e3c5501f e38550d3 e121f005 e3a05000    .P...P....!..P..
ff0000ec: ee075f17 ee075f16 ee075f15 ee085f17    ._..._..._..._..
ff0000fc: e59f2174 e3a03010 e5924000 e1c44003    t!...0...@...@..
ff00010c: e5824000 ee3f1f11 e3811505 ee2f1f11    .@....?......./.
ff00011c: e3a04003 ee034f10 e59f4160 ee024f10    .@...O..`A...O..
ff00012c: e3a03601 e3a02000 e3a01d06 e59f0150    .6... ......P...
GoFlexNet>
looks like 1.21

edit 4: with serial connected, I stopped autoboot by pressing any key, then typed help at the command prompt to reveal some commands that are on hand. In UART boot forum it says to download the kwboot-tool, but I can't figure how to do this with these commands. I'm reluctant to just start running commands because I don't want to make matters worse.
GoFlexNet> help
?       - alias for 'help'
base    - print or set address offset
bdinfo  - print Board Info structure
boot    - boot default, i.e., run 'bootcmd'
bootd   - boot default, i.e., run 'bootcmd'
bootm   - boot application image from memory
bootp   - boot image via network using BOOTP/TFTP protocol
chpart  - change active partition
cmp     - memory compare
coninfo - print console devices and information
cp      - memory copy
crc32   - checksum calculation
dhcp    - boot image via network using DHCP/TFTP protocol
diskboot- boot from IDE device
echo    - echo args to console
editenv - edit environment variable
env     - environment handling commands
exit    - exit script
ext2load- load binary file from a Ext2 filesystem
ext2ls  - list files in a directory (default /)
false   - do nothing, unsuccessfully
fatinfo - print information about filesystem
fatload - load binary file from a dos filesystem
fatls   - list files in a directory (default /)
fsinfo  - print information about filesystems
fsload  - load binary file from a filesystem image
go      - start application at address 'addr'
help    - print command description/usage
ide     - IDE sub-system
iminfo  - print header information for application image
imxtract- extract a part of a multi-image
itest   - return true/false on integer compare
loadb   - load binary file over serial line (kermit mode)
loads   - load S-Record file over serial line
loady   - load binary file over serial line (ymodem mode)
loop    - infinite loop on address range
ls      - list files in a directory (default /)
md      - memory display
mii     - MII utility commands
mm      - memory modify (auto-incrementing address)
mtdparts- define flash/nand partitions
mtest   - simple RAM read/write test
mw      - memory write (fill)
nand    - NAND sub-system
nboot   - boot from NAND device
nfs     - boot image via network using NFS protocol
nm      - memory modify (constant address)
ping    - send ICMP ECHO_REQUEST to network host
printenv- print environment variables
reset   - Perform RESET of the CPU
run     - run commands in an environment variable
saveenv - save environment variables to persistent storage
setenv  - set environment variables
showvar - print local hushshell variables
sleep   - delay execution for some time
source  - run script from memory
test    - minimal test like /bin/sh
tftpboot- boot image via network using TFTP protocol
true    - do nothing, successfully
ubi     - ubi commands
ubifsload- load file from an UBIFS filesystem
ubifsls - list files in a directory
ubifsmount- mount UBIFS volume
ubifsumount- unmount UBIFS volume
usb     - USB sub-system
usbboot - boot from USB device
version - print monitor, compiler and linker version
edit 5
GoFlexNet> nand bad

Device 0 bad blocks:
GoFlexNet> nand info

Device 0: nand0, sector size 128 KiB
  Page size      2048 b
  OOB size         64 b
  Erase size   131072 b
GoFlexNet>



Edited 5 time(s). Last edit at 09/16/2014 10:30PM by jfharper.
Re: Do I have the correct uBoot installed?
September 16, 2014 11:16PM
jfharper,


>
> GoFlexNet> nand bad
> 
> Device 0 bad blocks:

> GoFlexNet> nand info
> 
> Device 0: nand0, sector size 128 KiB
>   Page size      2048 b
>   OOB size         64 b
>   Erase size   131072 b
> GoFlexNet>
>

You are on the right track. The above shown that the bad blocks that we saw in Debian were not really bad blocks after all.

Now to enable booting stock u-boot and kernel, you can look for the orginal MTDs somewhere if people have uploaded them. And reflash mtd 1 to mtd 3. (keep mtd0 intact as currently). And also find the orginal u-boot (uboot-original-mtd0.kwb) for the GoFlex Net and copy it to the rootfs mtd (mtd 2).

I could dump those MTDs and provide them for you, but I'm pretty busy currently. If you can't find these MTDs anywhere, then post back here and wait.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)



Edited 2 time(s). Last edit at 09/17/2014 01:15AM by bodhi.
Re: Do I have the correct uBoot installed?
September 17, 2014 04:00PM
Thanks bodhi,

Edit 1:
OK...I'm figuring this out...

Edit 2:
I have another unmodified GFH base, and I soldered some pins on and setup the serial console...here is what I got on boot up. I'm going to attempt to get the original u-boot from this base, and also get the mtds off the nand and somehow transfer them to the base in question.


         -- NAS EXPLORER --
 _   _     ____              _
| | | |   | __ )  ___   ___ | |_
| | | |___|  _ \ / _ \ / _ \| __|
| |_| |___| |_) | (_) | (_) | |_
 \___/    |____/ \___/ \___/ \__|

 ** QSI BOARD: NAS-PLUG LE

U-Boot 1.1.4 (Sep 26 2011 - 13:01:13) Marvell version: 3.4.27
QSI NAS version: 1.0.6

U-Boot code: 00600000 -> 0067FFF0  BSS: -> 006CFB00

Soc: 88F6281 A1 (DDR2)
CPU running @ 1200Mhz L2 running @ 400Mhz
SysClock = 400Mhz , TClock = 200Mhz

DRAM CAS Latency = 5 tRP = 5 tRAS = 18 tRCD=6
DRAM CS[0] base 0x00000000   size 128MB
DRAM Total size 128MB  16bit width
Addresses 8M - 0M are saved for the U-Boot usage.
Mem malloc Initialization (8M - 7M): Done
NAND:NAND READID : MID=0x98, DID=0xda
256 MB
Flash:  0 kB

CPU : Marvell Feroceon (Rev 1)

Streaming disabled
Write allocate disabled


USB 0: host mode
PEX 0: interface detected no Link.
Net:   egiga0 [PRIME]
Hit any key to stop autoboot:  0

NAND read: device 0 offset 0x100000, size 0x300000

Reading data from 0x3ff800 -- 100% complete.
 3145728 bytes read: OK
## Booting image at 00800000 ...
   Image Name:   Linux-2.6.22.18
   Created:      2010-10-27  19:41:11 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2095528 Bytes =  2 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
OK

Starting kernel ...

Uncompressing Linux.............................................................          ....................................................................... done, bo          oting the kernel.
Linux version 2.6.22.18 (philippet@es5x86.axentra.com) (gcc version 4.3.2 (sdk3.2rc1-ct-ng-1.4.1) ) #14 Wed Oct 27 15:41:03 EDT 2010
CPU: ARM926EJ-S [56251311] revision 1 (ARMv5TE), cr=00053977
Machine: Feroceon-KW
Using UBoot passing parameters structure
Memory policy: ECC disabled, Data cache writeback
CPU0: D VIVT write-back cache
CPU0: I cache: 16384 bytes, associativity 4, 32 byte lines, 128 sets
CPU0: D cache: 16384 bytes, associativity 4, 32 byte lines, 128 sets
Built 1 zonelists.  Total pages: 32512
Kernel command line: console=ttyS0,115200 ubi.mtd=2,2048 root=ubi0:rootfs rootfstype=ubifs
PID hash table entries: 512 (order: 9, 2048 bytes)
Console: colour dummy device 80x30
Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
Memory: 128MB 0MB 0MB 0MB = 128MB total
Memory: 125568KB available (3844K code, 261K data, 128K init)
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
NET: Registered protocol family 16

CPU Interface
-------------
SDRAM_CS0 ....base 00000000, size 128MB
SDRAM_CS1 ....disable
SDRAM_CS2 ....disable
SDRAM_CS3 ....disable
PEX0_MEM ....base e8000000, size 128MB
PEX0_IO ....base f2000000, size   1MB
INTER_REGS ....base f1000000, size   1MB
NFLASH_CS ....base fa000000, size   2MB
SPI_CS ....base f4000000, size  16MB
BOOT_ROM_CS ....no such
DEV_BOOTCS ....no such
CRYPT_ENG ....base f0000000, size   2MB

  Marvell Development Board (LSP Version KW_LSP_4.3.4_patch22)-- SHEEVA PLUG  Soc: 88F6281 A1 LE

 Detected Tclk 200000000 and SysClk 400000000
MV Buttons Device Load
Marvell USB EHCI Host controller #0: c057b600
PEX0 interface detected no Link.
PCI: bus0: Fast back to back transfers enabled
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
NET: Registered protocol family 2
Time: kw_clocksource clocksource has been installed.
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 4096 (order: 3, 32768 bytes)
TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
TCP: Hash tables configured (established 4096 bind 4096)
TCP reno registered
RTC registered
XOR registered 2 channels
XOR 2nd invalidate WA enabled
cesadev_init(c0011854)
mvCesaInit: sessions=640, queue=64, pSram=f0000000
Warning: TS unit is powered off.
MV Buttons Driver Load
JFFS2 version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
io scheduler noop registered
io scheduler anticipatory registered (default)
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled
serial8250.0: ttyS0 at MMIO 0xf1012000 (irq = 33) is a 16550A
RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
loop: module loaded
Loading Marvell Ethernet Driver:
  o Cached descriptors in DRAM
  o DRAM SW cache-coherency
  o Single RX Queue support - ETH_DEF_RXQ=0
  o Single TX Queue support - ETH_DEF_TXQ=0
  o TCP segmentation offload enabled
  o Receive checksum offload enabled
  o Transmit checksum offload enabled
  o Network Fast Processing (Routing) supported
  o Driver ERROR statistics enabled
  o Driver INFO statistics enabled
  o Proc tool API enabled
  o SKB Reuse supported
  o SKB Recycle supported
  o Rx descripors: q0=128
  o Tx descripors: q0=532
  o Loading network interface(s):
    o  register under eth%d platform
    o eth0, ifindex = 1, GbE port = 0

Warning: Giga 1 is Powered Off

mvFpRuleDb (c7da7000): 1024 entries, 4096 bytes
Intel(R) PRO/1000 Network Driver - version 7.3.20-k2-NAPI
Copyright (c) 1999-2006 Intel Corporation.
e100: Intel(R) PRO/100 Network Driver, 3.5.17-k4-NAPI
e100: Copyright(c) 1999-2006 Intel Corporation
Integrated Sata device found
scsi0 : Marvell SCSI to SATA adapter
scsi1 : Marvell SCSI to SATA adapter
NFTL driver: nftlcore.c $Revision: 1.98 $, nftlmount.c $Revision: 1.41 $
NAND device: Manufacturer ID: 0x98, Chip ID: 0xda (Toshiba NAND 256MiB 3,3V 8-bit)
Scanning device for bad blocks
Using static partition definition
Creating 3 MTD partitions on "nand_mtd":
0x00000000-0x00100000 : "u-boot"
0x00100000-0x00700000 : "uImage"
0x00700000-0x10000000 : "root"
UBI: attaching mtd2 to ubi0
UBI: physical eraseblock size:   131072 bytes (128 KiB)
UBI: logical eraseblock size:    126976 bytes
UBI: smallest flash I/O unit:    2048
UBI: sub-page size:              512
UBI: VID header offset:          2048 (aligned 2048)
UBI: data offset:                4096
UBI: attached mtd2 to ubi0
UBI: MTD device name:            "root"
UBI: MTD device size:            249 MiB
UBI: number of good PEBs:        1992
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:     1
UBI: available PEBs:             0
UBI: total number of reserved PEBs: 1992
UBI: number of PEBs reserved for bad PEB handling: 38
UBI: max/mean erase counter: 5/1
UBI: background thread "ubi_bgt0d" started, PID 296
ehci_marvell ehci_marvell.70059: Marvell Orion EHCI
ehci_marvell ehci_marvell.70059: new USB bus registered, assigned bus number 1
ehci_marvell ehci_marvell.70059: irq 19, io base 0xf1050100
ehci_marvell ehci_marvell.70059: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
USB Universal Host Controller Interface driver v3.0
usbcore: registered new interface driver usblp
drivers/usb/class/usblp.c: v0.13: USB Printer Device Class driver
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
mice: PS/2 mouse device common for all mice
i2c /dev entries driver
Linux telephony interface: v1.00
Marvell Telephony Driver:

Warning Tdm is Powered Off
md: linear personality registered for level -1
md: raid0 personality registered for level 0
md: raid1 personality registered for level 1
raid6: int32x1     91 MB/s
raid6: int32x2    109 MB/s
raid6: int32x4    119 MB/s
raid6: int32x8     94 MB/s
raid6: using algorithm int32x4 (119 MB/s)
md: raid6 personality registered for level 6
md: raid5 personality registered for level 5
md: raid4 personality registered for level 4
raid5: measuring checksumming speed
   arm4regs  :  1072.400 MB/sec
   8regs     :   822.000 MB/sec
   32regs    :   803.200 MB/sec
raid5: using function: arm4regs (1072.400 MB/sec)
device-mapper: ioctl: 4.11.0-ioctl (2006-10-12) initialised: dm-devel@redhat.com
dm_crypt using the OCF package.
usbcore: registered new interface driver usbhid
drivers/hid/usbhid/hid-core.c: v2.6:USB HID core driver
TCP cubic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
UBIFS: recovery needed
UBIFS: recovery completed
UBIFS: mounted UBI device 0, volume 0, name "rootfs"
UBIFS: file system size:   239857664 bytes (234236 KiB, 228 MiB, 1889 LEBs)
UBIFS: journal size:       9023488 bytes (8812 KiB, 8 MiB, 72 LEBs)
UBIFS: media format:       4 (latest is 4)
UBIFS: default compressor: zlib
UBIFS: reserved for root:  0 bytes (0 KiB)
VFS: Mounted root (ubifs filesystem).
Freeing init memory: 128K
INIT: version 2.86 booting
                Welcome to HipServ
                Press 'I' to enter interactive startup.
Setting clock : Wed Sep 17 15:48:47 GMT+7 2014 [  OK  ]
Starting udev: [  OK  ]
Setting hostname axentraserver.goflex8822.seagateshare.com:  [  OK  ]
Setting up Logical Volume Management:   No volume groups found
[  OK  ]
Checking filesystems
Checking all file systems.
[  OK  ]
Mounting local filesystems:  mount: sysfs already mounted or /sys busy
mount: according to mtab, /sys is already mounted on /sys
[FAILED]
Enabling /etc/fstab swaps:  [  OK  ]
INIT: Entering runlevel: 3
Entering non-interactive startup
HipServ startup:[  OK  ]
Starting reset:  [  OK  ]
Starting seagate-lifecycle:[  OK  ]
Bringing up loopback interface:  [  OK  ]
Bringing up interface eth0:
Determining IP information for eth0... done.
/etc/init.d/iptables: line 42: /etc/sysconfig/networking/oe-profiles/default/ifcfg-eth0: No such file or directory
Flushing all current rules and user defined chains: [  OK  ]
Clearing all current rules and user defined chains: [  OK  ]
Applying iptables firewall rules:
[  OK  ]
[  OK  ]
check_igd.pl: no process killed
error reading information on service transmission.init: No such file or directory
[  OK  ]
Starting system logger: [  OK  ]
Starting kernel logger: [  OK  ]
Starting locator:[  OK  ]
Starting system message bus: [  OK  ]
Starting sshd: [  OK  ]
Starting cups: [  OK  ]
Starting vsftpd for vsftpd: [  OK  ]
Starting httpd: [  OK  ]
Starting appserver: [  OK  ]
Starting crond: [  OK  ]
Starting Netatalk services:
  Starting cnid_metad:[  OK  ]
  Starting afpd:[  OK  ]

Starting SMB services: [  OK  ]
Starting NMB services: [  OK  ]
Starting OEone System Proxy: SPD starting....log level=1, uid=0

[  OK  ]
Starting access-patrol:[  OK  ]
Starting Avahi daemon... [  OK  ]
Starting /usr/sbin/minidlna ... /etc/rc3.d/S98minidlna.init: line 45:  1576 Terminated              $MEDIASRV -f "${CONFIGFILE}"

Starting S99lld2: [  OK  ]
0
Starting DAAP server: [  OK  ]
Starting mynetworkd:[  OK  ]
    HipServ - Checking if RAID needs to be rebuilt
        HipServ - No RAID found
    HipServ - Bringing up iptables
    HipServ - Updating date...
        success
    HipServ - Enabling swap
    HipServ - Cleaning USB mountpoints
    HipServ - Mounting USB devices

    HipServ -  Checking for FTPS certificate
        HipServ - Found vsftpd key file
    HipServ -  Ensuring that table structures are up-to-date
    HipServ - Starting usbreaderd: [  OK  ]
    HipServ - Checking for updates...
        success
HipServ - boot complete
Starting spindownd.init:  [  OK  ]
Starting xMySyncMount.php:  [  OK  ]

axentraserver.goflex.seagateshare.com login:



Edited 4 time(s). Last edit at 09/17/2014 06:39PM by jfharper.
Re: Do I have the correct uBoot installed?
September 17, 2014 11:08PM
@ jfharper,

Great! but be careful about the mtd parts definition, they are different. Stock has 3 mtds, your current u-boot has 4 mtds, and the locations are different too, except for mtd0.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Re: Do I have the correct uBoot installed?
September 18, 2014 01:13AM
@Jharper,

Can't hurt using kwboot. Instruction to download in my u-boot thread:

Quote

Important Note: If possible, try to test this boot image with UART booting before flashing to NAND. See davygravy's UART booting using kwboot instruction: here in this thread.

To download ARM kwboot binary for UART booting at Dropbox:
kwboot
md5:
0efd011bdb244436e432a8de33e639a1

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Re: Do I have the correct uBoot installed?
September 18, 2014 10:08AM
Thanks, I'll check that out.

Edit 1:
In trying to futher my understanding/education, I found these two webpages:
GFH
GFN
where they illustrate the original Flash layout...the GFN page illustrates what you mentioned where they original MTDs had 3, and the new MTD has 4, excluding mtd0.



Edited 1 time(s). Last edit at 09/18/2014 10:17AM by jfharper.
Re: Do I have the correct uBoot installed?
September 18, 2014 11:18AM
jfharper,

Your dmesg shows:

Creating 3 MTD partitions on "nand_mtd":
0x00000000-0x00100000 : "u-boot"
0x00100000-0x00700000 : "uImage"
0x00700000-0x10000000 : "root"

So you should go with this actual layout as the original MTD parts.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Re: Do I have the correct uBoot installed?
September 18, 2014 01:24PM
OK.

Just for reference, here is the uboot tools available to me on the original unmodded GFH base...there is a nice little erase utility in the original that is not on the modded one.
NAS>> help
?       - alias for 'help'
base    - print or set address offset
boot    - boot default, i.e., run 'bootcmd'
bootd   - boot default, i.e., run 'bootcmd'
bootext2    dev:boot_part1,boot_part2 addr boot_image linux_dev_name
bootm   - boot application image from memory
bootp   - boot image via network using BootP/TFTP protocol
bubt    - Burn an image on the Boot Nand Flash.
chpart  - change active partition
cmp     - memory compare
cmpm    - Compare Memory
cp      - memory copy
cpumap - Display CPU memory mapping settings.
crc32   - checksum calculation
date    - get/set/reset date & time
dclk    - Display the MV device CLKs.
dhcp    - invoke DHCP client to obtain IP/boot params
diskboot- boot from IDE device
echo    - echo args to console
eeprom  - EEPROM sub-system
erase   - erase FLASH memory
ext2load- load binary file from a Ext2 filesystem
ext2ls  - list files in a directory (default /)
fatinfo - print information about filesystem
fatload - load binary file from a dos filesystem
fatls   - list files in a directory (default /)
fi      - Find value in the memory.
flinfo  - print FLASH memory information
fsinfo  - print information about filesystems
fsload  - load binary file from a filesystem image
g       - start application at cached address 'addr'(default addr 0x40000)
go      - start application at address 'addr'
help    - print online help
icrc32  - checksum calculation
ide     - IDE sub-system
iloop   - infinite loop on address range
imd     - i2c memory display
imm[.b, .s, .w, .l]     - i2c memory modify (auto-incrementing)
imw     - memory write (fill)
inm     - memory modify (constant address)
iprobe  - probe to discover valid I2C chip addresses
ir      - reading and changing MV internal register values.
ledtest - Discovery platform LED IO test (From GPIO 36 to 49)
loaduboot   - load uboot binary file over serial line (kermit mode)
loop    - infinite loop on address range
ls      - list files in a directory (default /)
map     - Diasplay address decode windows
md      - memory display
me      - PCI master enable
mm      - memory modify (auto-incrementing)
mmcinit - init mmc card
mp      - map PCI BAR
mtdparts- define flash/nand partitions
mtest   - simple RAM test
mv_diag - perform board diagnostics
mv_diag - run all available tests
mv_diag [1|2|...]
        - run specified test number
mw      - memory write (fill)
nand                   - NAND sub-system
nandtest        - loading file from TFT to do read/writ test of NAND.
nboot   - boot from NAND device
nbubt   - Burn a boot loader image on the Boot Nand Flash.
nm      - memory modify (constant address)
pci     - list and access PCI Configuration Space
phyRead - Read PCI-E Phy register
pciePhyWrite    - Write PCI-E Phy register
phyRead - Read Phy register
phyWrite        - Write Phy register
ping    - send ICMP ECHO_REQUEST to network host
printenv- print environment variables
protect - enable or disable FLASH write protection
rarpboot- boot image via network using RARP/TFTP protocol
rcvr    - Satrt recovery process (Distress Beacon with TFTP server)
reset   - Perform RESET of the CPU
resetenv        - Return all environment variable to default.
rtc     - RTC function command
run     - run commands in an environment variable
saveenv - save environment variables to persistent storage
se      - PCI Slave enable
setenv  - set environment variables
sflash  - read, write or erase the external SPI Flash.
sg      - scanning the PHYs status
sp      - Scan PCI bus.
switchRegRead   - Read switch register
switchRegWrite  - Write switch register
tftpboot- boot image via network using TFTP protocol
usb     - USB sub-system
usbboot - boot from USB device
version - print monitor version

Re: Do I have the correct uBoot installed?
September 18, 2014 01:39PM
So the way I understand it, the NAND is my Flash memory on the GFH board. It contains some partitions, and each partition has some stuff written on each partition. The stuff are utilities know as MTD utilities and are a booting information, a kernel (not sure exacltly what that is unless it is some thing that communicates and runs the on board chips), a linux root file system information, and some data on the last partition.

The boot stuff (uboot) is written on mtd0 partition on both original and modded base. Each NAND is partitioned at different locations/addresses as we have seen above.

Flashing nand, is the process of wiping all partitions, and repartitioning? Then I need to write the original mtds to the newly blank partitions on the modded base.

I need to get the mtds off the original unmod base somehow...I have yet to figure this out.

Hopefully, I am pretty close on my assumptions above...all this is super fun to learn and mess with...I just want to make sure I figure it out correctly before I move forward and risk messing something up.

EDIT 1:
I'm trying to understand what I did wrong to begin with. In running Jeff's script:
cd /tmp
wget http://projects.doozan.com/uboot/install_uboot_mtd0.sh
chmod +x install_uboot_mtd0.sh
./install_uboot_mtd0.sh
...I'm assuming it had a flash_erase and nand write function which rewrote my nand a certain way...then when I ran this on my own:
wget http://goflex.scottn.us/uboot-mtd0-orig-goflexhome.kwb
flash_erase /dev/mtd0 0 4
nandwrite /dev/mtd0 uboot-mtd0-orig-goflexhome.kwb
...I rewrote the mtd0 to a different size (0 with 4 block size), thereby leaving the rest of what Jeff's script wrote OR the original information at offset addresses and incomplete information...so that is why, now I have only a working uboot fom the scottn webpage, that cannot find anything else in complete form or where it should be in regards to address on the nand.

EDIT 2:
For reference (printenv of unmodded base):
NAS>> printenv
baudrate=115200
loads_echo=0
ipaddr=169.254.254.253
serverip=169.254.254.254
rootpath=/mnt/ARM_FS/
netmask=255.255.0.0
run_diag=yes
CASset=min
MALLOC_len=1
ethprime=egiga0
bootargs_end=:::DB88FXX81: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;
ethmtu=1500
usb0Mode=host
nandEcc=1bit
netretry=no
rcvrip=169.254.100.100
loadaddr=0x02000000
autoload=no
ethact=egiga0
rtc_mode=active
vm_ver_smt=2.0.381
ethaddr=00:10:75:2E:6E:77
explrpk=PGUJ-NBKB-TKAT-NZUB
explrsn=NA1XXND2
asm1_tag=12:09:16:07:05:11:32
bootargs_root=ubi.mtd=2,2048 root=ubi0:rootfs rootfstype=ubifs
console=console=ttyS0,115200
bootcmd=nand read.e 0x800000 0x100000 0x300000; setenv bootargs $(console) $(bootargs_root); bootm 0x800000
rtc_tz=PST
ntp_default=pool.ntp.org
smt_tag=12:09:16:07:05:13:16
stdin=serial
stdout=serial
stderr=serial
mainlineLinux=no
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
enaAutoRecovery=no
pcieTune=no

Environment size: 1203/131068 bytes

EDIT 3:
I found a webpage here: http://cyanlabs.net/Thread-Seagate-GoFlex-Home-recovery-via-serial
that illustrated the goflex home just like mine...the other pictures I found on the web had a header solder onto the board, but this webpage picture did not which resembled my GFH bases...I soldered pins on my boards just like they did, and they had a kwb file download for the GoFlexHome (not for sure the GoFlexNet)...also they illustrated how to setup the PumpKin tftp server and load the kwb file...so I thought I would try their guide, as it seemed to be just what I was looking for, without me having to figure everything out like they did (it would have been a good learning experience for me, but if it was done already...I thought why not try)...so I followed there guide and this is what I have now on the modded base in question:


         -- NAS EXPLORER --
 _   _     ____              _
| | | |   | __ )  ___   ___ | |_
| | | |___|  _ \ / _ \ / _ \| __|
| |_| |___| |_) | (_) | (_) | |_
 \___/    |____/ \___/ \___/ \__|
 ** QSI BOARD: NAS-PLUG LE

U-Boot 1.1.4 (Jun 10 2010 - 08:28:13) Marvell version: 3.4.27
QSI NAS version: 1.0.4

U-Boot code: 00600000 -> 0067FFF0  BSS: -> 006CFB00

Soc: 88F6281 A1 (DDR2)
CPU running @ 1200Mhz L2 running @ 400Mhz
SysClock = 400Mhz , TClock = 200Mhz

DRAM CAS Latency = 5 tRP = 5 tRAS = 18 tRCD=6
DRAM CS[0] base 0x00000000   size 128MB
DRAM Total size 128MB  16bit width
Addresses 8M - 0M are saved for the U-Boot usage.
Mem malloc Initialization (8M - 7M): Done
NAND:256 MB
Flash:  0 kB

CPU : Marvell Feroceon (Rev 1)

Streaming disabled
Write allocate disabled


USB 0: host mode
PEX 0: interface detected no Link.
Net:   egiga0 [PRIME]
Hit any key to stop autoboot:  0

NAND read: device 0 offset 0x100000, size 0x300000

Reading data from 0x3ff800 -- 100% complete.
 3145728 bytes read: OK
## Booting image at 00800000 ...
   Image Name:   Linux-2.6.22.18
   Created:      2010-10-27  19:41:11 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2095528 Bytes =  2 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
OK

Starting kernel ...

Uncompressing Linux.................................................................................................................................... done, booting the kernel.
Linux version 2.6.22.18 (philippet@es5x86.axentra.com) (gcc version 4.3.2 (sdk3.2rc1-ct-ng-1.4.1) ) #14 Wed Oct 27 15:41:03 EDT 2010
CPU: ARM926EJ-S [56251311] revision 1 (ARMv5TE), cr=00053977
Machine: Feroceon-KW
Using UBoot passing parameters structure
Memory policy: ECC disabled, Data cache writeback
CPU0: D VIVT write-back cache
CPU0: I cache: 16384 bytes, associativity 4, 32 byte lines, 128 sets
CPU0: D cache: 16384 bytes, associativity 4, 32 byte lines, 128 sets
Built 1 zonelists.  Total pages: 32512
Kernel command line: console=ttyS0,115200 ubi.mtd=2,2048 root=ubi0:rootfs rootfstype=ubifs
PID hash table entries: 512 (order: 9, 2048 bytes)
Console: colour dummy device 80x30
Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
Memory: 128MB 0MB 0MB 0MB = 128MB total
Memory: 125568KB available (3844K code, 261K data, 128K init)
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
NET: Registered protocol family 16

CPU Interface
-------------
SDRAM_CS0 ....base 00000000, size 128MB
SDRAM_CS1 ....disable
SDRAM_CS2 ....disable
SDRAM_CS3 ....disable
PEX0_MEM ....base e8000000, size 128MB
PEX0_IO ....base f2000000, size   1MB
INTER_REGS ....base f1000000, size   1MB
NFLASH_CS ....base fa000000, size   2MB
SPI_CS ....base f4000000, size  16MB
BOOT_ROM_CS ....no such
DEV_BOOTCS ....no such
CRYPT_ENG ....base f0000000, size   2MB

  Marvell Development Board (LSP Version KW_LSP_4.3.4_patch22)-- SHEEVA PLUG  Soc: 88F6281 A1 LE

 Detected Tclk 200000000 and SysClk 400000000
MV Buttons Device Load
Marvell USB EHCI Host controller #0: c057b600
PEX0 interface detected no Link.
PCI: bus0: Fast back to back transfers enabled
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
NET: Registered protocol family 2
Time: kw_clocksource clocksource has been installed.
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 4096 (order: 3, 32768 bytes)
TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
TCP: Hash tables configured (established 4096 bind 4096)
TCP reno registered
RTC registered
XOR registered 2 channels
XOR 2nd invalidate WA enabled
cesadev_init(c0011854)
mvCesaInit: sessions=640, queue=64, pSram=f0000000
Warning: TS unit is powered off.
MV Buttons Driver Load
JFFS2 version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
io scheduler noop registered
io scheduler anticipatory registered (default)
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled
serial8250.0: ttyS0 at MMIO 0xf1012000 (irq = 33) is a 16550A
RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
loop: module loaded
Loading Marvell Ethernet Driver:
  o Cached descriptors in DRAM
  o DRAM SW cache-coherency
  o Single RX Queue support - ETH_DEF_RXQ=0
  o Single TX Queue support - ETH_DEF_TXQ=0
  o TCP segmentation offload enabled
  o Receive checksum offload enabled
  o Transmit checksum offload enabled
  o Network Fast Processing (Routing) supported
  o Driver ERROR statistics enabled
  o Driver INFO statistics enabled
  o Proc tool API enabled
  o SKB Reuse supported
  o SKB Recycle supported
  o Rx descripors: q0=128
  o Tx descripors: q0=532
  o Loading network interface(s):
    o  register under eth%d platform
    o eth0, ifindex = 1, GbE port = 0

Warning: Giga 1 is Powered Off

mvFpRuleDb (c7da7000): 1024 entries, 4096 bytes
Intel(R) PRO/1000 Network Driver - version 7.3.20-k2-NAPI
Copyright (c) 1999-2006 Intel Corporation.
e100: Intel(R) PRO/100 Network Driver, 3.5.17-k4-NAPI
e100: Copyright(c) 1999-2006 Intel Corporation
Integrated Sata device found
scsi0 : Marvell SCSI to SATA adapter
scsi1 : Marvell SCSI to SATA adapter
NFTL driver: nftlcore.c $Revision: 1.98 $, nftlmount.c $Revision: 1.41 $
NAND device: Manufacturer ID: 0x98, Chip ID: 0xda (Toshiba NAND 256MiB 3,3V 8-bit)
Scanning device for bad blocks
Using static partition definition
Creating 3 MTD partitions on "nand_mtd":
0x00000000-0x00100000 : "u-boot"
0x00100000-0x00700000 : "uImage"
0x00700000-0x10000000 : "root"
UBI: attaching mtd2 to ubi0
UBI: physical eraseblock size:   131072 bytes (128 KiB)
UBI: logical eraseblock size:    126976 bytes
UBI: smallest flash I/O unit:    2048
UBI: sub-page size:              512
UBI: VID header offset:          2048 (aligned 2048)
UBI: data offset:                4096
UBI: attached mtd2 to ubi0
UBI: MTD device name:            "root"
UBI: MTD device size:            249 MiB
UBI: number of good PEBs:        1992
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:     1
UBI: available PEBs:             0
UBI: total number of reserved PEBs: 1992
UBI: number of PEBs reserved for bad PEB handling: 38
UBI: max/mean erase counter: 3/0
UBI: background thread "ubi_bgt0d" started, PID 296
ehci_marvell ehci_marvell.70059: Marvell Orion EHCI
ehci_marvell ehci_marvell.70059: new USB bus registered, assigned bus number 1
ehci_marvell ehci_marvell.70059: irq 19, io base 0xf1050100
ehci_marvell ehci_marvell.70059: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
USB Universal Host Controller Interface driver v3.0
usbcore: registered new interface driver usblp
drivers/usb/class/usblp.c: v0.13: USB Printer Device Class driver
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
mice: PS/2 mouse device common for all mice
i2c /dev entries driver
Linux telephony interface: v1.00
Marvell Telephony Driver:

Warning Tdm is Powered Off
md: linear personality registered for level -1
md: raid0 personality registered for level 0
md: raid1 personality registered for level 1
raid6: int32x1     91 MB/s
raid6: int32x2    109 MB/s
raid6: int32x4    119 MB/s
raid6: int32x8     94 MB/s
raid6: using algorithm int32x4 (119 MB/s)
md: raid6 personality registered for level 6
md: raid5 personality registered for level 5
md: raid4 personality registered for level 4
raid5: measuring checksumming speed
   arm4regs  :  1084.400 MB/sec
   8regs     :   822.000 MB/sec
   32regs    :   803.200 MB/sec
raid5: using function: arm4regs (1084.400 MB/sec)
device-mapper: ioctl: 4.11.0-ioctl (2006-10-12) initialised: dm-devel@redhat.com
dm_crypt using the OCF package.
usbcore: registered new interface driver usbhid
drivers/hid/usbhid/hid-core.c: v2.6:USB HID core driver
TCP cubic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
UBIFS: mounted UBI device 0, volume 0, name "rootfs"
UBIFS: file system size:   239857664 bytes (234236 KiB, 228 MiB, 1889 LEBs)
UBIFS: journal size:       9023488 bytes (8812 KiB, 8 MiB, 72 LEBs)
UBIFS: media format:       4 (latest is 4)
UBIFS: default compressor: zlib
UBIFS: reserved for root:  0 bytes (0 KiB)
VFS: Mounted root (ubifs filesystem).
Freeing init memory: 128K
INIT: version 2.86 booting
                Welcome to HipServ
                Press 'I' to enter interactive startup.
Setting clock : Thu Sep 18 13:36:30 GMT+7 2014 [  OK  ]
Starting udev: [  OK  ]
Setting hostname axentraserver.jasonsgoflex2.seagateshare.com:  [  OK  ]
Setting up Logical Volume Management:   No volume groups found
[  OK  ]
Checking filesystems
Checking all file systems.
[  OK  ]
Mounting local filesystems:  mount: sysfs already mounted or /sys busy
mount: according to mtab, /sys is already mounted on /sys
[FAILED]
Enabling /etc/fstab swaps:  [  OK  ]
INIT: Entering runlevel: 3
Entering non-interactive startup
HipServ startup:[  OK  ]
Starting reset:  [  OK  ]
Starting seagate-lifecycle:[  OK  ]
Bringing up loopback interface:  [  OK  ]
Bringing up interface eth0:
Determining IP information for eth0... done.
/etc/init.d/iptables: line 42: /etc/sysconfig/networking/oe-profiles/default/ifcfg-eth0: No such file or directory
Flushing all current rules and user defined chains: [  OK  ]
Clearing all current rules and user defined chains: [  OK  ]
Applying iptables firewall rules:
[  OK  ]
[  OK  ]
check_igd.pl: no process killed
error reading information on service transmission.init: No such file or directory
[  OK  ]
Starting system logger: [  OK  ]
Starting kernel logger: [  OK  ]
Starting locator:[  OK  ]
Starting system message bus: [  OK  ]
Starting sshd: [  OK  ]
Starting cups: [  OK  ]
Starting xinetd: [  OK  ]
Starting vsftpd for vsftpd: [  OK  ]
Starting httpd: [  OK  ]
Starting appserver: [  OK  ]
Starting crond: [  OK  ]
Starting Netatalk services:
  Starting cnid_metad:[  OK  ]
  Starting afpd:[  OK  ]

Starting SMB services: [  OK  ]
Starting NMB services: [  OK  ]
Starting OEone System Proxy: SPD starting....log level=1, uid=0

[  OK  ]
Starting access-patrol:[  OK  ]
Starting Avahi daemon... [  OK  ]
Starting /usr/sbin/minidlna ...
Starting S99lld2: [  OK  ]
0
Starting DAAP server: [  OK  ]
Starting mynetworkd:[  OK  ]
    HipServ - Checking if RAID needs to be rebuilt
        HipServ - No RAID found
    HipServ - Bringing up iptables
    HipServ - Updating date...
        success
    HipServ - Enabling swap
    HipServ - Cleaning USB mountpoints
    HipServ - Mounting USB devices

    HipServ -  Checking for FTPS certificate
        HipServ - Found vsftpd key file
    HipServ -  Ensuring that table structures are up-to-date
    HipServ - Starting usbreaderd: [  OK  ]
    HipServ - Checking for updates...
        success
HipServ - boot complete
Starting spindownd.init:  [  OK  ]
Starting xMySyncMount.php:  [  OK  ]

axentraserver.goflex.seagateshare.com login:
...looks like I got it back to stock!

My thinking was, if my nand was not messed up, and I could just run a nand erase (nand erase 0x0 0x80000) and then run a nand write (nand write.e 0x800000 0x0 0x80000) with the kwb file someone already put together, then this may just work.

Well, now that it looks like it is working properly now...what am I going to mess with now with my time? ;)

I've already run this guide: http://blog.qnology.com/2014/07/hacking-pogoplug-v4-series-4-and-mobile.html
on a couple pogoplug v4 mobiles to get samba running an external harddrive for network shares and mobile device accessibility...these now run debain...I think I'll leave the goflex home bases as is for now, since I can access them (usb hard drives) via ftp since they already have a ftp server and upnp and minidlna servers running...maybe I'll mess with the pogoplugs if I want to do any mods or debian customization.

I feel like I sold myself short on an education by following that guide instead of figuring it out for myself...oh well, I'm sure I'll get over it. Thanks again bodhi for your help.



Edited 3 time(s). Last edit at 09/18/2014 03:45PM by jfharper.
Re: Do I have the correct uBoot installed?
September 18, 2014 03:57PM
jfharper,

I will respond in detail when I got home. Pls see below for short answers.

Wrote:
-------------------------------------------------------
> So the way I understand it, the NAND is my Flash
> memory on the GFH board. It contains some
> partitions, and each partition has some stuff
> written on each partition. The stuff are
> utilities know as MTD utilities

Not utilities, they are system files.

> and are a booting
> information, a kernel (not sure exacltly what that
> is unless it is some thing that communicates and
> runs the on board chips),

Linux kernel image.

> linux root file system
> information, and some data on the last partition.
>
> The boot stuff (uboot) is written on mtd0
> partition on both original and modded base. Each
> NAND is partitioned at different
> locations/addresses as we have seen above.
>
> Flashing nand, is the process of wiping all
> partitions, and repartitioning? Then I need to
> write the original mtds to the newly blank
> partitions on the modded base.

No need to erase while repartioning. Just define new partitions. And erase each one before writing to flash.

> I need to get the mtds off the original unmod base
> somehow...I have yet to figure this out.

Use nanddump. Instruction is in one of the steps in my latest u-boot thread (see my signature).


> Hopefully, I am pretty close on my assumptions
> above...all this is super fun to learn and mess
> with...I just want to make sure I figure it out
> correctly before I move forward and risk messing
> something up.
>
> EDIT 1:
> I'm trying to understand what I did wrong to begin
> with. In running Jeff's script:
>
> cd /tmp
> wget
> http://projects.doozan.com/uboot/install_uboot_mtd
> 0.sh
> chmod +x install_uboot_mtd0.sh
> ./install_uboot_mtd0.sh
>
> ...I'm assuming it had a flash_erase and nand
> write function which rewrote my nand a certain
> way...then when I ran this on my own:
>
> wget
> http://goflex.scottn.us/uboot-mtd0-orig-goflexhome
> .kwb
> flash_erase /dev/mtd0 0 4
> nandwrite /dev/mtd0
> uboot-mtd0-orig-goflexhome.kwb
>
> ...I rewrote the mtd0 to a different size (0 with
> 4 block size), thereby leaving the rest of what
> Jeff's script wrote OR the original information at
> offset addresses and incomplete information...so
> that is why, now I have only a working uboot fom
> the scottn webpage, that cannot find anything else
> in complete form or where it should be in regards
> to address on the nand.
>
> EDIT 2:
> For reference (printenv of unmodded base):
>
> NAS>> printenv
> baudrate=115200
> loads_echo=0
> ipaddr=169.254.254.253
> serverip=169.254.254.254
> rootpath=/mnt/ARM_FS/
> netmask=255.255.0.0
> run_diag=yes
> CASset=min
> MALLOC_len=1
> ethprime=egiga0
> bootargs_end=:::DB88FXX81: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;
> ethmtu=1500
> usb0Mode=host
> nandEcc=1bit
> netretry=no
> rcvrip=169.254.100.100
> loadaddr=0x02000000
> autoload=no
> ethact=egiga0
> rtc_mode=active
> vm_ver_smt=2.0.381
> ethaddr=00:10:75:2E:6E:77
> explrpk=PGUJ-NBKB-TKAT-NZUB
> explrsn=NA1XXND2
> asm1_tag=12:09:16:07:05:11:32
> bootargs_root=ubi.mtd=2,2048 root=ubi0:rootfs
> rootfstype=ubifs
> console=console=ttyS0,115200
> bootcmd=nand read.e 0x800000 0x100000 0x300000;
> setenv bootargs $(console) $(bootargs_root); bootm
> 0x800000
> rtc_tz=PST
> ntp_default=pool.ntp.org
> smt_tag=12:09:16:07:05:13:16
> stdin=serial
> stdout=serial
> stderr=serial
> mainlineLinux=no
> 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
> enaAutoRecovery=no
> pcieTune=no
> 
> Environment size: 1203/131068 bytes
>

It's hard to say what went wrong without the log. The fact that Debian thinks they are bad is weird.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)



Edited 1 time(s). Last edit at 09/18/2014 03:59PM by bodhi.
Re: Do I have the correct uBoot installed?
September 18, 2014 11:27PM
@jfharper,

Before you flash the orignal u-boot to the bad GFH, try booting it with my uploaded Debian rootfs:
http://forum.doozan.com/read.php?2,12096

I looked over u-boot envs listed in serial console for the bad GFH, and did not see anything wrong. So perhaps something wrong with your Arch rootfs? best to try booting with Debian rootfs that we know working.

-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: