- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- ProLiant Servers (ML,DL,SL)
- >
- Problems with Proliant DL580 and Red Hat Advanced ...
ProLiant Servers (ML,DL,SL)
1753770
Members
4788
Online
108799
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-24-2003 02:48 PM
05-24-2003 02:48 PM
Problems with Proliant DL580 and Red Hat Advanced Server
Hello, we're having some problems configuring/installing Red Hat Advanced Server 2.1 on a Proliant DL580 Server w/ smart array controller (640x, 64x, 5i,5300 Series). I don't have the actual model number of the raid controller on hand, but I know it's in the aforementioned series. Anyways, we're having a boot order problem with the internal smart array and the external smart array drives.
During the Red Hat install, in the drive partitioning phase using disk druid, both arrays show up correctly (/dev/ida and /dev/cciss), but the external drive (/dev/cciss) shows up first in the list. We partition the disks, setting up mount points on both disk arrays. We place the common mount points on /dev/ida (/boot, /, swap, etc) and a few others on /dev/cciss.
When we get to the boat loader phase of install, the choices are:
1) Install boot loader to Master Boot Record of /dev/cciss/c0d0
2) Install boot loader to first segment of /boot on /dev/ida
We really want to install the boat loader to the master boot record of /dev/ida/c0d0, there is no option to change the drive order (like in Red Hat 8.0 - Advanced boot loader options). So we've tried both of the options above with no luck. When we boot-up, we simply get the word "GRUB" or "LILO" in the upper left-hand corner of the screen, and that's it. We've tried changing the drive boot order in the BIOS and still no luck.
We removed the external controller and we were able to successfully install Advanced Server. We thought we would simply install without the external controller and just add the card after linux was already installed, but then we couldn't figure out how to partition the drive at that point (fdisk didn't recognize /dev/cciss). It doesn't appear to be a driver issue, because linux correctly identifies both disk arrays. Maybe we didn't correctly change the drive order in the BIOS. I don't know. Any ideas/suggestions would be greatly appreciated.
Thanks,
Tony
During the Red Hat install, in the drive partitioning phase using disk druid, both arrays show up correctly (/dev/ida and /dev/cciss), but the external drive (/dev/cciss) shows up first in the list. We partition the disks, setting up mount points on both disk arrays. We place the common mount points on /dev/ida (/boot, /, swap, etc) and a few others on /dev/cciss.
When we get to the boat loader phase of install, the choices are:
1) Install boot loader to Master Boot Record of /dev/cciss/c0d0
2) Install boot loader to first segment of /boot on /dev/ida
We really want to install the boat loader to the master boot record of /dev/ida/c0d0, there is no option to change the drive order (like in Red Hat 8.0 - Advanced boot loader options). So we've tried both of the options above with no luck. When we boot-up, we simply get the word "GRUB" or "LILO" in the upper left-hand corner of the screen, and that's it. We've tried changing the drive boot order in the BIOS and still no luck.
We removed the external controller and we were able to successfully install Advanced Server. We thought we would simply install without the external controller and just add the card after linux was already installed, but then we couldn't figure out how to partition the drive at that point (fdisk didn't recognize /dev/cciss). It doesn't appear to be a driver issue, because linux correctly identifies both disk arrays. Maybe we didn't correctly change the drive order in the BIOS. I don't know. Any ideas/suggestions would be greatly appreciated.
Thanks,
Tony
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-26-2003 03:43 AM
05-26-2003 03:43 AM
Re: Problems with Proliant DL580 and Red Hat Advanced Server
Hi Tony,
here's a way you'll be able to proceed with your install. First make sure that the controller that will hold the /home partition is the first one in the boot controller order. Then proceed with the installation and isntall the lilo boot loader. You can then pick any partition for installing the boot record (as we are going to change this later on to the correct one which is /dev/cciss) Make sure to create the boot floppy at the end of the installation. You can then boot up your system, and edit the file called /etc/modules.conf and make sure that the controllers in this lists are in the correct order, with the controller holding the /boot partition being first. You can then recreate a new ramdisk image using the command mkinitrd (see manual page for help) and then reinstall lilo on the correct partition (again see man page of lilo for help) This will allow you to boot your system without a floppy for consequent boots.
Regards,
here's a way you'll be able to proceed with your install. First make sure that the controller that will hold the /home partition is the first one in the boot controller order. Then proceed with the installation and isntall the lilo boot loader. You can then pick any partition for installing the boot record (as we are going to change this later on to the correct one which is /dev/cciss) Make sure to create the boot floppy at the end of the installation. You can then boot up your system, and edit the file called /etc/modules.conf and make sure that the controllers in this lists are in the correct order, with the controller holding the /boot partition being first. You can then recreate a new ramdisk image using the command mkinitrd (see manual page for help) and then reinstall lilo on the correct partition (again see man page of lilo for help) This will allow you to boot your system without a floppy for consequent boots.
Regards,
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP