similar to: Intel SSD

Hi I have a supermicro server, motherboard is with C612 chipset and beside that with LSI3108 raid controller integrated. Two Intel SSD DC S3710 200GB. OS: Centos 7.1 up to date. My problem is that the Intel SSD Data Center Tool (ISDCT) does not recognize the SSD drives when they connected to the standard S-ATA ports on the motherboard, but through the LSI raid controller is working. Does

I always tell vendors I'm using RHEL, even though we're using CentOS. If you say CentOS, some vendors immediately throw up their hands and say "unsupported" and then won't even give you the time of day. A couple tricks for fooling tools into thinking they are on an actual RHEL system: 1. Modify /etc/redhat-release to say RedHat Enterprise Linux or whatever the actual RHEL

On 18/11/2015 16:37, Eero Volotinen wrote: > What is Intel SSD Data Center Tool (ISDCT) ? " This tool provides a command line interface for interacting with and issuning commands to Intel SSD Data Center devices. It is intended to configure and check the state of Intel PCIe SSDs and SATA SSDs for a production environment. " > Does Linux kernel detect disk on sata ports? >

On 11/18/2015 09:51 AM, Eero Volotinen wrote: > strace -f -e open software_binary might help, but I have noticed that > Centos is not really 100% binary compatible in some cases. CentOS Linux is not 100% bit for bit compatible with RHEL in ANY cases :) CentOS and RHEL are built from mostly the same source code (we remove RH trademarks and take out RHN update pieces). But RHEL source code

On Wed, 18 Nov 2015, Birta Levente wrote: > I have a supermicro server, motherboard is with C612 chipset and beside that > with LSI3108 raid controller integrated. > Two Intel SSD DC S3710 200GB. > OS: Centos 7.1 up to date. > > My problem is that the Intel SSD Data Center Tool (ISDCT) does not recognize > the SSD drives when they connected to the standard S-ATA ports on

What is Intel SSD Data Center Tool (ISDCT) ? Does Linux kernel detect disk on sata ports? Supported usually means that they have tested it and they can say that it works.. Many of hardware still works as linux kernel support lots of drivers -- even they are not officially supported by vendor. -- Eero 2015-11-18 16:25 GMT+02:00 Birta Levente <blevi.linux at gmail.com>: > Hi > > I

strace -f -e open software_binary might help, but I have noticed that Centos is not really 100% binary compatible in some cases. -- Eero 2015-11-18 17:42 GMT+02:00 Matt Garman <matthew.garman at gmail.com>: > I always tell vendors I'm using RHEL, even though we're using CentOS. > If you say CentOS, some vendors immediately throw up their hands and > say

On 11/19/2015 12:54 AM, Birta Levente wrote: > I tried today morning on RHEL too ... > The ISDCT tool does not work on supported OS neither I think everyone focused on your problem with the vendor, who didn't support your OS, and ignored the fact that the tool worked when the drives were connected to a secondary controller. The OS never caused a problem for the tool, only for the

I assume you are using one of the boards described here? http://www.intel.com/support/services/smartconnect/sb/CS-033108.htm On 11/19/2015 10:43 AM, Birta Levente wrote: > It is in AHCI, never was changed > > On 19:26, Thu, Nov 19, 2015 Gordon Messmer <gordon.messmer at gmail.com> wrote: > >> On 11/19/2015 12:54 AM, Birta Levente wrote: >>> I tried today morning

It is in AHCI, never was changed On 19:26, Thu, Nov 19, 2015 Gordon Messmer <gordon.messmer at gmail.com> wrote: > On 11/19/2015 12:54 AM, Birta Levente wrote: > > I tried today morning on RHEL too ... > > The ISDCT tool does not work on supported OS neither > > I think everyone focused on your problem with the vendor, who didn't > support your OS, and ignored

