consider running 'bootadm update-archive' on both servers, then if they're still vastly different sizes you can mount them and compare them.
i can't find any documentation anywhere that mentions boot archive's in a cluster should be a consistent size.
For example, you can determine if a device is recognized by the system and working properly, or you can also obtain useful system configuration information.
See also: start /SP/console [email protected] # uname -a Sun OS foo 5.10 Generic_142900-11 sun4v sparc SUNW, Sun-Blade-T6320 [email protected] # mount | fgrep '/dev/dsk' / on /dev/dsk/c0t0d0s0 read/write/setuid/devices/intr/largefiles/logging/xattr/onerr or=panic/dev=800008 on Thu Feb 17 2011 [email protected] # echo | format Searching for disks..AVAILABLE DISK SELECTIONS: 0. c0t1d0 /[email protected]/[email protected]/[email protected]/LSILogic,[email protected]/[email protected],0 Specify disk (enter its number): Specify disk (enter its number): So on this system, / is currently mounted on target 0 (c0t0d0).
The status LEDs of each system board on Ultra Enterprise servers indicate the POST completion status.
For example, if a system board fails the POST test, the amber LED stays lit.
You can watch POST ouput in real-time by attaching a terminal device to serial port A.
If none is available, you can use the OBP command show-post-results to view the results after POST completes.