Re: GSM Firmware Flashed, now UBIFS problem and Kernel Panic

2011-05-08 Thread Noel
 Anyway it could be a problem related to ubifs instability, which is a
 topic recently discussed in mailing list [1]. You can follow that tread
 and try to:

I don't think it's releated to ubifs stability.

It happens to me every time I boot from SD card with a linux kernel
different (at least older) then qtmoko/v31/nand one.

Who changes root partition (nand) in this case? Qi? The kernel from SD
card, even if it doesn't know about ubifs format? And for what? To
change a mount counter or last mount time?

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: GSM Firmware Flashed, now UBIFS problem and Kernel Panic

2011-05-08 Thread Jens Seidel
Am 08.05.2011 11:23, schrieb Noel:
 Anyway it could be a problem related to ubifs instability, which is a
 topic recently discussed in mailing list [1]. You can follow that tread
 and try to:

 It happens to me every time I boot from SD card with a linux kernel
 different (at least older) then qtmoko/v31/nand one.

I can confirm this. My ubifs errors always happened after I started
Debian from SD card.

PS: I have a nanddump of the faulty images. According the ubifs FAQ one
should not bother the developers with errors resulting from using old
ubifs code, so I haven't send it to anyone ...

Jens

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: GSM Firmware Flashed, now UBIFS problem and Kernel Panic

2011-04-15 Thread giacomo 'giotti' mariani

Hello,

If there is a better solution that preserves the FS,
  I would be happy to learn about it.
  

  I wonder if it would be possible to boot into a distro on the sd card
  and mount the nand partitions. Then you could save /home. Just a thought.
  

  Yes, it is: just mount  -t jffs2 /dev/mtdblock6 /mountpoint
  

  Thank you all for your input..

  I put a qtmoko v35 on an SD card.. an on terminal I did:

  mkdir /home/root/nandfs
  mount -t ubifs /dev/mtdblock6 /home/root/nandfs

  but sadly that doesn't work.. dmesg tells me:

  UBIFS error: ubifs_get_sb: cannot open /dev/mtdblock6, error -22

  Any ideas?

  Cheers,
  

I think you need to attach the ubifs before mounting.  See
http://openmoko-public-mailinglists.1958.n2.nabble.com/UBI-success-story-td4218730.html
for the steps, though unless you want to reformat, you shouldn't follow
all of them.

Ben

Alternatively, you can follow http://wiki.openmoko.org/wiki/UBIFS :
# apt-get install mtd-utils # if you are on qtmoko

# ubiattach /dev/ubi_ctrl -O 2048 -m 6
# mount -t ubifs ubi0:om-gta02-rootfs /media/om
# ls /media/om

Anyway it could be a problem related to ubifs instability, which is a 
topic recently discussed in mailing list [1]. You can follow that tread 
and try to:



Guy who'll have ubifs trubles please try to:

1. disable bulk read in fstab and check if problem will still exist.
2. do nanddump and post it or try to reproduce bug with nandsim. (i
guess ubifs guys can fix problem in case if such dump exist quite fast)


Regards
  Giacomo


[1] http://www.mail-archive.com/community@lists.openmoko.org/msg62518.html

--
##
giacomo 'giotti' mariani
gpg --keyserver pool.sks-keyservers.net --recv-key 0x99bfa859
O  ASCII ribbon campaign: stop HTML mail
www.asciiribbon.org
##


___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: GSM Firmware Flashed, now UBIFS problem and Kernel Panic

