I've got my last HDA box's 2TB still sitting around, so I'll use one of them to replace the failing drive.
I used Disk Wizard to add the new drive I'd inserted and it appeared to add it and format it. I saw that it was mounted ok.
I used Greyhole UI to add the drive to the pool. I unchecked my bad drive.
Check the greyhole log, nothing was happening so I used the greyhole --going command to remove the drive. It began trawling through the storage. But shortly after, my HDA went offline; no shares and dashboard showed the DEBUG page.
I checked greyhole from the command line and it did NOT show the drive I'd added to the pool. So I guess it's tried to create copies of shares in my landing zone.
I got the new drive added to the pool the manual way and checked that it was working. I'd also left the drive removed with the going command in, and ran an FSCK to try and repopulate my shares fully.
I ran a balance command, the new drive is filling up, but my root is still full (only a 9% free now).
I cleared the greyhole work queue and reran FSCK to see if it would move files from the LZ back to storage, it didn't.
I noticed that all the files on the drive I tried to remove also went into "greyhole trash".
APASTE (0.3.8.1) isn't working, says "Error: Server did not return a correct JSON response" (*fixed!)
but here you go, https://paste.fedoraproject.org/paste/x ... bWVAaKXtJw
I've not run the --going command again till I free up my space on the OS drive, which is usually nearly empty.
Log extracts -
httpd/error_log - https://paste.fedoraproject.org/paste/j ... Jh07tH5LHg
mariadb.log - https://paste.fedoraproject.org/paste/m ... xig3bQXzIA
dnf.log - https://paste.fedoraproject.org/paste/q ... phVhz~jBAQ
Lots of critcal errors in the dnf.log, I removed the lock file, updated FPASTE and tried APASTE again - now it works.
The files I suspect are in /var/hda/files/drives
Thank you in advance for your time looking at this.