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 somebody know what could be the problem?
I talked to the Intel support and they said the problem is that Centos is not supported OS ... only RHEL 7. But if not supported should not work on the LSI controlled neither.
Thanks,
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@gmail.com:
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 somebody know what could be the problem?
I talked to the Intel support and they said the problem is that Centos is not supported OS ... only RHEL 7. But if not supported should not work on the LSI controlled neither.
Thanks,
-- Levi _______________________________________________ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
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?
Of course they detected by kernel. They work very well, just this tool does not recognize them.
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@gmail.com mailto:blevi.linux@gmail.com>:
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 somebody know what could be the problem? I talked to the Intel support and they said the problem is that Centos is not supported OS ... only RHEL 7. But if not supported should not work on the LSI controlled neither. Thanks, -- Levi _______________________________________________ CentOS mailing list CentOS@centos.org <mailto:CentOS@centos.org> https://lists.centos.org/mailman/listinfo/centos
2015-11-18 16:48 GMT+02:00 Birta Levente blevi.linux@gmail.com:
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?
Of course they detected by kernel. They work very well, just this tool does not recognize them.
Well. You are using it on non supported configuration? You should try it with official RHEL, it might work or not. If not, then open support ticket.
-- Eero
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 the motherboard, but through the LSI raid controller is working.
Does somebody know what could be the problem?
I talked to the Intel support and they said the problem is that Centos is not supported OS ... only RHEL 7. But if not supported should not work on the LSI controlled neither.
Perhaps the tool looks for the string RHEL. My recollection is that when IBM PC's were fairly new, IBM used that trick with some of its software. To work around that, some open source developers used the string "not IBM". I think this was pre-internet, so google might not work.
If it's worth the effort, you might make another "CentOS" distribution, but call it "not RHEL".
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 systems have 2. Similarly modify /etc/issue
Another tip that has proven successful: run the vendor tool under strace. Sometimes you can get an idea of what it's trying to do and why it's failing. This is exactly what we did to determine why a vendor tool wouldn't work on CentOS. We had modified /etc/redhat-release (as in (1) above), but forgot about /etc/issue. Strace showed the program existing immediately after an open() call to /etc/issue.
Good luck!
On Wed, Nov 18, 2015 at 9:24 AM, Michael Hennebry hennebry@web.cs.ndsu.nodak.edu wrote:
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 the motherboard, but through the LSI raid controller is working.
Does somebody know what could be the problem?
I talked to the Intel support and they said the problem is that Centos is not supported OS ... only RHEL 7. But if not supported should not work on the LSI controlled neither.
Perhaps the tool looks for the string RHEL. My recollection is that when IBM PC's were fairly new, IBM used that trick with some of its software. To work around that, some open source developers used the string "not IBM". I think this was pre-internet, so google might not work.
If it's worth the effort, you might make another "CentOS" distribution, but call it "not RHEL".
-- Michael hennebry@web.cs.ndsu.NoDak.edu "Sorry but your password must contain an uppercase letter, a number, a haiku, a gang sign, a heiroglyph, and the blood of a virgin." -- someeecards _______________________________________________ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
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@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 "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:
- Modify /etc/redhat-release to say RedHat Enterprise Linux or
whatever the actual RHEL systems have 2. Similarly modify /etc/issue
Another tip that has proven successful: run the vendor tool under strace. Sometimes you can get an idea of what it's trying to do and why it's failing. This is exactly what we did to determine why a vendor tool wouldn't work on CentOS. We had modified /etc/redhat-release (as in (1) above), but forgot about /etc/issue. Strace showed the program existing immediately after an open() call to /etc/issue.
Good luck!
On Wed, Nov 18, 2015 at 9:24 AM, Michael Hennebry hennebry@web.cs.ndsu.nodak.edu wrote:
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
the motherboard, but through the LSI raid controller is working.
Does somebody know what could be the problem?
I talked to the Intel support and they said the problem is that Centos
is
not supported OS ... only RHEL 7. But if not supported should not work on the LSI controlled neither.
Perhaps the tool looks for the string RHEL. My recollection is that when IBM PC's were fairly new, IBM used that trick with some of its software. To work around that, some open source developers used the string "not
IBM".
I think this was pre-internet, so google might not work.
If it's worth the effort, you might make another "CentOS" distribution, but call it "not RHEL".
-- Michael hennebry@web.cs.ndsu.NoDak.edu "Sorry but your password must contain an uppercase letter, a number, a haiku, a gang sign, a heiroglyph, and the blood of a virgin." --
someeecards
CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
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 is rebuilt on RHEL in the Red Hat isolated build system .. and CentOS Linux is built CentOS in our isolated build system.
Red Hat does not always release everything in their build system (they might do 2 or 3 versions before they release something). We only have things they released (and we built) in our build system.
That means almost every single compiled binary file is 'not exactly' the same (on a bit for bit basis) when compared between CentOS Linux and RHEL.
Thanks, Johnny Hughes
-- Eero
2015-11-18 17:42 GMT+02:00 Matt Garman matthew.garman@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 "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:
- Modify /etc/redhat-release to say RedHat Enterprise Linux or
whatever the actual RHEL systems have 2. Similarly modify /etc/issue
Another tip that has proven successful: run the vendor tool under strace. Sometimes you can get an idea of what it's trying to do and why it's failing. This is exactly what we did to determine why a vendor tool wouldn't work on CentOS. We had modified /etc/redhat-release (as in (1) above), but forgot about /etc/issue. Strace showed the program existing immediately after an open() call to /etc/issue.
Good luck!
On Wed, Nov 18, 2015 at 9:24 AM, Michael Hennebry hennebry@web.cs.ndsu.nodak.edu wrote:
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
the motherboard, but through the LSI raid controller is working.
Does somebody know what could be the problem?
I talked to the Intel support and they said the problem is that Centos
is
not supported OS ... only RHEL 7. But if not supported should not work on the LSI controlled neither.
Perhaps the tool looks for the string RHEL. My recollection is that when IBM PC's were fairly new, IBM used that trick with some of its software. To work around that, some open source developers used the string "not
IBM".
I think this was pre-internet, so google might not work.
If it's worth the effort, you might make another "CentOS" distribution, but call it "not RHEL".
-- Michael hennebry@web.cs.ndsu.NoDak.edu "Sorry but your password must contain an uppercase letter, a number, a haiku, a gang sign, a heiroglyph, and the blood of a virgin." --
someeecards
CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
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 remove RH trademarks and take out RHN update pieces).
But RHEL source code is rebuilt on RHEL in the Red Hat isolated build system .. and CentOS Linux is built CentOS in our isolated build system.
Red Hat does not always release everything in their build system (they might do 2 or 3 versions before they release something). We only have things they released (and we built) in our build system.
That means almost every single compiled binary file is 'not exactly' the same (on a bit for bit basis) when compared between CentOS Linux and RHEL.
I tried today morning on RHEL too ... The ISDCT tool does not work on supported OS neither
Tanks,
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 vendor's support staff.
So, again, check your BIOS settings and make sure the SATA ports are in the standard AHCI mode.
It is in AHCI, never was changed
On 19:26, Thu, Nov 19, 2015 Gordon Messmer gordon.messmer@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 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 vendor's support staff.
So, again, check your BIOS settings and make sure the SATA ports are in the standard AHCI mode. _______________________________________________ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
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@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 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 vendor's support staff.
So, again, check your BIOS settings and make sure the SATA ports are in the standard AHCI mode. _______________________________________________ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
On 19/11/2015 20:46, Alice Wonder wrote:
I assume you are using one of the boards described here?
http://www.intel.com/support/services/smartconnect/sb/CS-033108.htm
Nope
This is my server: http://www.supermicro.com/products/system/1u/1028/sys-1028r-mctr.cfm
and this is my board: http://www.supermicro.com/products/motherboard/Xeon/C600/X10DRL-CT.cfm
On 11/19/2015 10:43 AM, Birta Levente wrote:
It is in AHCI, never was changed
You reported that the tool didn't work in RHEL, either. If you have an install on a supported OS, I'd say that it's time to go back to Intel with the support request. If you arrive at a resolution, I'd be curious to hear what it is.
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 remove RH trademarks and take out RHN update pieces).
But RHEL source code is rebuilt on RHEL in the Red Hat isolated build system .. and CentOS Linux is built CentOS in our isolated build system.
Red Hat does not always release everything in their build system (they might do 2 or 3 versions before they release something). We only have things they released (and we built) in our build system.
That means almost every single compiled binary file is 'not exactly' the same (on a bit for bit basis) when compared between CentOS Linux and RHEL.
I just made a test with Centos 6.7 up to date and the tool is working. What could be make the difference? Of course kernel and many newer packages, but ...
Thanks,
On 11/18/2015 06:25 AM, Birta Levente wrote:
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.
Check your BIOS settings for non-standard modes on the SATA ports. Maybe they're in legacy (IDE) or an incompatible RAID mode. Intel's docs don't note specific requirements, but I'd expect ports in AHCI mode to work correctly.
-
Alice Wonder -
Birta Levente -
Eero Volotinen -
Gordon Messmer -
Johnny Hughes -
Levente Birta
-
Matt Garman -
Michael Hennebry