2011-04-15 Thread 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@neo:~# cat /proc/mtd
dev:size   erasesize  name
mtd0: 0020 0001 physmap-flash.0
mtd1: 0004 0002 qi
mtd2: 0004 0002 depr-ub-env
mtd3: 0080 0002 kernel
mtd4: 000a 0002 depr
mtd5: 0004 0002 identity-ext2
mtd6: 0f6a 0002 rootfs
root@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@neo:~# mkdir /tmp/qtmoko
root@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.13] UBI: attaching mtd6 to ubi0
[ 1255.13] UBI: physical eraseblock size:   131072 bytes (128 KiB)
[ 1255.13] UBI: logical eraseblock size:126976 bytes
[ 1255.13] UBI: smallest flash I/O unit:2048
[ 1255.13] UBI: sub-page size:  512
[ 1255.13] UBI: VID header offset:  2048 (aligned 2048)
[ 1255.13] UBI: data offset:4096
[ 1255.46] UBI: attached mtd6 to ubi0
[ 1255.46] UBI: MTD device name:rootfs
[ 1255.46] UBI: MTD device size:246 MiB
[ 1255.46] UBI: number of good PEBs:1972
[ 1255.46] UBI: number of bad PEBs: 1
[ 1255.46] UBI: max. allowed volumes:   128
[ 1255.46] UBI: wear-leveling threshold:4096
[ 1255.46] UBI: number of internal volumes: 1
[ 1255.46] UBI: number of user volumes: 1
[ 1255.46] UBI: available PEBs: 0
[ 1255.46] UBI: total number of reserved PEBs: 1972
[ 1255.46] UBI: number of PEBs reserved for bad PEB handling: 19
[ 1255.46] UBI: max/mean erase counter: 15/4
[ 1255.46] UBI: image sequence number: 0
[ 1255.47] UBI: background thread ubi_bgt0d started, PID 1413
[ 1269.12] UBIFS error (pid 1416): ubifs_read_node: bad node type
(255 but expected 6)
[ 1269.12] 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-

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: GSM Firmware Flashed, now UBIFS problem and Kernel Panic

2011-04-15 Thread Ivan Matveev


 root@neo:~# cat /proc/mtd
 dev:size   erasesize  name
 mtd0: 0020 0001 physmap-flash.0
 mtd1: 0004 0002 qi
 mtd2: 0004 0002 depr-ub-env
 mtd3: 0080 0002 kernel
 mtd4: 000a 0002 depr
 mtd5: 0004 0002 identity-ext2
 mtd6: 0f6a 0002 rootfs
 root@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@neo:~# mkdir /tmp/qtmoko
 root@neo:~# mount -t ubifs ubi0_0 /tmp/qtmoko/

You can try:
mount -t ubifs /dev/mtdblock6 /tmp/qtmoko/



___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


GSM Firmware Flashed, now UBIFS problem and Kernel Panic

2011-04-14 Thread Thomas Franck
Hi..

Please advice if you can.. Stupidly I didn't make any backup prior to
this.. (well, nothing recent anyways)

my QtMoko is on NAND and I just used the µSD Flashing Method as
recommended in the Wiki to update my GSM Firmware from Moko10 to Moko11..

It finshed with D_O_N_E and showed the green Angstrom login, then I
removed the battery and flash SD.. put my SIM and storage SD back in and
was going to boot into QtMoko again, but I get:

---88-
UBIFS error (pid 1): ubifs_read_node: bad node type (255 but expected 6)
UBIFS error (pid 1): ubifs_Read_node: bad node at LEB 0:0
Kernel panic - not syncing: VFS: Unable to mount fs on unknown-block(0,0)
---88-

I think the flashing just messes with the GSM chip, so despite the
subject of the mail, I believe it might be something to do with what
happened before the flashing:

