Forums » Help »

Update from 3.1.0 to 3.1.3

Added by Doug Dalton 9 months ago

When I updated from 3.10 to 3.13 the nexenta box disconnected me, and it looks like the update didnt complete, what is the best way to proceed?

nmc@storage:/$ setup appliance upgrade Cleanup upgrade caches (note: cleanup is generally not required and can be skipped in most cases; if you say Yes, prepare to wait for software upgrade to complete a bit longer) ? Yes

You are about to upgrade the appliance software. Please be advised that by executing this operation you agree to be bound by the terms of the product license available at http://www.nexenta.com/nexentastor-licenses. This operation may take some time to check with the remote appliance's software repository. Proceed? (yYes Checking repository sources. Please wait...

Found new upgrades! Verifying upgrades... Trying to gain exclusive access to the appliance. This operation may take up to 30 seconds to complete. Please wait... Failed to gain exclusive access, operation timed out.


Replies

RE: Update from 3.1.0 to 3.1.3 - Added by Doug Dalton 9 months ago

I am very nervous that a system reboot will crash

RE: Update from 3.1.0 to 3.1.3 - Added by Derek Glover 9 months ago

Have you made any system checkpoints you could alternatively boot into? (always recommended before Upgprades)

RE: Update from 3.1.0 to 3.1.3 - Added by Doug Dalton 9 months ago

I think it made one when I did :

setup appliance upgrade

RE: Update from 3.1.0 to 3.1.3 - Added by Doug Dalton 9 months ago

Can i clear the lock and rerun

setup appliance upgrade

or would that damage anything?

RE: Update from 3.1.0 to 3.1.3 - Added by Derek Glover 9 months ago

You should be able to clear the lock. I don't have the steps for that myself, I imagine it is apt's lock. I can check with the devs for that. If you know how, go for it.

Alternatively, you can reboot and select the recently created Checkpoint, and retry the upgrade from there.

RE: Update from 3.1.0 to 3.1.3 - Added by Doug Dalton 9 months ago

This is a hosted server so I would have to travel to my colo to do this, so if I can avoid that I would like to, any word on if clearing the lock is ok todo and where the lock file is?

Regards, Doug

RE: Update from 3.1.0 to 3.1.3 - Added by Roman Strashkin 9 months ago

Try to restart NMS and re-run upgrade process

RE: Update from 3.1.0 to 3.1.3 - Added by Derek Glover 9 months ago

Doug, had a chance to try this yet?

RE: Update from 3.1.0 to 3.1.3 - Added by Doug Dalton 9 months ago

I am at a remote location so how can I reboot into a previous checkpoint without being at the console? can I list the checkpoints or is it just safe to reboot?

RE: Update from 3.1.0 to 3.1.3 - Added by Derek Glover 9 months ago

You don't need to reboot for this. Roman's suggestion would be to run this via the root console: svcadm restart nms

Older FAQ entry regarding this here: http://www.nexenta.com/corp/nms-and-dbus-restart-steps

RE: Update from 3.1.0 to 3.1.3 - Added by Doug Dalton 9 months ago

how do I check to be sure it has a previous checkpoint or list checkpoints?

RE: Update from 3.1.0 to 3.1.3 - Added by Derek Glover 9 months ago 

nmc@derekpro:/$ setup appliance checkpoint show
ROOTFS          CREATION           CHECKPOINT-TYPE  CURRENT DEFAULT VERSION
rootfs-nmu-001  Jul  9 15:29 2012  rollback         No      No      3.1.3
rootfs-nmu-000  Jun 20 17:14 2012  initial          Yes     Yes     3.1.3