#228508: Hosts Using SE3510 as the Boot Device May Fail to Boot After Upgrade to 4.15F Firmware

Hosts Using SE3510 as the Boot Device May Fail to Boot After Upgrade to 4.15F Firmware

Category :	Availability
Release Phase :	Resolved
Product :	Sun StorageTek 3510 FC Array
Bug Id :	6413623
Date of Workaround Release :	01-SEP-2006
Date of Resolved Release :	31-Mar-2008

Solaris 8, Solaris 9 or Solaris 10 hosts using the Sun StorEdge (SE) 3510 ... see below:

1. Impact

Solaris 8, Solaris 9 or Solaris 10 hosts using the Sun StorEdge (SE) 3510 as the boot device will fail to boot after upgrading the SE3510 with the latest (4.15F) firmware.

2. Contributing Factors

This issue can occur on the following platform:

Sun StorEdge 3510 running 4.15F firmware (on Solaris 8, 9 or 10 systems)

when the SE3510 is being used as the boot device.

3. Symptoms

Should the described issue occur, Solaris 8, 9 or 10 hosts using the SE3510 as their boot device will fail to boot after the firmware upgrade to 4.15F. The host will panic while booting, as in the following example:

    ok> boot
    Boot device: /pci@8,700000/SUNW,qlc@3/fp@0,0/disk@w216000c0ff000002,0:a File and args:
    SunOS Release 5.10 Version Generic 64-bit
    Copyright 1983-2005 Sun Microsystems, Inc. All rights reserved.
    Use is subject to license terms.
    Cannot assemble drivers for root /pci@8,700000/SUNW,qlc@3/fp@0,0/disk@w216000c0ff000002,0:a
    Cannot mount root on /pci@8,700000/SUNW,qlc@3/fp@0,0/disk@w216000c0ff000002,0:a fstype ufs

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

    000000000180b960 genunix:vfs_mountroot+290 (800, 200, 200, 1835200, 11cac00, 187f400)
    %l0-3: 0000000000000000 000000000109c268 000000000109c000 000000000109c34c
    %l4-7: 000000000109c000 000000000109c068 00000000018ad800 0000000000000600
    000000000180ba20 genunix:main+88 (1813c98, 1011c00, 1834340, 18a7c00, 0, 1813800)
    %l0-3: 000000000180e000 0000000000000001 000000000180c000 0000000001835200
    %l4-7: 0000000070002000 0000000000000000 000000000181ba48 0000000000000000

    skipping system dump - no dump device configured
    rebooting...
    Resetting ...

4. Workaround

To avoid this issue, do not upgrade to 4.15F firmware if you are using the SE3510 as a boot device. To work around the described issue, downgrade the SE3510 array firmware to 4.13C.

5. Resolution

There are no further updates planned for this Sun Alert document. If
you need additional assistance regarding this issue, please contact Sun
Services.

This Sun Alert notification is being provided to you on an "AS IS" basis. This Sun Alert notification may contain information provided by third parties. The issues described in this Sun Alert notification may or may not impact your system(s). Sun makes no representations, warranties, or guarantees as to the information contained herein. ANY AND ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT, ARE HEREBY DISCLAIMED. BY ACCESSING THIS DOCUMENT YOU ACKNOWLEDGE THAT SUN SHALL IN NO EVENT BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, PUNITIVE, OR CONSEQUENTIAL DAMAGES THAT ARISE OUT OF YOUR USE OR FAILURE TO USE THE INFORMATION CONTAINED HEREIN. This Sun Alert notification contains Sun proprietary and confidential information. It is being provided to you pursuant to the provisions of your agreement to purchase services from Sun, or, if you do not have such an agreement, the Sun.com Terms of Use. This Sun Alert notification may only be used for the purposes contemplated by these agreements.

Copyright 2000-2008 Sun Microsystems, Inc., 4150 Network Circle, Santa Clara, CA 95054 U.S.A. All rights reserved.

Modification History

31-Mar-2008: no further updates. Resolved.

Attachments

This solution has no attachment

Login Required

Login Required