Ok, the first thing to make sure is clear here is that the system is not in multi-user mode with a read only /var. It's booting, getting to the point where it remounts /var read-write and it's failing because of fsck problems with /var (apparently).
It seems some of the folks making the comments think the system is in rc2 or rc3 (this is just me making sure we're on subject).
Since we have the system in house and rebuilt, we did some testing with installboot to see if we could find out why we couldn't boot to c0t2d0s0 even after installing the bootblk.
Quote:
Originally Posted by BOFH
c0t0d0 and c0t2d0 are the two disks.
c0t2d0 is identified as the left side of the mirror where normally t0 is left and t2 is right.
6. eeprom to set boot-device=disk1
Just to make sure you see it, the first disk is:
c0t0d0s0
And the second disk is:
c0t2d0s0
Apparently when OPB does its configuration of the disks, it labels them based on the target. So when I tried to boot to
disk1 it was falling back to
disk. After testing, we found that we needed to boot to
disk2 not
disk1. When we booted to
disk2, we were able to successfully boot in.
So the process above was correct in that it should have booted as expected and we could have brought the system back up had we used the correct alias.
Thanks for all the comments. I did learn something from your replies. Hopefully the solution will help one of you as well.
Carl
