I'm receiving the same "No metadata files could be created" error that johnny5shared describes in this post but there are enough differences in other info reported there that a new topic seems warranted.
So here's my tale of woe. I'm in the process of upgrading my physical HDA server from Amahi 6 to Amahi 9. The last piece is to rebuild the greyhole storage pools. I have not installed the Greyhole UI app yet because I became quite nervous about the HDA OS Migration Guide and differences I noticed there in the greyhole setup. I'm in the same situation as johnny5shared when he said, "It's just that I stand to lose a lot of data if this isn't implemented properly...."
I decided to set up a Virtualbox VM, host-only network + NAT, so I could experiment and make sure I understood how share paths and the drive pools would be assigned. After over a couple dozen fresh Amahi 9 installs in vbox, I believe I have a reliable kickstart file that I can use to duplicate the setup. I am using the Greyhole UI on the VM. Basic VM stats: 1GB RAM, OS drive 8GB, what I hope will be the main drive for the landing zone is 1G, and three pool drives at 500MB each.
I made one manual tweak to an otherwise "normal" install using the Disk Wizard and Greyhole UI: in greyhole.conf I changed min_free from 10gb to 0gb (see https://www.greyhole.net/irc/ at timestamp 17:58:53) to stop the no-disk-space-available type messages.
What I think is the issue is that Greyhole UI is not creating the /gh subfolders and when the greyhole daemon doesn't find them, it spews out the "No metadata files could be created" error. I don't want to manually create them if I can avoid it -- I'm expecting the Disk Wizard and/or Greyhole UI to take the necessary steps. No files are getting duplicated as far as I can tell.
I know about manually adding a disk drive but just trying to get greyhole going with the disk wizard and automated steps has been almost too much already. Besides, I would think doing the wizard/automated steps would be preferable anyway.
I have not done anything to the mariadb files at all. I don't even know what all is in them. I'm blissfully unaware.
I know I need to (and do) stop samba and greyhole servers before I mess with this stuff.
I've had some contact with gboudreau about this, and after seeing the greyhole log, he wrote:
Output of gboudreau's script is here: http://ix.io/1PDnmkdir(/var/hda/drives/pooldisk3/gh/.gh_metastore_backup)
That seems to indicate the folder /var/hda/drives/pooldisk3/gh doesn't exist. The folders you specify as storage_pool_drive in greyhole.conf needs to exist.
Output of apaste --sysinfo is here: http://tinyurl.com/jqqb3hy
Other info requested by Greyhole Troubleshooting is here: http://tinyurl.com/zgs5sw8
generated by this frikkin' long command:
Code: Select all
( x="=======================================" ; echo -e "$x\nStatus of mariadb\n$x\n"; systemctl status mariadb ; echo -e "\n$x\nAmahi-greyhole version\n$x\n" ; rpm -q amahi-greyhole ; echo -e "\n$x\nfdisk output\n$x\n" ; fdisk -l ; echo -e "\n$x\nmysql query #1\n$x\n"; mysql -t -u root -phda -e "select * from disk_pool_partitions" hda_production ; echo -e "\n$x\nmysql query #2\n$x\n"; mysql -u root -phda -e "select concat(path, '/gh') from disk_pool_partitions" hda_production | grep -v 'concat(' | xargs ls -la 2>&1) | apaste