Solaris 10 luupgrade flash archive file system creation failed

UNIX Solaris
1

Hey guys,
I'm attempting to migrate us to a new box. First problem I had was the change in architecture going from sun4u to sun4v, we have a Sun M5000 and are moving to a Fujitsu M10-4. I figured out how to make the flash archive work between architectures.

Now I appear to be running into an issue with the file system I created for an ABE and using luupgrade to install the flash archive. The disk is appears to be fine and the creation of the ABE didn't appear to have any trouble with creating the UFS filesystem on it.

Not finding much out there through searches. I'm including the error received along with some configuration info. The file system was created on mirrored local disks. Any help pointing me in the right direction would be appreciated.

bash-3.2# luupgrade -f -n sol10-Q3-2015 -s /mnt/install_disk -a /root/erp-m5000
_20150821.flar          

67352 blocks
miniroot filesystem is <lofs>
Mounting miniroot at </mnt/install_disk/Solaris_10/Tools/Boot>
Validating the contents of the media </mnt/install_disk>.
The media is a standard Solaris media.
Validating the contents of the miniroot </mnt/install_disk/Solaris_10/Tools/Boot>.
Locating the flash install program.
Checking for existence of previously scheduled Live Upgrade requests.
Constructing flash profile to use.
Creating flash profile for BE <sol10-Q3-2015>.
Performing the operating system flash install of the BE <sol10-Q3-2015>.
CAUTION: Interrupting this process may leave the boot environment unstable or unbootable.
ERROR: The flash install failed; pfinstall returned these diagnostics:

Processing profile
        - Opening Flash archive
        - Validating Flash archive
        - Selecting all disks
        - Configuring boot device
        - Configuring SVM State Database Replica on  (c1t50000395BC890312d0s5)
        - Configuring SVM State Database Replica on  (c1t50000395BC890312d0s6)
        - Configuring SVM State Database Replica on  (c1t50000395CC88821Ed0s5)
        - Configuring SVM State Database Replica on  (c1t50000395CC88821Ed0s6)
        - Configuring SVM State Database Replica on  (c1t50000395CC88822Ad0s5)
        - Configuring SVM State Database Replica on  (c1t50000395CC88822Ad0s6)
        - Configuring SVM State Database Replica on  (c1t50000395CC88823Ad0s5)
        - Configuring SVM State Database Replica on  (c1t50000395CC88823Ad0s6)
        - Configuring SVM Mirror Volume d40 on / (c1t50000395BC890312d0s0)
        - Configuring SVM Mirror Volume d40 on  (c1t50000395CC88822Ad0s0)
        - Configuring SVM Mirror Volume d44 on /var (c1t50000395BC890312d0s4)
        - Configuring SVM Mirror Volume d44 on  (c1t50000395CC88822Ad0s4)
        - Configuring SVM Mirror Volume d47 on /export/home (c1t50000395BC890312d0s7)
        - Configuring SVM Mirror Volume d47 on  (c1t50000395CC88822Ad0s7)
        - Deselecting unmodified disk (c0t5002361004655480d0)
        - Deselecting unmodified disk (c0t5002361004658660d0)
        - Deselecting unmodified disk (c0t5002361004658880d0)
        - Deselecting unmodified disk (c0t5002361004659050d0)
        - Deselecting unmodified disk (c0t5002361004664800d0)
        - Deselecting unmodified disk (c0t5002361004668410d0)
        - Deselecting unmodified disk (c0t5002361004673060d0)
        - Deselecting unmodified disk (c0t5002361004675130d0)

Preparing system for Flash install

Creating and checking file systems
        - Creating / (c1t50000395BC890312d0s0)

ERROR: File system creation failed for / (c1t50000395BC890312d0s0)

ERROR: Could not check or create system critical file systems

ERROR: Could not update disks with new configuration

ERROR: Flash installation failed
The Solaris flash install of the BE <sol10-Q3-2015> failed.


