Sorry for the somewhat late summary , bur things have been quite hectic
Thanks to everybody who replied.
My original question was :-
I am trying to replicate the disk of our backup server (solaris 2.5), so
in the case of a disaster recover situation, I can simply hook up an
external disk, and boot.
I replicate the servers internal disk to an external disk and install
the bootblock. However when I then plug this into another workstation
and boot, the boot fails, as obviously the SCSI ID's have changed and
the device links aren't correct. At this point at get left at the prompt
with a read-only filesystem. Is there any way to remount this /
filesystem read-write, so that I can run drvconfig;disks;devlinks an
update the disk devices and associated links.
Thanks in advance
Unix Systems Admin
P.S Whats the difference between Solaris 2.5 and 2.5.1, Is there
anything to be gained from running 2.5.1 as opposed to 2.5. It was my
>understanding that 2.5.1 was only necessary fro Ultra architectures.
Thanks to all that responded,
Tim Carlson [firstname.lastname@example.org]
Frank Pardo [email@example.com]
Karlheiz Pischke [firstname.lastname@example.org]
R. Nemlekar [email@example.com]
Yizhong Zhou [firstname.lastname@example.org]
Caleb Warner [email@example.com]
Dan Pritts [firstname.lastname@example.org]
Michael Fetzer [Michael_Fetzer@mktstrat.com]
Lin Hai [Hai.Lin@PRC.Sun.COM]
Darrin Currier [email@example.com]
Peter Allan [firstname.lastname@example.org]
Rich Kulawiec [email@example.com]
1) To boot off an external disk boot -r diskn ( where n is the
scsid),Not quite the answer i was looking for.
2) Boot of cdrom, mount the / partition and edit vfstab.
3) try /sbin/mount -o remount,rw /dev/dsk/whatever /
This last one did the trick, i could then run drvconfig;disks;devlinks
and update all the device sym links, and edit the vfstab.
Answers to the P.s:-
I can't answer your first question sorry. However 2.5 versus 2.5.1 I can
a stab at. We are running in an environment with about 175 mixed
dual processor sparc20s. We meet weekly with Sun Service and Sun Sales
review any outstanding issues. They have been telling us for about two
now, that we should absolutely without question be running 2.5.1. They
give any specifics, however they do say there are a number of bugs that
fixed in 2.5.1.
Hope this helps
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:11:44 CDT