Community Forum

Resolved
0 votes
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?
Saturday, June 17 2017, 10:14 AM
Share this post:

Accepted Answer

Friday, June 23 2017, 05:39 PM - #Permalink
Resolved
0 votes
Meanwhie, I am leaning towards OPNsense, and it installed to the Proliant with no problems. It detected the raid and supports it fully.
The reply is currently minimized Show
Responses (15)
  • Accepted Answer

    Friday, June 23 2017, 05:33 PM - #Permalink
    Resolved
    0 votes
    It just does not recognise the rpm as a driver update, as offered as is. I wonder if I really need to roll it inside an iso or not. Now it is in the root of my clonezilla USB key, and I have tried inst.dd=/dev/sdc1 and inst.dd=/dev/sdc1/name-of-the.rpm and inst.dd

    Nothing works.
    The reply is currently minimized Show
  • Accepted Answer

    Friday, June 23 2017, 03:38 PM - #Permalink
    Resolved
    0 votes
    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
    The reply is currently minimized Show
  • Accepted Answer

    Thursday, June 22 2017, 09:31 PM - #Permalink
    Resolved
    0 votes
    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.
    The reply is currently minimized Show
  • Accepted Answer

    Thursday, June 22 2017, 09:07 PM - #Permalink
    Resolved
    0 votes
    Really really hard, as there is additional hardship to have a Finnish keyboard with US settings on boot (I can handle that OK) and no mouse working. I have a PS/2 mouse AND and USB mouse connected but neither of them work in the setup!
    The reply is currently minimized Show
  • Accepted Answer

    Thursday, June 22 2017, 09:02 PM - #Permalink
    Resolved
    0 votes
    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.
    The reply is currently minimized Show
  • Accepted Answer

    Wednesday, June 21 2017, 04:11 AM - #Permalink
    Resolved
    0 votes
    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.
    The reply is currently minimized Show
  • Accepted Answer

    Tuesday, June 20 2017, 09:09 PM - #Permalink
    Resolved
    0 votes
    Me too as it was marked as solved on Sunday but then the flag got removed.
    The reply is currently minimized Show
  • Accepted Answer

    Tuesday, June 20 2017, 08:56 PM - #Permalink
    Resolved
    0 votes
    Jari,

    I'm curious to see if this worked for you.
    The reply is currently minimized Show
  • Accepted Answer

    Monday, June 19 2017, 07:02 PM - #Permalink
    Resolved
    0 votes
    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?
    The reply is currently minimized Show
  • Accepted Answer

    Monday, June 19 2017, 06:53 PM - #Permalink
    Resolved
    0 votes
    Jari Fredriksson wrote:

    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:

    1. Prepare a VirtualBox VM using the ClearOS ISO
    2. Setup the elrepo as a repo to the VM and install the required driver from that.
    3. Export that using Clonezilla. Appears that Clonezilla supports the HP Smart Array tech.
    4. 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.
    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.
    The reply is currently minimized Show
  • Accepted Answer

    Monday, June 19 2017, 04:35 PM - #Permalink
    Resolved
    0 votes
    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:

    1. Prepare a VirtualBox VM using the ClearOS ISO
    2. Setup the elrepo as a repo to the VM and install the required driver from that.
    3. Export that using Clonezilla. Appears that Clonezilla supports the HP Smart Array tech.
    4. 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.
    The reply is currently minimized Show
  • Accepted Answer

    Monday, June 19 2017, 01:27 PM - #Permalink
    Resolved
    0 votes
    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
    The reply is currently minimized Show
  • Accepted Answer

    Sunday, June 18 2017, 10:03 AM - #Permalink
    Resolved
    0 votes
    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...
    The reply is currently minimized Show
  • Accepted Answer

    Sunday, June 18 2017, 07:01 AM - #Permalink
    Resolved
    0 votes
    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).
    The reply is currently minimized Show
  • Accepted Answer

    Sunday, June 18 2017, 12:59 AM - #Permalink
    Resolved
    0 votes
    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.
    The reply is currently minimized Show
Your Reply