Hi Lars, Thank you for the response - it has prompted me to do some more thinking and investigation.
Note: zfs root file systems are not mentioned in /etc/vfstab - in fact the file is not even included in the boot archive. Also the file /etc/path_to_inst is used to reserve driver instance to physical device paths, and does not specify the boot device - the boot device is specified by its full, real device path - nothing is trying to look-up driver instances just yet. I need to go re-read the boot process docs on x86 as it has changed much. But the stage where this is at: grub loads. find-root actually FINDS the boot-archive (Thus the real device is known) Solaris starts to load, so the boot-archive has decompresesed and un-mounted... Something in there refers to the boot device, overwriting what grub found/thought is the boot disk, so I try to look for it: / $ bootadm list-archive|xargs file|grep text|cut -d: -f1|xargs grep -i "[EMAIL PROTECTED]/[EMAIL PROTECTED],0" etc/path_to_inst:"/[EMAIL PROTECTED],0/[EMAIL PROTECTED],2/[EMAIL PROTECTED]/[EMAIL PROTECTED],0" 0 "cmdk" That is un-interesting. Lets look for the compliment: / $ bootadm list-archive|xargs file|egrep -v "text|directory" etc/devices/devid_cache: data etc/devices/mdi_scsi_vhci_cache: data We can eliminate vhci from the onset as I'm not multi-pathing (or can we? regardless... devid_cache looks interesting) / $ strings etc/devices/devid_cache /[EMAIL PROTECTED],0/[EMAIL PROTECTED],2/[EMAIL PROTECTED]/[EMAIL PROTECTED],0 devid &cmdkTOSHIBA MK1032GSX= 27BQFEJTS /[EMAIL PROTECTED],0/pci1179,[EMAIL PROTECTED],7/[EMAIL PROTECTED]/[EMAIL PROTECTED],0 devid bG'$2 /[EMAIL PROTECTED],0/pci1179,[EMAIL PROTECTED],7/[EMAIL PROTECTED]/[EMAIL PROTECTED],0 devid bG'$2 This looks very promising / $ man -k devid_cache devid_cache devices (4) - device configuration information The man page however does not help me much, so I'm stumped. Experimenting with this is also tedious, made worse by my paranoia about anti-static precautions. On Thu, Jul 31, 2008 at 11:59 AM, Lars Tunkrans <[EMAIL PROTECTED]>wrote: > > > > <br>Why would Solaris look for the device in the old > > location? Is this configured > > somewhere?<br> > > Yes , its configured in /etc/vfstab and in /etc/path_to_inst > and its depentent on you having a USB soultion thats usable. > > Its is possible to boot from USB as I have booted the the older Indiana > Preview from USB thanks to instrunctions in Dave Miners blog. > > This is probably not a bug. Solaris is not designed to be able to move a > system configured for SATA to boot via USB. > > it would be a request for enhancment in that case. > One possibility that might work is to do an upgrade install on the disk > once its moved , hovewer I have not tried to do that. > > > //Lars > > > This message posted from opensolaris.org > _______________________________________________ > opensolaris-help mailing list > [email protected] > -- Any sufficiently advanced technology is indistinguishable from magic. Arthur C. Clarke
_______________________________________________ opensolaris-help mailing list [email protected]
