We had a Sun Netra T1 go down the other day, the root disk was mirrored using vxvm. Upon boot from either disk, we had the following error appear:
WARNING: Error writing ufs log state
WARNING: ufs log for / changed state to Error
WARNING: Please umount(1M) / and run fsck(1M)
WARNING: Error writing master during ufs log roll
WARNING: ufs log for / changed state to Error
WARNING: Please umount(1M) / and run fsck(1M)
Cannot mount root on /pseudo/vxio@0:0 fstype ufs
panic[cpu0]/thread=140a000: vfs_mountroot: cannot mount root
no problems i thought. I'm well aware of this issue with VX. However I discovered I couldn't boot from vx root or mirror (same errors), we tried the cd, and the that failed too (suspected broken cdrom).
having given up all hope, I randomly tried a 'boot -a' (accepting all defaults) which somehow got me into multiuser, but with no vxvm partitions installed, or vx processes running. From there we were able to recover the system.
Can anyone shed any light as to how or why 'boot -a' worked? Not being a VX guy, I'm really scratching my head, and can't recreate this problem.
What is your Veritas Foundation version? Your Solaris OS version?
What caused the system to go down? What were you doing on the system? Any activities during the time? System running any HA?
system went down due to possible cpu/memory error (AFAR/AFSR). As autoboot had been set to true, we found it contsnantly trying to boot from rootdisk (and failing).
i'm 100% positive that boot into single user didnt succeed. I do know that I accepted all defaults when doing the 'boot -a' so maybe it wa something there that allowed me to boot without VX control.
We have a number of machines that are mirrored using vxvm (inherited systems - not my choice!) so it would be good to get to the bottom of this if anyone can shed some light.