7 Replies Latest reply: Jun 28, 2012 5:57 AM by user13643597 RSS

    raidctl  "panic[cpu0]/thread=180e000: vfs_mountroot: cannot remount root"

    user13643597
      Hi

      In one machine(T200), I was trying to break the raid

      before
      #format
      AVAILABLE DISK SELECTIONS:
      0. c0t0d0 <LSILOGIC-LogicalVolume-3000 cyl 65533 alt 2 hd 16 sec 136>
      /pci@780/pci@0/pci@9/scsi@0/sd@0,0

      #raidctl
      Controller: 0
      Volume:c0t0d0
      Disk: 0.0.0
      Disk: 0.1.0


      #raidctl -l c0t0d0
      Volume Size Stripe Status Cache RAID
      Sub Size Level
      Disk
      ----------------------------------------------------------------
      c0t0d0 247.1M N/A OPTIMAL OFF RAID1
      0.0.0 247.1M GOOD
      0.1.0 247.1M GOOD



      I do:

      #raidctl -d c0t0d0


      #format
      Searching for disks...done
      No disks found!

      reboot but on boot "panic[cpu0]/thread=180e000: vfs_mountroot: cannot remount root"

      boot on failsafe and when I do:

      #raidctl
      Controller: 0
      Disk: 0.0.0
      Disk: 0.1.0

      #format
      AVAILABLE DISK SELECTIONS:
      0. c0t0d0 <LSILOGIC-LogicalVolume-3000 cyl 65533 alt 2 hd 16 sec 136>
      /pci@780/pci@0/pci@9/scsi@0/sd@0,0
      1. c0t1d0 <LSILOGIC-LogicalVolume-3000 cyl 65533 alt 2 hd 16 sec 136>
      /pci@780/pci@0/pci@9/scsi@0/sd@1,0



      Can someone help me
        • 1. Re: raidctl  "panic[cpu0]/thread=180e000: vfs_mountroot: cannot remount root"
          bobthesungeek76036
          Yea you have successfully confused the heck out of Veritas. You now have two visible copies of your rootdg which probably doesn't make Veritas happy. You need to either pull the drive you un-mirrored or boot off DVD/CD and erase/format the other drive so it doesn't have a rootdg on it anymore...
          • 2. Re: raidctl  "panic[cpu0]/thread=180e000: vfs_mountroot: cannot remount root"
            user13643597
            its SVM:

            #metastat
            d40: Mirror
            Submirror 0: d41
            State: Okay
            Pass: 1
            Read option: roundrobin (default)
            Write option: parallel (default)
            Size: 4195328 blocks (2.0 GB)

            d41: Submirror of d40
            State: Okay
            Size: 4195328 blocks (2.0 GB)
            Stripe 0:
            Device Start Block Dbase State Reloc Hot Spare
            c0t0d0s5 0 No Okay Yes


            d30: Mirror
            Submirror 0: d31
            State: Okay
            Pass: 1
            Read option: roundrobin (default)
            Write option: parallel (default)
            Size: 16779136 blocks (8.0 GB)

            d31: Submirror of d30
            State: Okay
            Size: 16779136 blocks (8.0 GB)
            Stripe 0:
            Device Start Block Dbase State Reloc Hot Spare
            c0t0d0s3 0 No Okay Yes


            d20: Mirror
            Submirror 0: d21
            State: Okay
            Pass: 1
            Read option: roundrobin (default)
            Write option: parallel (default)
            Size: 33538688 blocks (15 GB)

            d21: Submirror of d20
            State: Okay
            Size: 33538688 blocks (15 GB)
            Stripe 0:
            Device Start Block Dbase State Reloc Hot Spare
            c0t0d0s1 0 No Okay Yes


            d10: Mirror
            Submirror 0: d11
            State: Okay
            Pass: 1
            Read option: roundrobin (default)
            Write option: parallel (default)
            Size: 16779136 blocks (8.0 GB)

            d11: Submirror of d10
            State: Okay
            Size: 16779136 blocks (8.0 GB)
            Stripe 0:
            Device Start Block Dbase State Reloc Hot Spare
            c0t0d0s0 0 No Okay Yes


            d64: Soft Partition
            Device: c0t0d0s6
            State: Okay
            Size: 5529600 blocks (2.6 GB)
            Device Start Block Dbase Reloc
            c0t0d0s6 0 No Yes

            Extent Start Block Block count
            0 65536009 5529600

            d63: Soft Partition
            Device: c0t0d0s6
            State: Okay
            Size: 8192000 blocks (3.9 GB)
            Device Start Block Dbase Reloc
            c0t0d0s6 0 No Yes

            Extent Start Block Block count
            0 57344008 8192000

            d62: Soft Partition
            Device: c0t0d0s6
            State: Okay
            Size: 8192000 blocks (3.9 GB)
            Device Start Block Dbase Reloc
            c0t0d0s6 0 No Yes

            Extent Start Block Block count
            0 49152007 8192000

            d51: Soft Partition
            Device: c0t0d0s6
            State: Okay
            Size: 8192000 blocks (3.9 GB)
            Device Start Block Dbase Reloc
            c0t0d0s6 0 No Yes

            Extent Start Block Block count
            0 8192002 8192000

            d61: Soft Partition
            Device: c0t0d0s6
            State: Okay
            Size: 8192000 blocks (3.9 GB)
            Device Start Block Dbase Reloc
            c0t0d0s6 0 No Yes

            Extent Start Block Block count
            0 40960006 8192000

            d60: Soft Partition
            Device: c0t0d0s6
            State: Okay
            Size: 8192000 blocks (3.9 GB)
            Device Start Block Dbase Reloc
            c0t0d0s6 0 No Yes

            Extent Start Block Block count
            0 32768005 8192000

            d53: Soft Partition
            Device: c0t0d0s6
            State: Okay
            Size: 8192000 blocks (3.9 GB)
            Device Start Block Dbase Reloc
            c0t0d0s6 0 No Yes

            Extent Start Block Block count
            0 24576004 8192000

            d52: Soft Partition
            Device: c0t0d0s6
            State: Okay
            Size: 8192000 blocks (3.9 GB)
            Device Start Block Dbase Reloc
            c0t0d0s6 0 No Yes

            Extent Start Block Block count
            0 16384003 8192000

            d50: Soft Partition
            Device: c0t0d0s6
            State: Okay
            Size: 8192000 blocks (3.9 GB)
            Device Start Block Dbase Reloc
            c0t0d0s6 0 No Yes

            Extent Start Block Block count
            0 1 8192000

            Device Relocation Information:
            Device Reloc Device ID
            c0t0d0 Yes id1,sd@n600508e000000000cc0d0c3b724c1f06
            • 3. Re: raidctl  "panic[cpu0]/thread=180e000: vfs_mountroot: cannot remount root"
              bobthesungeek76036
              My bad.

              Boot failsafe and check your /etc/vfstab. Also run prtvtoc /dev/rdsk/c0t0d0s2 and make sure your partition table is still intact on your disk.
              • 4. Re: raidctl  "panic[cpu0]/thread=180e000: vfs_mountroot: cannot remount root"
                user13643597
                The prtvtoc its intact in to disks:

                #prtvtoc /dev/rdsk/c0t1d0s0
                * First Sector Last
                * Partition Tag Flags Sector Count Sector Mount Directory
                0 2 00 33538688 16779136 50317823 /a
                1 3 01 0 33538688 33538687
                2 5 00 0 142599808 142599807
                3 7 00 50317824 16779136 67096959
                5 8 00 67096960 4195328 71292287
                6 0 00 71292288 71240064 142532351
                7 0 00 142532352 67456 142599807



                # prtvtoc /dev/rdsk/c0t0d0s2
                * /dev/rdsk/c0t0d0s2 partition map
                * First Sector Last
                * Partition Tag Flags Sector Count Sector Mount Directory
                0 2 00 33538688 16779136 50317823
                1 3 01 0 33538688 33538687
                2 5 00 0 142599808 142599807
                3 7 00 50317824 16779136 67096959
                5 8 00 67096960 4195328 71292287
                6 0 00 71292288 71240064 142532351
                7 0 00 142532352 67456 142599807


                # format
                AVAILABLE DISK SELECTIONS:
                0. c0t0d0 <LSILOGIC-LogicalVolume-3000 cyl 65533 alt 2 hd 16 sec 136>
                /pci@780/pci@0/pci@9/scsi@0/sd@0,0
                1. c0t1d0 <LSILOGIC-LogicalVolume-3000 cyl 65533 alt 2 hd 16 sec 136>
                /pci@780/pci@0/pci@9/scsi@0/sd@1,0
                • 5. Re: raidctl  "panic[cpu0]/thread=180e000: vfs_mountroot: cannot remount root"
                  user13643597
                  Hi,

                  I do:

                  #boot -F failsafe

                  #mount /dev/dsk/c0t0d0s0 /a

                  #cp /a/etc/vfstab /a/etc/vfstab.orig

                  comment and add in vfstab

                  #/dev/md/dsk/d10     /dev/md/rdsk/d10 / ufs 1 no -
                  /dev/dsk/c0t0d0s0     /dev/rdsk/c0t0d0s0 / ufs 1 no -

                  #cp /a/etc/system /a/etc/system.orig

                  comment line (# rootdev:/pseudo/md@0:0,0,blk)

                  #bootadm update-archive -R /a

                  #init 6

                  the machine boot normaly, but I the disk its same:

                  #format
                  AVAILABLE DISK SELECTIONS:
                  0. c0t0d0 <LSILOGIC-LogicalVolume-3000 cyl 65533 alt 2 hd 16 sec 136>
                  /pci@780/pci@0/pci@9/scsi@0/sd@0,0

                  and

                  #raidctl
                  Controller: 0
                  Disk: 0.0.0
                  Disk: 0.1.0


                  I boot anothter time in failsafe, and add the volume to raid


                  #raidctl -f -c c0t0d0 c0t1d0

                  # raidctl
                  Controller: 0
                  Volume:c0t0d0
                  Disk: 0.0.0
                  Disk: 0.1.0

                  #format
                  AVAILABLE DISK SELECTIONS:
                  0. c0t0d0 <LSILOGIC-LogicalVolume-3000 cyl 65533 alt 2 hd 16 sec 136>
                  /pci@780/pci@0/pci@9/scsi@0/sd@0,0



                  I ask what is the best pratice to destroy this raid, and have only two disks with SVM?

                  I want use the second disk to live upgrade(SVM>ZFS)
                  • 6. Re: raidctl  "panic[cpu0]/thread=180e000: vfs_mountroot: cannot remount root"
                    GNJ
                    Hi

                    After all the above actions and creation of raid back again, are you able to boot the system to normal mode? Some times the raid breaking can be destructive.

                    Can you provide me more details of your HBA controller? Raid on the OS disks must not be destroyed when OS is running. For Certain controllers, the Raid can be broken in the open boot debug level which is riskfree.
                    Please provide the details as below.

                    # fcinfo hba-port
                    # raidctl
                    # raidctl -l cxtxdx (I hope the device is c0t0d0 in your case)
                    # metastat -p


                    Regards
                    Jayakrishnan G Naik

                    Edited by: JKGN on Jun 12, 2012 10:42 PM

                    Edited by: JKGN on Jun 12, 2012 10:43 PM
                    • 7. Re: raidctl  "panic[cpu0]/thread=180e000: vfs_mountroot: cannot remount root"
                      user13643597
                      Hi,

                      I dont have hba's in this machine.

                      #raidctl
                      Controller: 0
                      Volume:c0t0d0
                      Disk: 0.0.0
                      Disk: 0.1.0
                      #raidctl -l c0t0d0
                      Volume Size Stripe Status Cache RAID
                      Sub Size Level
                      Disk
                      ----------------------------------------------------------------
                      c0t0d0 310.9M N/A OPTIMAL OFF RAID1
                      0.0.0 310.9M GOOD
                      0.1.0 310.9M GOOD
                      #metastat -p
                      d63 1 1 c0t0d0s6
                      d41 1 1 c0t0d0s5


                      I try create volumes with SVM, but I do not get it. but my main question is how to destroy the raid, and up the machine, and use the second disk to live upgrade.

                      Regards