I shut down Qt, took my SIM an SD out.. powered up - but forgot to press
AUX.. so I removed the battery when I saw the first text line from
normal boot (I guess it's a Kernel loading message or so).. then I
plugged in again and carried on with AUX and flashed..

Any ideas on this problem? I there any way to repair that FS?

Cheers,
-- 
Thomas

-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~
A distributed system is one in which the failure of a computer you
didn't even know existed can render your own computer unusable.
  - Leslie Lamport
-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: GSM Firmware Flashed, now UBIFS problem and Kernel Panic

2011-04-14 Thread Raphael Wimmer

Hi Thomas,


On Thu, 14 Apr 2011 11:05:38 +0200, Thomas Franck thomas.fra...@gmx.com  
wrote:

[...]

---88-
UBIFS error (pid 1): ubifs_read_node: bad node type (255 but expected 6)
UBIFS error (pid 1): ubifs_Read_node: bad node at LEB 0:0
Kernel panic - not syncing: VFS: Unable to mount fs on unknown-block(0,0)
---88-

[...]


Any ideas on this problem? I there any way to repair that FS?


I had the same probem when upgrading QtMoko a few days ago. Regardless of  
what fs image I flashed, I would get these error messages.


Completely erasing the NAND allowed me to re-install without problems. Of  
course, it means that your data will be gone. I did not find an easier  
solution, and actually had no important data on the phone.
I followed more or less the steps for clearing bad blocks [1] and threw in  
an erase command somewhere. Unfortunately, I do not remember the details.  
The NOR bootloader offers a help command, however.


If there is a better solution that preserves the FS, I would be happy to  
learn about it.


Raphael

[1] http://wiki.openmoko.org/wiki/NAND_bad_blocks#Clearing_BadBlocks


___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: GSM Firmware Flashed, now UBIFS problem and Kernel Panic

2011-04-14 Thread Dave
I wonder if it would be possible to boot into a distro on the sd card and
mount the nand partitions. Then you could save /home. Just a thought.

On Thu, Apr 14, 2011 at 7:21 PM, Raphael Wimmer
raphael.wim...@ifi.lmu.dewrote:

 Hi Thomas,


 On Thu, 14 Apr 2011 11:05:38 +0200, Thomas Franck thomas.fra...@gmx.com
 wrote:
 [...]

  ---88-
 UBIFS error (pid 1): ubifs_read_node: bad node type (255 but expected 6)
 UBIFS error (pid 1): ubifs_Read_node: bad node at LEB 0:0
 Kernel panic - not syncing: VFS: Unable to mount fs on unknown-block(0,0)
 ---88-

 [...]


  Any ideas on this problem? I there any way to repair that FS?


 I had the same probem when upgrading QtMoko a few days ago. Regardless of
 what fs image I flashed, I would get these error messages.

 Completely erasing the NAND allowed me to re-install without problems. Of
 course, it means that your data will be gone. I did not find an easier
 solution, and actually had no important data on the phone.
 I followed more or less the steps for clearing bad blocks [1] and threw in
 an erase command somewhere. Unfortunately, I do not remember the details.
 The NOR bootloader offers a help command, however.

 If there is a better solution that preserves the FS, I would be happy to
 learn about it.

 Raphael

 [1] http://wiki.openmoko.org/wiki/NAND_bad_blocks#Clearing_BadBlocks



 ___
 Openmoko community mailing list
 community@lists.openmoko.org
 http://lists.openmoko.org/mailman/listinfo/community

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: GSM Firmware Flashed, now UBIFS problem and Kernel Panic

2011-04-14 Thread W. B. Kranendonk

--- On Thu, 4/14/11, Dave dave...@gmail.com wrote:
 On Thu, Apr 14, 2011 at 7:21 PM, Raphael Wimmer
 raphael.wim...@ifi.lmu.de wrote:
  If there is a better solution that preserves the FS,
  I would be happy to learn about it.
 I wonder if it would be possible to boot into a distro on the sd card
 and mount the nand partitions. Then you could save /home. Just a thought.

Yes, it is: just mount  -t jffs2 /dev/mtdblock6 /mountpoint 

I haven't used it for ubifs yet though; I just tried on qtmoko 33(?) and got a 
wrong filesystem error on mounting; not sure which fs I'm using, I tried jffs2 
as well which I killed after half a minute. jffs2 can take a while to scan the 
flash, but when I used it that way before, it would be done in some 7 seconds 
(on SHR).

lsmod | grep ub does not give any results; 
lsmod | grep jff gives a single result on my currently running system.

I hope it helps a bit,

Boudewijn


___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: GSM Firmware Flashed, now UBIFS problem and Kernel Panic

2011-04-14 Thread Thomas Franck
 --- On Thu, 4/14/11, Dave dave...@gmail.com wrote:
 On Thu, Apr 14, 2011 at 7:21 PM, Raphael Wimmer
 raphael.wim...@ifi.lmu.de wrote:
 If there is a better solution that preserves the FS,
 I would be happy to learn about it.
 I wonder if it would be possible to boot into a distro on the sd card
 and mount the nand partitions. Then you could save /home. Just a thought.
 
 Yes, it is: just mount  -t jffs2 /dev/mtdblock6 /mountpoint 

Thank you all for your input..

I put a qtmoko v35 on an SD card.. an on terminal I did:

mkdir /home/root/nandfs
mount -t ubifs /dev/mtdblock6 /home/root/nandfs

but sadly that doesn't work.. dmesg tells me:

UBIFS error: ubifs_get_sb: cannot open /dev/mtdblock6, error -22

Any ideas?

Cheers,
-- 
Thomas

-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~
Trying to outsmart a compiler defeats much of the purpose of using one.
  - Kernighan  Plauger, The Elements of Programming Style
-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: GSM Firmware Flashed, now UBIFS problem and Kernel Panic

2011-04-14 Thread Benjamin Deering

On 04/14/2011 12:13 PM, Thomas Franck wrote:

--- On Thu, 4/14/11, Davedave...@gmail.com  wrote:
 

On Thu, Apr 14, 2011 at 7:21 PM, Raphael Wimmer
raphael.wim...@ifi.lmu.de  wrote:
   

If there is a better solution that preserves the FS,
I would be happy to learn about it.
 

I wonder if it would be possible to boot into a distro on the sd card
and mount the nand partitions. Then you could save /home. Just a thought.
   

Yes, it is: just mount  -t jffs2 /dev/mtdblock6 /mountpoint
 

Thank you all for your input..

I put a qtmoko v35 on an SD card.. an on terminal I did:

mkdir /home/root/nandfs
mount -t ubifs /dev/mtdblock6 /home/root/nandfs

but sadly that doesn't work.. dmesg tells me:

UBIFS error: ubifs_get_sb: cannot open /dev/mtdblock6, error -22

Any ideas?

Cheers,
   
I think you need to attach the ubifs before mounting.  See 
http://openmoko-public-mailinglists.1958.n2.nabble.com/UBI-success-story-td4218730.html 
for the steps, though unless you want to reformat, you shouldn't follow 
all of them.


Ben

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: GSM Firmware Flashed, now UBIFS problem and Kernel Panic

2011-04-14 Thread sferic
Hi,
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 found this at the ubuntu-wiki, a nice source for all linux-related questions
(as far they are not openmoko-specific - of course!)

Good luck
Sferic


At 14 Apr 2011 18:13:37 +0200 Thomas Franck wrote:
  --- On Thu, 4/14/11, Dave dave...@gmail.com wrote:
  On Thu, Apr 14, 2011 at 7:21 PM, Raphael Wimmer
  raphael.wim...@ifi.lmu.de wrote:
  If there is a better solution that preserves the FS,
  I would be happy to learn about it.
  I wonder if it would be possible to boot into a distro on the sd card
  and mount the nand partitions. Then you could save /home. Just a thought.
  
  Yes, it is: just mount  -t jffs2 /dev/mtdblock6 /mountpoint 
 
 Thank you all for your input..
 
 I put a qtmoko v35 on an SD card.. an on terminal I did:
 
 mkdir /home/root/nandfs
 mount -t ubifs /dev/mtdblock6 /home/root/nandfs
 
 but sadly that doesn't work.. dmesg tells me:
 
 UBIFS error: ubifs_get_sb: cannot open /dev/mtdblock6, error -22
 
 Any ideas?
 
 Cheers,
 -- 
 Thomas
 
 -~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~
 Trying to outsmart a compiler defeats much of the purpose of using one.
   - Kernighan  Plauger, The Elements of Programming Style
 -~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~



___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community