Are you talking about the GP installations that happen prior to login? If so, wasn't it a group policy setting that enabled those verbose status messages to begin with? It's in the system.adm template.
Computer Configuration\Policies\Administrative Templates\System
"Verbose vs normal status messages" = Enabled
Directs the system to display highly detailed status messages.
If you enable this setting, the system displays status messages that reflect each step in the process of starting, shutting down, logging on, or logging off the system.
This setting is designed for sophisticated users that require this information.
Note: This setting is ignored if the "Remove Boot / Shutdown / Logon / Logoff status messages" setting is enabled.
Pulling the power causes everything to stop in flight, with no warning. kill -9 has the same effect on a single process, forcefully terminating it with a SIGKILL.
If a process is killed by kernel or power outage, it doesn't do any clean-up. That means you could have half-written files, inconsistent states, or lost caches. You usually don't have to worry about any of this because of journaling, exit status and battery backup.
Temporary files in /tmp will be automatically gone if they are in tmpfs, but you may still have application-specific lock files laying around to remove, like the lock and .parentlock for firefox.
Most software is smart enough to retry a transaction if it doesn't record a successful exit status. A good example of this is a typical mail system. If a message is being delivered, but gets cut off in the middle, the sender will retry later until it gets a success.
Your filesystem is probably journaled. If you are moving or writing a file and it dies mid-stream, the journaled file system will still reference the original. The journaled filesystem will make changes non-destructively, leaving the old copy, then only reference the new copy as a last step before reclaiming space the old copies occupied on disk.
Now if you have a RAID array, it has all kinds of memory buffers to increase performance and provide reliability in a power failure. Most likely your filesystem will not know about the caches in the device and their state, so it thinks a change has been committed to disk, but it is still in the RAID cache somewhere. So what happens when the power dies? Hopefully you have a functional battery in your RAID enclosure and you monitor it. Otherwise you have a corrupt file system to fsck.
Yes, a few bits can become corrupted in a binary, but I would not worry about that much on modern hardware. If you are really paranoid, you can monitor the health of your disks and RAID with the appropriate tools, but you should be doing that anyway. Do regular backups and get an Uninterruptible Power Supply.
Best Answer
Actually, I just had to use the format command in the Solaris installation console. I then chose the disk (only one in my workstation, so it was an easy choice), and things went rolling.