DM8168 uboot下烧写ubi文件系统

大家好，
我在uboot下烧写ubi文件系统（uboot、内核、文件系统都放在sd卡里），烧写完后启动时，报ubi错误，有没有哪位知道是啥问题啊？
现在用的这个ubi文件系统，在系统从sd卡起来后，在系统里烧写，启动是没问题的。
烧写步骤：
mmc rescan 0
mw.b 0x81000000 0xFF 0x26000
fatload mmc 0 0x81000000 u-boot.noxip.bin
nand erase 0x0 0x260000
nand write.i 0x81000000 0x0 0x260000
mw.b 0x81000000 0xFF 0x280000
fatload mmc 0 0x81000000 uImage
nand erase 0x580000 0x280000
nand write.i 0x81000000 0x580000 0x280000
mw.b 0x81000000 0xFF 0xF640000
fatload mmc 0 0x81000000 ubi.img
nand erase 0x9c0000 0xF640000
nand write.i 0x81000000 0x9c0000 0xF640000
错误如下：
U-Boot 2010.06 (Oct 15 2015 - 15:57:30)
ti8168-GP rev 2.1
HDVICP clk : 600MHz
L3 Fast clk : 520MHz
HDVPSS clk : 260MHz
Ducati M3 clk : 260MHz
DSP clk : 1000MHz
ARMclk : 987MHz
DDR clk : 796MHz
I2C: ready
DRAM: 2 GiB
NAND: HW ECC BCH8 Selected
256 MiB
MMC: OMAP SD/MMC: 0
:,;;:;:;;;;;;;;r;;:,;;:;:;;;;;;;;:,;;:;:;;;;;;;;:,;;:;:;;;;;;;;:;;;;;;;;:,;;:;:
;,;:::;;;;r;;;rssiSiS552X5252525259GX2X9hX9X9XX2325S55252i5:,;;:;:;;;;;;;;:,;;:
;:;;;;;;;rrssSsS52S22h52299GGAAMHMM#BBH#B#HMM#HMBA&&XX2255S2S5Si:,;;:;:;;;;;;;;
;:;;r;;rsrrriiXS5S329&A&MH#BMB#A&9XXA252GXiSXX39AAMMMBB&G22S5i2SSiiiisi:,;;:;:;
;;;;;r;rr2iisiih393HB#B#AA99i22irrrX3X52AGsisss2Xii2299HBMA&X2S5S5iSiisSsi:,;;:
r:r;rrsrsihXSi2&##MHB&Ahh3AGHGA9G9h&#H##@@@##MAMMXXX9SSS29&&HGGX2i5iisiiisisi:,
;;rrrrsSiiiA&ABH&A9GAGhAhBAMHA9HM@@@@@@@@@@@@@@@@@@@HHhAh2S2SX9&Gh22SSiisiiisii
r:rrssisiS2XM##&h3AGAX&3GG3Ssr5H@M#HM2; ;2X&&&MHMB###GBB#B&XXSSs529XX55iSsisisi
r;rsrisSi2XHAhX99A3XXG&&XS;:,rH#HGhAS @@@@3rs2XBM@@A552&&AHA2XiisSS252SSsisSs
r;issi5S22&&3iSSX292&hXsr;;:;h@&G339&S9@@@@2@MA&9&HB##Xris29ABMAAX2ir;rsSi5iss5
rrsSi2XhG&9GXh399&X99i;;;;;;r#H&293H9X#@@@@@@@B&9GhAH@XrrsrsiXABHB&HG2rr;rrSiSi
;:rsisS599&AA9XG&3A35r;:::;,;BMh&&2iX5A@@@@@@@&392X5GB2;;;r;iSX393A##A&Xi:::rsi
;:rss552222X553&XHMhir;;::,:,h#HhGSXhG3#@@@@#AXXS2XAHA;::;;;;ss55XShBA3239r:,;;
r;ii2S5SSi2i53hirsh2srr::,,,,;MMXX359&Ah3h&Si59SX99A#i:,::::;;sri2,.2r;:SGAr;,:
;:;rrrrssiriXGSi::shs;;;,,,:,,rBBA9h5s5h5iS5isi2SAHB5:,,,:::;rrs5&SrisSX5Srrr:,
;,r;;;;rsriSSrrrr;;5Xrr;;,:,,.,;9AA2SsisS5323XXXG9&i:.,,::;;r;;;srrrrrr;;:;::::
:,;r;r;rrissrrr;:;::;s;;;;,:,,..,r293h222hXXAAGGGX;:,,,:,:,::;:;::,:,,,,...,,,,
;,;;;;rrrrrrrrirr;,.,,:::::::,,,,.,;SX&ABAB2hhXir:,,.,,.,,:,,,,..,,,..,..,,,..:
:.:;:;;;:;;;;r;rrs;:.. ,,:::::,:,:,,.::rrsrr;;,,.......,..,....,,,,,,,...,.,,:,
:.:::,::::::;;r;rrr;:.......,.,.,,:::,,...............,,::.,,,,:,::,,:,:,,,:,;:
,.::,:,,,,,;;;;;;;;r;;::,..............................;;;:;::::,:::::::,:,:,,,
: ,,:,,,,,,,,,,,,,:;rrr;;:;,,,,,,,::,.,.:.,.,;s,:;;;;:;:;;;;;::::,:::,:::,:,:,:
,.,,,,,,,...,,.,,....................................:,............:,,,:,:,,,,,
Net: Detected MACID:ec:24:b8:c1:59:c0
Ethernet PHY: GENERIC @ 0x18
DaVinci EMAC
Hit any key to stop autoboot: 0
Loading from NAND 256MiB 3,3V 8-bit, offset 0x580000
Image Name: Linux-2.6.37
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 2573856 Bytes = 2.5 MiB
Load Address: c0008000
Entry Point: c0008000
## Booting kernel from Legacy Image at 81000000 ...
Image Name: Linux-2.6.37
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 2573856 Bytes = 2.5 MiB
Load Address: c0008000
Entry Point: c0008000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK
Starting kernel ...
Uncompressing Linux... done, booting the kernel.
Linux version 2.6.37-2.0.0 (yelei@yelei-vm) (gcc version 4.5.3 20110311 (prerelease) (GCC) ) #3 Tue Dec 1 19:41:35 CST 2015
CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=10c53c7f
CPU: VIPT nonaliasing data cache, VIPT aliasing instruction cache
Machine: ti8168etv
vram size = 52428800 at 0x0
ti81xx_reserve: ### Reserved DDR region @dff00000
reserved size = 52428800 at 0x0
FB: Reserving 52428800 bytes SDRAM for VRAM
Memory policy: ECC disabled, Data cache writeback
OMAP chip is TI8168 2.1
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 116992
Kernel command line: mem=512M ddr_mem=2048M console=ttyO0,115200n8 ubi.mtd=4,2048 root=ubi0:rootfs rootwait=1 rootfstype=ubifs rw ip=192.168.1.133:192.168.1.90:192.168.1.8:255.255.0.0::eth0:off vram=50M vmalloc=476M notifyk.vpssm3_sva=0xBFB00000
PID hash table entries: 2048 (order: 1, 8192 bytes)
Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
Memory: 460MB 1MB = 461MB total
Memory: 462000k/462000k available, 62288k reserved, 41984K highmem
Virtual kernel memory layout:
vector : 0xffff0000 - 0xffff1000 ( 4 kB)
fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB)
DMA : 0xffc00000 - 0xffe00000 ( 2 MB)
vmalloc : 0xda800000 - 0xf8000000 ( 472 MB)
lowmem : 0xc0000000 - 0xda400000 ( 420 MB)
pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB)
modules : 0xbf000000 - 0xbfe00000 ( 14 MB)
.init : 0xc0008000 - 0xc003f000 ( 220 kB)
.text : 0xc003f000 - 0xc04e3000 (4752 kB)
.data : 0xc04e4000 - 0xc052b280 ( 285 kB)
SLUB: Genslabs=11, HWalign=64, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
NR_IRQS:375
IRQ: Found an INTC at 0xfa200000 (revision 5.0) with 128 interrupts
Total of 128 interrupts on 1 active controller
GPMC revision 6.0
Trying to install interrupt handler for IRQ368
Trying to install interrupt handler for IRQ369
Trying to install interrupt handler for IRQ370
Trying to install interrupt handler for IRQ371
Trying to install interrupt handler for IRQ372
Trying to install interrupt handler for IRQ373
Trying to install interrupt handler for IRQ374
Trying to install type control for IRQ375
Trying to set irq flags for IRQ375
OMAP clockevent source: GPTIMER1 at 27000000 Hz
Console: colour dummy device 80x30
Calibrating delay loop... 986.31 BogoMIPS (lpj=4931584)
pid_max: default: 32768 minimum: 301
Security Framework initialized
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
devtmpfs: initialized
TI81XX: Map 0xdff00000 to 0xfe500000 for dram barrier
TI81XX: Map 0x40300000 to 0xfe600000 for sram barrier
omap_voltage_early_init: voltage driver support not added
regulator: core version 0.5
regulator: dummy:
NET: Registered protocol family 16
omap_voltage_domain_lookup: Voltage driver init not yet happened.Faulting!
omap_voltage_add_dev: VDD specified does not exist!
OMAP GPIO hardware version 0.1
OMAP GPIO hardware version 0.1
omap_mux_init: Add partition: #1: core, flags: 0
_omap_mux_get_by_name: Could not find signal i2c2_scl.i2c2_scl
_omap_mux_get_by_name: Could not find signal i2c2_sda.i2c2_sda
Cannot clk_get ck_32
pm_dbg_init: only OMAP3 supported
registered ti81xx_vpss device
registered ti81xx_vidout device
registered ti81xx on-chip HDMI device
registered ti81xx_fb device
bio: create slab at 0
SCSI subsystem initialized
u***core: registered new interface driver u***fs
u***core: registered new interface driver hub
u***core: registered new device driver u***
USBSS revision 4ea20809
registerd cppi-dma Intr @ IRQ 17
Cppi41 Init Done
omap_i2c omap_i2c.1: bus 1 rev4.0 at 100 kHz
omap_i2c omap_i2c.2: bus 2 rev4.0 at 100 kHz
Advanced Linux Sound Architecture Driver Version 1.0.23.
Switching to clocksource gp timer
mu***-hdrc: version 6.0, host, debug=0
mu***-hdrc mu***-hdrc.0: dma type: dma-cppi41
MUSB controller-0 revision 4ea20800
mu***-hdrc mu***-hdrc.0: MUSB HDRC host driver
mu***-hdrc mu***-hdrc.0: new USB bus registered, assigned bus number 1
u*** u***1: New USB device found, idVendor=1d6b, idProduct=0002
u*** u***1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
u*** u***1: Product: MUSB HDRC host driver
u*** u***1: Manufacturer: Linux 2.6.37-2.0.0 mu***-hcd
u*** u***1: SerialNumber: mu***-hdrc.0
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
mu***-hdrc mu***-hdrc.0: USB Host mode controller at da81e000 using DMA, IRQ 18
mu***-hdrc mu***-hdrc.1: dma type: dma-cppi41
MUSB controller-1 revision 4ea20800
mu***-hdrc mu***-hdrc.1: MUSB HDRC host driver
mu***-hdrc mu***-hdrc.1: new USB bus registered, assigned bus number 2
u*** u***2: New USB device found, idVendor=1d6b, idProduct=0002
u*** u***2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
u*** u***2: Product: MUSB HDRC host driver
u*** u***2: Manufacturer: Linux 2.6.37-2.0.0 mu***-hcd
u*** u***2: SerialNumber: mu***-hdrc.1
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 1 port detected
mu***-hdrc mu***-hdrc.1: USB Host mode controller at da828800 using DMA, IRQ 19
NET: Registered protocol family 2
IP route cache hash table entries: 4096 (order: 2, 16384 bytes)
TCP established hash table entries: 16384 (order: 5, 131072 bytes)
TCP bind hash table entries: 16384 (order: 4, 65536 bytes)
TCP: Hash tables configured (established 16384 bind 16384)
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
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
NetWinder Floating Point Emulator V0.97 (double precision)
PMU: registered new PMU device of type 0
omap-iommu omap-iommu.0: ducati registered
omap-iommu omap-iommu.1: sys registered
highmem bounce pool size: 64 pages
JFFS2 version 2.2. (NAND) 漏 2001-2006 Red Hat, Inc.
msgmni has been set to 820
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
register mise_device success
Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
omap_uart.0: ttyO0 at MMIO 0x48020000 (irq = 72) is a OMAP UART0
console [ttyO0] enabled
omap_uart.1: ttyO1 at MMIO 0x48022000 (irq = 73) is a OMAP UART1
omap_uart.2: ttyO2 at MMIO 0x48024000 (irq = 74) is a OMAP UART2
brd: module loaded
loop: module loaded
omap2-nand driver initializing
NAND device: Maf ID: 0xec, Chip ID: 0xda (Samsung, )
erasesize: 0x20000, writesize: 2048, oobsize: 64
omap2-nand: detected x8 NAND flash
Creating 5 MTD partitions on "omap2-nand.0":
0x000000000000-0x000000260000 : "U-Boot"
0x000000260000-0x000000280000 : "U-Boot Env"
0x000000280000-0x000000580000 : "U-Boot Logo"
0x000000580000-0x0000009c0000 : "Kernel"
0x0000009c0000-0x000010000000 : "File System"
UBI: attaching mtd4 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: max. sequence number: 0
UBI: volume 0 ("rootfs") re-sized from 1570 to 1927 LEBs
UBI: attached mtd4 to ubi0
UBI: MTD device name: "File System"
UBI: MTD device size: 246 MiB
UBI: number of good PEBs: 1969
UBI: number of bad PEBs: 1
UBI: number of corrupted 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: 1969
UBI: number of PEBs reserved for bad PEB handling: 38
UBI: max/mean erase counter: 1/0
UBI: image sequence number: 589971459
UBI: background thread "ubi_bgt0d" started, PID 37
davinci_mdio davinci_mdio.0: davinci mdio revision 1.6
davinci_mdio davinci_mdio.0: detected phy mask feffffff
davinci_mdio.0: probed
davinci_mdio davinci_mdio.0: phy[24]: device 0:18, driver Marvell 88E1111
u***core: registered new interface driver cdc_ether
u***core: registered new interface driver dm9601
u***core: registered new interface driver cdc_wdm
Initializing USB Mass Storage driver...
u***core: registered new interface driver u***-storage
USB Mass Storage support registered.
mice: PS/2 mouse device common for all mice
omap_rtc omap_rtc: rtc core: registered omap_rtc as rtc0
rtc-x1226 1-006f: x1226_validate_client: register=3f, zero pattern=0, value=91
rtc-x1226 1-006f: Failed to validate device.
i2c /dev entries driver
Linux video capture interface: v2.00
u***core: registered new interface driver uvcvideo
USB Video Class driver (v1.0.0)
OMAP Watchdog Timer Rev 0x00: initial timeout 60 sec
u***core: registered new interface driver u***hid
u***hid: USB HID core driver
notify_init : notify drivercreated for remote proc id 2 at physical Address 0xbfb00000
u***core: registered new interface driver snd-u***-audio
u***core: registered new interface driver snd-ua101
asoc: tlv320aic3x-hifi <-> davinci-mcasp.2 mapping ok
asoc: HDMI-DAI-CODEC <-> hdmi-dai mapping ok
ALSA device list:
#0: TI81XX ETV SOUND0
#1: TI81XX ETV SOUND1
nf_conntrack version 0.5.0 (7218 buckets, 28872 max)
ip_tables: (C) 2000-2006 Netfilter Core Team
TCP cubic registered
NET: Registered protocol family 17
VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 3
omap_voltage_late_init: Voltage driver support not added
Power Management for TI81XX.
drivers/rtc/hctosys.c: unable to open rtc device (rtc1)
davinci_mdio davinci_mdio.0: resetting idled controller
net eth0: attached PHY driver [Marvell 88E1111] (mii_bus:phy_addr=0:18, id=1410cc2)
IP-Config: Complete:
device=eth0, addr=192.168.1.133, mask=255.255.0.0, gw=192.168.1.8,
host=192.168.1.133, domain=, nis-domain=(none),
bootserver=192.168.1.90, rootserver=192.168.1.90, rootpath=
UBIFS: start fixing up free space
PHY: 0:18 - Link is Up - 100/Full
UBIFS: free space fixup complete
UBIFS: mounted UBI device 0, volume 0, name "rootfs"
UBIFS: file system size: 199225344 bytes (194556 KiB, 189 MiB, 1569 LEBs)
UBIFS: journal size: 9023488 bytes (8812 KiB, 8 MiB, 72 LEBs)
UBIFS: media format: w4/r0 (latest is w4/r0)
UBIFS: default compressor: lzo
UBIFS: reserved for root: 0 bytes (0 KiB)
VFS: Mounted root (ubifs filesystem) on device 0:15.
devtmpfs: mounted
Freeing init memory: 220K
INIT: version 2.88 booting
Mounting /dev/shm :
Mounting /dev/pts :
Mounting other filesystems :
Sync command ...
Starting udev
udev[65]: starting version 164
Starting Bootlog daemon: UBIFS error (pid 472): ubifs_read_node: bad node type (255 but expected 2)
UBIFS error (pid 472): ubifs_read_node: bad node at LEB 444:111384, LEB mapping status 0
UBIFS error (pid 472): ubifs_readdir: cannot find next direntry, error -22
UBIFS error (pid 472): ubifs_read_node: bad node type (255 but expected 2)
UBIFS error (pid 472): ubifs_read_node: bad node at LEB 444:111384, LEB mapping status 0
UBIFS error (pid 472): ubifs_readdir: cannot find next direntry, error -22
UBIFS error (pid 472): ubifs_read_node: bad node type (255 but expected 2)
UBIFS error (pid 472): ubifs_read_node: bad node at LEB 444:111384, LEB mapping status 0
UBIFS error (pid 472): ubifs_readdir: cannot find next direntry, error -22
UBIFS error (pid 472): ubifs_read_node: bad node type (255 but expected 2)
UBIFS error (pid 472): ubifs_read_node: bad node at LEB 444:111384, LEB mapping status 0
UBIFS error (pid 472): ubifs_readdir: cannot find next direntry, error -22
UBIFS error (pid 472): ubifs_read_node: bad node type (255 but expected 2)
UBIFS error (pid 472): ubifs_read_node: bad node at LEB 444:111384, LEB mapping status 0
UBIFS error (pid 472): ubifs_readdir: cannot find next direntry, error -22
UBIFS error (pid 472): ubifs_read_node: bad node type (255 but expected 2)
UBIFS error (pid 472): ubifs_read_node: bad node at LEB 444:111384, LEB mapping status 0
UBIFS error (pid 472): ubifs_readdir: cannot find next direntry, error -22
UBIFS error (pid 472): ubifs_read_node: bad node type (255 but expected 2)
UBIFS error (pid 472): ubifs_read_node: bad node at LEB 444:111384, LEB mapping status 0
UBIFS error (pid 472): ubifs_readdir: cannot find next direntry, error -22
UBIFS error (pid 472): ubifs_read_node: bad node type (255 but expected 2)
UBIFS error (pid 472): ubifs_read_node: bad node at LEB 444:111384, LEB mapping status 0
UBIFS error (pid 472): ubifs_readdir: cannot find next direntry, error -22
UBIFS error (pid 472): ubifs_read_node: bad node type (255 but expected 2)
UBIFS error (pid 472): ubifs_read_node: bad node at LEB 444:111384, LEB mapping status 0
UBIFS error (pid 472): ubifs_readdir: cannot find next direntry, error -22
UBIFS error (pid 472): ubifs_read_node: bad node type (255 but expected 2)
UBIFS error (pid 472): ubifs_read_node: bad node at LEB 444:111384, LEB mapping status 0
UBIFS error (pid 472): ubifs_readdir: cannot find next direntry, error -22
UBIFS error (pid 472): ubifs_read_node: bad node type (255 but expected 2)
UBIFS error (pid 472): ubifs_read_node: bad node at LEB 444:111384, LEB mapping status 0
UBIFS error (pid 472): ubifs_readdir: cannot find next direntry, error -22
UBIFS error (pid 472): ubifs_read_node: bad node type (255 but expected 2)
UBIFS error (pid 472): ubifs_read_node: bad node at LEB 444:111384, LEB mapping status 0
UBIFS error (pid 472): ubifs_readdir: cannot find next direntry, error -22
UBIFS error (pid 472): ubifs_read_node: bad node type (255 but expected 2)
UBIFS error (pid 472): ubifs_read_node: bad node at LEB 444:111384, LEB mapping status 0
UBIFS error (pid 472): ubifs_readdir: cannot find next direntry, error -22
UBIFS error (pid 472): ubifs_read_node: bad node type (255 but expected 2)
UBIFS error (pid 472): ubifs_read_node: bad node at LEB 444:111384, LEB mapping status 0
UBIFS error (pid 472): ubifs_readdir: cannot find next direntry, error -22
UBIFS error (pid 472): ubifs_read_node: bad node type (255 but expected 2)
UBIFS error (pid 472): ubifs_read_node: bad node at LEB 444:111384, LEB mapping status 0
UBIFS error (pid 472): ubifs_readdir: cannot find next direntry, error -22
UBIFS error (pid 472): ubifs_read_node: bad node type (255 but expected 2)
UBIFS error (pid 472): ubifs_read_node: bad node at LEB 444:111384, LEB mapping status 0
UBIFS error (pid 472): ubifs_readdir: cannot find next direntry, error -22
UBIFS error (pid 472): ubifs_read_node: bad node type (255 but expected 2)
UBIFS error (pid 472): ubifs_read_node: bad node at LEB 444:111384, LEB mapping status 0
UBIFS error (pid 472): ubifs_readdir: cannot find next direntry, error -22
UBIFS error (pid 472): ubifs_read_node: bad node type (255 but expected 2)
UBIFS error (pid 472): ubifs_read_node: bad node at LEB 444:111384, LEB mapping status 0
UBIFS error (pid 472): ubifs_readdir: cannot find next direntry, error -22
UBIFS error (pid 472): ubifs_read_node: bad node type (255 but expected 2)
UBIFS error (pid 472): ubifs_read_node: bad node at LEB 444:111384, LEB mapping status 0
UBIFS error (pid 472): ubifs_readdir: cannot find next direntry, error -22
UBIFS error (pid 472): ubifs_read_node: bad node type (255 but expected 2)
UBIFS error (pid 472): ubifs_read_node: bad node at LEB 444:111384, LEB mapping status 0
UBIFS error (pid 472): ubifs_readdir: cannot find next direntry, error -22
UBIFS error (pid 472): ubifs_read_node: bad node type (255 but expected 2)
UBIFS error (pid 472): ubifs_read_node: bad node at LEB 444:111384, LEB mapping status 0
UBIFS error (pid 472): ubifs_readdir: cannot find next direntry, error -22
UBIFS error (pid 472): ubifs_read_node: bad node type (255 but expected 2)
UBIFS error (pid 472): ubifs_read_node: bad node at LEB 444:111384, LEB mapping status 0
UBIFS error (pid 472): ubifs_readdir: cannot find next direntry, error -22
UBIFS error (pid 472): ubifs_read_node: bad node type (255 but expected 2)
UBIFS error (pid 472): ubifs_read_node: bad node at LEB 444:111384, LEB mapping status 0
UBIFS error (pid 472): ubifs_readdir: cannot find next direntry, error -22
UBIFS error (pid 472): ubifs_read_node: bad node type (255 but expected 2)
UBIFS error (pid 472): ubifs_read_node: bad node at LEB 444:111384, LEB mapping status 0
UBIFS error (pid 472): ubifs_readdir: cannot find next direntry, error -22
UBIFS error (pid 472): ubifs_read_node: bad node type (255 but expected 2)
UBIFS error (pid 472): ubifs_read_node: bad node at LEB 444:111384, LEB mapping status 0
UBIFS error (pid 472): ubifs_readdir: cannot find next direntry, error -22
UBIFS error (pid 472): ubifs_read_node: bad node type (255 but expected 2)
UBIFS error (pid 472): ubifs_read_node: bad node at LEB 444:111384, LEB mapping status 0
UBIFS error (pid 472): ubifs_readdir: cannot find next direntry, error -22
UBIFS error (pid 472): ubifs_read_node: bad node type (255 but expected 2)
UBIFS error (pid 472): ubifs_read_node: bad node at LEB 444:111384, LEB mapping status 0
UBIFS error (pid 472): ubifs_readdir: cannot find next direntry, error -22
UBIFS error (pid 472): ubifs_read_node: bad node type (255 but expected 2)
UBIFS error (pid 472): ubifs_read_node: bad node at LEB 444:111384, LEB mapping status 0
UBIFS error (pid 472): ubifs_readdir: cannot find next direntry, error -22
UBIFS error (pid 472): ubifs_read_node: bad node type (255 but expected 2)
UBIFS error (pid 472): ubifs_read_node: bad node at LEB 444:111384, LEB mapping status 0
UBIFS error (pid 472): ubifs_readdir: cannot find next direntry, error -22
UBIFS error (pid 472): ubifs_read_node: bad node type (255 but expected 2)
UBIFS error (pid 472): ubifs_read_node: bad node at LEB 444:111384, LEB mapping status 0
UBIFS error (pid 472): ubifs_readdir: cannot find next direntry, error -22
UBIFS error (pid 472): ubifs_read_node: bad node type (255 but expected 2)
UBIFS error (pid 472): ubifs_read_node: bad node at LEB 444:111384, LEB mapping status 0
UBIFS error (pid 472): ubifs_readdir: cannot find next direntry, error -22
UBIFS error (pid 472): ubifs_read_node: bad node type (255 but expected 2)
UBIFS error (pid 472): ubifs_read_node: bad node at LEB 444:111384, LEB mapping status 0
UBIFS error (pid 472): ubifs_readdir: cannot find next direntry, error -22
UBIFS error (pid 472): ubifs_read_node: bad node type (255 but expected 2)
UBIFS error (pid 472): ubifs_read_node: bad node at LEB 444:111384, LEB mapping status 0
UBIFS error (pid 472): ubifs_readdir: cannot find next direntry, error -22
UBIFS error (pid 472): ubifs_read_node: bad node type (255 but expected 2)
UBIFS error (pid 472): ubifs_read_node: bad node at LEB 444:111384, LEB mapping status 0
UBIFS error (pid 472): ubifs_readdir: cannot find next direntry, error -22
UBIFS error (pid 472): ubifs_read_node: bad node type (255 but expected 2)

0