Welcome! Log In Create A New Profile

Advanced

Pogo mobile nand bad block - installation failure

Posted by E4691 
hello,

i am new to Linux but did read many topics in this forum and others.
after activating my new pogoplug mobile (v4-A1), i tried to install archlinux on it, using the instructions on ArchLinux site. i have encountered errors along the way. i have tried many steps to amend it, too many to recall.
current situation is that i am no longer able to connect to my home network. i am able to communicate with the unit with serial cable.
monitoring startup shows i have a bad block in the nand.
it can be seen here:
/ # dmesg | grep -i 'bad'
<6>[ 1.010000] Scanning device for bad blocks
<4>[ 1.020000] Bad eraseblock 157 at 0x0000013a0000
<5>[ 1.370000] UBI: number of bad PEBs: 1
<5>[ 1.410000] UBI: number of PEBs reserved for bad PEB handling: 8
/ #
and also:
/ # fw_printenv
Warning: Bad CRC, using default environment
bootcmd=bootp; setenv bootargs root=/dev/nfs nfsroot=${serverip}:${rootpath} ip=${ipaddr}:${m
bootdelay=5
baudrate=115200

i would like to get some help recovering the system; is it possible to re-install uBoot?
what should i do in order to amend the system and install Debian or Archlinux?

regards,

Eyal
Re: Pogo mobile nand bad block - installation failure
April 12, 2015 03:46PM
E4691,

Boot up again with serial console, and get the entire serial boot log and post here. Looks like you can log into Linux with serial console, so please also post these info after you are in the shell:

uname -a
cat /proc/mtd
cat /etc/fw_env.config

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Thanks for the fast respond.

the boot is done with a usb that includes re-installed Arch (based on re-installation instructions in ArchLinux.org). i can also boot without it (with same end result.
it is long, but here is the start log (with the last commands at the end):



U-Boot 1.1.4 (Oct  1 2011 - 12:21:35) Cloud Engines 1.1.2 (3.4.27) PHYADDR=0

U-Boot code: 00600000 -> 0067FFF0  BSS: -> 006918B4

Soc: 88F6192 A1 (DDR2)
CPU running @ 800Mhz L2 running @ 400Mhz
SysClock = 200Mhz , TClock = 166Mhz 

DRAM CAS Latency = 3 tRP = 3 tRAS = 8 tRCD=3
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:128 MB
*** Warning - bad CRC or NAND, using default environment

Flash:  0 kB

CPU : Marvell Feroceon (Rev 1)
CLOUD ENGINES BOARD (GUESSED): PPV4A1

Streaming disabled 
Write allocate disabled


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

Loading from NAND 128MB 3,3V 8-bit, offset 0x200000
   Image Name:   Linux-2.6.31.8
   Created:      2011-08-23  20:00:55 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2080956 Bytes =  2 MB
   Load Address: 00008000
   Entry Point:  00008000
## Booting image at 00800000 ...
   Image Name:   Linux-2.6.31.8
   Created:      2011-08-23  20:00:55 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2080956 Bytes =  2 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
OK

Starting kernel ...

Uncompressing Linux..................................................................................................................................... done, booting the kernel.
[    0.000000] Linux version 2.6.31.8 (afenn@kt) (gcc version 4.3.2 (sdk3.3-ct-ng-1.4.1) ) #4 Tue Aug 23 13:00:50 PDT 2011
[    0.000000] CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=00053977
[    0.000000] CPU: VIVT data cache, VIVT instruction cache
[    0.000000] Machine: Feroceon-KW
[    0.000000] Using UBoot passing parameters structure
[    0.000000] Ignoring unrecognised tag 0x41004345
[    0.000000] Memory policy: ECC disabled, Data cache writeback
[    0.000000] Built 1 zonelists in Zone order, mobility grouping off.  Total pages: 32512
[    0.000000] Kernel command line: console=ttyS0,115200 root=ubi0:rootfs ubi.mtd=4,2048 rootfstype=ubifs
[    0.000000] PID hash table entries: 512 (order: 9, 2048 bytes)
[    0.000000] Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
[    0.000000] Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
[    0.000000] Memory: 128MB = 128MB total
[    0.000000] Memory: 118356KB available (3852K code, 261K data, 124K init, 0K highmem)
[    0.000000] Hierarchical RCU implementation.
[    0.000000] NR_IRQS:128
[    0.000000] Console: colour dummy device 80x30
[    0.000000] Calibrating delay loop... 799.53 BogoMIPS (lpj=3997696)
[    0.230000] Mount-cache hash table entries: 512
[    0.230000] CPU: Testing write buffer coherency: ok
[    0.230000] NET: Registered protocol family 16
[    0.230000] Feroceon L2: Enabling L2
[    0.230000] Feroceon L2: Cache support initialised.
[    0.230000] 
[    0.230000] CPU Interface
[    0.230000] -------------
[    0.230000] SDRAM_CS0 ....base 00000000, size 128MB 
[    0.230000] SDRAM_CS1 ....disable
[    0.230000] SDRAM_CS2 ....disable
[    0.230000] SDRAM_CS3 ....disable
[    0.230000] PEX0_MEM ....base e0000000, size 128MB 
[    0.230000] PEX0_IO ....base f2000000, size   1MB 
[    0.230000] PEX1_MEM ....no such
[    0.230000] PEX1_IO ....no such
[    0.230000] INTER_REGS ....base f1000000, size   1MB 
[    0.230000] NFLASH_CS ....base fa000000, size   2MB 
[    0.230000] SPI_CS ....base f4000000, size  16MB 
[    0.230000] BOOT_ROM_CS ....no such
[    0.230000] DEV_BOOTCS ....no such
[    0.230000] CRYPT_ENG ....base f0000000, size   2MB 
[    0.230000] 
[    0.230000]   Marvell Development Board (LSP Version KW_LSP_5.1.3_patch18)-- RD-88F6192A-NAS  Soc: 88F6192 A1 LE
[    0.230000] 
[    0.230000]  Detected Tclk 166666667 and SysClk 200000000 
[    0.230000] Marvell USB EHCI Host controller #0: c403e740
[    0.730000] PEX0 interface detected no Link.
[    0.730000] PCI: bus0: Fast back to back transfers enabled
[    0.730000] mvPexLocalBusNumSet: ERR. Invalid PEX interface 1
[    0.750000] bio: create slab <bio-0> at 0
[    0.750000] SCSI subsystem initialized
[    0.750000] usbcore: registered new interface driver usbfs
[    0.750000] usbcore: registered new interface driver hub
[    0.750000] usbcore: registered new device driver usb
[    0.750000] NET: Registered protocol family 2
[    0.750000] IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.750000] TCP established hash table entries: 4096 (order: 3, 32768 bytes)
[    0.750000] TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
[    0.750000] TCP: Hash tables configured (established 4096 bind 4096)
[    0.750000] TCP reno registered
[    0.750000] NET: Registered protocol family 1
[    0.750000] cpufreq: Init kirkwood cpufreq driver
[    0.760000] XOR registered 4 channels
[    0.760000] XOR 2nd invalidate WA enabled
[    0.760000] cesadev_init(c000d7fc)
[    0.760000] mvCesaInit: sessions=640, queue=64, pSram=f0000000
[    0.760000] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[    0.770000] msgmni has been set to 231
[    0.770000] alg: No test for cipher_null (cipher_null-generic)
[    0.770000] alg: No test for ecb(cipher_null) (ecb-cipher_null)
[    0.770000] alg: No test for digest_null (digest_null-generic)
[    0.770000] alg: No test for compress_null (compress_null-generic)
[    0.780000] alg: No test for stdrng (krng)
[    0.780000] alg: No test for hmac(digest_null) (hmac(digest_null-generic))
[    0.790000] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253)
[    0.790000] io scheduler noop registered
[    0.790000] io scheduler anticipatory registered (default)
[    0.790000] Initializing ths8200_init
[    0.790000] Initializing dove_adi9889_init
[    0.810000] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
[    0.810000] serial8250.0: ttyS0 at MMIO 0xf1012000 (irq = 33) is a 16550A
[    0.810000] console [ttyS0] enabled
[    0.820000] Integrated Sata device found
[    0.830000] IRQ 21/mvSata: IRQF_DISABLED is not guaranteed on shared IRQs
[    0.850000] scsi0 : Marvell SCSI to SATA adapter
[    0.860000] scsi1 : Marvell SCSI to SATA adapter
[    0.870000] Loading Marvell Ethernet Driver:
[    0.870000]   o Cached descriptors in DRAM
[    0.880000]   o DRAM SW cache-coherency
[    0.880000]   o 1 Giga ports supported
[    0.880000]   o Single RX Queue support - ETH_DEF_RXQ=0
[    0.890000]   o Single TX Queue support - ETH_DEF_TXQ=0
[    0.890000]   o TCP segmentation offload (TSO) supported
[    0.900000]   o Large Receive offload (LRO) supported
[    0.900000]   o Receive checksum offload supported
[    0.910000]   o Transmit checksum offload supported
[    0.910000]   o Network Fast Processing (Routing) supported - (Disabled)
[    0.920000]   o Driver ERROR statistics enabled
[    0.930000]   o Proc tool API enabled
[    0.930000]   o SKB Reuse supported - (Disabled)
[    0.930000]   o SKB Recycle supported - (Disabled)
[    0.940000]   o Rx descripors: q0=128
[    0.940000]   o Tx descripors: q0=532
[    0.950000]   o Loading network interface(s):
[    0.950000]      o register under mv88fx_eth platform
[    0.960000]      o eth0, ifindex = 2, GbE port = 0
[    0.960000] 
[    0.960000] mvFpRuleDb (c45b2000): 1024 entries, 4096 bytes
[    0.970000] Counter=0, opIdx=6, overhead=16
[    0.970000] Counter=1, opIdx=2, overhead=0
[    0.980000] Counter=2, opIdx=1, overhead=18
[    0.980000] Counter=3, opIdx=2, overhead=0
[    0.990000] tun: Universal TUN/TAP device driver, 1.6
[    0.990000] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
[    1.000000] NAND device: Manufacturer ID: 0xad, Chip ID: 0xf1 (Hynix NAND 128MiB 3,3V 8-bit)
[    1.010000] Scanning device for bad blocks
[    1.020000] Bad eraseblock 157 at 0x0000013a0000
[    1.060000] Using static partition definition
[    1.070000] Creating 5 MTD partitions on "nand_mtd":
[    1.070000] 0x000000000000-0x000000200000 : "u-boot"
[    1.080000] 0x000000200000-0x000000500000 : "uImage"
[    1.080000] 0x000000500000-0x000000800000 : "uImage2"
[    1.090000] 0x000000800000-0x000001000000 : "failsafe"
[    1.090000] 0x000001000000-0x000008000000 : "root"
[    1.100000] UBI: attaching mtd4 to ubi0
[    1.100000] UBI: physical eraseblock size:   131072 bytes (128 KiB)
[    1.110000] UBI: logical eraseblock size:    126976 bytes
[    1.120000] UBI: smallest flash I/O unit:    2048
[    1.120000] UBI: sub-page size:              512
[    1.120000] UBI: VID header offset:          2048 (aligned 2048)
[    1.130000] UBI: data offset:                4096
[    1.360000] UBI: attached mtd4 to ubi0
[    1.360000] UBI: MTD device name:            "root"
[    1.360000] UBI: MTD device size:            112 MiB
[    1.370000] UBI: number of good PEBs:        895
[    1.370000] UBI: number of bad PEBs:         1
[    1.380000] UBI: max. allowed volumes:       128
[    1.380000] UBI: wear-leveling threshold:    4096
[    1.390000] UBI: number of internal volumes: 1
[    1.390000] UBI: number of user volumes:     1
[    1.400000] UBI: available PEBs:             0
[    1.400000] UBI: total number of reserved PEBs: 895
[    1.410000] UBI: number of PEBs reserved for bad PEB handling: 8
[    1.410000] UBI: max/mean erase counter: 1/0
[    1.420000] UBI: image sequence number: 0
[    1.420000] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    1.430000] ehci_marvell ehci_marvell.70059: Marvell Orion EHCI
[    1.430000] ehci_marvell ehci_marvell.70059: new USB bus registered, assigned bus number 1
[    1.440000] UBI: background thread "ubi_bgt0d" started, PID 451
[    1.470000] ehci_marvell ehci_marvell.70059: irq 19, io base 0xf1050100
[    1.490000] ehci_marvell ehci_marvell.70059: USB 2.0 started, EHCI 1.00
[    1.490000] usb usb1: configuration #1 chosen from 1 choice
[    1.500000] hub 1-0:1.0: USB hub found
[    1.500000] hub 1-0:1.0: 1 port detected
[    1.510000] Initializing USB Mass Storage driver...
[    1.510000] usbcore: registered new interface driver usb-storage
[    1.520000] USB Mass Storage support registered.
[    1.520000] usbcore: registered new interface driver ums-datafab
[    1.530000] usbcore: registered new interface driver ums-freecom
[    1.530000] usbcore: registered new interface driver ums-jumpshot
[    1.540000] usbcore: registered new interface driver ums-sddr09
[    1.550000] usbcore: registered new interface driver ums-sddr55
[    1.550000] usbcore: registered new interface driver ums-usbat
[    1.560000] mice: PS/2 mouse device common for all mice
[    1.560000] i2c /dev entries driver
[    1.580000] sdhci: Secure Digital Host Controller Interface driver
[    1.580000] sdhci: Copyright(c) Pierre Ossman
[    1.590000] mmc0: mvsdio driver initialized, using GPIO 27 for card detection
[    1.600000] usbcore: registered new interface driver usbhid
[    1.600000] usbhid: v2.6:USB HID core driver
[    1.610000] TCP cubic registered
[    1.610000] NET: Registered protocol family 17
[    1.620000] RPC: Registered udp transport module.
[    1.620000] RPC: Registered tcp transport module.
[    1.630000] drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
[    1.760000] UBIFS: mounted UBI device 0, volume 0, name "rootfs"
[    1.770000] UBIFS: file system size:   110723072 bytes (108128 KiB, 105 MiB, 872 LEBs)
[    1.770000] UBIFS: journal size:       9023488 bytes (8812 KiB, 8 MiB, 72 LEBs)
[    1.780000] UBIFS: media format:       w4/r0 (latest is w4/r0)
[    1.790000] UBIFS: default compressor: lzo
[    1.790000] UBIFS: reserved for root:  0 bytes (0 KiB)
[    1.800000] VFS: Mounted root (ubifs filesystem) on device 0:11.
[    1.800000] Freeing init memory: 124K
[    1.870000] usb 1-1: new high speed USB device using ehci_marvell and address 2
[    2.030000] usb 1-1: configuration #1 chosen from 1 choice
[    2.040000] scsi2 : SCSI emulation for USB Mass Storage devices
Too many bit errors @ 0xa0000 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xa0800 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xa1000 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xa1800 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xa2000 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xa2800 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xa3000 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xa3800 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xa4000 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xa4800 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xa5000 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xa5800 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xa6000 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xa6800 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xa7000 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xa7800 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xa8000 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xa8800 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xa9000 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xa9800 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xaa000 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xaa800 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xab000 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xab800 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xac000 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xac800 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xad000 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xad800 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xae000 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xae800 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xaf000 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xaf800 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xb0000 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xb0800 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xb1000 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xb1800 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xb2000 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xb2800 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xb3000 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xb3800 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xb4000 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xb4800 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xb5000 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xb5800 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xb6000 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xb6800 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xb7000 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xb7800 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xb8000 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xb8800 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xb9000 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xb9800 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xba000 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xba800 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xbb000 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xbb800 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xbc000 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xbc800 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xbd000 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xbd800 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xbe000 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xbe800 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xbf000 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xbf800 -- Can't correct!
PAGE DATA:
OOB:
   -- Invalid CRC32 on parameters: 0xffffffff != 0x619d86db
