File System Error...can not boot

Are you stuck at a particular point, can't find the answer elsewhere, here's the place to ask.
Posts: 1
Joined: Sat Apr 02, 2016 1:12 am

File System Error...can not boot

Postby kalux » Tue Apr 05, 2016 6:51 am

Followed the pin29 procedure to root my hub.... executed setenv .... command.. that was ok I believe. After executing "nand read ${loadaddr} app-kernel 0x00400000 && bootm ${loadaddr}".
After this executes, it shortly stops... the results are as follows:

Code: Select all

=> nand read ${loadaddr} app-kernel 0x00400000 && bootm ${loadaddr}

NAND read: device 0 offset 0x2b00000, size 0x400000
 4194304 bytes read: OK
## Booting kernel from Legacy Image at 42000000 ...
   Image Name:   Linux-
   Created:      2014-04-30   3:15:35 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    1928460 Bytes = 1.8 MiB
   Load Address: 40008000
   Entry Point:  40008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
Linux version (saurabh@localhost.localdomain) (gcc version 4.4.4 (4.4.4_09.06.2010) ) #32 PREEMPT Tue Apr 29 23:15:31 EDT 2014
CPU: ARM926EJ-S [41069265] revision 5 (ARMv5TEJ), cr=00053177
CPU: VIVT data cache, VIVT instruction cache
Machine: Freescale MX28EVK board
Memory policy: ECC disabled, Data cache writeback
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 16256
Kernel command line: noinitrd console=ttyAM0,115200 rootfstype=ubifs ubi.mtd=5 root=ubi0:rootfs rw gpmi init=/bin/sh
PID hash table entries: 256 (order: -2, 1024 bytes)
Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
Memory: 64MB = 64MB total
Memory: 60784k/60784k available, 4752k reserved, 0K highmem
Virtual kernel memory layout:
    vector  : 0xffff0000 - 0xffff1000   (   4 kB)
    fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
    DMA     : 0xfde00000 - 0xffe00000   (  32 MB)
    vmalloc : 0x84800000 - 0xf0000000   (1720 MB)
    lowmem  : 0x80000000 - 0x84000000   (  64 MB)
    modules : 0x7f000000 - 0x80000000   (  16 MB)
      .init : 0x80008000 - 0x80027000   ( 124 kB)
      .text : 0x80027000 - 0x803b6000   (3644 kB)
      .data : 0x803b6000 - 0x803deec0   ( 164 kB)
SLUB: Genslabs=11, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
Hierarchical RCU implementation.
        RCU-based detection of stalled CPUs is disabled.
        Verbose stalled-CPUs detection is disabled.
