Solaris Express 6/06 Issues

The following issues apply to the Solaris Express 6/06 release.

Solaris Volume Manager Not Starting on Systems That Revert to Solaris OS Previous to Solaris Express 4/06 Release

You encounter problems with starting the Solaris Volume Manager if you perform the following procedures on your system:

1. Upgrade to the Solaris Express 4/06 OS or a subsequent release that contains the new Solaris Volume Manager support for descriptive names.

2. Create volumes and hot-spare pools, which Solaris Volume Manager automatically configures with descriptive names.

3. Without removing these components, revert to a Solaris OS previous to the Solaris Express 4/06 release currently in the system.

The Solaris Volume Manager in the previous Solaris OS does not recognize the components with descriptive names. Consequently, in the reverted Solaris release, the Solaris Volume Manager does not start. The following error message is displayed:

svc:/system/mdmonitor:default: Method "/lib/svc/method/svc-mdmonitor" 
failed with exit status 1.
   system/mdmonitor:default failed

The system also panics and displays a message similar to the following:

Cannot open mirrored root device, error 19
Cannot remount root on /pseudo/md@0:0,10,blk fstype ufs

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

000000000180b950 genunix:vfs_mountroot+344 (18831f0, 2021, 18831f0, 18621a8, 
18362c0, 185d760)
  %l0-3: 00000000018362c0 000000000185d400 000000000183b400 00000000011e6400
  %l4-7: 0000000000000001 0000000000008025 000000000185d518 00000000018831f0
000000000180ba10 genunix:main+98 (18141a0, 1013400, 18362c0, 18aa000, 
180e000, 1814000)
  %l0-3: 0000000070002000 0000000000000001 000000000180c000 000000000180e000
  %l4-7: 0000000000000001 0000000001074400 0000000000000060 0000000000000000

Workaround: All Solaris Volume Manager components that you created subsequent to the OS upgrade use descriptive names. Remove these components first before performing the OS reversion. Follow these steps:

1. Become superuser.

2. With the metastat -D command, list the metadevices and hot-spare pools that use descriptive names.

   You must issue the command separately for local and named metasets to acquire a complete list of these components. For further details about the metastat command, see the metastat(1M) man page.

   1. Issue the metastat -D command for local metasets. The command generates an output similar to the following:

      # metastat -D
      d21: Concat/Stripe
          Size: 208278 blocks (101 MB)
          Stripe 0:
              Device     Start Block  Dbase   Reloc
              c1t1d0s1          0     No      Yes
      
      swimming: 1 hot spare
              Device     Status      Length           Reloc
              c1t2d0s1   Available    208278 blocks   Yes

   2. Issue the metastat -D command for named metasets. The command generates an output similar to the following

      # metastat -s named -D
      named/alley: Concat/Stripe
          Size: 208278 blocks (101 MB)
          Stripe 0:
              Device     Start Block  Dbase   Reloc
              c1t3d0s1          0     No      Yes

3. With the metaclear command, remove these components that use descriptive names. You must issue this command separately for local and named metasets.

   1. From the local set, remove the component d21 and the hot-spare pool swimming.

      # metaclear d21
      d21: Concat/Stripe is cleared
      # metahs -d swimming c1t2d0s1
      swimming: Hotspare is deleted
      # metahs -d swimming
      swimming: Hotspare pool is cleared

   2. From the named metaset, remove the component alley.

      # metaclear -s named alley
      named/alley: Concat/Stripe is cleared

4. Proceed with reverting to the previous Solaris OS.

smosservice add Command Does Not Install Designated ARCH=all Packages (4871256)

The smosservice add command does not install any packages that are designated ARCH=all in the root (/) or /usr file systems. No error message indicating that these packages were skipped is displayed. This behavior has existed since the Solaris 2.1 OS. The behavior applies to both SPARC based and x86 based clients.

Note that the list of missing packages varies, depending on the Solaris release that you are running.

Workaround:

Locate and install the missing ARCH=all packages.

For step-by-step instructions about locating and installing missing packages, see How to Locate and Install Missing ARCH=all Packages in System Administration Guide: Basic Administration.