As you are making the raid array via the motherboard BIOS it is likely that the specifics of the raid array from the new motherboard are different from those on the previous motherboard.
Hardware raid via the bios is different for each motherboard and you can’t take a raid array from one motherboard and have it easily accessed by another.
EDIT: Just realised that BIOS based raid is also software based and not hardware based but the software is specific to each motherboard manufacturer, hence the problems trying to get BIOS raid drives recognised and accessed by another manufacturers BIOS raid software.
Maybe that is where the issue is with IPFire.
EDIT: The question might be whether the linux system has drivers for the specific bios raid software on the new motherboard.
If IPFire saw the raid array on your old motherboard then maybe that manufacturer got its driver added into the kernel drivers.
All my raid array testing with ExtraHD has been with raid arrays that were software raid based on mdadm and those were properly seen with the new ExtraHD cgi code.
To add a comment into the IPFire bugzilla you have to login but your IPFire People email and password credentials will allow you to login.
That message is saying that the Intel Storage Matrix Raid signature has been found, which is the BIOS raid software approach used on your motherboard.
Reading about ISW it indicates that dmraid is the linux software package that would be able to recognise the ISW structured raid system. The dmraid software package is not on IPFire.
mdadm is the linux raid system software on IPFire. Searching on the internet apparently some versions of mdadm have been able to read ISW based raid systems but not all of them and not with newer versions of mdadm, which is the one running on IPFire for some time.
So the above gives an idea why your BIOS raid based on ISW is not recognised by IPFire.
What I don’t understand is why the BIOS raid on your previous motherboard was recognised by IPFire. What Core Update of IPFire were you running on that previous KONTRON motherboard?
Core Update 156 is 2.5 years old with a lot of core updates in between. You really should look at updating more frequently, especially for a security device like a firewall. There have been quite a few CVE vulnerabilities identified in that time period covering packages like the kernel, openssl, openssh, curl etc all of which you will not have had protection from.
That time period also includes an update in mdadm from version 4.1 to 4.2 and that update includes around 2 years worth of development and bugfixes and in that collection there were enhancements and bugfixes for IMSM Raid which is Intel Matrix Storage Manager.
Likely that something in that update no longer works with the version of IMSM Raid coming from your new motherboard. Also likely that if you installed Core Update 180 on your KONTRON motherboard you would also have had the same problem.
I would suggest that if you can start afresh with the two raid drives (ie not critical data stored on them) then your best bet is to configure your raid array on the two drives using mdadm on the IPFire machine. I am presuming that the two drives are not intended for the IPFire operating system but as Extra Hard Drives.
I have checked through the kernel modules code in IPFire and there is a line
CONFIG_INTEL_RST=m
So the Intel RST driver module is installed but it is not loaded. That is normal as most users won’t require it.
I believe that normally if it is needed it should be automatically loaded but maybe on your new motherboard it is not correctly flagging that it needs the Intel RST driver.
You could try lsmod | grep rst
which will show if any rst module is loaded. It will likely come back with no output showing no rst module loaded.
Then run modprobe intel_rst followed again by lsmod | grep rst
and you should see something like
lsmod | grep rst
intel_rst 16384 0
which I did on my system and which shows that the intel_rst module is now loaded.
You can then check if you can see the raid drive now.
If yes then you will need to add the modprobe command into rc.local to run and load the module when you start up your IPFire as obviously the motherboard is not triggering the loading of the module. https://wiki.ipfire.org/pkgs/rc-local
This will load the module each time you boot your IPFire. Once loaded it will stay loaded until IPFire is shutdown or rebooted.
What might be a “bug” is that I cannot mount md127 in the EXTRAHD menu. It says “You cannot mount md127”. If I enter it manually in fstab, everything is fine, it mounts immediately at startup.
On the ExtraHD page I could see the raid array drive and I was able to mount it on /mnt/data3
I then rebooted and the raid array was mounted after restarting.
So I can’t duplicate the problem you are experiencing.
That is why I have detailed the steps I took to create the raid array in case there is something different in the way you have created it.
The reason my raid array shows as md126 is that on my vm system I have the IPFire OS installed on a raid system so that is already using the md127 label.
Name : wrouter.srv:0 (local to host wrouter.srv)
UUID : 473141d6:060116f2:398aa4cf:291e7619
Events : 0
Number Major Minor RaidDevice State
0 8 1 0 active sync /dev/sda1
1 8 17 1 active sync /dev/sdb1
When I tried to mount md127 with EXTRAHD, it said “I cannot mount md127”. But I mounted it successfully by entering it in fstab.
Yes, it should have said that the mount path was not allowed but the typo meant that section was never printed because the entry could not be matched in the language files.
I think it is limited because of permissions aspects to be able to consistently work and because in the past it has not been unknown for users to try /dev or /proc
Please confirm that it works again for you if you use one of the alternative mount points.
Other than the very expensive server raid controllers, motherboard bios based raid is garbage, todays higher speed processors will see no performance loss with software raid under Linux and is prefered and movable from machine to machine. Best to forget the Bios raid and do software raid although think if can on IPfire would be command line options have to look. Other option is to get a known add on raid controller than can be moved, and can be replaced by same model so raid is recoverable.