I am attempting to deploy a new single node 9.7 OnTap Simulator on vSphere v6.7. We deployed it successfully, but when it deployed, it defaulted to creating 14 x 1Gb disks with the root aggregate. We have enough space allocated that I can have 56 x 4Gb disks (that is what we used for the previous 9.5 deployment).
Can anyone tell me why this is hanging? Or, am I just complicating this entire process? Is there a way to get it to deploy using the 4Gb disks? Or, a way to wipe the config from the boot menu and have it redeploy with 4Gb disks?
The drives aren't really defined in VMWare. In VMWare, it shows that there are 4 hard disks:
Hard disk 1: 1.89 Gb Hard disk 2: 1.50 Gb Hard disk 3: 4.75 Gb Hard disk 4: 230.70 Gb
I'm not sure that we can change these. The gentlemen that did the OVA install said that this was just how the OVA deployed the disks. He didn't choose anything.
I tried doing the reboot and the selected option 4 from the boot menu (there is no 4a), and it re-initializes the disks, but it creates the root aggregate on the small 1Gb disks again, even though there are 4Gb disks available.
Thanks, @derekb. I did delete all the disks, but I didn't remove the reservations or do the echo command. Now, the simulator won't boot at all (see attached screenshot). Would I have avoided this if I hadn't missed those two steps? We are going to redeploy the OVA tomorrow, so I'm hoping I can give it another try.
I was hesitant to delete the disks that had the root aggregate on them because I was afraid something like this would happen. But, it just would not let me move the root aggr to a new aggregate, so I deleted them as a last ditch effort. Obviously that didn't work out 😀. If you delete ALL of the simulated disks, how does it have any OS to boot from?