An odd booting problem in a special situation
 

Hello everyone£¬

My situation is the same as a previous issue yesterday
He installed SUSE10 in another real machine, and I installed in vmware, neither of us can boot in our own machines using that installed system.
there seems to be no body got the answer, so I raise the issue here again.

The details of the situation is that:
I installed SUSE 10 in real partition on vmware from Windows, it formated that partition as ReiserFS file system. After installation, it boots and works fine within vmware, and further, it should also be all right without vmware, in which is the real hardware booting, since previously I had such exprience using Redhat and SuSE 9 (btw, they use ext3 file system)

But the problem occured when trying the real booting, the system cannot find the hda at all
(btw, Grub can find all the hda and its file system and even its contents like /boot by using TAB)
When the kernel is booted up by Grub, firstly it detected some hardware without error, but after that, some messages were shown out, and the booting stoped. The last messages before stopping were:
"
Loading reiserfs
Waiting for device /dev/hda4 to appear.........(these dots appeared one by one)
not found -- exiting to /bin/sh
$
"
After that I can type commands after the dollar sign, but it is not the full linux shell, since most commands like ls cannot be used, only pwd and cd can.

That's the full story,
any one can help? For any further information I can provide, also ask here, Thanks

Here is that previous similar problem:
http://www.linuxquestions.org/questi...hreadid=382646

Actually, the problem is about how let kernel recognize the reiserfs file system while it is intalled in one machine and booting from another (vmware vs real machine or two different machines)

Addtionally, I add some grub's booting messages here:
"
root (hd0,3)
Filesystem type is reiserfs, partition type 0x83

kernel /boot/vmlinuz root=/dev/hda4 resume=/dev/hda3
[Linux-bzImage, setup=0x1e00, size=0x176657

initrd /boot/initrd
[Linux-initrd @ 0x1fe3d000 0x1b2c3d bytes]
"
So from there to see, grub can recognize the hda and reiserfs quite well, but kernel just stoped when find hda and reiserfs

"
Loading reiserfs
Waiting for device /dev/hda4 to appear.........(these dots appeared one by one)
not found -- exiting to /bin/sh
$
"

I cannot use any commands within that $, even if the most basic ones like su, sudo, ls, init etc, because the kernel has not yet loaded the root file system at all.

How can I deal with this problem?

Unless you have a good reason of using reiser,
why don't you try ext3 first on the real system?

I have no experience about reiser so I cannot tell you
if this problem with hda is not to do with the hard drive controller
(probably not actually unless it is a very new sata controller)

Try to boot the Rescue-System on the physical machine and confirm the availabilty of the partitions, especially /dev/hda4.

To get it straight, you have installed Suse10 on vmware and transferred the image to another drive?

hi karpi,
I installed SUSE10 onto REAL harddisk by using vmware, not image, so that I can boot the installed system directly without vmware.

I tried booting from CD and entered the rescue system, by using fdisk -l, it showed that all /dev/hdaX were recognizable, along with their file system.

New ISSUSE: reiserfs is not a part of the real reason

The problem is not caused by reiserfs, since I installed SUSE10 again from vmware onto real harddisk partition with EXT3 file system. The odd situation didn't change when booting from real machine, the last messages were also:
"Loading ext3 (not reiserfs now)
Waiting for device /dev/hda4 to appear.........(these dots appeared one by one)
not found -- exiting to /bin/sh
$
"

Can you install directly, not from vmware?

Is this a sata controller? If yes which one?
fact fdisk -l is ok suggests controller is recognised, but just in case I ask

Have you had a look into bootprompt parameters?
Maybe some nodetect option may help (wild guess, I know)