Re: Overwrite the O/S ?
From: Andreas Schulze (b79xan_at_gmx.de)
Date: 10/29/03
- Next message: Mike: "stopping nim?"
- Previous message: Scott Richardson: "Re: [Repost] Tivoli / Tivoli Enterprise Console"
- In reply to: R. Guzman: "Overwrite the O/S ?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Wed, 29 Oct 2003 23:22:15 +0100
"R. Guzman" <ralphguzman@earthlink.net> schrieb im Newsbeitrag
news:lPQnb.11247$FI2.364@newsread1.news.atl.earthlink.net...
> Hello all, does anyone know or can confirm if I can do the following.
>
> Can I overwrite O/S, AIX 4.3.3 using the preservation option when I do a
> install.
>
> The reason is, I have a problem box and it looks like there are numerous
> errors coming up.
> Therefore, I would like to overwrite the O/S, but keep the data and
> configuration on the box.
>
> Thanks for any help!
Hallo Ralph,
from what you write I feel that a new and complete overwrite installation
might help best. However you ask about overwriting the os and keeping the
configuration. So here are some corner stones you need to know. The name
'preservation install' is misleading. It will overwrite the complete
system's configuration including /var /usr and / ! All userdata in these
filesystems will be lost. Your /etc/hosts and others will be gone. So that
is probably not what you want. You could use /etc/preserve.list to name some
files that must not be overwritten but that implies that you know exactly
what to save. Furthermore this list must not become too big.
Thus I would recommend first installing the latest ML if you happen to be
downlevel. ML11 is several hundred megs of fresh binaries and appears as a
complete exchange of the os to me. It will not help if your problems are
caused by misconfiguration, though.
The second best solution might be to try a migration install as you
intended. However this usually works if version or release of the os is
different only. Unfortunately that is not the case as you are on 4.3 and you
want to stay on 4.3. You might fake the pad string to make the install
process think it is doing an upgrade but hey, that is not really for
beginners. So use this information at your own risk. Make sure you have got
a working backup before you start.
First check the pad string. It gives Version and Release, in this example
"4.3 pad string". Btw. what is said here applies for 5.1 and 5.2 also.
# lquerypv -h /dev/hd5 2A0 30
000002A0 31303333 37353233 35320000 00000000 |1033752352......|
000002B0 00000000 00000000 00000000 0000342E |..............4.|
000002C0 33207061 64207374 72696E67 3A402524 |3 pad string:@%$|
#
Or do a
# /usr/lpp/bosinst/blvset -d /dev/hdisk0 -g level
4.3
#
Check where the boot logical volume is
# lslv -m hd5
hd5:N/A
LP PP1 PV1 PP2 PV2 PP3 PV3
0001 0001 hdisk0 0001 hdisk2
#
It's on hdisk0 (and, mirrored, on hdisk2) Now change the pad string with the
blvset command.
# which_fileset blvset
/usr/lpp/bosinst/blvset bos.rte.bosinst 4.3.3.0
# /usr/lpp/bosinst/blvset -d /dev/hdisk0 -p level 4.2
Reboot and start from NIM or CD.
Again, the steps described will only activate the mere possibility to do a
migration install (e.g. the menu for migration install will be accessible)
but there is no guarantee that it will work out as you wish. It will in no
case correct problems with your config settings! Personally I still think
that a clean new install is the way to go because all the other
possibilities require much time for debugging.
HTH
Andreas
- Next message: Mike: "stopping nim?"
- Previous message: Scott Richardson: "Re: [Repost] Tivoli / Tivoli Enterprise Console"
- In reply to: R. Guzman: "Overwrite the O/S ?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
