We are hitting a wall trying to mount an ext2 filesystem as an initrd on /dev/ram0. I do not know if the error is due to the configuration of the filesystem, to the boot configs or due to kernel configs.
The error is generated after getting EINVAL errors for all file types from sys_mount, in mount_block_root. Any additional information on the processes in sys_mount() would be useful- ie, what is it trying to do and where can errors occur. sys_mount is a system call, and I'm not sure how to find and read the function.
Here is the exact error:
No filesystem could mount root, tried: ext3 ext2 cramfs vfat msdos
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(1,0)
I've read that this error indicates that the driver for the disk is installed, but there is an issue with identifying or mounting the filesystem.
We are using a file system that is a pared down version of base-rootfs-am180x-evm distributed with the Sitara linux tools. The filesystem image is created using dd, mke2fs and mkimage. I can provide additional details about the filesystem itself and the process to make the image if that would help.
Here are the bootargs:
bootargs=mem=64M@0xC0000000 console=ttyS1,115200n8 root=/dev/ram0 rw initrd=0xc1180000
I load the kernal image (uImage) to 0xC3000000 and the filesystem (uRamdisk) to 0xC1180000, and then boot with the command:
bootm 0xC3000000 0xC1180000
here is the initial file loading response from uboot:
## Booting kernel from Legacy Image at c3000000 ...
Image Name: Linux-2.6.33-rc4
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 2054908 Bytes = 2 MiB
Load Address: c0008000
Entry Point: c0008000
Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at c1180000 ...
Image Name: Test this image
Image Type: ARM Linux RAMDisk Image (gzip compressed)
Data Size: 1355925 Bytes = 1.3 MiB
Load Address: c1180000
Entry Point: c1180000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK
Starting kernel ...
We are using a custom board with an AM1808 and 64M SDRAM.
Thank you for any insight.