Probs upgr 5.0.4 to 5.0.5
Adrian Walsh
We are trying to upgrade a 5.0.4 machine to 5.0.5 using the "upgrade"
option. The fresh install option is not really a good one as the HD only
has a single partition.
When we try the upgrade option, the install process stops about fifteen
minutes into the install.
The install screen shows the "flashing asterisks" at the top. The status
line on the install screen mentions that it is running cqs, and the
progress bar indicates 3 asterisks and zero percent. I can switch to
console 3 (Alt+F3) and the system still responds. The last line in the
install.log states that "cqs running OS_DOC in with IQM_SAVE
FOR_LOCAL_CLIENT TRUE_CLIENT_ROOT UPGRADE ...".
I also noticed I cannot access the cdrom - which the log states is
mounted on /hdFS/mnt. And if I try to mount it, I get the response
"device busy".
Anyone have any ideas?
Please cc: to phe...@optusnet.com.au (I will be watching tonight!)
TIA,
Pat Heuvel
Bill Vermillion
Adrian Walsh <all...@internex.net.au> wrote:
>We are trying to upgrade a 5.0.4 machine to 5.0.5 using the
>"upgrade" option. ...
>When we try the upgrade option, the install process stops about fifteen
>minutes into the install.
So how long did you wait. On a slow machine I had to upgrade it
finally finished about 5 hours later.
Since you didn't mention hardware I just throw this suggestion out
in case you are using a computationally challenged machine.
--
Bill Vermillion bv @ wjv.com
Adrian Walsh
Bill Vermillion wrote:
> In article <3848F782...@internex.net.au>,
> Adrian Walsh <all...@internex.net.au> wrote:
> <..>
> So how long did you wait. On a slow machine I had to upgrade it
> finally finished about 5 hours later.
>
About one hour was the longest I waited.
> Since you didn't mention hardware I just throw this suggestion out
> in case you are using a computationally challenged machine.
>
Sorry: No-name Intel P166, 80meg RAM, 2940UW, 4.3G HDD
> --
> Bill Vermillion bv @ wjv.com
Thanx for the response!
Regards,
Pat
Pat Heuvel
A solution!
I set up a few links and got ps working. I was then able to find the
install process.
The install process had a child process which was a grep with a single
argument. This meant, of course that grep was waiting for input from
stdin! Having nothing else to lose, I killed the grep - rustle, rustle
(disk activity), silence. Checked ps again, a second grep. Killed that
one, more disk activity, and the install was away...
The two greps searched for (can't remember the exact) text in the
Netscape and Atlas installs, respectively. These products were not used,
nor were they installed at the site. So that was it!
Thanx to anyone who turned the grey matter in contemplation, and
especially to Bill for his response.
Regards,
Pat
+---------------------------------------------------------+
+ "Logic clearly dictates, that the strokes of the many +
+ outweigh the strokes of the two..." +
+ (Apologies to Mr Spock) +
+---------------------------------------------------------+
Tony Lawrence
> A solution!
>
> I set up a few links and got ps working. I was then able to find the
> install process.
>
> The install process had a child process which was a grep with a single
> argument. This meant, of course that grep was waiting for input from
> stdin! Having nothing else to lose, I killed the grep - rustle, rustle
> (disk activity), silence. Checked ps again, a second grep. Killed that
> one, more disk activity, and the install was away...
Actually, rather than celebrating your success, you should
be worrying about what might be screwed up on your system.
As you illustrated, the IPU can do stupid things when it
doesn't find what it expects. In the case of not finding
Netscape and Atlas, it apparently screws up by hanging with
an empty grep. So you fixed that, but what other
assumptions lurk in the IPU and what happens when the
assumptions aren't valid? Is it noticeable failure as in
this case or perhaps something more subtle that will mess
you up later? You don't know, and either does anyone else,
and that includes the engineers that wrote it.
Fresh installs are ALWAYS a better idea, period.
--
Tony Lawrence (to...@aplawrence.com)
SCO articles, help, book reviews, tests,
job listings and more : http://www.ApLawrence.com
Pat Heuvel
Tony Lawrence wrote
>
> Pat Heuvel wrote:
>
> > A solution!
<..>
(Actually, workaround is a more appropriate word)
>
<..>
>
> Fresh installs are ALWAYS a better idea, period.
>
Actually, we read through this newsgroup as well as the info on the SCO
page before doing this. I noticed your comment and wanted to check out
your website. For some reason, I couldn't access it!!
Anyway, one thing we considered was a fresh install (on the basis of
your recommendation), but ruled that out because everything was in the
root filesystem (I didn't set this machine up!!).
You may be right about being bitten in the bum later down the track, but
the first piece of advice I had given this client prior to the upgrade
was to get another (same size) hard drive, mirror the system onto that
and then do the upgrade. As it was, we needed to get the system
operational for the following morning and time was a-flyin'...
Thanx for the feedback, and the advice!
> --
> Tony Lawrence (to...@aplawrence.com)
> SCO articles, help, book reviews, tests,
> job listings and more : http://www.ApLawrence.com
By the way, I just checked and I can access your site now! (suitably
bookmarked)
Regards,
Pat Heuvel
--