SOLVED: Greyhole status - drives offline. WD 2GB RED Issue??

[whaites]

I have 4 drives mounted and configured (actually, I don't trust one so I'm trying to add a replacement), but I cannot get greyhole to use one of them. Two drives are 1GB, these are in the pool, the third is 2GB, but I greyhole is not using it even though I have it in the pool.

[root@whaites-server tom]# greyhole -s
Greyhole Statistics
===================

Storage Pool
Total - Used = Free + Trash = Possible
/var/hda/files/drives/drive1/gh: 917G - 447G = 423G + 53G = 475G
/var/hda/files/drives/drive2/gh: Offline
/var/hda/files/drives/drive3/gh: Offline
/var/hda/files/drives/drive4/gh: 917G - 342G = 528G + 53G = 581G
==========================================
Total: 1834G - 789G = 951G + 105G = 1056G

Here, I have 3 of the 4 drives mounted (drive 3 above I am replacing).

[root@whaites-server tom]# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/sde6 46G 2.0G 42G 5% /
devtmpfs 868M 0 868M 0% /dev
tmpfs 876M 0 876M 0% /dev/shm
tmpfs 876M 704K 875M 1% /run
tmpfs 876M 0 876M 0% /sys/fs/cgroup
tmpfs 876M 20K 876M 1% /tmp
/dev/sda1 917G 448G 423G 52% /var/hda/files/drives/drive1
/dev/sdd1 917G 343G 529G 40% /var/hda/files/drives/drive4
/dev/sdb1 1.8T 68M 1.7T 1% /var/hda/files/drives/drive2
/dev/sde1 190M 61M 115M 35% /boot
/dev/sde2 94G 60M 89G 1% /home

Drive 1 and Drive 4 were actually populated by greyhole with the landing zone on Drive 2, but I cannot get greyhole to use Drive 2 for storage.

I have since moved my landing zone to drive 1, but I plan to move it back to drive 2 because it is a 2GB drive. Here is the smb.conf
http://ur1.ca/g9rvv

And my greyhole.conf
http://ur1.ca/g9rwb

Following greyhole wiki instructions, I originally tried setting storage_pool_directory for each drive. That did not work, when I changed it to storage_pool_drive, I got the 1GB drives to show up.

Finally, here is my fstab
http://ur1.ca/g9rwn

I am definitely out of ideas, help much appreciated!

[bigfoot65]

What version of Greyhole? What OS, Amahi 6 or 7?

[whaites]

Oops - forgot to include. Amahi 7 from express install disk + a yum update

3.10.5-201.fc19.x86_64
samba-4.0.8-1.fc19.x86_64
hda-greyhole-0.9.35-1.x86_64

[bigfoot65]

Thanks for the info. Have the drives that are offline been properly formatted according to the wiki?

If so, I have found "storage_pool_directory" is all that works for me with Amahi 7 and the latest Greyhole. Might try that and see what happens. Ensure you stop Greyhole service before making the changes though.

If that does not work, check the greyhole log and report back any errors.

[whaites]

Using storage_pool_directory did not make a difference for me. I repartitioned my drives following the cfdisk instructions in the wiki, but the results in fdisk -1 seem odd to me. Both 2GB drives give this message

Disk /dev/sdb: 2000.4 GB, 2000398934016 bytes, 3907029168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk label type: dos
Disk identifier: 0x00000000

Device Boot Start End Blocks Id System
/dev/sdb1 63 3907029167 1953514552+ 83 Linux
Partition 1 does not start on physical sector boundary.

Both the Disk identifier and Partition physical sector boundary messages do not seem good.

hda-diskmount gives another complaint:

****************************************************************
mount: wrong fs type, bad option, bad superblock on /dev/sdb1,
missing codepage or helper program, or other error

In some cases useful info is found in syslog - try
dmesg | tail or so.
Mounted /dev/sdb1 as '/var/hda/files/drives/drive2' (read-write)
You may want your system to mount it every time you boot.
To do so, add this line VERY CAREFULLY to /etc/fstab and reboot:
UUID=b7bae3ba-8a7a-48e3-8107-3136cc172358 /var/hda/files/drives/drive2 ext4 defaults 1 2
****************************************************************
mount: wrong fs type, bad option, bad superblock on /dev/sdc1,
missing codepage or helper program, or other error

