6 Replies Latest reply: Jul 29, 2010 1:45 AM by abrante RSS

    DiskSuite Fail in SunOS 5.9

    807567
      Hello,

      I get this error when I run check_disksuite.sh.

      "Mirror d3 is in a wrong state / Submirror d13 is in a wrong state."

      SunOS 5.9

      What does this message mean?
      How can I fix it?

      Thanks
        • 1. Re: DiskSuite Fail in SunOS 5.9
          Robert Cohen
          Whats metastat show
          • 2. Re: DiskSuite Fail in SunOS 5.9
            807567
            the metastat command show this:

            root@... # metastat
            d3: Mirror
            Submirror 0: d13
            State: Needs maintenance
            Submirror 1: d23
            State: Okay
            Pass: 1
            Read option: roundrobin (default)
            Write option: parallel (default)
            Size: 71689920 blocks (34 GB)

            d13: Submirror of d3
            State: Needs maintenance
            Invoke: metareplace d3 c1t0d0s3 <new device>
            Size: 71689920 blocks (34 GB)
            Stripe 0:
            Device Start Block Dbase State Reloc Hot Spare
            c1t0d0s3 0 No Maintenance Yes


            d23: Submirror of d3
            State: Okay
            Size: 71689920 blocks (34 GB)
            Stripe 0:
            Device Start Block Dbase State Reloc Hot Spare
            c1t1d0s3 0 No Okay Yes


            d1: Mirror
            Submirror 0: d11
            State: Okay
            Submirror 1: d21
            State: Okay
            Pass: 1
            Read option: roundrobin (default)
            Write option: parallel (default)
            Size: 20484288 blocks (9.8 GB)

            d11: Submirror of d1
            State: Okay
            Size: 20484288 blocks (9.8 GB)
            Stripe 0:
            Device Start Block Dbase State Reloc Hot Spare
            c1t0d0s1 0 No Okay Yes


            d21: Submirror of d1
            State: Okay
            Size: 20484288 blocks (9.8 GB)
            Stripe 0:
            Device Start Block Dbase State Reloc Hot Spare
            c1t1d0s1 0 No Okay Yes


            d0: Mirror
            Submirror 0: d10
            State: Okay
            Submirror 1: d20
            State: Okay
            Pass: 1
            Read option: roundrobin (default)
            Write option: parallel (default)
            Size: 50798592 blocks (24 GB)

            d10: Submirror of d0
            State: Okay
            Size: 50798592 blocks (24 GB)
            Stripe 0:
            Device Start Block Dbase State Reloc Hot Spare
            c1t0d0s0 0 No Okay Yes


            d20: Submirror of d0
            State: Okay
            Size: 50798592 blocks (24 GB)
            Stripe 0:
            Device Start Block Dbase State Reloc Hot Spare
            c1t1d0s0 0 No Okay Yes


            Device Relocation Information:
            Device Reloc Device ID
            c1t1d0 Yes id1,sd@SFUJITSU_MAT3073N_SUN72G_000531B097BN____AAN0P58097BN
            c1t0d0 Yes id1,sd@SFUJITSU_MAT3073N_SUN72G_000531B099BS____AAN0P58099BS
            root@... #
            • 3. Re: DiskSuite Fail in SunOS 5.9
              wrobbins2
              check disk c1t0d0 for errors, replace if bad, if it looks good then run this command:
              metareplace -e d3 c1t0d0s3
              • 4. Re: DiskSuite Fail in SunOS 5.9
                807567
                Sorry but my Solaris level is very bad. What command can I use for check the disk?
                • 5. Re: DiskSuite Fail in SunOS 5.9
                  wrobbins2
                  iostat -en | grep c1t0d0
                  will show soft, hard, transport, total errors since the last reboot

                  you could also try
                  format
                  enter the appropriate number, then
                  analyze
                  read (doesn't harm SunOS)
                  • 6. Re: DiskSuite Fail in SunOS 5.9
                    abrante
                    You can also check the /var/adm/messages* file for errors related to the disk.

                    You can also run 'metastat' and see if there are any other failed metadevices belonging to the same disk, if multiple metadevices have failed you probably have a faulty harddrive.

                    Another option is to simply run the metareplace command stated above; if the device fails again within a short period of time its probably time to change the harddrive..

                    .7/M.