Summary:
========
thanks: sturges@gmri.com, "Marco Greene" <cmgreene@netcom.ca>,
Jim Robertori <jimr@tpesops.pr.lucent.com>,
ganeshan" <ganeshan@gcs.com.au>, "Carsten B. Knudsen" <cbk@terma.dk>,
dmorse@Morsesoft.COM, Lee Boon Heong <info@penang.csam.com.my>,
Rik Schneider <rik@netasset.com>, Matt Simmons <simmonmt@acm.org>,
and others.
I should have been clearer in my original post that SCSI disk IDs did not
change, and that the failed boot printout was from a "boot -r".
The solution to my problem was to:
- replace /etc/path_to_install on the non-booting disk with the
single line: #path_to_inst_bootstrap_1
- then do a: boot -r
During the reconfigure boot process, the /etc/path_to_install was automatically
rebuilt for the new machine, and the apropriate device links were remade.
As a side note, my news server running inn definitely performs better with
2.6 then before with 2.5.1.
Original:
==========
Hi,
I have a disk with Solaris-2.6 installed from an SUNW,Ultra-Enterprise
machine.
I'd like to make the disk bootable on a SUNW,Ultra-1, preferably
without doing a reinstall.
Currently the Ultra-1 machine is running 2.5.1, has the 2.6 disk in
it, but fails during boot from the 2.6 disk with these messages:
Boot device: /sbus/espdma@e,8400000/esp@e,8800000/sd@0,0 File and args: -rs
SunOS Release 5.6 Version Generic_105181-06 [UNIX(R) System V Release 4.0]
Copyright (c) 1983-1997, Sun Microsystems, Inc.
configuring network interfaces: le0.
Hostname: something.misty.com
mount: /dev/dsk/c0t0d0s6 no such device
/sbin/swapadd: expr: not found
/sbin/swapadd: /usr/sbin/swap: not found
WARNING - /usr/sbin/fsck not found. Most likely the
I tried mounting the 2.6 root while running 2.5.1, and adding appropriate
device nodes and symlinks for /dev/dsk/c0t0d0s6 (for the Ultra-1), but there
is clearly far more to it then that.
Any assistance or pointers would be greatly appreciated,
-Mark
-- Mark G. Thomas (Mark@Misty.com -- http://www.misty.com/)
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:12:50 CDT