Hello,
I logged this call through my support partner and got some advice from Aruba (slightly clarified by me):
1. Power cycle the controller and break into the CPBoot by hitting the enter key on startup (console access).
=> The one with cpboot> as the prompt - so the second one on a 7220.
2. Format Partition 0:2, which is where the configuration file is stored:
cpboot> format 0:2
Format will erase everything on the internal flash's partition 2.
Are you sure you want to continue (y/n)?y
Formating.........
Done
=> This took almost an hour for me on a 7220 and printed screens and screens of hashes.]
3. Reload the controller and follow the start-up wizard to regain IP connectivity to the controller.
=> In my case, this printed messages about the filesystem having errors, but the ArubaOS boot process rebuilt the filesystem and reinitialised everything without input.
4. Verify the images in the two partitions by issuing the following command:
(Aruba) #show image version
=> This command - and 'show version' - displayed a large warning about the bootloader needing to be reinstalled as it had been blanked. This just required a reinstall of the OS image as per a normal upgrade - I just installed the same OS image in the other partition and it resolved it.
This operation removed all my licences, but I was just able to re-enter the activation keys (which I got from the licensing website again) and it all worked peachy.
I can't vouch for this being safe on all controllers, although the example I was sent was slightly different (referring to 'internal flash' although my 7220 reported 'eUSB flash') - so it's possible it will brick another model. However, it did fix things. I would check with your support partner first, though!
- Bob
#7220