7 Replies Latest reply on Dec 12, 2017 9:33 AM by Intel Corporation

    P3x00 with Storage Spaces Direct

    AFurtenbacher

      Hi,

      we got a 4 node cluster running Storage Spaces direct, using P3700 NVMes as caching devices. There seems to be a problem with this combination:

      https://support.microsoft.com/en-gb/help/4052341/slow-performance-or-lost-communication-io-error-detached-or-no-redunda

      This can lead up to BSOD, which you can imagine is horrible in a production Cluster.

      I could not find any information from Intel on this topic. Can anyone help me out with this? I don't know if this is a Microsoft problem, or if a new driver/firmware could help out.

      I have also posted this in Microsoft TechNet.

      Any help is highly apreciated!

      Best regards,

      Andreas

        • 1. Re: P3x00 with Storage Spaces Direct
          Intel Corporation
          This message was posted on behalf of Intel Corporation

          Hello AFurtenbacher,

          Thanks for being part of Intel® communities.

          Reading the article you shared, the problem seems to be Windows* Server 2016 Datacenter related.

          I checked the latest firmware releases change notes, but there's was no mention of fixes/updates regarding Storage Spaces Direct (S2D). You can check these notes at the Release Notes for Intel® SSD Data Center Tool (found at the bottom of the download page) under "Product Firmware Revision History":

          Downloads for Intel® SSD Data Center Tool

          Please let us know if there''s anything else we can help you with.

          Best regards,
          Eugenio F.

          • 2. Re: P3x00 with Storage Spaces Direct
            AFurtenbacher

            Hi,

            in the Release Notes of the latest version, there is no hint on any fix pointing in our direction.

            Pointing at Microsoft, being honest, is a bit too simple, because the problem only occurs on Intel P3x00 discs. All other vendors cause no problems. I can't imagine, that Microsoft handles Intel NVMes differently than those of other vendors. So after all, I still think a change in the driver or the firmware could make a big difference.

            Best regards,

            Andreas

            p.s. I am not sure if the problem is connected to S2D. The NVMes in our area simply only get used now that S2D is in available, because now we can use the internal drives of the server and don't Need SAS disks in SANs anymore. Before this, I didn't know anyone, who used those disks in servers, because we couldn't build an HA solution with them.

            • 3. Re: P3x00 with Storage Spaces Direct
              Intel Corporation
              This message was posted on behalf of Intel Corporation

              Hello AFurtenbacher,

              Thanks for your observations.

              Our engineers are already working with Microsoft* to try and find a solution for this issue. For now, we recommend keeping the drives firmware and your operating system up to date in addition to applying the changes described in the Microsoft* article you shared.

              Best regards,
              Eugenio F.

              • 4. Re: P3x00 with Storage Spaces Direct
                AFurtenbacher

                Hi Eugenio,

                 

                thank you for the information. Is there any chance for an estimation when whis possibly will be solved? As I said: people are loosing their production clusters, so it is quite urgent.

                 

                Concerning the firmware I got one more question: The Intel SSD Tool shows, that my disks are on firmware 8DV1FJP5. As far as I have seen, 8DV1FJP9 ist already available, so I tried to update my drives. The Problem I got was, that the ISDCT always tells me, that the drives already have the latest version coming with the software. I have tried this with ISDCT 3.0.3 and 3.0.9 and manually downloades the firmware and put it into the "FirmwareModules" folder.

                How do I flash the disks?

                 

                Best regards,

                Andreas

                • 5. Re: P3x00 with Storage Spaces Direct
                  Intel Corporation
                  This message was posted on behalf of Intel Corporation

                  Hi AFurtenbacher,

                  So far, there's not an ETA for a solution regarding this issue from our side.

                  Regarding the firmware update, the latest release for the retail version of Intel® SSD DC P3700 Series is 8DV101H0.

                  A different firmware revision is usually an indicator that the drive is an OEM (Original Equipment Manufacturer) version. Judging by the "FJP5" and "FJP9" on the firmware, it's possible these were manufactured by Intel for Fujitsu*.

                  Firmware updates for OEM drives are provided by the OEM, in this case, you would have to contact them (Computer Manufacturer Support) to obtain firmware updates for this drive. ISDCT (Intel® SSD Data Center Tool) and other Intel tools are not able to update firmware on OEM drives.

                  Best regards,
                  Eugenio F.

                  • 6. Re: P3x00 with Storage Spaces Direct
                    AFurtenbacher

                    Dear Eugenio,

                     

                    we are thinking about changing from the P3600 to the P4600. Can you confirm, that the problem does not exist on the P4x00 series?

                     

                    Thank you and best regards,

                    Andreas

                    • 7. Re: P3x00 with Storage Spaces Direct
                      Intel Corporation
                      This message was posted on behalf of Intel Corporation

                      Hello AFurtenbacher,

                      Thanks for your reply.

                      The issue seems to affect the Intel® SSD DC P3500, P3600 and P3700 only.

                      We haven't  received reports regarding the Intel® SSD DC P4500 or P4600 Series, probably because these models have different structures (3D NAND based).

                      Regards,
                      Eugenio F.