Updating platform sun4v boot archive

Boot newly created ldom into single-user mode and then pkgrm all Veritas software and also edit the /etc/system file to ensure any remnant of veritas from the physical incarnation of the system are removed as well.

Investigating the sizes of existing filessystems on the server, it might turn out that a particular filesystem is not very heavily being used.

However, in Solaris 10 it does not seem to do the same. Sun Netra T5220, No Keyboard Copyright 2008 Sun Microsystems, Inc. Open Boot 4.30.0, 4096 MB memory available, Serial #81044804. Boot device: /[email protected]/[email protected]/[email protected]/[email protected]/[email protected],0:a File and args: ERROR: Last Trap: Fast Data Access MMU Miss ok I am stuck in the ok prompt and cannot boot anymore, not even to single user mode. Once you are in "ok" prompt, you have couple of choices to boot the system through network/jumpstart server or cdrom. You can also try booting into failsafe mode(not sure if this is gonna work, have not tried this option) from ok prompt by running boot -F failsafe. ok boot cdrom -s Sun OS Release 5.10 Version Generic_137137-09 64-bit Copyright 1983-2008 Sun Microsystems, Inc. Booting to milestone "milestone/single-user:default". Skipped interface e1000g2 Attempting to configure interface e1000g1... Skipped interface e1000g1 Attempting to configure interface e1000g0... In our instance (old-phys-server-ldom:/export/home size was 46GB and only 213MB of it was being used.Recently i faced an issue on T2000 server where i applied latest solaris patchset without reading the special instructions in the patchset readme and kernel readme files.

Search for updating platform sun4v boot archive:

updating platform sun4v boot archive-20updating platform sun4v boot archive-12updating platform sun4v boot archive-57

If not, look at the output and figure out what you might need to fix (eg: if the source system was mirroed using disksuite or veritas, you might want to edit the /etc/vfstab and /etc/system file by mounting rootdisk to temporary mount point and comment out entries corresponding to rootdev or encapsulated Solaris Vol Mgr or vxfs filesystems).

Leave a Reply

Your email address will not be published. Required fields are marked *

One thought on “updating platform sun4v boot archive”