3PAR StoreServ Storage
cancel
Showing results for 
Search instead for 
Did you mean: 

Trying to update from 3.3.1.215 (GA)+P01,P02,P04,P12,P20,P33 to 3.3.1.410-MU2

 
SOLVED
Go to solution
Highlighted
Occasional Visitor

Trying to update from 3.3.1.215 (GA)+P01,P02,P04,P12,P20,P33 to 3.3.1.410-MU2

HELP!!!  I am trying to update a 3PAR 3.3.1.215 (GA)+P01,P02,P04,P12,P20,P33 but I am receiving this error message during the System Readiness Checks:

 

Check Node Disk Free Space

Failed

  1. check_free_space: free space is too low.
    Node0: /dev/sda7 17G 13G 3.7G 77% /common (min=5120 MB)
    Node2: /dev/sda7 17G 12G 4.3G 73% /common (min=5120 MB)
    Node3: /dev/sda7 17G 12G 4.0G 76% /common (min=5120 MB)
    Contact your support organization.

 

I am assuming that this error is referring to the internal HDD on each node but I do not know how to free up the space needed.  Yes, this 3PAR is out of warranty so I am asking anyone for help.  I cannot do anything that will compromise the data on the existing VVs.

 

Thank you all in advance and if you need more information, I am happy to oblige. 

James
HPE SDCG
5 REPLIES 5

Re: Trying to update from 3.3.1.215 (GA)+P01,P02,P04,P12,P20,P33 to 3.3.1.410-MU2

I don't think you can do it by yourself without taking HPE support help. Need to free up space from each node /common folder but from root login only. Any 3PAR OS update or Patch update HPE support use this folder to dump files and execute update. So need to delete all old files which are already installed in this 3PAR. That will make space for new files.

 

Hope this helps!
Regards
Subhajit

I am an HPE employee

If you feel this was helpful please click the KUDOS! thumb below!

***********************************************************************************


I work for HPE
Accept or Kudo
Highlighted
Acclaimed Contributor
Solution

Re: Trying to update from 3.3.1.215 (GA)+P01,P02,P04,P12,P20,P33 to 3.3.1.410-MU2

As a quick solution you may consider a node-to-node rescue and see if it helps (it certainly will) using the startnoderescue command.


Hope this helps!
Regards
Torsten.

__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.

__________________________________________________
No support by private messages. Please ask the forum!

If you feel this was helpful please click the KUDOS! thumb below!   
Highlighted
Occasional Visitor

Re: Trying to update from 3.3.1.215 (GA)+P01,P02,P04,P12,P20,P33 to 3.3.1.410-MU2

Thank you I will try this.

 

Since Node1 is not in a failing state and I want Nodes 0, 2, and 3 to match Node 1.... What would be the syntax?

The help for this command is a little vague.

James
HPE SDCG
Highlighted
Occasional Visitor

Re: Trying to update from 3.3.1.215 (GA)+P01,P02,P04,P12,P20,P33 to 3.3.1.410-MU2

The node rescue worked, thank you very much for your help!!

James
HPE SDCG
Highlighted
Honored Contributor

Re: Trying to update from 3.3.1.215 (GA)+P01,P02,P04,P12,P20,P33 to 3.3.1.410-MU2

Before doing a complete Noderesue, check if there are only too many Updates Staged:

upgradesys -liststaged -full

upgradesys -unstage <package>

This was an easy fix for me.


======================
That was not planned in this way.