Hi!

I have one RS3DC080 controller on win2016 srv with 8core 1.7GHz CPU.

I have installed Intel RAID Web Console 3 on it and i don't satisfied by that functionality.

Is it possible to automate sending log messages into syslog server or at least into the file using or without webconsole (w/o webconsole case would be preferable)? Now i see just manually log download button in web console.

I have found some log file in C:\Program Files (x86)\LSI\LSIStorageAuthority\logs but there is multiple repeated messages like:

13/04 18:56:29 11f0 | Error:  Failed to free Memory

13/04 18:56:59 680 | Error:  Failed to free Memory

13/04 18:57:29 11f0 | Error:  Failed to free Memory

13/04 18:57:54 16e8 | Error:  Failed to free Memory

13/04 18:58:29 11f0 | Error:  Failed to free Memory

13/04 18:58:49 165c | Error:  Failed to free Memory

13/04 18:59:29 11f0 | Error:  Failed to free Memory

13/04 18:59:29 1200 | Warning:  DCMD_FW_call_Info: ctrl=0 DCMD=0x2010000  status=0x0

13/04 18:59:29 1200 | Warning:  DCMD_FW_call_Info: ctrl=0 DCMD=0x2010000  status=0x0

13/04 18:59:29 1200 | Warning:  SL_FW_call_Info: ctrl=0 SL_CMD_TYPE = 6 SL_CMD = 0 status = 0x0

13/04 18:59:29 1200 | Warning:  SL_FW_call_Info: ctrl=0 SL_CMD_TYPE = 6 SL_CMD = 0 status = 0x0

13/04 18:59:29 1200 | Warning:  SL_FW_call_Info: ctrl=0 SL_CMD_TYPE = 6 SL_CMD = 0 status = 0x0

13/04 18:59:29 1200 | Warning:  SL_FW_call_Info: ctrl=0 SL_CMD_TYPE = 6 SL_CMD = 0 status = 0x0

13/04 18:59:29 1200 | Warning:  SL_FW_call_Info: ctrl=0 SL_CMD_TYPE = 6 SL_CMD = 0 status = 0x0

13/04 18:59:29 1200 | Warning:  SL_FW_call_Info: ctrl=0 SL_CMD_TYPE = 6 SL_CMD = 0 status = 0x0

13/04 18:59:29 1200 | Warning:  SL_FW_call_Info: ctrl=0 SL_CMD_TYPE = 6 SL_CMD = 0 status = 0x0

13/04 18:59:29 1200 | Warning:  SL_FW_call_Info: ctrl=0 SL_CMD_TYPE = 6 SL_CMD = 0 status = 0x0

13/04 18:59:29 1200 | Warning:  DCMD_FW_call_Info: ctrl=0 DCMD=0x1010000  status=0x0

13/04 18:59:29 1200 | Warning:  DCMD_FW_call_Info: ctrl=0 DCMD=0x1080101  status=0x0

13/04 18:59:45 6dc | Warning:  DCMD_FW_call_Info: ctrl=0 DCMD=0x5010000  status=0x0

13/04 18:59:45 6dc | Warning:  DCMD_FW_call_Info: ctrl=0 DCMD=0x5030000  status=0x0

13/04 18:59:45 6dc | Warning:  DCMD_FW_call_Info: ctrl=0 DCMD=0x5050100  status=0x0

13/04 18:59:45 6dc | Error:  Failed to free Memory

13/04 19:00:29 11f0 | Error:  Failed to free Memory

13/04 19:00:40 1674 | Error:  Failed to free Memory

13/04 19:01:29 11f0 | Error:  Failed to free Memory

while in web console there is nothing erros\warnings:

Hello,

I have read on the VMware website that ESXi 5.x supports RSTe on the SATA/SAS capable C600 chipset and have a few questions...

1. Is an add in driver required or will it install with the downloadable ESXi install DVD.
2. How do you manage arrays inside VMware
3. Does it only work on 1400/1600/2400/2600 series boards or will it work on S1200V3RPS/L which also use RSTe ?

Apologies a newbie to VMware.

Regards,

GT

