I have insalled LINUX RH7 onto to A

[butchrecon]

I have insalled LINUX RH7 onto to A PIII 1G with an Adaptec 3200 RAID 5 configureation. Install went fine. But when I boot it gives me 3 choices I have never run into before.
1) LINUX
2) LINUX-SMP
3) LINUX-UP

Anyone have any idea what the 3 are for and why when I choose option #1 it crashes and I cannot boot into LINUX. When I choose option #2 it boots into LINUX (so far) without issues. Any clues? James Collins
Field Service Engineer
A+, MCP

email: butchrecon@skyenet.net

Please let us (Tek-tips members) know if the solutions we provide are helpful to you. Not only do they help you but they may help others.

 

[ifincham]

Hi,

Well the smp must mean a smp (symmetric multi-processor)enabled kernel, i.e. one compiled for multiple cpus. I'd guess the UP means the same for a single processor, i.e. uniprocessor. If you post the contents of your /etc/lilo.conf file it might be a bit clearer because the labels on the lilo menu are just that - it doesn't really tell you what's being booted.

It <could> be that the first image 'linux' doesn't include an initrd (initial read-disk) which contains drivers needed to access the hardware pre-boot - invariably scsi drivers.

Regards

 

[butchrecon]

ifincham

thanks fro your help. Its a dual processor board with 1 processor. Here is my lilo.conf file:

boot=/dev/sda
map=/boot/map
install=/boot/boot.b
prompt
timeout=50
message=/boot/message
linear
default=linux

image=/boot/vmlinuz-2.2.16-22enterprise
label=linux
read-only
root=/dev/sda5

image=/boot/vmlinuz-2.2.16-22smp
label=linux-smp
initrd=/boot/initrd-2.2.16-22smp.img
read-only
root=/dev/sda5

image=/boot/vmlinuz-2.2.16-22
label=linux-up
initrd=/boot/initrd-2.2.16-22.img
read-only
root=/dev/sda5

What you were saying make sense. So why would the LInux path not work? James Collins
Field Service Engineer
A+, MCP

email: butchrecon@skyenet.net

Please let us (Tek-tips members) know if the solutions we provide are helpful to you. Not only do they help you but they may help others.

 

[ifincham]

Hi,

Notice the others have a line like :

initrd=/boot/initrd-2.2.16-22.img

This is the initial read-disk I referred to before. If linux is installed on ide drives then the boot loader can access those through the motherboard resources without any special drivers. However, if its scsi its a bit of a catch-22. You can load drivers installed on the scsi drives but you can't access those drives until you've loaded a driver! Hence, the need for the initrd which contains drivers sufficient to access the boot sector of the scsi drive..

You could always copy the above line into the 'linux' labelled block and update the binary boot record with the '/sbin/lilo -v' command. If should then boot but quite what an 'enterprise' kernel is I'm not too sure - time to check redhat's site I guess.

Regards

 

[butchrecon]

I can get it to boot fine into the smp choice. I have not tried the up choice. James Collins
Field Service Engineer
A+, MCP

email: butchrecon@skyenet.net

Please let us (Tek-tips members) know if the solutions we provide are helpful to you. Not only do they help you but they may help others.

 

[ifincham]

Hi...



To answer my own question about the enterprise kernel...



&quot;This package includes a kernel that has appropriate configuration options enabled for the typical large enterprise server. This includes SMP support for multiple processor machines, support for large memory configurations, support for large file I/O, and other appropriate items.&quot;


So there you have it!

Regards

 

[Sina]

Hi there,

We recently have purchased a system from Dell, that is curently configured for Raid 5 running on NT.

I'm planning to install Linux Redhat 7.1 on it. What is there to do at the install to enable raid?

Do I have to do anything before the install except defining the raid channel and setting up the drives?

How would I partion the drives, for the Linux install?

Thank you.

 

[butchrecon]

What I did was insure I had s\drivers for the raid card and then installed. I did not do much partitioning except the basics. It is now running fine. I initially ran into some processor issues since I run a dual board. Other than that it installed ok. James Collins
Field Service Engineer
A+, MCP

email: butchrecon@skyenet.net

Please let us (Tek-tips members) know if the solutions we provide are helpful to you. Not only do they help you but they may help others.