This post is more than 5 years old
2 Posts
0
2392
October 6th, 2017 04:00
ECS-CommunityEdition 3.0.0.2 installation failed with error "Total block storage available for ECS is less then 100GB (0GB reported by node)"
Expected Behavior
TASK [common_baseline_check : Common | Make sure block device(s) are at least 100GB] ***
TASK [common_baseline_check : Common | Make sure block device(s) are unpartitioned] ***
Actual Behavior / Output
TASK [common_baseline_check : Common | Make sure block device(s) are at least 100GB] ***
fatal: [10.251.59.197]: FAILED! => {"changed": false, "failed": true, "msg": "Total block storage available for ECS is less then 100GB (0GB reported by node)"}
Steps to Reproduce Behavior
I downloaded dellemc-ecsce-3.0.0.2-install-node-2.4.0-vm0.ova and got it deployed on an ESX6.5. I finished the pre-configuration by referring to http://ecsce.readthedocs.io/en/latest/installation/ECS-Installation.htmland ran $ step1... Then it kept complaining that there was no available block storage even though the size of hard disk 2 was 104 GB.
This CE is just killing me as I got too many errors while running the command step1. I've even tried to use thick vmdk and increased the size to 150GB but still no luck. The same error message persists anyway. I've tried to search by using Google but unfortunately no such information could be found.
The related install.log and deploy.yml files are attached at here.
I'm appreciated if anyone could figure out what's exactly happening with this issue. Thanks.
travis_wichert
16 Posts
0
October 9th, 2017 07:00
Hi Jackie,
I'm betting the issue is the second block device is /dev/sdb rather than /dev/vda. Check to see what it actually shows up as under your virtualization environment and then make sure the "ecs_block_devices:" lists only contain valid block devices.
For example, change this:
ecs_block_devices:
- /dev/vda
To this:
ecs_block_devices:
- /dev/sdb
Let me know if that resolves the issue. Thanks!
Jackie_Liu
2 Posts
0
October 9th, 2017 16:00
Hi Travis,
Thanks for the reply. That fixed the issue.
BTW. now I'm wondering why we can't have this instruction into the get-started guide as this took me two days in the darkness (I'm a Windows guy).
TA.
travis_wichert
16 Posts
0
October 10th, 2017 08:00
I'll see what we can do.
felipe.roque
1 Message
0
July 24th, 2018 19:00
Almost 1 year later and the same problem with the new released version... just got here because of the error with /dev/vda.....
thanks for the solution... but need to fix the problem in the document or in the OVA.