Updating platform sun4v bootarchive mature dating sites in the slough area
If you do, you'll need to repartition disk1 the same way.
disk2 & disk3 don't appear to have a boot block, so they will be data disks Good luck! You normally do installboot to the first disk slice 1, eg: installboot /usr/platform/`uname -i`/lib/fs/ufs/bootblk /dev/rdsk/c0t0d0s0 If you want to boot from the mirror disk (disk 1), you might need to boot up the box from Solaris CD/DVD, perform install boot to disk 2, (you need to know the exact disk device name).
Each physical disk is perfectly usable on its own in case of disaster, so if you did the restore to one physical disk, e.g.
c0t0d0, the other one won't have changed I'm out of ideas here, but I'm trying to get hold of some Solaris gurus to help.
You can select the device from the Openboot ("OK") prompt If you've restored to the slices on one physical disk, that means the other is untouched for now; edit vfstab to boot from ONE of the disks (Either the one you've "fixed" or the untouched one, to try to get the system up.
You can recreate mirroring when the boot problem is fixed.
boot cdrom -s mount /dev/dsk/c0t0d0s0 /a patchrm -R /a 137137-09 init 6 ...
My company asked me to reinstall solaris, and restore the filesystem.
As I understand it, ufsdump dumps a single slice/volume and doesn't understand mount points or filesystem hierarchies.
So in presume you had separate tapes as you're not using the norewind device file ?
You already know the stuff in Section 4 ;-) I'm wondering if the Solaris 10 initial boot process is significantly different from Solaris 8/9, where I have most experience.
I've done administration on Solaris 10, but never had to deal with any serious problems...
Hopefully whoever set up the mirroring left the original info in vfstab, and just commented out the physical device names, so it's easy to see what the slice/filesystem mapping should be.