[    4.730000] eth0: started
udhcpc (v1.16.1) started
HWADDR 00 0x50 0x43 0x00 0x02 0x02
PIP0 2
PIP1 2
cat: can't open '/etc/resolv.conf': No such file or directory
route: SIOCDELRT: No such process
grep: /etc/resolv.conf: No such file or directory
Sending discover...
[    7.060000] scsi 2:0:0:0: Direct-Access     SanDisk  Cruzer Blade     1.26 PQ: 0 ANSI: 6
[    7.080000] sd 2:0:0:0: [sda] 15633408 512-byte logical blocks: (8.00 GB/7.45 GiB)
[    7.090000] sd 2:0:0:0: [sda] Write Protect is off
[    7.090000] sd 2:0:0:0: [sda] Assuming drive cache: write through
[    7.100000] sd 2:0:0:0: [sda] Assuming drive cache: write through
[    7.110000]  sda:
[    7.110000] sd 2:0:0:0: Attached scsi generic sg0 type 0
[    7.120000]  sda1 sda2
[    7.150000] sd 2:0:0:0: [sda] Assuming drive cache: write through
[    7.150000] sd 2:0:0:0: [sda] Attached SCSI removable disk
Sending discover...
Sending discover...
HWADDR 00 0x50 0x43 0x00 0x02 0x02
PIP0 2
PIP1 2
No lease, forking to background
Loading gpio_keys.ko...
Loading ejectbutton.ko...
[   14.250000] IRQ 93 uses trigger mode 0; requested 3
[   14.260000] input: gpio-keys as /devices/platform/gpio-keys.0/input/input0
[   14.270000] xce_ebtn: Pogoplug series V4 eject button initialized.
[   14.420000] ufsd: module license 'Commercial product' taints kernel.
[   14.420000] Disabling lock debugging due to kernel taint
[   14.450000] ufsd: driver (8.6 (U86_S[2012-02-28-18:39:23]), LBD=ON, delalloc, ioctl) loaded at bf00c000
[   14.450000] NTFS support included
[   14.450000] Hfs+/HfsX support included
[   14.450000] For 'CloudEngines_PogoPlug_2011-08-03'
Loading rt3070sta.ko:        [   14.780000] rtusb init rt2870 --->
[   14.790000] usbcore: registered new interface driver rt2870
Success
Loading xce.ko:              [   14.820000] Cloud Engines XCE Init [Version: 3.9.0.4]
[   14.820000] XCE: CPU MEMORY MAP:
[   14.820000] XCE:   -- 0x00001000 - 0xbeffffff (3055 MB)  User Space Mappings
[   14.830000] XCE:   -- 0xbf000000 - 0xbfffffff (  16 MB)  Kernel module space
[   14.840000] XCE:   -- 0xc0000000 - 0xc7ffffff ( 128 MB)  Kernel direct-mapped ram
[   14.850000] XCE:   -- 0xc8800000 - 0xe7ffffff ( 504 MB)  Kernel vmalloc space
[   14.850000] XCE:   -- 0xe8000000 - 0xfeffffff ( 367 MB)  Kernel platform space
[   14.860000] XCE: CPU FEATURES:
[   14.860000] XCE:   -- I Cache:         enabled
[   14.870000] XCE:   -- D Cache:         enabled
[   14.870000] XCE:   -- Branch Predict:  disabled
[   14.880000] XCE:   -- MMU:             enabled
[   14.880000] XCE:   -- Alignment Abort: enabled
[   14.890000] XCE: BLPARAMS:   -- Loading properties [c4befefc].
[   14.900000] XCE: BLPARAMS:   -- MTD @ [c45c0c00].
[   14.900000] XCE: BLPARAMS: Locating parameter block...
[   14.910000] XCE: BLPARAMS: reading 2048 bytes @ a0000
[   14.910000] XCE: BLPARAMS:   -- Too many bit errors -- Can't correct!
[   14.920000] XCE: Loaded Property Size: 0
[   14.920000] XCE: No board spec found matching boardid '<NULL>' -- Using 'PP_GTI:2.0'
[   14.930000] XCE:   -- ICache Prefetch: enabled
[   14.940000] XCE:   -- DCache Prefetch: enabled
[   14.940000] XCE:   -- L2 Cache:        enabled
[   14.940000] XCE:   -- L2 Prefetch:     disabled
[   14.950000] XCE:   -- L2 Writethrough: disabled
[   14.950000] XCE:   -- Write Allocate:  disabled
[   14.960000] XCE:   -- Streaming:       disabled
[   14.960000] XCE: Current GPIO State:
[   14.970000] XCE:  GPIO L OUT:    0x01a18400
[   14.970000] XCE:  GPIO L OE:     0xfe004800
[   14.970000] XCE:  GPIO L BLINK:  0x00400000
[   14.980000] XCE:  GPIO L POL:    0x28000000
[   14.980000] XCE:  GPIO L IN:     0x11e00000
[   14.990000] XCE:  GPIO H OUT:    0x00020008
[   14.990000] XCE:  GPIO H OE:     0x00000005
[   14.990000] XCE:  GPIO H BLINK:  0x00000000
[   15.000000] XCE:  GPIO H POL:    0x00000000
[   15.000000] XCE:  GPIO H IN:     0x00000008
Success
Starting hbplug:             Success
/ # [   15.180000] XCE: BLPARAMS:   -- Loading properties [c4b5becc].
[   15.190000] XCE: BLPARAMS:   -- MTD @ [c45c0c00].
[   15.190000] XCE: BLPARAMS: Locating parameter block...
[   15.200000] XCE: BLPARAMS: reading 2048 bytes @ a0000
[   15.210000] XCE: BLPARAMS:   -- Too many bit errors -- Can't correct!
[   20.500000] XCE: XCE: LED -> DISCONNECTED
[   20.690000] EXT3-fs: INFO: recovery required on readonly filesystem.
[   20.700000] EXT3-fs: write access will be enabled during recovery.
[   21.350000] kjournald starting.  Commit interval 5 seconds
[   21.360000] EXT3-fs: recovery complete.
[   21.370000] EXT3-fs: mounted filesystem with writeback data mode.
[   21.490000] EXT3-fs: INFO: recovery required on readonly filesystem.
[   21.490000] EXT3-fs: write access will be enabled during recovery.
[   21.500000] kjournald starting.  Commit interval 5 seconds
[   21.510000] EXT3-fs: recovery complete.
[   21.510000] EXT3-fs: mounted filesystem with writeback data mode.
[   21.700000] kjournald starting.  Commit interval 5 seconds
[   21.710000] EXT3 FS on sda1, internal journal
[   21.710000] EXT3-fs: mounted filesystem with writeback data mode.
[   22.060000] kjournald starting.  Commit interval 5 seconds
[   22.080000] EXT3 FS on sda2, internal journal
[   22.080000] EXT3-fs: mounted filesystem with writeback data mode.

