driver for LSI SAS1068

[v5134]

I am having troubles with installing SPLAT R60 on HP DL360 G4 with LSI SAS1068 raid controller. I have used driver disk SPLAT_NGX_R60_DriverDisk_B.img but it helped at first stage of installation only. After reboot SPLAT still uses old drivers and can not access to the disks. As I can see, there are drivers for BOOT kernel only. Where are drivers for cpsmp kernel?

[kva.kva]

I think the best way is to consult CP support. I don't see any easy ways to resolve with problems.
You can try to load server from cd then try to mount file system and change module file, for example. But it's not so simple. And there are a lot of chances that it will not work after that.

[danny92]

I'm facing the same issue, the modules installed in stage1 of installation (mptscsih.o, mptbase.o) don't work on first boot of splat.
Did you succeed in installing SPLAT R60 on LSI SAS1068 mass storage controller ?
I'm considering trying R60a and R61 as soon as I get Media Pack, the kernel version is different so the modules should have been corrected.
Any information related to this issue ?

[danzel]

count me in im having trouble with my intel 6300esb sata raid controller.

[chillyjim]

The R60_HFA03 media/ISO has the latest build of SPLAT on it. Try that and if it doesn't work you'll have to call support.

[danny92]

Sorry for the delay.

I suggest you to ask for the support, as they have an R61 development ISO which works (build 602000136).
They also gave me a link to a R60 ISO (build 591604034), I didn't test it either.
The modules mptbase.o and mptscsih.o installed on disk are revision 2.05.16.01, corresponding to bootdisk modules.

They ask me the log in debug mode :

Kdb Mode NGX
On the Gateway run:
# ulimit -a (to see if the core file blocksize is limited)
If it is limited issue:
# ulimit -c unlimited (this should enable the creation of the hole memory 
dump to a file)

In order to start the machine in Kernel Dbug mode:
First of all, we need to change the grub.conf file (under /etc/grub.conf) 
on the crashing SecurePlatform according to our configuration. If you'll 
open the grub.conf you'll see all the Kernel startup options. The one that 
interests us is this one:

title Start in debug mode
root (hd0,0)
kernel /vmlinuz-smp_kdb ro root=/dev/sda3 console=CURRENT 3
initrd /initrd-smp_kdb

The CURRENT should be changed to ttyS0 if we connect the crossed cable 
from COM1 on the crashing machine, and ttyS1 if the we connect to COM2. 
Before changing the grub.conf, please backup it. Reboot the machine and 
follow this procedure:

1. Connect a seperate machine to one of the cluster members using Serial 
cable to COM 1

2. From the seperate machine please connect to the machine (use serial 
application like CRT for example). The connection parameters are the RS232 
default (9600, NONE, 8, 1, NONE).

3. Even without the crash, we should be able to communicate with the 
crashing machine through the COM port. Make sure you have a Serial 
connection with the machine and that you can run commands (the syntax is 
like in telnet

4. Reboot the SecurePlatform and start in [Debugging] mode.

5. Make sure your serial connection is still working and that you can run 
commands through.

6. Now we need to wait till the freeze occurs.

7. When the freeze occurs please type on the serial console machine the 
command "bt" or "bta" (bt should be tried first), this will get the 
required stack from the freeze.

8. In case the keyboard are not responding use CTRL+C or CTRL+A or send a 
break signal from the Serial application and then try the "bt" command 
again.

9. Save the "bt" output and make sure we get all the stack

10. Reboot the module.

11. After changing grub.conf to the original version, reboot is must in 
order to get out from the debug mode.

12. Please send me the file.