Console: colour dummy device 80x30
console [ttyAM0] enabled
Calibrating delay loop... 226.09 BogoMIPS (lpj=1130496)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
regulator: core version 0.5
NET: Registered protocol family 16
regulator: vddd: 800 <--> 1575 mV at 1500 mV fast normal
regulator: vdddbo: 800 <--> 1575 mV fast normal
regulator: vdda: 1500 <--> 2275 mV at 1800 mV fast normal
vddio = 3380000, val=10
regulator: vddio: 2880 <--> 3680 mV at 3380 mV fast normal
regulator: overall_current: fast normal
regulator: vbus5v:
regulator: mxs-duart-1: fast normal
regulator: mxs-bl-1: fast normal
regulator: mxs-i2c-1: fast normal
regulator: mmc_ssp-1: fast normal
regulator: mmc_ssp-2: fast normal
regulator: charger-1: fast normal
regulator: power-test-1: fast normal
regulator: cpufreq-1: fast normal
i.MX IRAM pool: 124 KB@0x84820000
Initializing GPMI pins
bio: create slab <bio-0> at 0
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
cfg80211: Calling CRDA to update world regulatory domain
Switching to clocksource mxs clock source
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 2048 (order: 2, 16384 bytes)
TCP bind hash table entries: 2048 (order: 1, 8192 bytes)
TCP: Hash tables configured (established 2048 bind 2048)
TCP reno registered
UDP hash table entries: 256 (order: 0, 4096 bytes)
UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
NET: Registered protocol family 1
Bus freq driver module loaded
mxs_cpu_init: cpufreq init finished
Slow work thread pool: Starting up
Slow work thread pool: Ready
fuse init (API version 7.14)
msgmni has been set to 118
alg: No test for stdrng (krng)
cryptodev: driver loaded.
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
mxs-duart.0: ttyAM0 at MMIO 0x80074000 (irq = 47) is a DebugUART
mxs-auart.0: ttySP0 at MMIO 0x8006a000 (irq = 112) is a mxs-auart.0
Found APPUART 3.1.0
mxs-auart.1: ttySP1 at MMIO 0x8006c000 (irq = 113) is a mxs-auart.1
Found APPUART 3.1.0
mxs-auart.2: ttySP2 at MMIO 0x8006e000 (irq = 114) is a mxs-auart.2
Found APPUART 3.1.0
mxs-auart.3: ttySP3 at MMIO 0x80070000 (irq = 115) is a mxs-auart.3
Found APPUART 3.1.0
mxs-auart.4: ttySP4 at MMIO 0x80072000 (irq = 116) is a mxs-auart.4
Found APPUART 3.1.0
loop: module loaded
NFC: Version 1, 8-chip GPMI and BCH
Boot ROM: Version 1, Single-chip boot area, block mark swapping supported
Scanning for NAND Flash chips...
NAND device: Manufacturer ID: 0x01, Chip ID: 0xf1 (AMD NAND 128MiB 3,3V 8-bit)
NAND Flash Device Information
Manufacturer      : AMD (0x01)
Device Code       : 0xf1
Cell Technology   : SLC
Chip Size         : 128 MiB
Pages per Block   : 64
Page Geometry     : 2048+64
ECC Strength      : 4 bits
ECC Size          : 512 B
Data Setup Time   : 10 ns
Data Hold Time    : 5 ns
Address Setup Time: 10 ns
GPMI Sample Delay : 6 ns
tREA              : Unknown
tRLOH             : Unknown
tRHOH             : Unknown
Description       : S34ML01G1
Physical Geometry
Chip Count             : 1
Page Data Size in Bytes: 2048 (0x800)
Page OOB Size in Bytes : 64
Block Size in Bytes    : 131072 (0x20000)
Block Size in Pages    : 64 (0x40)
Chip Size in Bytes     : 134217728 (0x8000000)
Chip Size in Pages     : 65536 (0x10000)
Chip Size in Blocks    : 1024 (0x400)
Medium Size in Bytes   : 134217728 (0x8000000)
NFC Geometry
ECC Algorithm          : BCH
ECC Strength           : 8
Page Size in Bytes     : 2112
Metadata Size in Bytes : 10
ECC Chunk Size in Bytes: 512
ECC Chunk Count        : 4
Payload Size in Bytes  : 2048
Auxiliary Size in Bytes: 16
Auxiliary Status Offset: 12
Block Mark Byte Offset : 1999
Block Mark Bit Offset  : 0
Boot ROM Geometry
Boot Area Count            : 1
Boot Area Size in Bytes    : 3145728 (0x300000)
Stride Size in Pages       : 64
Search Area Stride Exponent: 2
Scanning device for bad blocks
Boot area protection is enabled.
Creating 6 MTD partitions on "gpmi-nfc-main":
0x000000000000-0x000000300000 : "gpmi-nfc-0-boot"
0x000000300000-0x000000700000 : "updater-kernel"
0x000000700000-0x000002300000 : "updater-rootfs"
0x000002300000-0x000002b00000 : "database"
0x000002b00000-0x000003300000 : "app-kernel"
0x000003300000-0x000008000000 : "gpmi-nfc-general-use"
cmdlinepart partition parsing not available
UBI: attaching mtd5 to ubi0
UBI: physical eraseblock size:   131072 bytes (128 KiB)
UBI: logical eraseblock size:    126976 bytes
UBI: smallest flash I/O unit:    2048
UBI: VID header offset:          2048 (aligned 2048)
UBI: data offset:                4096
UBI: attached mtd5 to ubi0
UBI: MTD device name:            "gpmi-nfc-general-use"
UBI: MTD device size:            77 MiB
UBI: number of good PEBs:        616
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: 616
UBI: number of PEBs reserved for bad PEB handling: 6
UBI: max/mean erase counter: 6/3
UBI: image sequence number: 1028287236
UBI: background thread "ubi_bgt0d" started, PID 922
 ubiblka: unknown partition table
mice: PS/2 mouse device common for all mice
MXS RTC driver v1.0 hardware v2.3.0
mxs-rtc mxs-rtc.0: rtc core: registered mxs-rtc as rtc0
mxs watchdog: initialized, heartbeat 19 sec
mxs-mmc: MXS SSP Controller MMC Interface driver
__mxs_reset_block(f0010000): timeout when resetting
mxs-mmc mxs-mmc.0: mmc0: MXS SSP MMC DMAIRQ 82 ERRIRQ 96
TCP cubic registered
NET: Registered protocol family 17
NET: Registered protocol family 15
lib80211: common routines for IEEE802.11 drivers
mxs-rtc mxs-rtc.0: setting system clock to 1970-01-01 00:37:44 UTC (2264)
mmc0: queuing unknown CIS tuple 0x80 (7 bytes)
mmc0: queuing unknown CIS tuple 0x80 (6 bytes)
mmc0: new high speed SDIO card at address 0001
UBIFS: recovery needed
UBIFS: recovery completed
UBIFS: mounted UBI device 0, volume 0, name "rootfs"
UBIFS: file system size:   75550720 bytes (73780 KiB, 72 MiB, 595 LEBs)
UBIFS: journal size:       9023488 bytes (8812 KiB, 8 MiB, 72 LEBs)
UBIFS: media format:       w4/r0 (latest is w4/r0)
UBIFS: default compressor: zlib
UBIFS: reserved for root:  0 bytes (0 KiB)
VFS: Mounted root (ubifs filesystem) on device 0:11.
Freeing init memory: 124K
UBIFS error (pid 1): ubifs_read_node: bad node type (255 but expected 9)
UBIFS error (pid 1): ubifs_read_node: bad node at LEB 247:35424
UBIFS error (pid 1): ubifs_iget: failed to read inode 703, error -22
UBIFS error (pid 1): ubifs_lookup: dead directory entry 'lib', error -22
UBIFS warning (pid 1): ubifs_ro_mode: switched to read-only mode, error -22
Failed to execute /bin/sh.  Attempting defaults...
Kernel panic - not syncing: No init found.  Try passing init= option to kernel. See Linux Documentation/init.txt for guidance.
[<8002b9d0>] (dump_backtrace+0x0/0x110) from [<802d90e0>] (dump_stack+0x18/0x1c)
 r7:00000013 r6:80046f38 r5:80022248 r4:803dfd58
