cancel
Showing results for 
Search instead for 
Did you mean: 

Appliance 5220 software fresh installation

demo4119
Level 6
Partner Accredited Certified

i have tried to fresh installing a new 5220 software version from 2.0.1 to 2.0.2.

Strange is that during the installation of the version 2.0.2 the progress wasnt shown on the monitor output.

But after the upgrade the server unable to bootup to operating system and it will always went to black screen after the symantec logo .

 

Is there a way to revert back the factory default ?

1 ACCEPTED SOLUTION

Accepted Solutions

demo4119
Level 6
Partner Accredited Certified

Appliance BIOS is booting to the wrong controller. We managed to found that the Controller bootup sequece is pointing to the wrong Raid group and caused this issue.

 

We have put it back to the correct boot up controller . Everything work fine.

View solution in original post

3 REPLIES 3

Sebastian_Baszc
Level 5
Partner Accredited Certified

Hey Mate,

 

If the operating system is screwed - you have 2 options:

 

1. If you have Linux skills - poke around, try the rescue mode and see if you can rescue it

2. This option is preferred - use the USB disk supplied with the appliance to rebuild the appliance to 2.0.1. Just plug it in, boot the appliance and it will get rebuilt. 

 

When you are upgrading from 2.0.1 to 2.0.2 you need to upload the rpm file (over 4GB) to the appliance after opening the share. Once it's done you need to verify the patch and finally apply the patch. During that procedure it will be displaying the progress in your SSH session or in the console (if connected to IPMI). If for some reasons the installer is stuck for longer than 20 min, log into the appliance using additional SSH session, cd to /tmp and check the install logs. Maybe the demo NBU license is expired.... ? 

 

 

Hope it helps. 

 

S

demo4119
Level 6
Partner Accredited Certified

thanks for check on that .

demo4119
Level 6
Partner Accredited Certified

Appliance BIOS is booting to the wrong controller. We managed to found that the Controller bootup sequece is pointing to the wrong Raid group and caused this issue.

 

We have put it back to the correct boot up controller . Everything work fine.