I'm trying to get remote LAN access to BMC on S1200V3RP (Rainbow Pass). The IP is set to static configuration with valid IP address on my network, all users are enabled and assigned password in setup, but no matter what I try, BMC doesn't respond to any attempts to communicate with it via LAN. I tried Ipmiutil, nmap, ssh, IPMIView...

The system runs Ubuntu, and it does have network connection via onboard LAN, so I am pretty positive it's not a HW issue. Ipmitool can access BMC locally, and I can verify the LAN setup of BMC corresponds to what I have configured in setup.

The system doesn't have RMM4 installed, just plain board with no extras. The BMC is Emulex Pilot III (?).

Is the BMC supposed to be accessible? Is there anything else I need to do, like a secret jumper, magical setup question... or it's simply not supposed to work?

ipmitool mc info:

Device ID: 33

Device revision: 1

Firmware revision: 1.13

IPMI Version: 2.0

BTW: I have the same problem with my Aztec City, again Emulex Pilot III. I don't have any problems with my Supermicro board using Nuvoton BMC.

I'll be grateful for any hints or suggestions!

Prior to replacing the 3V battery on the mother board, this command: "Ipmitool lan print 1" returned useful information.  Now the command returns: Invalid channel: 1.

Did I lose a configuration setting and if so, what change do I need to make? 

Hello,

I have a server mothebord S3420GP with 6 memory slots.

Now, I have 2 slots filled with these: 2x KINGSTON 4GB 1333MHz DDR3 ECC CL9 DIMM with Thermal Sensor.

Is possible to use another 4 these RAMs? So I would have 24 GB RAM with 6 x 4 GB. Is this combination possible?

Or is possible to use 4 x KINGSTON 8GB DDR3 1333MHz CL9 ECC Dual Rank BOX.

So total memory size will be 32 GB RAM.

Thanks for any answers.

Hi

I have installed two P4600 NVME devices in a server and installed Proxmox 5.1-3.  The running kernel is 4.13.13-6-pve.  There is no RAID controller involved.

# nvme list

Node             SN                   Model                                    Namespace Usage                      Format           FW Rev

---------------- -------------------- ---------------------------------------- --------- -------------------------- ---------------- --------

/dev/nvme0n1     BTLE736103CH4P0KGN   INTEL SSDPEDKE040T7                      1           4.00  TB /   4.00  TB    512   B +  0 B   QDV10170

/dev/nvme1n1     BTLE736103AG4P0KGN   INTEL SSDPEDKE040T7                      1           4.00  TB /   4.00  TB    512   B +  0 B   QDV10170

The output of "isdct show -a -intelssd" is attached in the file "intelssdp4600-2.txt".

Now by using LVM I can always reproduce a "hanging" behaviour of 1-2 minutes that does not lead to any fatal error:

vgcreate SSD /dev/nvme0n1 /dev/nvme1n1

lvcreate -l 100%FREE -n SSDVMSTORE01 --stripes 2 --stripesize 128 --type striped SSD

lvremove -d -v SSD/SSDVMSTORE01

Do you really want to remove and DISCARD active logical volume SSDTEST/SSDTEST01? [y/n]: y

here the command seems to be hanging for 1-2 minutes.  in the Logs I see:

Feb 21 14:14:17 px kernel: [ 3654.745355] nvme nvme0: I/O 200 QID 14 timeout, aborting

Feb 21 14:14:17 px kernel: [ 3654.745772] nvme nvme0: I/O 201 QID 14 timeout, aborting

Feb 21 14:14:17 px kernel: [ 3654.746110] nvme nvme0: I/O 202 QID 14 timeout, aborting

Feb 21 14:14:17 px kernel: [ 3654.746436] nvme nvme0: I/O 203 QID 14 timeout, aborting

Feb 21 14:14:32 px kernel: [ 3669.013614] nvme nvme0: Abort status: 0x0

Feb 21 14:14:32 px kernel: [ 3669.014012] nvme nvme0: Abort status: 0x0

Feb 21 14:14:32 px kernel: [ 3669.014325] nvme nvme0: Abort status: 0x0

Feb 21 14:14:32 px kernel: [ 3669.014629] nvme nvme0: Abort status: 0x0

Feb 21 14:15:10 px kernel: [ 3707.737495] nvme nvme1: I/O 297 QID 14 timeout, aborting

