× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  1.  Home
  2. MIDRANGE-L
  3. July 2017

Re: VIOS update failure

Smile!

No back up/recovery guide, just makesysb, which you're right is awful. Yes dual VIOS. The thing is still working too, we just can't apply any updates until the commit is done. Can't commit until the update is done. Depending on what IBM comes up with I might have to rebuild it which would be too much like work.

I thought I could use installb to apply the fixes but that's not working either.


Jim Oberholtzer
Agile Technology Architects
Office: 414-433-4363
Cell: 414-915-1445
Sent from iPad

"I've learned that courage is not the absence of fear, but the triumph over it. The brave man is not he who does not feel afraid, but he who conquers that fear". -- Nelson Mandela



On Jul 27, 2017, at 1:36 PM, Rob Berendt <rob@xxxxxxxxx> wrote:

Hopefully you have a redundant VIOS lpar serving up your ethernet with a
shared ethernet adapter. If so, it would be sweet if you did work through
this with IBM in order so both parties can gain knowledge in case it hits
someone else (like me).

Otherwise, how much is there to vios? I would suspect someone like you
sets up a new VIOS lpar on a somewhat regular basis. So recreate from
scratch using the newer version. As I'm kind of discovering this week,
delete and rebuild seems to be a popular path.

And, who backs up their VIOS to tape? Gee, a bare metal restore of that
is probably out of the realm for most mortals. Is there such a thing as
"Backup and Recovery Guide" for that?


Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





From: Jim Oberholtzer <midrangel@xxxxxxxxxxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 07/27/2017 02:24 PM
Subject: VIOS update failure
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>



I updated a VIOS install to 22410, but the PC that was doing the update
lost connectivity in the middle of the updatios command leaving it
incomplete.

After trying a comit, the log has the following:

installp -e install.log -c all
+-----------------------------------------------------------------------------+
Pre-commit Verification...
+-----------------------------------------------------------------------------+
done
FAILURES
--------
Filesets listed in this section failed pre-commit verification
and will not be committed.

Requisite Failures
(Commit Operation)
------------------
SELECTED FILESETS: The following is a list of filesets that you asked
to
commit. They cannot be committed until all of their requisite filesets
are also committed. See subsequent lists for details of requisites.

devices.ethernet.mlx.diag 6.1.9.100 # RoCE Converged Network
Adapt...
devices.pciex.b31503101410b504.diag 6.1.9.100 # RoCE Host Bus Adapter
Diagnostics (b31503101410b504)
devices.pciex.b31507101410e704.diag 6.1.9.100 # RoCE Host Bus Adapter
Diagnostics (b31507101410e704)
devices.pciex.b31507101410eb04.diag 6.1.9.100 # RoCE Host Bus Adapter
Diagnostics (b31507101410eb04)
devices.pciex.b315506714101604.diag 6.1.9.100 # RoCE Host Bus Adapter
Diagnostics (b315506714101604)
devices.pciex.b315506714106104.diag 6.1.9.100 # RoCE Host Bus Adapter
Diagnostics (b315506714106104)
devices.pciex.b3155067b3157265.diag 6.1.9.100 # RoCE Host Bus Adapter
Diagnostics (b3155067b3157265)
devices.pciex.b3155067b3157365.diag 6.1.9.100 # RoCE Host Bus Adapter
Diagnostics (b3155067b3157365)

MISSING REQUISITES: The following filesets are requisites of one or
more
of the selected filesets listed above. They are not currently installed
on the system. You should install these requisites to ensure that the
selected filesets function correctly. You MUST install these requisites
before committing the selected filesets.

devices.ethernet.mlx.rte 6.1.9.100 # Fileset Update
devices.pciex.b31503101410b504.rte 6.1.9.100 # Fileset Update
devices.pciex.b31507101410e704.rte 6.1.9.100 # Fileset Update
devices.pciex.b31507101410eb04.rte 6.1.9.100 # Fileset Update
devices.pciex.b315506714101604.rte 6.1.9.100 # Fileset Update
devices.pciex.b315506714106104.rte 6.1.9.100 # Fileset Update
devices.pciex.b3155067b3157265.rte 6.1.9.100 # Fileset Update
devices.pciex.b3155067b3157365.rte 6.1.9.100 # Fileset Update

<< End of Failure Section >>

FILESET STATISTICS
------------------
8 Selected to be committed, of which:
8 FAILED pre-installation verification
----
0 Total to be committed


Pre-installation Failure/Warning Summary
----------------------------------------
Name Level Pre-installation Failure/Warning
-------------------------------------------------------------------------------
devices.pciex.b3155067b31 6.1.9.100 Requisite failure
devices.pciex.b3155067b31 6.1.9.100 Requisite failure
devices.pciex.b3155067141 6.1.9.100 Requisite failure
devices.pciex.b3155067141 6.1.9.100 Requisite failure
devices.pciex.b3150710141 6.1.9.100 Requisite failure
devices.pciex.b3150710141 6.1.9.100 Requisite failure
devices.pciex.b3150310141 6.1.9.100 Requisite failure
devices.ethernet.mlx.diag 6.1.9.100 Requisite failure


END:Thu Jul 27 07:52:53 2017:072712525317


Clearly the Ethernet code did not update. Now VIOS will not let me SLIP
install to fix it claiming I need to commit all the software first, but in
order to commit, I need to install this software.

Any ideas how to fix this? IBM is giving me the we'll call you back in
this century routine so support is nearly worthless, not to mention the
guy
in a non-US city knows less about VIOS than I do.


Jim Oberholtzer
CEO/Chief Technical Architect
Agile Technology Architects
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate link: http://amzn.to/2dEadiD

As an Amazon Associate we earn from qualifying purchases.

This thread ...
Replies:
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.