/ # 
/ # uname -a
Linux PogoplugMobile 2.6.31.8 #4 Tue Aug 23 13:00:50 PDT 2011 armv5tel GNU/Linux
/ # 
/ # cat /proc/mtd
dev:    size   erasesize  name
mtd0: 00200000 00020000 "u-boot"
mtd1: 00300000 00020000 "uImage"
mtd2: 00300000 00020000 "uImage2"
mtd3: 00800000 00020000 "failsafe"
mtd4: 07000000 00020000 "root"
/ # 
/ # cat /etc/fw_env.config
# Configuration file for fw_(printenv/saveenv) utility.
# Up to two entries are valid, in this case the redundant
# environment sector is assumed present.
# Notice, that the "Number of sectors" is ignored on NOR.

# MTD device name	Device offset	Env. size	Flash sector size	Number of sectors
/dev/mtd0		0xc0000		0x20000		0x20000
/ # 
/ # 
/ # 
Re: Pogo mobile nand bad block - installation failure
April 12, 2015 06:55PM
OK, so you are not booting into Arch. It's in the stock Pogo OS. But also it seems the Arch installation was done unsuccesfully, but not because of the bad block 157 in NAND (it's far from the first 1M).

To recover, do the following:

1. Download the 3.16 rootfs from the Kirkwood rootfs thread (use Rootfs Debian-3.16.0-kirkwood-tld-2, Updated 02 Sept 2014). Put this on the USB drive per instruction.
http://forum.doozan.com/read.php?2,12096

