MTD mounting problem

[Krug, Markus]

Thanks Richard,
The problem was the minor number of the block device, which differs from the minor number of the char device.
With
mknod /dev/mtd5 c 31 10
mknod /dev/mtdblock5 b 90 5
I was able to mount the device. 
However I still don't know, why the devices are not created in /dev at start up. 

Markus

-----Ursprüngliche Nachricht-----
Von: Richard Weinberger [mailto:richard.weinberger at gmail.com] 
Gesendet: Montag, 2. November 2015 14:09
An: Krug, Markus
Cc: linux-mtd at lists.infradead.org
Betreff: Re: MTD mounting problem

On Mon, Nov 2, 2015 at 1:21 PM, Krug, Markus <Markus.Krug at bruker.com> wrote:
> and /proc/mtd shows:
> dev:    size   erasesize  name
> mtd0: 00100000 00010000 "qspi-fsbl-uboot"
> mtd1: 00500000 00010000 "qspi-linux"
> mtd2: 00020000 00010000 "qspi-device-tree"
> mtd3: 005e0000 00010000 "qspi-rootfs"
> mtd4: 00400000 00010000 "qspi-bitstream"
> mtd5: 01000000 00010000 "qspi-data"
> So everything seems to be fine.
> But in /dev there are only mtd0, mtd1, mtdblock0 and mtdblock1.
> So I added with mknod the missing partitions.

This should not happen.
Is your /dev really not managed by udev or devtmpfs?

> Then I run:
> flash_eraseall /dev/mtd5 (no problem)
> mount -t jffs2 /dev/mtdblock5 /mnt
> the mounting failed:
> mount: mounting /dev/mtdblock5 on /mnt failed: No such device
>
> Does someone know whats going wrong?

I think the root cause is the missing device node.
Please double check why it is not present.

-- 
Thanks,
//richard