How long after upgrade do you have to wait to access S160 via web gui again?

[keithsauer507]

Did the upgrade on an S160 to 7.5.2-303 about 9 AM.  Clicked the restart option at the end of the upgrade which is supposed to reboot the appliance.  Put a ping -t on the appliance to watch for reboot (packets should drop and then come back when its back up).  Thing is ping never fails, so its like it never rebooted.  HOWEVER web gui and SSH are not accessible even now as of 1:05 PM.  TAC says try a console cable.  There is no console port on here.  There is a serial port though. I connected a cisco console cable to this serial port, and the other end patched into the patch panel.  At a spare port at my desk I took another cisco console cable plugged it in there, and then the serial end into a usb/serial converter which claims its COM6.  But in Putty connecting to COM6 I get nothing.

Is it safe to pull the plug for a few seconds and then plug it back in and turn it on?  There's no way for me to access it, so I don't know what else to do.

[keithsauer507]

I found a different serial cable and connected it to a server that's in the same rack, then remoted to that server to check it.  But this is after giving up and hard power cycling the S160 and seeing it came back up fine no issues, system upgraded.

Its on 7.5.2-304.

I see 7.7.0-725 is available but I read there is a bug with that version causing high cpu usage on S160 so I will pass for now.  Besides that does anyone know what the latest async os for the S160 is now or will be?  Will 8.0 releases make it to the S160 with the cpu usage bug from 7.7 fixed?

[Vance Kwan · Accepted solution]

This is a known issue on the S160 model.  After the upgrade, when you click the button to reboot, it starts shutting down services to prepare for a graceful reboot.  Some services hang (but the service for the GUI already stopped).  You'll need to do a hard reset on the appliance by holding the power button for several seconds, then powering it back on.  After you do a hard reset, it's common for the RAID status to go to Sub-Optimal.  This means the RAID is rebuilding due to the hard reset and should revert back to Optimal in about 6 hours or so.

[keithsauer507]

Thank you.  My support contact didn't know that.  It took too long for them to get back to me about helping out getting a serial cable working, so I ended up doing just that.

Thanks for the confirmation.

[ashaw216]

This issue is not limited to the S160. I upgraded an S170 this past Friday from 7.7.0-725 to 7.7.0-757 and I had the same problem. I had to drive into work to manually press the button. This really needs to be fixed. I was only 25 minutes away but some folks aren't so lucky.