Uh, you also need to fix up /etc/vfstab, if the /dev/dsk/XXXX is not the
same.
Just removing all the links and doing a reconfiguration boot won't
_necessarily_ make the probe order of the controller any different. If
it is /dev/dsk/c1t0d0s0 it _might_ still be that after all that. (The
order in which things are probed won't necessarily be changed.)
Solaris is probably particularly ill-equipped for use on media like
removal USB devices, because it wants to to hard code physical paths in
places like /etc/path_to_inst, /etc/vfstab, etc.
-- Garrett
Noelle Milton Vega wrote:
> THIRD POSTING (LOOKING FOR HELP). SEE PROBLEM DESCRIPTION BELOW
>
> (Because there were no answers to my previous two posts below on this
> same topic). Please email me with any answers, since I cross posted in hopes
> of finding an answer. I will post-back good results. The email address is:
>
> nmvega at ComputingArchitects.Com
>
> Hi:
>
> After moving my USB drive (on which the O/S is installed) from one USB
> port to another on my laptop, I need to reconfigure/re-order the Solaris
> 10 x86 (nv48) device trees so that it can boot again. Right now,
> it does not boot as attached to the new USB port.
>
> So as shown below, I performed the standard reconfiguration
> steps I have many times over the years, yet they do not seem
> to be enough on Solaris 10 x86. Here they are. What did
> I miss (TIA!):
>
> ====================================================
> Step 1) boot to failsafe ramdisk based O/S
> Step 2) mount -F ufs -o rw /dev/dsk/c1t0d0s0 /a
> Step 3) (see rest that follows)...
>
> rm -f /a/dev/dsk/*
> rm -f /a/dev/rdsk/*
> rm -f /a/etc/path_to_inst
> (I never "rm" the /devices tree; I only append to it)
>
> cp /tmp/root/etc/path_to_inst /a/etc/path_to_inst
> cd /dev/dsk; find . | cpio -pudm /a/dev/dsk
> cd /dev/rdsk; find . | cpio -pudm /a/dev/rdsk
> cd /devices; find . | cpio -pudm /a/devices
>
> vi /a/boot/solaris/bootenv.rc (adjust the bootpath directive).
>
> /sbin/bootadm update_archive -v -R /a
>
> # And for good measure, I also did this:
> cd /a/boot/grub
> installgrub ./stage1 ./stage2 /dev/rdsk/c1t0d0s0
> =====================================================
>
> So after doing all that and rebooting, I get the GRUB menu
> and select Solaris to boot normally. What happens? The initial
> Solaris banner shows up (and nothing else). It just hangs
> forever. I specified "-v" to the kernel line within GRUB, and
> I see its gets to the "PCI Express device line (early)", and
> thats it (it goes no further).
>
> Did I miss something?
>
> Thanks,
> Noel Milton Vega
> nmvega at ComputingArchitects.Com
>
>
> This message posted from opensolaris.org
> _______________________________________________
> laptop-discuss mailing list
> laptop-discuss at opensolaris.org
>
--
Garrett D'Amore, Principal Software Engineer
Tadpole Computer / Computing Technologies Division,
General Dynamics C4 Systems
http://www.tadpolecomputer.com/
Phone: 951 325-2134 Fax: 951 325-2191
