Wont boot when two RH9.0 hdd's. i.e. one master and one slave.
Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Wont boot when two RH9.0 hdd's. i.e. one master and one slave.
Using a new Intel dual processor machine we need to boot on one RH9.0 disk and have another mounted as a slave. But, it won't boot.
With RH 7.2 this was not a problem.
Also, we can boot with RH.0 as master and XP as slave or XP as master and Linux RH9.0 as slave.
But when we install both Linux RH9.0 drives and strap one as master and one as slave, no boot.
Kernel is: 2.4.20-6smp
There are 2 hdd's. We use those sliding rail removable drives.
The problem (no-boot) occurs when both drives contain RH9.0, and we strap 1 as master and 1 as slave.
If I put the RH9.0 master in and put an XP drive in as slave, it will boot.
The error message says something like "INIT respawning too fast".
Problem is, this machine is in our lab where there is no internet, so my error description is from my memory. I can duplicate the error probably on Monday and get more details if needed.
The linux kernel has loaded and started, its dieing in the startup stuff.
Is the BIOS detecting the drive size correctly?
It may be related to mounting the partitions.
Perhaps it is booting from the second HD then getting confused.
I'd try using fdisk to mark the partitions on the slave drive as inactive.
I think we need to see the exact error messages including whatever happens
before init starts looping.
You can hit ctrl-s and ctrl-Q to halt the messages scrolling up the screen.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.