If you have Ubuntu MAAS (Metal As A Service) and, like most of us, have a hard drive configuration that is over 2 TB, you will run into trouble deploying. At least that was the case for me. In our server room we have Dell R710's with 12TB's of storage (6, 2TB drives). For these systems, I have them configured in RAID 6 giving us 8TB of space. However, any time I deployed, it would fail. But there was never a problem with our R410's that have only 900GB of space. Also, I know that a 8TB deployment was possible, since we've been doing it with FUEL since Ubuntu 12. So what gives? Was there some sort of limitation mentioned that we overlooked? Not according to the troubleshooting guide [5].
What was/is the problem? Our Environment: We have:
Error message: Error: attempt to read or write outside of disk `hd0'. Entering rescue mode... grub rescue> Attempts: Fails:
Success!
Conclusion: I do not know why the larger (1GB) boot directory was critical but it has worked across all of our 710's while the others have failed. I hope this helps someone. I got the idea of the separate partitions from resource 3 below. Hopefully as MAAS matures more, this bug will work itself out, however, it has been noted since 2014, which is a bit concerning [4]. Resources: [1] . http://en.community.dell.com/techcenter/extras/w/wiki/2837.hdd-support-for-2-5tb-3tb-drives-and-beyond [2] . https://askubuntu.com/questions/495994/what-filesystem-should-boot-be [3] . https://askubuntu.com/questions/470823/ubuntu-14-04-lts-maas-boot-fails-on-fresh-install-on-a-dell-2950 [4] . https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1284196 [5] . https://docs.ubuntu.com/maas/2.1/en/troubleshoot-faq
Quick way to get the inventory of you host and write it to a file:
root@r6-410-1:/home/ubuntu# ansible all -i INVENTORY_FILE -m setup --tree /tmp/facts
This will print the inventory into terminal and write it into a file with the name of the file being the name of the machine listed in your inventory file. This could be either a FQDN or IP address. The file will be in JSON format as well for easy viewing. Enjoy!
Receiving an error like this:
root@r6-410-1:/home/ubuntu# ansible all -i tmp -m setup --tree /tmp/facts 192.168.6.29 | FAILED! => { "changed": false, "failed": true, "module_stderr": "Shared connection to 192.168.6.29 closed.\r\n", "module_stdout": "/bin/sh: 1: /usr/bin/python: not found\r\n", "msg": "MODULE FAILURE", "rc": 0 }
Go to your inventory file and add this:
ansible_python_interpreter=/usr/bin/python3 So your inventory file might look something like this now: 192.168.6.29 ansible_python_interpreter=/usr/bin/python3 |
AuthorJames Benson is an IT professional. Archives
August 2022
Categories
All
|