Feb 21 14:15:10 px kernel: [ 3707.737902] nvme nvme1: I/O 298 QID 14 timeout, aborting

Feb 21 14:15:10 px kernel: [ 3707.738231] nvme nvme1: I/O 299 QID 14 timeout, aborting

Feb 21 14:15:10 px kernel: [ 3707.738547] nvme nvme1: I/O 300 QID 14 timeout, aborting

Feb 21 14:15:25 px kernel: [ 3722.005726] nvme nvme1: Abort status: 0x0

Feb 21 14:15:25 px kernel: [ 3722.006113] nvme nvme1: Abort status: 0x0

Feb 21 14:15:25 px kernel: [ 3722.006434] nvme nvme1: Abort status: 0x0

Feb 21 14:15:25 px kernel: [ 3722.006751] nvme nvme1: Abort status: 0x0

After this, the command completes without error.

This does not happen with Debian 9.3 (Kernel 4.9.x).  If I partition the devices with one 2GB primary partition and do the same operation but with /dev/nvmeXn1p1 or p2  the timeout does happen on the second partition but not on the first:

parted -a optimal /dev/nvme0n1 mklabel gpt

parted -a optimal /dev/nvme0n1 mkpart primary 4 2047

parted -a optimal /dev/nvme0n1 mkpart primary 2048 100%

parted -a optimal /dev/nvme1n1 mklabel gpt

parted -a optimal /dev/nvme1n1 mkpart primary 4 2047

parted -a optimal /dev/nvme1n1 mkpart primary 2048 100%

Any clues?

Best,

Pierre

Hi Team,

We have Intel Server System R2224WFTZS with minimum configuration(Single processor & Memory).

Please let me know whether I can use all the available PCIe slots with single CPU?

Thanks!

Hi, downloaded RAID Web Console 3 from here Download Intel® RAID Web Console 3 for Windows*

- Install the GATEWAY server on a remote machine, can log in ok.

- Installed the RAID driver version (SAS v6.713.05.00 (Trimode wont load, even though its listed there doesnt appear to be drivers in the package for this card)) for the RMS3CC090 on a S1200SPOR server running Windows 10 Pro

- Installed the DIRECT AGENT service for RAID Web Console 3 on the above server.

Logging in to the GATEWAY server, then pressing "Re-discover servers", this remote Windows 10 S1200SPOR with the RMS3CC080 never shows up.

We have disabled the firewall on the Windows 10 system

We have disabled the firewall on the gateway server

Is there no way of adding servers to the gateway server?

All documentation for Intel RAID Web Console 3 says the RMS3CC080 is fully supported...

Many Thanks

First of all I apologize for incorrect English, I'm using google translator. I have a s1200btsr with Xeon processor, it was working normally, suddenly it started to make a strange noise like it had a cable twisted in the cooler.

I try to call it already starts with this noise, as if a cable was catching on the cooler, or a bursting speaker. It has no beep and does not turn on the corner leds.

Hi,

I've just been given an ancient, refurbished S2600CP2J motherboard complete with CPUs and RAM and would like to get it fully working again.

The obvious first step is to update the BIOS but the oldest EFI update package available (01.02.003) states that I need to have at least version 01.01.1002 before starting or "the update process may render the system not operatable!"

According to the BIOS screen, my system is currently SE5C600.86B.99.99.x034, build date 08/23/2011.

As I have no wish to kill the system before I get started, is there any way of upgrading it to 01.01.1002 as a minimum?

Thanks.

Hi

I have installed two P4600 NVME devices in a server and installed Proxmox 5.1-3.  The running kernel is 4.13.13-6-pve.  There is no RAID controller involved.

# nvme list

Node             SN                   Model                                    Namespace Usage                      Format           FW Rev

---------------- -------------------- ---------------------------------------- --------- -------------------------- ---------------- --------

/dev/nvme0n1     BTLE736103CH4P0KGN   INTEL SSDPEDKE040T7                      1           4.00  TB /   4.00  TB    512   B +  0 B   QDV10170

/dev/nvme1n1     BTLE736103AG4P0KGN   INTEL SSDPEDKE040T7                      1           4.00  TB /   4.00  TB    512   B +  0 B   QDV10170