2. Boot into Pogo OS like you did above.

3. Kill Pogo process:
killall hbwd


4. Mount the USB rootfs

5. Follow the instruction in the u-boot thread and install the latest u-boot for Pogo V4:
http://forum.doozan.com/read.php?3,12381

Note: the nandwrite and flash_erase utilities are already inside the USB rootfs so you don't need to download them:
/usr/sbin/nandwrite
/usr/sbin/flash_erase

6. After installing u-boot, you could reboot. And it will boot into Debian on USB. If you are not sure about you should reboot, please post the entire installation log here (including the creation of the rootfs) and I'll look it over.

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



Edited 1 time(s). Last edit at 04/12/2015 06:57PM by bodhi.
Ok. i will have to do this later on (going to work now).
2 questions:

1. # cat /proc/mtd
gives a different data than what is specified, see here:

/ # cat /proc/mtd
dev: size erasesize name
mtd0: 00200000 00020000 "u-boot"
mtd1: 00300000 00020000 "uImage"
mtd2: 00300000 00020000 "uImage2"
mtd3: 00800000 00020000 "failsafe"
mtd4: 07000000 00020000 "root"
/ #

it is OK that mtd0 is 00200000 00020000 "u-boot" (and not 00100000 ....) ?

2. / # nanddump -nf mtd0 /dev/mtd0
is answered with
mtd0: Read-only file system
how can i overcome this?

