@ITstaff Hello there.
Re:
As @Hooverdan indicated this controller has some quirks and under one kernel driver presents drive names that are just not recognised by Rockstor. They kernel drivers presented the drives as regularly named scsi devices. This is what you need. Rockstor uses by-id names.
What is the output of for example (run as the root user setup during install):
ls -la /dev/disk/by-id/
also to see the drivers that are being loaded could you past the output of:
lsmod
It may be the older driver is still being used and we may have to try and persuade the our openSUSE Leap OS kernel to do the right thing with this controller. If it’s possible. As @Hooverdan stated there is the need to have the hardware scsi setup (via it’s bios/firware setup) to present the drives individually, and we need the correct (later) driver to be used so that the drive names presented to the rest of the operating system (and thus to Rockstor).
Take a look also as:
So partially from memory, on the raid card driver from, we have:
cciss = non scsi compatible and has weird device names that Rockstor known nothing about.
hpsa = newer scsi driver that presents drives in a way Rockstor does know about and can use.
But the problem may be, especially given the serial number error, that the cciss is the default driver for older P410i cards. But one can coax the newer compatible driver into driving the older raid controllers via an “hpsa_allow_any=1” module option.
The following thread, although pertaining to our now legacy CentOS based v3 may also help with some background on getting the cciss driver out of the way and the hpsa in by default via grub kernel command line options:
Again this may all not be the problem at all, but one first has to have the raid controller itself setup to present the drives individually. Then the OS should see them. Then they have to be of the newer scsi type.
Apologies for a load of info at once here but just trying to present the potential hickups with some of these older raid controllers. I really don’t know which driver is now active for this raid controller, hence the lsmod request. As if it’s the older cciss that is in charge then there is no compatibility there. But if it’s the newer hpsa then you should be OK.
This, at least initially, is because by default we have an empty smartmontools configuration. We follow our default upstream on this front. See the new doc entry by @Hooverdan on this:
https://rockstor.com/docs/howtos/smart.html#configure-monitoring
But smart monitoring through hardware raid controller can be tricky. See later on in that same doc section for some more info. Plus you need to ensure you have proper scsi drive names first, not the weird cciss names.
I hope I haven’t confused matters more. You are the first forum poster to be engaging with us since the new v4 “Built on openSUSE” (which is openSUSE Leap 15.3 based) who is using one of these older between-drivers raid controllers. And as stated I’m really not sure which driver, by default, grabs this older raid controller. And the last forum link above indicates the potentially required module ‘switches’/optinos. One to have cciss leave well alone, and the other to allow the hpsa to reach-back to manage these older cards so they can be presented in scsi standard form.
Unfortunately I don’t have one of these controllers here to test with. But we may be able to sort out what is needed here and then add a doc section on some installer tweak to address this module issue if it in fact is down to that.
Hope that help