The output of "isdct show -a -intelssd" is attached in the file "intelssdp4600-2.txt".

Now by using LVM I can always reproduce a "hanging" behaviour of 1-2 minutes that does not lead to any fatal error:

vgcreate SSD /dev/nvme0n1 /dev/nvme1n1

lvcreate -l 100%FREE -n SSDVMSTORE01 --stripes 2 --stripesize 128 --type striped SSD

lvremove -d -v SSD/SSDVMSTORE01

Do you really want to remove and DISCARD active logical volume SSDTEST/SSDTEST01? [y/n]: y

here the command seems to be hanging for 1-2 minutes.  in the Logs I see:

Feb 21 14:14:17 px kernel: [ 3654.745355] nvme nvme0: I/O 200 QID 14 timeout, aborting

Feb 21 14:14:17 px kernel: [ 3654.745772] nvme nvme0: I/O 201 QID 14 timeout, aborting

Feb 21 14:14:17 px kernel: [ 3654.746110] nvme nvme0: I/O 202 QID 14 timeout, aborting

Feb 21 14:14:17 px kernel: [ 3654.746436] nvme nvme0: I/O 203 QID 14 timeout, aborting

Feb 21 14:14:32 px kernel: [ 3669.013614] nvme nvme0: Abort status: 0x0

Feb 21 14:14:32 px kernel: [ 3669.014012] nvme nvme0: Abort status: 0x0

Feb 21 14:14:32 px kernel: [ 3669.014325] nvme nvme0: Abort status: 0x0

Feb 21 14:14:32 px kernel: [ 3669.014629] nvme nvme0: Abort status: 0x0

Feb 21 14:15:10 px kernel: [ 3707.737495] nvme nvme1: I/O 297 QID 14 timeout, aborting

Feb 21 14:15:10 px kernel: [ 3707.737902] nvme nvme1: I/O 298 QID 14 timeout, aborting

Feb 21 14:15:10 px kernel: [ 3707.738231] nvme nvme1: I/O 299 QID 14 timeout, aborting

Feb 21 14:15:10 px kernel: [ 3707.738547] nvme nvme1: I/O 300 QID 14 timeout, aborting

Feb 21 14:15:25 px kernel: [ 3722.005726] nvme nvme1: Abort status: 0x0

Feb 21 14:15:25 px kernel: [ 3722.006113] nvme nvme1: Abort status: 0x0

Feb 21 14:15:25 px kernel: [ 3722.006434] nvme nvme1: Abort status: 0x0

Feb 21 14:15:25 px kernel: [ 3722.006751] nvme nvme1: Abort status: 0x0

After this, the command completes without error.

This does not happen with Debian 9.3 (Kernel 4.9.x).  If I partition the devices with one 2GB primary partition and do the same operation but with /dev/nvmeXn1p1 or p2  the timeout does happen on the second partition but not on the first:

parted -a optimal /dev/nvme0n1 mklabel gpt

parted -a optimal /dev/nvme0n1 mkpart primary 4 2047

parted -a optimal /dev/nvme0n1 mkpart primary 2048 100%

parted -a optimal /dev/nvme1n1 mklabel gpt

parted -a optimal /dev/nvme1n1 mkpart primary 4 2047

parted -a optimal /dev/nvme1n1 mkpart primary 2048 100%

Any clues?

Best,

Pierre

Hi,

I've just been given an ancient, refurbished S2600CP2J motherboard complete with CPUs and RAM and would like to get it fully working again.

The obvious first step is to update the BIOS but the oldest EFI update package available (01.02.003) states that I need to have at least version 01.01.1002 before starting or "the update process may render the system not operatable!"

According to the BIOS screen, my system is currently SE5C600.86B.99.99.x034, build date 08/23/2011.

As I have no wish to kill the system before I get started, is there any way of upgrading it to 01.01.1002 as a minimum?

Thanks.

Hi . Where I can get power 5V  for SSD disk attached to sata port 4 on platform in 1208WTTGSR ?

Port 4 sata   & port5  sata   are inside platform  (on image )

Hello Members,

