| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 8554.1 | Been there... done that! | TROOA::ras007p01.srn.dec.com::dloten | semper ubi sub ubi | Fri Jan 24 1997 08:52 | 6 |
| The hitch is that v3.2F and probably G have a 'new' version of vdump (ie.
v4.0)... the v3.2C kit had v1.3... hence the version mismatch message.
During the upgrade, it should have saved the old vdump... copy it back or use
it in-place.
-doug
|
| 8554.2 | alternatively: use a V4.0 CD-rom vrestore | DOOSJE::HERTA | For something fulfilled this hour, loved, or endured | Fri Jan 24 1997 11:00 | 6 |
| Boot the system from the Digital UNIX V4.0 CD-ROM, go to system management
and vrestore from there.
Worked for us when we were cloning systems.
Herta
|
| 8554.3 | Thanks, and... | HGOVC::NANDAN | | Sun Jan 26 1997 00:19 | 14 |
|
Doug & Herta,
Thanks for your responses. I would feel that the customer should use
the version of 'vdump' & 'vrestore' that goes with 3.2C, since it is of
the 3.2x "flavour".
More worrying is, is there anything else which would show up a mismatch
or cause any other problems in AdvFS ? The reason is, I was surprised
that this happened after doing an usual upgrade.
Thanks in advance.
Nandan
|
| 8554.4 | Same here | EPS::CONNORS | | Wed Jan 29 1997 12:17 | 7 |
|
Same problem here .. only difference is that my system
was a 3.2G system build from the start and I received the
same error message found in .0 ... My next step is to try
booting from a V4.0 CD .. it's a good thing I have a 4.0 CD ..
I'm sure in every customer situation, this is not the case.
|
| 8554.5 | | DECWET::MARTIN | | Wed Jan 29 1997 16:46 | 2 |
| Take a look at DECWET::ADVFS_SUPPORT note 877.9 for more complete and detailed
information on this problem.
|
| 8554.6 | Thanks & please see 8662... | HGOVC::NANDAN | | Fri Jan 31 1997 02:37 | 8 |
|
Connors & Martin,
Thanks for the information on the problem.
Please see my note no 8662 herein which describes the entire problem.
Nandan
|