could not mount a spi-flash on rootfs

Hi,

I am working on Lager board from Renesas, We have tested qspi driver on upstream-ltsi v3.10.31、

(http://ltsi.linuxfoundation.org/sites/ltsi/files/patch-3.10.31-ltsi.gz)

When mounting /dev/mtdblock2 on /mnt/, there are some messages as a below:

"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"

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.

Best regards,
Cao Minh Hiep

root@linaro-nano:~# fdisk /dev/mtdblock2 
Device contains neither a valid DOS partition table, nor Sun, SGI or OSF disklabel
Building a new DOS disklabel with disk identifier 0xb8711025.
Changes will remain in memory only, until you decide to write them.
After that, of course, the previous content won't be recoverable.

Warning: invalid flag 0x0000 of partition table 4 will be corrected by w(rite)

Command (m for help): n
Partition type:
p primary (0 primary, 0 extended, 4 free)
e extended
Select (default p):
Using default response p
Partition number (1-4, default 1):
Using default value 1
First sector (2048-122367, default 2048):
Using default value 2048
Last sector, +sectors or +size{K,M,G} (2048-122367, default 122367):
Using default value 122367

Command (m for help): t
Selected partition 1
Hex code (type L to list codes): 83

Command (m for help): w
The partition table has been altered!

Calling ioctl() to re-read partition table.

WARNING: Re-reading the partition table failed with error 22: Invalid argument. The kernel still uses the old table. The new table will be used at the next reboot or after you run partprobe(8) or kpartx(8)
Syncing disks.

root@linaro-nano:~# mkfs.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:~#

root@linaro-nano:~# mount /dev/mtdblock2 /mnt/
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

Hi Hiep-san,

Does it make a difference if you explicitly specify the file system type, by adding "-t ext3"?

It looks like the file system wasn't written correctly to the device. Do you see anything suspicious in the kernel log (dmesg)?

You mentioned you tested this on upstream-ltsi v3.10.31. Do you mean the above test, which failed?

[...]

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!

Gr{oetje,eeting}s,

Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [email protected]

In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
--
To unsubscribe from this list: send the line "unsubscribe linux-spi" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html

Hi Geert-san

Thanks for your replying

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.

No, I don't see anything suspicious in the kernel log. It is normally log for qspi.

yes, I do.

Thanks, I got it.

Best regards,
Hiep

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

Hi Hiep-san,

"renesas_spi qspi.0: master is unqueued, this is deprecated"

So this is indeed a very old version of the rspi driver. Which 3.10.31-ltsi are you using? The one from renesas-backports?

Strange.

Can you check that writing works using some other way, e.g. using dd?

Gr{oetje,eeting}s,

Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [email protected]

In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
--
To unsubscribe from this list: send the line "unsubscribe linux-spi" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html

Hi Geert-san

The source code is link below:
http://ltsi.linuxfoundation.org/sites/ltsi/files/patch-3.10.31-ltsi.gz
This qspi is added on rspi driver together that i am using. I think that It was back-ported from a upstream version. I think this message does not causing of the problem.

I have checked the writing works using other way (using dd command directly) as below:

# uname -a
Linux linaro-nano 3.10.31-ltsi-00002-g7bdf07f-dirty #1 Mon Jun 30 09:18:01 JST 2014x
# du -h 2.in
2.1M    2.in

# dd if=2M.in of=/dev/mtdblock2 bs=1M count=2
2+0 records in
2+0 records out
2097152 bytes (2.1 MB) copied, 155.454 s, 13.5 kB/s
root@linaro-nano:~# dd if=/dev/mtdblock2 of=2M.out bs=1M count=2
2+0 records in
2+0 records out
2097152 bytes (2.1 MB) copied, 83.3882 s, 25.1 kB/s
root@linaro-nano:~# ls
2M.in    2M.out
root@linaro-nano:~# md5sum 2M.in 2M.out
bf90a4724c584901fae07749965208e3  2M.in
bf90a4724c584901fae07749965208e3  2M.out

Best regards,
Hiep
--
To unsubscribe from this list: send the line "unsubscribe linux-spi" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html