[QUOTE=jmozdzen;17018]Hi lpphigpg,
opening the ticket is a good idea - is it already closed or is SUSE still looking into it to see if they can help? If you’d share the SR number (via private message) I’ll try to take a look at the details.[/QUOTE]
The ticket is open but the response was pretty much, “we see no evidence of compatibility, tough luck”… I’ll send the SR#, thanks!
[QUOTE=jmozdzen;17018]
“SLES11” in this context is especially relating to the kernel/driver that is used to access the SCSI card. Oh, and which SLES11 are we talking about, SP1 as the title suggests? SLES11 (“SP0”) and SP1 use 2.6 kernel, while SP2&SP3 use 3.0 kernels.
Same kernel/driver in SLES as with the non-working box? Is that SCSI card connected to the same library (same lib or at least the same type of lib)? You might want to look into firmware versions of the library, if one works and another one of the same model and make doesn’t.[/QUOTE]
The problem server is SLES11 sp2;
But here’s an update: as a test last night, I set up another Dell R-710 with the exact same type card, connected to another TL2000 (both TL2000s have the latest firmware, that was one thing Dell had me update) and installed SLES11sp2… and it works just fine.
These setups are identical in nearly every respect, except I had run updates on the problem server.
I looked at the modules under /lib/modules/3.0.93.-0.5-default/kernel/drivers/message/fusion, the dates on the problem box modules is 8/27/31, but on the working server just installed, they’re 2/15/2012.
Notably, the kernel is slightly older on the working server: 3.0.13-0.27-default. So yeah, something in the updated kernel but not from the Service Pack itself) seems to have broken the card.
[QUOTE=jmozdzen;17018]
The problem probably relates exactly to the fact that the card isn’t ancient - these cards carry an embedded system that operates as an independent computer system, initialized by firmware and handling all the bus traffic. The more recent the card, the more sophisticated theses controllers get and the less time manufactures have to spend on debugging their firmware and drivers - at least that’s what my experience tells me. Add a community-developed driver to that picture (relying on consistent and stable controller APIs across all “supported” card models and firmwares) and you’ll see why it sometimes needs only a minor card/firmware update to break things badly.
This is why I recommended contacting LSI and/or Dell in my first response - they do know which version of driver and (Linux-shipped) firmware works, sometimes vendors even provide their own, updated drivers for Linux Enterprise versions. As I see it, you bought all hardware components from a single vendor - you wrote you contacted them, but did not write what they said. Is your SLES11 version a supported OS on that hardware platform?[/QUOTE]
Thanks, that’s interesting, enlightening… and depressing. I bought the cards back in March of 2012. (I still have the PO) Dell didn’t find anything for an update.
They pointed me to LSI’s website, I guess contacting them is my next step.
[QUOTE=jmozdzen;17018]
From what my “crystal ball” tells me, this is a software-related problem. But as we’re talking about kernel drivers here, simply copying over ancient driver files (SLES10 drivers on a SLES11SP3 system) won’t work and will break things completely - these drivers are kernel-version-specific. My hope goes for a firmware/driver recommendation from Dell/LSI or some Dell support pack for your SLES11 version, shipping updated drivers/firmware optimized and tested by the vendor.
It all depends on the vendor stating that your SLES11 is supported on your hardware. Did you get any feedback to that question?
Regards,
Jens[/QUOTE]
Well, I know now I wouldn’t have to copy the modules from SLES10, perhaps un-updated SLES11sp2 modules would work but, there’s still the minor difference in kernel - 3.0.93.-0.5-default vs 3.0.13-0.27-default. Not sure if that’s a problem nor not.
If I tried it, how much damage could it do? It already doesn’t work… could I get a kernel panic that prevented me from booting the machine? (It shouldn’t affect the RAID array, that’s a megaraid SAS driver, altogether different.)
Which vendor? It’s kinda both Dell and LSI. Dell is stumped.
Contacting LSI is next option but they list no drives… they consider this thing legacy already, last I checked.
I can check for newer firmware for the card at least.
I’m worried the catch22 is probably going to be: too old to support, too new to work correctly.
# rpm -qf /lib/modules/3.0.93-0.5-default/kernel/drivers/message/fusion/mptbase.ko