I have a motherboard Intel S2600CP running inside a Coller Master Chasis for 2.5 years and it was replaced. Now I have a new replacement board, 1 Xeon CPU and 32 Gigs of Ram. The PSU has been Changed to Antec HCG-850W.

Here is the problem;

1. I installed Windows 10 on this and it worked fine for 2 days; After a sudden power cycle; it will boot up and then reboot automatically couple of times and then the beeps would be 1-5-4-2.

2. This continued couple of times. Clearing the CMOS and waiting for the 2 green light to glow; did the trick I was able to boot up; I read that from a thread linked below.

3. I updated BIOS to S2600CP_EFI_BIOS02060006_ME020107328_BMC0128r10603_FRUSDR111 and there was one successful boot to OS after this

4. There was a software BSOD after this; and now it does not POST even after clearing the CMOS. The error code now is 1-5-4-4 and the light stays at amber

Any suggestion where the issue lies?

Please see some similar threads;

S2600CP2 - On losing PSU power, it won't post, except after a CMOS flash, even on a clean shutdown from OS - Feature or known issues and how to change if its a feature?

S2600CP board - Need a CMOS flash for every boot, where the PSU lost power (on purpose) | ServeTheHome and ServeThe.Biz …

Thanks in advance!!

I use Intel's dual-server server S2600CP2 and Windows Server 2008 R2 operating systems. After installing the INTEL RSTE GUI, when setting up a mail reminder, after entering the SMTP mail server address and port and the sender and recipient email addresses, Send test mail each unsuccessful, for a lot of SMTP mail server address and port number, as well as the sender and the recipient's mail address will not work. And I was thinking, if you do not need to enter the login password of the mailbox, how can it send a test mail? I need to remind the function of mail, how should I properly set it, in order to normal use of the e-mail alert function.

Good Day.

I am tried enable "OS boot watchdog timer" at BIOS, but my OS (Window 10 - 1709) always rebooted.

I didnt find Intel Watchdog driver and i dont understand how i should install it.

I am really need your help.

How i should check this driver? Does this function support Windows 10?

Hello,

I met a strange issue with this board and ESRT2 driver.

For the beginning, I would like to say that, if I do a clean installation of Windows 10 and offer ESRT2 v17 driver and finish installation - all good and no problems.

We have a WDS server for OS installation and if I do a clean installation from there, then there appeard Intel RSTe driver instead, despite the fact I have ESRT2 controller enabled.

The problem appears, when I update this driver to v17 from USB stick and restart the server. Then Event ID 153 with disk warning appears in System Event Log.

Once driver rolled back - all good. I removed all 3d party drivers with DISM and only v17 ESRT2 driver left. Still problem appears.

Seems like there is some kind of conflict with another driver or something else. I have 6 servers right now where this problem appears.

Clean installation of Windows 10 solves the problem, but there should be an easier way to fix it.

Can you give any hint what to try?

regards,

Sergei.

I use Intel's dual server S2600CP2 and Windows Server 2008 R2 operating systems. When I set up boot from EFI, Intel Embedded Server RAID Technology 2 could not be found under the Advanced Tab in BIOS, which means I could not use Human Interface Infrastructure Configuration Utility, how should I solve the problem, I checked a lot of Intel's technical documentation, did not find helpful to me.

Hi

We have connected a PCI-e display adapter (nVidia) inside this server, Windows 10 does not see any new hardware, we do not get any video from this adapter (on boot or Windows), we have the BIOS drivers loaded.

Are there any standards that need to be met in the new card for the system to see it?  How can we tell in BIOS if it sees the new adapter?

The card we are testing (Jaton nVidia VIDEO-PX628GS-LP1), works in other Intel boards (DX79xx series).

Will the XXV710-DA2 OCP Module (XXV710DA2OCP{1,2}) work in S2600WF Wolf Pass systems, specifically in the R2308WFTZS platform?

If so, should one get XXV710DA2OCP1 (OCP Type 1 Mezzanine Module with 8mm stacking) or XV710DA2OCP2 (OCP Type 2 Mezzanine Module with 12mm stacking)?

I presume the Type 1 with 8mm stacking since the S2600WFT board already has a cutout in the area designated for the OCP mezzanine module.