Forum Discussion

Nimbostratus

Nov 16, 2015

Failed upgrade from 11.6.0 >> 12.0.0

I am failing an upgrade from 11.6.0 >> 12.0.0 with the following error.

error: result: info: mount: proc already mounted or /mnt/tm_install/19632.iYk0K0/proc/busy info: mount: according to mtab, proc is already mounted on /mnt/tm_install/19632.iYk0K0/proc Could not access configuration destination;

upgrade screen: Boot Location: HD 1.1 >> HD 1.2 Product: BIG-IP Version: 11.6.0 >> 12.0.0 Build: 0.0.401 >> 0.0.606 Install Configuration: Yes Source Volume: HD 1.2:12.0.0

application delivery

BIG-IP

LTM

Brad_Parker_139
Nov 16, 2015
Looks like the problem is you have chosen your new v12 volume as the source on the config install. "Install Configuration: Yes Source Volume: HD 1.2:12.0.0". HD 1.1 should be the source in your case.

nathe
Cirrocumulus
Nov 16, 2015
k2networks,

What about if you select No to "Install Configuration"? Does it then boot up fine? If this works then you could boot back into the 11.6.0 volume and use the cpcfg command to copy the configuration to the new volume. See Using the cpcfg command to copy a configuration from one boot location to another

If it doesn't boot up using the Activate screen then I'd drop into the CLI and execute the command
reboot volume 1.2

Hope this helps,

N
Brad_Parker
Cirrus
Nov 16, 2015
Looks like the problem is you have chosen your new v12 volume as the source on the config install. "Install Configuration: Yes Source Volume: HD 1.2:12.0.0". HD 1.1 should be the source in your case.
- nathe
  Cirrocumulus
  Nov 16, 2015
  Great spot Brad!
- k2networks_2342
  Nimbostratus
  Dec 01, 2015
  Thanks for the answer this in combination with the other comment helped us get the install to work.
Brad_Parker_139
Nacreous
Nov 16, 2015
Looks like the problem is you have chosen your new v12 volume as the source on the config install. "Install Configuration: Yes Source Volume: HD 1.2:12.0.0". HD 1.1 should be the source in your case.
- nathe
  Cirrocumulus
  Nov 16, 2015
  Great spot Brad!
- k2networks_2342
  Nimbostratus
  Dec 01, 2015
  Thanks for the answer this in combination with the other comment helped us get the install to work.