No filesystem could mount root

No filesystem could mount root

[mahendra varman]

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

Hi all

We are porting linux 2.6.24 on a board with powerpc processor and with AMD
79C972 ethernet chip

Thru ramdisk I can able to boot the board and i can do the ifconfig eth0
up..

When I try to boot the board with nfs iam getting the following

NET: Registered protocol family 1
NET: Registered protocol family 17
RPC: Registered udp transport module.
RPC: Registered tcp transport module
List of all partitions:
No filesystem could mount root, tried:  ext3 ext2 msdos ntfs
Kernel panic - not syncing: VFS: Unable to mount root fs on
unknown-block(1,0)
Rebooting in 180 seconds..

1. In the kernel the nfs related configs are enabled properly
2. The nfs server and file system is proper( I have mounted and checked the
nfs server & file system thru another working setup)
3. The ethernet driver  pcnet32.c  under drivers/net  is okkk it seems becaz
it is working when i boot the board thru ramdisk

Please shed me some light where to look and what may be the reason iam
getting the above error when i boot thru NFS

Thanks in advance

[-- Attachment #2: Type: text/html, Size: 1183 bytes --]

Re: No filesystem could mount root

[selvamuthukumar v]

> NET: Registered protocol family 1
> NET: Registered protocol family 17
> RPC: Registered udp transport module.
> RPC: Registered tcp transport module
> List of all partitions:
> No filesystem could mount root, tried:  ext3 ext2 msdos ntfs

There are no messages from the kernel that it's trying NFS. You can
check the boot arguments you are passing to the kernel.

Re: No filesystem could mount root

[mahendra varman]

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

> There are no messages from the kernel that it's trying NFS. You can
> check the boot arguments you are passing to the kernel.
>

The boot arguments are passed correctly only.

setenv bootargs console=ttyS0,57600 root=/dev/nfs
nfsroot=192.168.0.6:/root/FILESYSTEM/target/target-minimal
ip=192.168.0.200:192.168.0.6:192.168.0.1:255.255.255.0::eth0

still Iam getting the above said error

Any clue??

[-- Attachment #2: Type: text/html, Size: 639 bytes --]

Re: No filesystem could mount root

[Marco Stornelli]

mahendra varman ha scritto:
>> There are no messages from the kernel that it's trying NFS. You can
>> check the boot arguments you are passing to the kernel.
>>
> 
> The boot arguments are passed correctly only.
> 
> setenv bootargs console=ttyS0,57600 root=/dev/nfs
> nfsroot=192.168.0.6:/root/FILESYSTEM/target/target-minimal
> ip=192.168.0.200:192.168.0.6:192.168.0.1:255.255.255.0::eth0
> 
> still Iam getting the above said error
> 
> Any clue??
> 
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
Sometimes ago I had the same problem, I don't exactly remember the 
problem, but it was related to the NFS server configuration. Check it out.

Regards,

-- 
Marco Stornelli
Embedded Software Engineer
CoRiTeL - Consorzio di Ricerca sulle Telecomunicazioni
http://www.coritel.it

marco.stornelli@coritel.it
+39 06 72582838

Re: No filesystem could mount root

[Jens Gehrlein]

Hi,

mahendra varman schrieb:
> setenv bootargs console=ttyS0,57600 root=/dev/nfs
> nfsroot=192.168.0.6:/root/FILESYSTEM/target/target-minimal
> ip=192.168.0.200:192.168.0.6:192.168.0.1:255.255.255.0::eth0

I had a similar problem. Setting the rw flag helped, e.g.
... root=/dev/nfs rw nfsroot ...
                   ^^
Kind regards,
Jens