Complete newbie clueless question here:
I have a clean new install of Amahi 8 on Fedora 23. I have no experience of either, so I have done my best to follow the wiki instructions.
I have four hard drives, two 100Gb ones, two 1.5Tb ones, all formatted as Ext4. One of the two 100Gb drives has the /, /boot and /home partitions on it, the others have nothing. I added the three empty drives with Disk Wizard and formatted them all. I purchased Greyhole UI and added the three empty drives to the Greyhole pool and then went into the Drive Pooling > Shares tab and ticked all the shares I want to add to the pool.
I then downloaded Greyhole log viewer and found that it is listing the same error over and over again:
ERROR initialize: You have no 'storage_pool_drive' defined. Greyhole can't run.
CRITICAL initialize: Config file parsing failed. Exiting.
I have noticed that when I go into Settings > Servers, MariaDB Server is showing as stopped, and when I click on Start, nothing happens. Greyhole UI Server is also shown as stopped, and although when I click on it, it starts up, it stops again shortly after.
Any ideas of where things have gone wrong?
SOLVED: Greyhole Error: no 'storage_pool_drive' defined.
-
Camperdownfamily
- Posts: 44
- Joined: Tue May 31, 2016 4:29 pm
Re: Greyhole Error: no 'storage_pool_drive' defined.
Not being picky, but it's Amahi 9.I have a clean new install of Amahi 8 on Fedora 23.
Did you select the status tab in the greyhole-ui App and choose run FSCK? Recommend you check the Greyhole Troubleshooting page in the wiki. Looking at the /etc/greyhole.conf might help as well.Greyhole UI Server is also shown as stopped, and although when I click on it, it starts up, it stops again shortly after.
See the Amahi 9 Troubleshooting page in the wiki. This is a known bug.I have noticed that when I go into Settings > Servers, MariaDB Server is showing as stopped
ßîgƒσστ65
Applications Manager
My HDA: Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz on MSI board, 16GB RAM, 1TBx1+2TBx2+4TBx2
Applications Manager
My HDA: Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz on MSI board, 16GB RAM, 1TBx1+2TBx2+4TBx2
-
Camperdownfamily
- Posts: 44
- Joined: Tue May 31, 2016 4:29 pm
Re: Greyhole Error: no 'storage_pool_drive' defined.
Thanks for the quick reply bigfoot65.
Apologies for the typo - I meant Amahi 9.
I have clicked on the button to run FSCK and I just get the rotating circle of dots indicating activity for a moment and then it goes back to a red button.
Going through the Greyhole trouble shooting, the details are:
1. Version numbers
4.4.9-300.fc23.x86_64
samba-4.3.9-0.fc23.x86_64
amahi-greyhole-0.9.67-1.x86_64
2. the two conf files are at:
http://paste.fedoraproject.org/373315/78318514/
http://paste.fedoraproject.org/373318/47833281/
3. The result of the three commands are:
Mount
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
devtmpfs on /dev type devtmpfs (rw,nosuid,size=2015536k,nr_inodes=503884,mode=755)
securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /run type tmpfs (rw,nosuid,nodev,mode=755)
tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755)
cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/usr/lib/systemd/systemd-cgroups-agent,name=systemd)
pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer)
cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices)
cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)
cgroup on /sys/fs/cgroup/hugetlb type cgroup (rw,nosuid,nodev,noexec,relatime,hugetlb)
cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls,net_prio)
cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset)
cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory)
cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,nosuid,nodev,noexec,relatime,perf_event)
cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio)
cgroup on /sys/fs/cgroup/pids type cgroup (rw,nosuid,nodev,noexec,relatime,pids)
configfs on /sys/kernel/config type configfs (rw,relatime)
/dev/sda3 on / type xfs (rw,relatime,attr2,inode64,noquota)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=31,pgrp=1,timeout=0,minproto=5,maxproto=5,direct)
hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime)
mqueue on /dev/mqueue type mqueue (rw,relatime)
tmpfs on /tmp type tmpfs (rw)
debugfs on /sys/kernel/debug type debugfs (rw,relatime)
/dev/sda5 on /home type xfs (rw,relatime,attr2,inode64,noquota)
/dev/sda1 on /boot type ext4 (rw,relatime,data=ordered)
tmpfs on /run/user/0 type tmpfs (rw,nosuid,nodev,relatime,size=404740k,mode=700)
tmpfs on /run/user/1000 type tmpfs (rw,nosuid,nodev,relatime,size=404740k,mode=700,uid=1000,gid=100)
fdisk -1
fdisk: cannot open /dev/sr0: Permission denied
fdisk: cannot open /dev/sda: Permission denied
fdisk: cannot open /dev/sdb: Permission denied
fdisk: cannot open /dev/sdd: Permission denied
fdisk: cannot open /dev/sdc: Permission denied
df -h
Filesystem Size Used Avail Use% Mounted on
devtmpfs 2.0G 0 2.0G 0% /dev
tmpfs 2.0G 0 2.0G 0% /dev/shm
tmpfs 2.0G 696K 2.0G 1% /run
tmpfs 2.0G 0 2.0G 0% /sys/fs/cgroup
/dev/sda3 50G 1.7G 49G 4% /
tmpfs 2.0G 32K 2.0G 1% /tmp
/dev/sda5 46G 33M 46G 1% /home
/dev/sda1 477M 76M 373M 17% /boot
tmpfs 396M 0 396M 0% /run/user/0
tmpfs 396M 0 396M 0% /run/user/1000
greyhole --stats
No response - it just returned to the command prompt.
mysql -u root -phda -e "select * from disk_pool_partitions" hda_production
+----+----------------------------------------+--------------+---------------------+---------------------+
| id | path | minimum_free | created_at | updated_at |
+----+----------------------------------------+--------------+---------------------+---------------------+
| 1 | /var/hda/files/drives/Greyhole Pool #1 | 10 | 2016-06-01 08:51:10 | 2016-06-01 08:51:10 |
| 2 | /var/hda/files/drives/Greyhole Pool #2 | 10 | 2016-06-01 08:51:11 | 2016-06-01 08:51:11 |
| 3 | /var/hda/files/drives/Greyhole Pool #3 | 10 | 2016-06-01 08:51:12 | 2016-06-01 08:51:12 |
+----+----------------------------------------+--------------+---------------------+---------------------+
mysql -u root -phda -e "select concat(path, '/gh') from disk_pool_partitions" \
hda_production | grep -v 'concat(' | xargs ls -la | pastebinit
initiall came up with "ERROR 1046 (3D000) at line 1: No database selected"
and then uploaded some details to http://paste.fedoraproject.org/373325/46478420/
greyhole --view-queue
No response - it just returned to the command prompt.
tail /var/log/greyhole.log
Jun 01 13:33:26 ERROR initialize: You have no 'storage_pool_drive' defined. Greyhole can't run.
Jun 01 13:33:26 CRITICAL initialize: Config file parsing failed. Exiting.
Jun 01 13:33:27 ERROR initialize: You have no 'storage_pool_drive' defined. Greyhole can't run.
Jun 01 13:33:27 CRITICAL initialize: Config file parsing failed. Exiting.
Jun 01 13:33:27 ERROR initialize: You have no 'storage_pool_drive' defined. Greyhole can't run.
Jun 01 13:33:27 CRITICAL initialize: Config file parsing failed. Exiting.
Jun 01 13:33:27 ERROR initialize: You have no 'storage_pool_drive' defined. Greyhole can't run.
Jun 01 13:33:27 CRITICAL initialize: Config file parsing failed. Exiting.
Jun 01 13:33:27 ERROR initialize: You have no 'storage_pool_drive' defined. Greyhole can't run.
Jun 01 13:33:27 CRITICAL initialize: Config file parsing failed. Exiting.
Apologies for the typo - I meant Amahi 9.
I have clicked on the button to run FSCK and I just get the rotating circle of dots indicating activity for a moment and then it goes back to a red button.
Going through the Greyhole trouble shooting, the details are:
1. Version numbers
4.4.9-300.fc23.x86_64
samba-4.3.9-0.fc23.x86_64
amahi-greyhole-0.9.67-1.x86_64
2. the two conf files are at:
http://paste.fedoraproject.org/373315/78318514/
http://paste.fedoraproject.org/373318/47833281/
3. The result of the three commands are:
Mount
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
devtmpfs on /dev type devtmpfs (rw,nosuid,size=2015536k,nr_inodes=503884,mode=755)
securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /run type tmpfs (rw,nosuid,nodev,mode=755)
tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755)
cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/usr/lib/systemd/systemd-cgroups-agent,name=systemd)
pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer)
cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices)
cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)
cgroup on /sys/fs/cgroup/hugetlb type cgroup (rw,nosuid,nodev,noexec,relatime,hugetlb)
cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls,net_prio)
cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset)
cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory)
cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,nosuid,nodev,noexec,relatime,perf_event)
cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio)
cgroup on /sys/fs/cgroup/pids type cgroup (rw,nosuid,nodev,noexec,relatime,pids)
configfs on /sys/kernel/config type configfs (rw,relatime)
/dev/sda3 on / type xfs (rw,relatime,attr2,inode64,noquota)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=31,pgrp=1,timeout=0,minproto=5,maxproto=5,direct)
hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime)
mqueue on /dev/mqueue type mqueue (rw,relatime)
tmpfs on /tmp type tmpfs (rw)
debugfs on /sys/kernel/debug type debugfs (rw,relatime)
/dev/sda5 on /home type xfs (rw,relatime,attr2,inode64,noquota)
/dev/sda1 on /boot type ext4 (rw,relatime,data=ordered)
tmpfs on /run/user/0 type tmpfs (rw,nosuid,nodev,relatime,size=404740k,mode=700)
tmpfs on /run/user/1000 type tmpfs (rw,nosuid,nodev,relatime,size=404740k,mode=700,uid=1000,gid=100)
fdisk -1
fdisk: cannot open /dev/sr0: Permission denied
fdisk: cannot open /dev/sda: Permission denied
fdisk: cannot open /dev/sdb: Permission denied
fdisk: cannot open /dev/sdd: Permission denied
fdisk: cannot open /dev/sdc: Permission denied
df -h
Filesystem Size Used Avail Use% Mounted on
devtmpfs 2.0G 0 2.0G 0% /dev
tmpfs 2.0G 0 2.0G 0% /dev/shm
tmpfs 2.0G 696K 2.0G 1% /run
tmpfs 2.0G 0 2.0G 0% /sys/fs/cgroup
/dev/sda3 50G 1.7G 49G 4% /
tmpfs 2.0G 32K 2.0G 1% /tmp
/dev/sda5 46G 33M 46G 1% /home
/dev/sda1 477M 76M 373M 17% /boot
tmpfs 396M 0 396M 0% /run/user/0
tmpfs 396M 0 396M 0% /run/user/1000
greyhole --stats
No response - it just returned to the command prompt.
mysql -u root -phda -e "select * from disk_pool_partitions" hda_production
+----+----------------------------------------+--------------+---------------------+---------------------+
| id | path | minimum_free | created_at | updated_at |
+----+----------------------------------------+--------------+---------------------+---------------------+
| 1 | /var/hda/files/drives/Greyhole Pool #1 | 10 | 2016-06-01 08:51:10 | 2016-06-01 08:51:10 |
| 2 | /var/hda/files/drives/Greyhole Pool #2 | 10 | 2016-06-01 08:51:11 | 2016-06-01 08:51:11 |
| 3 | /var/hda/files/drives/Greyhole Pool #3 | 10 | 2016-06-01 08:51:12 | 2016-06-01 08:51:12 |
+----+----------------------------------------+--------------+---------------------+---------------------+
mysql -u root -phda -e "select concat(path, '/gh') from disk_pool_partitions" \
hda_production | grep -v 'concat(' | xargs ls -la | pastebinit
initiall came up with "ERROR 1046 (3D000) at line 1: No database selected"
and then uploaded some details to http://paste.fedoraproject.org/373325/46478420/
greyhole --view-queue
No response - it just returned to the command prompt.
tail /var/log/greyhole.log
Jun 01 13:33:26 ERROR initialize: You have no 'storage_pool_drive' defined. Greyhole can't run.
Jun 01 13:33:26 CRITICAL initialize: Config file parsing failed. Exiting.
Jun 01 13:33:27 ERROR initialize: You have no 'storage_pool_drive' defined. Greyhole can't run.
Jun 01 13:33:27 CRITICAL initialize: Config file parsing failed. Exiting.
Jun 01 13:33:27 ERROR initialize: You have no 'storage_pool_drive' defined. Greyhole can't run.
Jun 01 13:33:27 CRITICAL initialize: Config file parsing failed. Exiting.
Jun 01 13:33:27 ERROR initialize: You have no 'storage_pool_drive' defined. Greyhole can't run.
Jun 01 13:33:27 CRITICAL initialize: Config file parsing failed. Exiting.
Jun 01 13:33:27 ERROR initialize: You have no 'storage_pool_drive' defined. Greyhole can't run.
Jun 01 13:33:27 CRITICAL initialize: Config file parsing failed. Exiting.
-
Camperdownfamily
- Posts: 44
- Joined: Tue May 31, 2016 4:29 pm
Re: Greyhole Error: no 'storage_pool_drive' defined.
By the way, I forgot to mention that the bug fix for MariaDB Server appears to have worked - it is now showing as running.
Re: Greyhole Error: no 'storage_pool_drive' defined.
Your issue is likely the naming of your drives. Linux does not like spaces in the mount points. Recommend you adjust them to use underscore (_) or dash (-). Not sure if the hash (#) would cause an issue, but best to keep the naming simple. For example, I would use ghp1, ghp2, etc.storage_pool_directory = /var/hda/files/drives/Greyhole Pool #1/gh, min_free: 10gb
storage_pool_directory = /var/hda/files/drives/Greyhole Pool #2/gh, min_free: 10gb
storage_pool_directory = /var/hda/files/drives/Greyhole Pool #3/gh, min_free: 10gb
In order to fix this, you will need to uncheck them from the Greyhole UI, then unmount the drives, create new mount points, and then mount them. There should be guidance in the wiki for help with this or use the disk-wizard App.
Once you do that, you can reboot and see if that fixes your issue.
ßîgƒσστ65
Applications Manager
My HDA: Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz on MSI board, 16GB RAM, 1TBx1+2TBx2+4TBx2
Applications Manager
My HDA: Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz on MSI board, 16GB RAM, 1TBx1+2TBx2+4TBx2
-
Camperdownfamily
- Posts: 44
- Joined: Tue May 31, 2016 4:29 pm
Re: Greyhole Error: no 'storage_pool_drive' defined.
A step forwards, but now I am getting:
Jun 01 16:39:14 CRITICAL daemon: ERROR: The following storage pool drives are on the same partition: /var/hda/files/drives/Greyhole_Pool_1/gh, /var/hda/files/drives/Greyhole_Pool_2/gh, /var/hda/files/drives/Greyhole_Pool_3/gh. The Greyhole daemon will now stop.
Jun 01 16:39:14 INFO daemon: Greyhole (version 0.9.67) daemon started.
Jun 01 16:39:14 INFO daemon: Optimizing MySQL tables...
Jun 01 16:39:14 CRITICAL daemon: ERROR: The following storage pool drives are on the same partition: /var/hda/files/drives/Greyhole_Pool_1/gh, /var/hda/files/drives/Greyhole_Pool_2/gh, /var/hda/files/drives/Greyhole_Pool_3/gh. The Greyhole daemon will now stop.
Jun 01 16:39:15 INFO daemon: Greyhole (version 0.9.67) daemon started.
Jun 01 16:39:15 INFO daemon: Optimizing MySQL tables...
Jun 01 16:39:15 CRITICAL daemon: ERROR: The following storage pool drives are on the same partition: /var/hda/files/drives/Greyhole_Pool_1/gh, /var/hda/files/drives/Greyhole_Pool_2/gh, /var/hda/files/drives/Greyhole_Pool_3/gh. The Greyhole daemon will now stop.
Jun 01 16:39:15 INFO daemon: Greyhole (version 0.9.67) daemon started.
Jun 01 16:39:15 INFO daemon: Optimizing MySQL tables...
Jun 01 16:39:15 CRITICAL daemon: ERROR: The following storage pool drives are on the same partition: /var/hda/files/drives/Greyhole_Pool_1/gh, /var/hda/files/drives/Greyhole_Pool_2/gh, /var/hda/files/drives/Greyhole_Pool_3/gh. The Greyhole daemon will now stop.
Jun 01 16:39:14 CRITICAL daemon: ERROR: The following storage pool drives are on the same partition: /var/hda/files/drives/Greyhole_Pool_1/gh, /var/hda/files/drives/Greyhole_Pool_2/gh, /var/hda/files/drives/Greyhole_Pool_3/gh. The Greyhole daemon will now stop.
Jun 01 16:39:14 INFO daemon: Greyhole (version 0.9.67) daemon started.
Jun 01 16:39:14 INFO daemon: Optimizing MySQL tables...
Jun 01 16:39:14 CRITICAL daemon: ERROR: The following storage pool drives are on the same partition: /var/hda/files/drives/Greyhole_Pool_1/gh, /var/hda/files/drives/Greyhole_Pool_2/gh, /var/hda/files/drives/Greyhole_Pool_3/gh. The Greyhole daemon will now stop.
Jun 01 16:39:15 INFO daemon: Greyhole (version 0.9.67) daemon started.
Jun 01 16:39:15 INFO daemon: Optimizing MySQL tables...
Jun 01 16:39:15 CRITICAL daemon: ERROR: The following storage pool drives are on the same partition: /var/hda/files/drives/Greyhole_Pool_1/gh, /var/hda/files/drives/Greyhole_Pool_2/gh, /var/hda/files/drives/Greyhole_Pool_3/gh. The Greyhole daemon will now stop.
Jun 01 16:39:15 INFO daemon: Greyhole (version 0.9.67) daemon started.
Jun 01 16:39:15 INFO daemon: Optimizing MySQL tables...
Jun 01 16:39:15 CRITICAL daemon: ERROR: The following storage pool drives are on the same partition: /var/hda/files/drives/Greyhole_Pool_1/gh, /var/hda/files/drives/Greyhole_Pool_2/gh, /var/hda/files/drives/Greyhole_Pool_3/gh. The Greyhole daemon will now stop.
After mounting the three drives using Drive Wizard, I went into drive pooling and ticked the 'Pooled' check box against all three. Is that not the right thing to do?
Jun 01 16:39:14 CRITICAL daemon: ERROR: The following storage pool drives are on the same partition: /var/hda/files/drives/Greyhole_Pool_1/gh, /var/hda/files/drives/Greyhole_Pool_2/gh, /var/hda/files/drives/Greyhole_Pool_3/gh. The Greyhole daemon will now stop.
Jun 01 16:39:14 INFO daemon: Greyhole (version 0.9.67) daemon started.
Jun 01 16:39:14 INFO daemon: Optimizing MySQL tables...
Jun 01 16:39:14 CRITICAL daemon: ERROR: The following storage pool drives are on the same partition: /var/hda/files/drives/Greyhole_Pool_1/gh, /var/hda/files/drives/Greyhole_Pool_2/gh, /var/hda/files/drives/Greyhole_Pool_3/gh. The Greyhole daemon will now stop.
Jun 01 16:39:15 INFO daemon: Greyhole (version 0.9.67) daemon started.
Jun 01 16:39:15 INFO daemon: Optimizing MySQL tables...
Jun 01 16:39:15 CRITICAL daemon: ERROR: The following storage pool drives are on the same partition: /var/hda/files/drives/Greyhole_Pool_1/gh, /var/hda/files/drives/Greyhole_Pool_2/gh, /var/hda/files/drives/Greyhole_Pool_3/gh. The Greyhole daemon will now stop.
Jun 01 16:39:15 INFO daemon: Greyhole (version 0.9.67) daemon started.
Jun 01 16:39:15 INFO daemon: Optimizing MySQL tables...
Jun 01 16:39:15 CRITICAL daemon: ERROR: The following storage pool drives are on the same partition: /var/hda/files/drives/Greyhole_Pool_1/gh, /var/hda/files/drives/Greyhole_Pool_2/gh, /var/hda/files/drives/Greyhole_Pool_3/gh. The Greyhole daemon will now stop.
Jun 01 16:39:14 CRITICAL daemon: ERROR: The following storage pool drives are on the same partition: /var/hda/files/drives/Greyhole_Pool_1/gh, /var/hda/files/drives/Greyhole_Pool_2/gh, /var/hda/files/drives/Greyhole_Pool_3/gh. The Greyhole daemon will now stop.
Jun 01 16:39:14 INFO daemon: Greyhole (version 0.9.67) daemon started.
Jun 01 16:39:14 INFO daemon: Optimizing MySQL tables...
Jun 01 16:39:14 CRITICAL daemon: ERROR: The following storage pool drives are on the same partition: /var/hda/files/drives/Greyhole_Pool_1/gh, /var/hda/files/drives/Greyhole_Pool_2/gh, /var/hda/files/drives/Greyhole_Pool_3/gh. The Greyhole daemon will now stop.
Jun 01 16:39:15 INFO daemon: Greyhole (version 0.9.67) daemon started.
Jun 01 16:39:15 INFO daemon: Optimizing MySQL tables...
Jun 01 16:39:15 CRITICAL daemon: ERROR: The following storage pool drives are on the same partition: /var/hda/files/drives/Greyhole_Pool_1/gh, /var/hda/files/drives/Greyhole_Pool_2/gh, /var/hda/files/drives/Greyhole_Pool_3/gh. The Greyhole daemon will now stop.
Jun 01 16:39:15 INFO daemon: Greyhole (version 0.9.67) daemon started.
Jun 01 16:39:15 INFO daemon: Optimizing MySQL tables...
Jun 01 16:39:15 CRITICAL daemon: ERROR: The following storage pool drives are on the same partition: /var/hda/files/drives/Greyhole_Pool_1/gh, /var/hda/files/drives/Greyhole_Pool_2/gh, /var/hda/files/drives/Greyhole_Pool_3/gh. The Greyhole daemon will now stop.
After mounting the three drives using Drive Wizard, I went into drive pooling and ticked the 'Pooled' check box against all three. Is that not the right thing to do?
Re: Greyhole Error: no 'storage_pool_drive' defined.
That is correct.
Please post the /etc/greyhole.conf and /etc/fstab file contents.
Please post the /etc/greyhole.conf and /etc/fstab file contents.
ßîgƒσστ65
Applications Manager
My HDA: Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz on MSI board, 16GB RAM, 1TBx1+2TBx2+4TBx2
Applications Manager
My HDA: Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz on MSI board, 16GB RAM, 1TBx1+2TBx2+4TBx2
-
Camperdownfamily
- Posts: 44
- Joined: Tue May 31, 2016 4:29 pm
Re: Greyhole Error: no 'storage_pool_drive' defined.
The first link provided was the smb.conf file, not /etc/fstab as requested.
Please post.
Please post.
ßîgƒσστ65
Applications Manager
My HDA: Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz on MSI board, 16GB RAM, 1TBx1+2TBx2+4TBx2
Applications Manager
My HDA: Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz on MSI board, 16GB RAM, 1TBx1+2TBx2+4TBx2
-
Camperdownfamily
- Posts: 44
- Joined: Tue May 31, 2016 4:29 pm
Who is online
Users browsing this forum: No registered users and 18 guests