Eyal
Re: Pogo mobile nand bad block - installation failure
April 12, 2015 11:27PM
E4691,

> 1. # cat /proc/mtd
> gives a different data than what is specified, see
> here:
>
> / # cat /proc/mtd
> dev: size erasesize name
> mtd0: 00200000 00020000 "u-boot"
> mtd1: 00300000 00020000 "uImage"
> mtd2: 00300000 00020000 "uImage2"
> mtd3: 00800000 00020000 "failsafe"
> mtd4: 07000000 00020000 "root"
> / #

This is correct for the Pogo Mobile.

>
> it is OK that mtd0 is 00200000 00020000 "u-boot"
> (and not 00100000 ....) ?
>

It's OK.

> 2. / # nanddump -nf mtd0 /dev/mtd0
> is answered with
> mtd0: Read-only file system
> how can i overcome this?
>
> Eyal

Dump to the USB drive. You were in the root directory (/). So if the USB was mounted as sda1 then

cd /media/sda1
/media/sda1/usr/sbin/nanddump -nf mtd0 /dev/mtd0

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

i did try to dump the nand to the usb, but with no success.
it seems that one of the issues of the bad system is it can not write or read to/from the usb. see here - end part of boot, finding the usb, my attempts to cd to it, and even fdisk p in order to see the partitions on the usb:

