5 Replies Latest reply: Aug 23, 2010 3:40 PM by wrobbins2 RSS

    V440 raidctl did not remove mirror

    807559
      Hi there,

      I have a problem with SunFire v440 servers and HW raid. Today I removed HW raid with "raidctl -d" command. It gives no error and removal completed successfully. raidctl shows no mirrors. However "format" command does not see the disk and "iostat -E" shows the disks as LSI which means It is owned by HW mirror. I tried all combinations of "cfgadm" and "devfsadm" but did not work. I do not want to reboot the system before solving this problem because facing of an unbootable system. Is it possible to remove HW mirror without "raidctl"? Any ideas?
        • 1. Re: V440 raidctl did not remove mirror
          807559
          v445 Admin guide document says that we cannot fix it, it is a service issue...
          Anyone did this before?
          • 2. Re: V440 raidctl did not remove mirror
            807559
            Here is the solution I found on the mailing lists:
            Crist,

            This has worked for me before on the V245:

            You may want to remove all the hard drives except the troubled one
            first.

            ok setenv fcode-debug? true
            fcode-debug? = true
            ok setenv auto-boot? false
            auto-boot? = false
            ok reset-all

            ok show-disks
            a) /pci at 1e,600000/pci at 0/pci at a/pci at 0/pci at 8/scsi at 1/disk
            b) /pci at 1e,600000/pci at 0/pci at 1/pci at 0/ide at 1f/cdrom
            c) /pci at 1e,600000/pci at 0/pci at 1/pci at 0/ide at 1f/disk
            q) NO SELECTION
            Enter Selection, q to quit: q
            ok select /pci at 1e,600000/pci at 0/pci at a/pci at 0/pci at 8/scsi at 1

            ok show-volumes
            Volume 0 Target 0 Type IM (Integrated Mirroring)
            Optimal Enabled
            2 Members 143112591 Blocks, 73 GB
            Disk 1
            Primary Online
            Target 4 FUJITSU MAY2073RCSUN72G 0401
            Disk 0
            Secondary Online
            Target 1 FUJITSU MAY2073RCSUN72G 0401

            ok 0 delete-volume
            The volume and its data will be deleted
            Are you sure (yes/no)? [no] yes
            Volume 0 has been deleted

            ok show-volumes
            No volumes to show

            ok setenv auto-boot? true
            auto-boot? = true
            ok setenv fcode-debug? false
            fcode-debug? = false

            You can now boot the system, run devfsadm to see the fixed hard
            drive,
            and run the format utility to detect the type and label the drive.

            Note that when you run the show-volumes command one of the physical
            disks in the array will be shown as Missing.
            • 3. Re: V440 raidctl did not remove mirror
              807559
              Were you getting any errors or did you just want to break all mirrors?
              I have a few V440s that are mirrored and have broken them many times with no problems.
              • 4. Re: V440 raidctl did not remove mirror
                807559
                Actually I have one Sun Fire T5140 and on os side it shows only one disk.. and i want to break the mirror .i.e. hard mirror using raidctl -d.

                Is it possible to break the hard mirror using the steps given, without loosing the data on main root disk?

                If any process is there then please let me know and i want to try it.

                Thanks
                Andy
                • 5. Re: V440 raidctl did not remove mirror
                  wrobbins2
                  from the man page:
                  "-d [-f] volume

                  Delete the RAID volume specified as volume. The volume is specified in canonical form (for example, c0t0d0).

                  When a volume is deleted, all data is lost. Therefore, unless the -f option is specified, raidctl prompts the user for confirmation before deleting the volume.

                  When a RAID 1 volume is deleted from a LSI1020, LSI1030, SAS1064, or SAS1068 HBA, the primary and secondary disks are “split”. If the volume was in SYNCING state, the primary will contain the data, and the secondary will not. If the volume state was OPTIMAL, both disks will contain a complete image of the data."