I installed Redhat 9 on my VmWare workstation 4.0.2 as a guest OS. I was able to load it up and run it wiht no problems. I then ran Redhats update utility and it updated numerous items, including the kernel which I wary about due to past problems of updating the kernel in other distros and older versions. After everything finally updated I rebooted to see if it all worked out well only to find that with the updated kernel I cannot get past whatever comes after "updating fstab". I guessing it is whatever comes after because thats usually how it works. Not only does this kill the boot-up of the Linux Virtual Machine, it makes windows so unstable that windows eventually dies as well. Any help would be greatly appreciated.
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Redhat 9 stops booting after updating fstab under VmWare
- Thread starter mike2312
- Start date
The point of VMware is that you can install a completely independant and separate guest OS from your host OS. Your Windows machine cannot be affected by what you do in a guest OS. If Windows is running slow when VMware is up, try allocating less RAM to your virtual machines, or upgrade the RAM in your box.
In the future, never do a kernel *upgrade*. If you want to try a new kernel, install it alongside your old one so that you can always go back to the old one if something goes wrong with the new kernel. You can create a separate GRUB stanza to switch back and forth between kernels.
To fix your Red Hat problem, boot from the RH90 Disc1 CD. Type 'linux rescue' from the boot: prompt. When it asks if you want to mount your filesystems, say yes. When you get to the shell, type 'chroot /mnt/sysimage'. From here, you can edit your /etc/grub.conf file and change whatever is wrong. Maybe it is referencing the wrong kernel? If you need more help, let us know and be sure to include the contents of grub.conf, 'ls /boot', and the error message including the last few lines before it stops booting.
ChrisP
RHCE, LPIC-1, CCNA, CNE, MCSE, +10 others
In the future, never do a kernel *upgrade*. If you want to try a new kernel, install it alongside your old one so that you can always go back to the old one if something goes wrong with the new kernel. You can create a separate GRUB stanza to switch back and forth between kernels.
To fix your Red Hat problem, boot from the RH90 Disc1 CD. Type 'linux rescue' from the boot: prompt. When it asks if you want to mount your filesystems, say yes. When you get to the shell, type 'chroot /mnt/sysimage'. From here, you can edit your /etc/grub.conf file and change whatever is wrong. Maybe it is referencing the wrong kernel? If you need more help, let us know and be sure to include the contents of grub.conf, 'ls /boot', and the error message including the last few lines before it stops booting.
ChrisP
RHCE, LPIC-1, CCNA, CNE, MCSE, +10 others
- Thread starter
- #3
I missed some more information, and possibly some clarifications.
More information: There is a problem while installing Redhat 9 under VmWare Workstation that causes the installation to fail upon reaching a certain point in disc 2. The fix for this that I found was to mount disc 2 as a virtual CD-Rom drive, doing so will allow one to install without the error message "foo.bar is unreadable, which is caused by either corrupt media, or ...." media test was okay, etc.
Clarification: After linux stops booting, VmWare stops responding, I have waited 30 mins just to see if it will continue. During this period of not-responding, no other program will load in Windows.
Think I will step down to 8.0 on the RedHat see if that is any better.
Thank you for your help
More information: There is a problem while installing Redhat 9 under VmWare Workstation that causes the installation to fail upon reaching a certain point in disc 2. The fix for this that I found was to mount disc 2 as a virtual CD-Rom drive, doing so will allow one to install without the error message "foo.bar is unreadable, which is caused by either corrupt media, or ...." media test was okay, etc.
Clarification: After linux stops booting, VmWare stops responding, I have waited 30 mins just to see if it will continue. During this period of not-responding, no other program will load in Windows.
Think I will step down to 8.0 on the RedHat see if that is any better.
Thank you for your help
This sounds like a VMware issue then. I don't that think that running RH80 or any other OS will make any difference. Try re-installing VMware or contact their support. You might want to post a question in the VMware newsgroup as well.
ChrisP
RHCE, LPIC-1, CCNA, CNE, MCSE, +10 others
ChrisP
RHCE, LPIC-1, CCNA, CNE, MCSE, +10 others
- Status
Similar threads