[<802d90c8>] (dump_stack+0x0/0x1c) from [<802d915c>] (panic+0x78/0xfc)
[<802d90e4>] (panic+0x0/0xfc) from [<800275fc>] (init_post+0xb4/0xdc)
 r3:00000000 r2:83ef6100 r1:83ef6300 r0:8035bab2
[<80027548>] (init_post+0x0/0xdc) from [<800084fc>] (kernel_init+0x12c/0x170)
 r5:80022248 r4:803def40
[<800083d0>] (kernel_init+0x0/0x170) from [<80046f38>] (do_exit+0x0/0x6a4)
 r5:800083d0 r4:00000000

the hub displays a white light.

Any suggestions and specific instructions would be greatly appreciated!

Posts: 6
Joined: Thu Sep 01, 2016 2:07 am

Re: File System Error...can not boot

Postby nepto » Wed Sep 14, 2016 5:35 am

This exactly happened to me, but because it is late in the night, I did only this brief investigation. Tomorrow I will try to find more (if I will have time).

Yours and mine root filesystem on mtd5 aka gpmi-nfc-general-use gets corrupted. The reason for this is unknown. To find out I will need a brief history of your Wink Hub, because this may be related to 2015-04-SNAFU.

What you can do is boot into updater using this command in your bootloader:

Code: Select all

=> run boot_updater

Log in (root & empty password), and once there, you can try to mount it manually. However it would probably not work. But give it a try:

Code: Select all

mkdir /tmp/work/
ubiattach -p /dev/mtd5
mount -t ubifs ubi2:rootfs /tmp/work/

If it gets mounted successfully, than it means filesystem get repaired (on mount) and next boot should be fine.

If mount failed like this, then, well, we have a problem:

Code: Select all

[root@flex-dvt ~]# mount -t ubifs ubi2:rootfs /tmp/work/
UBIFS: recovery needed
UBI error: ubi_io_read: error -74 while reading 106496 bytes from PEB 401:24576, read 106496 bytes
UBIFS error (pid 5150): ubifs_scanned_corruption: corruption at LEB 583:45056
UBIFS error (pid 5150): ubifs_recover_leb: LEB 583 scanning failed
mount: mounting ubi2:rootfs on /tmp/work/ failed: Structure needs cleaning

What makes this situation especially difficult is that there is no file-system recovery for UBIFS. So no fsck.ubifs, see this thread: ... 57710.html

What I am thinking could work is to re-create clean partition and run upgrade process, which will pretty much recreate content. But I am not sure if everything would be recreated. If not, then we need to create that damn mtd5 from mtd2. Or someone here could be so kind and provide mtd5 image. There are definitely few some options.

Site Admin
Posts: 107
Joined: Wed Jan 07, 2015 10:02 am

Re: File System Error...can not boot

Postby CloneNum3 » Wed Sep 14, 2016 6:01 am

If you can boot into the updater partition, then go straight to the upgrade. The upgrade doesn't pick and choose what files to update, it actually wipes out the entire partition replacing it with a new one. So updating the primary from the update boot should get you going.

If it thinks you are already current, change the cf_ files in /database to an older version so it will think you need an update.

If your updater partition is pre-snafu, update the bottom of /root/platform/updater.config (from memory, may not be exact name) at the bottom where it sets the curl arguments and ADD --insecure

Site Admin
Posts: 107
Joined: Wed Jan 07, 2015 10:02 am

Re: File System Error...can not boot

Postby CloneNum3 » Wed Sep 14, 2016 6:05 am

I have most of the various images... Root, updater, kernel, etc... Ranging back to the early days. I even have the beta, staging, and other random non-production ones too.

If anyone wants a hub that follows the beta or staging, I'll list a rooted hub on eBay for you the way you want it.

Posts: 6
Joined: Thu Sep 01, 2016 2:07 am

Re: File System Error...can not boot

Postby nepto » Wed Sep 28, 2016 1:46 am

CloneNum3 wrote:If your updater partition is pre-snafu, update the bottom of /root/platform/updater.config (from memory, may not be exact name) at the bottom where it sets the curl arguments and ADD --insecure

Just a quick update, that all the instructions in your post worked like a charm. Thank you!

Yes, when it is pre-SNAFU, it is bit more difficult, but definitely doable. Still better than shipping Wink Hub to factory -- saving some shipping costs for Wink, hope they appreciate:)

Return to “Help me, I can't do xyz”

Who is online

Users browsing this forum: No registered users and 1 guest