Starting hbplug: Success
/ # [ 14.840000] XCE: BLPARAMS: -- Loading properties [c4d3fecc].
[ 14.850000] XCE: BLPARAMS: -- MTD @ [c45b1c00].
[ 14.850000] XCE: BLPARAMS: Locating parameter block...
[ 14.860000] XCE: BLPARAMS: reading 2048 bytes @ a0000
[ 14.860000] XCE: BLPARAMS: -- Too many bit errors -- Can't correct!
[ 20.130000] XCE: XCE: LED -> DISCONNECTED
[ 20.290000] kjournald starting. Commit interval 5 seconds
[ 20.300000] EXT3 FS on sda1, internal journal
[ 20.300000] EXT3-fs: mounted filesystem with writeback data mode.
[ 20.620000] kjournald starting. Commit interval 5 seconds
[ 20.630000] EXT3 FS on sda2, internal journal
[ 20.630000] EXT3-fs: mounted filesystem with writeback data mode.

/ # cd /media/sda1
-/bin/sh: cd: can't cd to /media/sda1
/ # fdisk /dev/sda

Command (m for help): p

Disk /dev/sda: 8004 MB, 8004304896 bytes
247 heads, 62 sectors/track, 1020 cylinders
Units = cylinders of 15314 * 512 = 7840768 bytes

