> So on both Solaris 8 x86 and Solaris 10 x86/AMD64 (s10u5 ) I see a
> bootpath device provided to the boot software in some file. Except
> with OpenSolaris which does not seem to have such a thing.
OpenSolaris (Solaris Nevada) on an UFS root should continue to use
a bootpath property in /boot/solaris/bootenv.rc
On snv_96 with an UFS root, I have this:
% grep bootpath /boot/solaris/bootenv.rc
setprop bootpath /[EMAIL PROTECTED],0/pci1043,[EMAIL PROTECTED]/[EMAIL
PROTECTED],0:a
> It looks like I need to inform the boot process about what the correct
> boot device really is. I *think* that means I need to tweak the boot
> envionment with a bootpath device. That *seems* to be possible with
> Solaris 10 but not with OpenSolaris.
Why isn't this possible with OpenSolaris / Solaris Nevada?
Boot using the failsafe grub option, let it mount the hdd under /a,
run "format" to find out the physical device path of the hdd,
and edit that into /a/boot/solaris/bootenv.rc
Update the boot archive with "bootadm update-archive -R /a".
I think there had been some bugs with "bootadm update-archive"
in old Nevada releases when an alternate root was specified, but
they should all have been fixed by now, in recent Nevada release.
> I can tell you
> that I can boot with a CDROM and then just look at the PCI device path
> to the bootable disk but when I enter that info into the
> /boot/solaris/bootenv.rc file as a valid bootpath I get the exact same
> panic.
Hmm, /boot/solaris/bootenv.rc looks wrong.
If you mounted the HDD under /mnt (e.g.), you should
edit /mnt/boot/solaris/bootenv.rc
Note: don't unmount the HDD after making that change.
Either run "bootadm update-archive -R /mnt" before unmounting,
or use the halt / reboot command, which should automatically
update the boot archive on all *mounted* root filesystems.
> I can try to edit the vfstab file and that fails also but I
> don't really think the boot process has proceeded
> that far anyways.
Ok, vfstab needs to be fixed, too. Without that change
you'll get a failure when the HDD boot tries to remount the
root filesystem in read/write mode. You end up with a
single user mode prompt and the root filesystem still
being mounted in read-only mode.
If you do not have a separate /usr filesystem, you can
fix this by:
- remount root in read/write mode
mount -o remount,rw /devices/pysical/path/to/root_fs_device:a /
(I think you can also use "uadmin 4 0" to change the read-only
root into a read/write mounted root)
- mount /tmp, /var/run
- devfsadm -v
- format
(find out the new c?t?d? for the root fs)
- edit /etc/vfstab
- reboot
This message posted from opensolaris.org
_______________________________________________
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
