From: Bütow, Michael (michael.buetow@comsoft.de)
Date: Mon Jun 16 2003 - 11:21:59 EDT
Thanks to all those who replied - all your advice was helpful!
The problem turned out to be that the dsf database is not backwards compatible between releases or patchkits.
One of the patches in the 5.1B patch kit 2 introduced an incompatibility with the previous version.
I solved the problem by running (still in single user mode):
# dn_setup -init
# dsfmgr -K
Then I rebooted and the OS installation concluded successfully.
Dr Blinn also suggested to execute
>>>set bootdef_dev ""
from the SRM console before reinstalling - this supposedly also clears the problem before a fresh installation.
Unfortunately I have not verified that yet myself, but it is apparently also mentioned in connection with the guilty patch.
Lesson learned - next time I shall be more careful to read up on the patches and not just go ahead installing all of them.
Fortunately this was just a test system...
Kind regards,
Michael
=== original mail follows ===
Hi managers,
I have a strange problem installing Tru64 5.1B on a DS-10.
I am in the process of adapting an installation procedure based on the clone installation feature to the version 5.1B, and so far I had performed MANY such installations of 5.1B on this particular machine as well as others.
However, yesterday I downloaded the aggregate patch kit 0002 for 5.1B (which was released on 14 May 2003), and installed it on that particular machine (ALL patches).
Things were apparently fine - the patches installed OK and the machine rebooted OK.
Then later shut it down to begin a fresh installation for testing. The installation went through the post-OS-install configuration stage, and the subsequent reboot. Then it failed to single user mode with the following messages while trying to mount the filesystems (I type them below, they may not be 100% exact but maybe it is sufficient for someone to identify the cause):
(for information, a is root partition, g is /usr, d is /usr/users, e is private /locrec partition)
----- begin boot error msg
/dev/disk/dsk0g : No such file or directory
BAD DISK NAME /dev/disk/dsk0d
Device Naming: first boot initialization . . .
cluster/members/{memb}/etc/cfginfo
.
. (healthy-looking output omitted)
.
dsfmgr: ERROR: cannot open and read file /etc/dfsc.dat : Bad status file/data format
dsfmgr: ERROR: cannot open and read file /etc/dfsl.dat : Bad status file/data format
bcheckrc : Device Naming failed boot configure or verify.
Please correct the problem and continue or reboot.
----- end boot error msg : the machine was in single user mode
..... I decided to do another bcheckrc to investigate further. It also returned with the following errors:
----- begin bcheckrc errors (reconstructed from written notes - may not be exact format):
Checking device naming:
dsfmgr: ERROR: reading cluster file, line 5:
V: 1.1 V5.1B (REV. 2650) <yesterday's date>
dsfmgr: ERROR: reading local file, line 3:
V: 1.1 V5.1B (REV. 2650) <yesterday's date>
/dev/disk/dsk0a : No such file or directory
/dev/disk/dsk0g : No such file or directory
BAD DISK NAME /dev/disk/dsk0g
invalid device or cannot be opened
/dev/disk/dsk0g : No such file or directory
BAD DISK NAME /dev/disk/dsk0d
invalid device or cannot be opened
/dev/disk/dsk0g : No such file or directory
BAD DISK NAME /dev/disk/dsk0e
invalid device or cannot be opened
----- end bcheckrc errors
The devices in /dev/disk/dsk0* exist, and the files /etc/df*.dat are also there and seem readable enough using cat.
I have not encountered this problem on the other machines I use for testing, therefore my initial assumption that it is somehow a result of installing the patch kit.
Does anyone have any solid ideas what might have caused this problem, and what the best way would be to fix it?
Kind regards,
Michael Bütow
========================================================
Michael Bütow Phone: (49) 721-9497221
COMSOFT GmbH Fax: (49) 721-9497129
Wachhausstr. 5a WWW: http://www.comsoft.de
D-76227 Karlsruhe, Germany
========================================================
This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 10:49:23 EDT