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

[whaites]

I wish I had enabled the greyhole error log about a day and a half ago. Greyhole needed to know that I changed the drive. This command fixed the offline error:

Code: Select all

greyhole --replace=/var/hda/files/drives/drive2/gh

For the record:

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

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

Storage Pool
Total - Used = Free + Trash = Possible
/var/hda/files/drives/drive1/gh: 917G - 395G = 475G + 106G = 581G
/var/hda/files/drives/drive4/gh: 917G - 395G = 475G + 106G = 581G
/var/hda/files/drives/drive2/gh: Offline
==========================================
Total: 1834G - 790G = 951G + 212G = 1163G

[root@whaites-server tom]# tail /var/log/greyhole.err
Dec 29 22:21:59 4 daemon: Warning! It seems the partition UUID of /var/hda/files/drives/drive2/gh changed. This probably means this mount is currently unmounted, or that you replaced this drive and didn't use 'greyhole --replace'. Because of that, Greyhole will NOT use this drive at this time.
[root@whaites-server tom]# greyhole --replace=/var/hda/files/drives/drive2/gh
Storage pool drive /var/hda/files/drives/drive2/gh has been marked replaced. The Greyhole daemon will now be restarted to allow it to use this new drive.
[root@whaites-server tom]# greyhole -s

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

Storage Pool
Total - Used = Free + Trash = Possible
/var/hda/files/drives/drive1/gh: 917G - 399G = 471G + 106G = 577G
/var/hda/files/drives/drive4/gh: 917G - 399G = 471G + 106G = 577G
/var/hda/files/drives/drive2/gh: 1834G - 83G = 1658G + 0G = 1658G
==========================================
Total: 3667G - 880G = 2600G + 212G = 2813G

In the end, I partitioned the drive with cfdisk per the wiki: https://wiki.amahi.org/index.php/Adding ... o_your_HDA

[bigfoot65]

Sorry about that, I feel like a rookie. That is one of the first things I typically have folks check. I guess I thought you already did and didn't ask. I overlooked the fact that this was a drive replacement. With that being said, I would have suggested the command that resolved your issue.

I suppose we both got a little wrapped up in the drive issues and overlooked the obvious path to a solution. Glad it is resolved now.