On 18/11/2015 22:35, Johnny Hughes wrote: > On 11/18/2015 09:51 AM, Eero Volotinen wrote: >> strace -f -e open software_binary might help, but I have noticed that >> Centos is not really 100% binary compatible in some cases. > > CentOS Linux is not 100% bit for bit compatible with RHEL in ANY cases :) > > CentOS and RHEL are built from mostly the same source code (we

Hi to all I have a supermicro server with LSI 3108 with - 2x300GB SAS spin drive in raid1 (virtual drive 0) - 2x300GB SAS spin drive in raid1 (virtual drive 1) - 2x200GB Intel SSD DC S3710 drives configured as JBOD in LSI bios In the IPMI storage health status eveything looks fine until I boot into Centos 7.1 (unfortunatelly I didn't try other OS, but also I'm not interested in other)

OS: CentosOS 7 I have installed samba + openldap + smbldap-tools + pam. I create users and groups by: sudo smbldap-groupadd -a g1 sudo smbldap-groupadd -a g2 sudo smbldap-useradd -a -P -g 1001 u1 sudo smbldap-useradd -a -P -g 1002 u1 groups u1 u1 : g1 groups u2 u2 : g2 I create shared folder: cd / sudo mkdir data sudo chown u1 /data sudo chgrp g1 /data sudo chmod ugo+rwx /data I edit

Hi Rowland, Could you refer me some online docs about AD domain? Thanks At 2016-12-04 17:23:48, "Rowland Penny via samba" <samba at lists.samba.org> wrote: >On Sun, 4 Dec 2016 16:57:56 +0800 (CST) >truename via samba <samba at lists.samba.org> wrote: > >> OS: CentosOS 7 >> >> I have installed samba + openldap + smbldap-tools + pam. > >I

OS: CentosOS 7 I have installed samba + openldap + smbldap-tools + pam by: yum --enablerepo=extras install -y epel-release yum install -y smbldap-tools yum install -y samba openldap openldap-clients openldap-servers migrationtools yum install -y nss-pam* I know that smbldap-tools is a dead project, but I'm interested in it and would like research on it. I create users and

Hello everybody, A recent update of the sssd-common-2.8.1-1.el8.x86_64 package is causing sssd.service systemctl failures all over my CentosOS machines. What is the best way to report this issue and when can we expect an update from the sssd-common package for this regression bug? I think sssd-common is part of the baseos repository and installed even when the configuration file is not

Hello, Have Centos a Repository with corrected or newer Packages for KVM. On my brand new System ;-), but also with my older System. I have big problems with KVM guests "slow slow slow", the DomU's are also CentOS 7 virt-manager is also broken with the 7.1 The "old" Bug in the Kernel is really bad, I have several hundreds log from the vcpu0 Problem. thank's for a

On 12/27/22 22:55, Gordon Messmer wrote: > On 2022-12-25 07:44, Jelle de Jong wrote: >> A recent update of the sssd-common-2.8.1-1.el8.x86_64 package is >> causing sssd.service systemctl failures all over my CentosOS machines. > ... >> [sssd] [confdb_expand_app_domains] (0x0010): No domains configured, >> fatal error! > > > Were you previously using

> On 1/3/23 05:17, Orion Poplawski wrote: >> On 12/30/22 04:06, Jelle de Jong wrote: >>> On 12/27/22 22:55, Gordon Messmer wrote: >>>> On 2022-12-25 07:44, Jelle de Jong wrote: >>>>> A recent update of the sssd-common-2.8.1-1.el8.x86_64 package is >>>>> causing sssd.service systemctl failures all over my CentosOS >>>>>

On 12/30/22 04:06, Jelle de Jong wrote: > On 12/27/22 22:55, Gordon Messmer wrote: >> On 2022-12-25 07:44, Jelle de Jong wrote: >>> A recent update of the sssd-common-2.8.1-1.el8.x86_64 package is >>> causing sssd.service systemctl failures all over my CentosOS machines. >> ... >>> [sssd] [confdb_expand_app_domains] (0x0010): No domains configured,