bash-3.2# metastat -p
d47 -m d57 d67 1
d57 1 1 /dev/dsk/c1t50000395BC890312d0s7
d67 1 1 /dev/dsk/c1t50000395CC88822Ad0s7
d44 -m d54 d64 1
d54 1 1 /dev/dsk/c1t50000395BC890312d0s4
d64 1 1 /dev/dsk/c1t50000395CC88822Ad0s4
d41 -m d51 d61 1
d51 1 1 /dev/dsk/c1t50000395BC890312d0s1
d61 1 1 /dev/dsk/c1t50000395CC88822Ad0s1
d40 -m d50 d60 1
d50 1 1 /dev/dsk/c1t50000395BC890312d0s0
d60 1 1 /dev/dsk/c1t50000395CC88822Ad0s0
d7 -m d17 d27 1
d17 1 1 /dev/dsk/c1t50000395CC88821Ed0s7
d27 1 1 /dev/dsk/c1t50000395CC88823Ad0s7
d4 -m d14 d24 1
d14 1 1 /dev/dsk/c1t50000395CC88821Ed0s4
d24 1 1 /dev/dsk/c1t50000395CC88823Ad0s4
d1 -m d11 d21 1
d11 1 1 /dev/dsk/c1t50000395CC88821Ed0s1
d21 1 1 /dev/dsk/c1t50000395CC88823Ad0s1
d0 -m d10 d20 1
d10 1 1 /dev/dsk/c1t50000395CC88821Ed0s0
d20 1 1 /dev/dsk/c1t50000395CC88823Ad0s0


bash-3.2# metastat d40
d40: Mirror
    Submirror 0: d50
      State: Okay         
    Submirror 1: d60
      State: Okay         
    Pass: 1
    Read option: roundrobin (default)
    Write option: parallel (default)
    Size: 167777568 blocks (80 GB)

d50: Submirror of d40
    State: Okay         
    Size: 167777568 blocks (80 GB)
    Stripe 0:
        Device                             Start Block  Dbase        State Reloc Hot Spare
        /dev/dsk/c1t50000395BC890312d0s0          0     No            Okay   Yes 


d60: Submirror of d40
    State: Okay         
    Size: 167777568 blocks (80 GB)
    Stripe 0:
        Device                             Start Block  Dbase        State Reloc Hot Spare
        /dev/dsk/c1t50000395CC88822Ad0s0          0     No            Okay   Yes 


Device Relocation Information:
Device                           Reloc  Device ID
/dev/dsk/c1t50000395BC890312d0   Yes    id1,sd@n50000395bc890310
/dev/dsk/c1t50000395CC88822Ad0   Yes    id1,sd@n50000395cc888228


bash-3.2# iostat -En
c1t50000395BC890312d0 Soft Errors: 0 Hard Errors: 0 Transport Errors: 0 
Vendor: TOSHIBA  Product: PX02SMF020       Revision: 3701 Serial No: 8490A005TZV2 
Size: 200.05GB <200049647616 bytes>
Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0 
Illegal Request: 0 Predictive Failure Analysis: 0 
c1t50000395CC88822Ad0 Soft Errors: 0 Hard Errors: 0 Transport Errors: 0 
Vendor: TOSHIBA  Product: PX02SMF020       Revision: 3701 Serial No: 9440A018TZV2 
Size: 200.05GB <200049647616 bytes>
Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0 
Illegal Request: 0 Predictive Failure Analysis: 0
2

Nearly a whole day and no replies so I'll try to get some dialogue going here.

I think the issue is occurring because of the change of hardware and the fact that all device nodes (/dev/rdsk/<node>) are going to be different from the original hardware. This is always a bit complex.

Therefore when it tries to create a filesystem on the original device node it's not there. This is also true if you were to try and boot from the new root filesystem.

I think therefore you may need to manage the creation of the new device nodes.

You are a new member on this forum so I have no clue how much Solaris experience you are carrying and therefore how easy you will find this to resolve.

You may well get some better answers than this but thought I'd chip in due to the lack of responses.

3

I went ahead and put in a support request to Oracle. Looks like they already had a bug with the same error.

BUG 15817675 - SUNBT7200212 luupgrade with flar archive and svm errors
"https://support.oracle.com/epmos/faces/BugDisplay?id=15817675&parent=SrDetailText&sourceId=3-11262419481"

They said this was fixed in Solaris 10u11, but we're already on that version. They asked for further information and I'm awaiting a response to that now. I'll keep this updated on what I find.