Shay wrote:
> p@p.com wrote:
>
> > I used the following, I can't see much difference and I still get the WWN
> > errors?
> >
> > # mount -F ufs /dev/dsk/<root disk device name> /mnt
> > # rm -rf /mnt /dev
> > # rm -rf /mnt /devices
> > # devfsadm -r /mnt -p /mnt/etc/path_to_inst
> > # cp -R /devices /mnt/devices <Solaris 10 only>
> >
> > # cp -R /dev /mnt/dev <Solaris 10 only>
> > # init 0
> > ok boot -r
>
> As far as I can tell, this might not works for drive replacement if the
> drive uses a WWN. You might have to rebuild /etc/path_to_inst from
> scratch. I'm not sure if devfsadm will be sufficient (people have both
> sworn by this method and disavowed it as insufficient - apparently
> mileage varies with this approach from release to release).
>
> Try the same procedure, but remove /mnt/etc/path_to_inst entirely (in
> lieue of the devfsadm run) and reboot with the "reboot -- -a". This
> should give you the option to rebuild path_to_inst. Alternately you can
> boot from cdrom and compare the files to see if there are any
> discernable difference between the active file and the one on /mnt.
>
> If that doesn't correct the issue, I'm not sure what is causing the
> errors. At that point, if it didn't correct the issue, I'd probably
> build the drive fresh and copy everything over But path_to_inst and the
> /dev and /devices dirs.
>
> ~ Shay

Another possible solution would be to copy the old path_to_inst, blow
away the device entries
in path_to_inst, blow away /devices and /dev and boot -r