I have an original ancient Proliant ML110 G2 server with two original 750GB Sata hard disks. They worked and the system worked with CentOS 6.x and has now CentOS 6.9 and the disks are in RAID 1 configuration and all good.
When I try to install ClearOS 7.3 into it, the installer can not identify the disks and can't install. I have tried the disks in every mode: RAID, IDE Enhanced, IDE Compatible (in this mode only 1 hd is visible in BIOS). No disk whatsoever can be detected by ClearOS.
I think that is the same with CentOS 7 too, as I tried to upgrade to that a couple of years ago, but was not able, and conitinued to use the 6.x
Any ideas?
When I try to install ClearOS 7.3 into it, the installer can not identify the disks and can't install. I have tried the disks in every mode: RAID, IDE Enhanced, IDE Compatible (in this mode only 1 hd is visible in BIOS). No disk whatsoever can be detected by ClearOS.
I think that is the same with CentOS 7 too, as I tried to upgrade to that a couple of years ago, but was not able, and conitinued to use the 6.x
Any ideas?
In Hardware
Share this post:
Responses (15)
-
Accepted Answer
The csiss driver was removed from the upstream Linux distribution. You can still find it in ELREPO.
http://cciss.sourceforge.net/
https://elrepo.org/tiki/kmod-cciss
https://www.centos.org/forums/viewtopic.php?t=51302
This is not an easy problem to solve
But it should work with ClearOS 6.x
If you have a different PCI controller you might be able to do an end run around the onboard or RAID controller that is failing during the install. -
Accepted Answer
I have the csiss driver compiled here. Read the Centos forum link Dave gave. That will tell you how to use it.
Reading the Centos thread, there may be an alternative way to get the installer running. See this post. If that works, you can install my rpm afterwards (or permanently add those two lines to grub but that may not be a brilliant solution). -
Accepted Answer
So. My options are to add a new drive and driver to the box, install ClearOS 7 and that driver into that, and manually add the RAID to the mix later?
The ClearOS installer does not add any options for 3rd party drivers to the process.
I have an old SCSI card and a SCSI drive that I am going to try to do that. Wonder if that is supported... -
Accepted Answer
To pass driver options during install for non-detected resources you have to assemble a driver disk and then pass the 'inst.dd' parameter when you do the install. I don't know where csiss exists as a driver disk but I'm sure someone out there has done it.
https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Installation_Guide/chap-anaconda-boot-options.html -
Accepted Answer
I had trouble preparing the driver disk as it requires exactly the same kernel to build against that is in the ClearOS disk. Could not find any.
So I'm proceeding with this plan:
- Prepare a VirtualBox VM using the ClearOS ISO
- Setup the elrepo as a repo to the VM and install the required driver from that.
- Export that using Clonezilla. Appears that Clonezilla supports the HP Smart Array tech.
- Import that with Clonezilla to the Proliant
I have now done steps 1 and 2, and now waiting for the proliant to build a new clear RAID 1 array. I already imported the Clonezilla stuff to the old disk layout, and Clonezilla somehow stored the small VM partition to the end of the disk#1 as a new pv. It is possible that Clonezilla really can't see the RAID setup as a mirrored set of drives, but two separate disks!?
After a clear fresh RAID 1 I will retry the import. - Prepare a VirtualBox VM using the ClearOS ISO
-
Accepted Answer
Jari Fredriksson wrote:
This won't work. You can't use elrepo kernel modules directly, they have to be recompiled against the ClearOS kernel. That is why I compile a number of different modules that people have requested. Use the csiss module I've compiled and not the one compiled by ElRepo.
I had trouble preparing the driver disk as it requires exactly the same kernel to build against that is in the ClearOS disk. Could not find any.
So I'm proceeding with this plan:
- Prepare a VirtualBox VM using the ClearOS ISO
- Setup the elrepo as a repo to the VM and install the required driver from that.
- Export that using Clonezilla. Appears that Clonezilla supports the HP Smart Array tech.
- Import that with Clonezilla to the Proliant
I have now done steps 1 and 2, and now waiting for the proliant to build a new clear RAID 1 array. I already imported the Clonezilla stuff to the old disk layout, and Clonezilla somehow stored the small VM partition to the end of the disk#1 as a new pv. It is possible that Clonezilla really can't see the RAID setup as a mirrored set of drives, but two separate disks!?
After a clear fresh RAID 1 I will retry the import. - Prepare a VirtualBox VM using the ClearOS ISO
-
Accepted Answer
-
Accepted Answer
-
Accepted Answer
I will report later, as currently the proliant is still building the RAID... for two more days it looks. The inst.dd option was totally new to me, as it was never mentioned in the CentOS bbs post and not here either until lately.
I will try it first and let you know. I will mark the winning reply as accepted answer after it really is done and working. -
Accepted Answer
Bummer. Still no go. I have not tried the plan of my own as I believe it does not work as you guys told.
But this does not work either, now it shows me that I can install to the usb key I have The usb key is on /dev/sdc1 and I got this by entering
<tab> inst.dd=/dev/sdc1/kmod-cciss-3.6.26-3.clearos7.njh.x86_64.rpm<enter>
I'll try once again, but this is really hard. -
Accepted Answer
-
Accepted Answer
Nick Howitt wrote:
Can you copy my rpm to the root of your flash drive then use inst.dd=/sda1/my.rpm or just set inst.dd and it will prompt you for a location?
<esc>inst.dd told that no such image inst.dd
<tab>inst.dd did show possible locations for driver disk, and the usb key was there, but that did not help
<tab>inst.dd=/dev/sdc1/kmod-cciss-3.6.26-3.clearos7.njh.x86_64.rpm proceeded but did not help at all.
Damnit I would like to have this ClearOS on my Proliant but maybe I need to see some alternative Debian based Firewall disto... soon. -
Accepted Answer
There is not essential filesystem under a block device. You can actually browse for files (somewhat, more like scan) during the install. Simply leave inst.dd all by itself on the kernel line.
Check this out as well:
https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Installation_Guide/sect-driver-updates-performing-ppc.html -
Accepted Answer
Please login to post a reply
You will need to be logged in to be able to post a reply. Login using the form on the right or register an account if you are new here.
Register Here »