From: Sylvain Robitaille (syl@alcor.concordia.ca)
Date: Fri Nov 01 2002 - 14:47:06 EST
[ This message posted to the comp.unix.tru64 newsgroup and mailed to the
tru64-unix-managers mailing list. My apologies to those who will see
it multiple times... ]
Folks, I'm having a bit of a strange problem. Last week the main system
disk on my AlphaServer4000 system, running Tru64 Unix 5.1A (with
patchkit 3, but I doubt that makes any difference), stopped working.
I installed a "scratch" OS on a spare disk, and reloaded the real OS
from tape, but now I can't boot it. It gets as far as:
Loading vmunix
text XXXXXXXXX <- (I can't recall the exact number displayed here)
text short read <- (definitely indicative of a problem, but what?)
Then it displays a prompt asking me for the filename of the kernel I
wish to boot, or "press return for /vmunix". Both pressing return for
/vmunix, or entering "/genvmunix", for example, result in a
near-immediate scrolling of various system register values, followed by
a system reset (ultimately back to the SRM prompt). The "scratch" OS
boots fine, and the previous installation *used* to boot fine...
To be sure anyone trying to help me has a clear picture of how I've setup
the disk to reload the OS on, here is a brief transcript of my
operations:
(with the scratch OS booted, and my "local software" disk mounted at
/local, so I can have access to relevant data. The file "disklabel.dsk1"
contains a disklabel read from the original system disk, permitting me
to restore the label on the replacement disk so that it matches.)
disklabel -z dsk1
disklabel -Rr -t advfs dsk1 /local/pkg/_OS/disks/disklabel.dsk1
# Create and mount file domains for recovery:
mkfdmn -r /dev/disk/dsk1a recover_root
mkfset recover_root root
mkfdmn /dev/disk/dsk1d recover_usr
mkfset recover_usr usr
mkfdmn /dev/disk/dsk1e recover_var
mkfset recover_var var
mount recover_root#root /mnt
mkdir /mnt/usr /mnt/var
chmod 555 /mnt/usr /mnt/var
mount recover_usr#usr /mnt/usr
mount recover_var#var /mnt/var
# Finally, reload the data from tape.
Since the replacement disk was in the system originally as dsk2, I then
went in and changed references to dsk1 to point to the new system disk:
cd /mnt/etc/fdmns/root_domain
rm dsk1a
ln -s /dev/disk/dsk2a .
cd /mnt/etc/fdmns/usr_domain
rm dsk1d
ln -s /dev/disk/dsk2d .
cd /mnt/etc/fdmns/var_domain
rm dsk1e
ln -s /dev/disk/dsk2e .
# Move the swap partition:
# --- /mnt/etc/old/sysconfigtab.20021031 2002-10-10 14:43:02.000000000 -0400
# +++ /mnt/etc/sysconfigtab 2002-10-31 16:35:30.000000000 -0500
# @@ -412,7 +412,7 @@
# new_vers_low = 51969
#
# vm:
# - swapdevice = /dev/disk/dsk1b
# + swapdevice = /dev/disk/dsk2b
# vm-swap-eager = 1
#
# #-----------------------------------------------------------------------
Now, I expected that at this point I should be able to reboot with my
system intact, but it's not booting. :-( Does anyone have any idea
what I'm doing wrong?
-- ---------------------------------------------------------------------- Sylvain Robitaille syl@alcor.concordia.ca Systems analyst Concordia University Instructional & Information Technology Montreal, Quebec, Canada ----------------------------------------------------------------------
This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 10:48:58 EDT