All of lore.kernel.org
 help / color / mirror / Atom feed
From: カオ ミン ヒェップ <cm-hiep-HEF513clHfp3+QwDJ9on6Q@public.gmane.org>
To: Geert Uytterhoeven <geert-Td1EMuHUCqxL1ZNQvxDV9g@public.gmane.org>
Cc: linux-spi <linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	"Shimoda,
	Yoshihiro"
	<yoshihiro.shimoda.uh-zM6kxYcvzFBBDgjK7y7TUQ@public.gmane.org>
Subject: Re: could not mount a spi-flash on rootfs
Date: Mon, 30 Jun 2014 11:29:24 +0900	[thread overview]
Message-ID: <53B0CB84.6030001@jinso.co.jp> (raw)
In-Reply-To: <CAMuHMdWBf1+A9=8b1x+e0YcV3d=K_tBvqUeBXxvoHFy=QHcJxQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 1786 bytes --]

Hi Geert-san

Thanks for your replying


>> "EXT3-fs (mtdblock2): error: can't find ext3 filesystem on dev mtdblock2.
>> EXT2-fs (mtdblock2): error: can't find an ext2 filesystem on dev mtdblock2.
>> EXT4-fs (mtdblock2): VFS: Can't find ext4 filesystem
>> FAT-fs (mtdblock2): bogus number of reserved sectors
>> FAT-fs (mtdblock2): Can't find a valid FAT filesystem
>> FAT-fs (mtdblock2): bogus number of reserved sectors
>> FAT-fs (mtdblock2): Can't find a valid FAT filesystem
>> mount: you must specify the filesystem type"
>> root@linaro-nano:~# mount /dev/mtdblock2 /mnt/
> Does it make a difference if you explicitly specify the file system type,
> by adding "-t ext3"?
I have tried to specify the system type by adding "-t ext3" or "-t ext4",
but it has no change anything.
I attached the qspi test logs file. Please see it.

>> I have enabled ext2,3,4 file systems when configuring the kernel.
>> and I saw that the qspi driver code is same with upstream version code that
>> be good.
>> maybe the problem related to mtd (m25p80.c) (?)
>> I attach the logs files when making a spi-flash partition and mount it on
>> rootfs.
> It looks like the file system wasn't written correctly to the device.
> Do you see anything suspicious in the kernel log (dmesg)?
No, I don't see anything suspicious in the kernel log. It is normally 
log for qspi.

> You mentioned you tested this on upstream-ltsi v3.10.31.
> Do you mean the above test, which failed?
yes, I do.
>> root@linaro-nano:~# fdisk /dev/mtdblock2
> [...]
>
>> root@linaro-nano:~# mkfs.ext3 /dev/mtdblock2
> BTW, why do you run fdisk on /dev/mtdblock2 first?
> According to your logs, you're running mkfs.ext3 on the raw /dev/mtdblock2
> afterwards, erasing your partition table again.
Thanks, I got it.


Best regards,
Hiep


