Amahi Forums

Regarding that command.

This is what I got.

5058652056 1835040276 1024

Also, I had the fsck stopped from previously runing that troubleshooter stuff. When I fsck it to get it started again (to make sure the results were accurate.) I noticed on Logmon that it was doing something else different at the fsck startup. Then it a pop up from Putty said that the server had cut the connection. When I pulled Logmon up again, it was back to trying to move the same documents again (and failing). The attached is what I got before it was disconnected.

Ok I see you have the latest version of Greyhole.

You will need to make a manual change to /etc/greyhole.conf file. Replace all occurrences of storage_pool_directory with storage_pool_drive. Once done, restart Greyhole.

If you use the greyhole-ui App, you will need to uninstall/reinstall it or the next time you make a change to storage pool or drive copies, the change will be lost. Recommend you document your settings before doing the uninstall.

Watch the log and see if the any errors are still present.

Unfortunately...no joy.

That doesn't explain anything.

Is there something you've changed when this started?

Are the errors the same? Wonder if there's a problem with one of the drives.

That would make sense. If it's trying to copy files across the Greyhole area, and one of the drives was down, it would error out...but a couple of questions:

1) By now, someones drive would have failed and you would have seen this error, right?
2) All of the disks on the dashboard are showing good.
3) Is There a way to test them through command line or some kind of Amahi app?

I know when I used to run my windows based server in a RAID array, I could see through Windows if a drive was failing. Is there something like that in an app or something I can install?

One more thing. All of those drives are newer (last year) WD Reds. I realize, of course, that they can still fail, but I wanted to put that out there.

As for changing anything. I hadn't touched the server in months before this started happening.

Could it be something malicious?

I don't mean to toot my own horn....but I am VERY careful about what I download (making sure to always check the Custom Install box in order to ensure no adware is being installed), checking certificates on HTTPS downloads, not clicking on links that aren't explained to me, etc.

Believe it or not, despite my apparent lack of knowledge of Linux, when I was in High School during the '80s I got arrested for hacking by the FBI (squatting on AT&T mainframe hard drive space to run my BBS)...luckily I was a minor and only had to pay a fine. My point is I am very vigilant about what gets on my server. So, hopefully it is not that.

I just realized something. I forgot about the Uninstalling the the UI app. I was kind of hesitant because you mentioned saving all of my settings (don't know how to do that) and I thought I might mess something up pretty bad if I uninstalled it.

Never mind! Uninstalling and reinstalling the UI worked!

Thanks for your patience!!

Uninstalling and reinstalling the UI worked!

So are all your issues resolved?

BTW to check drives for failure, you can reference the disk error alerts. I use the phpsysinfo App and have it doing the monitoring of my drives. The phpSysInfo wiki page has some guidance.

Yes it worked. Thanks for the help!

Great.

Marking as solved.