799786 wrote:There are people who know these things far better than me, and I will easily defer, but ensure you have visited e.g. http://docs.oracle.com/cd/E19082-01/819-2379/gglbi/index.html to review the troubleshooting advice about boot archive
Hi - I've just O/S patched one of our Solaris 10 servers and it's not come back after the reboot. It's remote and I can't go onsite until later today but do have details of what happened just after I issued the reboot command and am wondering if anyone knows what this means? It's a SunFire T2000 running several non-global zones. Previous patch cluster applied was from 14 Feb 2013 and the kernel running was:
SunOS xxxxxxxxxxxx 5.10 Generic_147147-26 sun4v sparc SUNW,SPARC-Enterprise-T2000
I patched it with Oracles patch cluster from 2013.04.23.
Upon reboot I got this on my ssh session:
mount: /dev/lofi/1 is not this fstype
umount: warning: //boot/create_ramdisk.14706.tmp/rd.mount.32 not in mnttab
umount: //boot/create_ramdisk.14706.tmp/rd.mount.32 not mounted
rmdir: directory "//boot/create_ramdisk.14706.tmp/rd.mount.32": Directory not empty
15+0 records in
15+0 records out
It's the lines in BOLD that I've never seen before, the patching went fine and only about 4 patches were applied. The servers O/S is mirrored via SVM and I'd split the disk mirrors before patching so worst case I'll boot from the unpatched half of the mirror .... hopefully.
Anyone seen this before or any help / advice would be appreciated.
Thanks - Julian.