Forum Discussion
fail to provision ASM
hi
We have encountered a strange situation with one of our VE's:
When Trying to provision ASM, the provisioning fails due to insufficient space to install / create mysql. - The log (mysql.out) stated that there were 2GB missing.
We have extended the VM's "physical disk" by 20GB and still we got the same… BIG-IP simply does not acknowledge the new disk size. any Idea?
5 Replies
- JRahm
Admin
you'll need to attach a new disk of the right size to the BIG-IP VE and build from .iso. make sure create a full archive and then also that you don't blow the nics away in the process or you'll end up talking to support to allow a move from one VE to another.
Detailed instructions on increasing disk size.
- Yalkrif_99781
Nimbostratus
thanks for the answer, we attached new disk but cant do the install on it only on the existing HD that have two pretation , do you know how we can change the boot HD to be the second one?
- JRahm
Admin
the instructions above should clarify that. The image will be rebuilt on your new disk, but initial boot should be to the BIG-IP .iso file.
- Yalkrif_99781
Nimbostratus
i can see only HD1 and his Pretentions (i can choose 1.1 or 1.3) i cant choose the seconed HD (HD2) that i have add on this VE, i can see him on disk managment page but i cant choose it on install page
- JRahm
Admin
you have to do it from the virtual console within your hypervisor. The new disk should be the only disk attached.Please re-read steps 4-12 in the instructions I linked above.
Help guide the future of your DevCentral Community!
What tools do you use to collaborate? (1min - anonymous)Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com