GSM Firmware Flashed, now UBIFS problem and Kernel Panic

[Thomas Franck]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi..

I appreciate all the help you're all giving me..


On 04/14/2011 06:30 PM, sferic wrote:
> to mount a ubifs you should give another way a try:
> 
> cat /proc/mtd
> ubiattach /dev/ubi_ctrl -m 6 -d 0 -O 2048
> mkdir /tmp/qtmoko
> mount -t ubifs ubi0_0 /tmp/qtmoko/

I tried that just now.. same result, though.. :(

root at neo:~# cat /proc/mtd
dev:    size   erasesize  name
mtd0: 00200000 00010000 "physmap-flash.0"
mtd1: 00040000 00020000 "qi"
mtd2: 00040000 00020000 "depr-ub-env"
mtd3: 00800000 00020000 "kernel"
mtd4: 000a0000 00020000 "depr"
mtd5: 00040000 00020000 "identity-ext2"
mtd6: 0f6a0000 00020000 "rootfs"
root at neo:~# ubiattach /dev/ubi_ctrl -m 6 -d 0 -O 2048
UBI device number 0, total 1972 LEBs (250396672 bytes, 238.8 MiB),
available 0 LEBs (0 bytes), LEB size 126976 bytes (124.0 KiB)
root at neo:~# mkdir /tmp/qtmoko
root at neo:~# mount -t ubifs ubi0_0 /tmp/qtmoko/
mount: wrong fs type, bad option, bad superblock on ubi0_0,
       missing codepage or helper program, or other error
       (for several filesystems (e.g. nfs, cifs) you might
       need a /sbin/mount.<type> helper program)
       In some cases useful info is found in syslog - try
       dmesg | tail  or so


here's my dmesg about it:
[ 1255.130000] UBI: attaching mtd6 to ubi0
[ 1255.130000] UBI: physical eraseblock size:   131072 bytes (128 KiB)
[ 1255.130000] UBI: logical eraseblock size:    126976 bytes
[ 1255.130000] UBI: smallest flash I/O unit:    2048
[ 1255.130000] UBI: sub-page size:              512
[ 1255.130000] UBI: VID header offset:          2048 (aligned 2048)
[ 1255.130000] UBI: data offset:                4096
[ 1255.460000] UBI: attached mtd6 to ubi0
[ 1255.460000] UBI: MTD device name:            "rootfs"
[ 1255.460000] UBI: MTD device size:            246 MiB
[ 1255.460000] UBI: number of good PEBs:        1972
[ 1255.460000] UBI: number of bad PEBs:         1
[ 1255.460000] UBI: max. allowed volumes:       128
[ 1255.460000] UBI: wear-leveling threshold:    4096
[ 1255.460000] UBI: number of internal volumes: 1
[ 1255.460000] UBI: number of user volumes:     1
[ 1255.460000] UBI: available PEBs:             0
[ 1255.460000] UBI: total number of reserved PEBs: 1972
[ 1255.460000] UBI: number of PEBs reserved for bad PEB handling: 19
[ 1255.460000] UBI: max/mean erase counter: 15/4
[ 1255.460000] UBI: image sequence number: 0
[ 1255.470000] UBI: background thread "ubi_bgt0d" started, PID 1413
[ 1269.120000] UBIFS error (pid 1416): ubifs_read_node: bad node type
(255 but expected 6)
[ 1269.120000] UBIFS error (pid 1416): ubifs_read_node: bad node at LEB 0:0


I worry that I lost my data here.. :'( so bad..

here[1] it's written that UBIFS is so robust, though, and virtually
indestructible.. that website states that the tools to recover have not
been written yet, though.. is that so?

[1] http://www.linux-mtd.infradead.org/doc/ubifs.html

Cheers,
- -- 
Thomas

- -~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~
...speed is a virtue, but we have finally reached the point of
computational affluence where other things are more important.
  - Dan Ingalls
- -~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJNqAyVAAoJEOLs7+64bK+eBSYH/Al498zjeYs0sgONbYdNmO64
Kkv3GGvlBuhP7B0IPzGRa2d+kXASkU4krYgnUIbSUJRRfiZenhY06Vw8Pu19ZF6l
O0vlXAfkhfAoSOlpnmz0DxIeLkF6Ga71r783OFsXNau5I+2UTtba7AXeQu8ePCk0
TwDKF+K2XHDgRUp206A3N3k8UOx8GSlDR4VtUaj5hl+2tDqhPd1A3joDn2vsWATW
NH/pFHHunLS2YkQy5bSKjZRfvPFO6bAKGknUoorSOMPyZaTMEwpeqS/hhZvcvMOm
TiSW+iqm1Cru237jpOPucb6n4+CuhpVSM7jAKTs75BL2lBAUdc5Y6vCt07MqKgI=
=M2Bt
-----END PGP SIGNATURE-----