14 Replies Latest reply: Mar 1, 2012 7:55 PM by Soret SO RSS

    STK 6140 Array HDD

    Soret SO
      Dear All,

      I had a very crazy problem with the Sun StorageTek 6140 Arry of it hard disk. When hard disk show amber and blue led, we replaced it with new hdd (Ready Test, it good) but that new is cannot work. The crazy problem is when we put old hdd (Fail Hdd) it will work fine then we keep monitoring it then one week latter other hdd will come with the same problem. It already happened 4 to 5 times. :(...

      Did anyone have some idea about this problem?

      Thanks you in advance.

      Regards,
      Soret.
        • 1. Re: STK 6140 Array HDD
          Nik
          Hi.
          IMHO you have two undepended state:
          1. Old HDD FAIL. But this problem is not persistent and cause fail after some time.
          Realy this defect stable ( you reproduce it 4 or 5 times).

          2. You have one New Disk. But this disk not work at 6140. For trubleshuting this problem, need see logs for understanding why this disk
          detected as fault.


          Regards.
          • 2. Re: STK 6140 Array HDD
            Soret SO
            Hi,

            Appreciate it for your help.

            During my log checked, I have mention, the problem came from the firmware. Does it can be that? Because that storage is not in the baseline firmware. Do you have any idea about this?

            Thanks you,

            Edited by: Soret SO on Feb 28, 2012 11:01 AM
            • 3. Re: STK 6140 Array HDD
              Nik
              Hi.

              Before do anything need read logs and understand what happens.
              Why new disk not detected.
              Why old disk go to offline.

              Bad FW it's only one possible reason from many other.
              Possible eoy need install latest version of CAM and update FW to current relelase, but in any case you need understand what happens.

              Regards.
              • 4. Re: STK 6140 Array HDD
                Soret SO
                Dear Nik,

                Thanks you so much for advices us.

                ***Here is some logs:

                Date/Time: Mon Feb 27 23:43:11 ICT 2012
                Sequence number: 28963
                Event type: 1012
                Event category: Error
                Priority: Informational
                Description: Destination driver event
                Event specific codes: 204/15/1
                Component type: Drive
                Component location: Tray.00.Drive.01
                Logged by: Controller in slot A


                Date/Time: Mon Feb 27 23:43:11 ICT 2012
                Sequence number: 28964
                Event type: 201E
                Event category: Notification
                Priority: Informational
                Description: VDD repair started
                Event specific codes: 0/0/0
                Component type: Controller
                Component location: Controller in slot A
                Logged by: Controller in slot A


                Date/Time: Mon Feb 27 23:43:11 ICT 2012
                Sequence number: 28965
                Event type: 2014
                Event category: Notification
                Priority: Informational
                Description: VDD logged an error
                Event specific codes: 0/0/0
                Component type: Controller
                Component location: Controller in slot A
                Logged by: Controller in slot A


                Date/Time: Mon Feb 27 23:43:12 ICT 2012
                Sequence number: 28966
                Event type: 201F
                Event category: Notification
                Priority: Informational
                Description: VDD repair completed
                Event specific codes: 0/0/0
                Component type: Controller
                Component location: Controller in slot A
                Logged by: Controller in slot A


                Date/Time: Tue Feb 28 00:08:35 ICT 2012
                Sequence number: 28967
                Event type: 100A
                Event category: Error
                Priority: Informational
                Description: Drive returned CHECK CONDITION
                Event specific codes: 4/22/47
                Component type: Drive
                Component location: Tray.00.Drive.01
                Logged by: Controller in slot A


                Date/Time: Tue Feb 28 00:08:35 ICT 2012
                Sequence number: 28968
                Event type: 1012
                Event category: Error
                Priority: Informational
                Description: Destination driver event
                Event specific codes: 204/15/1
                Component type: Drive
                Component location: Tray.00.Drive.01
                Logged by: Controller in slot A


                Date/Time: Tue Feb 28 00:36:27 ICT 2012
                Sequence number: 28969
                Event type: 100A
                Event category: Error
                Priority: Informational
                Description: Drive returned CHECK CONDITION
                Event specific codes: 4/22/47
                Component type: Drive
                Component location: Tray.00.Drive.01
                Logged by: Controller in slot A


                Date/Time: Tue Feb 28 00:36:27 ICT 2012
                Sequence number: 28970
                Event type: 1012
                Event category: Error
                Priority: Informational
                Description: Destination driver event
                Event specific codes: 204/15/1
                Component type: Drive
                Component location: Tray.00.Drive.01
                Logged by: Controller in slot A


                Date/Time: Tue Feb 28 00:58:54 ICT 2012
                Sequence number: 28971
                Event type: 100A
                Event category: Error
                Priority: Informational
                Description: Drive returned CHECK CONDITION
                Event specific codes: 6/0/0
                Component type: Drive
                Component location: Tray.85.Drive.11
                Logged by: Controller in slot A

                ***Alarm

                Alarm list for device SUN.54065460150.0748AWF0FF

                Alarm ID : alarm5
                Description: ST6140 is at revision "N399X-619843-004" baseline version is "N399X-660843-003"
                Tray.85.Controller.B is at revision "06.19.25.16" baseline version is "06.60.22.10"
                Tray.85.Controller.A is at revision "06.19.25.16" baseline version is "06.60.22.10"
                Tray.00.IOM.B is at revision "9887" baseline version is "98D3"
                Tray.00.IOM.A is at revision "9887" baseline version is "98D3"
                Tray.00.Drive.02 is at revision "3090" baseline version is "3192"
                Tray.00.Drive.03 is at revision "0691" baseline version is "3192"
                Tray.00.Drive.05 is at revision "3092" baseline version is "3192"
                Tray.00.Drive.01 is at revision "0691" baseline version is "3192"
                Tray.00.Drive.06 is at revision "0691" baseline version is "3192"
                Tray.00.Drive.07 is at revision "0691" baseline version is "3192"
                Tray.00.Drive.08 is at revision "3092" baseline version is "3192"
                Tray.00.Drive.09 is at revision "0691" baseline version is "3192"
                Tray.85.Drive.09 is at revision "0691" baseline version is "3192"
                Tray.00.Drive.13 is at revision "0691" baseline version is "3192"
                Tray.00.Drive.14 is at revision "0691" baseline version is "3192"
                Tray.00.Drive.15 is at revision "0691" baseline version is "3192"
                Tray.00.Drive.16 is at revision "0691" baseline version is "3192"
                Tray.00.Drive.11 is at revision "0691" baseline version is "3192"
                Tray.85.Drive.14 is at revision "0691" baseline version is "3192"
                Tray.85.Drive.15 is at revision "0691" baseline version is "3192"
                Tray.85.Drive.10 is at revision "0691" baseline version is "3192"
                Tray.85.Drive.11 is at revision "0691" baseline version is "3192"
                Tray.85.Drive.12 is at revision "0691" baseline version is "3192"
                Tray.85.Drive.13 is at revision "0691" baseline version is "3192"

                Severity : Major
                Element : SUN.54065460150.0748AWF0FF
                GridCode : 57.75.42
                Date : 2012-02-13 14:16:35

                Alarm ID : alarm7
                Description: The following volume(s) is/are not managed by their preferred controller: DB3LabVol4 DB1LabVol2
                Severity : Major
                Element : 600A0B800029E086000003C547C8F0F3
                GridCode : 57.66.1010
                Date : 2012-02-13 14:16:35

                Alarm ID : alarm9
                Description: Battery Tray.85.Battery.B has failed.
                Severity : Critical
                Element : t85bat2
                GridCode : 57.66.1006
                Date : 2012-02-13 14:16:35

                Alarm ID : alarm16
                Description: A hot spare is in use. The affected virtual disk is vdisk.1, failed drive(s) Tray.00.Drive.04, spare(s) used Tray.85.Drive.16, the affected volume(s) DB1LabVol2
                Severity : Major
                Element : t0drive4
                GridCode : 57.66.1021
                Date : 2012-02-28 09:44:16

                Alarm ID : alarm17
                Description: Drive Tray.00.Drive.04 is bypassed, reason not specified by the array.
                Severity : Critical
                Element : t0drive4
                GridCode : 57.66.1064
                Date : 2012-02-28 09:44:1

                May you share us some solution about this?

                Regards,

                Edited by: Soret SO on Feb 28, 2012 2:29 PM
                • 5. Re: STK 6140 Array HDD
                  Nik
                  Hi.
                  1. Replace Drive Tray.00.Drive.04
                  Wait for all volumes repaired.
                  2. Replace Tray.85.Battery.B
                  3. Monitor Tray.00.Drive.01

                  But you not say about what disk you start this post.


                  Regards.
                  • 6. Re: STK 6140 Array HDD
                    Soret SO
                    Hi Nik,

                    We already replaced it with the new hard disk (The same Part Number) but still the same problem like I wrote before. But we see that the volume is not map to the pool, can we click the Reset Settings on that volume? If we click it, does it have any impact?

                    Appreciated for your help.

                    Regards,
                    • 7. Re: STK 6140 Array HDD
                      Nik
                      Hi.
                      > We already replaced it with the new hard disk
                      Please read all your post. Did You say what disk you replaced ?
                      In case you say about disk 04. If this disk was used in array with 7.x FW of controller, this will not work on 6.x FW.
                      You can try clear this disk by connect to server and use dd or format.
                      • 8. Re: STK 6140 Array HDD
                        Soret SO
                        Hi Nik,

                        Really appreciated for your help us.

                        Now I understand about it. One more thing during we click on the volume it will show us below message:

                        "*The settings of this volume do not conform to its pool's profile.*
                        *Click the Reset Settings button to attempt to match the volume settings with the profile. If the Reset Settings operation fails again, move the volume to a different pool that matches its settings.*"

                        May you shared us some idea about this?

                        Thanks you in advance.

                        Regards,
                        • 9. Re: STK 6140 Array HDD
                          Nik
                          I don't know history of your array. So don't know why this problem occured.

                          You don't show settings of this volume and settings of profie for this volume.

                          In case you not need this volume - just remove it.
                          Also you can try do recommed action.
                          • 10. Re: STK 6140 Array HDD
                            Soret SO
                            Hi,

                            Thanks you so much Nik.

                            If I want to update of the Array Controller, may you tell me what can impaction during this process?

                            Thanks you in advance.

                            Best Regards,
                            • 11. Re: STK 6140 Array HDD
                              Nik
                              Hi.

                              Best way to study - read Docs. It's open and free.

                              Wha mean
                              I want to update of the Array Controller
                              ?

                              Upgrade FW to Baseline - in you case, require downtime, becouse disk FW sould be upgraded to and it's require stop OI.
                              Upgrade FW 6.x to 7.x - Special procedure, require downtime.

                              Hardware upgrade ?
                              • 12. Re: STK 6140 Array HDD
                                Soret SO
                                Hi,

                                Oh! Yes, I want to upgrade the Array Controller firmware from 6.x to 7.x.

                                When we complete upgrade the firmware, does it effect to any applications that installed on server? I mean, when the storage is up the application can start whatever Array Controller and HDD firmware is upgraded?

                                Thanks you for you value time to help us.

                                Best Regards,
                                • 13. Re: STK 6140 Array HDD
                                  Nik
                                  Hi.
                                  Answer on all you questions:
                                  http://docs.oracle.com/cd/E19381-01/index.htmlhttp://docs.oracle.com/cd/E19381-01/index.html

                                  Upgrade Fw 6.x to 7.x
                                  http://docs.oracle.com/cd/E19381-01/820-7197-12/820-7197-12.pdf

                                  In normal condition you not loosen data after FW upgrade, but backup strong recommended in any case.

                                  Regards
                                  • 14. Re: STK 6140 Array HDD
                                    Soret SO
                                    Hi Nik,

                                    Appreciated and Thanks you so much for your help.

                                    Have a Good Day!!!

                                    Regards,