[mroshan]

devils_casper:

/etc/fstab file plays a major role while booting up any Linux OS. Init Scripts read /etc/fstab file to mount partitions during boot up.

OK, you're right. But, I told "in this stage of booting". In my case, the boot process even does not arrive to "Welcome to Fedora" message, until the control be delegated to init scripts and the fstab file be read to mount user partitions. To check and test my inference, I booted by Fedora CD Live and renamed the /etc/fstab file! What was the result in your opinion?! Nothing, the error and boot messages repeated without any difference!

devils_casper:

Its not finding root partition and throwing errors while reading fstab.sys file.
Is it throwing Label error right now? Have you tried adding (hd0,6) in kernel and initrd path?

About the message "no fstab.sys...", I think this is not so important. Because accidently, I saw this message in Live-CD booting too, and it did not make any problem.
About Label error, as far as I remember, we had one label error about swap and resuming: "Unable to access resume device (LABEL=SWAP-sda8 )", that I mentioned in my previous post that it wiped out by passing "noresume" parameter to kernel.
There is one "root (hd0,6)" line in my grub file that refers to /boot partition.

Thank you my friend.

[mroshan]

So, the problem solved!

From initrd manual page:

... A second scenario is for installations where Linux runs on systems with different hardware configurations in a single administrative network. In such cases, it may be desirable to use only a small set of kernels (ideally only one) and to keep the system-specific part of configuration information as small as possible. In this case, create a common file with all needed modules...

Yes, initrd was the point. The fact is that the initrd loads the necessary modules for mounting the 'real' root filesystem, and in my case, the required modules were not loading to identify my root filesystem in second (B) system, hence the error message.

Since I did not have the precise information about my system hardwares and the necessary modules for them, the only solution I considered, was: installing a minimal Fedora 8 on system B to acquire an adequate initrd for system and merging it with the initrd of existing installed Fedora 8 on system A.

The only thing that remains is the different configurations for two systems, that a simple script resolves it.

Thank you all.