From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from casablanca.magic.fr ([195.154.101.81]) by pentafluge.infradead.org with esmtp (Exim 3.22 #1 (Red Hat Linux)) id 15A7Hn-0002il-00 for ; Wed, 13 Jun 2001 10:50:03 +0100 Received: from serveur.inventel.fr (ppp-146.net-1002.magic.fr [195.115.184.146]) by casablanca.magic.fr (8.9.3/8.9.3) with ESMTP id LAA08832 for ; Wed, 13 Jun 2001 11:55:32 +0200 (CEST) Message-ID: <3B273827.33CC03BB@inventel.fr> Date: Wed, 13 Jun 2001 11:53:43 +0200 From: Xavier DEBREUIL MIME-Version: 1.0 To: linux-mtd@lists.infradead.org Subject: root jffs2 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: linux-mtd-admin@lists.infradead.org Errors-To: linux-mtd-admin@lists.infradead.org List-Help: List-Post: List-Subscribe: , List-Id: Linux MTD discussion mailing list List-Unsubscribe: , List-Archive: I have managed to mount the jffs2 as root filesystem (yes I know many did it but I encountered problems here and there...) Nevertheless, some kernel messages are a little amazing : (root=1F01 and not root=/dev/mtdblock1...) ... root_device_name : 1F01 mtdblock_open ok mtdblock: read on "cramfs partition" at 0x400, size 0x400 mtdblock: read on "cramfs partition" at 0x0, size 0x1000 mtdblock: read on "cramfs partition" at 0x1000, size 0x1000 mtdblock: read on "cramfs partition" at 0x2000, size 0x1000 mtdblock: read on "cramfs partition" at 0x3000, size 0x1000 wrong magic JFFS: Trying to mount device 1f:01. jffs_build_fs() jffs_create_control() jffs_scan_flash(): start pos = 0x0, end = 0x300000 check_partly_erased_sector():checking sector which contains offset 0x0 for flipping bits.. check_partly_erased_sector():checking sector which contains offset 0x1000 for flipping bits.. ... blahblah... ... check_partly_erased_sector():Done checking all sectors till offset 0x300000 for flipping bits. *************** Dirty flash memory or bad inode: hexdump(pos = 0x0, len = 128): 0: 8519 02e0 4400 0000 1dfb f798 0100 0000 ...àD....û÷..... 16: 0100 0000 ed41 0000 f501 f501 0000 0000 ....íA..õ.õ..... 32: de1d 1d3b 4228 263b 4228 263b 0000 0000 Þ..;B(&;B(&;.... 48: 0000 0000 0000 0000 0000 0000 0000 0000 ................ 64: 3c72 4031 8519 01e0 2b00 0000 e66e 267d free_size == 0x0 jffs_cleanup_control() ----> !!!!! ----> JFFS: Failed to mount device 1f:01. ----> VFS: Mounted root (jffs2 filesystem) readonly. ----> !!!!! Freeing init memory: 48K serial console detected. Disabling virtual terminals. init started: BusyBox v0.51 (2001.06.05-17:42+0000) multi-call binary So, on the one hand, it indicates that it failed to mount the device on 1F01 but afterwards, it managed to mount the jffs2 filesystem as root fs. Is it a known behaviour or do I have to modify some parameters ? Xavier