Device Boot Start End Blocks Id System
/dev/sda1 1 523 3998976 83 Linux
Partition 1 does not end on cylinder boundary
/dev/sda2 523 1021 3816704 83 Linux
Partition 2 does not end on cylinder boundary

Command (m for help): q

/ # cd /dev/sda1
-/bin/sh: cd: can't cd to /dev/sda1
/ # cd /dev/sda2
-/bin/sh: cd: can't cd to /dev/sda2

if i understand correctly, the nand dump is not a must.
And if this is the situation, how can i transfer the uBoot image to the nand? (meaning - how do i move the downloaded image to a directory were it can be found and extracted?)
any way you can think of in order amend it?

also
though it is stock pogo linux, i do have fw_printenv. nevertheless, ethaddr is not defined:
/ # fw_printenv
Warning: Bad CRC, using default environment
bootcmd=bootp; setenv bootargs root=/dev/nfs nfsroot=${serverip}:${rootpath} ip=${ipaddr}:${sem
bootdelay=5
baudrate=115200
/ #
anything to do with that?


regards
Re: Pogo mobile nand bad block - installation failure
April 13, 2015 03:15PM
E4691,

> if i understand correctly, the nand dump is not a
> must.

Correct. If you can't do it then it's OK.

> And if this is the situation, how can i transfer
> the uBoot image to the nand? (meaning - how do i
> move the downloaded image to a directory were it
> can be found and extracted?)
> any way you can think of in order amend it?
>

Do what I described above to prepare the USB rootfs using another Linux box (if you don't have one, then download Live CD to run on PC or Mac):
http://forum.doozan.com/read.php?3,21166,21172#msg-21172

Mount this USB rootfs on the Pogo so you can access it from there. Have you tried:

mkdir /tmp/sda1
mount /dev/sda1 /tmp/sda1

UPDATE:

And this is not good:
/dev/sda2 523 1021 3816704 83 Linux

Your USB drive contains other partition. You should reformat it a a single Ext3 partition and extract the rootfs to it per instruction.

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



Edited 3 time(s). Last edit at 04/13/2015 04:23PM by bodhi.
bodhi,

i am trying to prepare the USB rootfs, with version 3.16.0. after extracting, i am stuck on step 4: there is no zImage file or /dts directory for correct DTB file name.

?

Eyal
just tried mounting the usb as you suggested - it works....
thanks.
what is the preferred path now - rootfs Debian or reflashing the nand?

Eyal
Re: Pogo mobile nand bad block - installation failure
April 13, 2015 06:22PM
Quote

i am trying to prepare the USB rootfs, with version 3.16.0. after extracting, i am stuck on step 4: there is no zImage file or /dts directory for correct DTB file name.

The 3.16 rootfs is non-FDT so there is no DTB file. Each rootfs/kernel release has its own instruction. So when you use 3.16, you must follow the istruction in that section.

Quote

what is the preferred path now - rootfs Debian or reflashing the nand?

Look back the post above, I have laid out the steps above.

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

i finally have it working.
i greatly appreciate your help, you saved my Pogo. and you did it with patience.

now starts the hard work - installing Samba etc...

regards

eyal
Re: Pogo mobile nand bad block - installation failure
April 15, 2015 02:51PM
E4691,

Cool! glad it worked out well.

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