In some cases useful info is found in syslog - try
dmesg | tail or so.
Mounted /dev/sdc1 as '/var/hda/files/drives/drive3' (read-write)
You may want your system to mount it every time you boot.
To do so, add this line VERY CAREFULLY to /etc/fstab and reboot:
UUID=b90232ce-56c6-495d-8e03-7860c8d2bc79 /var/hda/files/drives/drive3 ext4 defaults 1 2
****************************************************************
Ignoring /dev/sdd1 - already mounted
Ignoring /dev/sdd1 - already in /etc/fstab as UUID=518ee222-d02e-4269-9d52-245ed955f825
****************************************************************
Ignoring /dev/sde1 - already mounted
Ignoring /dev/sde1 - already in /etc/fstab as UUID=b8ddfd92-f2bd-4f59-83f5-b4c88286c179
****************************************************************
Ignoring /dev/sde2 - already mounted
Ignoring /dev/sde2 - already in /etc/fstab as UUID=6a89e32a-2814-40e9-8630-cbfa72209c3f
****************************************************************
Ignoring /dev/sde6 - already mounted
Ignoring /dev/sde6 - already in /etc/fstab as UUID=5a29a40e-a091-47b5-b17b-c116e7618545
****************************************************************
All Linux, Windows and Mac partitions on your disks have been mounted.
[root@whaites-server tom]# dmesg | tail
[ 34.407377] FS-Cache: Loaded
[ 34.409977] Key type dns_resolver registered
[ 34.428900] FS-Cache: Netfs 'cifs' registered for caching
[ 34.429077] Key type cifs.spnego registered
[ 34.429092] Key type cifs.idmap registered
[ 229.210523] sdb: sdb1
[ 5782.610448] sdc: sdc1
[ 5819.595874] sdb: sdb1
[ 6602.054748] EXT4-fs (sdb1): no journal found
[ 6602.191077] EXT4-fs (sdc1): no journal found

dmesg | tail gives something about no journal found for my 2gb drives

Does this suggest anything I could try?

[bigfoot65]

I would suggest unmounting those two drives. Then redo them with cfdisk. Make one partition, primary but not bootable.

Then format ext4 and try remounting them. Not sure if this applies, but might check out the wiki guidance for drives greater than 2.1TB.
https://wiki.amahi.org/index.php/Partitions_Over_2.1_TB

I presume you installed the packages required for hda-diskmount based on the wiki.
https://wiki.amahi.org/index.php/Adding ... o_your_HDA

[whaites]

I redid the partitions on both drives, after yuming the prereqs again from the wiki (I may have missed that). Now, one of the two drives shows up, even though I took the same steps on each.

[root@whaites-server tom]# greyhole -s

Greyhole Statistics
===================

Storage Pool
Total - Used = Free + Trash = Possible
/var/hda/files/drives/drive1/gh: 917G - 420G = 450G + 106G = 556G
/var/hda/files/drives/drive2/gh: Offline
/var/hda/files/drives/drive3/gh: 1834G - 0G = 1740G + 0G = 1740G
/var/hda/files/drives/drive4/gh: 917G - 336G = 534G + 104G = 638G
==========================================
Total: 3667G - 757G = 2724G + 210G = 2934G

fdisk -l shows a slight difference between the disks (and again, I took the same steps):

Disk /dev/sdb: 2000.4 GB, 2000398934016 bytes, 3907029168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk label type: dos
Disk identifier: 0x00000000

Device Boot Start End Blocks Id System
/dev/sdb1 63 3907029167 1953514552+ 83 Linux
Partition 1 does not start on physical sector boundary.

Disk /dev/sdc: 2000.4 GB, 2000398934016 bytes, 3907029168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk label type: dos
Disk identifier: 0x00000000

Device Boot Start End Blocks Id System
/dev/sdc1 63 3907029167 1953514552+ 83 Linux

The physical sector boundary is the only difference I can see. And of course, the drive greyhole can now find is the one I don't really trust, not my new drive.

I had tried the steps for a 2.1GB + sized drive, gpt drive - but I could not get hda-diskmount to find those drives either. I modified the hda-diskmount script but it still didn't find it. Maybe I'll try those steps again now after redoing the pre-req yum installs.

[bigfoot65]

Good to hear you are getting closer to a solution. Not sure why the drives are not showing up correctly. Hopefully you get it resolved.

[whaites]

Looking at the fdisk difference more carefully, now I see that the 2GB drives are not identical. The new drive has an I/O size of 4096, which is the sames as bigger drives from the wiki - so, I tried that formatting. Following the 4GB example, I didn't get any warnings, so I think that is good.

My problem now is just getting hda-diskmount to recognize. The new drive shows as /dev/type:

Ignoring /dev/sda1 - already mounted
Ignoring /dev/sda1 - already in /etc/fstab as UUID=b00ac89a-ef29-48cf-91c9-7368815e8af4
****************************************************************
Ignoring /dev/type: - already in /etc/fstab as UUID=
****************************************************************
Ignoring /dev/sdc1 - already mounted
Ignoring /dev/sdc1 - already in /etc/fstab as UUID=df7380b2-5a21-4ba9-bde3-3caa74866802
****************************************************************

fdisk -l has a different label format for the new drive

WARNING: fdisk GPT support is currently new, and therefore in an experimental phase. Use at your own discretion.

Disk /dev/sdb: 2000.4 GB, 2000398934016 bytes, 3907029168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk label type: gpt

# Start End Size Type Name
1 4096 3907028991 1.8T Microsoft basic primary

On the drives hda-diskmount finds, the first column is Device and would show sdb1, but for the new disk, it is just # and 1.

Is there an update to hda-diskmount I am missing?

[bigfoot65]

No update to the script. You can actually mount drives manually without it as well. It just gives you all the info in 1 line to add to /etc/fstab and mounts the drive for you.

Find the UUID for the drive and copy the same pattern of the other drive entries. Pick a mount point different from the others of course.

I have done it manually before and was not too hard to do without the script.