[-- Attachment #2: qspi-test-log.txt --]
[-- Type: text/plain, Size: 3435 bytes --]

renesas_spi qspi.0: master is unqueued, this is deprecated
m25p80 spi0.0: s25fl512s (65536 Kbytes)
Creating 3 MTD partitions on "m25p80":
0x000000000000-0x000000040000 : "loader"
0x000000040000-0x000000440000 : "user"
0x000000440000-0x000004000000 : "flash"
renesas_spi qspi.0: probed


# mkfs.ext3 -t ext3 /dev/mtdblock2                                    
mke2fs 1.42.5 (29-Jul-2012)
Filesystem label=
OS type: Linux
Block size=1024 (log=0)
Fragment size=1024 (log=0)
Stride=0 blocks, Stripe width=0 blocks
15296 inodes, 61184 blocks
3059 blocks (5.00%) reserved for the super user
First data block=1
Maximum filesystem blocks=62652416
8 block groups
8192 blocks per group, 8192 fragments per group
1912 inodes per group
Superblock backups stored on blocks: 
        8193, 24577, 40961, 57345

Allocating group tables: done                            
Writing inode tables: done                            
Creating journal (4096 blocks): done
Writing superblocks and filesystem accounting information: done

root@linaro-nano:~# mount /dev/mtdblock2 /mnt/
EXT3-fs (mtdblock2): error: can't find ext3 filesystem on dev mtdblock2.
EXT4-fs (mtdblock2): VFS: Can't find ext4 filesystem
EXT4-fs (mtdblock2): VFS: Can't find ext4 filesystem
FAT-fs (mtdblock2): bogus number of reserved sectors
FAT-fs (mtdblock2): Can't find a valid FAT filesystem
FAT-fs (mtdblock2): bogus number of reserved sectors
FAT-fs (mtdblock2): Can't find a valid FAT filesystem
mount: you must specify the filesystem type
root@linaro-nano:~# mount -t ext3 /dev/mtdblock2 /mnt/                                  
EXT3-fs (mtdblock2): error: can't find ext3 filesystem on dev mtdblock2.
mount: wrong fs type, bad option, bad superblock on /dev/mtdblock2,
       missing codepage or helper program, or other error
       In some cases useful info is found in syslog - try
       dmesg | tail  or so




# mkfs.ext4 -t ext4 /dev/mtdblock2 
mke2fs 1.42.5 (29-Jul-2012)
Filesystem label=
OS type: Linux
Block size=1024 (log=0)
Fragment size=1024 (log=0)
Stride=0 blocks, Stripe width=0 blocks
15296 inodes, 61184 blocks
3059 blocks (5.00%) reserved for the super user
First data block=1
Maximum filesystem blocks=62652416
8 block groups
8192 blocks per group, 8192 fragments per group
1912 inodes per group
Superblock backups stored on blocks: 
        8193, 24577, 40961, 57345

Allocating group tables: done                            
Writing inode tables: done                            
Creating journal (4096 blocks): done
Writing superblocks and filesystem accounting information:    


done

root@linaro-nano:~# 
root@linaro-nano:~# 
root@linaro-nano:~# 
root@linaro-nano:~# mount -t ext4 /dev/mtdblock2 /mnt/
EXT4-fs (mtdblock2): VFS: Can't find ext4 filesystem
mount: wrong fs type, bad option, bad superblock on /dev/mtdblock2,
       missing codepage or helper program, or other error
       In some cases useful info is found in syslog - try
       dmesg | tail  or so

root@linaro-nano:~# mount /dev/mtdblock2 /mnt/
EXT3-fs (mtdblock2): error: can't find ext3 filesystem on dev mtdblock2.
EXT4-fs (mtdblock2): VFS: Can't find ext4 filesystem
EXT4-fs (mtdblock2): VFS: Can't find ext4 filesystem
FAT-fs (mtdblock2): bogus number of reserved sectors
FAT-fs (mtdblock2): Can't find a valid FAT filesystem
FAT-fs (mtdblock2): bogus number of reserved sectors
FAT-fs (mtdblock2): Can't find a valid FAT filesystem
mount: you must specify the filesystem type


  parent reply	other threads:[~2014-06-30  2:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-25  9:19 could not mount a spi-flash on rootfs カオ ミン ヒェップ
     [not found] ` <53AA941D.3000808-HEF513clHfp3+QwDJ9on6Q@public.gmane.org>
2014-06-27 13:17   ` Geert Uytterhoeven
     [not found]     ` <CAMuHMdWBf1+A9=8b1x+e0YcV3d=K_tBvqUeBXxvoHFy=QHcJxQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-06-30  2:29       ` カオ ミン ヒェップ [this message]
     [not found]         ` <53B0CB84.6030001-HEF513clHfp3+QwDJ9on6Q@public.gmane.org>
2014-06-30  7:21           ` Geert Uytterhoeven
     [not found]             ` <CAMuHMdXnLG==TmZCLd=tZ0C1PPurjWkbE=ysCFCOgVK+5UCJnw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-07-02  6:01               ` カオ ミン ヒェップ
     [not found] <CAN=meTma1_cAHQ82S0VHemYDChJw_Orpc3K7-k9O3ggPqtsDuQ@mail.gmail.com>
     [not found] ` <CAN=meTma1_cAHQ82S0VHemYDChJw_Orpc3K7-k9O3ggPqtsDuQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-07-03  8:41   ` Geert Uytterhoeven

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=53B0CB84.6030001@jinso.co.jp \
    --to=cm-hiep-hef513clhfp3+qwdj9on6q@public.gmane.org \
    --cc=geert-Td1EMuHUCqxL1ZNQvxDV9g@public.gmane.org \
    --cc=linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=yoshihiro.shimoda.uh-zM6kxYcvzFBBDgjK7y7TUQ@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.